Posts tagged "warning"

LiveCycle ES: JMXBeanManager warning filling up the server log

Issue

If you are using Adobe LiveCycle ES 8.2.1.2 or 8.2.1.3 you may notice that the server logs are filling up with warnings similar to those shown below:

####<Jan 27, 2010 9:27:11 AM MET> <Warning> <com.adobe.idp.dsc.jmx.JMXBeanManager> <sunc01016> <wl01qalc01> 
<[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> 
<1264580831624> <000000> <Failed to get mbean: server1:Type=AdobeService,Name=DirectoryManagerService,version=1.0. 
This message is a warning only. It should not impact LiveCycle's invocation>

####<Jan 27, 2010 9:27:11 AM MET> <Warning> <com.adobe.idp.dsc.jmx.JMXBeanManager> <sunc01016> <wl01qalc01> 
<[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> 
<1264580831649> <000000> <Failed to get mbean: server1:Type=AdobeService,Name=DirectoryManagerService,version=1.0. 
This message is a warning only. It should not impact LiveCycle's invocation>

####<Jan 27, 2010 9:27:11 AM MET> <Warning> <com.adobe.idp.dsc.jmx.JMXBeanManager> <sunc01016> <wl01qalc01> 
<[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> 
<1264580831694> <000000> <Failed to get mbean: server1:Type=AdobeService,Name=DirectoryManagerService,version=1.0. 
This message is a warning only. It should not impact LiveCycle's invocation>

This warning is harmless and can be ignored, however it can lead to the log files growing exponentially.

Solution

This issue is fixed in LiveCycle ES2 (9.0.0.0). Patches are available for LiveCycle ES SP2 (8.2.1.2) and LiveCycle ES SP3 (8.2.1.3). Contact enterprise support if you require one of these patches to ensure that they are compatible with your environment.

reference: (181407992/2540696)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 8.0/10 (1 vote cast)