Re: Long Polling : Tomcat 7.0.50 / 8.0.9

2014-08-28 Thread anurag gupta
Can anyone help regarding this ? Update:-- A simple test on Tomcat 7.0.50/7.0.55 of Longpolling implementation using JAX-RS 2.0 AsyncResponse mechanism. I'm seeing the following the errors in the logs and a lot many CLOSE_WAIT connections, Why ? Exception in thread "http-nio-8080-ClientPoller-0"

Re: Spnego authentication with Tomcat 7.0.55 on Linux 6.5 returns null from request.getremoteUser

2014-08-28 Thread Mark Thomas
On 29/08/2014 03:51, Seshadri, Usha wrote: > Hi, > I am trying to configure spnego out of the box on tomcat 7.0.55 on Linux 6.5, > with directions given at > http://tomcat.apache.org/tomcat-7.0-doc/windows-auth-howto.html. And I am > trying to test the configuration with a sample hello_spnego.js

Spnego authentication with Tomcat 7.0.55 on Linux 6.5 returns null from request.getremoteUser

2014-08-28 Thread Seshadri, Usha
Hi, I am trying to configure spnego out of the box on tomcat 7.0.55 on Linux 6.5, with directions given at http://tomcat.apache.org/tomcat-7.0-doc/windows-auth-howto.html. And I am trying to test the configuration with a sample hello_spnego.jsp file given below. When I load http://localhost:808

Re: Client certificate keystore configuration

2014-08-28 Thread Javier Conti
On 28 August 2014 13:50, Konstantin Kolinko wrote: > 2014-08-28 14:46 GMT+04:00 Javier Conti : > > Hi all, > > > > in a Tomcat 7.0.53 container we are running an application which needs to > > use client certificates to connect to other webservices. > > This is currently done by configuring a key

Re: Websocket Ubuntu 14.04 Apache2 2.4 Tomcat 8.0.9

2014-08-28 Thread PLA
Chris, I added the trailing slash at one point after reading this: http://stackoverflow.com/a/22873747/4046 I took the trailing slash off in one of my iterations. It is now: ProxyPass /RealTime/chatws://LOCALTOMCAT:8080/RealTime/chat ProxyPassReverse /RealTime/chatws://LOCALT

Re: url http://localhost:8443 and https://localhost:8443 does not display anything after configuring the ssl for running tomcat 4.1.18

2014-08-28 Thread Sunny Bhargava
I agree with you that it is a very old version of Tomcat. But configuring the ssl for running tomcat is almost same for all the versions of Tomcat. Can any body has any idea where I am missing any step ? On Thu, Aug 28, 2014 at 1:25 PM, David kerber wrote: > On 8/28/2014 12:55 PM, Sunny Bhargav

Re: Websocket Ubuntu 14.04 Apache2 2.4 Tomcat 8.0.9

2014-08-28 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Patrick, On 8/28/14, 10:54 AM, Patrick L Archibald (PLA) ☮ wrote: > Thanks for the reply. > > I mentioned the AJP connector just for completeness. It doesn't > have anything to do with websockets since I'm using > mod_proxy_wstunnel. > > Good to k

Re: url http://localhost:8443 and https://localhost:8443 does not display anything after configuring the ssl for running tomcat 4.1.18

2014-08-28 Thread David kerber
On 8/28/2014 12:55 PM, Sunny Bhargava wrote: Hi All, I tried to run tomcat 4.1.18 with ssl connection. I followed the instructions in 'ssl configuration HOW-TO'.I changed the server.xml file and mentioned the ssl port as 8443 which is the default. I tried both the links https://localhost:8443 an

Re: Websocket Ubuntu 14.04 Apache2 2.4 Tomcat 8.0.9

2014-08-28 Thread Mark Thomas
On 28/08/2014 17:51, Patrick L Archibald (PLA) ☮ wrote: > Chris, > > Got it working. It was a authentication issue. I assume ws and wss > protocol does not handle authentication. I unprotected /RealTime/chat > and it works. Woohoo! > > So, I guess I'll need to roll a token routine to ensure trans

url http://localhost:8443 and https://localhost:8443 does not display anything after configuring the ssl for running tomcat 4.1.18

2014-08-28 Thread Sunny Bhargava
Hi All, I tried to run tomcat 4.1.18 with ssl connection. I followed the instructions in 'ssl configuration HOW-TO'.I changed the server.xml file and mentioned the ssl port as 8443 which is the default. I tried both the links https://localhost:8443 and http://localhost:8443 but the page does not d

Re: Websocket Ubuntu 14.04 Apache2 2.4 Tomcat 8.0.9

2014-08-28 Thread PLA
Chris, Got it working. It was a authentication issue. I assume ws and wss protocol does not handle authentication. I unprotected /RealTime/chat and it works. Woohoo! So, I guess I'll need to roll a token routine to ensure transactions coming over the unprotected source are legit. Thanks, PLA --

Re: Websocket Ubuntu 14.04 Apache2 2.4 Tomcat 8.0.9

2014-08-28 Thread PLA
Chris, Thanks for the reply. I mentioned the AJP connector just for completeness. It doesn't have anything to do with websockets since I'm using mod_proxy_wstunnel. Good to know that I don't have to go wss between Apache and Tomcat on my internal network. ws and wss in my ProxyPass statements f

Re: Websocket Ubuntu 14.04 Apache2 2.4 Tomcat 8.0.9

2014-08-28 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Patrick, On 8/27/14, 10:12 PM, Patrick L Archibald (PLA) ☮ wrote: > I have a websocket app that works fine on Tomcat. I can not get it > configured to run behind Apache2 web server. Apache2 is configured > with SSL and LDAP basic authentication an

Re: Daily catalina.out has thousands of NPEs

2014-08-28 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 John, On 8/27/14, 9:29 AM, John Smith wrote: >> >> >> >> You haven't really provided any information, here. Please post >> full stack traces. >> >> You might want to do something like catch NPE around the area(s) >> where they are being thrown,

Re: Client certificate keystore configuration

2014-08-28 Thread Konstantin Kolinko
2014-08-28 14:46 GMT+04:00 Javier Conti : > Hi all, > > in a Tomcat 7.0.53 container we are running an application which needs to > use client certificates to connect to other webservices. > This is currently done by configuring a keystore containing keys, > certificates and CAs for the JVM (via co

Client certificate keystore configuration

2014-08-28 Thread Javier Conti
Hi all, in a Tomcat 7.0.53 container we are running an application which needs to use client certificates to connect to other webservices. This is currently done by configuring a keystore containing keys, certificates and CAs for the JVM (via command line arguments) as follows: -Djavax.net.ssl.