Re: Unconnected sockets not implemented
hi Mark, i was having problems on configuring ssl on the client.It is ok now.Thanks. Nencho 2007/5/29, Mark Thomas <[EMAIL PROTECTED]>: Nencho Lupanov wrote: > any idea? OS? Tomcat version? Steps you followed to configure SSL? Full stack trace? Mark - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Unconnected sockets not implemented
Hi all, I have tomcat ssl configured ant tried to access it with a jsse client but i get the following error: [java] Exception in thread "main" org.apache.axis2.AxisFault: Unconnected s ockets not implemented; nested exception is: [java] java.net.SocketException: Unconnected sockets not implemented; n any idea? Thanks, Nencho
Re: tomcat webapp startup order
Hi david, the web app do the call to this url itself and not upon a client request. It's the axis2 web app that reads a policy file by reference. Regards, Nencho 2007/5/25, David Delbecq <[EMAIL PROTECTED]>: Or you can delay your intialization code to the first hit to webapplication (if faisable, using a requestfilter for example). At startup, tomcat won't respond to any request until all webapps have been started, so if filter code is reached, all webapps have been started. En l'instant précis du 25/05/07 13:28, Tim Lucia s'exprimait en ces termes: > >> -Original Message- >> From: Nencho Lupanov [mailto:[EMAIL PROTECTED] >> Sent: Friday, May 25, 2007 7:22 AM >> To: Tomcat Users List >> Subject: tomcat webapp startup order >> >> Hi all, >> >> I have vanilla tomcat 5.5 installed. >> I also have axis2 web application deploying on every startup. >> the problem is that the axis2 web app needs to read a url from the same >> tomcat server, only that the server is not yet started >> because in the same moment is yet deploying the axis2 web app. >> is there any way to solve/work-around this problem? >> > > You can start a thread in the ServletContextListener of the 1st application > which allows the application to complete startup from Tomcat's perspective. > Then the thread you started can wait / retry until it can read the 2nd URL > at which time you can have the thread mark the 1st application as available > / ready / whatever. > > Tim > > >> Regards, >> Nencho >> > > > > - > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: tomcat webapp startup order
Hi Tim, That's a pretty good idea, Thanks. 2007/5/25, Tim Lucia <[EMAIL PROTECTED]>: > -Original Message- > From: Nencho Lupanov [mailto:[EMAIL PROTECTED] > Sent: Friday, May 25, 2007 7:22 AM > To: Tomcat Users List > Subject: tomcat webapp startup order > > Hi all, > > I have vanilla tomcat 5.5 installed. > I also have axis2 web application deploying on every startup. > the problem is that the axis2 web app needs to read a url from the same > tomcat server, only that the server is not yet started > because in the same moment is yet deploying the axis2 web app. > is there any way to solve/work-around this problem? You can start a thread in the ServletContextListener of the 1st application which allows the application to complete startup from Tomcat's perspective. Then the thread you started can wait / retry until it can read the 2nd URL at which time you can have the thread mark the 1st application as available / ready / whatever. Tim > > Regards, > Nencho - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
tomcat webapp startup order
Hi all, I have vanilla tomcat 5.5 installed. I also have axis2 web application deploying on every startup. the problem is that the axis2 web app needs to read a url from the same tomcat server, only that the server is not yet started because in the same moment is yet deploying the axis2 web app. is there any way to solve/work-around this problem? Regards, Nencho
Re: Servlet init method invocation
I used load-on-startup and it works fine. Thanks, Nencho 2007/4/11, David Delbecq <[EMAIL PROTECTED]>: init() is called when servlet is initialized. The servlet is, by default (see j2EE specs) initialized when it is first accessed. The 'load-on-startup' element of web.xml can be used to force servlet to be initialized upon webapp startup. The value of this element is a number that specify order, compared to other servlet, in which it is initialized. En l'instant précis du 11/04/07 12:47, Nencho Lupanov s'exprimait en ces termes: > Hi All, > > I am trying to understand, when is the Servlet init() method invoked in > tomcat. > I expected it to be executed after succesfull deployment but it seems > that > it is > executed the first time(only) when request arives. > So, i need to receive a request in order this method to be executed? > Is that configurable?Thanks. > > Nencho > - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Servlet init method invocation
Hi All, I am trying to understand, when is the Servlet init() method invoked in tomcat. I expected it to be executed after succesfull deployment but it seems that it is executed the first time(only) when request arives. So, i need to receive a request in order this method to be executed? Is that configurable?Thanks. Nencho