Bug 899087 (JBEWS-301)

For the no write permission on directroy, can you please specify how to reproduce that warning?

The java.lang.NoClassDefFoundError: org/apache/tomcat/util/buf/ByteChunk  happens when the manager app is clicked, that will be fixed in the next build.

For tomcat 5, when using tcnative, you won't see the warning that the native library is not used. (This is already added to the Release Notes).

#1 you just start tomcat
#2 cool
#3 let me clarify this. I see tcnative working. But when I enable SSL it doesn't actually work and I don't see anything interesting in the log.

I'm investigatind on #3 and will update you in a comment later.

Mladen,

Can you please take a look at 1 and 3?


Thanks,
Permaine

wrt SSL. THis is an issue with RHEL and tomcat5 as well. I verified that SSL works on tomcat 6 but not tomcat 5. Both using the native library. Again, I can't see anything in the tomcat 5 log that indicates an attempt to use SSL although I've changed configuration accordingly.

Sorry, yet another clarification to the issue #3. I am able to access tomcat 5 configured for ssl on port 8443 but only through HTTP, not HTTPS.

Alex,
Can you attach all the configuration you made for openssl, as well as certificates and keys
I suspect this is access problem
can you for start enable read acces to the tomcat group to
/opt/redhat/ews/etc/ssl and all child directories.

Regards

I'll attach requested files today. But it doesn't seem like anything permissions related since tomcat6 is working fine.

tomcat5_server.xml is the server.xml I'm using. I don't do any openssl configuration. It is what postinstall script leaves it. Certificate is a plain self-signed certificate in my home directory that I'm using for testing. It works with tomcat6.

Attachment: Added: tomcat5_server.xml

Attaching the certificates for completeness. 

Attachment: Added: certs.zip

Seems to me you are missing the
SSLEngine="on" inside https connector.
It's a little fifferent setup for Tomcat5 and Tomcat6
Tomcat6 needs SSLEngine="on" in lifecycle listener declaration

Hmm, odd that I didn't noticed one is SSLEnabled and the other SSLEngine. Changing to SSLEngine for tomcat5 shows the following in the logs:

SEVERE: Error initializing endpoint
org.apache.tomcat.jni.Error: This function has not been implemented on this plat
form
        at org.apache.tomcat.jni.SSL.initialize(Native Method)
        at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:635)

I'm not receiving this error, although I can confirm it doesn't work with Tomcat5.
I'll check if it works with stock Tomcat 5.5.

This is really weired issue.
The same native works with Tomcat6 on Solaris, but doesn't work on Tomcat5
However the RHATews generic Linux build works with Tomcat5, so its probably
some initialization issue that manifest only on Solaris/Tomcat5.
Since this was never reported neither on Tomcat dev nor user lists,
I'll need to make some debugging and see what might be the problem.

However, not sure if it's realistic that this issues will be resolved in
timely fashion, so we should either consider this as a missing feature on
Solaris/Tomcat5 or leave it as a bug.

The server.xml configuration was wrong
Tomcat5.5 requires
SSLEngine="on" and SSLEnabled="true" inside Connector tag.
Modified the server.xml on dev66 and it works now.

.cgi?case_id=5559 but it will be worth this to be explained in some EWS documentation as well. I will leave that to the PM team to decide if needed.

Well it is explained in official Tomcat docs. The setup is different for 6.0 and 5.5.
Althought the SSLEnabled is missing from
http://tomcat.apache.org/tomcat-5.5-doc/apr.html
documentation. I'll add that to the ASF site, cause it wasn't updated
when this directive was added.
For 6.0 http://tomcat.apache.org/tomcat-6.0-doc/apr.html
everything is explained correctly.

Now I see my thanks to you, Mladen, were truncated from the original comment? So thank you for your help! :)