If you are sure you have copied the appropriate JDBC connection JAR for your webapp onto the new server, then are you POSITIVE your database allows connections from that new server using the db username and db password specified in the DATA_SOURCE. I've been in plenty of scenarios where the same setup didn't work on a new server because the database was hosted on another machine and didn't allow access from that new IP addresws as well as people forgetting to verify their db username/password if there is a database running on the new server. Can you connect on the server to the database from the command line using all of the details specified in your DATA_SOURCE configuration section?
Also, what version of Struts are you using? I thought DATA_SOURCES were taken out of the Struts config (or severly not recommended) as of the current Stable v1.2.4? Regards, David -----Original Message----- From: Kalluru Uma. Maheswar [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 19, 2005 8:38 AM To: Struts Users Mailing List Subject: RE: Marking servlet action as unavailable But it's a working struts-config.xml file in my local machine. The same database connection applies in the server too. Uma -----Original Message----- From: James Mitchell [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 19, 2005 6:53 PM To: Struts Users Mailing List Subject: Re: Marking servlet action as unavailable Here's 2 suggestions off the top of my head: - invalid syntax for the ds definition - you failed to provide the specified jdbc driver -- James Mitchell Software Engineer / Open Source Evangelist EdgeTech, Inc. 678.910.8017 AIM: jmitchtx ----- Original Message ----- From: "Kalluru Uma. Maheswar" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <user@struts.apache.org> Sent: Wednesday, January 19, 2005 8:19 AM Subject: Marking servlet action as unavailable Hi, I get the following error 2005-01-18 08:02:32 StandardContext[]Marking servlet action as unavailable 2005-01-18 08:02:33 StandardContext[]Servlet threw load() exception javax.servlet.UnavailableException: Initializing application data source org.apache.struts.action.DATA_SOURCE at org.apache.struts.action.ActionServlet.initModuleDataSources(ActionServl et.java:782) at org.apache.struts.action.ActionServlet.init(ActionServlet.java:331) at javax.servlet.GenericServlet.init(GenericServlet.java:211) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.jav a:1029) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:862) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.j ava:4013) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4357 ) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) at org.apache.catalina.core.StandardHost.start(StandardHost.java:789) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478) at org.apache.catalina.core.StandardService.start(StandardService.java:480) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2313) at org.apache.catalina.startup.Catalina.start(Catalina.java:556) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:2 18) which results in not loading my ActionServlet. This is due me configuring Database connection in struts-config.xml file. If I remove the db connection from struts-config.xml file then the app is working fine. Any ideas on why this is caused and how to resolve this? Uma --------------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
