RE: Problems setting up JDBCStore

2004-11-09 Thread Jeremy Nix
Scratch that.  Figured out that there wasn't actually a problem  When
the JDBCStore loads up, it attempts to get a connection which causes the
error message The database connection is null or was found to be
closed. Trying to re-open it..  Maybe a better way of dealing with this
would be to initialize the database connection.  This way, no error
message means a successful startup.


_
Jeremy Nix
Senior Application Developer
Southwest Financial Services, LTD.
(513) 621-6699 x1158
www.sfsltd.com



-Original Message-
From: Jeremy Nix 
Sent: Monday, November 08, 2004 3:40 PM
To: [EMAIL PROTECTED]
Subject: Problems setting up JDBCStore


I'm having a little difficulty setting up the JDBCStore session
persistence layer.  Has anybody had a similar problem?  Or do you see
anyting wrong in my configuration.  Here's the error that I'm getting:

2004-11-08 15:32:11 JDBCStore[/test]: The database connection is null or
was found to be closed. Trying to re-open it.

My server.xml looks like this:

Server port=8005 shutdown=SHUTDOWN debug=0

  !-- Uncomment these entries to enable JMX MBeans support --
  Listener
className=org.apache.catalina.mbeans.ServerLifecycleListener
debug=0/
  Listener
className=org.apache.catalina.mbeans.GlobalResourcesLifecycleListener
debug=0/

!-- Global JNDI resources --
GlobalNamingResources

!-- Editable user database that can also be used by
UserDatabaseRealm to authenticate users --
Resource name=UserDatabase auth=Container

type=org.apache.catalina.UserDatabase
description=User database that
can be updated and saved
/Resource
ResourceParams name=UserDatabase
parameter
namefactory/name

valueorg.apache.catalina.users.MemoryUserDatabaseFactory/value
/parameter
parameter
namepathname/name
valueconf/tomcat-users.xml/value
/parameter
/ResourceParams
/GlobalNamingResources
  
!-- Define the Tomcat Stand-Alone Service --
Service name=Catalina

!-- Define a non-SSL Coyote HTTP/1.1 Connector on port
80 --
Connector
className=org.apache.coyote.tomcat5.CoyoteConnector
address=10.0.2.130 port=80 
maxThreads=150
minSpareThreads=25 maxSpareThreads=75
enableLookups=false
redirectPort=443 acceptCount=100
debug=0 scheme=http
connectionTimeout=2
disableUploadTimeout=true /

!-- Define a SSL Coyote HTTP/1.1 Connector on port 443
--
Connector
className=org.apache.coyote.tomcat5.CoyoteConnector
address=10.0.2.130 port=443 
maxThreads=150
minSpareThreads=25 maxSpareThreads=75
enableLookups=false
redirectPort=443 acceptCount=100
debug=0 scheme=https
secure=true connectionTimeout=2
disableUploadTimeout=true
Factory
className=org.apache.coyote.tomcat5.CoyoteServerSocketFactory
clientAuth=false
protocol=TLS

keystoreFile=certs/phoenix.keystore
keystorePass=alpine /
/Connector

!-- Define the top level container in our container
hierarchy --
Engine name=Standalone defaultHost=10.0.2.130
debug=9 jvmRoute=tomcat1

!-- This Realm uses the UserDatabase configured
in the global JNDI
  resources under the key
UserDatabase.  Any edits
  that are performed against this
UserDatabase are immediately
  available for use by the Realm.  --
Realm
className=org.apache.catalina.realm.UserDatabaseRealm
debug=0
resourceName=UserDatabase/

  !-- Global logger unless overridden at lower
levels --
  Logger
className=org.apache.catalina.logger.FileLogger
  directory=logs
prefix=catalina_log. suffix=.txt
  timestamp=true
verbosity=4/

!-- Define the default virtual host --
Host name=10.0.2.130 debug=0
appBase=webapps
unpackWARs=true
autoDeploy=false
   

Re: Problems setting up JDBCStore

2004-11-09 Thread karjera

Laba diena.



Dkojame, kad mums parate.

Js atsista inut isaugota ms duomen bazje.

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