Howdy,
I don't think enough of us tested it well enough to vote.  I'd be very
very surprised if 4.1.30 is not a stable quality build.

Yoav Shapira
Millennium ChemInformatics


>-----Original Message-----
>From: Tim Funk [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, February 10, 2004 4:13 PM
>To: Tomcat Users List
>Subject: Re: Starting tomcat when the DB is down
>
>4.1.30 went for a stable vote. I guess it didn't get enough +1's for a
>stable
>vote. I should be stable enough.
>
>Worst case, just rip out JDBCRealm.class from server/lib/catalina.jar
(in
>4.1.30) and place it into the server/classes dir (in the correct nested
>directory)
>
>-Tim
>
>Bill Faulk wrote:
>> Hi Tim,
>>
>> Sorry, I forgot to mention I'm running 4.1.29. I didn't see 4.1.30 on
>> the Tomcat downloads page but I do see a 4.1.30-alpha dated
25-Jan-2004
>> on the downloads site. Also, I need to continue this in Tomcat-4 for
now
>> rather than 5.
>>
>> I'll be moving to production soon so I'm a bit leery of anything with
>> "alpha" in the name. I can try it and put 4.1.29 back if there's a
>> problem. Thanks for the info!
>>
>> ---
>> Bill Faulk
>>
>>
>>
>> -----Original Message-----
>> From: Tim Funk [mailto:[EMAIL PROTECTED]
>> Sent: Tuesday, February 10, 2004 1:08 PM
>> To: Tomcat Users List
>> Subject: Re: Starting tomcat when the DB is down
>>
>>
>> Which version? I thought 4.1.30 was patched to allow tomcat to start
up
>> even
>> if the database realm connect failed.
>>
>> -Tim
>>
>> Bill Faulk wrote:
>>
>>>Hi Folks,
>>>
>>>I am using SQL Server 2000 via the JDBC realm with forms
>>>authentication. If the database is down when tomcat starts there is
an
>>
>>
>>>unhandled LifecycleException generated and tomcat quits. I have the
>>>code in place in my login.jsp to generate a "please try again later"
>>>style message (or whatever other message I choose) if the database
>>>goes down after Tomcat starts. However, I want to avoid a "Cannot
find
>>
>>
>>>server" error if the database isn't up.
>>>
>>>If there's a problem with the database I want the alternative to just
>>>having the site be down because Tomcat won't start. Not all of the
>>>site is actually part of the protected content and I want the
>>>unprotected content still available if the DB is down.
>>>
>>>Is there supposed to be any way to allow tomcat to start even with an
>>>unreachable database configured? If this is the expected behavior and
>>>is unavoidable then I guess I'll just live with it. Hopefully it
>>>doesn't happen enough to be an issue. :-)
>>>
>>>Catalina.start: LifecycleException:  Exception opening database
>>>connection:
>>>  java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for
>>>JDBC]Error establishing socket.
>>>LifecycleException:  Exception opening database connection:
>>>java.sql.SQLException:
>>> [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing
socket.
>>>        at
>>
>> org.apache.catalina.realm.JDBCRealm.start(JDBCRealm.java:681)
>>
>>>        at
>>>org.apache.catalina.core.StandardContext.start(StandardContext.java:3
>>>... snip ...
>>>Stopping service salesweb
>>>Catalina.stop: LifecycleException:  Coyote connector has not been
>>>started
>>>LifecycleException:  Coyote connector has not been started
>>>        at
>>>org.apache.coyote.tomcat4.CoyoteConnector.stop(CoyoteConnector.java:1
>>>... snip ...
>>>
>>>---
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to