Troubleshooting Details
Problem 1: Cannot find message in Message Monitor
Possible causes:
1. User does not have security for the message channel.
2. The message monitor criteria have filtered out the message.
Problem 2: Messages are being processed in an incorrect order
Possible cause:
1. The Channel has been partitioned, and the resulting subchannels do not match what was assumed for the ordering of the messages.
Problem 3: Message Instance not created
Possible cause:
1. Message is inactive.
Problem 4: Message Instance stays in NEW status.
Possible cause:
1. The pub/sub servers are not booted.
2. The Message Dispatcher has crashed or has been brought down.
3. The Item is not at the top of the queue. All messages with the same Channel/ Subchannel are in the same queue
4. Run appmsgpurgeall.dms
5. Restart PUBSUB processes
6. Force cleanup from the monitor message -> domain status
7. Test your message by routing it through another channel to make sure that it is not an issue with the channel.
Problem 5: Message Instance stays in STARTED status.
Possible cause:
1. All Message Handlers have crashed or have been brought down. Processing will resume when Message handlers come brought back up
2. The Message dispatcher processing the message is on another machine, and either the machine or the application server domain is down.
Problem 6: Message Instance stays in WORKING status.
Possible cause:
1. Message Handler has crashed.
2. The Message Handler processing the message is on another machine, and either the machine or the application server domain is down. The Message handler working on the message is "blocked". The service will timeout, and the Message Dispatcher will retry the message.
Problem 7: Publication Contract not created
Possible cause:
1. Channel routing rules not set up properly.
Problem 8: Publication Contract stays in NEW status
Possible cause:
1. Publication Dispatcher has crashed or has been brought down.
2. Message Channel paused.
3. Node paused
4. Previous message had a status of RETRY, ERROR, or TIMEOUT.
5. The Publication Contract is not at the top of the queue. All Publication Contracts with the same Channel/ Subchannel and subscribing node are in the same queue
Problem 9: Publication Contract stays in RETRY status
Possible cause:
1. The remote node cannot be "pinged" successfully. The publication contract will be processed when the remote node comes back up.
2. No publication handler available, either because it's crashed or it has been brought down.
Problem 10: Publication Contract stays in WORKING status
Possible cause:
1. The publication handler processing the contract is on another machine and either the machine or the domain is down. Processing should continue when the pub/sub system on the other machine comes back up.
Problem 11: Subscription Contract not created.
Possible causes:
1. Message Subscription is inactive.
2. Channel routing rules not set up properly.
Problem 12: For a message published by the local node, subscription contract not created for local node even when Message Subscription is active and "Invoke for local publication" is checked.
Possible cause:
1. The local node was not included in the routing rules for the channel. To subscribe to its own publications, the local node must be included in the channel routing rules.
Problem 13: Subscription Contract stays in NEW status.
Possible causes:
1. The Subscription Dispatcher has crashed or has been brought down.
2. Message Channel Node or System paused.
3. Message Definition not Active.
4. Previous message had a status of RETRY, ERROR, or TIMEOUT.
5. The Subscription contract is not at the top of the queue. All Subscription Contracts with the same Channel/ Subchannel and subscription owner are in the same queue.
Problem 14: All publication Contracts remain in a NEW status.
The queue was blocked from a Publication Contact that was in a status of ERROR from two weeks prior. User did not see the error on the message monitor because he was only looking at today. User entered xx day in and the ERROR publication appeared. Canceled the error and all subsequent publication contracts processed successfully.
Problem: Subscription Contract stays in STARTED status.
Possible causes:
1. The Subscription Handler has crashed or has been brought down.
Problem 15: Subscription Contract stays in WORKING status.
Possible causes:
1. The Subscription Handler has crashed or has been brought down. Check in Application Messaging Gateway Administrator
2. Also look for any errors in App Serv Log
Problem 16: Subscription Contract in ERROR status.
Possible causes:
1. Subscription PeopleCode errors
2. Application data errors.
Problem 17: Subscription Contract in TIMEOUT status.
Possible causes:
1. Subscription PeopleCode errors
2. If the message works sometimes, and sometimes does not this may be a problem with the application server configuration. Tune up your application server min/max values, or reconfigure your domain to a medium or large domain. Also, changing the recycle count for these services from 0 to 25,000 or 10,000 may eliminate this problem.
Problem 18: Unable to ping a node.
Possible causes:
1. The web server for the Gateway is down.
2. The Gateway is not configured properly.
3. The app server for the node is down.
4. Verify url is correct. Copy url in browser address, should see "PeopleSoft <tools release> Application Messaging gateway".
(note: be sure that url in the manage lookup contains // before an ip address or machine name)
NOTE: In PeopleBooks it is stated as "//http://HRMS-01/servlet/psft.pt8.gateway.GatewayServlet"
it should read "http://HRMS-01/servlets/gateway" notice the "//" are missing from the begining and is should read "servlets" not "servlet"
Problem 19: "Access denied, source node not found" message even when source node defined on target database.
Possible cause:
1. Known bug: Message Node caching not working. If a new node is added, reboot appserver.
Problem 20: "Bad Gateway, General Exception error .." message when pinging node.
Possible cause:
1. Check Opid/ Password of node on Configuration Servlet page. (http:// ?/servlet/gateway.administration)
Problem 21: "Access denied. Target and source message node password's do not match." message even when no passwords are defined on target and source nodes.
Possible cause:
1. Target application server has entry in Distinguished Name field in source node's message properties.
2. Target URL must be defined with https:// on target node in source application server.
Problem 21.1: "Access denied. No password defined on source message node."
Possible cause:
In 8.1x Source Message Node properties has entries in 'Password' and 'Re- verify Password'.
Solution: Blank these fileds and ping the source node it worked fine.
Problem 22: "Page cannot be displayed message when attempting to bring up Gateway or gateway Administration page.
Possible cause:
3. Make sure Apache/ Jserv started.
4. Make sure aliases are correct in zone.properties
Problem 23: Ping failed, Application server log message saying cannot find JVM.
Resolution: The application server was on a different machine as the web server. The Sun JRE 1.2 was downloaded on the web server machine. Sun JRE 1.2 was re-downloaded on the application server machine and the setting JavaVM Shared Library in psappsrv.cfg file was set to point to the location of this JRE.
Problem 1: Cannot find message in Message Monitor
Possible causes:
1. User does not have security for the message channel.
2. The message monitor criteria have filtered out the message.
Problem 2: Messages are being processed in an incorrect order
Possible cause:
1. The Channel has been partitioned, and the resulting subchannels do not match what was assumed for the ordering of the messages.
Problem 3: Message Instance not created
Possible cause:
1. Message is inactive.
Problem 4: Message Instance stays in NEW status.
Possible cause:
1. The pub/sub servers are not booted.
2. The Message Dispatcher has crashed or has been brought down.
3. The Item is not at the top of the queue. All messages with the same Channel/ Subchannel are in the same queue
4. Run appmsgpurgeall.dms
5. Restart PUBSUB processes
6. Force cleanup from the monitor message -> domain status
7. Test your message by routing it through another channel to make sure that it is not an issue with the channel.
Problem 5: Message Instance stays in STARTED status.
Possible cause:
1. All Message Handlers have crashed or have been brought down. Processing will resume when Message handlers come brought back up
2. The Message dispatcher processing the message is on another machine, and either the machine or the application server domain is down.
Problem 6: Message Instance stays in WORKING status.
Possible cause:
1. Message Handler has crashed.
2. The Message Handler processing the message is on another machine, and either the machine or the application server domain is down. The Message handler working on the message is "blocked". The service will timeout, and the Message Dispatcher will retry the message.
Problem 7: Publication Contract not created
Possible cause:
1. Channel routing rules not set up properly.
Problem 8: Publication Contract stays in NEW status
Possible cause:
1. Publication Dispatcher has crashed or has been brought down.
2. Message Channel paused.
3. Node paused
4. Previous message had a status of RETRY, ERROR, or TIMEOUT.
5. The Publication Contract is not at the top of the queue. All Publication Contracts with the same Channel/ Subchannel and subscribing node are in the same queue
Problem 9: Publication Contract stays in RETRY status
Possible cause:
1. The remote node cannot be "pinged" successfully. The publication contract will be processed when the remote node comes back up.
2. No publication handler available, either because it's crashed or it has been brought down.
Problem 10: Publication Contract stays in WORKING status
Possible cause:
1. The publication handler processing the contract is on another machine and either the machine or the domain is down. Processing should continue when the pub/sub system on the other machine comes back up.
Problem 11: Subscription Contract not created.
Possible causes:
1. Message Subscription is inactive.
2. Channel routing rules not set up properly.
Problem 12: For a message published by the local node, subscription contract not created for local node even when Message Subscription is active and "Invoke for local publication" is checked.
Possible cause:
1. The local node was not included in the routing rules for the channel. To subscribe to its own publications, the local node must be included in the channel routing rules.
Problem 13: Subscription Contract stays in NEW status.
Possible causes:
1. The Subscription Dispatcher has crashed or has been brought down.
2. Message Channel Node or System paused.
3. Message Definition not Active.
4. Previous message had a status of RETRY, ERROR, or TIMEOUT.
5. The Subscription contract is not at the top of the queue. All Subscription Contracts with the same Channel/ Subchannel and subscription owner are in the same queue.
Problem 14: All publication Contracts remain in a NEW status.
The queue was blocked from a Publication Contact that was in a status of ERROR from two weeks prior. User did not see the error on the message monitor because he was only looking at today. User entered xx day in and the ERROR publication appeared. Canceled the error and all subsequent publication contracts processed successfully.
Problem: Subscription Contract stays in STARTED status.
Possible causes:
1. The Subscription Handler has crashed or has been brought down.
Problem 15: Subscription Contract stays in WORKING status.
Possible causes:
1. The Subscription Handler has crashed or has been brought down. Check in Application Messaging Gateway Administrator
2. Also look for any errors in App Serv Log
Problem 16: Subscription Contract in ERROR status.
Possible causes:
1. Subscription PeopleCode errors
2. Application data errors.
Problem 17: Subscription Contract in TIMEOUT status.
Possible causes:
1. Subscription PeopleCode errors
2. If the message works sometimes, and sometimes does not this may be a problem with the application server configuration. Tune up your application server min/max values, or reconfigure your domain to a medium or large domain. Also, changing the recycle count for these services from 0 to 25,000 or 10,000 may eliminate this problem.
Problem 18: Unable to ping a node.
Possible causes:
1. The web server for the Gateway is down.
2. The Gateway is not configured properly.
3. The app server for the node is down.
4. Verify url is correct. Copy url in browser address, should see "PeopleSoft <tools release> Application Messaging gateway".
(note: be sure that url in the manage lookup contains // before an ip address or machine name)
NOTE: In PeopleBooks it is stated as "//http://HRMS-01/servlet/psft.pt8.gateway.GatewayServlet"
it should read "http://HRMS-01/servlets/gateway" notice the "//" are missing from the begining and is should read "servlets" not "servlet"
Problem 19: "Access denied, source node not found" message even when source node defined on target database.
Possible cause:
1. Known bug: Message Node caching not working. If a new node is added, reboot appserver.
Problem 20: "Bad Gateway, General Exception error .." message when pinging node.
Possible cause:
1. Check Opid/ Password of node on Configuration Servlet page. (http:// ?/servlet/gateway.administration)
Problem 21: "Access denied. Target and source message node password's do not match." message even when no passwords are defined on target and source nodes.
Possible cause:
1. Target application server has entry in Distinguished Name field in source node's message properties.
2. Target URL must be defined with https:// on target node in source application server.
Problem 21.1: "Access denied. No password defined on source message node."
Possible cause:
In 8.1x Source Message Node properties has entries in 'Password' and 'Re- verify Password'.
Solution: Blank these fileds and ping the source node it worked fine.
Problem 22: "Page cannot be displayed message when attempting to bring up Gateway or gateway Administration page.
Possible cause:
3. Make sure Apache/ Jserv started.
4. Make sure aliases are correct in zone.properties
Problem 23: Ping failed, Application server log message saying cannot find JVM.
Resolution: The application server was on a different machine as the web server. The Sun JRE 1.2 was downloaded on the web server machine. Sun JRE 1.2 was re-downloaded on the application server machine and the setting JavaVM Shared Library in psappsrv.cfg file was set to point to the location of this JRE.
No comments:
Post a Comment