March 2011 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3582) SOA-P 5.1.0 classloader caching issues with embedded jar artifacts

by Dave Siracusa (JIRA)

SOA-P 5.1.0 classloader caching issues with embedded jar artifacts ------------------------------------------------------------------ Key: JBESB-3582 URL: https://issues.jboss.org/browse/JBESB-3582 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 5.0 Milestone Release 1 Environment: Windows 7 Reporter: Dave Siracusa An existing .ESB file with embedded jar artifact ends up being used for subsequently deployed .ESB applications even if the second ESB contains a newer/different version of the embedded jar artifact. If you repeatly redeploy the first and the second, eventually the ESB file fails to deploy due to duplicate class issues. SOA-P 5.0.0/1/2 does not behave this way as the VFSClassloader uniquely captures each artifact in the tmp vsf folder. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

4
13
0 / 0

[JBoss JIRA] Created: (JBESB-3419) Expanding soapenc:array is not supported by SOAPClient(SoapUI)

by Jiangshan Zhang (JIRA)

Expanding soapenc:array is not supported by SOAPClient(SoapUI) -------------------------------------------------------------- Key: JBESB-3419 URL: https://jira.jboss.org/browse/JBESB-3419 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Environment: JBoss ESB 4.7 (SOA Platform 5.0) Reporter: Jiangshan Zhang The SOAPClient (SoapUI) does not seem to be able to handle web services that have arrays that are generated by Axis 1.4.(see the attached sample WSDL file). -- 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

15 years

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-3591) Add explicit classpath to the helloworld quickstart

by Daniel Bevenius (JIRA)

Add explicit classpath to the helloworld quickstart --------------------------------------------------- Key: JBESB-3591 URL: https://issues.jboss.org/browse/JBESB-3591 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Reporter: Daniel Bevenius Assignee: Daniel Bevenius Priority: Minor If we add an explicit classpath to one of the quickstarts, for example the helloworld quickstart, we could point users to this when they have issues setting up their own project classpaths. Now and again questions pop up in the user forum regarding this and even though we have documented this in the user guide that information is static and putting this in a quickstart would make the tests for that quickstart to fail when a newer version of the ESB is developed and a dependency as changed. An example of this for JBossAS 5.x could look like: {code:xml} <target name="runtest" depends="compile" description="Will send an esb Message"> <path id="serviceinvoker-classpath"> <pathelement location="${org.jboss.esb.server.deploy.dir}/jbossesb.sar/lib/jbossesb-rosetta.jar"/> <pathelement location="${org.jboss.esb.server.deploy.dir}/jbossesb.sar/lib/jbossesb-config-model-*.jar"/> <pathelement location="${org.jboss.esb.server.deploy.dir}/jbossesb.sar/lib/commons-configuration-1.5.jar"/> <pathelement location="${org.jboss.esb.server.deploy.dir}/jbossesb.sar/lib/commons-lang-2.3.jar"/> <pathelement location="${org.jboss.esb.server.deploy.dir}/jbossesb.sar/lib/commons-codec-1.3.jar"/> <pathelement location="${org.jboss.esb.server.deploy.dir}/jbossesb.sar/lib/wstx-asl-3.2.8.jar"/> <pathelement location="${org.jboss.esb.server.deploy.dir}/jbossesb.sar/lib/stax-api-1.0.1.jar"/> <pathelement location="${org.jboss.esb.server.deploy.dir}/jbossesb.sar/lib/xbean-2.2.0.jar"/> <pathelement location="${org.jboss.esb.server.deploy.dir}/jbossesb.sar/lib/scout-1.2.2.jar"/> <pathelement location="${org.jboss.esb.server.deploy.dir}/jbossesb.sar/lib/juddi-client-3.0.3.jar"/> <pathelement location="${org.jboss.esb.server.deploy.dir}/jbossesb.sar/lib/uddi-ws-3.0.3.jar"/> <pathelement location="${org.jboss.esb.server.deploy.dir}/jboss-aop-jdk50.deployer/jboss-aop-jdk50.jar"/> <pathelement location="${org.jboss.esb.server.server}/lib/jbossts-common.jar"/> <pathelement location="${org.jboss.esb.server.server}/lib/jboss-remoting.jar"/> <pathelement location="${org.jboss.esb.server.server}/lib/jboss-messaging-client.jar"/> <pathelement location="${org.jboss.esb.server.server}/lib/jboss-messaging.jar"/> <pathelement location="${org.jboss.esb.server.server}/lib/javassist.jar"/> <pathelement location="${org.jboss.esb.server.server}/lib/log4j.jar"/> <pathelement location="${org.jboss.esb.server.server}/lib/commons-logging.jar"/> <pathelement location="${org.jboss.esb.server.server}/lib/commons-collections.jar"/> <pathelement location="${org.jboss.esb.server.home}/client/jbossall-client.jar"/> <pathelement location="${org.jboss.esb.server.home}/client/trove.jar"/> <pathelement location="${org.jboss.esb.server.home}/lib/endorsed/xercesImpl.jar"/> <pathelement location="${basedir}/build/classes"/>  <pathelement location="${basedir}/."/>  <pathelement location="${basedir}/../conf/registry/"/> </path> <echo>Runs Test ESB Message Sender</echo> <java fork="yes" classname="org.jboss.soa.esb.samples.quickstart.helloworld.test.SendEsbMessage" failonerror="true"> <arg value="FirstServiceESB"/>  <arg value="SimpleListener"/>  <arg value="Hello World - Straight to ESB listener - no Gateway"/>  <classpath refid="serviceinvoker-classpath"/> </java> </target> {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-3502) Document LocalRegistryInterceptor

by Kevin Conner (JIRA)

Document LocalRegistryInterceptor --------------------------------- Key: JBESB-3502 URL: https://jira.jboss.org/browse/JBESB-3502 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.9 Reporter: Kevin Conner Assignee: Kevin Conner Priority: Minor 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

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-844) Pull together some developer docs around the lifecycle identity (on the wiki?)

by Tom Fennelly (JIRA)

Pull together some developer docs around the lifecycle identity (on the wiki?) ------------------------------------------------------------------------------ Key: JBESB-844 URL: http://jira.jboss.com/jira/browse/JBESB-844 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: Tom Fennelly Assigned To: Kevin Conner And draw a few pictures while yer at it Kev ;-) -- 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

15 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-3585) SOAPProxy needs to handle the document case where SOAPAction is not set

by Tom Cunningham (JIRA)

SOAPProxy needs to handle the document case where SOAPAction is not set ----------------------------------------------------------------------- Key: JBESB-3585 URL: https://issues.jboss.org/browse/JBESB-3585 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 CP2 Reporter: Tom Cunningham Assignee: David Ward Fix For: 4.7 CP3 SOAPProxy needs to handle the Document case (it already handles the RPC case) when the SOAPAction is not provided. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-3590) HttpRouter attachResponseDetails java.lang.IllegalArgumentException

by Jurij Kruske (JIRA)

HttpRouter attachResponseDetails java.lang.IllegalArgumentException ------------------------------------------------------------------- Key: JBESB-3590 URL: https://issues.jboss.org/browse/JBESB-3590 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.8 Reporter: Jurij Kruske in the case that the http server send back empty header value, HttpRouter crash, for example [2011-03-22 10:39:57,609][DEBUG][pool-270-thread-2][header]<< "HTTP/1.1 200 OK[\r][\n]" [2011-03-22 10:39:57,609][DEBUG][pool-270-thread-2][header]<< "Responsetype: errorResponse[\r][\n]" [2011-03-22 10:39:57,609][DEBUG][pool-270-thread-2][header]<< "Content-Length: 245[\r][\n]" [2011-03-22 10:39:57,609][DEBUG][pool-270-thread-2][header]<< "Server: Ypsilon.Net AG, XMLAPI-SERVER 4012_0[\r][\n]" [2011-03-22 10:39:57,609][DEBUG][pool-270-thread-2][header]<< "Session: [\r][\n]" [2011-03-22 10:39:57,609][DEBUG][pool-270-thread-2][header]<< "Date: Tue, 22 Mar 2011 09:39:56 GMT[\r][\n]" [2011-03-22 10:39:57,609][DEBUG][pool-270-thread-2][header]<< "User-Agent: Ypsilon satellite application[\r][\n]" [2011-03-22 10:39:57,609][DEBUG][pool-270-thread-2][header]<< "Content-Type: text/html[\r][\n]" [2011-03-22 10:39:57,609][DEBUG][pool-270-thread-2][content]<< "<?xml version="1.0" encoding="UTF-8"?>[\n]" [2011-03-22 10:39:57,609][DEBUG][pool-270-thread-2][content]<< " <?ypsilon RNGSchema="errorResponse.rnc" type="compact"?> [\n]" [2011-03-22 10:39:57,609][DEBUG][pool-270-thread-2][content]<< " <errorResponse no="86">HTTP-header: "Api-version" contains wrong version number.</errorResponse>" here is the header param "Seesion: " is empty the resutl is java.lang.IllegalArgumentException: null or empty 'value' arg in method call. at org.jboss.internal.soa.esb.assertion.AssertArgument.isNotNullAndNotEmpty(AssertArgument.java:71) at org.jboss.soa.esb.http.HttpHeader.<init>(HttpHeader.java:40) at org.jboss.soa.esb.actions.routing.http.HttpRouter.attachResponseDetails(HttpRouter.java:206) at org.jboss.soa.esb.actions.routing.http.HttpRouter.process(HttpRouter.java:136) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:634) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:588) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:419) at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:540) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-3586) org.jboss.soa.esb.actions.routing.http.HttpRouter and ActionProcessingException

by Jurij Kruske (JIRA)

org.jboss.soa.esb.actions.routing.http.HttpRouter and ActionProcessingException ------------------------------------------------------------------------------- Key: JBESB-3586 URL: https://issues.jboss.org/browse/JBESB-3586 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.9 Reporter: Jurij Kruske In the case IOException process method fired ActionProcessingException and the ActionProcessingPipeline send new Message to FaultTo. The original meaase will be lost, in FaultTo service we have no chance to send the message to ReplayTo service because the address is completely losed. Could you please change the throw ActionProcessingException to ActionProcessingFaultException? Jurij -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-3584) SOAPProxy needs to handle the document case where SOAPAction is not set

by Tom Cunningham (JIRA)

SOAPProxy needs to handle the document case where SOAPAction is not set ----------------------------------------------------------------------- Key: JBESB-3584 URL: https://issues.jboss.org/browse/JBESB-3584 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 CP2 Reporter: Tom Cunningham Assignee: David Ward Fix For: 4.7 CP3 SOAPProxy needs to handle the Document case (it already handles the RPC case) when the SOAPAction is not provided. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-2551) Configure TTL on MessageProducer sending replies on behalf of RequestResponse pipelines

by Ryan Hochstetler (JIRA)

Configure TTL on MessageProducer sending replies on behalf of RequestResponse pipelines --------------------------------------------------------------------------------------- Key: JBESB-2551 URL: https://jira.jboss.org/jira/browse/JBESB-2551 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.5 Reporter: Ryan Hochstetler When an external client sends a message via the ServiceInvoker to a RequestReponse service that takes longer than the client-configured timeout to reply, the reply message is still sent to the service's reply queue, but gets stuck, forever, since the courier that delivered the message did not configure a TTL on the MessageProducer or set the TTL on the MessageProducer's send() method. Add a property to jbossesb-properties.xml to hold the defined timout (zero for no TTL, if the original functionality is preferred.). Add hooks to the JmsCourier (and clients thereof) to set the TTL only on reply messages. The courier is unlikely to know which messages are replies, but the clients of the courier should know well enough. This brings up an interesting point, now that I think of it. In the event that the queue receiving the original message from the ServiceInvoker is backed-up, the ServiceInvoker will time-out before the original message is even picked up and inserted into a processing pipeline. It seems to me that it would be better if the message would never be processed if the client has given up on waiting for the reply. This way, we eliminate unintended consequences or mysterious behavior, where we tell the user that the request was not serviced, but in fact, the user sees evidence to the contrary in the system. Perhaps the courier used by the ServiceInvoker should also set a TTL on the request mesage. This TTL should probably be equal to the timeout passed to the deliverSync() method. Of course, this would not be guaranteed behavior, as the message could be inserted into a pipeline just prior to the TTL, but the ServiceInvoker could still timeout. The real benefit here would be that hundreds of sync messages wouldn't queue up and then be unleashed after a previously unavailable resource comes back online an hour later. -- 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

15 years, 1 month

3
10
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 2011