[
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.
