EclipseLink JMX Warnings

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

EclipseLink JMX Warnings

Dalia Abo Sheasha
Hello,

When running EclipseLink within WebSphere, we see the following warning messages in our logs:

eclipselink   W   [server] Multiple JMX MBeanServer instances [2] exist, we will use the server at index [0] : [com.ibm.ws.management.PlatformMBeanServer@35dbb4c6].
eclipselink   3   [server] JMX MBeanServer instance found: [com.ibm.ws.management.PlatformMBeanServer@35dbb4c6], # of beans: [194], domain: 
eclipselink   W   [server] JMX MBeanServer in use: [com.ibm.ws.management.PlatformMBeanServer@35dbb4c6] from index [0] 
eclipselink   3   [server] JMX MBeanServer instance found: [com.sun.jmx.mbeanserver.JmxMBeanServer@49a1df30], # of beans: [29], domain: [DefaultDomain] at index: [1].
eclipselink   W   [server] JMX MBeanServer in use: [com.sun.jmx.mbeanserver.JmxMBeanServer@49a1df30] from index [1] 

After digging in the code a bit more, I found out that EclipseLink throws a warning during startup if it discovers multiple MBeanServers which is dependent on the server platform running with EclipseLink. From an EclipseLink customer standpoint, they can't do anything about MBeanServer discovery and EclipseLink has logic to choose which MBeanServer to use. Therefore, it seems like these messages should be informational instead of warnings. 

Would anyone object if I change the warnings mentioned above to be informational messages instead of warnings? 

--
Thanks, 
Dalia

_______________________________________________
eclipselink-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
Reply | Threaded
Open this post in threaded view
|

Re: EclipseLink JMX Warnings

Dalia Abo Sheasha
I opened a bug for this change and attached a patch to change the warnings to informational messages. Let me know if anyone has any objections. 

Thanks,
Dalia

On Wed, Jul 26, 2017 at 9:29 AM, Dalia Abo Sheasha <[hidden email]> wrote:
Hello,

When running EclipseLink within WebSphere, we see the following warning messages in our logs:

eclipselink   W   [server] Multiple JMX MBeanServer instances [2] exist, we will use the server at index [0] : [com.ibm.ws.management.PlatformMBeanServer@35dbb4c6].
eclipselink   3   [server] JMX MBeanServer instance found: [com.ibm.ws.management.PlatformMBeanServer@35dbb4c6], # of beans: [194], domain: 
eclipselink   W   [server] JMX MBeanServer in use: [com.ibm.ws.management.PlatformMBeanServer@35dbb4c6] from index [0] 
eclipselink   3   [server] JMX MBeanServer instance found: [com.sun.jmx.mbeanserver.JmxMBeanServer@49a1df30], # of beans: [29], domain: [DefaultDomain] at index: [1].
eclipselink   W   [server] JMX MBeanServer in use: [com.sun.jmx.mbeanserver.JmxMBeanServer@49a1df30] from index [1] 

After digging in the code a bit more, I found out that EclipseLink throws a warning during startup if it discovers multiple MBeanServers which is dependent on the server platform running with EclipseLink. From an EclipseLink customer standpoint, they can't do anything about MBeanServer discovery and EclipseLink has logic to choose which MBeanServer to use. Therefore, it seems like these messages should be informational instead of warnings. 

Would anyone object if I change the warnings mentioned above to be informational messages instead of warnings? 

--
Thanks, 
Dalia



--
Thanks, 
Dalia

_______________________________________________
eclipselink-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
Reply | Threaded
Open this post in threaded view
|

Re: EclipseLink JMX Warnings

Dalia Abo Sheasha
Forgot to include the link (Sorry about that). Here is the bug link: https://bugs.eclipse.org/bugs/show_bug.cgi?id=520316

On Fri, Jul 28, 2017 at 10:12 AM, Dalia Abo Sheasha <[hidden email]> wrote:
I opened a bug for this change and attached a patch to change the warnings to informational messages. Let me know if anyone has any objections. 

Thanks,
Dalia

On Wed, Jul 26, 2017 at 9:29 AM, Dalia Abo Sheasha <[hidden email]> wrote:
Hello,

When running EclipseLink within WebSphere, we see the following warning messages in our logs:

eclipselink   W   [server] Multiple JMX MBeanServer instances [2] exist, we will use the server at index [0] : [com.ibm.ws.management.PlatformMBeanServer@35dbb4c6].
eclipselink   3   [server] JMX MBeanServer instance found: [com.ibm.ws.management.PlatformMBeanServer@35dbb4c6], # of beans: [194], domain: 
eclipselink   W   [server] JMX MBeanServer in use: [com.ibm.ws.management.PlatformMBeanServer@35dbb4c6] from index [0] 
eclipselink   3   [server] JMX MBeanServer instance found: [com.sun.jmx.mbeanserver.JmxMBeanServer@49a1df30], # of beans: [29], domain: [DefaultDomain] at index: [1].
eclipselink   W   [server] JMX MBeanServer in use: [com.sun.jmx.mbeanserver.JmxMBeanServer@49a1df30] from index [1] 

After digging in the code a bit more, I found out that EclipseLink throws a warning during startup if it discovers multiple MBeanServers which is dependent on the server platform running with EclipseLink. From an EclipseLink customer standpoint, they can't do anything about MBeanServer discovery and EclipseLink has logic to choose which MBeanServer to use. Therefore, it seems like these messages should be informational instead of warnings. 

Would anyone object if I change the warnings mentioned above to be informational messages instead of warnings? 

--
Thanks, 
Dalia



--
Thanks, 
Dalia



--
Thanks, 
Dalia

_______________________________________________
eclipselink-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev