tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tschaef...@acesoft.com
Subject Re: Tomcat on AIX, IBM's JVM. Was Re: [OT] AIX filtering Explorer?
Date Thu, 13 Apr 2006 14:41:34 GMT
tschaeffer@acesoft.com wrote on 04/07/2006 01:28:42 PM:

> "Tremal Naik" <tremalnaik@gmail.com> wrote on 04/07/2006 09:48:53 AM:
> 
> > 2006/4/4, Tremal Naik <tremalnaik@gmail.com>:
> > > I have no problem with Firefox, while IE looks as if it get lost. 
The
> > > secure request does not arrive on the tomcat server. Where did it 
go?
> > 
> > from the Tomcat SSL howto:
> > 
> > http://tomcat.apache.org/tomcat-5.5-doc/ssl-howto.html
> > 
> > "sslProtocol - It is reported that IBM's 1.4.1 implementation of the
> > TLS protocol is not compatible with some popular browsers. In this
> > case, use the value SSL."
> > 
> > Now it works. Alternatively, you can leave the default settings but
> > enable the TLS protocol in IE using Tools -> Internet Options ->
> > Security
> 
> Hi,
> 
> I'm glad you brought this up.  We are using Tomcat on AIX with IBM's 
JVM. 
> We have setup the Connector in the server.xml file, changing the 
algorithm 
> and sslProtocol as the SSL How-to instructed. At first it worked, but 
now 
> it doesn't.  We have not changed the configuration of Tomcat, nor have 
we 
> changed the JDK.  When we connect, we get a notice about the 
certificate, 
> but it does not display the pages: IE tells us that it can't find any 
> pages, and Firefox just shows us blank pages. Here is the Connector 
> configuration:
> 
>     <Connector className="org.apache.coyote.tomcat5.CoyoteConnector"
>                port="8443" 
>                maxThreads="150" minSpareThreads="25" 
maxSpareThreads="75"
>                enableLookups="false" disableUploadTimeout="true"
>                acceptCount="100" debug="0" scheme="https" secure="true"
>                clientAuth="false" sslProtocol="SSL"
>                algorithm="IbmX509"/>
> 
> We don't need a secure connection now, but we will when we install the 
> system for the client. I was hoping to avoid the installation of Apache 
on 
> our clients' systems.  Does anyone know how this could happen?
> 
> Thanks,
> 
> Tim S

FWIW,

I thought I had solved this problem yesterday, because I could connect on 
8080 and 8443, all hunky-dory.  When I started today, however, things were 
still hunky on 8080, but nothing dorey on 8443.  At that point I thought 
it had as much to do with the phases of the moon as anyting else, but with 
debug="99", catalina.out showed this:

WARNING: Error registering contexts
java.util.ConcurrentModificationException
        at java.util.HashMap$HashIterator.nextEntry(HashMap.java(Compiled 
Code))
        at java.util.HashMap$EntryIterator.next(HashMap.java(Compiled 
Code))
        at java.util.HashMap.putAllForCreate(HashMap.java(Compiled Code))
        at java.util.HashMap.clone(HashMap.java:811)
        at 
mx4j.server.DefaultMBeanRepository.clone(DefaultMBeanRepository.java(Inlined 
Compiled Code))
        at 
mx4j.server.MBeanServerImpl.findMBeansByPattern(MBeanServerImpl.java(Compiled 
Code))
        at 
mx4j.server.MBeanServerImpl.queryObjectNames(MBeanServerImpl.java:1568)
        at 
mx4j.server.MBeanServerImpl.queryMBeans(MBeanServerImpl.java:1512)
        at 
org.apache.coyote.tomcat5.MapperListener.init(MapperListener.java:115)
        at 
org.apache.coyote.tomcat5.CoyoteConnector.start(CoyoteConnector.java:1537)
        at 
org.apache.catalina.core.StandardService.start(StandardService.java:489)
        at 
org.apache.catalina.core.StandardServer.start(StandardServer.java:2313)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled

Code))
        at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425)

I had two connectors: were these conflicting? Commenting out the connector 
on 8080 relieved the conflict, and I can now connect on 8443---dory, but 
no hunky.  For now.

Is this a known problem?  I had a redirect on the 8080 port too but 
eliminating that didn't help; only disabling one enables the other.

Tim S.

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
Our company accepts no liability for the content of this email, or for the consequences of
any actions taken on the basis of the information
provided, unless that information is subsequently confirmed in writing.
Any views or opinions presented in this email are solely those of the 
author and do not necessarily represent those of the company.
WARNING: Computer viruses can be transmitted via email.
The recipient should check this email and any attachments for the 
presence of viruses. The company accepts no liability for any damage 
caused by any virus transmitted by this email.
11/29/2003 ACE Software, LLC

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


Mime
View raw message