APAR status
Closed as program error.
Error description
WSRR do not output messages to mark the start or end of import operations. In the event of a failure to commit the transaction we would output a message although the absence of an error cannot guarantee that the import was actually initiated.
Local fix
Not applicable
Problem summary
When invoking an import operation from the ServiceRegistry MBean it is possible that the MBean client could disconnect from the MBean before the import process completes. Therefore the client will not receive success or failure messages and will need to look at the logs and what is published in WSRR to establish whether the import was successful.
Problem conclusion
Start and completed messages were added to the MBean so that the SystemOut.log of the server running the import will clearly show when the import process began and when it completed successfully. The messages are: GSR9500I: Import process starting. GSR9501I: Import process completed. Objects created: {0}.
Temporary fix
Comments
APAR Information
APAR number
IZ91250
Reported component name
SERVICE REGISTR
Reported component ID
5724N7200
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-12-20
Closed date
2010-12-29
Last modified date
2010-12-29
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
SERVICE REGISTR
Fixed component ID
5724N7200
Applicable component levels
R700 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSWLGF","label":"WebSphere Service Registry and Repository"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
29 December 2010