You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by Ruwan Linton <ru...@gmail.com> on 2009/06/07 19:26:57 UTC
Sample 51 client side issue when Synapse is runing on DEBUG mode
Folks,
When I start the sample 51 with org.apache.synapse log level set to DEBUG I
get an RuntimeException on the client side;
optimizeclient:
[java] Sending file :
./../../repository/conf/sample/resources/mtom/asf-logo.gif as MTOM
[java] 2009-06-07 22:51:47,541 [-] [main] ERROR SandeshaModule Could
not load module policies. Using default values.
[java] 2009-06-07 22:51:47,612 [-] [main] INFO MailTransportSender
MAILTO Sender started
[java] 2009-06-07 22:51:47,623 [-] [main] INFO JMSSender JMS Sender
started
[java] 2009-06-07 22:51:47,625 [-] [main] INFO JMSSender JMS Transport
Sender initialized...
[java] Exception in thread "main" java.lang.RuntimeException: ContentID
is null
[java] at
org.apache.axiom.om.impl.llom.OMTextImpl.getDataHandler(OMTextImpl.java:363)
[java] at samples.userguide.MTOMSwAClient.sendUsingMTOM(Unknown
Source)
[java] at samples.userguide.MTOMSwAClient.main(Unknown Source)
Please note that this happens only if the DEBUG logs are on... So I assume
that this is something to do with the serialization.
Any one having a clue on what is going wrong here.
Thanks,
Ruwan
--
Ruwan Linton
Senior Software Engineer & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com
Re: Sample 51 client side issue when Synapse is runing on DEBUG mode
Posted by Supun Kamburugamuva <su...@gmail.com>.
Thanks for the pointer. This is the exact error.
Supun.
On Wed, Jun 10, 2009 at 2:59 PM, Andreas Veithen
<an...@gmail.com>wrote:
> Sounds like WSCOMMONS-446.
>
> Andreas
>
> On Wed, Jun 10, 2009 at 11:56, Supun Kamburugamuva<su...@gmail.com>
> wrote:
> > Hi all,
> >
> > This error occurs when we do a serialize call before doing a
> > serializeAndConsume method of Envelope. In the debug mode we are
> serializing
> > the Envelope in the SynapseCallbackReceiver. Then we call
> > serializeAndConsume in the HTTPCoreNIOSender. This causes the XML to be
> > serialized incorrectly. Does anyone has idea about this?
> >
> > Thanks,
> > Supun..
> >
> > On Sun, Jun 7, 2009 at 10:26 PM, Ruwan Linton <ru...@gmail.com>
> > wrote:
> >>
> >> Folks,
> >>
> >> When I start the sample 51 with org.apache.synapse log level set to
> DEBUG
> >> I get an RuntimeException on the client side;
> >>
> >> optimizeclient:
> >> [java] Sending file :
> >> ./../../repository/conf/sample/resources/mtom/asf-logo.gif as MTOM
> >> [java] 2009-06-07 22:51:47,541 [-] [main] ERROR SandeshaModule
> Could
> >> not load module policies. Using default values.
> >> [java] 2009-06-07 22:51:47,612 [-] [main] INFO MailTransportSender
> >> MAILTO Sender started
> >> [java] 2009-06-07 22:51:47,623 [-] [main] INFO JMSSender JMS
> Sender
> >> started
> >> [java] 2009-06-07 22:51:47,625 [-] [main] INFO JMSSender JMS
> >> Transport Sender initialized...
> >> [java] Exception in thread "main" java.lang.RuntimeException:
> >> ContentID is null
> >> [java] at
> >>
> org.apache.axiom.om.impl.llom.OMTextImpl.getDataHandler(OMTextImpl.java:363)
> >> [java] at samples.userguide.MTOMSwAClient.sendUsingMTOM(Unknown
> >> Source)
> >> [java] at samples.userguide.MTOMSwAClient.main(Unknown Source)
> >>
> >>
> >> Please note that this happens only if the DEBUG logs are on... So I
> assume
> >> that this is something to do with the serialization.
> >>
> >> Any one having a clue on what is going wrong here.
> >>
> >> Thanks,
> >> Ruwan
> >>
> >> --
> >> Ruwan Linton
> >> Senior Software Engineer & Product Manager; WSO2 ESB;
> http://wso2.org/esb
> >> WSO2 Inc.; http://wso2.org
> >> email: ruwan@wso2.com; cell: +94 77 341 3097
> >> blog: http://ruwansblog.blogspot.com
> >
> >
> >
> > --
> > Software Engineer, WSO2 Inc
> > http://wso2.org
> > supunk.blogspot.com
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
--
Software Engineer, WSO2 Inc
http://wso2.org
supunk.blogspot.com
Re: Sample 51 client side issue when Synapse is runing on DEBUG mode
Posted by Andreas Veithen <an...@gmail.com>.
Sounds like WSCOMMONS-446.
Andreas
On Wed, Jun 10, 2009 at 11:56, Supun Kamburugamuva<su...@gmail.com> wrote:
> Hi all,
>
> This error occurs when we do a serialize call before doing a
> serializeAndConsume method of Envelope. In the debug mode we are serializing
> the Envelope in the SynapseCallbackReceiver. Then we call
> serializeAndConsume in the HTTPCoreNIOSender. This causes the XML to be
> serialized incorrectly. Does anyone has idea about this?
>
> Thanks,
> Supun..
>
> On Sun, Jun 7, 2009 at 10:26 PM, Ruwan Linton <ru...@gmail.com>
> wrote:
>>
>> Folks,
>>
>> When I start the sample 51 with org.apache.synapse log level set to DEBUG
>> I get an RuntimeException on the client side;
>>
>> optimizeclient:
>> [java] Sending file :
>> ./../../repository/conf/sample/resources/mtom/asf-logo.gif as MTOM
>> [java] 2009-06-07 22:51:47,541 [-] [main] ERROR SandeshaModule Could
>> not load module policies. Using default values.
>> [java] 2009-06-07 22:51:47,612 [-] [main] INFO MailTransportSender
>> MAILTO Sender started
>> [java] 2009-06-07 22:51:47,623 [-] [main] INFO JMSSender JMS Sender
>> started
>> [java] 2009-06-07 22:51:47,625 [-] [main] INFO JMSSender JMS
>> Transport Sender initialized...
>> [java] Exception in thread "main" java.lang.RuntimeException:
>> ContentID is null
>> [java] at
>> org.apache.axiom.om.impl.llom.OMTextImpl.getDataHandler(OMTextImpl.java:363)
>> [java] at samples.userguide.MTOMSwAClient.sendUsingMTOM(Unknown
>> Source)
>> [java] at samples.userguide.MTOMSwAClient.main(Unknown Source)
>>
>>
>> Please note that this happens only if the DEBUG logs are on... So I assume
>> that this is something to do with the serialization.
>>
>> Any one having a clue on what is going wrong here.
>>
>> Thanks,
>> Ruwan
>>
>> --
>> Ruwan Linton
>> Senior Software Engineer & Product Manager; WSO2 ESB; http://wso2.org/esb
>> WSO2 Inc.; http://wso2.org
>> email: ruwan@wso2.com; cell: +94 77 341 3097
>> blog: http://ruwansblog.blogspot.com
>
>
>
> --
> Software Engineer, WSO2 Inc
> http://wso2.org
> supunk.blogspot.com
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: Sample 51 client side issue when Synapse is runing on DEBUG mode
Posted by Supun Kamburugamuva <su...@gmail.com>.
Hi all,
This error occurs when we do a serialize call before doing a
serializeAndConsume method of Envelope. In the debug mode we are serializing
the Envelope in the SynapseCallbackReceiver. Then we call
serializeAndConsume in the HTTPCoreNIOSender. This causes the XML to be
serialized incorrectly. Does anyone has idea about this?
Thanks,
Supun..
On Sun, Jun 7, 2009 at 10:26 PM, Ruwan Linton <ru...@gmail.com>wrote:
> Folks,
>
> When I start the sample 51 with org.apache.synapse log level set to DEBUG I
> get an RuntimeException on the client side;
>
> optimizeclient:
> [java] Sending file :
> ./../../repository/conf/sample/resources/mtom/asf-logo.gif as MTOM
> [java] 2009-06-07 22:51:47,541 [-] [main] ERROR SandeshaModule Could
> not load module policies. Using default values.
> [java] 2009-06-07 22:51:47,612 [-] [main] INFO MailTransportSender
> MAILTO Sender started
> [java] 2009-06-07 22:51:47,623 [-] [main] INFO JMSSender JMS Sender
> started
> [java] 2009-06-07 22:51:47,625 [-] [main] INFO JMSSender JMS
> Transport Sender initialized...
> [java] Exception in thread "main" java.lang.RuntimeException:
> ContentID is null
> [java] at
> org.apache.axiom.om.impl.llom.OMTextImpl.getDataHandler(OMTextImpl.java:363)
> [java] at samples.userguide.MTOMSwAClient.sendUsingMTOM(Unknown
> Source)
> [java] at samples.userguide.MTOMSwAClient.main(Unknown Source)
>
>
> Please note that this happens only if the DEBUG logs are on... So I assume
> that this is something to do with the serialization.
>
> Any one having a clue on what is going wrong here.
>
> Thanks,
> Ruwan
>
> --
> Ruwan Linton
> Senior Software Engineer & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ruwan@wso2.com; cell: +94 77 341 3097
> blog: http://ruwansblog.blogspot.com
>
--
Software Engineer, WSO2 Inc
http://wso2.org
supunk.blogspot.com