Re: SSL with IBM JVM

2010-03-08 Thread Carl

Pid,

I would never hijack a thread.  I started this thread from scratch by 
sending it to the Tomcat users group... is that not what I have done?


Thanks,

Carl

- Original Message - 
From: "Pid" 

To: 
Sent: Monday, March 08, 2010 10:41 AM
Subject: Re: SSL with IBM JVM



On 08/03/2010 12:53, Carl wrote:
I am trying the IBM JVM as a possible cure for the problem 'Tomcat dies 
suddenly'.


A quick recap:

New Dell T110
Slackware 13 - 64 bit
Tomcat 6.0.24

The problem: Tomcat would die suddenly without any entry in any log but 
would leave a core file that indicated the JVM exited with a seg fault.


I had been using the Sun JVM 1.6.0_18.  I have tried 1.6.0_16 (because 
Taylan said his system started a similar problem when he went from 
1.6.0_16 to 1.6.0_18) but not 1.6.0_9 (as Chuck suggested.)


Switched to the latest IBM JVM last Friday.  We run https for all 
applications as we deal mostly with children's data.  About 10% of the 
users experienced problems with accessing the site.  Both IE and Firefox 
caused problems.  Switching them to http eliminated the problem but we 
can not run that way on a regular basis.


Here is what we have done:

IE - IE 6 simply doesn't work.  If IE 8 is installed, removing it and 
reinstalling it seems to allow it to work.  If both IE and Firefox are 
installed, both must be removed and IE 8 installed first followed by 
Firefox seems to allow IE 8 to work.


Firefox - The 'Use TLS 1.0' must be selected but it still doesn't always 
seem to work.  Sometimes (I can't tell you the characteristics), the 
customer must go through the remove and re-install process described 
above.


I believe the remove and re-install process is likely setting some value 
to the one that allows the browser to work.  Does anyone have any idea 
what that setting would be to avoid all this removing/re-installing?


Thanks,

Carl


Carl,

Please don't hijack threads.

When you want to send an email to the list, just editing the subject line 
and the body isn't enough, most email clients leave the headers, (which 
contain the thread information), intact.



p

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: SSL with IBM JVM

2010-03-08 Thread Pid

On 08/03/2010 12:53, Carl wrote:

I am trying the IBM JVM as a possible cure for the problem 'Tomcat dies 
suddenly'.

A quick recap:

New Dell T110
Slackware 13 - 64 bit
Tomcat 6.0.24

The problem: Tomcat would die suddenly without any entry in any log but would 
leave a core file that indicated the JVM exited with a seg fault.

I had been using the Sun JVM 1.6.0_18.  I have tried 1.6.0_16 (because Taylan 
said his system started a similar problem when he went from 1.6.0_16 to 
1.6.0_18) but not 1.6.0_9 (as Chuck suggested.)

Switched to the latest IBM JVM last Friday.  We run https for all applications 
as we deal mostly with children's data.  About 10% of the users experienced 
problems with accessing the site.  Both IE and Firefox caused problems.  
Switching them to http eliminated the problem but we can not run that way on a 
regular basis.

Here is what we have done:

IE - IE 6 simply doesn't work.  If IE 8 is installed, removing it and 
reinstalling it seems to allow it to work.  If both IE and Firefox are 
installed, both must be removed and IE 8 installed first followed by Firefox 
seems to allow IE 8 to work.

Firefox - The 'Use TLS 1.0' must be selected but it still doesn't always seem 
to work.  Sometimes (I can't tell you the characteristics), the customer must 
go through the remove and re-install process described above.

I believe the remove and re-install process is likely setting some value to the 
one that allows the browser to work.  Does anyone have any idea what that 
setting would be to avoid all this removing/re-installing?

Thanks,

Carl


Carl,

Please don't hijack threads.

When you want to send an email to the list, just editing the subject 
line and the body isn't enough, most email clients leave the headers, 
(which contain the thread information), intact.



p

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: SSL with IBM JVM

2010-03-08 Thread Carl

Peter,

Good questions.

I am dumping each request to catalina.out.  I see the expected sequence of 
requests in the log.  The sequence is:


- Create two frames (one for work which covers the entire visible screen and 
one for communicating with the server for printing, applets, etc... an 
applet is started in this second frame which has a width of 0.)


-  In the visible frame, it simply display a 'Loading your settings...' 
message.


- In the invisible frame, it starts the applet process by copying down some 
jars... we never see the requests to copy the jars.


-  Once the jars are copied, we see a request for the actual login page... 
this never happens on the machines that fail to copy the jars.


The fact that it fails to request the jars implies to me (remember, this is 
the edge of my knowledge) the handshake negotiation was not going well and 
never completed so the server couldn't figure out how to communicate with 
the workstation.


We normally have about 80 users from organizations we serve.  About 20% of 
these appear to fail.  I could take them through the process described 
earlier.  However, we have several thousand users who are customers of these 
organizations and we can't really get them to do the uninstall/reinstall, 
hope it will work process.


Hope this clarifies the problem a little bit.

Thanks,

Carl

- Original Message - 
From: "Peter Crowther" 

To: "Tomcat Users List" 
Sent: Monday, March 08, 2010 8:57 AM
Subject: Re: SSL with IBM JVM



On 8 March 2010 12:53, Carl  wrote:


Switched to the latest IBM JVM last Friday.  We run https for all
applications as we deal mostly with children's data.  About 10% of the 
users

experienced problems with accessing the site.  Both IE and Firefox caused
problems.  Switching them to http eliminated the problem but we can not 
run

that way on a regular basis.

Here is what we have done:

IE - IE 6 simply doesn't work.  If IE 8 is installed, removing it and
reinstalling it seems to allow it to work.  If both IE and Firefox are
installed, both must be removed and IE 8 installed first followed by 
Firefox

seems to allow IE 8 to work.

Firefox - The 'Use TLS 1.0' must be selected but it still doesn't always
seem to work.  Sometimes (I can't tell you the characteristics), the
customer must go through the remove and re-install process described 
above.


I believe the remove and re-install process is likely setting some value 
to

the one that allows the browser to work.  Does anyone have any idea what
that setting would be to avoid all this removing/re-installing?

There are a number of possibilities.  Could you give us any more detail 
on
which particular "doesn't work" you're getting?  Browser hangs?  Blank 
pages

returned?  Certificate errors?  Error messages from browsers or server?

- Peter




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: SSL with IBM JVM

2010-03-08 Thread Carl

Chuck,

I have downloaded that JVM and brought it up on a spare server.  We'll find 
out in the next week if it will work.


Thanks,

Carl

- Original Message - 
From: "Caldarale, Charles R" 

To: "Tomcat Users List" 
Sent: Monday, March 08, 2010 8:10 AM
Subject: RE: SSL with IBM JVM



From: Carl [mailto:c...@etrak-plus.com]
Subject: SSL with IBM JVM

I had been using the Sun JVM 1.6.0_18.  I have tried 1.6.0_16 (because
Taylan said his system started a similar problem when he went from
1.6.0_16 to 1.6.0_18) but not 1.6.0_9 (as Chuck suggested.)


Minor correction: there is no 1.6.0_9; 1.6.0_7 (aka 6u7) was the last 
release prior to the major changes introduced in 6u10.  Might be easier 
switching to that than the IBM JVM.


- Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: SSL with IBM JVM

2010-03-08 Thread Carl

Thanks for your reply.

Interesting.  Your suggestion is to front Tomcat with Apache and let Apache 
deal with SSL.  I have tried to let Tomcat do everything, including serving 
html pages.


I am going to try Chuck's idea of Sun's JVM 1.6.0_7 first.

Thanks,

Carl

- Original Message - 
From: "Mikolaj Rydzewski" 

To: "Tomcat Users List" 
Sent: Monday, March 08, 2010 8:26 AM
Subject: Re: SSL with IBM JVM



Carl wrote:
Switched to the latest IBM JVM last Friday.  We run https for all 
applications as we deal mostly with children's data.  About 10% of the 
users experienced problems with accessing the site.  Both IE and Firefox 
caused problems.  Switching them to http eliminated the problem but we 
can not run that way on a regular basis.
Have you considered to use Apache httpd to maintain https traffic? You can 
use AJP or http tomcat connectors then.


--
Mikolaj Rydzewski 


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: SSL with IBM JVM

2010-03-08 Thread Peter Crowther
On 8 March 2010 12:53, Carl  wrote:

> Switched to the latest IBM JVM last Friday.  We run https for all
> applications as we deal mostly with children's data.  About 10% of the users
> experienced problems with accessing the site.  Both IE and Firefox caused
> problems.  Switching them to http eliminated the problem but we can not run
> that way on a regular basis.
>
> Here is what we have done:
>
> IE - IE 6 simply doesn't work.  If IE 8 is installed, removing it and
> reinstalling it seems to allow it to work.  If both IE and Firefox are
> installed, both must be removed and IE 8 installed first followed by Firefox
> seems to allow IE 8 to work.
>
> Firefox - The 'Use TLS 1.0' must be selected but it still doesn't always
> seem to work.  Sometimes (I can't tell you the characteristics), the
> customer must go through the remove and re-install process described above.
>
> I believe the remove and re-install process is likely setting some value to
> the one that allows the browser to work.  Does anyone have any idea what
> that setting would be to avoid all this removing/re-installing?
>
> There are a number of possibilities.  Could you give us any more detail on
which particular "doesn't work" you're getting?  Browser hangs?  Blank pages
returned?  Certificate errors?  Error messages from browsers or server?

- Peter


Re: SSL with IBM JVM

2010-03-08 Thread Mikolaj Rydzewski

Carl wrote:

Switched to the latest IBM JVM last Friday.  We run https for all applications 
as we deal mostly with children's data.  About 10% of the users experienced 
problems with accessing the site.  Both IE and Firefox caused problems.  
Switching them to http eliminated the problem but we can not run that way on a 
regular basis.
Have you considered to use Apache httpd to maintain https traffic? You 
can use AJP or http tomcat connectors then.


--
Mikolaj Rydzewski 


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



RE: SSL with IBM JVM

2010-03-08 Thread Caldarale, Charles R
> From: Carl [mailto:c...@etrak-plus.com]
> Subject: SSL with IBM JVM
> 
> I had been using the Sun JVM 1.6.0_18.  I have tried 1.6.0_16 (because
> Taylan said his system started a similar problem when he went from
> 1.6.0_16 to 1.6.0_18) but not 1.6.0_9 (as Chuck suggested.)

Minor correction: there is no 1.6.0_9; 1.6.0_7 (aka 6u7) was the last release 
prior to the major changes introduced in 6u10.  Might be easier switching to 
that than the IBM JVM.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



SSL with IBM JVM

2010-03-08 Thread Carl
I am trying the IBM JVM as a possible cure for the problem 'Tomcat dies 
suddenly'.

A quick recap:

New Dell T110
Slackware 13 - 64 bit
Tomcat 6.0.24

The problem: Tomcat would die suddenly without any entry in any log but would 
leave a core file that indicated the JVM exited with a seg fault.

I had been using the Sun JVM 1.6.0_18.  I have tried 1.6.0_16 (because Taylan 
said his system started a similar problem when he went from 1.6.0_16 to 
1.6.0_18) but not 1.6.0_9 (as Chuck suggested.)

Switched to the latest IBM JVM last Friday.  We run https for all applications 
as we deal mostly with children's data.  About 10% of the users experienced 
problems with accessing the site.  Both IE and Firefox caused problems.  
Switching them to http eliminated the problem but we can not run that way on a 
regular basis.  

Here is what we have done:

IE - IE 6 simply doesn't work.  If IE 8 is installed, removing it and 
reinstalling it seems to allow it to work.  If both IE and Firefox are 
installed, both must be removed and IE 8 installed first followed by Firefox 
seems to allow IE 8 to work.

Firefox - The 'Use TLS 1.0' must be selected but it still doesn't always seem 
to work.  Sometimes (I can't tell you the characteristics), the customer must 
go through the remove and re-install process described above.

I believe the remove and re-install process is likely setting some value to the 
one that allows the browser to work.  Does anyone have any idea what that 
setting would be to avoid all this removing/re-installing?

Thanks,

Carl