Originally posted by: smcasey

What would cause Launcher to automatically change a system's status to "Paused"? There were no manual changes to the system status. We've never seen this before- using WTX 8.1 on W2003 Server. The system msl logs logging category only LogError- no messages. Nothing in Event Viewer.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: paul.brett

I know of nothing that would cause this automatically. All 'pause' events would be initiated by either the GUI or command line tools, both of which would require prior knowledge of the username/password combo.

I suppose it is possible to generaet a fake 'pause' request and squirt it to the Event Server management port, but it would require a lot of knowledge of the internal format of the command sequences, and still require prior knowledge of the authentication details.

If I had to guess, I would say this 'pause' event was caused by a user or script. It may be possible to trace this back to source with a snoop of the TCP/IP packets to/from the ES management port.

Paul.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: janhess

Is it possible that a GPF could put it in a paused state?
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: paul.brett

A GPF would typically result in an 'Unknown' state.

Paul.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

I've used both the GUI and the command line to generate the PAUSE request, and in both cases the Launcherlog captures the administrator logging in and the fact that the administrator is issuing a Pause request.

Result of test:
"May 12, 2008 11:15:03 AM
The system E:\SRPApps\OperationsSupport\TRACKIT\OperationsSupport-TrackIt.msl has responded with the response System Paused for the request Pause System."

In our production log where the system seems to have Paused on its own:
"May 8, 2008 2:11:40 PM
The system E:\SRPApps\OperationsSupport\TRACKIT\OperationsSupport-TrackIt.msl has responded with the response System Paused for the request ."

In other words, the Launcherlog appears to be unable to determine what the request was that resulted in the system being paused.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

I was going to say; it's possible that the pause is misleading and it's another type of error. Is there nothing in the log files?
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

There is no indication of any "events" in the logs for the individual systems at the time the Launcherlog shows the systems going to the Paused state.

We also went back over our audit logs to see if WTX was processing a lot of requests at the time. Our guess was that WTX might pause the systems if resources were low, but there's no indication that the server was under an out of the ordinary load.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange