Thank you Mark for pointing out the mistake. Following url works
wss://127.0.0.1:8443/Myserver
On 6/16/2012 2:32 PM, Mark Thomas wrote:
On 16/06/2012 20:28, Ravi wrote:
I am able to connect from browser to tomcat using non secure WS connection:
ws://127.0.0.1:8080/Myserver
If I switch the
On 16/06/2012 20:28, Ravi wrote:
>
> I am able to connect from browser to tomcat using non secure WS connection:
> ws://127.0.0.1:8080/Myserver
>
> If I switch the connection string to secure protocol
> ws://127.0.0.1:8080/Myserver
That is neither the correct protocol nor the correct port.
> I
I am able to connect from browser to tomcat using non secure WS connection:
ws://127.0.0.1:8080/Myserver
If I switch the connection string to secure protocol
ws://127.0.0.1:8080/Myserver
I get following error. Can somebody confirm if this has been
implemented/known to work? I am using tomcat 7
On 16/06/2012 12:49, Miguel González Castaños wrote:
Dear all,
We have a webapp under Tomcat 5.5 and jdk 1.5 32 bits under a
virtual machine of 4 Gb and a 64 bits OS.
Some of you have helped me suggesting me to install Javamelody and
sar to monitor the system. Setting up heap dumps
Dear all,
We have a webapp under Tomcat 5.5 and jdk 1.5 32 bits under a
virtual machine of 4 Gb and a 64 bits OS.
Some of you have helped me suggesting me to install Javamelody and
sar to monitor the system. Setting up heap dumps I have managed to see
what was going on with the eclipse
Good morning,
I could need some ideas how to debug a very specific network problem. It
is not directly Tomcat related (more JVM) but maybe you have some pointers.
The situation: We have an application running in Tomcat on two different
servers (TomcatA, TomcatB). Both are doing HTTP calls to
