Community
Participate
Working Groups
Created attachment 277773 [details] Eclipse configuration Hello, I switched my eclipse from Eclipse Neon.2 (4.6.2) to 4.10.0. I am using the same workspace. I encountered the following problem when started the weblogic server (12.2.1.3) in debug mode. <Mar 6, 2019 10:27:05 AM EET> <Info> <Security> <BEA-090905> <Disabling the CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true.> <Mar 6, 2019 10:27:05 AM EET> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG128 to HMACDRBG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true.> <Mar 6, 2019 10:27:07 AM EET> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 25.121-b13 from Oracle Corporation.> <Mar 6, 2019 10:27:07 AM EET> <Info> <RCM> <BEA-2165021> <"ResourceManagement" is not enabled in this JVM. Enable "ResourceManagement" to use the WebLogic Server "Resource Consumption Management" feature. To enable "ResourceManagement", you must specify the following JVM options in the WebLogic Server instance in which the JVM runs: -XX:+UnlockCommercialFeatures -XX:+ResourceManagement.> <Mar 6, 2019 10:27:07 AM EET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 12.2.1.3.0 Thu Aug 17 13:39:49 PDT 2017 1882952> <Mar 6, 2019 10:27:12 AM EET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING.> <Mar 6, 2019 10:27:12 AM EET> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool.> <Mar 6, 2019 10:27:12 AM EET> <Info> <WorkManager> <BEA-002942> <CMM memory level becomes 0. Setting standby thread pool size to 256.> <Mar 6, 2019 10:27:14,564 AM EET> <Notice> <Log Management> <BEA-170019> <The server log file weblogic.logging.FileStreamHandler instance=1794326905 Current log file=D:\Dev\tools\Maya_JDK8\Oracle_Home\user_projects\domains\MAYA-STB-DMN\servers\AdminServer\logs\AdminServer.log Rotation dir=D:\Dev\tools\Maya_JDK8\Oracle_Home\user_projects\domains\MAYA-STB-DMN\servers\AdminServer\logs is opened. All server side log events will be written to this file.> <Mar 6, 2019 10:27:14,820 AM EET> <Notice> <Security> <BEA-090946> <Security pre-initializing using security realm: myrealm> <Mar 6, 2019 10:27:17,860 AM EET> <Notice> <Security> <BEA-090947> <Security post-initializing using security realm: myrealm> <Mar 6, 2019 10:27:20,345 AM EET> <Notice> <Security> <BEA-090082> <Security initialized using administrative security realm: myrealm> log4j:WARN Continuable parsing error 95 and column 11 log4j:WARN The content of element type "logger" must match "(param*,level?,appender-ref*)". log4j:WARN Continuable parsing error 100 and column 11 log4j:WARN The content of element type "logger" must match "(param*,level?,appender-ref*)". log4j:WARN Continuable parsing error 105 and column 11 log4j:WARN The content of element type "logger" must match "(param*,level?,appender-ref*)". log4j:WARN Continuable parsing error 110 and column 11 log4j:WARN The content of element type "logger" must match "(param*,level?,appender-ref*)". weblogic is trying to login IDM Realm <Mar 6, 2019 10:27:22,441 AM EET> <Critical> <Security> <BEA-090402> <Authentication denied: Boot identity not valid. The user name or password or both from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.> <Mar 6, 2019 10:27:22,478 AM EET> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: A MultiException has 2 exceptions. They are: 1. java.lang.VerifyError: Stack map does not match the one at exception handler 18 Exception Details: Location: weblogic/rmi/internal/BasicRuntimeDescriptor.<init>(Ljava/lang/Class;)V @18: invokestatic Reason: Current frame's flags are not assignable to stack map frame's. Current Frame: bci: @3 flags: { flagThisUninit } locals: { uninitializedThis, 'java/lang/Class' } stack: { 'java/lang/Throwable' } Stackmap Frame: bci: @18 flags: { } locals: { top, 'java/lang/Class' } stack: { 'java/lang/Throwable' } Bytecode: 0x0000000: b805 7d2a 012b 2bb8 0002 04b7 0003 b805 0x0000010: 80b1 b805 80bf Exception Handler Table: bci [3, 18] => handler: 18 Stackmap Table: full_frame(@18,{Top,Object[#35]},{Object[#622]}) 2. java.lang.IllegalStateException: Unable to perform operation: post construct on weblogic.rmi.internal.RMIServerService A MultiException has 2 exceptions. They are: 1. java.lang.VerifyError: Stack map does not match the one at exception handler 18 Exception Details: Location: weblogic/rmi/internal/BasicRuntimeDescriptor.<init>(Ljava/lang/Class;)V @18: invokestatic Reason: Current frame's flags are not assignable to stack map frame's. Current Frame: bci: @3 flags: { flagThisUninit } locals: { uninitializedThis, 'java/lang/Class' } stack: { 'java/lang/Throwable' } Stackmap Frame: bci: @18 flags: { } locals: { top, 'java/lang/Class' } stack: { 'java/lang/Throwable' } Bytecode: 0x0000000: b805 7d2a 012b 2bb8 0002 04b7 0003 b805 0x0000010: 80b1 b805 80bf Exception Handler Table: bci [3, 18] => handler: 18 Stackmap Table: full_frame(@18,{Top,Object[#35]},{Object[#622]}) 2. java.lang.IllegalStateException: Unable to perform operation: post construct on weblogic.rmi.internal.RMIServerService at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:392) at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:487) at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:305) at org.glassfish.hk2.runlevel.RunLevelContext.findOrCreate(RunLevelContext.java:85) at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2126) Truncated. see log file for complete stacktrace Caused By: java.lang.VerifyError: Stack map does not match the one at exception handler 18 Exception Details: Location: weblogic/rmi/internal/BasicRuntimeDescriptor.<init>(Ljava/lang/Class;)V @18: invokestatic Reason: Current frame's flags are not assignable to stack map frame's. Current Frame: bci: @3 flags: { flagThisUninit } locals: { uninitializedThis, 'java/lang/Class' } stack: { 'java/lang/Throwable' } Stackmap Frame: bci: @18 flags: { } locals: { top, 'java/lang/Class' } stack: { 'java/lang/Throwable' } Bytecode: 0x0000000: b805 7d2a 012b 2bb8 0002 04b7 0003 b805 0x0000010: 80b1 b805 80bf Exception Handler Table: bci [3, 18] => handler: 18 Stackmap Table: full_frame(@18,{Top,Object[#35]},{Object[#622]}) at weblogic.rmi.internal.DescriptorManager.createRuntimeDescriptor(DescriptorManager.java:127) at weblogic.rmi.internal.DescriptorManager.getBasicRuntimeDescriptor(DescriptorManager.java:106) at weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManager.java:66) at weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManager.java:51) at weblogic.rmi.internal.OIDManager.makeServerReference(OIDManager.java:192) Truncated. see log file for complete stacktrace > *************************************************************************** The WebLogic Server encountered a critical failure Reason: Stack map does not match the one at exception handler 18 Exception Details: Location: weblogic/rmi/internal/BasicRuntimeDescriptor.<init>(Ljava/lang/Class;)V @18: invokestatic Reason: Current frame's flags are not assignable to stack map frame's. Current Frame: bci: @3 flags: { flagThisUninit } locals: { uninitializedThis, 'java/lang/Class' } stack: { 'java/lang/Throwable' } Stackmap Frame: bci: @18 flags: { } locals: { top, 'java/lang/Class' } stack: { 'java/lang/Throwable' } Bytecode: 0x0000000: b805 7d2a 012b 2bb8 0002 04b7 0003 b805 0x0000010: 80b1 b805 80bf Exception Handler Table: bci [3, 18] => handler: 18 Stackmap Table: full_frame(@18,{Top,Object[#35]},{Object[#622]}) ***************************************************************************
Please try to disable Java -> Debug -> Use advanced source lookup.
New setting did not work.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
