APAR status
Closed as program error.
Error description
Error Message: When a Java program running as a Windows user process tries to use the Attach API to connect to a Java program running as a Windows 7 service, either the service process is absent from the output of AttachProvider.listVirtualMachines() or the attach attempt fails after a long delay. . Stack Trace: N/A .
Local fix
A process running as a service can attach to other Java services owned by the same user.
Problem summary
User processes cannot attach to services and vice versa due to Windows operating system restrictions. Inter-user permission failures can cause corruption of the service's files for attach API. This does not affect other aspects of the service process's operation.
Problem conclusion
This defect will be fixed in: 7.0.0 SR2 6.0.1 SR3 6.0.0 SR11 . The JVM has been fixed to prevent corruption or removal of Attach API files for processes owned by other users. Attachment between user processes and services is not supported; an "AttachNotSupportedException" is thrown if a user process tries to connect to a Java service.
Temporary fix
Comments
APAR Information
APAR number
IV21472
Reported component name
J9 COMMON CODE
Reported component ID
620700127
Reported release
260
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-05-18
Closed date
2012-06-18
Last modified date
2012-06-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
J9 COMMON CODE
Fixed component ID
620700127
Applicable component levels
R260 PSY
UP
R600 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]
Document Information
Modified date:
21 February 2022