Community
Participate
Working Groups
OS: Windows Server 2008 R2 Standard Service Park 1 64-bit Operating System JDK: java version "1.6.0_20" Java(TM) SE Runtime Environment (build 1.6.0_20-b02) Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode) Spring Version: 2.5.6.SEC01 Our application has a lot of java batch jobs that are been run on the server. Almost once a week, our batch jobs would failed to run with the jvm crashed with the attached log hs_err_pid3488.log. Based on the log, it is pointing the problematic frame from aspectJ # JRE version: 6.0_20-b02 # Java VM: Java HotSpot(TM) 64-Bit Server VM (16.3-b01 mixed mode windows-amd64 ) # Problematic frame: # J org.aspectj.weaver.UnresolvedType.nameToSignature(Ljava/lang/String;)Ljava/lang/String; We have tried upgrading to the latest version of aspjectJ 1.6.12 and aspectJ 1.7.0M1 but we are still hitting this error. After we re-run the batch job again, the error would disappear. Our batch job is using the spring framework and transaction is been controlled using AOP. Thanks.
Created attachment 212184 [details] Error log from jvm
Not quite sure why it will be complaining, but something interesting I noticed just now is that nameToSignature() is one of the very few methods that has an 'assert' in it. What I've done in a commit just now is rework the method, restructure it a bit, remove the assert. Hopefully that will keep the JDK happy. If you want to try it out, it is in the dev build available at: http://eclipse.org/aspectj/downloads.php You could also maybe try a later JDK in case it is a JVM issue.
Hi Andrew, Thanks, we would try the latest build of aspectJ to see. Would keep you updated with the findings.
Hi Andrew, We have tested with the latest development build DEVELOPMENT-20120307120800 but we are still encountering the same error. So the assert fix seems not to be applicable to this error.
Can you maybe try updating your JDK?
