What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
300.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

After tomcat upgrade HTTP XML/REST Value sensors stopped working

Votes:

0

Your Vote:

Up

Down

We upgraded service desk server that uses apache tomcat to run. Tomcat version changed from 7.0.55 to 7.0.62 After upgrade 2 PRTG HTTP XML/REST Value sensors that monitor that server stopped working. They show "An unexpected error occurred on a send." instead of sensor value. Pade is returning some values in JSON forms, it did not change during upgrade. Same page that is used for sensors if perfectly forking in both ie and chrome. Other sensors, like HTTP Advanced and HTTP SSL Certificate Expiry are working ok too. Need help.

http json resrt tomcat xml

Created on Aug 27, 2015 1:59:14 PM by  polyakov (0) 1



7 Replies

Votes:

0

Your Vote:

Up

Down

What PRTG version are you running?

Created on Aug 28, 2015 9:07:25 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

PRTG Network Monitor 15.3.18.3616+

Created on Aug 28, 2015 9:09:25 AM by  polyakov (0) 1



Votes:

0

Your Vote:

Up

Down

In sensor log there is just this: ... [Trace] Sending request [Error] The underlying connection was closed: An unexpected error occurred on a send. Exitcode custom_error

Created on Aug 28, 2015 10:37:06 AM by  polyakov (0) 1



Votes:

0

Your Vote:

Up

Down

During experiments I figured out that setting senspors parametr "SSLv3 Connection" from default "Force usage of SSLv3" to "Use SSLv3 if available" enables sensor. Its a possible workaround, but what happens with such settings? PRTG uses TLS?

Created on Aug 28, 2015 11:41:11 AM by  polyakov (0) 1



Votes:

0

Your Vote:

Up

Down

Ah, okay - yep, PRTG uses TLS then; 1.2, then 1.1, then 1.0 :)

Created on Aug 28, 2015 12:05:14 PM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

I seems that in tomcat after 7.0.57 SSLv3 is disabled by default https://tomcat.apache.org/tomcat-7.0-doc/changelog.html

But still I have a question: I dont have the TLS option like on screenshot https://kb.paessler.com/en/topic/61045-my-http-sensors-could-not-create-an-ssl-secure-channel-and-are-down-what-can-i-do Is TLS really working in my case?

Created on Aug 28, 2015 12:09:44 PM by  polyakov (0) 1



Votes:

0

Your Vote:

Up

Down

The naming is different for various channels, i.e. sometimes not consistent :)

Created on Aug 28, 2015 12:28:04 PM by  Stephan Linke [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.