Re: T5 IoC Advice: Inconsistent args_size for opc_invokeinterface
Hi Howard, Sorry, should have included it. I'm running java version 1.6.0_24 Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) on Ubuntu 10.10. I've had the feeling this may be a tough one to pin down. I can work around it for now by excluding some methods, so can wait for the ASM implementation and then try again. Cheers, Adriaan On 17 April 2011 22:15, Howard Lewis Ship hls...@gmail.com wrote: What JDK are you compiling for, executing under? It's very hard to say what the problem really is ... a bug in the wrappers around Tapestry or a bug in Javassist. I'm hoping that the 5.3 code, based on wrappers around ASM, will be faster, more efficient, and more stable. On Sun, Apr 17, 2011 at 12:30 AM, Adriaan Joubert adriaan...@gmail.com wrote: Which Tapestry-IoC version are you using? I tried with both 5.1.0.5 and 5.2.4. I should also mention that I thought this may have something to do with other advisors (we use them for transaction management as well as checking that a slave database has caught up to a certain point). I've marked all of these to prevent decoration and the specific method where it fails every time is not decorated other than by the timing advice. After more experimentation I can get this to run through with only excluding a handful of methods from the timing advice, all of them in a single service. These methods are always called from methods in other services, so the advice will appear more than once on the call chain. However in many other cases this does not cause any problems. I can't see anything special about any of the methods causing the problems, or the service for that matter, but they do create the problem in a reproducible fashion. A typical signature is public MonthlyStandardReturnsSeries create(TimeSeries timeSeries, MonthRange itv, double[] values); so nothing special. I have methods in the same service that use generic types, e.g. and they cause no problems. Any hint what to look for would be great - seems that this is usually a call out of the javassist generated code, so it is kind-of hard to debug. Cheers, Adriaan - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: T5 IoC Advice: Inconsistent args_size for opc_invokeinterface
Which Tapestry-IoC version are you using? I tried with both 5.1.0.5 and 5.2.4. I should also mention that I thought this may have something to do with other advisors (we use them for transaction management as well as checking that a slave database has caught up to a certain point). I've marked all of these to prevent decoration and the specific method where it fails every time is not decorated other than by the timing advice. After more experimentation I can get this to run through with only excluding a handful of methods from the timing advice, all of them in a single service. These methods are always called from methods in other services, so the advice will appear more than once on the call chain. However in many other cases this does not cause any problems. I can't see anything special about any of the methods causing the problems, or the service for that matter, but they do create the problem in a reproducible fashion. A typical signature is public MonthlyStandardReturnsSeries create(TimeSeries timeSeries, MonthRange itv, double[] values); so nothing special. I have methods in the same service that use generic types, e.g. and they cause no problems. Any hint what to look for would be great - seems that this is usually a call out of the javassist generated code, so it is kind-of hard to debug. Cheers, Adriaan - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: T5 IoC Advice: Inconsistent args_size for opc_invokeinterface
What JDK are you compiling for, executing under? It's very hard to say what the problem really is ... a bug in the wrappers around Tapestry or a bug in Javassist. I'm hoping that the 5.3 code, based on wrappers around ASM, will be faster, more efficient, and more stable. On Sun, Apr 17, 2011 at 12:30 AM, Adriaan Joubert adriaan...@gmail.com wrote: Which Tapestry-IoC version are you using? I tried with both 5.1.0.5 and 5.2.4. I should also mention that I thought this may have something to do with other advisors (we use them for transaction management as well as checking that a slave database has caught up to a certain point). I've marked all of these to prevent decoration and the specific method where it fails every time is not decorated other than by the timing advice. After more experimentation I can get this to run through with only excluding a handful of methods from the timing advice, all of them in a single service. These methods are always called from methods in other services, so the advice will appear more than once on the call chain. However in many other cases this does not cause any problems. I can't see anything special about any of the methods causing the problems, or the service for that matter, but they do create the problem in a reproducible fashion. A typical signature is public MonthlyStandardReturnsSeries create(TimeSeries timeSeries, MonthRange itv, double[] values); so nothing special. I have methods in the same service that use generic types, e.g. and they cause no problems. Any hint what to look for would be great - seems that this is usually a call out of the javassist generated code, so it is kind-of hard to debug. Cheers, Adriaan - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: T5 IoC Advice: Inconsistent args_size for opc_invokeinterface
On Sat, 16 Apr 2011 09:22:52 -0300, Adriaan Joubert adriaan...@gmail.com wrote: Hi, Hi! I tried to build a rough-and-ready timer for service method calls by using an advisor. We already use these for transaction management etc and never had an issue. However after many successful calls I suddenly get: Exception in thread Thread-26 java.lang.VerifyError: (class: Invocation$MonthlyTimeSeriesFactory$create$12f5e314f65, method: invokeDelegateMethod signature: ()V) Inconsistent args_size for opc_invokeinterface Which Tapestry-IoC version are you using? -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
