robbinma
Newbie
Karma: 1
Posts: 12
|
 |
« on: September 22, 2009, 09:47:48 pm » |
|
Hello,
Is it possible to automatically monitor the incoming continuous queue in Maximo 6.2
I would like to monitor the queue and identify the number of messages with errors?
In my setup the JMS queue uses an ORACLE database as a data store for the queue.
I know that the table sib001 contains records for items in the queue.
I have a situation where a number of incoming messages have errors and the queue stops if there are too many errors.
I would like to have an automatic process that reads the queue and checks the number of messages with errors.
I can then build an alerter that will let me know so I can move/manage the messages as necessary.
Mark
|
|
|
|
|
Logged
|
|
|
|
robbinma
Newbie
Karma: 1
Posts: 12
|
|
« Reply #1 on: October 30, 2009, 04:47:53 pm » |
|
The quick answer to this is no.
There is no way of doing this purely from ORACLE.
The best way to do this is as follows:
Open the Websphere admin front-end.
Looking at each message in turn:
check the creation timestamp
See if that is different from the same day.
Check the timestamp in the error log file.
The timestamp in there needs to be compared with the creation timestamp in the message. If the message is a minute later then it is almost certainly the relevant file/message combination.
|
|
|
|
|
Logged
|
|
|
|
|
Ethen
|
|
« Reply #2 on: February 12, 2010, 09:14:53 am » |
|
one way of doing this maybe writing down an user exit class.. Whenever a queue message is successfully recieved userexit class is executed.. so you can maintain the log of messages who are successfully recieved.
there is one more type of validation class in JMS messages which you can cuztomize and get the list of all the messages sent to the queue..
|
|
|
|
|
Logged
|
regards,
Ethen...
|
|
|
robbinma
Newbie
Karma: 1
Posts: 12
|
|
« Reply #3 on: March 02, 2010, 04:28:42 pm » |
|
Thanks Ethen. I'll have a think about that.
It may not log the messages that fail but we sometimes wonder about messages which are sucessful
|
|
|
|
|
Logged
|
|
|
|
|
Ethen
|
|
« Reply #4 on: March 03, 2010, 04:11:10 am » |
|
you can write an end point exit class in which recieves the response code from external system. if the response code is between 200 to 299 the data was sent successfully. In case of data being sent using HTTP u can extend HTTPExit class and write method
public void processResponseData(int responseCode, String responseMsg, byte msgBodyData[])
{
if(responseCode >= 200 && responseCode <= 299)
//write ur logic here
}
u can do some research on HTTPExit class and how to deploy it since its very large process..
|
|
|
|
|
Logged
|
regards,
Ethen...
|
|
|
|
|
robbinma
Newbie
Karma: 1
Posts: 12
|
 |
« Reply #6 on: June 28, 2010, 10:24:13 am » |
|
Thanks for all the responses.
The final resolution was to look at the root cause (the MEA implementation) and remove the cause of the issues.
After a number of patches the implementation has been tuned so almost all of the problems are prevented from occurring in the first place.
Best regards,
Mark
|
|
|
|
|
Logged
|
|
|
|
|
Ethen
|
|
« Reply #7 on: June 28, 2010, 02:57:08 pm » |
|
you can probably post here what you did.
|
|
|
|
|
Logged
|
regards,
Ethen...
|
|
|
|
