J.Gustafsson wrote:
>
> Hi,
>
> I have encountered a very strange error . I have a SA made of
> servicemix-http and servicemix-jsr181.
>
> When I set my log4j root logger to level "DEBUG", everything works fine.
> If I however set it to level "INFO", the applications starts looping in
> the the method checkHasMoreChildReaders() of the class
> org.codehaus.xfire.aegis.stax.ElementReader. This is due to the exchange
> looks a little bit weird:
>
> InOut[
> id: ID:192.168.170.140-1156f013ad4-2:1
> status: Active
> role: provider
> service: {http://XXX.com/trsService}TrsWebServicesImpl
> endpoint: TrsWebServicesImplJBIPort
> operation: {http://client.webservice.trs.XXX.com}exportTransactions
> in: Unable to display: java.util.EmptyStackException
> ]
>
> It also works if I step through the code in the debugger.
> I'm currently running ServiceMix 3.1.2. I have not had the same problem in
> earlier versions I have used.
>
> Any ideas?
>
> regards,
>
> Jonas Gustafsson
>
>
Hi,
I must correct myself. I have detected the same problem also in version
3.1.1-incubating but it works fine in 3.1-incubating.
I have also come down to a minimum requirement of the amount of logging on
DEBUG-level. It works as long as I set the logger of class
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue to level DEBUG. A timing
problem perhaps ???
regards,
/jonas
--
View this message in context:
http://www.nabble.com/Webservice-call-failes-when-log4j-level-is-set-to-DEBUG.-tf4575623s12049.html#a13095649
Sent from the ServiceMix - User mailing list archive at Nabble.com.
