[
https://issues.apache.org/jira/browse/TUSCANY-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramkumar Ramalingam resolved TUSCANY-2922.
------------------------------------------
Resolution: Fixed
Thanks for the patch Greg.
Committed at revision 755969 and 755970 in 1.x.
> Miscellaneous binding.jms fixes
> -------------------------------
>
> Key: TUSCANY-2922
> URL: https://issues.apache.org/jira/browse/TUSCANY-2922
> Project: Tuscany
> Issue Type: Bug
> Reporter: Greg Dritschler
> Assignee: Ramkumar Ramalingam
> Attachments: tuscany-2922.patch
>
>
> I am attaching a patch with miscellaneous JMS fixes described below.
> JMSBindingProcessor
> - don't throw JMSBindingException for validation errors, since they are
> already reported via monitor interface
> - remove validationMessage member variable, which is not thread-safe
> JMSBindingContext
> - add methods to close request and response session, so that the session
> variable gets cleaned up
> JMSResourceFactory/JMSResourceFactoryImpl
> - add query method to find out whether connections must be closed after use,
> for environments where connections cannot be held open indefinitely (e.g.
> connection sharing environment)
> JMSBindingServiceBindingProvider
> - don't set a default destination if an activationSpec is used, since the
> activation spec provides a destination
> RRBJMSBindingInvoker
> - defer lookup of statically-configured callback response destination until
> needed
> - close request connection after use if resource factory requires it
> TransportReferenceInterceptor/TransportServiceInterceptor
> - use binding context to close response session
> - close response connection after use if resource factory requires it
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
