[
https://issues.apache.org/activemq/browse/SM-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44189#action_44189
]
Bernhard Huber commented on SM-1245:
------------------------------------
I have similar problems, using log4j setting:
<logger name="org.apache.servicemix">
<!-- To enable debug logging, replace the INFO by DEBUG -->
<level value="INFO"/>
</logger>
<!-- DEBUG and NOT INFO BEGIN -->
<logger name="org.apache.servicemix.jbi.nmr.flow.seda">
<level value="DEBUG"/>
</logger>
everything works fine, if I use:
<logger name="org.apache.servicemix">
<!-- To enable debug logging, replace the INFO by DEBUG -->
<level value="INFO"/>
</logger>
<!-- DEBUG and NOT INFO BEGIN -->
<logger name="org.apache.servicemix.jbi.nmr.flow.seda">
<level value="INFO"/>
</logger>
(Note the second INFO level)
I receive soap responses, like:
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope";>
<soap:Body>
<soap:Fault>
<soap:Code>
<soap:Value>soap:Sender</soap:Value>
<soap:Subcode>
<soap:Value>soap:Sender</soap:Value>
</soap:Subcode>
</soap:Code>
<soap:Reason>
<soap:Text xml:lang="en">Not enough message parts were received for
the operation.</soap:Text>
</soap:Reason>
<soap:Detail>
<stack>org.codehaus.xfire.fault.XFireFault: Not enough message
parts were received for the operation.
at
org.codehaus.xfire.service.binding.ServiceInvocationHandler.fillInHolders(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:114)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:538)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:490)
at
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.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.seda.SedaFlow.doRouting(SedaFlow.java:167)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)</stack>
</soap:Detail>
</soap:Fault>
</soap:Body>
</soap:Envelope>
> Every other parameter is dropped on a SOAP call if log4j logging is not
> turned on.
> ----------------------------------------------------------------------------------
>
> Key: SM-1245
> URL: https://issues.apache.org/activemq/browse/SM-1245
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-jsr181
> Affects Versions: 3.2.1
> Environment: Built with maven and the XFire JSR181 tooling. Occurs on
> multiple platforms.
> Reporter: Lance Finn Helsten
>
> If JSR181 annotated class is created with a web method that has multiple
> parameters then every even parameter is dropped (i.e. 2nd, 4th, 6th, etc.
> parameters); if <servicemix>/conf/log4j.xml is not configured correctly.
> In the log4j.xml configuration file if in the start element the debug
> attribute is set to "false" or in the logger element for
> "org.apache.servicemix" the level is set to anything other than "DEBUG" then
> the above problem will manifest. If the debug attribute is set to "true" AND
> the log level is set to "DEBUG" then multiple parameters work correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
