You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Lance Finn Helsten (JIRA)" <ji...@apache.org> on 2008/02/22 18:06:15 UTC
[jira] Created: (SM-1245) Every other parameter is dropped on a
SOAP call if log4j logging is not turned on.
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.
[jira] Commented: (SM-1245) Every other parameter is dropped on a
SOAP call if log4j logging is not turned on.
Posted by "Marc Palyart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48762#action_48762 ]
Marc Palyart commented on SM-1245:
----------------------------------
I have the same problem with ServiceMix 3.2.1 and the change of the log4j config file "fix" the problem. I tried to run it with ServiceMix 3.3 and it looks like the change of the log4j config file doesn't "fix" the problem anymore. I'm really curious to know how a log parameter can affect the application execution flow. Anyway this is the error I get on the console with ServiceMix 3.3 :
SupportWebServiceInterface.loginAme(hilas.groundsupport.esb.beans.LoginAme)'. Nested exception is java.lang.reflect.InvocationTargetException: null
at org.codehaus.xfire.fault.XFireFault.createFault(XFireFault.java:89)
at org.codehaus.xfire.service.binding.ServiceInvocationHandler$1.run(ServiceInvocationHandler.java:90)
at org.codehaus.xfire.service.binding.ServiceInvocationHandler.execute(ServiceInvocationHandler.java:134)
at org.codehaus.xfire.service.binding.ServiceInvocationHandler.invoke(ServiceInvocationHandler.java:109)
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.Jsr181Endpoint.process(Jsr181Endpoint.java:498)
at org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:600)
at org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:554)
at org.apache.servicemix.common.AsyncBaseLifeCycle.onMessageExchange(AsyncBaseLifeCycle.java:510)
at org.apache.servicemix.common.SyncLifeCycleWrapper.onMessageExchange(SyncLifeCycleWrapper.java:60)
at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImp...
> 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.
[jira] Commented: (SM-1245) Every other parameter is dropped on a
SOAP call if log4j logging is not turned on.
Posted by "Bernhard Huber (JIRA)" <ji...@apache.org>.
[ 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.