You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Crimor <cr...@web.de> on 2008/10/01 12:57:26 UTC
Re: RemoteServiceMixClient sendSync response error
Hi Gert,
I just build a new versions of servicemix and components. Deploy my services
and then starts my remoteservicemixclient. Now a new error occurs. The
remoteservicemixclient can't even call the other services and promt
following error:
http://www.nabble.com/file/p19758121/JMSException.txt JMSException.txt
Greetings
Stephan
Gert Vanthienen wrote:
>
> L.S.,
>
> This was a bug in our latest release, where the CXF message exchanges
> contained an object that isn't serializable [1]. If you are using the
> RemoteServicemixClient, you're using JMS to communicate with the
> container and messages are being serialized to be put in the queues.
> Could you try with a more recent version of the CXF components installed
> on the container?
>
> Regards,
>
> Gert
>
> -----
> ---
> Gert Vanthienen
> http://www.anova.be
>
--
View this message in context: http://www.nabble.com/RemoteServiceMixClient-sendSync-response-error-tp19738724p19758121.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: RemoteServiceMixClient sendSync response error
Posted by Crimor <cr...@web.de>.
Hi Gert,
yes I synchronize servicemix3.3 on
http://svn.apache.org/repos/asf/servicemix/smx3/trunk and components on
http://svn.apache.org/repos/asf/servicemix/components Repository. So I
should have the newest versions. I build first the components with maven and
afterwards servicemix. So I guess this should be ok.
Regards
Stephan
Gert Vanthienen wrote:
>
> Stephan,
>
> Do you get this after a full rebuild of ServiceMix and the components?
> If so, I think you should open a JIRA issue for it -- this shouldn't
> happen if all classes are up-to-date.
>
> Regards,
>
> Gert
>
> Crimor wrote:
>> Hi Gert,
>>
>> I just build a new versions of servicemix and components. Deploy my
>> services
>> and then starts my remoteservicemixclient. Now a new error occurs. The
>> remoteservicemixclient can't even call the other services and promt
>> following error:
>>
>> http://www.nabble.com/file/p19758121/JMSException.txt JMSException.txt
>>
>> Greetings
>>
>> Stephan
>>
>>
>> Gert Vanthienen wrote:
>>
>>> L.S.,
>>>
>>> This was a bug in our latest release, where the CXF message exchanges
>>> contained an object that isn't serializable [1]. If you are using the
>>> RemoteServicemixClient, you're using JMS to communicate with the
>>> container and messages are being serialized to be put in the queues.
>>> Could you try with a more recent version of the CXF components installed
>>> on the container?
>>>
>>> Regards,
>>>
>>> Gert
>>>
>>> -----
>>> ---
>>> Gert Vanthienen
>>> http://www.anova.be
>>>
>>>
>>
>>
>
>
>
> -----
> ---
> Gert Vanthienen
> http://www.anova.be
>
--
View this message in context: http://www.nabble.com/RemoteServiceMixClient-sendSync-response-error-tp19738724p19762050.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: RemoteServiceMixClient sendSync response error
Posted by Gert Vanthienen <ge...@skynet.be>.
Stephan,
Do you get this after a full rebuild of ServiceMix and the components?
If so, I think you should open a JIRA issue for it -- this shouldn't
happen if all classes are up-to-date.
Regards,
Gert
Crimor wrote:
> Hi Gert,
>
> I just build a new versions of servicemix and components. Deploy my services
> and then starts my remoteservicemixclient. Now a new error occurs. The
> remoteservicemixclient can't even call the other services and promt
> following error:
>
> http://www.nabble.com/file/p19758121/JMSException.txt JMSException.txt
>
> Greetings
>
> Stephan
>
>
> Gert Vanthienen wrote:
>
>> L.S.,
>>
>> This was a bug in our latest release, where the CXF message exchanges
>> contained an object that isn't serializable [1]. If you are using the
>> RemoteServicemixClient, you're using JMS to communicate with the
>> container and messages are being serialized to be put in the queues.
>> Could you try with a more recent version of the CXF components installed
>> on the container?
>>
>> Regards,
>>
>> Gert
>>
>> -----
>> ---
>> Gert Vanthienen
>> http://www.anova.be
>>
>>
>
>