Re: Tomcat 7 SSL activation on AS/400? (Cross-posted to JAVA400)

2012-01-10 Thread James Lampert
Tim Watts wrote: That's a possibility if it's padding the passwords as well. I'm not an AS/400 expert by any means. Is /foo a preallocated file and if so could the problem be with the way it was allocated? The Java-400 list over at Midrange.com is also in on this (albeit not this specific

Re: Tomcat 7 SSL activation on AS/400? (Cross-posted to JAVA400)

2012-01-10 Thread Tim Watts
On Tue, 2012-01-10 at 09:35 -0800, James Lampert wrote: Tim Watts wrote: That's a possibility if it's padding the passwords as well. I'm not an AS/400 expert by any means. Is /foo a preallocated file and if so could the problem be with the way it was allocated? The Java-400 list over

Re: Tomcat 7 SSL activation on AS/400? (Cross-posted to JAVA400)

2012-01-10 Thread James Lampert
Well, using a keystore created on my WinDoze box, and FTP'd to the 400 definitely works: Port 8443 came right up. But that still leaves open the question of why on earth keytool fails to create valid keystores on the 400, whether run from QShell or QP2Term. Inquiring minds want to know.

Re: Tomcat 7 SSL activation on AS/400? (Cross-posted to JAVA400)

2012-01-09 Thread James Lampert
Tim Watts (from the Tomcat Users List) wrote: Can you successfully run this command: keytool -list -keystore {path/to/your/keystore/file} -storepass {passwd-in-server.xml} It gives the same error message. And yes, EBCDIC is the default encoding for AS/400s. The attributes on /foo show that

Re: Tomcat 7 SSL activation on AS/400? (Cross-posted to JAVA400)

2012-01-09 Thread Tim Watts
On Mon, 2012-01-09 at 15:55 -0800, James Lampert wrote: Tim Watts (from the Tomcat Users List) wrote: Can you successfully run this command: keytool -list -keystore {path/to/your/keystore/file} -storepass {passwd-in-server.xml} It gives the same error message. And yes, EBCDIC is the