synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SYNAPSE-448) NullPointerException in JMSSender when JMS config details defined in axis2.xml
Date Mon, 15 Sep 2008 19:11:44 GMT

    [ https://issues.apache.org/jira/browse/SYNAPSE-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631105#action_12631105
] 

Andreas Veithen commented on SYNAPSE-448:
-----------------------------------------

The resource leak was actually due to the fact that the sender doesn't close the JMS connections
when the transport is stopped. This is now corrected in trunk.

> NullPointerException in JMSSender when JMS config details defined in axis2.xml
> ------------------------------------------------------------------------------
>
>                 Key: SYNAPSE-448
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-448
>             Project: Synapse
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 1.2
>         Environment: Any
>            Reporter: Jason Royals
>            Assignee: Andreas Veithen
>
> I am proxying a JMS service over HTTP.  The JMS service responds with some XML, so the
JMSSender expects a reply.  To make my endpoint more reusable, I'm putting the JMS connection
details in axis2.xml (as detailed in SYNAPSE-183).  What's actually happening though is that
the HTTP client is just timing out.  I ran the debugger over Synapse to see what was going
on, and it looks like a defect with the implementation of that feature.
> To listen for a JMS reply from the endpoint, Synapse starts a connection (JMSSender:267)
after sending the message.  However, this connection is only ever initialised if the JMS connection
is _not_ defined in axis2.xml, due to the if/else that checks for an already established connectionFactory
at the key "transport.jms.ConnectionFactory" (JMSSender:119).  This means the connection is
always null when using this feature, and a NPE will be thrown at line 267.
> I'll supply a test if required.
> Cheers,
> Jason

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


Mime
View raw message