Patches item #968074, was opened at 2004-06-07 13:02 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376687&aid=968074&group_id=22866
Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Sozonnik Andrew (sozonnik) Assigned to: Nobody/Anonymous (nobody) Summary: Connect to external JMS provider Initial Comment: I had a task to connect one JBoss to another via JMS through the firewall. I've discovered 2 problems with it. First I can't specify JMSConnectionFactory - it hardcoded to "org.jnp.interfaces.NamingContextFactory" but because I have firewall I need "org.jboss.naming.HttpNamingContextFactory". So a I've added parameter "Factory" to "org.jboss.jms.jndi.JMSProviderLoader" MBean. Second, when connection was established, and I shutdown and then startup JBoss that acts as JMS server another server won't to reconnect, because "JMSContainerInvoker" catch only JMSException, not NamingException that can happened because I use "org.jboss.naming.ExternalContext" to connect to remote JMS. So I've added NamingException processing to "JMSContainerInvoker". I include all files that I change to attachment file. Used JBoss 3.2.3 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376687&aid=968074&group_id=22866 ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
