You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Martin Kreidenweis (Updated) (JIRA)" <ji...@apache.org> on 2011/09/29 10:44:45 UTC
[jira] [Updated] (OFBIZ-4453) Refactoring JMS Handling
[ https://issues.apache.org/jira/browse/OFBIZ-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Kreidenweis updated OFBIZ-4453:
--------------------------------------
Attachment: JMS-keep-connection.patch
We already made some code changes to reuse the ActiveMQ connection for sending data:
* Created JmsServiceJndiConfiguration class, which has the JNDI specific configuration
* Created JmsServiceSession class, which holds all data associated to an open connection to ActiveMW so that all resources can be closed appropriately
* Adapted the JmsServiceEngine to check if the connection was not open and to reopen a connection on failing to connect to ActiveMQ
> Refactoring JMS Handling
> ------------------------
>
> Key: OFBIZ-4453
> URL: https://issues.apache.org/jira/browse/OFBIZ-4453
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
> Reporter: Dimitri Unruh
> Attachments: JMS-keep-connection.patch
>
>
> This is the main ticket for the JMS refactoring tasks.
> I would like to start here some concept discussion ant the create sub-tasks...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira