[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
14 years, 10 months
[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
14 years, 10 months
[JBoss JIRA] Created: (JBESB-2106) JBR listener doesn't return error to a client
by Martin Vecera (JIRA)
JBR listener doesn't return error to a client
---------------------------------------------
Key: JBESB-2106
URL: https://jira.jboss.org/jira/browse/JBESB-2106
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.4
Reporter: Martin Vecera
When I'm using JBR listener in synchronous way, I'm not able to find out whether the message was successfully delivered.
JBossRemotingGatewayListener, method invoke(), line 345:
Object response = messageDeliveryAdapter.deliverSync(invocationRequest, 20000);
When an exception is thrown (e.g. SecurityServiceException), the client is never informed of this problem. As a response it simply gets null. I'd expect for the client to get the exception.
--
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
14 years, 11 months
[JBoss JIRA] Created: (JBESB-1965) Poor Exception Message "doesn't define a Message-Aware Listener"
by Burr Sutter (JIRA)
Poor Exception Message "doesn't define a Message-Aware Listener"
----------------------------------------------------------------
Key: JBESB-1965
URL: https://jira.jboss.org/jira/browse/JBESB-1965
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.4
Reporter: Burr Sutter
Priority: Minor
This message should also indicate that an InVM listener can also be used by adding invmScope="GLOBAL" to the service declaration.
12:31:43,355 WARN [ServiceController] Problem starting service jboss.esb:deploy
ment=Quickstart_helloworld_http.esb
java.lang.RuntimeException: org.jboss.soa.esb.ConfigurationException: Service co
nfiguration for Service 'HelloWorld:HelloWorld_HTTP' doesn't define a Message-Aw
are Listener (i.e. is-gateway='false').
at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration
.java:138)
at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment.startService(J
Boss4ESBDeployment.java:99)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
--
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
14 years, 11 months
[JBoss JIRA] Created: (JBESB-1774) Messages are returned to client from the wrong service
by Mika Leino (JIRA)
Messages are returned to client from the wrong service
------------------------------------------------------
Key: JBESB-1774
URL: http://jira.jboss.com/jira/browse/JBESB-1774
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Process flow
Affects Versions: 4.2.1 CP1
Environment: Windows Server 2003
Reporter: Mika Leino
Attachments: service_A_jboss-esb.xml, service_B_jboss-esb.xml
We have a setup in which a client calls an ESB service (service A) with a webservice interface and this service then calls on another ESB service (service B). Both of the services have their action pipelines set to be "RequestResponse".
For some reason the first attempt to handle the client's message always fails as the message is returned to the client from service B. As the message never returns to service A it assumes an unresponsive EPR and resends the message which on the second attempt returns to service A.
The first attempt looks like this:
client -> service A -> service B -> client
And the second like this:
(client ->) service A -> service B -> service A -> client
Unfortunately the client interpreters the first response as the one it is waiting for and fails as service A has not made the necessary changes to the message. The second attempt produces a valid response but the client is no longer listening for it.
--
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
[JBoss JIRA] Created: (JBESB-1961) [esb/jbpm exception handling] message ends up in endless loop
by Joakim Sandström (JIRA)
[esb/jbpm exception handling] message ends up in endless loop
-------------------------------------------------------------
Key: JBESB-1961
URL: https://jira.jboss.org/jira/browse/JBESB-1961
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Process flow
Affects Versions: 4.4
Reporter: Joakim Sandström
We have configured the exception handling according to 'Scenario 2. Exception Transition' in
http://www.jboss.org/jbossesb/docs/4.3.GA/manuals/html/services/jBPMInteg...
If in ServiceInvoker we're sending a message with exception/fault, we get back the same message containing the fault/exception and this causes yet another exception..
from ServiceInvoker.post:
replyMessage = eprInvoker.attemptDelivery(message, epr);
if (replyMessage != null) {
if (Type.isFaultMessage(replyMessage)) {
Factory.createExceptionFromFault(replyMessage) ;
}
// We've delivered it, we're done!
return replyMessage;
replyMessage is the same as message (which contains the fault), this causes the message to get delivered over and over again.
Example stacktrace, 'WSException: Target endpoint address not set' is thrown in order to simulate backend system failure:
16:05:50,258 WARN [ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline: header: [ To: JMSEpr [ PortReference < <wsa:Address jms://localhost:1099/queue/submit_activate_Request_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ReplyTo: EPR: PortReference < <wsa:Address logical:JBossESB-Internal#JBpmCallbackService/>, <wsa:ReferenceProperties jbossesb:esbToBpmVars : <esbToBpmVars><mapping esb="BODY_CONTENT" bpm="theBody"/><mapping esb="activation_result" bpm="activation_result"/><mapping esb="address" bpm="address"/><mapping esb="product" bpm="product"/><mapping esb="customer" bpm="customer"/><mapping esb="myid" bpm="myid"/></esbToBpmVars>/>, <wsa:ReferenceProperties jbossesb:jbpmTokenId : 1/>, <wsa:ReferenceProperties jbossesb:jbpmNodeId : 4/>, <wsa:ReferenceProperties jbossesb:jbpmProcessInstId : 1/>, <wsa:ReferenceProperties jbossesb:jbpmProcessNodeVersionCounter4_1 : 0/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/logical/> > FaultTo: EPR: PortReference < <wsa:Address logical:JBossESB-Internal#JBpmCallbackService/>, <wsa:ReferenceProperties jbossesb:esbToBpmVars : <esbToBpmVars><mapping esb="BODY_CONTENT" bpm="theBody"/><mapping esb="activation_result" bpm="activation_result"/><mapping esb="address" bpm="address"/><mapping esb="product" bpm="product"/><mapping esb="customer" bpm="customer"/><mapping esb="myid" bpm="myid"/></esbToBpmVars>/>, <wsa:ReferenceProperties jbossesb:jbpmTokenId : 1/>, <wsa:ReferenceProperties jbossesb:jbpmNodeId : 4/>, <wsa:ReferenceProperties jbossesb:jbpmProcessInstId : 1/>, <wsa:ReferenceProperties jbossesb:jbpmProcessNodeVersionCounter4_1 : 0/>, <wsa:ReferenceProperties jbossesb:jbpmTransitionName : exception/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/logical/> > MessageID: 7f9a4be3-6647-41b6-ad0f-cc2edfc389af RelatesTo: jms:correlationID#7f9a4be3-6647-41b6-ad0f-cc2edfc389af ]
javax.xml.ws.WebServiceException: org.jboss.ws.WSException: Target endpoint address not set
at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:317)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:255)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
at $Proxy108.createSubscription(Unknown Source)
at x.y.z.service.order.na.activatezxc.createzxcSubscription(activatezxc.java:61)
at x.y.z.service.order.TuotteenAktivointi.activateProduct(TuotteenAktivointi.java:94)
at x.y.z.service.order.TuotteenAktivointi.process(TuotteenAktivointi.java:61)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102)
at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316)
at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530)
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)
Caused by: org.jboss.ws.WSException: Target endpoint address not set
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:329)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:243)
... 17 more
16:06:02,222 ERROR [ActionProcessingPipeline] Failed to send fault to address EPR: PortReference < <wsa:Address logical:JBossESB-Internal#JBpmCallbackService/>, <wsa:ReferenceProperties jbossesb:esbToBpmVars : <esbToBpmVars><mapping esb="BODY_CONTENT" bpm="theBody"/><mapping esb="activation_result" bpm="activation_result"/><mapping esb="address" bpm="address"/><mapping esb="product" bpm="product"/><mapping esb="customer" bpm="customer"/><mapping esb="myid" bpm="myid"/></esbToBpmVars>/>, <wsa:ReferenceProperties jbossesb:jbpmTokenId : 1/>, <wsa:ReferenceProperties jbossesb:jbpmNodeId : 4/>, <wsa:ReferenceProperties jbossesb:jbpmProcessInstId : 1/>, <wsa:ReferenceProperties jbossesb:jbpmProcessNodeVersionCounter4_1 : 0/>, <wsa:ReferenceProperties jbossesb:jbpmTransitionName : exception/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/logical/> > for message header: [ To: EPR: PortReference < <wsa:Address logical:JBossESB-Internal#JBpmCallbackService/>, <wsa:ReferenceProperties jbossesb:esbToBpmVars : <esbToBpmVars><mapping esb="BODY_CONTENT" bpm="theBody"/><mapping esb="activation_result" bpm="activation_result"/><mapping esb="address" bpm="address"/><mapping esb="product" bpm="product"/><mapping esb="customer" bpm="customer"/><mapping esb="myid" bpm="myid"/></esbToBpmVars>/>, <wsa:ReferenceProperties jbossesb:jbpmTokenId : 1/>, <wsa:ReferenceProperties jbossesb:jbpmNodeId : 4/>, <wsa:ReferenceProperties jbossesb:jbpmProcessInstId : 1/>, <wsa:ReferenceProperties jbossesb:jbpmProcessNodeVersionCounter4_1 : 0/>, <wsa:ReferenceProperties jbossesb:jbpmTransitionName : exception/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/logical/> > From: JMSEpr [ PortReference < <wsa:Address jms://localhost:1099/queue/submit_activate_Request_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] RelatesTo: 7f9a4be3-6647-41b6-ad0f-cc2edfc389af ]
org.jboss.soa.esb.listeners.message.MessageDeliverException: Unexpected FaultMessageException during message delivery.
at org.jboss.soa.esb.client.ServiceInvoker.deliverAsync(ServiceInvoker.java:246)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.messageTo(ActionProcessingPipeline.java:511)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.faultTo(ActionProcessingPipeline.java:471)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:352)
at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530)
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)
Caused by: org.jboss.soa.esb.couriers.FaultMessageException: javax.xml.ws.WebServiceException: org.jboss.ws.WSException: Target endpoint address not set
at org.jboss.soa.esb.listeners.message.errors.Factory.createExceptionFromFault(Factory.java:49)
at org.jboss.soa.esb.client.ServiceInvoker.post(ServiceInvoker.java:321)
at org.jboss.soa.esb.client.ServiceInvoker.deliverAsync(ServiceInvoker.java:227)
... 7 more
Caused by: javax.xml.ws.WebServiceException: org.jboss.ws.WSException: Target endpoint address not set
at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:317)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:255)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
at $Proxy108.createSubscription(Unknown Source)
at x.y.z.service.order.na.activatezxc.createzxcSubscription(activatezxc.java:61)
at x.y.z.service.order.TuotteenAktivointi.activateProduct(TuotteenAktivointi.java:94)
at x.y.z.service.order.TuotteenAktivointi.process(TuotteenAktivointi.java:61)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102)
at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316)
... 4 more
Caused by: org.jboss.ws.WSException: Target endpoint address not set
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:329)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:243)
... 17 more
..
..
16:09:05,637 WARN [ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline: header: [ To: JMSEpr [ PortReference < <wsa:Address jms://localhost:1099/queue/submit_activate_Request_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ReplyTo: EPR: PortReference < <wsa:Address logical:JBossESB-Internal#JBpmCallbackService/>, <wsa:ReferenceProperties jbossesb:esbToBpmVars : <esbToBpmVars><mapping esb="BODY_CONTENT" bpm="theBody"/><mapping esb="activation_result" bpm="activation_result"/><mapping esb="address" bpm="address"/><mapping esb="product" bpm="product"/><mapping esb="customer" bpm="customer"/><mapping esb="myid" bpm="myid"/></esbToBpmVars>/>, <wsa:ReferenceProperties jbossesb:jbpmTokenId : 2/>, <wsa:ReferenceProperties jbossesb:jbpmNodeId : 4/>, <wsa:ReferenceProperties jbossesb:jbpmProcessInstId : 2/>, <wsa:ReferenceProperties jbossesb:jbpmProcessNodeVersionCounter4_2 : 0/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/logical/> > FaultTo: EPR: PortReference < <wsa:Address logical:JBossESB-Internal#JBpmCallbackService/>, <wsa:ReferenceProperties jbossesb:esbToBpmVars : <esbToBpmVars><mapping esb="BODY_CONTENT" bpm="theBody"/><mapping esb="activation_result" bpm="activation_result"/><mapping esb="address" bpm="address"/><mapping esb="product" bpm="product"/><mapping esb="customer" bpm="customer"/><mapping esb="myid" bpm="myid"/></esbToBpmVars>/>, <wsa:ReferenceProperties jbossesb:jbpmTokenId : 2/>, <wsa:ReferenceProperties jbossesb:jbpmNodeId : 4/>, <wsa:ReferenceProperties jbossesb:jbpmProcessInstId : 2/>, <wsa:ReferenceProperties jbossesb:jbpmProcessNodeVersionCounter4_2 : 0/>, <wsa:ReferenceProperties jbossesb:jbpmTransitionName : exception/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/logical/> > MessageID: efcbd07a-5884-47cd-8430-87054e162a7f RelatesTo: jms:correlationID#efcbd07a-5884-47cd-8430-87054e162a7f ]
javax.xml.ws.WebServiceException: org.jboss.ws.WSException: Target endpoint address not set
at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:317)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:255)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
at $Proxy108.createSubscription(Unknown Source)
at x.y.z.service.order.na.activatezxc.createzxcSubscription(activatezxc.java:61)
at x.y.z.service.order.TuotteenAktivointi.activateProduct(TuotteenAktivointi.java:94)
at x.y.z.service.order.TuotteenAktivointi.process(TuotteenAktivointi.java:61)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102)
at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316)
at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530)
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)
Caused by: org.jboss.ws.WSException: Target endpoint address not set
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:329)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:243)
... 17 more
16:09:06,804 ERROR [ActionProcessingPipeline] Failed to send fault to address EPR: PortReference < <wsa:Address logical:JBossESB-Internal#JBpmCallbackService/>, <wsa:ReferenceProperties jbossesb:esbToBpmVars : <esbToBpmVars><mapping esb="BODY_CONTENT" bpm="theBody"/><mapping esb="activation_result" bpm="activation_result"/><mapping esb="address" bpm="address"/><mapping esb="product" bpm="product"/><mapping esb="customer" bpm="customer"/><mapping esb="myid" bpm="myid"/></esbToBpmVars>/>, <wsa:ReferenceProperties jbossesb:jbpmTokenId : 2/>, <wsa:ReferenceProperties jbossesb:jbpmNodeId : 4/>, <wsa:ReferenceProperties jbossesb:jbpmProcessInstId : 2/>, <wsa:ReferenceProperties jbossesb:jbpmProcessNodeVersionCounter4_2 : 0/>, <wsa:ReferenceProperties jbossesb:jbpmTransitionName : exception/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/logical/> > for message header: [ To: EPR: PortReference < <wsa:Address logical:JBossESB-Internal#JBpmCallbackService/>, <wsa:ReferenceProperties jbossesb:esbToBpmVars : <esbToBpmVars><mapping esb="BODY_CONTENT" bpm="theBody"/><mapping esb="activation_result" bpm="activation_result"/><mapping esb="address" bpm="address"/><mapping esb="product" bpm="product"/><mapping esb="customer" bpm="customer"/><mapping esb="myid" bpm="myid"/></esbToBpmVars>/>, <wsa:ReferenceProperties jbossesb:jbpmTokenId : 2/>, <wsa:ReferenceProperties jbossesb:jbpmNodeId : 4/>, <wsa:ReferenceProperties jbossesb:jbpmProcessInstId : 2/>, <wsa:ReferenceProperties jbossesb:jbpmProcessNodeVersionCounter4_2 : 0/>, <wsa:ReferenceProperties jbossesb:jbpmTransitionName : exception/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/logical/> > From: JMSEpr [ PortReference < <wsa:Address jms://localhost:1099/queue/submit_activate_Request_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] RelatesTo: efcbd07a-5884-47cd-8430-87054e162a7f ]
org.jboss.soa.esb.listeners.message.MessageDeliverException: Unexpected FaultMessageException during message delivery.
at org.jboss.soa.esb.client.ServiceInvoker.deliverAsync(ServiceInvoker.java:246)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.messageTo(ActionProcessingPipeline.java:511)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.faultTo(ActionProcessingPipeline.java:471)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:352)
at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530)
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)
Caused by: org.jboss.soa.esb.couriers.FaultMessageException: javax.xml.ws.WebServiceException: org.jboss.ws.WSException: Target endpoint address not set
at org.jboss.soa.esb.listeners.message.errors.Factory.createExceptionFromFault(Factory.java:49)
at org.jboss.soa.esb.client.ServiceInvoker.post(ServiceInvoker.java:321)
at org.jboss.soa.esb.client.ServiceInvoker.deliverAsync(ServiceInvoker.java:227)
... 7 more
Caused by: javax.xml.ws.WebServiceException: org.jboss.ws.WSException: Target endpoint address not set
at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:317)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:255)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
at $Proxy108.createSubscription(Unknown Source)
at x.y.z.service.order.na.activatezxc.createzxcSubscription(activatezxc.java:61)
at x.y.z.service.order.TuotteenAktivointi.activateProduct(TuotteenAktivointi.java:94)
at x.y.z.service.order.TuotteenAktivointi.process(TuotteenAktivointi.java:61)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102)
at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316)
... 4 more
Caused by: org.jboss.ws.WSException: Target endpoint address not set
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:329)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:243)
... 17 more
16:09:08,616 WARN [ProxyWarnLog] Narrowing proxy to class org.jbpm.graph.node.TaskNode - this operation breaks ==
--
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