Fixes are available
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for AIX
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for IBM i
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Windows
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for HP-UX
7.0.0.5: Java SDK 1.6 SR5 Cumulative Fix for WebSphere Application Server
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Solaris
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Linux
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for IBM i
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for AIX
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Windows
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for HP-UX
7.0.0.7: Java SDK 1.6 SR6 Cumulative Fix for WebSphere Application Server
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Solaris
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Linux
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for IBM i
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Windows
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for AIX
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for HP-UX
7.0.0.9: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Solaris
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Linux
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
When a deployment manager is registered to a job manager, or an admin agent has managed nodes that are registered to a job manager, and the job manager is not running, the SystemErr.log of the deployment manager or admin agent fills up with messages. These messages are written to SystemErr.log at each job manager polling interval (by default, every 30 seconds). Each message is similar the following: [1/13/09 15:05:20:500 EST] 00000029 SystemErr R com.ibm.syncml4j.SyncMLException: E4: (com.ibm.syncml4j.dm.DMSession@616b616b) [1/13/09 15:05:20:515 EST] 00000029 SystemErr R at com.ibm.syncml4j.SyncMLException.makeSyncMLException(Unknown Source) [1/13/09 15:05:20:515 EST] 00000029 SystemErr R at com.ibm.syncml4j.Session.sendMessageEnd(Unknown Source) [1/13/09 15:05:20:515 EST] 00000029 SystemErr R at com.ibm.syncml4j.dm.DMSession.run(Unknown Source) [1/13/09 15:05:20:515 EST] 00000029 SystemErr R at com.ibm.ws.management.system.dmagent.SessionDispatcher.runAs System(SessionDispatcher.java:314) [1/13/09 15:05:20:515 EST] 00000029 SystemErr R at com.ibm.ws.management.system.dmagent.SessionDispatcher.access $000(SessionDispatcher.java:49) [1/13/09 15:05:20:515 EST] 00000029 SystemErr R at com.ibm.ws.management.system.dmagent.SessionDispatcher$1.run( SessionDispatcher.java:277) [1/13/09 15:05:20:515 EST] 00000029 SystemErr R at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextMana gerImpl.java:4359) [1/13/09 15:05:20:515 EST] 00000029 SystemErr R at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(Conte xtManagerImpl.java:4447) [1/13/09 15:05:20:515 EST] 00000029 SystemErr R at com.ibm.ws.security.core.SecurityContext.runAsSystem(Security Context.java:255) [1/13/09 15:05:20:515 EST] 00000029 SystemErr R at com.ibm.ws.management.system.dmagent.SessionDispatcher.run(Se ssionDispatcher.java:283) [1/13/09 15:05:20:515 EST] 00000029 SystemErr R at java.lang.Thread.run(Thread.java:735)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of job manager function in IBM * * WebSphere Application Server V7 * **************************************************************** * PROBLEM DESCRIPTION: Repeated SyncMLExceptions in * * SystemErr.log of the admin agent or * * deployment manager when the job * * manager is not started. * **************************************************************** * RECOMMENDATION: * **************************************************************** As part of normal flexible management function, when a managed node (either a deployment manager or a node managed by an admin agent) is registered with a job manager, the deployment manager or admin agent will periodically attempt to contact the job manager to see if there are any jobs available. The amount of time between attempted contacts is called the polling interval, and is set to 30 seconds by default. The problem occurs when a deployment manager or admin agent is running, but the job manager to which a managed node has been registered has not been started or cannot be contacted. In such cases, an error is written to the SystemErr.log of the admin agent or deployment manager at every polling interval. This can quickly fill the SystemErr.log with repetitive information, especially when the polling interval is short. Here is an example of what is printed to SystemErr.log at each polling interval: [1/13/09 11:55:49:765 EST] 00000032 SystemErr R com.ibm.syncml4j.SyncMLException: E4: (com.ibm.syncml4j.dm.DMSession@33e933e9) [1/13/09 11:55:49:765 EST] 00000032 SystemErr R at com.ibm.syncml4j.SyncMLException.makeSyncMLException(Unknown Source) [1/13/09 11:55:49:765 EST] 00000032 SystemErr R at com.ibm.syncml4j.Session.sendMessageEnd(Unknown Source) [1/13/09 11:55:49:765 EST] 00000032 SystemErr R at com.ibm.syncml4j.dm.DMSession.run(Unknown Source) [1/13/09 11:55:49:765 EST] 00000032 SystemErr R at com.ibm.ws.management.system.dmagent.SessionDispatcher.runAsSyst em(SessionDispatcher.java:311) [1/13/09 11:55:49:765 EST] 00000032 SystemErr R at com.ibm.ws.management.system.dmagent.SessionDispatcher.access$00 0(SessionDispatcher.java:49) [1/13/09 11:55:49:765 EST] 00000032 SystemErr R at com.ibm.ws.management.system.dmagent.SessionDispatcher$1.run(Ses sionDispatcher.java:277) [1/13/09 11:55:49:765 EST] 00000032 SystemErr R at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManager Impl.java:4359) [1/13/09 11:55:49:765 EST] 00000032 SystemErr R at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextM anagerImpl.java:4447) [1/13/09 11:55:49:765 EST] 00000032 SystemErr R at com.ibm.ws.security.core.SecurityContext.runAsSystem(SecurityCon text.java:255) [1/13/09 11:55:49:765 EST] 00000032 SystemErr R at com.ibm.ws.management.system.dmagent.SessionDispatcher.run(Sessi onDispatcher.java:283) [1/13/09 11:55:49:781 EST] 00000032 SystemErr R at java.lang.Thread.run(Thread.java:735)
Problem conclusion
The code was modified to not print any information to the admin agent or deployment manager SystemErr.log when the job manager cannot be contacted during routine polling. Instead, the following new message is periodically printed to the SystemOut.log of the admin agent or deployment manager: CWWSY0427I: The job manager at the MYHOST host and MYPORT port cannot be contacted. In the above message, MYHOST and MYPORT are replaced with the actual hostname and port number of the job manager that cannot be contacted. If there are multiple job managers that are not started or cannot be contacted, a separate message will print periodically for each job manager. If the polling interval is 10 minutes or longer, this message will print to SystemOut.log every polling interval. If the polling interval is less than 10 minutes, the message will print no more often than every 10 minutes. Finally, if trace is enabled on the admin agent or deployment manager (using the specification com.ibm.ws.management.system.dmagent.*=all), then statements showing the failure to communicate with the job manager are still logged at every polling interval to the trace.log file. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.5. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PK84245
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-04-07
Closed date
2009-05-18
Last modified date
2009-05-18
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R700 PSY
UP
Document Information
Modified date:
24 October 2021