Hi all,
I've implemented my own JSSE-Implemantation to do some special
Client-Certificate Validations.
When I sent a Client Certificate with length 0 I get in tomcat 6.0.35 this
Exception:
javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate
This is good because I can check
I ask the same question yes, but i still don't see a way to really do that
nicely through an EndpointConfig
So if somebody has a nice example that gets the Servletcontext that i then
can access in the websocket instance that would be nice
This example should be something different then what is
On Thu, Dec 5, 2013 at 12:18 AM, Konstantin Kolinko
knst.koli...@gmail.com wrote:
Remove the tomcat7-websocket.jar library if you do not need it. This
library (added in 7.0.47, a JSR-356 Java WebSocket 1.0 implementation)
has a ServletContainerInitializer and thus forces Tomcat to perform
Hi Andre,
Finally it worked!!! Thanks a ton.
Below is the setting that I used.
ProxyPassMatch ^/.*\.(gif|jpg|css|png)$! http://localhost:8080/
ProxyPassMatch ^/(.*/servlet/.*)$ http://localhost:8080/$1
ProxyPassMatch ^/(.*\.jsp)$ http://localhost:8080/$1
Now, One final
Hi all,
I've no found that with tomcat 7.0.19 I get a
javax.net.ssl.SSLHandshakeException:
Received fatal alert: bad_certificate
With tomcat 7.0.20 I get the SocketException.
But I don't understand which change in 7.0.20 could cause my problem?
Best regards,
Nancee
2013/12/6 Nancee Riehl
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Thursday, December 05, 2013 5:00 PM
To: Tomcat Users List
Subject: Re: Expire Sesssion
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Crystal,
On 12/5/13, 6:25 PM, Crystal Maramba wrote:
Sorry
I'm sure it *is* some kind of buffer boundary - 16384 is not a random
number ;-) As it happens, I *did* miss some logging (my IDE made it easy to
miss). I have no idea what this exception means though:
SEVERE: Servlet.service() for servlet [jsp] in context with path [] threw
exception
On 06/12/2013 17:33, C. Benson Manica wrote:
I'm sure it *is* some kind of buffer boundary - 16384 is not a
random number ;-) As it happens, I *did* miss some logging (my IDE
made it easy to miss). I have no idea what this exception means
though:
SEVERE: Servlet.service() for servlet [jsp]
Yes, I did mean Apache httpd. I'll be more detailed going forward.
You were right. I found the AJP connector enabled by default, and disabled it.
Thanks again.
-John
Apache is not running and in fact has been uninstalled.
Presumably you mean Apache httpd, not Apache Tomcat (both are from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
C.,
On 12/5/13, 8:06 PM, C. Benson Manica wrote:
I got this back: (apologies if the fixed-width formatting doesn't
come through)
It came through just fine.
16:34:44.954734 IP6 localhost.http-alt localhost.61592: Flags
[P.], seq 1:9001, ack
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 12/6/13, 1:07 PM, Mark Thomas wrote:
On 06/12/2013 17:33, C. Benson Manica wrote:
I'm sure it *is* some kind of buffer boundary - 16384 is not a
random number ;-) As it happens, I *did* miss some logging (my
IDE made it easy to miss).
Hello All,
I am updating the Tomcat JVM configuration to enable java assertions as below:
a. Once tomcat server is configured in local eclipse,I pressed F3 on
it.
b. Click on Open launch configuration link.
c. Go to Arguments tab.
d. Add -ea at the beginning of JVM
On 12/6/2013 3:28 PM, Frank Lugalla wrote:
Hello All,
I am updating the Tomcat JVM configuration to enable java assertions as below:
a. Once tomcat server is configured in local eclipse,I pressed F3 on
it.
b. Click on Open launch configuration link.
c. Go to Arguments
We've been systematically updating our customers from Tomcat 7.0.25 to
7.0.47 this week, after we've determined that our webapp runs just fine
on 47, and 47 runs just fine on AS/400s.
Until now.
We have one customer box on which, if you launch Tomcat 7.0.25, it works
just fine. But if you
2013/12/7 Christopher Schultz ch...@christopherschultz.net:
On 12/6/13, 1:07 PM, Mark Thomas wrote:
On 06/12/2013 17:33, C. Benson Manica wrote:
I'm sure it *is* some kind of buffer boundary - 16384 is not a
random number ;-) As it happens, I *did* miss some logging (my
IDE made it easy to
Johan,
On 12/6/13, 3:53 AM, Johan Compagner wrote:
I ask the same question yes, but i still don't see a way to really
do that nicely through an EndpointConfig
EndpointConfig.getUserProperties().put(ServletContext,
((HttpSession)request.getHttpSession()).getServletContext());
??
It's ugly,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
James,
On 12/6/13, 7:59 PM, James H. H. Lampert wrote:
We've been systematically updating our customers from Tomcat 7.0.25
to 7.0.47 this week, after we've determined that our webapp runs
just fine on 47, and 47 runs just fine on AS/400s.
On Sat, Dec 7, 2013 at 5:48 AM, Christopher Schultz
ch...@christopherschultz.net wrote:
Johan,
On 12/6/13, 3:53 AM, Johan Compagner wrote:
I ask the same question yes, but i still don't see a way to really
do that nicely through an EndpointConfig
18 matches
Mail list logo
