Was wondering if anyone else ran into this situation.
We have had instances where the JMX Bridge (jsl.exe) stops on an application but the polling engine it is on shows no signs of any issues with it.
It will show that it is running in the Orion Services Manager and in task manager it will show that it is functioning. This happens when maintenance is performed on an application that needs JMX and also at random times.
I was hoping someone knows of a way to correct this.
You should be getting that in response if you have not already. Feel free to add me via email directly to any communications you have with support.
I had another issue with the jmx bridge stopped but yet I did not get an email stating that it stopped on the poller. This is not the orion poller but one of our additional polling engines. I had closed the previous ticket as it was no longer needed. Is there anything you can suggest to help us monitor this better?
Here is how I have the alert template set to trigger. Before the view below I noticed that I did not have the OM Weblogic application added and I changed the child conditions from component to application status.
If you are looking to determine if the JMX Bridge Service on the poller has stopped, you will need to create an application template to monitor that and set up an alert to notify you. You can even configure an alert action to restart the service. Let me know if you have any difficulty achieving this.
Ok, I am not sure if I can use an existing application monitor and add the node names to it or create a new one specifically for these polling engines and I have no idea what the credentials need to be.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.