6
來自java 7u45的樂趣不斷給予。這一次,它是webstart內部的一個死鎖。這種情況發生的非常一致(每次)啓動一個大型應用程序(〜100罐)。7u45 webstart中的新死鎖錯誤?
是否有其他人遇到這種情況或知道任何解決方法?除了恢復到1.7.0_40?
感謝,
Found one Java-level deadlock:
=============================
"Java Web Start Main Thread":
waiting to lock monitor 0x066368bc (object 0x29e65428, a java.lang.Class),
which is held by "Finalizer"
"Finalizer":
waiting to lock monitor 0x00dbc954 (object 0x2a1b52b0, a com.sun.deploy.cache.CacheEntry),
which is held by "Java Web Start Main Thread"
Java stack information for the threads listed above:
===================================================
"Java Web Start Main Thread":
at com.sun.deploy.cache.MemoryCache.getLoadedResource(Unknown Source)
- waiting to lock <0x29e65428> (a java.lang.Class for com.sun.deploy.cache.MemoryCache)
at com.sun.deploy.cache.CachedJarFile.getCacheEntry(Unknown Source)
- locked <0x24810058> (a com.sun.deploy.cache.CachedJarFile)
at com.sun.deploy.cache.CachedJarFile.getManifest(Unknown Source)
- locked <0x24810058> (a com.sun.deploy.cache.CachedJarFile)
at com.sun.deploy.util.JarUtil.isBlobSigned(Unknown Source)
at com.sun.deploy.cache.CacheEntry.getJarFile(Unknown Source)
- locked <0x2a1b52b0> (a com.sun.deploy.cache.CacheEntry)
at com.sun.deploy.security.DeployManifestChecker.verify(Unknown Source)
at com.sun.javaws.security.AppPolicy.grantUnrestrictedAccess(Unknown Source)
at com.sun.javaws.security.JNLPSignedResourcesHelper.checkSignedResourcesHelper(Unknown Source)
at com.sun.javaws.security.JNLPSignedResourcesHelper.checkSignedResources(Unknown Source)
at com.sun.javaws.Launcher.prepareResources(Unknown Source)
at com.sun.javaws.Launcher.prepareAllResources(Unknown Source)
at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
at com.sun.javaws.Launcher.launch(Unknown Source)
at com.sun.javaws.Main.launchApp(Unknown Source)
at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
at com.sun.javaws.Main.access$000(Unknown Source)
at com.sun.javaws.Main$1.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
"Finalizer":
at com.sun.deploy.cache.CacheEntry.storageFilesExist(Unknown Source)
- waiting to lock <0x2a1b52b0> (a com.sun.deploy.cache.CacheEntry)
at com.sun.deploy.cache.MemoryCache.validateResource(Unknown Source)
at com.sun.deploy.cache.MemoryCache.getLoadedResource(Unknown Source)
- locked <0x29e65428> (a java.lang.Class for com.sun.deploy.cache.MemoryCache)
at com.sun.deploy.cache.CachedJarFile.isReferencedTo(Unknown Source)
at com.sun.deploy.cache.CachedJarFile.close(Unknown Source)
at java.util.zip.ZipFile.finalize(Unknown Source)
at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
at java.lang.ref.Finalizer.runFinalizer(Unknown Source)
at java.lang.ref.Finalizer.access$100(Unknown Source)
at java.lang.ref.Finalizer$FinalizerThread.run(Unknown Source)
Found 1 deadlock.
如果您發現JVM/JRE/JDK錯誤,請將其報告給Oracle。 http://www.oracle.com/technetwork/java/javase/bugreports-140511.html –
我打算這樣做,但oracle對bug報告的反饋只是「謝謝」。沒有反應,而且一旦他們「接受」它甚至不能看到該錯誤。我打算再捅一點,看看我能否在7月40日到7月45日之間找到他們在deploy.jar中更改的內容。 –
該錯誤來自於在7u40和7u45之間的deploy.jar的CacheEntry類中的getJarFile()中添加的新代碼塊。我現在提交了這個bug。幸運的是,也許他們會公開bug。 (你在聽Larry嗎?) –