[JBoss JIRA] Created: (JBESB-2106) JBR listener doesn't return error to a client
by Martin Vecera (JIRA)
JBR listener doesn't return error to a client
---------------------------------------------
Key: JBESB-2106
URL: https://jira.jboss.org/jira/browse/JBESB-2106
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.4
Reporter: Martin Vecera
When I'm using JBR listener in synchronous way, I'm not able to find out whether the message was successfully delivered.
JBossRemotingGatewayListener, method invoke(), line 345:
Object response = messageDeliveryAdapter.deliverSync(invocationRequest, 20000);
When an exception is thrown (e.g. SecurityServiceException), the client is never informed of this problem. As a response it simply gets null. I'd expect for the client to get the exception.
--
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
15 years, 5 months
[JBoss JIRA] Created: (JBESB-1965) Poor Exception Message "doesn't define a Message-Aware Listener"
by Burr Sutter (JIRA)
Poor Exception Message "doesn't define a Message-Aware Listener"
----------------------------------------------------------------
Key: JBESB-1965
URL: https://jira.jboss.org/jira/browse/JBESB-1965
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.4
Reporter: Burr Sutter
Priority: Minor
This message should also indicate that an InVM listener can also be used by adding invmScope="GLOBAL" to the service declaration.
12:31:43,355 WARN [ServiceController] Problem starting service jboss.esb:deploy
ment=Quickstart_helloworld_http.esb
java.lang.RuntimeException: org.jboss.soa.esb.ConfigurationException: Service co
nfiguration for Service 'HelloWorld:HelloWorld_HTTP' doesn't define a Message-Aw
are Listener (i.e. is-gateway='false').
at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration
.java:138)
at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment.startService(J
Boss4ESBDeployment.java:99)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
--
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
15 years, 5 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-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
15 years, 6 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.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
15 years, 6 months