[JBoss JIRA] (JBESB-3932) JmsConnectionPool reverts to non-xa when transaction has expired
by Tom Cunningham (JIRA)
[ https://issues.jboss.org/browse/JBESB-3932?page=com.atlassian.jira.plugin... ]
Tom Cunningham resolved JBESB-3932.
-----------------------------------
Resolution: Done
> JmsConnectionPool reverts to non-xa when transaction has expired
> ----------------------------------------------------------------
>
> Key: JBESB-3932
> URL: https://issues.jboss.org/browse/JBESB-3932
> Project: JBoss ESB
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Transports
> Affects Versions: 4.10 CP1
> Reporter: Kevin Conner
> Assignee: Tom Cunningham
> Fix For: 4.11 CP3
>
> Attachments: JBESB-3932.diff
>
>
> The JmsConnectionPool test for whether to create a non-XA session or XA session does not take into account an expired transaction. The test checks for active transactions and, it not found, falls back to the non-XA API.
> The test should only check for an existing transaction, whether active or not, and allow the TransactionManager to fail when invoked.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 12 months
[JBoss JIRA] (JBESB-3932) JmsConnectionPool reverts to non-xa when transaction has expired
by Tom Cunningham (JIRA)
[ https://issues.jboss.org/browse/JBESB-3932?page=com.atlassian.jira.plugin... ]
Tom Cunningham updated JBESB-3932:
----------------------------------
Fix Version/s: 4.11 CP3
> JmsConnectionPool reverts to non-xa when transaction has expired
> ----------------------------------------------------------------
>
> Key: JBESB-3932
> URL: https://issues.jboss.org/browse/JBESB-3932
> Project: JBoss ESB
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Transports
> Affects Versions: 4.10 CP1
> Reporter: Kevin Conner
> Assignee: Tom Cunningham
> Fix For: 4.11 CP3
>
> Attachments: JBESB-3932.diff
>
>
> The JmsConnectionPool test for whether to create a non-XA session or XA session does not take into account an expired transaction. The test checks for active transactions and, it not found, falls back to the non-XA API.
> The test should only check for an existing transaction, whether active or not, and allow the TransactionManager to fail when invoked.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 12 months
[JBoss JIRA] (JBESB-2558) monitoring.cfg.xml not found
by Tom Cunningham (JIRA)
[ https://issues.jboss.org/browse/JBESB-2558?page=com.atlassian.jira.plugin... ]
Work on JBESB-2558 stopped by Tom Cunningham.
> monitoring.cfg.xml not found
> -----------------------------
>
> Key: JBESB-2558
> URL: https://issues.jboss.org/browse/JBESB-2558
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Management
> Affects Versions: 4.4 CP2
> Reporter: Kevin Conner
> Assignee: Tom Cunningham
> Labels: soa_subject_to_time
> Fix For: 4.4 CP5
>
>
> The configuration of the management services is currently broken, leaving an opportunity for the following exception to be thrown.
> org.hibernate.HibernateException: monitoring.cfg.xml not found
> at org.hibernate.util.ConfigHelper.getResourceAsStream(ConfigHelper.java:147)
> at org.hibernate.cfg.Configuration.getConfigurationInputStream(Configuration.java:1405)
> at org.hibernate.cfg.Configuration.configure(Configuration.java:1427)
> at org.jboss.soa.esb.monitoring.MonitoringSessionFactory.init(MonitoringSessionFactory.java:80)
> at org.jboss.soa.esb.monitoring.MonitoringSessionFactory.getInstance(MonitoringSessionFactory.java:68)
> at org.jboss.soa.esb.monitoring.client.OperationsCollector.getClassPatterns(OperationsCollector.java:84)
> at org.jboss.soa.esb.monitoring.client.OperationsCollector.collectData(OperationsCollector.java:165)
> at org.jboss.soa.esb.monitoring.client.OperationsCollectorAction.collectOperations(OperationsCollectorAction.java:72)
> The reason for this issue is that the monitoring services specified in jbossesb.esb have an implicit dependency on a jar provided in management.esb but management.esb has an explicit dependency on jbossesb.esb. This will, therefore, leave a window where the management configuration may be required *before* the jar has been loaded.
> The implicit dependency is caused by the requirement of jbossesb.esb/management-client.jar to access the monitoring.cfg.xml file included in management.esb/management-server.jar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 12 months