Re: JMSMonitorAdapter Error in AO: A request was sent to a remote peer and a response was not received prior to the specified timeout
Hi Carl, Thanks for your suggestion. We missed out activating AutoPilot-AD-Utilities module over the grid which was causing the issue. As soon as we activated it, we were able to monitor the messages and were able to retrieve correlationid and append to a notepad. So finally the steps for jms monitor adapter which would be listening to weblogic queue are: 1. Configure monitor adapter for the particular queue. 2. Create an AO workflow which would be doing transformation on inputevent context item and writing it to a text file using file adapter. 3. Create a rule by providing the xml from gid.log after Sending event to adapter manager text 4. Export the module to repository. 5. Activate the imported module along with any AutoPilot module being used in the workflow. 6. Post messages in the weblogic after restarting the CDP. 7. Check the text file. Thanks Regards, Saurabh -- View this message in context: http://ars-action-request-system.1.n7.nabble.com/JMSMonitorAdapter-Error-in-AO-A-request-was-sent-to-a-remote-peer-and-a-response-was-not-received-prt-tp112117p112280.html Sent from the ARS (Action Request System) mailing list archive at Nabble.com. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: JMSMonitorAdapter Error in AO: A request was sent to a remote peer and a response was not received prior to the specified timeout
Hi Carl, We have written a rule and provided the xml as given in Grid.log (18 Sep 2013 17:19:04,612 INFO JMSMonitorAdapter : Sending event to adapter manager :) message destinationDistributedReplyToQueue/destination header JMSDeliveryMode2/JMSDeliveryMode JMSExpiration0/JMSExpiration JMSPriority4/JMSPriority JMSMessageIDID:lt;204539.1379501249462.0gt;/JMSMessageID JMSTimestamp1379501249462/JMSTimestamp JMSCorrelationID111/JMSCorrelationID JMSTypeJMS monitor/JMSType JMSRedeliveredfalse/JMSRedelivered character-setISO-8859-2/character-set JMSReplyTo / properties property nameJMSXDeliveryCount/name value type=Integer1/value /property /properties /header body / /message with the rule transformation as string(//destination) = DistributedReplyToQueue We have created a process which would be getting the value of Context item inputevent from rule and fetching the correlationid and writing it to a text file using file adapter. We are able to test the process successfully when we provide the above xml for inputevent but as soon as when we activate the module on the grid we get the following error: Unable to locate configuration for XPath /config/grid/grid/consumer-metrics-map as shown in the grid.log below 18 Sep 2013 17:19:04,612 DEBUG DestinationManager : DistributedReplyToQueue-destination-manager Sending message ID:204539.1379504944543.0 from DistributedReplyToQueue to GRID 18 Sep 2013 17:19:04,612 DEBUG JMSMonitorAdapter : Sending message : messagedestinationDistributedReplyToQueue/destinationheaderJMSDeliveryMode2/JMSDeliveryModeJMSExpiration0/JMSExpirationJMSPriority4/JMSPriorityJMSMessageIDID:lt;204539.1379504944543.0gt;/JMSMessageIDJMSTimestamp1379504944543/JMSTimestampJMSCorrelationID234/JMSCorrelationIDJMSTypeJMS/JMSTypeJMSRedeliveredfalse/JMSRedeliveredcharacter-setISO-8859-2/character-setJMSReplyTo /propertiespropertynameJMSXDeliveryCount/namevalue type=Integer1/value/property/properties/headerbody //message 18 Sep 2013 17:19:04,612 INFO JMSMonitorAdapter : Sending event to adapter manager : message destinationDistributedReplyToQueue/destination header JMSDeliveryMode2/JMSDeliveryMode JMSExpiration0/JMSExpiration JMSPriority4/JMSPriority JMSMessageIDID:lt;204539.1379504944543.0gt;/JMSMessageID JMSTimestamp1379504944543/JMSTimestamp JMSCorrelationID234/JMSCorrelationID JMSTypeJMS/JMSType JMSRedeliveredfalse/JMSRedelivered character-setISO-8859-2/character-set JMSReplyTo / properties property nameJMSXDeliveryCount/name value type=Integer1/value /property /properties /header body / /message 18 Sep 2013 17:19:04,612 DEBUG DestinationManager : DistributedReplyToQueue-destination-manager Average Time To Send Message[Total Msgs: 9]: 0 msecs 18 Sep 2013 17:19:04,612 DEBUG DestinationManager : DistributedReplyToQueue-destination-manager Message count: 1; Completed processing message from DistributedReplyToQueue 18 Sep 2013 17:19:04,612 DEBUG DestinationManager : DistributedReplyToQueue-destination-manager Acknowledging message ID:204539.1379504944543.0 18 Sep 2013 17:19:04,612 INFO AdapterManager : ADAPTER_MANAGER: JMSMonitorAdapter sent event: jms message received event 18 Sep 2013 17:19:04,612 DEBUG AdapterProxy: Attempting to locate a peer with a running Activity Processor instance to process a rules job... 18 Sep 2013 17:19:04,612 DEBUG AdapterProxy: Located a running instance of the Activity Processor on peer CDP1. Attempting to send a submit rules job request... 18 Sep 2013 17:19:04,612 DEBUG AdapterProxy: Successfully submitted rules job to peer CDP1. 18 Sep 2013 17:19:04,612 DEBUG ActivityJob : [Thread 5442] - Setting state from [READY] to [ASSIGNED] for job ID [10e951e181756736:-2b1b6d7c:14130aaf06a:-7ffb2-1379504944612]... 18 Sep 2013 17:19:04,612 DEBUG ActivityJob : [Thread 5442] - Notifying observers of state change from [READY] to [ASSIGNED] for job ID [10e951e181756736:-2b1b6d7c:14130aaf06a:-7ffb2-1379504944612]... 18 Sep 2013 17:19:04,612 DEBUG ArchiveConfiguration : Attempting to load configuration from XPath /config/grid/grid/consumer-metrics-map. 18 Sep 2013 17:19:04,612 INFO AdapterManager : ADAPTER_MANAGER: Submitted event to local Activity Processor. 18 Sep 2013 17:19:04,612 INFO ArchiveConfiguration : Unable to locate configuration for XPath /config/grid/grid/consumer-metrics-map. 18 Sep 2013 17:19:04,612 DEBUG Configuration : Registering Configuration Observer (com.realops.foundation.metrics.GridMetricsCollectOptionConfiguration@26f7ec09). 18 Sep 2013 17:19:04,612 DEBUG DestinationManager : DistributedReplyToQueue-destination-manager MsgCount: 1; Elapsed time: 2656 msecs 18 Sep 2013 17:19:04,612 INFO DestinationManager : Maximum allowed message rate: 10 messages per 1000 msecs 18 Sep 2013 17:19:04,612 DEBUG ArchiveConfiguration : Attempting to load configuration from XPath
Re: JMSMonitorAdapter Error in AO: A request was sent to a remote peer and a response was not received prior to the specified timeout
Hi, I would check out the Process log to see what is says as it appears from the below that there was an event triggered and sent to CDP1 for processing, but I do not see a distinct error message on the failure of the processing. Also, have you restarted your CDP since loading in the Rules/Module - AO can sometimes be touchy on not picking these up correctly until restarted? Kind Regards, Carl Wilson http://www.missingpiecessoftware.com/ -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of MalviyaSaurabh Sent: 18 September 2013 14:21 To: arslist@ARSLIST.ORG Subject: Re: JMSMonitorAdapter Error in AO: A request was sent to a remote peer and a response was not received prior to the specified timeout Hi Carl, We have written a rule and provided the xml as given in Grid.log (18 Sep 2013 17:19:04,612 INFO JMSMonitorAdapter : Sending event to adapter manager :) message destinationDistributedReplyToQueue/destination header JMSDeliveryMode2/JMSDeliveryMode JMSExpiration0/JMSExpiration JMSPriority4/JMSPriority JMSMessageIDID:lt;204539.1379501249462.0gt;/JMSMessageID JMSTimestamp1379501249462/JMSTimestamp JMSCorrelationID111/JMSCorrelationID JMSTypeJMS monitor/JMSType JMSRedeliveredfalse/JMSRedelivered character-setISO-8859-2/character-set JMSReplyTo / properties property nameJMSXDeliveryCount/name value type=Integer1/value /property /properties /header body / /message with the rule transformation as string(//destination) = DistributedReplyToQueue We have created a process which would be getting the value of Context item inputevent from rule and fetching the correlationid and writing it to a text file using file adapter. We are able to test the process successfully when we provide the above xml for inputevent but as soon as when we activate the module on the grid we get the following error: Unable to locate configuration for XPath /config/grid/grid/consumer-metrics-map as shown in the grid.log below 18 Sep 2013 17:19:04,612 DEBUG DestinationManager : DistributedReplyToQueue-destination-manager Sending message ID:204539.1379504944543.0 from DistributedReplyToQueue to GRID 18 Sep 2013 17:19:04,612 DEBUG JMSMonitorAdapter : Sending message : messagedestinationDistributedReplyToQueue/destinationheaderJMSDeliv eryMode2/JMSDeliveryModeJMSExpiration0/JMSExpirationJMSPriority4/J MSPriorityJMSMessageIDID:lt;204539.1379504944543.0gt;/JMSMessageIDJM STimestamp1379504944543/JMSTimestampJMSCorrelationID234/JMSCorrelation IDJMSTypeJMS/JMSTypeJMSRedeliveredfalse/JMSRedeliveredcharacter-se tISO-8859-2/character-setJMSReplyTo /propertiespropertynameJMSXDeliveryCount/namevalue type=Integer1/value/property/properties/headerbody //message 18 Sep 2013 17:19:04,612 INFO JMSMonitorAdapter : Sending event to adapter manager : message destinationDistributedReplyToQueue/destination header JMSDeliveryMode2/JMSDeliveryMode JMSExpiration0/JMSExpiration JMSPriority4/JMSPriority JMSMessageIDID:lt;204539.1379504944543.0gt;/JMSMessageID JMSTimestamp1379504944543/JMSTimestamp JMSCorrelationID234/JMSCorrelationID JMSTypeJMS/JMSType JMSRedeliveredfalse/JMSRedelivered character-setISO-8859-2/character-set JMSReplyTo / properties property nameJMSXDeliveryCount/name value type=Integer1/value /property /properties /header body / /message 18 Sep 2013 17:19:04,612 DEBUG DestinationManager : DistributedReplyToQueue-destination-manager Average Time To Send Message[Total Msgs: 9]: 0 msecs 18 Sep 2013 17:19:04,612 DEBUG DestinationManager : DistributedReplyToQueue-destination-manager Message count: 1; Completed processing message from DistributedReplyToQueue 18 Sep 2013 17:19:04,612 DEBUG DestinationManager : DistributedReplyToQueue-destination-manager Acknowledging message ID:204539.1379504944543.0 18 Sep 2013 17:19:04,612 INFO AdapterManager : ADAPTER_MANAGER: JMSMonitorAdapter sent event: jms message received event 18 Sep 2013 17:19:04,612 DEBUG AdapterProxy: Attempting to locate a peer with a running Activity Processor instance to process a rules job... 18 Sep 2013 17:19:04,612 DEBUG AdapterProxy: Located a running instance of the Activity Processor on peer CDP1. Attempting to send a submit rules job request... 18 Sep 2013 17:19:04,612 DEBUG AdapterProxy: Successfully submitted rules job to peer CDP1. 18 Sep 2013 17:19:04,612 DEBUG ActivityJob : [Thread 5442] - Setting state from [READY] to [ASSIGNED] for job ID [10e951e181756736:-2b1b6d7c:14130aaf06a:-7ffb2-1379504944612]... 18 Sep 2013 17:19:04,612 DEBUG ActivityJob : [Thread 5442] - Notifying observers of state change from [READY] to [ASSIGNED] for job ID [10e951e181756736:-2b1b6d7c:14130aaf06a:-7ffb2-1379504944612]... 18 Sep 2013 17:19:04,612 DEBUG ArchiveConfiguration : Attempting to load configuration from XPath
JMSMonitorAdapter Error in AO: A request was sent to a remote peer and a response was not received prior to the specified timeout
Hi All, We are tyring to monitor a jms queue in Weblogic. We have already created a jms actor adapter and are able to post a message in the queue. We have also successfully configured a jms monitor adapter and the grid status is running in grid manager. We have created a workflow in AO, with the following activities: Start (with inputevent parameter) Append (with adapter name, file name (for writing in text file), line1 statement (xpath from the xml) Stop We have created a rule (which i understand would be monitoring the queue and based on the qualification would be triggering the workflow) Source: string(//source-adapter) Comparitor: = Value: JMSMonitorAdapter (with quotes) The question here is what should i specify in this rule here, and what should we specify in the inputevent when we execute the process. Kindly help. Thanks Regards, Saurabh -- View this message in context: http://ars-action-request-system.1.n7.nabble.com/JMSMonitorAdapter-Error-in-AO-A-request-was-sent-to-a-remote-peer-and-a-response-was-not-received-prt-tp112117.html Sent from the ARS (Action Request System) mailing list archive at Nabble.com. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: JMSMonitorAdapter Error in AO: A request was sent to a remote peer and a response was not received prior to the specified timeout
Hi, A monitor adapter will generate an event (inputevent) that is sent to the Rules of a Module every x (configurable) minutes - this is a pre-determined XML with details of the event. The Rules then evaluate the XML inputevent and based on your condition will trigger your process. You can grab sample of the inputevent from the logs when the adapter is enabled on the Grid for use with processing (samples). You need to configure an input context item called inputevent in your process, which will contain the details from the monitor adapter at run-time - therefore you cannot test your workflow in the Developer Studio unless you have a sample of the inputevent from the logs to pass in as the required context item with testing. You can see what is in the XML of the inputevent from the sample (logs) and therefore create the associated rule to trigger your workflow - again however, you cannot test the rule in the Developer Studio, it needs to be actived on the Grid to run. Kind Regards, Carl Wilson http://www.missingpiecessoftware.com/ -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of MalviyaSaurabh Sent: 13 September 2013 09:34 To: arslist@ARSLIST.ORG Subject: JMSMonitorAdapter Error in AO: A request was sent to a remote peer and a response was not received prior to the specified timeout Hi All, We are tyring to monitor a jms queue in Weblogic. We have already created a jms actor adapter and are able to post a message in the queue. We have also successfully configured a jms monitor adapter and the grid status is running in grid manager. We have created a workflow in AO, with the following activities: Start (with inputevent parameter) Append (with adapter name, file name (for writing in text file), line1 statement (xpath from the xml) Stop We have created a rule (which i understand would be monitoring the queue and based on the qualification would be triggering the workflow) Source: string(//source-adapter) Comparitor: = Value: JMSMonitorAdapter (with quotes) The question here is what should i specify in this rule here, and what should we specify in the inputevent when we execute the process. Kindly help. Thanks Regards, Saurabh -- View this message in context: http://ars-action-request-system.1.n7.nabble.com/JMSMonitorAdapter-Error-in- AO-A-request-was-sent-to-a-remote-peer-and-a-response-was-not-received-prt-t p112117.html Sent from the ARS (Action Request System) mailing list archive at Nabble.com. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: JMSMonitorAdapter Error in AO: A request was sent to a remote peer and a response was not received prior to the specified timeout
Thanks Carl for your reply. Can you please elaborate on what do you mean by sample log. If you are referring to the grid log can you please help me in locating which part of xml should i take from the log. Yes we have enalbed the monitor adapter on the grid and have also configured the rule as well as shown below to trigger the process Source: string(//source-adapter) Comparitor: = Value: JMSMonitorAdapter (with quotes) We have to figure out which part of xml we have to give while defining rules. Thanks Regards, Saurabh -- View this message in context: http://ars-action-request-system.1.n7.nabble.com/JMSMonitorAdapter-Error-in-AO-A-request-was-sent-to-a-remote-peer-and-a-response-was-not-received-prt-tp112117p112119.html Sent from the ARS (Action Request System) mailing list archive at Nabble.com. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: JMSMonitorAdapter Error in AO: A request was sent to a remote peer and a response was not received prior to the specified timeout
Hi, You need to take a sample of the generated inputevent (or use the provided samples by BMC in documentation) - it will be present in the Grid/Process log. It will be XML tagged as such. The Module rules will always take in the inputevent, so you only need to target the part of the inputevent that you want to evaluate - thus you need a sample to perform the XPath on. Source: //source-adapter Comparitor: = Value: JMSMonitorAdapter (or the name of the adapter you setup) Kind Regards, Carl Wilson http://www.missingpiecessoftware.com/ -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of MalviyaSaurabh Sent: 13 September 2013 11:01 To: arslist@ARSLIST.ORG Subject: Re: JMSMonitorAdapter Error in AO: A request was sent to a remote peer and a response was not received prior to the specified timeout Thanks Carl for your reply. Can you please elaborate on what do you mean by sample log. If you are referring to the grid log can you please help me in locating which part of xml should i take from the log. Yes we have enalbed the monitor adapter on the grid and have also configured the rule as well as shown below to trigger the process Source: string(//source-adapter) Comparitor: = Value: JMSMonitorAdapter (with quotes) We have to figure out which part of xml we have to give while defining rules. Thanks Regards, Saurabh -- View this message in context: http://ars-action-request-system.1.n7.nabble.com/JMSMonitorAdapter-Error-in- AO-A-request-was-sent-to-a-remote-peer-and-a-response-was-not-received-prt-t p112117p112119.html Sent from the ARS (Action Request System) mailing list archive at Nabble.com. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
