From: chuckharris <nu...@jb...> - 2004-07-15 16:30:50
|
Thanks for the reply. I converted to using UIL2 ejb-jar.xml: <resource-ref> | <res-ref-name>jms/UIL2ConnectionFactory</res-ref-name> | <res-type>javax.jms.UIL2ConnectionFactory</res-type> | <res-auth>Container</res-auth> | </resource-ref> jboss.xml: <resource-ref> | <res-ref-name>jms/UIL2ConnectionFactory</res-ref-name> | <jndi-name>queue/MY_Queue</jndi-name> | </resource-ref> but the same exception is thrown, although it does take a few seconds longer to fail than before: Logging: The provider name from jndi is ip:1099 09:04:54,380 DEBUG [main] [messages.JMSMessageUtils] *** jndicontext created 09:04:54,380 DEBUG [main] [messages.JMSMessageUtils] Looking up UILConnectionFactory in JNDI 09:04:58,847 DEBUG [main] [messages.JMSMessageUtils] *** obj created with jndicontext org.jboss.mq.SpyConnectionFactory@7a1576 org.jboss.mq.SpyJMSException: Cannot authenticate user; - nested throwable: (java.net.ConnectException: Connection refus ed: connect) at org.jboss.mq.Connection.authenticate(Connection.java:883) at org.jboss.mq.Connection.(Connection.java:238) at org.jboss.mq.Connection.(Connection.java:315) at org.jboss.mq.SpyConnection.(SpyConnection.java:60) at org.jboss.mq.SpyConnectionFactory.createQueueConnection(SpyConnectionFactory.java:116) at messages.AsyncObjectMessageClient.send(Unknown Source) at messages.CommandLineWorkcaseInvoker.main(Unknown Source) Caused by: java.net.ConnectException: Connection refused: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:169) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158) at java.net.Socket.connect(Socket.java:452) at java.net.Socket.connect(Socket.java:402) at java.net.Socket.(Socket.java:309) at java.net.Socket.(Socket.java:153) at javax.net.DefaultSocketFactory.createSocket(DashoA6275) at org.jboss.mq.il.uil2.UILServerIL.createConnection(UILServerIL.java:579) at org.jboss.mq.il.uil2.UILServerIL.getSocketMgr(UILServerIL.java:500) at org.jboss.mq.il.uil2.UILServerIL.authenticate(UILServerIL.java:302) at org.jboss.mq.Connection.authenticate(Connection.java:876) ... 6 more 09:05:20,898 ERROR [main] [messages.AsyncObjectMessageClient] jmsex Cannot authenticate user; - nested throwable: (java.net.ConnectException: Connection refused: connect) Since the uil2 change did not fix the issue, is there a reason (performance or otherwise) not to leave it using uil? I can send messages to the queue from the app server to itself. It just fails from the client. Is there a security setting in 1.4.2 that I need to make that I didn't with 1.3.1? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3842278#3842278 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3842278 |