Nice catch Scott. That stack trace was coming from a hot deployment of
jbossmq-service.xml to change from UIL2 to UIL without changing the JNDI name. I
copied and pasted the wrong stack trace. Sorry for the mistake.
The real stack trace from my UIL2 problem is below. The UIL2 works a couple of times.
The client then starts to get this exception.
******** ERROR Jul 11 17:48:55 [ddk.j2ee.FWAEventSender] -
Exception:org.jboss.mq.SpyJMSException: Cannot authenticate user; - nested throwable:
(java.net.SocketException: errno: 125, error: Address already in use for fd: 56)
at org.jboss.mq.Connection.authenticate(Connection.java:883)
at org.jboss.mq.Connection.<init>(Connection.java:238)
at org.jboss.mq.SpyConnection.<init>(SpyConnection.java:48)
at
org.jboss.mq.SpyConnectionFactory.createQueueConnection(SpyConnectionFactory.java:135)
at com.fusura.xcs.ddk.j2ee.FWAEventSender.sendMessage(FWAEventSender.java:180)
at
com.fusura.xcs.ddk.j2ee.FWAEventSender.sendDispositionEvent(FWAEventSender.java:157)
at
com.fusura.xcs.southsea.csr.DispositionFormHandler.handleUpdate(DispositionFormHandler.java:68)
at java.lang.reflect.Method.invoke(Native Method)
at atg.droplet.EventSender.sendEvent(EventSender.java:528)
at atg.droplet.FormTag.doSendEvents(FormTag.java:687)
at atg.droplet.FormTag.sendEvents(FormTag.java:592)
at atg.droplet.DropletEventServlet.sendEvents(DropletEventServlet.java:245)
at atg.droplet.DropletEventServlet.service(DropletEventServlet.java:262)
at
atg.servlet.pipeline.PipelineableServletImpl.service(PipelineableServletImpl.java:224)
at
atg.servlet.pipeline.DispatcherPipelineServletImpl.service(DispatcherPipelineServletImpl.java:146)
at
atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:114)
at
atg.servlet.pipeline.MimeTyperPipelineServlet.service(MimeTyperPipelineServlet.java:204)
at
atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:114)
at atg.servlet.pipeline.FileFinderPipelineServlet.service(Unknown Source)
at
atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:114)
at
atg.servlet.pipeline.DispatcherPipelineServletImpl.service(DispatcherPipelineServletImpl.java:163)
at
atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:114)
at atg.servlet.CgiServlet.serviceRequest(Unknown Source)
at atg.servlet.CgiServlet.service(Unknown Source)
at
atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:114)
at
atg.servlet.pipeline.WebApplicationDispatcherPipelineServlet.service(WebApplicationDispatcherPipelineServlet.java:64)
at atg.servlet.pipeline.PipelineableServletImpl.passRequest(Pipelineabl
-----Original Message-----
From: Scott M Stark [mailto:[EMAIL PROTECTED]
Sent: Friday, July 11, 2003 12:35 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] JMS behind a firewall.
The previous message shown an exception due to the jms destination
being shutdown due
undeployment of the destination service descriptor. This cannot be
triggered by the close of
the jms connection so how is that coming about?
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
On Friday, July 11, 2003, at 06:11 AM, Lyvers, William wrote:
> Hauer,
>
> This is the code that is executing on each request. At this point in
> time, we haven't even began caching off the context and such. One
> thing that I did notice, is that we are binding the clients to one
> port using the org.jboss.mq.il.uil2.localAddr and
> org.jboss.mq.il.uil2.localPort system properites from the client side.
> I am not sure if this would make a difference, since we are doing
> this for uil as well. I haven't had a chance to test taking these
> properties out. I believe we were originally setting these when
> trying to get through our firewall.
>
>
> InitialContext iniCtx = new InitialContext( env );
> QueueConnectionFactory qcf = (QueueConnectionFactory)
> iniCtx.lookup( QUEUE_CONNECTION_FACTORY );
> QueueConnection conn =
> qcf.createQueueConnection(USERID,PASSWORD);
> Queue que = (Queue) iniCtx.lookup(EVENT_QUEUE);
> QueueSession session = conn.createQueueSession(false,
> QueueSession.AUTO_ACKNOWLEDGE);
> conn.start();
> QueueSender send = session.createSender(que);
> ObjectMessage om = session.createObjectMessage( message );
>
> om.setStringProperty ("MessageType", messageType );
> send.send(om);
> send.close();
> conn.stop();
> session.close();
> conn.close();
>
>
> Thanks,
> Billy
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
