March 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2449) The Get or Post request 'http://localhost:8080/jbossesb/httpgateway/serviceA' can not be passed in ESB service through HttpGateway

by Kevin Conner (JIRA)

The Get or Post request 'http://localhost:8080/jbossesb/httpgateway/serviceA' can not be passed in ESB service through HttpGateway ----------------------------------------------------------------------------------------------------------------------------------- Key: JBESB-2449 URL: https://jira.jboss.org/jira/browse/JBESB-2449 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Jim Ma Assignee: Tom Fennelly Fix For: 4.4 FP1 When context value of <http-bus> is configured to "/jbossesb/httpgateway/serviceA" ,the HttpGatewayListener will use name "jbossesb/httpgateway/serviceA" to create web context and use "/" to create servlet mapping . The Get or Post request for "http://localhost:8080/jbossesb/httpgateway/serviceA" can not be passed in HttpDistpatchServlet. I think we can use "jbossesb/httpgateway" to create web context and use "/serviceA/*" to create servlet mapping , then all the following requests can be passed in ESB service. http://localhost:8080/jbossesb/httpgateway/serviceA/1234 http://localhost:8080/jbossesb/httpgateway/serviceA/5678 http://localhost:8080/jbossesb/httpgateway/serviceA?a=b http://localhost:8080/jbossesb/httpgateway/serviceA/ -- 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
3
0 / 0

[JBoss JIRA] Created: (JBESB-2436) Add test for new HttpGateway classes

by Daniel Bevenius (JIRA)

Add test for new HttpGateway classes ------------------------------------ Key: JBESB-2436 URL: https://jira.jboss.org/jira/browse/JBESB-2436 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta, Testing, Transports Reporter: Daniel Bevenius Fix For: 4.6 -- 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

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-2434) mep="OneWay" on a published webservice results in a zero-length wsdl returned by <web service URL>?wsdl

by Len DiMaggio (JIRA)

mep="OneWay" on a published webservice results in a zero-length wsdl returned by <web service URL>?wsdl -------------------------------------------------------------------------------------------------------- Key: JBESB-2434 URL: https://jira.jboss.org/jira/browse/JBESB-2434 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.4 CP2 Reporter: Len DiMaggio Project issue for SOA-P platform issue SOA-1186 -- 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

3
5
0 / 0

[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, 9 months

2
9
0 / 0

[JBoss JIRA] Created: (JBESB-2395) add ingres db support to message-store db configurations

by murray armfield (JIRA)

add ingres db support to message-store db configurations -------------------------------------------------------- Key: JBESB-2395 URL: https://jira.jboss.org/jira/browse/JBESB-2395 Project: JBoss ESB Issue Type: Patch Security Level: Public (Everyone can see) Components: Message Store Affects Versions: 4.5, 4.6 Environment: N/A Reporter: murray armfield Priority: Minor Simple patch to add ingres sql files for using ingres as a message store. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBESB-2211) Sort out logging for OSGi deployment

by Tom Fennelly (JIRA)

Sort out logging for OSGi deployment ------------------------------------ Key: JBESB-2211 URL: https://jira.jboss.org/jira/browse/JBESB-2211 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Reporter: Tom Fennelly Fix For: 5.0 initial development We currently have log4j configs in places where they shouldn't be. There's an OSGi LogService. Not sure how we can log4j into this without polluting code with OSGi code. There should be a way. Maybe there's an OSGi LogService log4j appender , or something like that. -- 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

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-1710) Documentation of Standalone mode in Quickstarts is confusing

by Tom Cunningham (JIRA)

Documentation of Standalone mode in Quickstarts is confusing ------------------------------------------------------------ Key: JBESB-1710 URL: http://jira.jboss.com/jira/browse/JBESB-1710 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation, Examples Affects Versions: 4.2.1 CP2 Reporter: Tom Cunningham In the readme.txt of every QuickStart, we document how to run in standalone mode. Do we really want to do this? Standalone mode seems like an edge case that we support, and listing it in every QS readme.txt is confusing to first time users (see forum post reference). Maybe we should have a standalone guide that describes how to run QS's in standalone mode, and focus the QS readmes on the most common method of running the QS's (running in ESB server or JBossAS+ESB). -- 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, 10 months

6
7
0 / 0

[JBoss JIRA] Created: (JBESB-1699) Update Chapter 9 of the Programmers Guide ("Configuration")

by Tom Fennelly (JIRA)

Update Chapter 9 of the Programmers Guide ("Configuration") ----------------------------------------------------------- Key: JBESB-1699 URL: http://jira.jboss.com/jira/browse/JBESB-1699 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 CP2 Reporter: Tom Fennelly The Config Model diagram is out of date. -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2147) Managing gateway listeners from JON

by Jaroslaw Kijanowski (JIRA)

Managing gateway listeners from JON ----------------------------------- Key: JBESB-2147 URL: https://jira.jboss.org/jira/browse/JBESB-2147 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.4 CP1 Reporter: Jaroslaw Kijanowski Assignee: Tom Cunningham Starting/Stopping the MessageAwareListener is possible, but if you want to start/stop a gateway listener, you need to do it via the jmx-console. Currently gateway listeners are not available in the JON GUI. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBESB-2117) Documentation on jbr transport configuration

by Magesh Kumar B (JIRA)

Documentation on jbr transport configuration -------------------------------------------- Key: JBESB-2117 URL: https://jira.jboss.org/jira/browse/JBESB-2117 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration, Documentation, Rosetta, Transports Reporter: Magesh Kumar B Currently there is no reference in Programmers Guide or any other related to jbr-provider, jbr-bus, jbr-listener etc., An extensive coverage of all features for this transport along with the mention that this transport is not ESB aware and cannot be used as a listener is needed. -- 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues March 2009