| Summary: | JMX:CurrentEclipseLinkLogLevel attribute of TopLink MBean should be disabled on WebLogic | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Yiping Zhao <yiping.zhao> |
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | eclipselink.orm-inbox, michael.f.obrien |
| Version: | unspecified | Flags: | michael.f.obrien:
documentation+
|
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| URL: | http://wiki.eclipse.org/EclipseLink/DesignDocs/316513 | ||
| Whiteboard: | JMX | ||
| Bug Depends on: | 316513 | ||
| Bug Blocks: | |||
|
Description
Yiping Zhao
>verify on SUN-JConsole/JRockit-JRMC and formal-test-EAR/tutorial-EAR as there are differences between the EAR architecture and possibly the JVM/JMX-viewer combination Scheduled for more in-depth investigation (debug session) and possible inclusion in the next release. Tracking of this issue will be in conjuction with the other 23 open issues on parent bug # 316513 >WebLogic provides the log implementation (different than the other 3 servers)
>Actually we do have control when the DefaultLogger is set to something other than WeblogicEclipseLinkLog <property name="eclipselink.logging.level" value="FINEST"/> <!-- new for 10.3.4.0 http://wiki.eclipse.org/EclipseLink/Examples/JPA/Logging#Server_Logging --> <property name="eclipselink.logging.logger" value="DefaultLogger"/> Logs using the following static logger will still goto WeblogicEclipseLinkLog and not be printed except at level 1 >AbstractSessionLog.getLog().log However, logs using the session logger will be affected by logging level. >getSession().log or >getDatabaseSession().getSessionLog().log We may want to revisit this issue and enable it if the logger is set as a property on the persistence unit. >I see the following logs in the above case [EL Info]: 2010-10-18 16:28:20.9--ServerSession(33006544)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--EclipseLink, version: Eclipse Persistence Services - 2.1.2.qualifier [EL Finer]: 2010-10-18 16:28:20.99--ServerSession(33006544)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--JMX MBeanServer instance found: [weblogic.management.jmx.mbeanserver.WLSMBeanServer@751d58], # of beans: [504], domain: [base_domain] at index: [0]. [EL Finest]: 2010-10-18 16:28:21.0--ServerSession(33006544)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--Registered MBean: org.eclipse.persistence.services.mbean.MBeanDevelopmentServices[TopLink:Name=Development-file_/F_/view_w35e/examples/org.eclipse.persistence.example.jpa.server.weblogic.enterpriseEJB/build/classes/_example,Type=Configuration] [EL Finest]: 2010-10-18 16:28:21.0--ServerSession(33006544)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--Registered MBean: org.eclipse.persistence.services.weblogic.MBeanWebLogicRuntimeServices[TopLink:Name=Session(file_/F_/view_w35e/examples/org.eclipse.persistence.example.jpa.server.weblogic.enterpriseEJB/build/classes/_example)] [EL Finest]: 2010-10-18 16:28:21.0--ServerSession(33006544)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The applicationName for the MBean attached to session [file:/F:/view_w35e/examples/org.eclipse.persistence.example.jpa.server.weblogic.enterpriseEJB/build/classes/_example] is [org.eclipse.persistence.example.jpa.server.weblogic.enterpriseEAR] [EL Finest]: 2010-10-18 16:28:21.0--ServerSession(33006544)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--The moduleName for the MBean attached to session [file:/F:/view_w35e/examples/org.eclipse.persistence.example.jpa.server.weblogic.enterpriseEJB/build/classes/_example] is [enterprise] >Under JRockit JRMC changing the log level is working - goto Attributes tab - change the value of FINEST to FINER for CurrentEclipseLinkLogLevel - goto Operations tab - call printClassesInSession >see no output >do above and return FINER to FINEST - call printClassesInSession >see 2 FINEST logs [EL Finest]: 2010-10-20 11:04:54.135--Thread(Thread[RMI TCP Connection(3)-192.168.0.194,5,RMI Runtime])--org.eclipse.persistence.example.jpa.server.business.Cell [EL Finest]: 2010-10-20 11:04:54.135--Thread(Thread[RMI TCP Connection(3)-192.168.0.194,5,RMI Runtime])--org.eclipse.persistence.example.jpa.server.business.CellAttribute >reraise if this issue is only specific to WebLogic on the SUN JRE (using JConsole) The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |