JMS ConnectionFactory not bound issue

[anil.saldhana]

As of yesterday, I am seeing the following error affecting some of the MDB tests.

ConnectionFactory not bound

javax.naming.NameNotFoundException: ConnectionFactory not bound
 at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
 at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)
 at org.jnp.server.NamingServer.getObject(NamingServer.java:785)
 at org.jnp.server.NamingServer.lookup(NamingServer.java:443)
 at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
 at sun.rmi.transport.Transport$1.run(Transport.java:153)
 at java.security.AccessController.doPrivileged(Native Method)
 at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
 at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
 at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
 at java.lang.Thread.run(Thread.java:595)
 at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
 at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
 at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
 at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
 at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:713)
 at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:673)
 at javax.naming.InitialContext.lookup(InitialContext.java:351)
 at org.jboss.test.security.test.EJBSpecUnitTestCase.testMDBRunAs(EJBSpecUnitTestCase.java:601)
 at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
 at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
 at junit.extensions.TestSetup.run(TestSetup.java:25)

Was this the messaging upgrade or something in "connector"?

[anil.saldhana]

Question is whether there is a replacement for "connection-factories-service.xml" in AS5? If not, then this file is missing with the latest messaging upgrade.

[anil.saldhana]

This file is supposed to be bundled as per the messaging workspace.

anil@localhost:~/messaging/Branch_1_4$ find . -name connection-factories-service.xml
./integration/EAP4/etc/server/default/deploy/connection-factories-service.xml
./integration/AS5/etc/server/default/deploy/connection-factories-service.xml
./output/etc/server/default/deploy/connection-factories-service.xml
./output/jar/connection-factories-service.xml

[anil.saldhana]

I am going to fix this by adding this file to the messaging module in AS5 workspace until the messaging team figures out a AS release plan that verifies that their releases do not mess. ;)

[brian.stansberry]

[semi-OT] This is probably the cause of the aborted testsuite runs; probably fails the JBM ClusteredTestCase and that prevents the shutdown of one of the servers. I'm changing the ClusteredTestCase to add logic to ensure it cleans up after itself.