September 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3478) Handle websphere broken connections

by Kevin Conner (JIRA)

Handle websphere broken connections ----------------------------------- Key: JBESB-3478 URL: https://jira.jboss.org/browse/JBESB-3478 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 CP4 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP5 We currently handle the detection of connection failures for JBoss Messaging by examining the exceptions thrown by the JMS operations, we need to extend this to include Websphere MQ The only known error, at this stage, is a JMSException with error code "MQJE001: Completion Code 2, Reason 2009" and a linked exception with message "MQJMS2008". This should be configurable so that we have an opportunity to augment this if necessary. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-3441) Add activation mapper for hornetq-ra.rar

by Kevin Conner (JIRA)

Add activation mapper for hornetq-ra.rar ---------------------------------------- Key: JBESB-3441 URL: https://jira.jboss.org/browse/JBESB-3441 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.9 Reporter: Kevin Conner Fix For: 4.9 CP1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-3479) juddi webservice wsdl needs to correct service names

by Kevin Conner (JIRA)

juddi webservice wsdl needs to correct service names ---------------------------------------------------- Key: JBESB-3479 URL: https://jira.jboss.org/browse/JBESB-3479 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.9 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.9 CP1 The juddi webservices, provided by ESB on behalf of the platform, need to have their service names corrected. The previous platforms ignored the service names but now they are required to match the annotations. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3480) webservice_producer quickstart deploys war multiple times

by Kevin Conner (JIRA)

webservice_producer quickstart deploys war multiple times --------------------------------------------------------- Key: JBESB-3480 URL: https://jira.jboss.org/browse/JBESB-3480 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.9 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.9 CP1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3009) GettingStarted.odt -> Maven/JDocbook project contribution

by Darrin Mison (JIRA)

GettingStarted.odt -> Maven/JDocbook project contribution --------------------------------------------------------- Key: JBESB-3009 URL: https://jira.jboss.org/jira/browse/JBESB-3009 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Darrin Mison Attachments: Getting_Started_Guide.zip This is a conversion of existing content of the trunk GettingStarted.odt to docbook XML with a Maven pom.xml to build it. source: https://svn.jboss.org/repos/labs/labs/jbossesb/trunk/product/docs/Getting... Revision 30054 Let me know your thoughts and I can continue on with the other documents. Note that the content is word for word, only a few obvious spelling mistakes were corrected. The Author list is based on the SVN log for the file The Legal Notice is a slightly massaged version from the .odt and would need to be verified. The file layout is also compatible with Publican for easy integration into SOA Platform documentation. -- 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

13 years, 7 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-3420) SOAPProcessor picks up wrong WSDL when two WS Endpoints with the same name are deployed via different deployments

by Magesh Kumar B (JIRA)

SOAPProcessor picks up wrong WSDL when two WS Endpoints with the same name are deployed via different deployments ----------------------------------------------------------------------------------------------------------------- Key: JBESB-3420 URL: https://jira.jboss.org/browse/JBESB-3420 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Reporter: Magesh Kumar B Fix For: 4.9 CP1 JBossWS creates deployments with the format jboss.ws:context=foo,endpoint=fooservice If two deployments are deployed like this jboss.ws:context=foo1,endpoint=fooservice jboss.ws:context=foo2,endpoint=fooservice Then the following <property name="jbossws-endpoint" value="fooservice"/> will find any one of the deployment above that may not be what we intended. The property should be changed to use the deployment name rather than just the endpoint's shortname to avoid picking up the wrong WSDL <property name="jbossws-endpoint" value="jboss.ws:context=foo1,endpoint=fooservice"/> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-880) The ESB is blocked under heavy load when using JMS

by Jiri Pechanec (JIRA)

The ESB is blocked under heavy load when using JMS -------------------------------------------------- Key: JBESB-880 URL: http://jira.jboss.com/jira/browse/JBESB-880 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2 Milestone Release 3 Environment: RHEL 5, PostgreSQL Reporter: Jiri Pechanec Assigned To: Mark Little Priority: Blocker When the ESB is forced to process a huge batch of messages then it blocks completely. The ESB configuration was just one service with one listener and gateway. Both gateway and listener are using JMS. The testing was executed twice using one and then four threads per listener and gateway. The service contains two actions that serves only for message counting. If you try to send 10000 messages sized around 20 KB it will probaly block after few minutes of processing. The ESB do not respond to TERM signal and even JMX console is not available. The only solution is to kill process violently. With the smaller messages the block does not happend or happends after bigger amount of messages. The sender is generating following log messages [Timer-1][BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask@201d592a: detected failure on control connection Thread[control: Socket[addr=/10.34.34.47,port=2660,localport=51957],5,main]: requesting new control connection We can not exclude problem in JBoss Messaging itself but when we tried to use plain JMS without ESB we were able to send/receive 300000 messages without any problem. Moreover the more messages were processed the longer time it takes for the next batch to be processed. -- 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

13 years, 7 months

7
33
0 / 0

[JBoss JIRA] Created: (JBESB-3470) SOAPProcessor isn't thread-safe

by Pavel Macik (JIRA)

SOAPProcessor isn't thread-safe ------------------------------- Key: JBESB-3470 URL: https://jira.jboss.org/browse/JBESB-3470 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.9 CP1 Reporter: Pavel Macik Priority: Blocker The SOAPProcessor during message processing creates and destroys a subcontext named "env" which is fine when the ESB service is configured as single-threaded. But when the ESB service's action pipeline is configured as multi-threaded (maxThreads > 1) one of the following exceptions will occure: javax.naming.NameNotFoundException: env not bound at org.jnp.server.NamingServer.getBinding(NamingServer.java:771) at org.jnp.server.NamingServer.getBinding(NamingServer.java:779) at org.jnp.server.NamingServer.unbind(NamingServer.java:349) at org.jnp.interfaces.NamingContext.unbind(NamingContext.java:871) at org.jnp.interfaces.NamingContext.destroySubcontext(NamingContext.java:1193) at org.jnp.interfaces.NamingContext.destroySubcontext(NamingContext.java:1185) at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:231) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:649) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:603) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:433) 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) or javax.naming.NameAlreadyBoundException; remaining name 'env' at org.jnp.server.NamingServer.createSubcontext(NamingServer.java:619) at org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:1116) at org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:1096) at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:229) ... 7 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

5
27
0 / 0

[JBoss JIRA] Created: (JBESB-3476) base-build.xml for quickstarts asserts CXF WS availability by misplaced cxf-rt-core.jar

by Pavel Macik (JIRA)

base-build.xml for quickstarts asserts CXF WS availability by misplaced cxf-rt-core.jar --------------------------------------------------------------------------------------- Key: JBESB-3476 URL: https://jira.jboss.org/browse/JBESB-3476 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.9, 4.9 CP1 Reporter: Pavel Macik Priority: Critical 'ws-cxf-rt-as5' available property is checking for presence of cxf-rt-core.jar file on following path '${org.jboss.esb.server.home}/common/lib/cxf-rt-core.jar' that is a wrong location of the file. The file is actually placed in ${org.jboss.esb.server.home}/client/cxf-rt-core.jar. That causes failures during deployment of ws-related quickstarts when WS stack is switched to CXF. The value of the property should change to the right location. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-3477) http-gateway crosstalk among multiple ESBs

by Dave Siracusa (JIRA)

http-gateway crosstalk among multiple ESBs ------------------------------------------ Key: JBESB-3477 URL: https://jira.jboss.org/browse/JBESB-3477 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Application Server Affects Versions: 5.0 Environment: RHEL 64bit Reporter: Dave Siracusa Priority: Critical Attachments: http_gateway.zip, Quickstart_http_gateway.esb, Xuickstart_http_gateway.esb I have multipel ESBs eployed, I'm finding that sometime that an inappropriate ESB is being used to service an http request. The ESB projects have unique names. If I reduce the environment down to one ESB all is fine. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2010