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: [EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
