[jira] (MNG-5676) mvn -U crashes with IBM JDK
[ https://jira.codehaus.org/browse/MNG-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352793#comment-352793 ] Jason van Zyl commented on MNG-5676: Fix on 1a05ae3def04c11f5906f2399af139d4326fdce6 mvn -U crashes with IBM JDK --- Key: MNG-5676 URL: https://jira.codehaus.org/browse/MNG-5676 Project: Maven Issue Type: Bug Affects Versions: 3.1.1, 3.2.2, 3.2.3 Environment: IBM JDK, OpenSuSE enterprise server 11 Reporter: Dan Tran Assignee: Jason van Zyl Fix For: 3.2.4 details discussion is at http://maven.40175.n5.nabble.com/Upgrade-to-3-1-1-causes-problems-td5776875.html work around is replace boot/plexus-classworlds-2.5.x.jar with plexus-classworlds-2.4.1.jar as discussed at the link -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5676) mvn -U crashes with IBM JDK
[ https://jira.codehaus.org/browse/MNG-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-5676. -- Resolution: Fixed mvn -U crashes with IBM JDK --- Key: MNG-5676 URL: https://jira.codehaus.org/browse/MNG-5676 Project: Maven Issue Type: Bug Affects Versions: 3.1.1, 3.2.2, 3.2.3 Environment: IBM JDK, OpenSuSE enterprise server 11 Reporter: Dan Tran Assignee: Jason van Zyl Fix For: 3.2.4 details discussion is at http://maven.40175.n5.nabble.com/Upgrade-to-3-1-1-causes-problems-td5776875.html work around is replace boot/plexus-classworlds-2.5.x.jar with plexus-classworlds-2.4.1.jar as discussed at the link -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5676) mvn -U crashes with IBM JDK
[ https://jira.codehaus.org/browse/MNG-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-5676: --- Assignee: Jason van Zyl mvn -U crashes with IBM JDK --- Key: MNG-5676 URL: https://jira.codehaus.org/browse/MNG-5676 Project: Maven Issue Type: Bug Affects Versions: 3.1.1, 3.2.2, 3.2.3 Environment: IBM JDK, OpenSuSE enterprise server 11 Reporter: Dan Tran Assignee: Jason van Zyl Fix For: 3.2.4 details discussion is at http://maven.40175.n5.nabble.com/Upgrade-to-3-1-1-causes-problems-td5776875.html work around is replace boot/plexus-classworlds-2.5.x.jar with plexus-classworlds-2.4.1.jar as discussed at the link -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5676) mvn -U crashes with IBM JDK
[ https://jira.codehaus.org/browse/MNG-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-5676: --- Fix Version/s: 3.2.4 Affects Version/s: 3.2.3 mvn -U crashes with IBM JDK --- Key: MNG-5676 URL: https://jira.codehaus.org/browse/MNG-5676 Project: Maven Issue Type: Bug Affects Versions: 3.1.1, 3.2.2, 3.2.3 Environment: IBM JDK, OpenSuSE enterprise server 11 Reporter: Dan Tran Fix For: 3.2.4 details discussion is at http://maven.40175.n5.nabble.com/Upgrade-to-3-1-1-causes-problems-td5776875.html work around is replace boot/plexus-classworlds-2.5.x.jar with plexus-classworlds-2.4.1.jar as discussed at the link -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5676) mvn -U crashes with IBM JDK
[ https://jira.codehaus.org/browse/MNG-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351711#comment-351711 ] BJ Hargrave commented on MNG-5676: -- I have debugged this and there is an error in the getClassLoadingLock implementation in IBM Java. I am reporting this to the IBM Java team. In the interim, I have created a workaround at https://github.com/bjhargrave/plexus-classworlds/compare/loadinglocks that avoids the problem. With this workaround, maven works fine on IBM Java and Oracle Java. mvn -U crashes with IBM JDK --- Key: MNG-5676 URL: https://jira.codehaus.org/browse/MNG-5676 Project: Maven Issue Type: Bug Affects Versions: 3.1.1, 3.2.2 Environment: IBM JDK, OpenSuSE enterprise server 11 Reporter: Dan Tran details discussion is at http://maven.40175.n5.nabble.com/Upgrade-to-3-1-1-causes-problems-td5776875.html work around is replace boot/plexus-classworlds-2.5.x.jar with plexus-classworlds-2.4.1.jar as discussed at the link -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5676) mvn -U crashes with IBM JDK
[ https://jira.codehaus.org/browse/MNG-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351712#comment-351712 ] Kristian Rosenvold commented on MNG-5676: - That's great; would you mind shedding some light on the nature of the problem you found ? I have tried debugging a parallel class loading related issue with IBM jdk but did not manage to find the problem. Could this be related ? mvn -U crashes with IBM JDK --- Key: MNG-5676 URL: https://jira.codehaus.org/browse/MNG-5676 Project: Maven Issue Type: Bug Affects Versions: 3.1.1, 3.2.2 Environment: IBM JDK, OpenSuSE enterprise server 11 Reporter: Dan Tran details discussion is at http://maven.40175.n5.nabble.com/Upgrade-to-3-1-1-causes-problems-td5776875.html work around is replace boot/plexus-classworlds-2.5.x.jar with plexus-classworlds-2.4.1.jar as discussed at the link -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5676) mvn -U crashes with IBM JDK
[ https://jira.codehaus.org/browse/MNG-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351713#comment-351713 ] BJ Hargrave commented on MNG-5676: -- Probably. The implementation of loadClass(String,boolean) incorrectly forgets about class loading locks already returned to callers of getClassLoadingLock. So if the code calls getClassLoadingLock and synchronizes on the lock and then calls super.loadClass(String,boolean) before findLoadedClass/defineClass, another thread that calls getClassLoadingLock after the first thread calls super.loadClass(String,boolean) will get a different lock object. So both threads can then race to define the class and boom. mvn -U crashes with IBM JDK --- Key: MNG-5676 URL: https://jira.codehaus.org/browse/MNG-5676 Project: Maven Issue Type: Bug Affects Versions: 3.1.1, 3.2.2 Environment: IBM JDK, OpenSuSE enterprise server 11 Reporter: Dan Tran details discussion is at http://maven.40175.n5.nabble.com/Upgrade-to-3-1-1-causes-problems-td5776875.html work around is replace boot/plexus-classworlds-2.5.x.jar with plexus-classworlds-2.4.1.jar as discussed at the link -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5676) mvn -U crashes with IBM JDK
[ https://jira.codehaus.org/browse/MNG-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351713#comment-351713 ] BJ Hargrave edited comment on MNG-5676 at 8/22/14 9:46 AM: --- Probably. The implementation of loadClass(String,boolean) incorrectly forgets about class loading locks already returned to callers of getClassLoadingLock. So if the code calls getClassLoadingLock and synchronizes on the lock and then calls super.loadClass(String,boolean) before findLoadedClass/defineClass, another thread that calls getClassLoadingLock after the first thread calls super.loadClass(String,boolean) will get a different lock object. So both threads can then race to define the class and boom. Basically, if ClassLoader.loadClass(String,boolean) is called in a critical section protected by the lock from ClassLoader.getClassLoadingLock, you are in trouble. So the workaround is to override getClassLoadingLock. was (Author: bjhargrave): Probably. The implementation of loadClass(String,boolean) incorrectly forgets about class loading locks already returned to callers of getClassLoadingLock. So if the code calls getClassLoadingLock and synchronizes on the lock and then calls super.loadClass(String,boolean) before findLoadedClass/defineClass, another thread that calls getClassLoadingLock after the first thread calls super.loadClass(String,boolean) will get a different lock object. So both threads can then race to define the class and boom. mvn -U crashes with IBM JDK --- Key: MNG-5676 URL: https://jira.codehaus.org/browse/MNG-5676 Project: Maven Issue Type: Bug Affects Versions: 3.1.1, 3.2.2 Environment: IBM JDK, OpenSuSE enterprise server 11 Reporter: Dan Tran details discussion is at http://maven.40175.n5.nabble.com/Upgrade-to-3-1-1-causes-problems-td5776875.html work around is replace boot/plexus-classworlds-2.5.x.jar with plexus-classworlds-2.4.1.jar as discussed at the link -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5676) mvn -U crashes with IBM JDK
[ https://jira.codehaus.org/browse/MNG-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351713#comment-351713 ] BJ Hargrave edited comment on MNG-5676 at 8/22/14 9:47 AM: --- Probably. The implementation of loadClass(String,boolean) incorrectly forgets about class loading locks already returned to callers of getClassLoadingLock. So if the code calls getClassLoadingLock and synchronizes on the lock and then calls super.loadClass(String,boolean) before findLoadedClass/defineClass, another thread that calls getClassLoadingLock after the first thread calls super.loadClass(String,boolean) will get a different lock object. So both threads can then race to define the class and boom. Basically, if ClassLoader.loadClass(String,boolean) is called in a critical section protected by the lock from ClassLoader.getClassLoadingLock, you are in trouble since the call to ClassLoader.loadClass(String,boolean) effectively ends the critical section. So the workaround is to override getClassLoadingLock. was (Author: bjhargrave): Probably. The implementation of loadClass(String,boolean) incorrectly forgets about class loading locks already returned to callers of getClassLoadingLock. So if the code calls getClassLoadingLock and synchronizes on the lock and then calls super.loadClass(String,boolean) before findLoadedClass/defineClass, another thread that calls getClassLoadingLock after the first thread calls super.loadClass(String,boolean) will get a different lock object. So both threads can then race to define the class and boom. Basically, if ClassLoader.loadClass(String,boolean) is called in a critical section protected by the lock from ClassLoader.getClassLoadingLock, you are in trouble. So the workaround is to override getClassLoadingLock. mvn -U crashes with IBM JDK --- Key: MNG-5676 URL: https://jira.codehaus.org/browse/MNG-5676 Project: Maven Issue Type: Bug Affects Versions: 3.1.1, 3.2.2 Environment: IBM JDK, OpenSuSE enterprise server 11 Reporter: Dan Tran details discussion is at http://maven.40175.n5.nabble.com/Upgrade-to-3-1-1-causes-problems-td5776875.html work around is replace boot/plexus-classworlds-2.5.x.jar with plexus-classworlds-2.4.1.jar as discussed at the link -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5676) mvn -U crashes with IBM JDK
[ https://jira.codehaus.org/browse/MNG-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351727#comment-351727 ] Kristian Rosenvold commented on MNG-5676: - I'd appreciate it if you linked any issues you file in the IBM issue trackers, assuming IBM has anything like that which is public :) mvn -U crashes with IBM JDK --- Key: MNG-5676 URL: https://jira.codehaus.org/browse/MNG-5676 Project: Maven Issue Type: Bug Affects Versions: 3.1.1, 3.2.2 Environment: IBM JDK, OpenSuSE enterprise server 11 Reporter: Dan Tran details discussion is at http://maven.40175.n5.nabble.com/Upgrade-to-3-1-1-causes-problems-td5776875.html work around is replace boot/plexus-classworlds-2.5.x.jar with plexus-classworlds-2.4.1.jar as discussed at the link -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5676) mvn -U crashes with IBM JDK
[ https://jira.codehaus.org/browse/MNG-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351728#comment-351728 ] BJ Hargrave commented on MNG-5676: -- The IBM PMR number is 24945,001,866. I don't know if there is a public link for it. mvn -U crashes with IBM JDK --- Key: MNG-5676 URL: https://jira.codehaus.org/browse/MNG-5676 Project: Maven Issue Type: Bug Affects Versions: 3.1.1, 3.2.2 Environment: IBM JDK, OpenSuSE enterprise server 11 Reporter: Dan Tran details discussion is at http://maven.40175.n5.nabble.com/Upgrade-to-3-1-1-causes-problems-td5776875.html work around is replace boot/plexus-classworlds-2.5.x.jar with plexus-classworlds-2.4.1.jar as discussed at the link -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5676) mvn -U crashes with IBM JDK
[ https://jira.codehaus.org/browse/MNG-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351729#comment-351729 ] BJ Hargrave commented on MNG-5676: -- Also, I submitted a PR for the workaround. https://github.com/sonatype/plexus-classworlds/pull/15 mvn -U crashes with IBM JDK --- Key: MNG-5676 URL: https://jira.codehaus.org/browse/MNG-5676 Project: Maven Issue Type: Bug Affects Versions: 3.1.1, 3.2.2 Environment: IBM JDK, OpenSuSE enterprise server 11 Reporter: Dan Tran details discussion is at http://maven.40175.n5.nabble.com/Upgrade-to-3-1-1-causes-problems-td5776875.html work around is replace boot/plexus-classworlds-2.5.x.jar with plexus-classworlds-2.4.1.jar as discussed at the link -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5676) mvn -U crashes with IBM JDK
[ https://jira.codehaus.org/browse/MNG-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351736#comment-351736 ] Kristian Rosenvold commented on MNG-5676: - I'm in favor of letting IBM fix the bug. If it takes an inordinate amount time, we'll do the pull request. Do keep us posted on what happens to 24945,001,866 :) mvn -U crashes with IBM JDK --- Key: MNG-5676 URL: https://jira.codehaus.org/browse/MNG-5676 Project: Maven Issue Type: Bug Affects Versions: 3.1.1, 3.2.2 Environment: IBM JDK, OpenSuSE enterprise server 11 Reporter: Dan Tran details discussion is at http://maven.40175.n5.nabble.com/Upgrade-to-3-1-1-causes-problems-td5776875.html work around is replace boot/plexus-classworlds-2.5.x.jar with plexus-classworlds-2.4.1.jar as discussed at the link -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5676) mvn -U crashes with IBM JDK
[ https://jira.codehaus.org/browse/MNG-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351310#comment-351310 ] Jason van Zyl commented on MNG-5676: Which version of Java are you running on? mvn -U crashes with IBM JDK --- Key: MNG-5676 URL: https://jira.codehaus.org/browse/MNG-5676 Project: Maven Issue Type: Bug Affects Versions: 3.1.1, 3.2.2 Environment: IBM JDK, OpenSuSE enterprise server 11 Reporter: Dan Tran details discussion is at http://maven.40175.n5.nabble.com/Upgrade-to-3-1-1-causes-problems-td5776875.html work around is replace boot/plexus-classworlds-2.5.x.jar with plexus-classworlds-2.4.1.jar as discussed at the link -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5676) mvn -U crashes with IBM JDK
[ https://jira.codehaus.org/browse/MNG-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=351312#comment-351312 ] Dan Tran commented on MNG-5676: --- I am using java version 1.7.0 Java(TM) SE Runtime Environment (build pxa6470sr6fp1-20140108_01(SR6 FP1)) IBM J9 VM (build 2.6, JRE 1.7.0 Linux amd64-64 Compressed References 20140106_181350 (JIT enabled, AOT enabled) J9VM - R26_Java726_SR6_20140106_1601_B181350 JIT - r11.b05_20131003_47443.02 GC - R26_Java726_SR6_20140106_1601_B181350_CMPRSS J9CL - 20140106_181350) JCL - 20140103_01 based on Oracle 7u51-b11 mvn -U crashes with IBM JDK --- Key: MNG-5676 URL: https://jira.codehaus.org/browse/MNG-5676 Project: Maven Issue Type: Bug Affects Versions: 3.1.1, 3.2.2 Environment: IBM JDK, OpenSuSE enterprise server 11 Reporter: Dan Tran details discussion is at http://maven.40175.n5.nabble.com/Upgrade-to-3-1-1-causes-problems-td5776875.html work around is replace boot/plexus-classworlds-2.5.x.jar with plexus-classworlds-2.4.1.jar as discussed at the link -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5676) mvn -U crashes with IBM JDK
Dan Tran created MNG-5676: - Summary: mvn -U crashes with IBM JDK Key: MNG-5676 URL: https://jira.codehaus.org/browse/MNG-5676 Project: Maven Issue Type: Bug Affects Versions: 3.2.2, 3.1.1 Environment: IBM JDK, OpenSuSE enterprise server 11 Reporter: Dan Tran details discussion is at http://maven.40175.n5.nabble.com/Upgrade-to-3-1-1-causes-problems-td5776875.html work around is replace boot/plexus-classworlds-2.5.x.jar with plexus-classworlds-2.4.1.jar as discussed at the link -- This message was sent by Atlassian JIRA (v6.1.6#6162)
