Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

Java Agent on WebLogic breaks the application on Windows.


This may be the same problem as a 2012 post titled 'Enabling dynaTrace agents causes "Error creating bean"'. That post indicated that there was a solution, but that solution was not included in the thread. This is my problem. (I removed actual server names and IP numbers)

The newly installed Java agent on WebLogic is causing the overall application to fail. A service on one Windows server is trying to get information from WebLogic on another Windows server. This is part of the error in the requesting service's log:


[{user=OurUserName}]##> - Trying to get Intial Context from:http://OurWebLogicServer:7001 position_in_list:0
####[Platform-Server]-[OurUserName] [2017-08-28 16:25:50.469-0400] [ERROR] [main] [ConnectionInfo ] <##[{user=OurUserName}]##> - Logger.logStackTrace(): exceptionMsg=null
####[Platform-Server]-[OurUserName] [2017-08-28 16:25:50.469-0400] [ERROR] [main] [ConnectionInfo ] <##[{user=OurUserName}]##> - Logger.logStackTrace():----- Begin Stack Trace ------
javax.naming.CommunicationException [Root exception is http://OurWebLogicServer:7001: Bootstrap to OurWebLogicServer/OurIP_Number:7001 failed. It is likely that the remote side declared peer gone on this JVM]


I see in the WebLogic Java agent's log file:

"2017-08-28 15:55:58 [00000cb0] info [java ] Added missing MBeanServer with default domain: DefaultDomain"

The WebLogic Java agent connects to dynaTrace successfully and seems to function OK, but it breaks the overall application.


Dynatrace Pro
Dynatrace Pro

Hi Steve,

Please open a support case and attach a support archive with agent logs. Please also provide the weblogic logs.