July 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2484) 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-2484 URL: https://jira.jboss.org/jira/browse/JBESB-2484 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, 8 months

2
9
0 / 0

[JBoss JIRA] Created: (JBESB-2627) InVM XAResource is not serializable and causes issues in recovery

by Kevin Conner (JIRA)

InVM XAResource is not serializable and causes issues in recovery ----------------------------------------------------------------- Key: JBESB-2627 URL: https://jira.jboss.org/jira/browse/JBESB-2627 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 This causes the following messages to be raised on recovery. Could not find new XAResource to use for recovering non-serializable XAResource -- 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, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2649) Create a transport for HP for co-located registry

by Tom Cunningham (JIRA)

Create a transport for HP for co-located registry ------------------------------------------------- Key: JBESB-2649 URL: https://jira.jboss.org/jira/browse/JBESB-2649 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.6 Create a transport for HP for co-located registry. -- 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, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2758) ReplyTo header is invalid after static router with InVM

by Martin Vecera (JIRA)

ReplyTo header is invalid after static router with InVM ------------------------------------------------------- Key: JBESB-2758 URL: https://jira.jboss.org/jira/browse/JBESB-2758 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 CP3 Reporter: Martin Vecera I have two services in a single ESB archive. Both have set invmScope="GLOBAL", the first service is accessible via EBWS and routes the message to the second service. The client awaits a response, which should be sent by the second service to a thread that executes EBWS servlet. Instead of this and exception is thrown. 2009-07-22 08:30:43,550 ERROR [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] Failed to send reply to address InVMEpr [ PortReference < <wsa:Address invm://thread-910-3/ >, <wsa:ReferenceProperties jbossesb:passByValue : false/> > ] for message header: [ To: InVMEpr [ PortReference < <wsa:Address invm://thread-910-3/>, <wsa:ReferenceProperties jbossesb :passByValue : false/> > ] From: InVMEpr [ PortReference < <wsa:Address invm://526f757465725465737424242424242424242424242445425753526f757465/false?false#10000/>, <wsa:ReferencePropert ies jbossesb:passByValue : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/invm/> > ] RelatesTo: b013fa7a-18ac-40ef-bac5-7ad3ef2c6c5b ] org.jboss.soa.esb.couriers.CourierException: No deliverAsync courier at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.deliver(TwoWayCourierImpl.java:170) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.messageTo(ActionProcessingPipeline.java:835) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.replyTo(ActionProcessingPipeline.java:757) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:687) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:574) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:408) at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:540) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) When an JMS queue is configured in the first service, everything works like a charm. -- 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, 9 months

2
8
0 / 0

[JBoss JIRA] Created: (JBESB-2763) WSSecurityInfoExtractor's smooks selectors are incorrect.

by Daniel Bevenius (JIRA)

WSSecurityInfoExtractor's smooks selectors are incorrect. --------------------------------------------------------- Key: JBESB-2763 URL: https://jira.jboss.org/jira/browse/JBESB-2763 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Security Affects Versions: 4.6 Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 4.7 This selectors in the bindings are incorrect and should be using absolute node names so they do not conflict with nodes with the same name but located in elements other then the header element of the SOAP message. -- 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, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2767) GettingStartedGuide: Tomcat is no longer a supported deployment target. Remove information regarding Tomcat.

by Daniel Bevenius (JIRA)

GettingStartedGuide: Tomcat is no longer a supported deployment target. Remove information regarding Tomcat. ------------------------------------------------------------------------------------------------------------ Key: JBESB-2767 URL: https://jira.jboss.org/jira/browse/JBESB-2767 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.6 Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 4.7 -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2695) Add jndi security support to EJBProcessor

by Daniel Bevenius (JIRA)

Add jndi security support to EJBProcessor ----------------------------------------- Key: JBESB-2695 URL: https://jira.jboss.org/jira/browse/JBESB-2695 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Security Reporter: Daniel Bevenius Fix For: 4.7 Currently there is no support for supplying jndi security credentials and principals which should be added. I also think that the EJBProcessor could be refactored to be simpler but I'll create a jira for that and link it to this one. -- 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, 9 months

2
11
0 / 0

[JBoss JIRA] Created: (JBESB-2759) SOAPProxy should propagate Basic Auth information to proxied web serivce

by David Ward (JIRA)

SOAPProxy should propagate Basic Auth information to proxied web serivce ------------------------------------------------------------------------ Key: JBESB-2759 URL: https://jira.jboss.org/jira/browse/JBESB-2759 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Security, Web Services Affects Versions: 4.6 Reporter: David Ward Assignee: David Ward Priority: Critical Fix For: 4.7 Currently, HttpSOAPProxyTransport has a default MappedHeaderList of "SOAPAction, Content-Type, Accept". These get pulled from the ESB Message (because they originally came in as HttpRequest headers) and propagated to the new request that gets sent to the actual external endpoint. "Authorization" should be added to this list so Basic Auth security still works. The fix should be easy, basically changing this line: setAttribute(cloned_config, "MappedHeaderList", "SOAPAction, Content-Type, Accept"); to this: setAttribute(cloned_config, "MappedHeaderList", "SOAPAction, Content-Type, Accept, Authorization"); in HttpSOAPProxyTransport.java. That way people don't need to even think about configuring it. It just gets propagated if it's already in the incoming request. -- 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, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-2761) HTTP response (status) codes should be returned through relevant gateways

by David Ward (JIRA)

HTTP response (status) codes should be returned through relevant gateways ------------------------------------------------------------------------- Key: JBESB-2761 URL: https://jira.jboss.org/jira/browse/JBESB-2761 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Web Services Affects Versions: 4.6 Reporter: David Ward Assignee: David Ward Fix For: 4.7 When the <jbr-provider/> (JBossRemotingGatewayListener using http protocol) or <http-provider/> (HttpGatewayListener) is used in a synchronous fashion, HTTP response (status) codes should be returned when there are "proxied" HTTP actions in the service's pipeline. This includes HttpRouter, SOAPClient, SOAPProcessor and SOAPProxy. This is similar to JBESB-2511, where response headers weren't always being propagated back, but now we're talking about the response (status) code. -- 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, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2765) tmp wsdl files not always cleaned up by SOAPProxyWsdlContractPublisher

by David Ward (JIRA)

tmp wsdl files not always cleaned up by SOAPProxyWsdlContractPublisher ---------------------------------------------------------------------- Key: JBESB-2765 URL: https://jira.jboss.org/jira/browse/JBESB-2765 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.6 Reporter: David Ward Assignee: David Ward Fix For: 4.7 Turns out you can't really trust file.deleteOnExit(), as several /tmp/org.jboss.soa.esb.actions.soap.proxy.SOAPProxyWsdlContractPublisher-####.wsdl files can bulid up. The fix would be to be more agreesive in deleting the tmp files in a finally block, as soon as SOAPProxy is done using it. -- 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, 9 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2009