April 2009 - esb-issues - Jboss List Archives

[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

16 years, 11 months

4
11
0 / 0

[JBoss JIRA] Created: (JBESB-1904) The stateful working memory cannot be disposed based on rules processing

by Jiri Pechanec (JIRA)

The stateful working memory cannot be disposed based on rules processing ------------------------------------------------------------------------ Key: JBESB-1904 URL: https://jira.jboss.org/jira/browse/JBESB-1904 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.4 Reporter: Jiri Pechanec Fix For: 4.4 CP1 It should be very useful to control disposing of stateful working memory based on outcome of rules execution. Unfortunately this is not possible as the dispose message property is checked before rule execution. -- 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

16 years, 11 months

4
6
0 / 0

[JBoss JIRA] Created: (JBESB-2495) Merge JBESB-2492: Smooks transformer in WSSecurityInfoExtractor should probably use SAX filter

by Tom Fennelly (JIRA)

Merge JBESB-2492: Smooks transformer in WSSecurityInfoExtractor should probably use SAX filter ---------------------------------------------------------------------------------------------- Key: JBESB-2495 URL: https://jira.jboss.org/jira/browse/JBESB-2495 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.5 Reporter: Tom Fennelly Fix For: 4.6 Is currently using the DOM filter (default). Should use the SAX filter for performance reasons. -- 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

16 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-2494) Merge JBESB-2252: JBossRemotingMessageComposer should have the security extractors as fields and not create them everytime.

by Tom Fennelly (JIRA)

Merge JBESB-2252: JBossRemotingMessageComposer should have the security extractors as fields and not create them everytime. --------------------------------------------------------------------------------------------------------------------------- Key: JBESB-2494 URL: https://jira.jboss.org/jira/browse/JBESB-2494 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.4 CP1 Reporter: Tom Fennelly Assignee: Daniel Bevenius Fix For: 4.5 This task mainly concerns the WSSecurityInfoExtractor which uses Smooks and the current impl will in effect create a new Smooks instance upon every call. Making this a field will have it create only once. I'd did this so I bow my head in shame :( I discovered this issue when investigating this user forum thread: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4198266#4198266 -- 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

16 years, 11 months

3
5
0 / 0

[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

16 years, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-2455) SoapUIClientService does not populate request attributes

by Joakim Sandström (JIRA)

SoapUIClientService does not populate request attributes -------------------------------------------------------- Key: JBESB-2455 URL: https://jira.jboss.org/jira/browse/JBESB-2455 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.5, 4.4 CP2 Reporter: Joakim Sandström SoapUIClientService only appears to handle population of text elements and not the attributes. expected request: <soapenv:Body> <ns:updateCustomer customerId="124343"> <ns:name> <ns:firstName>FIRSTNAME</ns:firstName> actual request: <soapenv:Body> <ns:updateCustomer customerId="?"> <ns:name> <ns:firstName>FIRSTNAME</ns:firstName> -- 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

16 years, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-2381) XMLBeansModel: toProperties method should handle configs that contain attribute and element value content

by Tom Fennelly (JIRA)

XMLBeansModel: toProperties method should handle configs that contain attribute and element value content --------------------------------------------------------------------------------------------------------- Key: JBESB-2381 URL: https://jira.jboss.org/jira/browse/JBESB-2381 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.5 Reporter: Tom Fennelly Fix For: 4.6 The toProperties method currently only handles mapping values defined on the "value" attribute. It doesn't handle property values defined as element content, or both element and on the attribute. -- 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

16 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2519) ServiceClient hides some errors which makes debugging config problems difficult

by toby cabot (JIRA)

ServiceClient hides some errors which makes debugging config problems difficult ------------------------------------------------------------------------------- Key: JBESB-2519 URL: https://jira.jboss.org/jira/browse/JBESB-2519 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: toby cabot Priority: Minor I accidentally mis-configured a node with a "-b" bind address of "0.0.0.0". This causes a pretty obvious problem for other nodes that want to connect to it - they try to connect to themselves. Unfortunately ServiceClient swallows the error data and just emits "Failed to get JMS Session from pool" which can have 3 different causes. For example: 2009-04-13 09:52:30,937 DEBUG [org.jboss.soa.esb.client.ServiceInvoker] Caught service lookup exception for EPR [JMSEpr [ PortReference < <wsa:Address jms://10.18.2.178:1099/queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 10.18.2.178:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ]] and Service [JBossESB-Internal:DeadLetterService] and Message [header: [ To: JMSEpr [ PortReference < <wsa:Address jms://10.18.2.178:1099/queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 10.18.2.178:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: 05576e08-115c-4233-b417-262b7b174c47 RelatesTo: jms:correlationID#05576e08-115c-4233-b417-262b7b174c47 ]]. Failed to get JMS Session from pool. -- 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

16 years, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-2522) twiddle get for ServiceMessageCounter causes NPE

by toby cabot (JIRA)

twiddle get for ServiceMessageCounter causes NPE ------------------------------------------------ Key: JBESB-2522 URL: https://jira.jboss.org/jira/browse/JBESB-2522 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.4 Reporter: toby cabot Using twiddle to "get" ServiceMessageCounter properties trips a NullPointerException: jboss-4.2.1.GA/bin$ ./twiddle.sh get jboss.esb:category=MessageCounter,deployment=jbossesb.esb,service-name=DeadLetterService 11:39:24,423 ERROR [Twiddle] Exec failed java.lang.NullPointerException at org.jboss.soa.esb.listeners.message.ServiceMessageCounter.getAttributes(ServiceMessageCounter.java:300) at org.jboss.mx.server.RawDynamicInvoker.getAttributes(RawDynamicInvoker.java:140) at org.jboss.mx.server.MBeanServerImpl.getAttributes(MBeanServerImpl.java:571) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:818) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:419) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) at sun.rmi.transport.Transport$1.run(Transport.java:153) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:149) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707) at java.lang.Thread.run(Thread.java:613) -- 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

16 years, 11 months

4
6
0 / 0

[JBoss JIRA] Created: (JBESB-2236) Investigate drools flow support

by Kevin Conner (JIRA)

Investigate drools flow support ------------------------------- Key: JBESB-2236 URL: https://jira.jboss.org/jira/browse/JBESB-2236 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.4 Reporter: Kevin Conner Fix For: 4.5 Attachments: bpm_orchestration_flow_1.zip -- 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

16 years, 11 months

2
11
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues April 2009