[anirbannabrinagmail-com]

Hi Swapna,

Thanks. I got the boot.properties and its having only two entries of username/password in encrypted manner.

Can you/team please look into the patch issue? As one of your early thread clearly have mentioned this ->
One of the reason for the following error can be that the AdminServer and ManagedServers are on different patch set mistakenly.

Thanks,
Anirban

[support-swapna]

Anirban,

Can you please clarify how you installed Weblogic in your current system? Please share the steps you followed.
Also clarify if this is the first time you are working with Weblogic + MyEclipse. Were you able to start Weblogic fine with any of our previous versions of MyEclipse?

–Swapna
Genuitec Support

[anirbannabrinagmail-com]

Weblogic has been provided to us by certain team. Its installed under following path -> C:\Oracle\Middleware.

Earlier we use to have MyEclipse 2017 but now we moved to MyEclipse 2019.

With MyEclipse 2017 we dont have any issue with either of Weblogic
Weblogic 12.1.1.0
Weblogic 12.2.1.0

With MyEclipse 2019 we never able to start any of the following Weblogic server.
Weblogic 12.2.1.0
Weblogic 12.2.1.3

• This reply was modified 5 years, 3 months ago by anirbannabrinagmail-com.

[anirbannabrinagmail-com]

Can someone please look into the issue urgently. There is a serious problem seems in the 2019 version.

[Brian Fernandes]

Anirban,

1) Our team is looking into the problem, but we have been unable to replicate this issue locally, which is why we haven’t been able to make any progress so far. In our tests, both 12.2.1.0 and 12.2.1.3 work just fine with MyEclipse 2019, without any special steps. We are still investigating.

2) You mentioned this worked with MyEclipse 2017 and 12.2.1.0 – is this the same installation of Weblogic that is currently not working with 2019? Or was it another installation, or on another system? Knowing that exactly the same installation does work with 2017 helps remove a lot of variables from our investigation process.

If it is the same installation that works with 2017, one suggestion I have is to change the VM that MyEclipse starts with to a Java 8 VM. Please shutdown MyEclipse and edit the myeclipse.ini file. Change the path of javaw.exe in the -vm argument to a 64-bit Java 8 VM (you could use the one from your 2017 installation). Now save the file, start MyEclipse and try again. This is one big difference between 2017 and 2019, our connector code has not changed in a way that could cause this problem.

3) Has Weblogic been installed as a Windows service? Please check with your installation team.

4) One of the reason for the following error can be that the AdminServer and ManagedServers are on different patch set mistakenly.
This refers to your Weblogic installation and configuration, it is not something we can correct, unfortunately. You will need to check with your installation team.

[anirbannabrinagmail-com]

I don’t have the old installation.
Changing the path to – C:\Program Files (x86)\Java\jre1.8.0_211\bin is giving me error.

Attachments:

You must be logged in to view attached files.

[Brian Fernandes]

Anirban,

You’ve pointed to a 32-bit version of Java instead of a 64-bit version, should work after you correct this.

If that does not work, please let us know, in detail, the answers to #2 and #3.

[anirbannabrinagmail-com]

Ok I correctly pointed where the java is installed.
C:\Program Files\Java\jdk1.8.0_201\bin\javaw.exe

Now eclipse is opening but the same error.

Caused By: weblogic.management.ManagementException: [Management:141266]Parsing failure in config.xml: The following failures occurred:
— Unresolved reference to WebLogicCertPathProvider by [lmydomain]/SecurityConfiguration[lmydomain]/Realms[myrealm]/CertPathBuilder

[anirbannabrinagmail-com]

please let us know, in detail, the answers to #2 and #3.

#2 – Same weblogic installation worked for MyEclipse 2017.
#3 – I am not sure about this. It’s a software package installation.
We give domain name in configuration while adding in eclipse. And we can login to admin console and create further data source connections.

• This reply was modified 5 years, 3 months ago by anirbannabrinagmail-com.

[anirbannabrinagmail-com]

If i don’t add any project in server and just wanted to start without deploying any application from eclipse, still the server not getting started.

<Aug 2, 2019 12:45:48 PM EDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: A MultiException has 11 exceptions. They are:
1. weblogic.management.ManagementException: [Management:141266]Parsing failure in config.xml: The following failures occurred:
— Unresolved reference to WebLogicCertPathProvider by [lmydomain]/SecurityConfiguration[lmydomain]/Realms[myrealm]/CertPathBuilder
.
2. java.lang.IllegalStateException: Unable to perform operation: create on weblogic.management.provider.internal.RuntimeAccessImpl
3. java.lang.IllegalStateException: Unable to perform operation: post construct on weblogic.management.provider.internal.RuntimeAccessService
4. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.t3.srvr.FinalThreadLocalService errors were found
5. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.t3.srvr.FinalThreadLocalService
6. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.t3.srvr.BootService errors were found
7. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.t3.srvr.BootService
8. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.rjvm.RJVMService errors were found
9. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.rjvm.RJVMService
10. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.protocol.ProtocolRegistrationService errors were found
11. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.protocol.ProtocolRegistrationService

A MultiException has 11 exceptions. They are:
1. weblogic.management.ManagementException: [Management:141266]Parsing failure in config.xml: The following failures occurred:
— Unresolved reference to WebLogicCertPathProvider by [lmydomain]/SecurityConfiguration[lmydomain]/Realms[myrealm]/CertPathBuilder
.
2. java.lang.IllegalStateException: Unable to perform operation: create on weblogic.management.provider.internal.RuntimeAccessImpl
3. java.lang.IllegalStateException: Unable to perform operation: post construct on weblogic.management.provider.internal.RuntimeAccessService
4. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.t3.srvr.FinalThreadLocalService errors were found
5. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.t3.srvr.FinalThreadLocalService
6. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.t3.srvr.BootService errors were found
7. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.t3.srvr.BootService
8. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.rjvm.RJVMService errors were found
9. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.rjvm.RJVMService
10. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.protocol.ProtocolRegistrationService errors were found
11. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.protocol.ProtocolRegistrationService

at org.jvnet.hk2.internal.Collector.throwIfErrors(Collector.java:89)
at org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:249)
at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:357)
at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:471)
at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:228)
at org.glassfish.hk2.runlevel.RunLevelContext.findOrCreate(RunLevelContext.java:85)
at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2072)
at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:114)
at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:88)
at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.oneJob(CurrentTaskFuture.java:1213)
at org.glassfish.hk2.runlevel.internal.CurrentTaskFuture$QueueRunner.run(CurrentTaskFuture.java:1144)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused By: weblogic.management.ManagementException: [Management:141266]Parsing failure in config.xml: The following failures occurred:
— Unresolved reference to WebLogicCertPathProvider by [lmydomain]/SecurityConfiguration[lmydomain]/Realms[myrealm]/CertPathBuilder
.
at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:139)

[Author]

Posts