Jeffrey C. Baldwin wrote:
Chris,

Thank you for the time. However, I'm still not having any luck...

What's in your Host definition in server.xml, can you post that too?

p


Again, I have the entries in server.xml, so if I restart the Tomcat
service AFTER deploying the app, all is well.  However, I want the
application developers to be able to deploy their app and not have to,
or need to contact me to, restart the Tomcat service.

Thanks again!

In:
/usr/local/tomcat/webapps/mrs2/META-INF

I have:

<?xml version='1.0' encoding='utf-8'?>
<Context docBase="/usr/local/tomcat/webapps/mrs2" path="/mrs2"
workDir="work/Catalina/localhost/mrs2">
  <Resource auth="Container" description="zos DB2 Connection"
name="jdbc/ZosDataSource" type="javax.sql.DataSource"/>
  <Resource auth="Container" description="local DB2 Connection"
name="jdbc/db2ds" type="javax.sql.DataSource"/>
  <Resource auth="Container" description="msql DB Connection"
name="jdbc/mssql2000ds" type="javax.sql.DataSource"/>
  <ResourceParams name="jdbc/ZosDataSource">
    <parameter>
      <name>maxWait</name>
      <value>10000</value>
    </parameter>
    <parameter>
      <name>maxActive</name>
      <value>2</value>
    </parameter>
    <parameter>
      <name>password</name>
      <value>test</value>
    </parameter>
    <parameter>
      <name>url</name>
      <value>jdbc:db2://123.456.789.120:5019/NETSNDB01</value>
    </parameter>
    <parameter>
      <name>driverClassName</name>
      <value>com.ibm.db2.jcc.DB2Driver</value>
    </parameter>
    <parameter>
      <name>maxIdle</name>
      <value>1</value>
    </parameter>
    <parameter>
      <name>username</name>
      <value>TS59MRS</value>
    </parameter>
  </ResourceParams>
  <ResourceParams name="jdbc/db2ds">
    <parameter>
      <name>driverClassName</name>
      <value></value>
    </parameter>
  </ResourceParams>
  <ResourceParams name="jdbc/mssql2000ds">
    <parameter>
      <name>maxWait</name>
      <value>10000</value>
    </parameter>
    <parameter>
      <name>maxActive</name>
      <value>2</value>
    </parameter>
    <parameter>
      <name>password</name>
      <value>password</value>
    </parameter>
    <parameter>
      <name>url</name>
<value>jdbc:jtds:sqlserver://123.456.789.96/mrsuat;user=rreddy;password=password</value>
    </parameter>
    <parameter>
      <name>driverClassName</name>
      <value>net.sourceforge.jtds.jdbc.Driver</value>
    </parameter>
    <parameter>
      <name>maxIdle</name>
      <value>1</value>
    </parameter>
    <parameter>
      <name>username</name>
      <value>rreddy</value>
    </parameter>
  </ResourceParams>
</Context>


Christopher Schultz wrote:
Jeffrey,

Jeffrey C. Baldwin wrote:
I appreciate all the input guys.  I put everything into server.xml and
the application is working great.
You should put that setup into META-INF/context.xml in your webapp
directory (or your WAR file) instead of into server.xml. This is likely
to fix your problem.

So, my question is, I was trying to set it up so that my developers
could just deploy/undeploy/stop/start their apps all through the web,
w/out needing shell access to the server.  Is there a way for them to
restart the Tomcat service through a web interface?
Restart the entire Tomcat service? I don't think Tomcat includes this
capability. You'd have to write your own, separate utility app that can
take down and restart Tomcat.

Is it normal that they should have to restart the entire Tomcat service
for their app to be able to talk to the configured database connections
in server.xml?
No, it's not. Configuring those connections in context.xml will
certainly alleviate this problem.

-chris


---------------------------------------------------------------------
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]



Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to