March 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2361) Return the http error code and message in JBossRemotingGateway Listener.

by Jim Ma (JIRA)

Return the http error code and message in JBossRemotingGateway Listener. ------------------------------------------------------------------------- Key: JBESB-2361 URL: https://jira.jboss.org/jira/browse/JBESB-2361 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Reporter: Jim Ma Assignee: Jim Ma Fix For: 4.5 When there is FaultMessageException occurred, Jbr listener can not return the error code and detail message to client. -- 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, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-1909) JmsConnectionPool overflows sometimes with JBossMQ

by Pavel Kadlec (JIRA)

JmsConnectionPool overflows sometimes with JBossMQ -------------------------------------------------- Key: JBESB-1909 URL: https://jira.jboss.org/jira/browse/JBESB-1909 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.3 Environment: JBossAS-4.2.2.GA with JBossMQ Reporter: Pavel Kadlec The core reason is that JBossMQ's XAConnectionFactory.createSession always creates XASession (is always transacted and with SESSION_TRANSACTED acknowledgement mode), but JBossMessaging's XAConnectionFactory.createSession creates non-xa Session (transacted or non-transacted and with customized acknowledgement mode). The JmsConnectionPool is intended to be used with JBossMessaging behaviour only. The overflow occurs when caller thread associated with *NO* transaction sends esb message (by jms courier) using *XAConnectionFactory* to the esb service. In this case the connection pool uses XAConnectionFactory.createSession for creating the session. The pool has hashmaps which key is acknowledgement mode. JBossMQ's XAConnectionFactory.createSession always creates Session with SESSION_TRANSACTED acknowledgement mode. But the pool registers the session under customized acknowledgement mode into the maps (eg. AUTO_ACKNOWLEDGE). When session clean is called, the JmsConnectionPool tries to remove the session from the pool, but uses Session.getAcknowledgement to find out what type of session it is. This returns SESSION_TRANSACTED mode, but session was registered under eg. AUTO_ACKNOWLEDGE mode. The pool is not cleaned up correctly and overflows. -- 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, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-2483) JBM HeuristicMixedException may destabilise the resource used during transactional contexts

by Kevin Conner (JIRA)

JBM HeuristicMixedException may destabilise the resource used during transactional contexts ------------------------------------------------------------------------------------------- Key: JBESB-2483 URL: https://jira.jboss.org/jira/browse/JBESB-2483 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.6 JBoss Messaging sometimes causes a HeuristicMixedException to be raised by the transaction manager during commit. Once this happens the associated session would appear to be destabilised in that subsequent use does not appear possible The log files contain the following output. On the client side 2009-03-03 07:17:13,137 118839811 ERROR [org.hibernate.transaction.JTATransaction] (JbpmJobExector:<ip addr>:12:) JTA commit failed javax.transaction.HeuristicMixedException at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1414) at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:135) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:87) at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.commit(ServerVMClientUserTransaction.java:140) at org.hibernate.transaction.JTATransaction.commit(JTATransaction.java:146) at org.jbpm.persistence.db.DbPersistenceService.commit(DbPersistenceService.java:295) at org.jbpm.persistence.db.DbPersistenceService.close(DbPersistenceService.java:253 This exception is sometimes, although not always, paired up with the following exception on the server side. 2009-03-03 07:29:32,752 119400749 ERROR [org.jboss.messaging.util.ExceptionUtil] (WorkerThread#7[<ip addr>:35552]:) ConnectionEndpoint[2gw-biv0otrf-1-png68srf-w3rpob-v2p1hs4] sendTransaction [4bz-4vj97urf-1-png68srf-w3rpob-v2p1hs4] javax.jms.IllegalStateException: Cannot find session with id i2y-gk8bttrf-1-png68srf-w3rpob-v2p1hs4 at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.processTransaction(ServerConnectionEndpoint.java:835) at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendTransaction(ServerConnectionEndpoint.java:497) at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.org$jboss$jms$server$endpoint$advised$ConnectionAdvised$sendTransaction$aop(ConnectionAdvised.java:101) at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N3268650789275322226.invokeNext(ConnectionAdvised$sendTransaction_N3268650789275322226.java) at org.jboss.jms.server.container.SecurityAspect.handleSendTransaction(SecurityAspect.java:195) at sun.reflect.GeneratedMethodAccessor231.invoke(Unknown Source) The exceptions are always generated with the same session id which would suggest that there is an underlying issue in the JBoss Messaging codebase. We need to handle this until the issue is resolved within JBM. -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2480) Client and server side JBM information can become out of sync

by Kevin Conner (JIRA)

Client and server side JBM information can become out of sync ------------------------------------------------------------- Key: JBESB-2480 URL: https://jira.jboss.org/jira/browse/JBESB-2480 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.6 The issue appears to be occurring with the connection information and has been seen with a co-located (client and server in same VM) deployment. This may be indicative of a race condition, with the server side (even though co-located) deciding to close the connection at the same time as we access it. The result of this is the following Caused by: java.lang.IllegalStateException: Cannot find object in dispatcher with id jr51-zktjeurf-1-wxm28srf-0fpqee-t2p1hs4 at org.jboss.jms.wireformat.ConnectionCreateSessionDelegateRequest.serverInvoke(ConnectionCreateSessionDelegateRequest.java:84) at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:866) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:608) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:420) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:173) We should check for this during session creation and, if found, attempt to cleanup and re-establish the connection. -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2097) ServiceInvoker Exception details

by Burr Sutter (JIRA)

ServiceInvoker Exception details -------------------------------- Key: JBESB-2097 URL: https://jira.jboss.org/jira/browse/JBESB-2097 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Burr Sutter Current the ServiceInvoker.deliverSync() method might throw the following exceptions: MessageDeliverException RegistryException FaultMessageException requestMessage = MessageFactory.getInstance().getMessage(); requestMessage.getProperties().setProperty(Environment.EXCEPTION_ON_DELIVERY_FAILURE,"true"); ServiceInvoker invoker = new ServiceInvoker("MyCategory", "Service99"); replyMessage = invoker.deliverSync(requestMessage,2000); A service name which does not exist results in a MessageDeliverException, with the following information exposed via a System.err.println(mde); 11:25:16,179 ERROR [STDERR] org.jboss.soa.esb.listeners.message.MessageDeliverEx ception: Failed to deliver message [header: [ ]] to Service [MyCategory:Servic e99]. Check for errors. It would have made more sense for it to be a RegistryException and the actual message doesn't indicate that there is a lookup problem. Futhermore, a timeout results in the following MessageDeliverException: 11:45:06,278 ERROR [STDERR] org.jboss.soa.esb.listeners.message.MessageDeliverEx ception: Failed to deliver message [header: [ To: InVMEpr [ PortReference < <wsa :Address invm://52455354456173794553425365727669636531/false?false#10000/>, <wsa :ReferenceProperties jbossesb:passByValue : false/>, <wsa:ReferenceProperties jb ossesb:type : urn:jboss/esb/epr/type/invm/> > ] ReplyTo: InVMEpr [ PortReference < <wsa:Address invm://thread-559/>, <wsa:ReferenceProperties jbossesb:passByVal ue : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/in vm/> > ] ]] to Service [MyCategory:Service1]. Told not to retry. No indication that the problem is timeout and the "Told not to retry" is a bit terse. -- 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, 10 months

4
11
0 / 0

[JBoss JIRA] Created: (JBESB-2328) JBossWS getPort not thread safe

by Kevin Conner (JIRA)

JBossWS getPort not thread safe ------------------------------- Key: JBESB-2328 URL: https://jira.jboss.org/jira/browse/JBESB-2328 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP2, 4.5 This has been seen on the SOA 4.3 GA release when concurrent access are being made to getPort. Caused by: java.util.ConcurrentModificationException at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:449) at java.util.AbstractList$Itr.next(AbstractList.java:420) at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitializeOperations(EndpointMetaData.java:538) at org.jboss.ws.metadata.umdm.EndpointMetaData.initializeInternal(EndpointMetaData.java:525) at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitialize(EndpointMetaData.java:513) at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(JAXWSClientMetaDataBuilder.java:308) at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPortInternal(ServiceDelegateImpl.java:262) at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:193) at javax.xml.ws.Service.getPort(Service.java:116) I reproduced this by updating the Wise-core.jar and jbossesb-soap.jar to the ESB 4.4CP2 versions and modified the webservice_consumer_wise quickstart to send 20 concurrent messages. -- 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, 10 months

1
8
0 / 0

[JBoss JIRA] Created: (JBESB-2245) Investigate support for AS 5

by Kevin Conner (JIRA)

Investigate support for AS 5 ---------------------------- Key: JBESB-2245 URL: https://jira.jboss.org/jira/browse/JBESB-2245 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.4 Reporter: Kevin Conner Fix For: 4.5 We need to take a look at ESB within AS 5 to determine how this will impact the ESB. If the necessary changes are not too invasive then we should look at supporting AS5 as well as AS 4. The focus of the ESB 4.x stream is still the AS 4.x releases. -- 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, 10 months

2
15
0 / 0

[JBoss JIRA] Created: (JBESB-2464) MessageImpl copy() method eats exceptions

by Kevin Conner (JIRA)

MessageImpl copy() method eats exceptions ----------------------------------------- Key: JBESB-2464 URL: https://jira.jboss.org/jira/browse/JBESB-2464 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.5 Reporter: Kevin Conner Fix For: 4.6 The copy() method in *both* MessageImpl classes eats the exception on failure. The methods trap Exception and translate it into the following throw new IOException(ex.toString()); This should be something like throw new IOException("Unexpected exception during copying", ex) ; so that the original cause of the exception is not lost. -- 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, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2438) Upgrade to scout-1.0.rc3

by Tom Cunningham (JIRA)

Upgrade to scout-1.0.rc3 ------------------------ Key: JBESB-2438 URL: https://jira.jboss.org/jira/browse/JBESB-2438 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.5 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.6 We need to upgrade to scout-1.0.rc3 for 4.6. scout-1.0.rc3 should be released soon. -- 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, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-2210) ESB service clustering info not in admin guide

by Darrin Mison (JIRA)

ESB service clustering info not in admin guide ---------------------------------------------- Key: JBESB-2210 URL: https://jira.jboss.org/jira/browse/JBESB-2210 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Reporter: Darrin Mison The 4.2 SOA Platform admin guide has a small section at the start on ESB Service Clustering scenarios. This content isn't in the ESB admin guide that was used as the source for the 4.3 admin guide (http://anonsvn.jboss.org/repos/labs/labs/jbossesb/branches/JBESB_4_4_GA_C...) . Was this content added to the SOA guide, or has it been removed from ESB guide ? -- 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
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues March 2009