Re: [JBoss-user] Jetty SSL with 3.2.0RC2

2003-03-07 Thread Neal Sanche
Excellent. I'm glad I put that little bit of information there. It's always good to solve these things. Cheers. -Neal On Friday 07 March 2003 08:47 pm, Frank Morton wrote: > Thanks! You were a huge help. I missed the obvious and was changing > the jboss-service.xml in server/default/conf instea

Re: [JBoss-user] Jetty SSL with 3.2.0RC2

2003-03-07 Thread Frank Morton
Thanks! You were a huge help. I missed the obvious and was changing the jboss-service.xml in server/default/conf instead of the one in server/default/deploy/jbossweb.sar/META-INF. Worked first time after that. Your other info was also helpful. Frank On Friday, March 7, 2003, at 08:33 PM, Neal Sa

Re: [JBoss-user] Jetty SSL with 3.2.0RC2

2003-03-07 Thread Neal Sanche
On Friday 07 March 2003 09:12 am, Frank Morton wrote: > I added the following to jboss-service.xml while running 3.2.0RC2 > under MacOS X: > > > > > 8443 > 5 > 255 > 5 > 2000 > name="Keystore">/usr/local/jboss/server/default/conf/keystore > mypwurd > mypwurd > > > Hey Frank, it really l

Re: [JBoss-user] Jetty SSL with 3.2.0RC2

2003-03-07 Thread Frank Morton
On Friday, March 7, 2003, at 06:19 PM, Jules Gosnell wrote: Frank Morton wrote: I added the following to jboss-service.xml while running 3.2.0RC2 under MacOS X: 8443 5 255 5 2000 /usr/local/jboss/server/default/conf/keystore mypwurd mypwurd Nothing is listening on port 8443 at all. Thi

Re: [JBoss-user] Jetty SSL with 3.2.0RC2

2003-03-07 Thread Jules Gosnell
Frank Morton wrote: I added the following to jboss-service.xml while running 3.2.0RC2 under MacOS X: 8443 5 255 5 2000 /usr/local/jboss/server/default/conf/keystore mypwurd mypwurd Nothing is listening on port 8443 at all. This appears to be ignored. Sounds like you are not running the

[JBoss-user] Jetty SSL with 3.2.0RC2

2003-03-07 Thread Frank Morton
I added the following to jboss-service.xml while running 3.2.0RC2 under MacOS X: 8443 5 255 5 2000 /usr/local/jboss/server/default/conf/keystore mypwurd mypwurd Nothing is listening on port 8443 at all. This appears to be ignored. Ultimately, I want to configure this on a production 3.