[
https://issues.apache.org/jira/browse/TUSCANY-3634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder closed TUSCANY-3634.
------------------------------
Resolution: Fixed
Thanks for finding this bug. Its now fixed in 1.x and 2.x trunks.
If you need a patched jar or new release done that contains the fix please
reopen the JIRA saying what you need.
> JMS Session is not closed when replyDest is null, then OutOfMemoroy
> --------------------------------------------------------------------
>
> Key: TUSCANY-3634
> URL: https://issues.apache.org/jira/browse/TUSCANY-3634
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA JMS Binding Extension
> Affects Versions: Java-SCA-1.6
> Reporter: i0505
>
> in
> \modules\binding-jms-runtime\src\main\java\org\apache\tuscany\sca\binding\jms\transport\TransportServiceInterceptor.java,
>
> when (1) is executed, (2) never,so there is a memory leak that finally
> cause OutOfMemoroy error.
> public Message invokeResponse(Message msg) {
> try {
> ... ...
> JMSBindingContext context = msg.getBindingContext();
> Session session = context.getJmsResponseSession();
> ... ...
> if (replyDest == null) {
> // assume no reply is expected
> if (msg.getBody() != null) {
> logger.log(Level.FINE, "JMS service '" +
> service.getName() + "' dropped response as request has no replyTo");
> }
> return msg; //(1)
> }
>
> ... ...
> context.closeJmsResponseSession(); //(2)
>
> return msg;
>
> } catch (JMSException e) {
> throw new JMSBindingException(e);
> }
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
