[DBCP] Problem when hosting live

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

[DBCP] Problem when hosting live

Martin Grogan-2
Hi all,
Some time ago, I was looking for help with getting started on Connection
Pooling. Well, we got the problem sorted on our development server, but
when we move to a live hosting server (shared Tomcat), it's a different
story. We keep getting a message
    Cannot create JDBC driver of class '' for connect URL 'null'
We have made sure all the JAR files necessary for connection pooling are
available in the CATALINA_HOME/common/lib directory and all the settings
on our web.xml and context.xml files seem to be in order.
If anyone can point us in the right direction, we would be really
grateful. We really need to have the hosting problem sorted out straight
away.
Many thanks,
Martin


 
------------
Martin Grogan
Keizen Software

[hidden email]
www.keizensoftware.com


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [DBCP] Problem when hosting live

Christian Hufgard
Hi Martin,

I saw exactly the same problem two days ago. :) What Tomcat versions
are running on your servers? Our problem was, that we tried to install an
application that was running fine on Tomcat 4.x onto a Tomcat 5.5.x
and missed that the way datasource are configured was changed.

Christian

Saturday, January 7, 2006, 10:58:57 AM, you wrote:

> Hi all,
> Some time ago, I was looking for help with getting started on Connection
> Pooling. Well, we got the problem sorted on our development server, but
> when we move to a live hosting server (shared Tomcat), it's a different
> story. We keep getting a message
>     Cannot create JDBC driver of class '' for connect URL 'null'
> We have made sure all the JAR files necessary for connection pooling are
> available in the CATALINA_HOME/common/lib directory and all the settings
> on our web.xml and context.xml files seem to be in order.
> If anyone can point us in the right direction, we would be really
> grateful. We really need to have the hosting problem sorted out straight
> away.
> Many thanks,
> Martin


 
> ------------
> Martin Grogan
> Keizen Software

> [hidden email]
> www.keizensoftware.com


> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail:
> [hidden email]



--
Best regards,
 Christian                            mailto:[hidden email]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [DBCP] Problem when hosting live

Martin Grogan
Hi Christian,
Our development server is Tomcat 5.0.28, and the hosting comapny uses
Tomcat 5.5.7
However, we don't use Apache as a webserver (just Tomact), and the
hosting company uses Apache 3.3?
If I can provide any other information that might help, please let me know.
Thanks,
Martin


Christian Hufgard wrote:

>Hi Martin,
>
>I saw exactly the same problem two days ago. :) What Tomcat versions
>are running on your servers? Our problem was, that we tried to install an
>application that was running fine on Tomcat 4.x onto a Tomcat 5.5.x
>and missed that the way datasource are configured was changed.
>
>Christian
>
>Saturday, January 7, 2006, 10:58:57 AM, you wrote:
>
>  
>
>>Hi all,
>>Some time ago, I was looking for help with getting started on Connection
>>Pooling. Well, we got the problem sorted on our development server, but
>>when we move to a live hosting server (shared Tomcat), it's a different
>>story. We keep getting a message
>>    Cannot create JDBC driver of class '' for connect URL 'null'
>>We have made sure all the JAR files necessary for connection pooling are
>>available in the CATALINA_HOME/common/lib directory and all the settings
>>on our web.xml and context.xml files seem to be in order.
>>If anyone can point us in the right direction, we would be really
>>grateful. We really need to have the hosting problem sorted out straight
>>away.
>>Many thanks,
>>Martin
>>    
>>
>
>
>
>  
>
>>------------
>>Martin Grogan
>>Keizen Software
>>    
>>
>
>  
>
>>[hidden email]
>>www.keizensoftware.com
>>    
>>
>
>
>  
>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [hidden email]
>>For additional commands, e-mail:
>>[hidden email]
>>    
>>
>
>
>
>  
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re[2]: [DBCP] Problem when hosting live

Christian Hufgard
Think this might be exactly the problem we had.

Tomcat 5.0 uses another way to configure datasources. In this versions
datasources are defined with

 <Resource name="jdbc/TestDB"
               auth="Container"
               type="javax.sql.DataSource"/>

  <ResourceParams name="jdbc/TestDB">
    <parameter>
      <name>factory</name>
      <value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
    </parameter>
    ...
  </ResourceParams>

Tomcat 5.5 uses the following format:

  <Resource name="jdbc/TestDB" auth="Container"
  type="javax.sql.DataSource" .../>

 
Did you check this allready?

Christian

Saturday, January 7, 2006, 12:30:49 PM, you wrote:

> Hi Christian,
> Our development server is Tomcat 5.0.28, and the hosting comapny uses
> Tomcat 5.5.7
> However, we don't use Apache as a webserver (just Tomact), and the
> hosting company uses Apache 3.3?
> If I can provide any other information that might help, please let me know.
> Thanks,
> Martin


> Christian Hufgard wrote:

>>Hi Martin,
>>
>>I saw exactly the same problem two days ago. :) What Tomcat versions
>>are running on your servers? Our problem was, that we tried to install an
>>application that was running fine on Tomcat 4.x onto a Tomcat 5.5.x
>>and missed that the way datasource are configured was changed.
>>
>>Christian
>>
>>Saturday, January 7, 2006, 10:58:57 AM, you wrote:
>>
>>  
>>
>>>Hi all,
>>>Some time ago, I was looking for help with getting started on Connection
>>>Pooling. Well, we got the problem sorted on our development server, but
>>>when we move to a live hosting server (shared Tomcat), it's a different
>>>story. We keep getting a message
>>>    Cannot create JDBC driver of class '' for connect URL 'null'
>>>We have made sure all the JAR files necessary for connection pooling are
>>>available in the CATALINA_HOME/common/lib directory and all the settings
>>>on our web.xml and context.xml files seem to be in order.
>>>If anyone can point us in the right direction, we would be really
>>>grateful. We really need to have the hosting problem sorted out straight
>>>away.
>>>Many thanks,
>>>Martin
>>>    
>>>
>>
>>
>>
>>  
>>
>>>------------
>>>Martin Grogan
>>>Keizen Software
>>>    
>>>
>>
>>  
>>
>>>[hidden email]
>>>www.keizensoftware.com
>>>    
>>>
>>
>>
>>  
>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: [hidden email]
>>>For additional commands, e-mail:
>>>[hidden email]
>>>    
>>>
>>
>>
>>
>>  
>>

> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail:
> [hidden email]



--
Best regards,
 Christian                            mailto:[hidden email]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [DBCP] Problem when hosting live

Martin Grogan
Hi Christian,
In our web.xml file, we have a resource description as follows:

<resource-ref>
    <description>DB Connection</description>
    <res-ref-name>jdbc/pokerdb</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
  </resource-ref>

Is this what we need to change? Will this require other changes in the
context.xml file aswell?
Incidentally, because we are being hosted on a shared Tomcat server,
will changes to our web.xml and context.xml files require a global
tomcat restart, or will it be enough just to restart our context? I
would expect the hosting company not to allow us to restart Tomcat for
more than 100 users every time we need to make a change?
Thanks,
Martin


Christian Hufgard wrote:

>Think this might be exactly the problem we had.
>
>Tomcat 5.0 uses another way to configure datasources. In this versions
>datasources are defined with
>
> <Resource name="jdbc/TestDB"
>               auth="Container"
>               type="javax.sql.DataSource"/>
>
>  <ResourceParams name="jdbc/TestDB">
>    <parameter>
>      <name>factory</name>
>      <value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
>    </parameter>
>    ...
>  </ResourceParams>
>
>Tomcat 5.5 uses the following format:
>
>  <Resource name="jdbc/TestDB" auth="Container"
>  type="javax.sql.DataSource" .../>
>
>  
>Did you check this allready?
>
>Christian
>
>Saturday, January 7, 2006, 12:30:49 PM, you wrote:
>
>  
>
>>Hi Christian,
>>Our development server is Tomcat 5.0.28, and the hosting comapny uses
>>Tomcat 5.5.7
>>However, we don't use Apache as a webserver (just Tomact), and the
>>hosting company uses Apache 3.3?
>>If I can provide any other information that might help, please let me know.
>>Thanks,
>>Martin
>>    
>>
>
>
>  
>
>>Christian Hufgard wrote:
>>    
>>
>
>  
>
>>>Hi Martin,
>>>
>>>I saw exactly the same problem two days ago. :) What Tomcat versions
>>>are running on your servers? Our problem was, that we tried to install an
>>>application that was running fine on Tomcat 4.x onto a Tomcat 5.5.x
>>>and missed that the way datasource are configured was changed.
>>>
>>>Christian
>>>
>>>Saturday, January 7, 2006, 10:58:57 AM, you wrote:
>>>
>>>
>>>
>>>      
>>>
>>>>Hi all,
>>>>Some time ago, I was looking for help with getting started on Connection
>>>>Pooling. Well, we got the problem sorted on our development server, but
>>>>when we move to a live hosting server (shared Tomcat), it's a different
>>>>story. We keep getting a message
>>>>   Cannot create JDBC driver of class '' for connect URL 'null'
>>>>We have made sure all the JAR files necessary for connection pooling are
>>>>available in the CATALINA_HOME/common/lib directory and all the settings
>>>>on our web.xml and context.xml files seem to be in order.
>>>>If anyone can point us in the right direction, we would be really
>>>>grateful. We really need to have the hosting problem sorted out straight
>>>>away.
>>>>Many thanks,
>>>>Martin
>>>>  
>>>>
>>>>        
>>>>
>>>
>>>
>>>
>>>      
>>>
>>>>------------
>>>>Martin Grogan
>>>>Keizen Software
>>>>  
>>>>
>>>>        
>>>>
>>>
>>>
>>>      
>>>
>>>>[hidden email]
>>>>www.keizensoftware.com
>>>>  
>>>>
>>>>        
>>>>
>>>
>>>
>>>      
>>>
>>>>---------------------------------------------------------------------
>>>>To unsubscribe, e-mail: [hidden email]
>>>>For additional commands, e-mail:
>>>>[hidden email]
>>>>  
>>>>
>>>>        
>>>>
>>>
>>>
>>>
>>>      
>>>
>
>  
>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [hidden email]
>>For additional commands, e-mail:
>>[hidden email]
>>    
>>
>
>
>
>  
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re[2]: [DBCP] Problem when hosting live

Christian Hufgard
Hi Martin,

I think first of all, you should change the mailing list. :) This is
more a tomcat-config than a dbcp problem.
The resource-ref in the web.xml seems ok for me. Did you have the
datasource globally defined on your development/testing system?
Restarting your context should be sufficent if you changed your
web.xml/context.xml.

Take a look at
http://tomcat.apache.org/tomcat-5.5-doc/jndi-resources-howto.html
there is a pretty helpful documentation how to set up datasource for
Tomcat 5.5.

Christian

Saturday, January 7, 2006, 1:31:53 PM, you wrote:

> Hi Christian,
> In our web.xml file, we have a resource description as follows:

> <resource-ref>
>     <description>DB Connection</description>
>     <res-ref-name>jdbc/pokerdb</res-ref-name>
>     <res-type>javax.sql.DataSource</res-type>
>     <res-auth>Container</res-auth>
>   </resource-ref>

> Is this what we need to change? Will this require other changes in the
> context.xml file aswell?
> Incidentally, because we are being hosted on a shared Tomcat server,
> will changes to our web.xml and context.xml files require a global
> tomcat restart, or will it be enough just to restart our context? I
> would expect the hosting company not to allow us to restart Tomcat for
> more than 100 users every time we need to make a change?
> Thanks,
> Martin




---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [DBCP] Problem when hosting live

Martin Grogan
Hi Christian,
Apologies for emailing the wrong list. I assumed this would be more a
dbcp-config problem. Is there an alternative list specifically for
dealing with Tomcat config?
Other than the web.xml and context.xml files, we have made no other
changes to the tomcat setup. I will attach a copy of the context.xml
file in the hope that someone might be able to see what is wrong.
If the web.xml and context.xml files appear fine, I really have no idea
where to turn. Unfortunately, the technical people in the hosting
company don't seem to know what's wrong either.
Martin


Christian Hufgard wrote:

>Hi Martin,
>
>I think first of all, you should change the mailing list. :) This is
>more a tomcat-config than a dbcp problem.
>The resource-ref in the web.xml seems ok for me. Did you have the
>datasource globally defined on your development/testing system?
>Restarting your context should be sufficent if you changed your
>web.xml/context.xml.
>
>Take a look at
>http://tomcat.apache.org/tomcat-5.5-doc/jndi-resources-howto.html
>there is a pretty helpful documentation how to set up datasource for
>Tomcat 5.5.
>
>Christian
>
>Saturday, January 7, 2006, 1:31:53 PM, you wrote:
>
>  
>
>>Hi Christian,
>>In our web.xml file, we have a resource description as follows:
>>    
>>
>
>  
>
>><resource-ref>
>>    <description>DB Connection</description>
>>    <res-ref-name>jdbc/pokerdb</res-ref-name>
>>    <res-type>javax.sql.DataSource</res-type>
>>    <res-auth>Container</res-auth>
>>  </resource-ref>
>>    
>>
>
>  
>
>>Is this what we need to change? Will this require other changes in the
>>context.xml file aswell?
>>Incidentally, because we are being hosted on a shared Tomcat server,
>>will changes to our web.xml and context.xml files require a global
>>tomcat restart, or will it be enough just to restart our context? I
>>would expect the hosting company not to allow us to restart Tomcat for
>>more than 100 users every time we need to make a change?
>>Thanks,
>>Martin
>>    
>>
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [hidden email]
>For additional commands, e-mail: [hidden email]
>
>
>
>  
>

<?xml version="1.0" encoding="UTF-8"?>
<Context path="/">
  <Logger className="org.apache.catalina.logger.FileLogger" prefix="poker." suffix=".log" timestamp="true"/>
<Resource name="jdbc/pokerdb" auth="Container" type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/pokerdb">
    <parameter>
        <name>factory</name>
        <value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
    </parameter>

    <!-- Maximum number of dB connections in pool. Make sure you configure your mysqld max_connections large enough to handle all of your db connections. Set to 0 for no limit.  -->
    <parameter>
        <name>maxActive</name>
        <value>30</value>
    </parameter>

    <!-- Maximum number of idle dB connections to retain in pool. Set to -1 for no limit.  See also the DBCP documentation on this and the minEvictableIdleTimeMillis configuration parameter. -->
    <parameter>
        <name>maxIdle</name>
        <value>10</value>
    </parameter>

    <!-- Maximum time to wait for a dB connection to become available in ms, in this example 10 seconds. An Exception is thrown if this timeout is exceeded.  Set to -1 to wait indefinitely. -->
    <parameter>
        <name>maxWait</name>
        <value>10000</value>
    </parameter>

    <!-- MySQL dB username and password for dB connections  -->
    <parameter>
        <name>username</name>
        <value>myuser</value>
    </parameter>
    <parameter>
        <name>password</name>
        <value>mypassword</value>
    </parameter>
       
    <!-- Class name for the official MySQL Connector/J driver -->
    <parameter>
        <name>driverClassName</name>
        <value>com.mysql.jdbc.Driver</value>
    </parameter>
   
    <!-- Force DBCP to remove abandoned connections -->
    <parameter>
        <name>removeAbandoned</name>
        <value>true</value>
    </parameter>
    <parameter>
        <name>removeAbandonedTimeout</name>
        <value>60</value>
    </parameter>
   
    <!-- The JDBC connection url for connecting to your MySQL dB. The autoReconnect=true argument to the url makes sure that the mm.mysql JDBC Driver will automatically reconnect if mysqld closed the connection.  mysqld by default closes idle connections after 8 hours. -->
    <parameter>
        <name>url</name>
        <value>jdbc:mysql://217.114.172.221/pokerhou_pokerdb</value>
    </parameter>
</ResourceParams>
</Context>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re[2]: [DBCP] Problem when hosting live

Christian Hufgard
Hi Martin,

I think no one will punish you for using the wrong list. At least not
me, since I am just a dump user. :) Think there are dedicated mailing
lists for tomcat problems, but I had to look for them...
In your context.xml you set the parameters the way it had to be done
before Tomcat 5.5.

Try these settings in the context.xml:

<Resource name="jdbc/pokerdb"
auth="Container"
type="javax.sql.DataSource"
maxActive="30" maxIdle="10"
maxWait="10000"
username="myuser"
password="mypassword"
driverClassName="com.mysql.jdbc.Driver"
removeAbandoned="true"
removeAbandonedTimeout="60"
url="jdbc:mysql://217.114.172.221/pokerhou_pokerdb" />

Christian


Saturday, January 7, 2006, 2:30:22 PM, you wrote:

> Hi Christian,
> Apologies for emailing the wrong list. I assumed this would be more a
> dbcp-config problem. Is there an alternative list specifically for
> dealing with Tomcat config?
> Other than the web.xml and context.xml files, we have made no other
> changes to the tomcat setup. I will attach a copy of the context.xml
> file in the hope that someone might be able to see what is wrong.
> If the web.xml and context.xml files appear fine, I really have no idea
> where to turn. Unfortunately, the technical people in the hosting
> company don't seem to know what's wrong either.
> Martin


> Christian Hufgard wrote:

>>Hi Martin,
>>
>>I think first of all, you should change the mailing list. :) This is
>>more a tomcat-config than a dbcp problem.
>>The resource-ref in the web.xml seems ok for me. Did you have the
>>datasource globally defined on your development/testing system?
>>Restarting your context should be sufficent if you changed your
>>web.xml/context.xml.
>>
>>Take a look at
>>http://tomcat.apache.org/tomcat-5.5-doc/jndi-resources-howto.html
>>there is a pretty helpful documentation how to set up datasource for
>>Tomcat 5.5.
>>
>>Christian
>>
>>Saturday, January 7, 2006, 1:31:53 PM, you wrote:
>>
>>  
>>
>>>Hi Christian,
>>>In our web.xml file, we have a resource description as follows:
>>>    
>>>
>>
>>  
>>
>>><resource-ref>
>>>    <description>DB Connection</description>
>>>    <res-ref-name>jdbc/pokerdb</res-ref-name>
>>>    <res-type>javax.sql.DataSource</res-type>
>>>    <res-auth>Container</res-auth>
>>>  </resource-ref>
>>>    
>>>
>>
>>  
>>
>>>Is this what we need to change? Will this require other changes in the
>>>context.xml file aswell?
>>>Incidentally, because we are being hosted on a shared Tomcat server,
>>>will changes to our web.xml and context.xml files require a global
>>>tomcat restart, or will it be enough just to restart our context? I
>>>would expect the hosting company not to allow us to restart Tomcat for
>>>more than 100 users every time we need to make a change?
>>>Thanks,
>>>Martin
>>>    
>>>
>>
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [hidden email]
>>For additional commands, e-mail:
>>[hidden email]
>>
>>
>>
>>  
>>



--
Best regards,
 Christian                            mailto:[hidden email]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [DBCP] Problem when hosting live

Martin Grogan
Hi Christian,
Afraid still no luck. I've made the changes to the context.xml file as
you suggested, and reloaded the context on the remote server, but I'm
having the same troubles.
I will try to have another look around the net for possible solutions.
It may be possible that a global tomcat restart is necessary, in which
case a more ideal solution would have to be found, since that would
upset too many other users.
Having asked the remote administrators to review the tomcat logs, they
said that my application was loaded OK, and they couldn't see any error
messages in the logs. I wouldn't even know what kind of log error to
look for.
Thanks,
Martin


Christian Hufgard wrote:

>Hi Martin,
>
>I think no one will punish you for using the wrong list. At least not
>me, since I am just a dump user. :) Think there are dedicated mailing
>lists for tomcat problems, but I had to look for them...
>In your context.xml you set the parameters the way it had to be done
>before Tomcat 5.5.
>
>Try these settings in the context.xml:
>
><Resource name="jdbc/pokerdb"
>auth="Container"
>type="javax.sql.DataSource"
>maxActive="30" maxIdle="10"
>maxWait="10000"
>username="myuser"
>password="mypassword"
>driverClassName="com.mysql.jdbc.Driver"
>removeAbandoned="true"
>removeAbandonedTimeout="60"
>url="jdbc:mysql://217.114.172.221/pokerhou_pokerdb" />
>
>Christian
>
>
>Saturday, January 7, 2006, 2:30:22 PM, you wrote:
>
>  
>
>>Hi Christian,
>>Apologies for emailing the wrong list. I assumed this would be more a
>>dbcp-config problem. Is there an alternative list specifically for
>>dealing with Tomcat config?
>>Other than the web.xml and context.xml files, we have made no other
>>changes to the tomcat setup. I will attach a copy of the context.xml
>>file in the hope that someone might be able to see what is wrong.
>>If the web.xml and context.xml files appear fine, I really have no idea
>>where to turn. Unfortunately, the technical people in the hosting
>>company don't seem to know what's wrong either.
>>Martin
>>    
>>
>
>
>  
>
>>Christian Hufgard wrote:
>>    
>>
>
>  
>
>>>Hi Martin,
>>>
>>>I think first of all, you should change the mailing list. :) This is
>>>more a tomcat-config than a dbcp problem.
>>>The resource-ref in the web.xml seems ok for me. Did you have the
>>>datasource globally defined on your development/testing system?
>>>Restarting your context should be sufficent if you changed your
>>>web.xml/context.xml.
>>>
>>>Take a look at
>>>http://tomcat.apache.org/tomcat-5.5-doc/jndi-resources-howto.html
>>>there is a pretty helpful documentation how to set up datasource for
>>>Tomcat 5.5.
>>>
>>>Christian
>>>
>>>Saturday, January 7, 2006, 1:31:53 PM, you wrote:
>>>
>>>
>>>
>>>      
>>>
>>>>Hi Christian,
>>>>In our web.xml file, we have a resource description as follows:
>>>>  
>>>>
>>>>        
>>>>
>>>
>>>
>>>      
>>>
>>>><resource-ref>
>>>>   <description>DB Connection</description>
>>>>   <res-ref-name>jdbc/pokerdb</res-ref-name>
>>>>   <res-type>javax.sql.DataSource</res-type>
>>>>   <res-auth>Container</res-auth>
>>>> </resource-ref>
>>>>  
>>>>
>>>>        
>>>>
>>>
>>>
>>>      
>>>
>>>>Is this what we need to change? Will this require other changes in the
>>>>context.xml file aswell?
>>>>Incidentally, because we are being hosted on a shared Tomcat server,
>>>>will changes to our web.xml and context.xml files require a global
>>>>tomcat restart, or will it be enough just to restart our context? I
>>>>would expect the hosting company not to allow us to restart Tomcat for
>>>>more than 100 users every time we need to make a change?
>>>>Thanks,
>>>>Martin
>>>>  
>>>>
>>>>        
>>>>
>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: [hidden email]
>>>For additional commands, e-mail:
>>>[hidden email]
>>>
>>>
>>>
>>>
>>>
>>>      
>>>
>
>
>
>  
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re[2]: [DBCP] Problem when hosting live

Christian Hufgard
Hi Martin,

now it starts beeing strange... Did you allready try to set up a
Tomcat 5.5 on a testing machine with the same settings the live system
has? Think you should do this, so you can look faster at the logs and
test if a restart of the whole Tomcat is necessary.
It could also be helpfull to install the Tomcat Admin webapps. There
you could get some information concerning your application setup.
It is normal that there are no errors in the log during startup if the
pool does not has a setting to open some connections during
construction.

Christian

Saturday, January 7, 2006, 4:10:44 PM, you wrote:

> Hi Christian,
> Afraid still no luck. I've made the changes to the context.xml file as
> you suggested, and reloaded the context on the remote server, but I'm
> having the same troubles.
> I will try to have another look around the net for possible solutions.
> It may be possible that a global tomcat restart is necessary, in which
> case a more ideal solution would have to be found, since that would
> upset too many other users.
> Having asked the remote administrators to review the tomcat logs, they
> said that my application was loaded OK, and they couldn't see any error
> messages in the logs. I wouldn't even know what kind of log error to
> look for.
> Thanks,
> Martin


> Christian Hufgard wrote:

>>Hi Martin,
>>
>>I think no one will punish you for using the wrong list. At least not
>>me, since I am just a dump user. :) Think there are dedicated mailing
>>lists for tomcat problems, but I had to look for them...
>>In your context.xml you set the parameters the way it had to be done
>>before Tomcat 5.5.
>>
>>Try these settings in the context.xml:
>>
>><Resource name="jdbc/pokerdb"
>>auth="Container"
>>type="javax.sql.DataSource"
>>maxActive="30" maxIdle="10"
>>maxWait="10000"
>>username="myuser"
>>password="mypassword"
>>driverClassName="com.mysql.jdbc.Driver"
>>removeAbandoned="true"
>>removeAbandonedTimeout="60"
>>url="jdbc:mysql://217.114.172.221/pokerhou_pokerdb" />
>>
>>Christian
>>
>>
>>Saturday, January 7, 2006, 2:30:22 PM, you wrote:
>>
>>  
>>
>>>Hi Christian,
>>>Apologies for emailing the wrong list. I assumed this would be more a
>>>dbcp-config problem. Is there an alternative list specifically for
>>>dealing with Tomcat config?
>>>Other than the web.xml and context.xml files, we have made no other
>>>changes to the tomcat setup. I will attach a copy of the context.xml
>>>file in the hope that someone might be able to see what is wrong.
>>>If the web.xml and context.xml files appear fine, I really have no idea
>>>where to turn. Unfortunately, the technical people in the hosting
>>>company don't seem to know what's wrong either.
>>>Martin
>>>    
>>>
>>
>>
>>  
>>
>>>Christian Hufgard wrote:
>>>    
>>>
>>
>>  
>>
>>>>Hi Martin,
>>>>
>>>>I think first of all, you should change the mailing list. :) This is
>>>>more a tomcat-config than a dbcp problem.
>>>>The resource-ref in the web.xml seems ok for me. Did you have the
>>>>datasource globally defined on your development/testing system?
>>>>Restarting your context should be sufficent if you changed your
>>>>web.xml/context.xml.
>>>>
>>>>Take a look at
>>>>http://tomcat.apache.org/tomcat-5.5-doc/jndi-resources-howto.html
>>>>there is a pretty helpful documentation how to set up datasource for
>>>>Tomcat 5.5.
>>>>
>>>>Christian
>>>>
>>>>Saturday, January 7, 2006, 1:31:53 PM, you wrote:
>>>>
>>>>
>>>>
>>>>      
>>>>
>>>>>Hi Christian,
>>>>>In our web.xml file, we have a resource description as follows:
>>>>>  
>>>>>
>>>>>        
>>>>>
>>>>
>>>>
>>>>      
>>>>
>>>>><resource-ref>
>>>>>   <description>DB Connection</description>
>>>>>   <res-ref-name>jdbc/pokerdb</res-ref-name>
>>>>>   <res-type>javax.sql.DataSource</res-type>
>>>>>   <res-auth>Container</res-auth>
>>>>> </resource-ref>
>>>>>  
>>>>>
>>>>>        
>>>>>
>>>>
>>>>
>>>>      
>>>>
>>>>>Is this what we need to change? Will this require other changes in the
>>>>>context.xml file aswell?
>>>>>Incidentally, because we are being hosted on a shared Tomcat server,
>>>>>will changes to our web.xml and context.xml files require a global
>>>>>tomcat restart, or will it be enough just to restart our context? I
>>>>>would expect the hosting company not to allow us to restart Tomcat for
>>>>>more than 100 users every time we need to make a change?
>>>>>Thanks,
>>>>>Martin
>>>>>  
>>>>>
>>>>>        
>>>>>
>>>>
>>>>
>>>>---------------------------------------------------------------------
>>>>To unsubscribe, e-mail:
>>>>[hidden email]
>>>>For additional commands, e-mail:
>>>>[hidden email]
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>      
>>>>
>>
>>
>>
>>  
>>

> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail:
> [hidden email]



--
Best regards,
 Christian                            mailto:[hidden email]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [DBCP] Problem when hosting live

Martin Grogan
Hi Christian,
Afraid it would be a considerable effort to upgrade our Tomcat version
to 5.5 at this time. We're still doing work on other applicatons that
are hosted on 5.0.28.
I'm sure we're on the right track with the different versions of
context.xml, but am still getting the same messages. I will double check
with the hosting company that *all necessary* files are correctly
installed with Tomcat and will continue to pour over logs, etc. until we
find something that might give us a clue.
It hadn't occurred to me that this may due to differences in Tomcat
versions, so when I looked, I found and followed the information on this
site.
http://www.crazysquirrel.com/computing/java/connection-pooling.jspx
Hopefully it may prove useful for the hosting admin people.

Thanks for all your help,
Martin


Christian Hufgard wrote:

>Hi Martin,
>
>now it starts beeing strange... Did you allready try to set up a
>Tomcat 5.5 on a testing machine with the same settings the live system
>has? Think you should do this, so you can look faster at the logs and
>test if a restart of the whole Tomcat is necessary.
>It could also be helpfull to install the Tomcat Admin webapps. There
>you could get some information concerning your application setup.
>It is normal that there are no errors in the log during startup if the
>pool does not has a setting to open some connections during
>construction.
>
>Christian
>
>Saturday, January 7, 2006, 4:10:44 PM, you wrote:
>
>  
>
>>Hi Christian,
>>Afraid still no luck. I've made the changes to the context.xml file as
>>you suggested, and reloaded the context on the remote server, but I'm
>>having the same troubles.
>>I will try to have another look around the net for possible solutions.
>>It may be possible that a global tomcat restart is necessary, in which
>>case a more ideal solution would have to be found, since that would
>>upset too many other users.
>>Having asked the remote administrators to review the tomcat logs, they
>>said that my application was loaded OK, and they couldn't see any error
>>messages in the logs. I wouldn't even know what kind of log error to
>>look for.
>>Thanks,
>>Martin
>>    
>>
>
>
>  
>
>>Christian Hufgard wrote:
>>    
>>
>
>  
>
>>>Hi Martin,
>>>
>>>I think no one will punish you for using the wrong list. At least not
>>>me, since I am just a dump user. :) Think there are dedicated mailing
>>>lists for tomcat problems, but I had to look for them...
>>>In your context.xml you set the parameters the way it had to be done
>>>before Tomcat 5.5.
>>>
>>>Try these settings in the context.xml:
>>>
>>><Resource name="jdbc/pokerdb"
>>>auth="Container"
>>>type="javax.sql.DataSource"
>>>maxActive="30" maxIdle="10"
>>>maxWait="10000"
>>>username="myuser"
>>>password="mypassword"
>>>driverClassName="com.mysql.jdbc.Driver"
>>>removeAbandoned="true"
>>>removeAbandonedTimeout="60"
>>>url="jdbc:mysql://217.114.172.221/pokerhou_pokerdb" />
>>>
>>>Christian
>>>
>>>
>>>Saturday, January 7, 2006, 2:30:22 PM, you wrote:
>>>
>>>
>>>
>>>      
>>>
>>>>Hi Christian,
>>>>Apologies for emailing the wrong list. I assumed this would be more a
>>>>dbcp-config problem. Is there an alternative list specifically for
>>>>dealing with Tomcat config?
>>>>Other than the web.xml and context.xml files, we have made no other
>>>>changes to the tomcat setup. I will attach a copy of the context.xml
>>>>file in the hope that someone might be able to see what is wrong.
>>>>If the web.xml and context.xml files appear fine, I really have no idea
>>>>where to turn. Unfortunately, the technical people in the hosting
>>>>company don't seem to know what's wrong either.
>>>>Martin
>>>>  
>>>>
>>>>        
>>>>
>>>
>>>
>>>      
>>>
>>>>Christian Hufgard wrote:
>>>>  
>>>>
>>>>        
>>>>
>>>
>>>
>>>      
>>>
>>>>>Hi Martin,
>>>>>
>>>>>I think first of all, you should change the mailing list. :) This is
>>>>>more a tomcat-config than a dbcp problem.
>>>>>The resource-ref in the web.xml seems ok for me. Did you have the
>>>>>datasource globally defined on your development/testing system?
>>>>>Restarting your context should be sufficent if you changed your
>>>>>web.xml/context.xml.
>>>>>
>>>>>Take a look at
>>>>>http://tomcat.apache.org/tomcat-5.5-doc/jndi-resources-howto.html
>>>>>there is a pretty helpful documentation how to set up datasource for
>>>>>Tomcat 5.5.
>>>>>
>>>>>Christian
>>>>>
>>>>>Saturday, January 7, 2006, 1:31:53 PM, you wrote:
>>>>>
>>>>>
>>>>>
>>>>>    
>>>>>
>>>>>          
>>>>>
>>>>>>Hi Christian,
>>>>>>In our web.xml file, we have a resource description as follows:
>>>>>>  
>>>>>>
>>>>>>      
>>>>>>
>>>>>>            
>>>>>>
>>>>>    
>>>>>
>>>>>          
>>>>>
>>>>>><resource-ref>
>>>>>>  <description>DB Connection</description>
>>>>>>  <res-ref-name>jdbc/pokerdb</res-ref-name>
>>>>>>  <res-type>javax.sql.DataSource</res-type>
>>>>>>  <res-auth>Container</res-auth>
>>>>>></resource-ref>
>>>>>>  
>>>>>>
>>>>>>      
>>>>>>
>>>>>>            
>>>>>>
>>>>>    
>>>>>
>>>>>          
>>>>>
>>>>>>Is this what we need to change? Will this require other changes in the
>>>>>>context.xml file aswell?
>>>>>>Incidentally, because we are being hosted on a shared Tomcat server,
>>>>>>will changes to our web.xml and context.xml files require a global
>>>>>>tomcat restart, or will it be enough just to restart our context? I
>>>>>>would expect the hosting company not to allow us to restart Tomcat for
>>>>>>more than 100 users every time we need to make a change?
>>>>>>Thanks,
>>>>>>Martin
>>>>>>  
>>>>>>
>>>>>>      
>>>>>>
>>>>>>            
>>>>>>
>>>>>---------------------------------------------------------------------
>>>>>To unsubscribe, e-mail:
>>>>>[hidden email]
>>>>>For additional commands, e-mail:
>>>>>[hidden email]
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>    
>>>>>
>>>>>          
>>>>>
>>>
>>>
>>>
>>>      
>>>
>
>  
>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [hidden email]
>>For additional commands, e-mail:
>>[hidden email]
>>    
>>
>
>
>
>  
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re[2]: [DBCP] Problem when hosting live

Christian Hufgard
Hello Martin,

Can't you install a seperate Tomcat for testing? It would be the best
way to test your application on the platform it will later be used on.
In the example context.xml-snippet I gave you, there was no factory
definied. Maybe this is a problem.

Christian

Saturday, January 7, 2006, 4:49:21 PM, you wrote:

> Hi Christian,
> Afraid it would be a considerable effort to upgrade our Tomcat version
> to 5.5 at this time. We're still doing work on other applicatons that
> are hosted on 5.0.28.
> I'm sure we're on the right track with the different versions of
> context.xml, but am still getting the same messages. I will double check
> with the hosting company that *all necessary* files are correctly
> installed with Tomcat and will continue to pour over logs, etc. until we
> find something that might give us a clue.
> It hadn't occurred to me that this may due to differences in Tomcat
> versions, so when I looked, I found and followed the information on this
> site.
> http://www.crazysquirrel.com/computing/java/connection-pooling.jspx
> Hopefully it may prove useful for the hosting admin people.

> Thanks for all your help,
> Martin


> Christian Hufgard wrote:

>>Hi Martin,
>>
>>now it starts beeing strange... Did you allready try to set up a
>>Tomcat 5.5 on a testing machine with the same settings the live system
>>has? Think you should do this, so you can look faster at the logs and
>>test if a restart of the whole Tomcat is necessary.
>>It could also be helpfull to install the Tomcat Admin webapps. There
>>you could get some information concerning your application setup.
>>It is normal that there are no errors in the log during startup if the
>>pool does not has a setting to open some connections during
>>construction.
>>
>>Christian
>>
>>Saturday, January 7, 2006, 4:10:44 PM, you wrote:
>>
>>  
>>
>>>Hi Christian,
>>>Afraid still no luck. I've made the changes to the context.xml file as
>>>you suggested, and reloaded the context on the remote server, but I'm
>>>having the same troubles.
>>>I will try to have another look around the net for possible solutions.
>>>It may be possible that a global tomcat restart is necessary, in which
>>>case a more ideal solution would have to be found, since that would
>>>upset too many other users.
>>>Having asked the remote administrators to review the tomcat logs, they
>>>said that my application was loaded OK, and they couldn't see any error
>>>messages in the logs. I wouldn't even know what kind of log error to
>>>look for.
>>>Thanks,
>>>Martin
>>>    
>>>
>>
>>
>>  
>>
>>>Christian Hufgard wrote:
>>>    
>>>
>>
>>  
>>
>>>>Hi Martin,
>>>>
>>>>I think no one will punish you for using the wrong list. At least not
>>>>me, since I am just a dump user. :) Think there are dedicated mailing
>>>>lists for tomcat problems, but I had to look for them...
>>>>In your context.xml you set the parameters the way it had to be done
>>>>before Tomcat 5.5.
>>>>
>>>>Try these settings in the context.xml:
>>>>
>>>><Resource name="jdbc/pokerdb"
>>>>auth="Container"
>>>>type="javax.sql.DataSource"
>>>>maxActive="30" maxIdle="10"
>>>>maxWait="10000"
>>>>username="myuser"
>>>>password="mypassword"
>>>>driverClassName="com.mysql.jdbc.Driver"
>>>>removeAbandoned="true"
>>>>removeAbandonedTimeout="60"
>>>>url="jdbc:mysql://217.114.172.221/pokerhou_pokerdb" />
>>>>
>>>>Christian
>>>>
>>>>
>>>>Saturday, January 7, 2006, 2:30:22 PM, you wrote:
>>>>
>>>>
>>>>
>>>>      
>>>>
>>>>>Hi Christian,
>>>>>Apologies for emailing the wrong list. I assumed this would be more a
>>>>>dbcp-config problem. Is there an alternative list specifically for
>>>>>dealing with Tomcat config?
>>>>>Other than the web.xml and context.xml files, we have made no other
>>>>>changes to the tomcat setup. I will attach a copy of the context.xml
>>>>>file in the hope that someone might be able to see what is wrong.
>>>>>If the web.xml and context.xml files appear fine, I really have no idea
>>>>>where to turn. Unfortunately, the technical people in the hosting
>>>>>company don't seem to know what's wrong either.
>>>>>Martin
>>>>>  
>>>>>
>>>>>        
>>>>>
>>>>
>>>>
>>>>      
>>>>
>>>>>Christian Hufgard wrote:
>>>>>  
>>>>>
>>>>>        
>>>>>
>>>>
>>>>
>>>>      
>>>>
>>>>>>Hi Martin,
>>>>>>
>>>>>>I think first of all, you should change the mailing list. :) This is
>>>>>>more a tomcat-config than a dbcp problem.
>>>>>>The resource-ref in the web.xml seems ok for me. Did you have the
>>>>>>datasource globally defined on your development/testing system?
>>>>>>Restarting your context should be sufficent if you changed your
>>>>>>web.xml/context.xml.
>>>>>>
>>>>>>Take a look at
>>>>>>http://tomcat.apache.org/tomcat-5.5-doc/jndi-resources-howto.html
>>>>>>there is a pretty helpful documentation how to set up datasource for
>>>>>>Tomcat 5.5.
>>>>>>
>>>>>>Christian
>>>>>>
>>>>>>Saturday, January 7, 2006, 1:31:53 PM, you wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>    
>>>>>>
>>>>>>          
>>>>>>
>>>>>>>Hi Christian,
>>>>>>>In our web.xml file, we have a resource description as follows:
>>>>>>>  
>>>>>>>
>>>>>>>      
>>>>>>>
>>>>>>>            
>>>>>>>
>>>>>>    
>>>>>>
>>>>>>          
>>>>>>
>>>>>>><resource-ref>
>>>>>>>  <description>DB Connection</description>
>>>>>>>  <res-ref-name>jdbc/pokerdb</res-ref-name>
>>>>>>>  <res-type>javax.sql.DataSource</res-type>
>>>>>>>  <res-auth>Container</res-auth>
>>>>>>></resource-ref>
>>>>>>>  
>>>>>>>
>>>>>>>      
>>>>>>>
>>>>>>>            
>>>>>>>
>>>>>>    
>>>>>>
>>>>>>          
>>>>>>
>>>>>>>Is this what we need to change? Will this require other changes in the
>>>>>>>context.xml file aswell?
>>>>>>>Incidentally, because we are being hosted on a shared Tomcat server,
>>>>>>>will changes to our web.xml and context.xml files require a global
>>>>>>>tomcat restart, or will it be enough just to restart our context? I
>>>>>>>would expect the hosting company not to allow us to restart Tomcat for
>>>>>>>more than 100 users every time we need to make a change?
>>>>>>>Thanks,
>>>>>>>Martin
>>>>>>>  
>>>>>>>
>>>>>>>      
>>>>>>>
>>>>>>>            
>>>>>>>
>>>>>>---------------------------------------------------------------------
>>>>>>To unsubscribe, e-mail:
>>>>>>[hidden email]
>>>>>>For additional commands, e-mail:
>>>>>>[hidden email]
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>    
>>>>>>
>>>>>>          
>>>>>>
>>>>
>>>>
>>>>
>>>>      
>>>>
>>
>>  
>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: [hidden email]
>>>For additional commands, e-mail:
>>>[hidden email]
>>>    
>>>
>>
>>
>>
>>  
>>

> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail:
> [hidden email]



--
Best regards,
 Christian                            mailto:[hidden email]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [DBCP] Problem when hosting live

Martin Grogan
Hi Christian,
I noticed that the factory wasn't defined and put one in, according to
the instructions on the website I sent earlier.
Unfortunately this did not make a difference.
I will look into the possibility of installing another version of
Tomcat, but this may take a while to get sorted and application
re-deployed and tested, etc.
I'm just hoping in the meantime that someone in the hosting company has
a suggestion given the fact that any website I've seen describes
reasonably clearly how to get the connection pooling done.
Here's hoping...
Thanks,
Martin


Christian Hufgard wrote:

>Hello Martin,
>
>Can't you install a seperate Tomcat for testing? It would be the best
>way to test your application on the platform it will later be used on.
>In the example context.xml-snippet I gave you, there was no factory
>definied. Maybe this is a problem.
>
>Christian
>
>Saturday, January 7, 2006, 4:49:21 PM, you wrote:
>
>  
>
>>Hi Christian,
>>Afraid it would be a considerable effort to upgrade our Tomcat version
>>to 5.5 at this time. We're still doing work on other applicatons that
>>are hosted on 5.0.28.
>>I'm sure we're on the right track with the different versions of
>>context.xml, but am still getting the same messages. I will double check
>>with the hosting company that *all necessary* files are correctly
>>installed with Tomcat and will continue to pour over logs, etc. until we
>>find something that might give us a clue.
>>It hadn't occurred to me that this may due to differences in Tomcat
>>versions, so when I looked, I found and followed the information on this
>>site.
>>http://www.crazysquirrel.com/computing/java/connection-pooling.jspx
>>Hopefully it may prove useful for the hosting admin people.
>>    
>>
>
>  
>
>>Thanks for all your help,
>>Martin
>>    
>>
>
>
>  
>
>>Christian Hufgard wrote:
>>    
>>
>
>  
>
>>>Hi Martin,
>>>
>>>now it starts beeing strange... Did you allready try to set up a
>>>Tomcat 5.5 on a testing machine with the same settings the live system
>>>has? Think you should do this, so you can look faster at the logs and
>>>test if a restart of the whole Tomcat is necessary.
>>>It could also be helpfull to install the Tomcat Admin webapps. There
>>>you could get some information concerning your application setup.
>>>It is normal that there are no errors in the log during startup if the
>>>pool does not has a setting to open some connections during
>>>construction.
>>>
>>>Christian
>>>
>>>Saturday, January 7, 2006, 4:10:44 PM, you wrote:
>>>
>>>
>>>
>>>      
>>>
>>>>Hi Christian,
>>>>Afraid still no luck. I've made the changes to the context.xml file as
>>>>you suggested, and reloaded the context on the remote server, but I'm
>>>>having the same troubles.
>>>>I will try to have another look around the net for possible solutions.
>>>>It may be possible that a global tomcat restart is necessary, in which
>>>>case a more ideal solution would have to be found, since that would
>>>>upset too many other users.
>>>>Having asked the remote administrators to review the tomcat logs, they
>>>>said that my application was loaded OK, and they couldn't see any error
>>>>messages in the logs. I wouldn't even know what kind of log error to
>>>>look for.
>>>>Thanks,
>>>>Martin
>>>>  
>>>>
>>>>        
>>>>
>>>
>>>
>>>      
>>>
>>>>Christian Hufgard wrote:
>>>>  
>>>>
>>>>        
>>>>
>>>
>>>
>>>      
>>>
>>>>>Hi Martin,
>>>>>
>>>>>I think no one will punish you for using the wrong list. At least not
>>>>>me, since I am just a dump user. :) Think there are dedicated mailing
>>>>>lists for tomcat problems, but I had to look for them...
>>>>>In your context.xml you set the parameters the way it had to be done
>>>>>before Tomcat 5.5.
>>>>>
>>>>>Try these settings in the context.xml:
>>>>>
>>>>><Resource name="jdbc/pokerdb"
>>>>>auth="Container"
>>>>>type="javax.sql.DataSource"
>>>>>maxActive="30" maxIdle="10"
>>>>>maxWait="10000"
>>>>>username="myuser"
>>>>>password="mypassword"
>>>>>driverClassName="com.mysql.jdbc.Driver"
>>>>>removeAbandoned="true"
>>>>>removeAbandonedTimeout="60"
>>>>>url="jdbc:mysql://217.114.172.221/pokerhou_pokerdb" />
>>>>>
>>>>>Christian
>>>>>
>>>>>
>>>>>Saturday, January 7, 2006, 2:30:22 PM, you wrote:
>>>>>
>>>>>
>>>>>
>>>>>    
>>>>>
>>>>>          
>>>>>
>>>>>>Hi Christian,
>>>>>>Apologies for emailing the wrong list. I assumed this would be more a
>>>>>>dbcp-config problem. Is there an alternative list specifically for
>>>>>>dealing with Tomcat config?
>>>>>>Other than the web.xml and context.xml files, we have made no other
>>>>>>changes to the tomcat setup. I will attach a copy of the context.xml
>>>>>>file in the hope that someone might be able to see what is wrong.
>>>>>>If the web.xml and context.xml files appear fine, I really have no idea
>>>>>>where to turn. Unfortunately, the technical people in the hosting
>>>>>>company don't seem to know what's wrong either.
>>>>>>Martin
>>>>>>  
>>>>>>
>>>>>>      
>>>>>>
>>>>>>            
>>>>>>
>>>>>    
>>>>>
>>>>>          
>>>>>
>>>>>>Christian Hufgard wrote:
>>>>>>  
>>>>>>
>>>>>>      
>>>>>>
>>>>>>            
>>>>>>
>>>>>    
>>>>>
>>>>>          
>>>>>
>>>>>>>Hi Martin,
>>>>>>>
>>>>>>>I think first of all, you should change the mailing list. :) This is
>>>>>>>more a tomcat-config than a dbcp problem.
>>>>>>>The resource-ref in the web.xml seems ok for me. Did you have the
>>>>>>>datasource globally defined on your development/testing system?
>>>>>>>Restarting your context should be sufficent if you changed your
>>>>>>>web.xml/context.xml.
>>>>>>>
>>>>>>>Take a look at
>>>>>>>http://tomcat.apache.org/tomcat-5.5-doc/jndi-resources-howto.html
>>>>>>>there is a pretty helpful documentation how to set up datasource for
>>>>>>>Tomcat 5.5.
>>>>>>>
>>>>>>>Christian
>>>>>>>
>>>>>>>Saturday, January 7, 2006, 1:31:53 PM, you wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>    
>>>>>>>
>>>>>>>        
>>>>>>>
>>>>>>>              
>>>>>>>
>>>>>>>>Hi Christian,
>>>>>>>>In our web.xml file, we have a resource description as follows:
>>>>>>>>
>>>>>>>>
>>>>>>>>      
>>>>>>>>
>>>>>>>>          
>>>>>>>>
>>>>>>>>                
>>>>>>>>
>>>>>>>    
>>>>>>>
>>>>>>>        
>>>>>>>
>>>>>>>              
>>>>>>>
>>>>>>>><resource-ref>
>>>>>>>> <description>DB Connection</description>
>>>>>>>> <res-ref-name>jdbc/pokerdb</res-ref-name>
>>>>>>>> <res-type>javax.sql.DataSource</res-type>
>>>>>>>> <res-auth>Container</res-auth>
>>>>>>>></resource-ref>
>>>>>>>>
>>>>>>>>
>>>>>>>>      
>>>>>>>>
>>>>>>>>          
>>>>>>>>
>>>>>>>>                
>>>>>>>>
>>>>>>>    
>>>>>>>
>>>>>>>        
>>>>>>>
>>>>>>>              
>>>>>>>
>>>>>>>>Is this what we need to change? Will this require other changes in the
>>>>>>>>context.xml file aswell?
>>>>>>>>Incidentally, because we are being hosted on a shared Tomcat server,
>>>>>>>>will changes to our web.xml and context.xml files require a global
>>>>>>>>tomcat restart, or will it be enough just to restart our context? I
>>>>>>>>would expect the hosting company not to allow us to restart Tomcat for
>>>>>>>>more than 100 users every time we need to make a change?
>>>>>>>>Thanks,
>>>>>>>>Martin
>>>>>>>>
>>>>>>>>
>>>>>>>>      
>>>>>>>>
>>>>>>>>          
>>>>>>>>
>>>>>>>>                
>>>>>>>>
>>>>>>>---------------------------------------------------------------------
>>>>>>>To unsubscribe, e-mail:
>>>>>>>[hidden email]
>>>>>>>For additional commands, e-mail:
>>>>>>>[hidden email]
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>    
>>>>>>>
>>>>>>>        
>>>>>>>
>>>>>>>              
>>>>>>>
>>>>>
>>>>>    
>>>>>
>>>>>          
>>>>>
>>>
>>>
>>>      
>>>
>>>>---------------------------------------------------------------------
>>>>To unsubscribe, e-mail: [hidden email]
>>>>For additional commands, e-mail:
>>>>[hidden email]
>>>>  
>>>>
>>>>        
>>>>
>>>
>>>
>>>
>>>      
>>>
>
>  
>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [hidden email]
>>For additional commands, e-mail:
>>[hidden email]
>>    
>>
>
>
>
>  
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]