How easy will it be for you to run with mod and catch the error again? Do we need to think really hard about all the different possibilities and design a comprehensive trap now up front or can we do something quick and simple first and based on the results of that if we need more or different info can we write another trap patch for you to try?
>From a quick look it seems like if org.apache.tuscany.sca.host.jms.asf.ServiceInvoker.onMessage was changed to dumped out the context of the JMS request message on an exception and org.apache.tuscany.sca.implementation.spring.invocation.SpringInvoker.doInvoke did the same with the request it gets then that would give us a better picture of what the request objects looked like and why its getting an argument type mismatch. ...ant On Fri, Jul 29, 2011 at 10:49 AM, ant elder <[email protected]> wrote: > Ok, can you give me some more detail about what you're doing. Do you > have the complete stacktrace from that exception? It looks like thats > using <implementation.spring> and you've said it uses the JMS binding > so can you you show the composite for that with the binding > configuration. Are you running a Tuscany standalone runtime or in a > webapp or something else? > > ...ant > > On Fri, Jul 29, 2011 at 10:37 AM, Gregor Kiddie > <[email protected]> wrote: >> I'd be overjoyed with that! >> >> Gk. >> >> -----Original Message----- >> From: ant elder [mailto:[email protected]] >> Sent: 29 July 2011 10:23 >> To: [email protected] >> Subject: Re: Exceptions occur over time. >> >> This sounds like it could be quite hard to track down. Would it be >> possible to give you a patched version of the code which you then run >> with and try to recreate? If so we could patch the code so that when >> that particular exception happens we try to dump out more detailed >> diagnostics to see if that could help pin down whats happening. >> >> ...ant >> >> On Tue, Jul 26, 2011 at 1:43 PM, Gregor Kiddie >> <[email protected]> wrote: >>> Tuscany 1.6 (Getting that up front as I always forget!) >>> >>> >>> >>> We're getting this error occurring over time in our application. It's a >>> distributed Domain spread over 5 machines using JMS as the transport. When >>> the modules start, all communication is fine. After a period of time >>> (random, but never shorter than a couple of hours), some of the connections >>> start getting this error. Nothing changes code wise between the application >>> working, and not working. >>> >>> >>> >>> >>> >>> remote service exception, see nested exception >>> >>> java.lang.RuntimeException: Message = argument type mismatch >>> >>> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native >>> Method) >>> >>> >> at >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >>> >>> >> at >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>> >>> >> at java.lang.reflect.Method.invoke(Method.java:597) >>> >>> >> at >>> org.apache.tuscany.sca.implementation.spring.invocation.SpringInvoker.doInvoke(SpringInvoker.java:97) >>> >>> >> at >>> org.apache.tuscany.sca.implementation.spring.invocation.SpringInvoker.invoke(SpringInvoker.java:113) >>> >>> >> at >>> org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:60) >>> >>> >>> >>> >>> >>> >>> >>> Any suggestions as to why this is happening, as we can't see any good reason >>> for this happening! >>> >>> >>> >>> Gk. >> >
