[JBoss JIRA] Created: (JBESB-2586) DefaultJMSPropertiesSetter should filter out all JMS vendor specific properties
by Kevin Conner (JIRA)
DefaultJMSPropertiesSetter should filter out all JMS vendor specific properties
-------------------------------------------------------------------------------
Key: JBESB-2586
URL: https://jira.jboss.org/jira/browse/JBESB-2586
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Transports
Affects Versions: 4.5
Reporter: Kevin Conner
Assignee: Daniel Bevenius
…
[View More] Fix For: 4.6
JBESB-2287 introduced filtering into the DefaultJMSPropertiesSetter but this is only usable in certain circumstances.
One area which cannot use this, at present, is the JmsCourier created from EPRs. Listeners can therefore introduce properties which should be filtered.
We are already filtering out all JMS Header properties, that is properties that start with JMSX.
We should also be filtering out JMS Vendor specific properties, that is properties that start with JMS_. These properties can be read-only and there will be no way for us to re-set them when sending outbound JMS Messages so it makes no sense extracting them either.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
15 years, 10 months
[JBoss JIRA] Created: (JBESB-1774) Messages are returned to client from the wrong service
by Mika Leino (JIRA)
Messages are returned to client from the wrong service
------------------------------------------------------
Key: JBESB-1774
URL: http://jira.jboss.com/jira/browse/JBESB-1774
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Process flow
Affects Versions: 4.2.1 CP1
Environment: Windows Server 2003
Reporter: Mika Leino
Attachments: service_A_jboss-…
[View More]esb.xml, service_B_jboss-esb.xml
We have a setup in which a client calls an ESB service (service A) with a webservice interface and this service then calls on another ESB service (service B). Both of the services have their action pipelines set to be "RequestResponse".
For some reason the first attempt to handle the client's message always fails as the message is returned to the client from service B. As the message never returns to service A it assumes an unresponsive EPR and resends the message which on the second attempt returns to service A.
The first attempt looks like this:
client -> service A -> service B -> client
And the second like this:
(client ->) service A -> service B -> service A -> client
Unfortunately the client interpreters the first response as the one it is waiting for and fails as service A has not made the necessary changes to the message. The second attempt produces a valid response but the client is no longer listening for it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
15 years, 10 months
[JBoss JIRA] Created: (JBESB-2186) monitoring.cfg.xml not found
by Kevin Conner (JIRA)
monitoring.cfg.xml not found
-----------------------------
Key: JBESB-2186
URL: https://jira.jboss.org/jira/browse/JBESB-2186
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Management
Reporter: Kevin Conner
The configuration of the management services is currently broken, leaving an opportunity for the following exception to be thrown.
org.hibernate.…
[View More]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 contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
15 years, 10 months