[JBoss JIRA] Created: (JBESB-3549) Race in jUDDI UDDIClientContainer
by Kevin Conner (JIRA)
Race in jUDDI UDDIClientContainer
---------------------------------
Key: JBESB-3549
URL: https://issues.jboss.org/browse/JBESB-3549
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Registry and Repository
Affects Versions: 4.9 CP1
Reporter: Kevin Conner
Assignee: Kevin Conner
Fix For: 4.9 CP1
Results in failures during ESB service registration
Exception detected by:`Caused by: org.jboss.soa.esb.services.registry.RegistryException: org.apache.ws.scout.transport.TransportException: java.lang.Exception: Cannot locate configuration source META-INF/uddi.xml
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (JBESB-3550) Aggregator doesn't work with XA transaction rollback
by Michael Burman (JIRA)
Aggregator doesn't work with XA transaction rollback
----------------------------------------------------
Key: JBESB-3550
URL: https://issues.jboss.org/browse/JBESB-3550
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Process flow
Affects Versions: 4.9
Reporter: Michael Burman
If Aggregator's service fails, it will rollback one instance of the message, and thus in the following round when reading the messages from queue, it will never finish as it expects several messages.
Patched Aggregator with printing out the MessageId (for better logs):
2010-12-20 15:06:17,162 INFO [STDOUT] (Thread-12 (group:HornetQ-client-global-threads-320732754)) Received message: 7c7b6080-485c-4f6e-9f40-8c49f676cb76
2010-12-20 15:06:17,984 INFO [STDOUT] (Thread-3 (group:HornetQ-client-global-threads-320732754)) Received message: 7c7b6080-485c-4f6e-9f40-8c49f676cb76
2010-12-20 15:06:18,305 ERROR [org.hornetq.ra.inflow.HornetQMessageHandler] (Thread-3 (group:HornetQ-client-global-threads-320732754)) Failed to deliver message
java.lang.RuntimeException:
2010-12-20 15:06:18,356 INFO [STDOUT] (Thread-12 (group:HornetQ-client-global-threads-320732754)) Received message: 7c7b6080-485c-4f6e-9f40-8c49f676cb76
So not everything is rolled back to the original queue and thus when Aggregator waits for the other message, it will fail.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (JBESB-3544) Same bus-id's in jboss-esb.xml are allowed
by Johan Kumps (JIRA)
Same bus-id's in jboss-esb.xml are allowed
------------------------------------------
Key: JBESB-3544
URL: https://issues.jboss.org/browse/JBESB-3544
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Configuration
Affects Versions: 4.9
Reporter: Johan Kumps
Strange behavior can be experienced when you configure multiple jms-bus 's in jboss-esb.xml having the same bus-id. In this case multiple services are listining to the same channel. The component validating the jboss-esb.xml configuration file should report this as an error.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years