Hi Chris,
Thanks for the code,it helped a lot.
Now,using that code on my server machine I found out that
TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA is not even in the defaults ciphers for
jdk1.6.0_39. Isn't this a strange behaviour? Server can only select available
ciphers,I suppose.
Thanks
Chirag
N.s.Karthik wrote:
Hi
Do any body have any Brain storming Ideas for the Following
With single Web Application Installation
Use a Web application for Web based - Browser Interface.
Use the same Web application for exposing the SOAP based - Client
Interface
URL should be same
On 09/10/2013 04:43, Salisbury, Richard W DLA CTR TRANSACTION SERVICES
snip/
We confirmed that Tomcat on server-B is configured to handle port 53309,
from this excerpt from its server.xml:
Connector description=Content Switch HTTPS maxHttpHeaderSize=8192
maxThreads=150
minSpareThreads=25
On Oct 8, 2013, at 9:37 PM, Phuoc Nguyen nhph...@mytrax.co.jp wrote:
Dear tomcat experts,
I am using Tomcat 7. In the manager html interface, there is a column named
version in the list of applications table. I read the document here
On Oct 8, 2013, at 11:03 PM, David Bullock david.bull...@machaira.com.au
wrote:
Please answer at Stackoverflow, and I'll report the results back to this
list:
http://stackoverflow.com/questions/19261727/in-tomcat-juli-do-the-facility-specific-loggers-become-per-webapp-logger-root
If you
Hi Dan
Are you using ROOT#version.war? Cause it should be
ROOT##version.war. Using one # means something different.
I am using ROOT##version.war. I have a typo mistake in the previous email.
My problem is using tomcat-maven-plugin. I don't know how to achieve this
with tomcat-maven-plugin.
My Friend
Let me Explain...
I have an an web based application hosted on a tomcat server (port :8080)
hence to access the application , i have to use the URL as follows
*http://IP:port/APP/index.jsp*
Now if some reason , I have to expose some underlying methods part's of
the same web
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chirag,
On 10/8/13 9:48 PM, Chirag Dewan wrote:
For this particular cipher, the server sends a RST to the client
after the certificate exchange is done. And the handshaking
fails,for the first time only. Second request onwards handshaking
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chirag,
On 10/8/13 9:48 PM, Chirag Dewan wrote:
For this particular cipher, the server sends a RST to the client
after the certificate exchange is done. And the handshaking
fails,for the first time only. Second request onwards handshaking
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 10/8/13 11:03 PM, David Bullock wrote:
Please answer at Stackoverflow, and I'll report the results back to
this list:
Hi,
The first request after the Server is started gets rejected. I am setting my
connector as follows:
IntrospectionUtils.setProperty( this, sslProtocol, TLS );
IntrospectionUtils.setProperty( this, keystore,
keyStoreFile );
N.s.Karthik wrote:
My Friend
Let me Explain...
I have an an web based application hosted on a tomcat server (port :8080)
hence to access the application , i have to use the URL as follows
*http://IP:port/APP/index.jsp*
Now if some reason , I have to expose some underlying methods part's
On 9 October 2013 23:33, Christopher Schultz
ch...@christopherschultz.net wrote:
On 10/8/13 11:03 PM, David Bullock wrote:
Please answer at Stackoverflow, and I'll report the results back to
this list:
Hi i am using tomcat-7 with eclipse kepler. I am getting the following
exception very often. Is there a way to prevent this?
Exception:org.apache.jasper.JasperException: Unable to compile class
for JSPStack
trace:
org.apache.jasper.JasperException: Unable to compile class for JSP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chirag,
On 10/9/13 8:39 AM, Chirag Dewan wrote:
The first request after the Server is started gets rejected.
Interesting.
I am setting my connector as follows:
IntrospectionUtils.setProperty( this, sslProtocol, TLS );
Hi,
I have a wrapper connector class :
public HTTPConnector(int port, String keystoreFile, String password, int
maxKeepAliveRequests, int maxThreads, int connectionTimeout, Logger logger)
throws Exception
{
myLogger = logger;
this.keyStoreFile = keystoreFile;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 10/9/13 9:25 AM, David Bullock wrote:
Nice. Virtual Class Loader seems like a good general solution to
the problem that's been un-necessarily introduced by JULI, as well
as many other similar problems.
Suggestions (especially with
You appear to be missing SSLEnabled=true on your Tomcat connector.
The start-up log messages for that connector will confirm whether that
analysis is correct.
Mark
Thank you Mark.
That was it.
I added SSLEnabled=true to the Tomcat connector, restarted Tomcat and
the Bad Gateway error
Hi All,
I am struggling on SSO configuration using SPENGO mechanism on Tomcat 7.0.42
but not able to get it working. We tried on 7.0.29 version too. Since I get
Login Successful in logs, I assume Kerberos login was successful. Its
SpnegoAuthentication that is failing.
Exception:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chirag,
I have a bunch of non-SSL-related questions about your code.
On 10/9/13 9:59 AM, Chirag Dewan wrote:
I have a wrapper connector class :
public HTTPConnector(int port, String keystoreFile, String
password, int maxKeepAliveRequests, int
Chris,
This is a legacy code and do need some tweaks for sure.
Regarding the issue,for some other Cipher as well the handshaking is failing. I
get a TCP_ZERO_WINDOW in my snoops. And thus resulting in Server sending a RST
to client.
Chirag
Sent from Yahoo! Mail on Android
I am getting this exception very often even when i am using tomcat without
eclipse. Is there a way to avoid this?
*Thanks And Regards,*
Muralidhar Yaragalla.*
(Visit My Blog http://yaragalla.blogspot.in)
*
On Wed, Oct 9, 2013 at 7:00 PM, Muralidhar Yaragalla
java.yaraga...@gmail.com wrote:
On Tue, Oct 8, 2013 at 5:42 AM, Daniel Mikusa dmik...@gopivotal.com wrote:
On Oct 7, 2013, at 11:14 PM, John Rellis john.d.rel...@gmail.com wrote:
Hi,
Tomcat : 7.0.33
Java : 6
JDBC Pool : 1.0.9.3
Grails : 1.3.9
We are running a grails app that is using the tomcat JDBC thread pool, what
On 09/10/2013 16:21, Salisbury, Richard W DLA CTR TRANSACTION SERVICES
wrote:
You appear to be missing SSLEnabled=true on your Tomcat connector.
The start-up log messages for that connector will confirm whether that
analysis is correct.
Mark
Thank you Mark.
That was it.
Happy to help.
Am 2013-10-09 17:28, schrieb Chawla, Rachit:
Hi All,
I am struggling on SSO configuration using SPENGO mechanism on Tomcat 7.0.42
but not able to get it working. We tried on 7.0.29 version too. Since I get
Login Successful in logs, I assume Kerberos login was successful. Its
Hi ,
A small update. The customers client is C++ client,which uses OpenSSL. And I
found that client hello message is SSLv2 protocol. And the server
response(server hello) is a TLSv1 protocol. Is there something I am missing?
Chirag
On Wednesday, 9 October 2013 9:25 PM, Chirag Dewan
26 matches
Mail list logo
