Failed JMS Environment: ConnectionFactory
oosie Mar 22, 2012 1:46 PMI'm trying to use JMS in a clustered JBoss AS 7 environment. I'm using JBoss AS 7.1.1.Final in order to achieve this.
I followed the instructions as described in the following document: https://docs.jboss.org/author/display/AS71/AS7+Cluster+Howto
I have one master and three slaves defined. I can start-up the master and when I start-up the slaves, the correctly authenticate to the master. So far, so good.
The documentation doesn't cover any specifics regarding JMS configuration in a cluster. It'll be best efforts from this point on.
I'm using the InitialContext approach (with an emtpy Environment) in order to get the ConnectionFactory:
new InitialContext(new Properties()).lookup("java:/ConnectionFactory");
However, when trying to deploy my application I get the following exception:
An error occurred while trying to set up!: com.icesoft.net.messaging.MessageServiceException: javax.naming.NameNotFoundException: ConnectionFactory -- service jboss.naming.context.java.ConnectionFactory
When starting up the JBoss instances I see the following in the logs as well:
[Server:server-three-node1] JBAS014775: New missing/unsatisfied dependencies:
[Server:server-three-node1] service jboss.binding.jacorb (missing) dependents: [service jboss.jacorb.orb-service]
[Server:server-three-node1] service jboss.binding.jacorb-ssl (missing) dependents: [service jboss.jacorb.orb-service]
[Server:server-three-node1] service jboss.binding.messaging (missing) dependents: [service jboss.messaging.default]
[Server:server-three-node1] service jboss.binding.messaging-throughput (missing) dependents: [service jboss.messaging.default]
The server-three-node1 is defined according to the document:
<server name="server-three-node1" group="other-server-group" auto-start="true">
<socket-bindings port-offset="250"/>
</server>
The other-server-group is defined as default:
<server-group name="other-server-group" profile="full-ha">
<jvm name="default">
<heap size="64m" max-size="512m"/>
</jvm>
<socket-binding-group ref="ha-sockets"/>
</server-group>
Now I noticed that the ha-sockets socket-binding-group lacked declarations for the jacorb, jacorb-ssl, messaging and messaging-throughput ports. But switching to full-ha-sockets didn't help. I'm still getting the JBAS014775 message in the logs and I still can't lookup the ConnectionFactory.
What am I missing?
Thanks,
Jack...