Did you upgrade from 3.1 to 3.1.1 maybe ?
3.1.1 has been upgraded to the latest XFire version which may cause
problems
(by fixing bugs that has an impact).
Cheers,
Guillaume Nodet
On Aug 27, 2007, at 2:36 AM, Benamin wrote:
I have 2 existing ServiceMix SA's running on Solaris. THe first
one dequeues
messages from OracleAQ and sends them via Web Service to another SA
that is
the web service. THe web service sends a response back that then gets
enqueued to OracleAQ. This works fine. I move these 2 SA's over
to Linux,
and now, I am always getting a "Missing Parts" error when
attempting to send
a SOAP message. Both the Linux and Solaris installs are using
3.1.1. HEre
is the debug output:
DEBUG - tapestry - SyncDequeueService
<?xml version="1.0" encoding="UTF-8"?>
<NSRSyncRequest>
<OperationCode>Activate</OperationCode>
<SourceOrderID>s00002</SourceOrderID>
</NSRSyncRequest>
DEBUG - MyComponent - Created correlation id:
ID:162.70.8.49-114993b5139-3:3
DEBUG - DefaultEndpoint - Received message to null
DEBUG - HandlerPipeline - adding handler
[EMAIL PROTECTED] to phase
dispatch
DEBUG - HandlerPipeline - adding handler
[EMAIL PROTECTED] to phase
dispatch
DEBUG - HandlerPipeline - adding handler
[EMAIL PROTECTED] to phase
dispatch
DEBUG - HandlerPipeline - adding handler
[EMAIL PROTECTED] t
o
phase service
DEBUG - HandlerPipeline - adding handler
[EMAIL PROTECTED]
to phase
service
DEBUG - HandlerPipeline - Invoking phase transport
DEBUG - HandlerPipeline - Invoking phase parse
DEBUG - HandlerPipeline - Invoking phase pre-dispatch
DEBUG - HandlerPipeline - Invoking phase dispatch
DEBUG - HandlerPipeline - Invoking handler
org.codehaus.xfire.handler.LocateBindingHandler in phase dispatch
DEBUG - HandlerPipeline - Invoking handler
org.codehaus.xfire.soap.handler.SoapBodyHandler in phase dispatch
DEBUG - HandlerPipeline - Invoking handler
org.codehaus.xfire.handler.DispatchServiceHandler in phase dispatch
DEBUG - HandlerPipeline - adding handler
[EMAIL PROTECTED] to phase send
DEBUG - HandlerPipeline - Invoking phase policy
DEBUG - HandlerPipeline - Invoking phase user
DEBUG - HandlerPipeline - Invoking phase pre-invoke
DEBUG - HandlerPipeline - Invoking phase service
DEBUG - HandlerPipeline - Invoking handler
org.codehaus.xfire.service.binding.ServiceInvocationHandler in
phase service
INFO - DefaultFaultHandler - Fault occurred!
org.codehaus.xfire.fault.XFireFault: Not enough message parts were
received
for the operation.
at
org.codehaus.xfire.service.binding.ServiceInvocationHandler.fillInHold
ers(ServiceInvocationHandler.java:240)
at
org.codehaus.xfire.service.binding.ServiceInvocationHandler.invoke
(ServiceInvocationHandler.java:73)
at
org.codehaus.xfire.handler.HandlerPipeline.invoke
(HandlerPipeline.java:131)
at
org.codehaus.xfire.transport.DefaultEndpoint.onReceive
(DefaultEndpoint.java:64)
at
org.codehaus.xfire.transport.AbstractChannel.receive
(AbstractChannel.java:38)
at
org.apache.servicemix.jsr181.Jsr181ExchangeProcessor.process
(Jsr181ExchangeProcessor.java:113)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess
(AsyncBaseLifeCycle.java:489)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange
(AsyncBaseLifeCycle.java:441)
at
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange
(BaseLifeCycle.java:46)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound
(DeliveryChannelImpl.java:595)
at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting
(AbstractFlow.java:174)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting
(SedaFlow.java:176)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run
(SedaQueue.java:134)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:595)
DEBUG - HandlerPipeline - adding handler
[EMAIL PROTECTED] to phase send
DEBUG - HandlerPipeline - adding handler
[EMAIL PROTECTED] to phase user
DEBUG - HandlerPipeline - Invoking phase post-invoke
DEBUG - HandlerPipeline - Invoking phase policy
DEBUG - HandlerPipeline - Invoking phase user
DEBUG - HandlerPipeline - Invoking handler
org.codehaus.xfire.handler.CustomFaultHandler in phase user
DEBUG - HandlerPipeline - Invoking phase transport
DEBUG - HandlerPipeline - Invoking phase send
DEBUG - HandlerPipeline - Invoking handler
org.codehaus.xfire.fault.FaultSender in phase send
DEBUG - MyComponent - Received exchange: status:
Active,
role: consumer
DEBUG - MyComponent - Retrieved correlation id:
ID:162.70.8.49-114993b5139-3:3
ERROR - tapestry
Any ideas?
--
View this message in context: http://www.nabble.com/Moving-to-Linux-
tf4332802s12049.html#a12340034
Sent from the ServiceMix - User mailing list archive at Nabble.com.
