Ganesh,
Unfortunately, this attachment is being dropped by the mailing list.
Does this problem impact all services or only the JSR-181 services?
Does the CXF SE have the same problem too?
Regards,
Gert
navigator09 wrote:
Gert,
I have attached servicemix.log file to the post. From the log, its clear
that the service is invoked correctly and there is a response from the back
end. However servicemix is not handling this response correctly.
Regards,
Ganesh
navigator09 wrote:
only pinned services are working, clustered services throw the following
error
<vdssSCMItemResponsexmlns="http://vdssfrontend";><vdssSCMItemReturn>Could
not invoke service.. Nested exception is
org.codehaus.xfire.fault.XFireFault: Current state not START_ELEME
NT, END_ELEMENT or
ENTITY_REFERENCE</vdssSCMItemReturn></vdssSCMItemResponse>
Regards,
Ganesh
Gert Vanthienen wrote:
Ganesh,
What version of servicemix are you using? Could you try enabling DEBUG
logging on both nodes to check that this isn't an issue that is caused
by http://servicemix.apache.org/javaioioexception-stream-closed.html?
Regards,
Gert
navigator09 wrote:
Hi,
In another scenario, I have two servicemix instances in the same
machine
connected using a multicast discovery. Each instance has the same jsr181
service exposed. when I send an input message to the cluster, it gets
load
balanced in round robin fashion. But all requests fail with the same
error
given below
Could not invoke service.. Nested exception is
org.codehaus.xfire.fault.XFireFault: Current state not START_ELEMENT,
END_ELEMENT or ENTITY_REFERENCE
when I kill any one instance of the two in the cluster, the single
instance works fine.I have verified that the back end webservices are
called
correctly.
Pls let me know how to solve the problem.
Regards,
Ganesh
navigator09 wrote:
Hi,
I have successfully enabled clustering in servicemix using multicast
discovery mechanism. However its not working consistantly. The
following
are the problems that I face
I have a routing slip service in "instance A" and jsr181 service in
"Instance B". The routing slip service calls the jsr 181 service
correctly for sometime then it fails. After a break when messsages are
sent again works the similar way and so on.
The logs on instance A
java.lang.IllegalStateException: Endpoint not found:
{http://vdssfrontend}Vdssfrontend:VDSS at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:482)
at
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLife
Cycle.java:46)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:610)
at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:170)
at
org.apache.servicemix.jbi.nmr.flow.jms.AbstractJMSFlow.access$201(AbstractJMSFlow.java:63)
at
org.apache.servicemix.jbi.nmr.flow.jms.AbstractJMSFlow$4.run(AbstractJMSFlow.java:521)
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)
ERROR - Jsr181Component - Error setting exchange status
to
ERROR
javax.jbi.messaging.MessagingException: illegal call to send / sendSync
at
org.apache.servicemix.jbi.messaging.MessageExchangeImpl.handleSend(MessageExchangeImpl.java:614)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.doSend(DeliveryChannelImpl.java:385)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.send(DeliveryChannelImpl.java:431)
at
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:58)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:610)
at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:170)
at
org.apache.servicemix.jbi.nmr.flow.jms.AbstractJMSFlow.access$201(AbstractJMSFlow.java:63)
at
org.apache.servicemix.jbi.nmr.flow.jms.AbstractJMSFlow$4.run(AbstractJMSFlow.java:521)
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)
logs on instance B
Processing SCMItem
Completed SCMItem
Processing SCMItem
Completed SCMItem
Processing SCMItem
Completed SCMItem
Processing SCMItem
Completed SCMItem
Processing SCMItem
Completed SCMItem
ERROR - JMSFlow - Caught an exception routing
ExchangePac
ket:
javax.jbi.messaging.MessagingException: Component servicemix-eip is
shut
down
at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlo
w.java:177)
at
org.apache.servicemix.jbi.nmr.flow.jms.AbstractJMSFlow.access$201(Abs
tractJMSFlow.java:63)
at
org.apache.servicemix.jbi.nmr.flow.jms.AbstractJMSFlow$4.run(Abstract
JMSFlow.java:521)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:885)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:907)
at java.lang.Thread.run(Thread.java:619)
why is this happening and how do I correct it?
Regards,
Ganesh
-----
---
Gert Vanthienen
http://www.anova.be
http://www.nabble.com/file/p18887172/servicemix.log servicemix.log
