Re: [Tomcat 5.5.17] Strange Problem With Batabase Connection Pool
Hi, (n+1)-th times !! : I've new information about the Database Connection Pool's mistery. After the last setup, adding testWhileIdle="true" and timeBetweenEvictionRunsMillis="240" it worked nice after about 3 hours of inactivity, but I don't undestand why It seems to work now and it didn't work before. Any ideas about what could be happening here?. Thanks in advance. Albert - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Tomcat 5.5.17] Strange Problem With Batabase Connection Pool
Hi for the n-th time ! : I've set up testWhileIdle="true" and timeBetweenEvictionRunsMillis="240". I'll try again in about an hour with this new setup and I'll come back if the new setup give me any new information. 2007/11/30, albert quinn <[EMAIL PROTECTED]>: > Hi again : > > I've read the URLs about DBCP configuration. Then, I've set up DBCP > for my connection pool. I've added a validation query and I've set > testOnBorrow="true". I've tried again and I've achieved the same > strange behaviour : after about and hour of inactivity, it waits > forever in the 3th line. No errors reported in the Tomcat logs. > > Any idea of what's happening or what can I do to know what's > happening?. Thanks in advance. > > Albert > > > > 2007/11/29, albert quinn <[EMAIL PROTECTED]>: > > Hi once more time : > > > > Thanks again for your help. Sorry, I didn't know the connections > > aren't really closed. I've to leave now, but I'll read the URLs you > > gave me tomorrow and then, I'll try to set up DHCP properly. > > > > Thanks a lot. I'll come back if I get any kind of new information > > about the mistery. > > > > > > Albert > > > > > > > > > > > > > > 2007/11/29, Mark Thomas <[EMAIL PROTECTED]>: > > > albert quinn wrote: > > > > Hi again, Mark : > > > > > > > > I've benn thinking about the problem and I don't really think it > > > > could be a problem with database connection timeout due to inactivity > > > > because when the web service is called, the web service gets a > > > > connection from the pool, it uses the connection, and then it closes > > > > the connection before returning the web service results. So, it > > > > mustn't be a problem with database connection timeout due to > > > > inactivity, don't you think? > > > > > > No. I disagree with your analysis. The point of DBCP is that the > > > connections aren't closed. When you call close() in your code that just > > > returns the connection to the pool. The actual database connection remains > > > open. > > > > > > The URL you want is: > > > http://commons.apache.org/dbcp/configuration.html > > > > > > The starting point for DBCP is > > > http://commons.apache.org/dbcp/ > > > > > > Mark > > > > > > > > > > > > - > > > 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]
Re: [Tomcat 5.5.17] Strange Problem With Batabase Connection Pool
Hi again : I've read the URLs about DBCP configuration. Then, I've set up DBCP for my connection pool. I've added a validation query and I've set testOnBorrow="true". I've tried again and I've achieved the same strange behaviour : after about and hour of inactivity, it waits forever in the 3th line. No errors reported in the Tomcat logs. Any idea of what's happening or what can I do to know what's happening?. Thanks in advance. Albert 2007/11/29, albert quinn <[EMAIL PROTECTED]>: > Hi once more time : > > Thanks again for your help. Sorry, I didn't know the connections > aren't really closed. I've to leave now, but I'll read the URLs you > gave me tomorrow and then, I'll try to set up DHCP properly. > > Thanks a lot. I'll come back if I get any kind of new information > about the mistery. > > > Albert > > > > > > > 2007/11/29, Mark Thomas <[EMAIL PROTECTED]>: > > albert quinn wrote: > > > Hi again, Mark : > > > > > > I've benn thinking about the problem and I don't really think it > > > could be a problem with database connection timeout due to inactivity > > > because when the web service is called, the web service gets a > > > connection from the pool, it uses the connection, and then it closes > > > the connection before returning the web service results. So, it > > > mustn't be a problem with database connection timeout due to > > > inactivity, don't you think? > > > > No. I disagree with your analysis. The point of DBCP is that the > > connections aren't closed. When you call close() in your code that just > > returns the connection to the pool. The actual database connection remains > > open. > > > > The URL you want is: > > http://commons.apache.org/dbcp/configuration.html > > > > The starting point for DBCP is > > http://commons.apache.org/dbcp/ > > > > Mark > > > > > > > > - > > 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]
Re: [Tomcat 5.5.17] Strange Problem With Batabase Connection Pool
Hi once more time : Thanks again for your help. Sorry, I didn't know the connections aren't really closed. I've to leave now, but I'll read the URLs you gave me tomorrow and then, I'll try to set up DHCP properly. Thanks a lot. I'll come back if I get any kind of new information about the mistery. Albert 2007/11/29, Mark Thomas <[EMAIL PROTECTED]>: > albert quinn wrote: > > Hi again, Mark : > > > > I've benn thinking about the problem and I don't really think it > > could be a problem with database connection timeout due to inactivity > > because when the web service is called, the web service gets a > > connection from the pool, it uses the connection, and then it closes > > the connection before returning the web service results. So, it > > mustn't be a problem with database connection timeout due to > > inactivity, don't you think? > > No. I disagree with your analysis. The point of DBCP is that the > connections aren't closed. When you call close() in your code that just > returns the connection to the pool. The actual database connection remains > open. > > The URL you want is: > http://commons.apache.org/dbcp/configuration.html > > The starting point for DBCP is > http://commons.apache.org/dbcp/ > > Mark > > > > - > 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]
Re: [Tomcat 5.5.17] Strange Problem With Batabase Connection Pool
Hi again, Mark : I've benn thinking about the problem and I don't really think it could be a problem with database connection timeout due to inactivity because when the web service is called, the web service gets a connection from the pool, it uses the connection, and then it closes the connection before returning the web service results. So, it mustn't be a problem with database connection timeout due to inactivity, don't you think? Thanks again for your help. 2007/11/29, albert quinn <[EMAIL PROTECTED]>: > It could be. I'm really lost, and have no idea about what is happening. > > I forgot to tell that, when I call the web service after about an > hour of inactivity and it waits forever at the 3th line, if i call the > web service again, it works nice and it keeps on working nice (except > if I wait about an hour again). So, it could be what you say. > > Any URL where I can learn about the DBCP configuration and how to > set testOnBorroy to true?. > > MANY thanks for your help with this strange behaviour!!. > > > > 2007/11/29, Mark Thomas <[EMAIL PROTECTED]>: > > albert quinn wrote: > > > The lines 1 and 2 are executed, but the 4th line is never reached. > > > Any idea of what could be happening here or how could I do to discover > > > what's happening? does it seems to be a bug on my code or a setup > > > problem? > > > > Could you database connection be timing out due to inactivity? It is worth > > adding a validation query to your DBCP configuration and setting > > testOnBorrow to true. > > > > Mark > > > > > > > > - > > 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]
Re: [Tomcat 5.5.17] Strange Problem With Batabase Connection Pool
It could be. I'm really lost, and have no idea about what is happening. I forgot to tell that, when I call the web service after about an hour of inactivity and it waits forever at the 3th line, if i call the web service again, it works nice and it keeps on working nice (except if I wait about an hour again). So, it could be what you say. Any URL where I can learn about the DBCP configuration and how to set testOnBorroy to true?. MANY thanks for your help with this strange behaviour!!. 2007/11/29, Mark Thomas <[EMAIL PROTECTED]>: > albert quinn wrote: > > The lines 1 and 2 are executed, but the 4th line is never reached. > > Any idea of what could be happening here or how could I do to discover > > what's happening? does it seems to be a bug on my code or a setup > > problem? > > Could you database connection be timing out due to inactivity? It is worth > adding a validation query to your DBCP configuration and setting > testOnBorrow to true. > > Mark > > > > - > 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]
[Tomcat 5.5.17] Strange Problem With Batabase Connection Pool
Hi all ! : I'm facing a very strange problem. I'm developing a web service with : - Apache Axis 2 RC 1.3 running on Tomcat 5.5.17, running on Windows XP Professional - Java JDK 1.5 I've set up a database connection pool in Tomcat. My Web Service gets a connection from the pool, sends a query to the Database and returns some information. When I call the Web Service for the first time, it works nice. If I call it again, it works nice. If I wait a few minutes (10 minutes or 20 minutes) and call it again, it works nice. If I wait about an hour and call it again, the Web Service call never returns. I've seen the Tomcat logs but no errors are reported. So, I've been searching about that problem in Google and Tomcat's mailing lists but I haven't found any useful information about the strange problem. So, I've been debugging the Web Service code : 1 - Context ctxt = new InitialContext(); 2 - DataSource ds = (DataSource) ctxt.lookup(java:comp/env/jdbc/database); 3 - Connection con = ds.getConnection(); 4 - The lines 1 and 2 are executed, but the 4th line is never reached. Any idea of what could be happening here or how could I do to discover what's happening? does it seems to be a bug on my code or a setup problem? Thanks in advance for any kind of help with this annoying error. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis 2, POJO, Exceptions and Faults
Hi Joe !!! :
Many thanks by your answer, I'm really a newbie in the Axis world
and I'm still lost, spending a lot of time reading the Axis 2 docs and
samples but not finding answers to thowsands of questions in that docs
and samples. So, I'm trying to find the easiest way to do what I need
quickly and in a few months (if a better Axis 2 docs and samples are
available) I'll try to do it better using my own AxisFaults, Axis 2
sessions, Rampart, and so on.
Again, many thanks by spending your time with my newbie
questions. Regards.
2007/7/16, Joe Nathan <[EMAIL PROTECTED]>:
albert quinn wrote:
>
> I've been trying to do something like that but i couldn't make it
> work . My test Web Service returns a String and the client receives
> the AxisFault/RemoteException message throwed from the Web Service as
> it was the returned value from the Web Service !!, so I'd
> been able to know in the client side if an error happened in the
> server side.
>
POJO is a plain Java objects that you cannot throw things!
I tend to return results wrapped in XML strings containing
types (=ok, error, ...) and contents. For clients, any exceptions
happened in transport will be captured by try {} catch blocks.
Errors occured in POJO servers will be embedded in return strings
as XML strings. Note that use of SOAP means that you should
live with XML!
regards.
--
View this message in context:
http://www.nabble.com/Axis-2%2C-POJO%2C-Exceptions-and-Faults-tf4080311.html#a11606621
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
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]
Axis 2, POJO, Exceptions and Faults
Hi !! :
I'd like to develop a web service in Axis 2 the easiest way
possible. So, I'd like to develop a POJO, and then generate a POJO Web
Service from it with the "Axis 2 Service Archiver" Eclipse plugin.
I'd like my POJO Web Service throwed RemoteExceptions or AxisFaults
and develop a RPCServiceClient catching that exceptions/faults,
something like this :
[web service]
...
if(anErrorHappened) throw AxisFault/RemoteException;
...
[web service]
[RPCServiceClient]
...
try {
...
returned_object = call_the_pojo_web_service(parameters);
...
}
catch (AxisFault e) {
// AxisFault or RemoteException
print_an_error(e);
}
...
[RPCServiceClient]
I've been trying to do something like that but i couldn't make it
work . My test Web Service returns a String and the client receives
the AxisFault/RemoteException message throwed from the Web Service as
it was the returned value from the Web Service !!, so I'd
been able to know in the client side if an error happened in the
server side.
The question is : is that scenario supported? If not... which is the
best choice to do it easy and with AxisFaults/RemoteExceptions? where
could i find more information about that (I've already read the Axis 2
docs)?
Thanks to everybody!.
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: problem with Tomcat 5.5.17, Axis 2, MySQL 3.1.12, JNDI
Hi again David !!! : Many thanks again. I've checked the mysql driver was in Tomcat's "common/lib" directory... it was. So, i've been reading again the Tomcat docs a lot of time, trying this, trying that... and finally i've solved the problem!!!. The problem was the "name" atribute in the "Resource" element, I've changed it from "java:comp/env/jdbc/DB" to "jdbc/DB" and it began to work fine !!.. yeah I've problems with Axis 2 now, but I can connect to the remote Database without problems. Many, many thanks again for spending your time with this problem!. 2007/7/12, David Smith <[EMAIL PROTECTED]>: No problem. One of the typical causes of this error is the element is missing or doesn't match what you've declared in axis2/WEB-INF/web.xml. In your case it could be there's a completing ... definition at conf/Catalina/localhost/axis2.xml? If so, delete the axis2.xml (or use it and fix it's declaration) and restart tomcat. Also be sure your mysql driver jar file is in tomcat's common/lib directory. I would think the error would be different if this weren't in the right place, but it's a good thing to check anyway especially since the direct connect method worked in your original post. --David albert quinn wrote: > Hi David !! : > > Many thanks for your advices. I've tried it. I've dropped the > context definition in my server.xml (i'd put it there after reading > this tutorial > http://tomcat.apache.org/tomcat-5.5-doc/jndi-datasource-examples-howto.html > > in the Tomcat docs), i've fixed the port number in my > "axis2/META-INF/context.xml file" and dropped the "autoReconnect" > paramater, adding validationQuery="select 1" to my Resource element. > > After that changes, i've removed the Tomcat logs and reboot Tomcat. > Then I've tried the web service, getting this new Exception message : > > Cannot create JDBC driver of class '' for connect URL 'null' > > > Then I've read the Tomcat logs looking for ideas about what [EMAIL PROTECTED]& > is going wrong with this, but I've not found any information that help > to discover what's happening. Any new ideas about what's going on or > about how to find the problem? > > Many thanks again by spending your (sure precious) time with this. > > > > > > > 2007/7/12, David Smith <[EMAIL PROTECTED]>: > >> I'd recommend dropping the context definition in your server.xml. Under >> normal conditions you should never have to modify that file except to >> alter server-wide settings like which ports it listens on. >> >> Also looking at your axis2/META-INF/context.xml file, I see the port >> number is incorrect. >> >> Lastly, I would recommend you drop the autoReconnect parameter of your >> database url and add validationQuery="select 1" to your Resource >> element. Autoreconnect is of minimal usefullness and validationQuery >> can test the db connection before your app attemps to use it. >> >> --David >> >> albert quinn wrote: >> > Hi ! : >> > >> > First of all : excuse my poor english. Second : I'm trying to set up >> > a MySQL connection pool on Tomcat 5.5.17 (running over Windows XP) to >> > connect to a remote DB from a web service running on the Axis 2 >> > deployed in Tomcat. I've read the Tomcat docs and the Tomcat mailing >> > lists but i've not founded any answers that help me to fix the >> > problem. I've this in my "conf\server.xml" : >> > >> > >> > . >> > > > reloadable="true"> >> > >> >> > name="java:comp/env/jdbc/DB" password="mypassword" >> > type="javax.sql.DataSource" >> > url="jdbc:mysql://remoteaddress.com:3306/db?autoReconnect=true" >> > username="myname"/> >> > >> > >> > >> > >> > >> > >> > >> > I've this "C:\Archivos de programa\Apache Software Foundation\Tomcat >> > 5.5\webapps\axis2\META-INF\context.xml " file : >> > >> > >> > >> > >> >WEB-INF/web.xml >> > >> > > > name="jdbc/DB" password="mypassword" type="javax.sql.DataSource" >> > url="jdbc:mysql://remoteaddress.com:3036/db?autoReconnect=true" >> > username="myname"/> >&g
Re: problem with Tomcat 5.5.17, Axis 2, MySQL 3.1.12, JNDI
Hi David !! : Many thanks for your advices. I've tried it. I've dropped the context definition in my server.xml (i'd put it there after reading this tutorial http://tomcat.apache.org/tomcat-5.5-doc/jndi-datasource-examples-howto.html in the Tomcat docs), i've fixed the port number in my "axis2/META-INF/context.xml file" and dropped the "autoReconnect" paramater, adding validationQuery="select 1" to my Resource element. After that changes, i've removed the Tomcat logs and reboot Tomcat. Then I've tried the web service, getting this new Exception message : Cannot create JDBC driver of class '' for connect URL 'null' Then I've read the Tomcat logs looking for ideas about what [EMAIL PROTECTED]& is going wrong with this, but I've not found any information that help to discover what's happening. Any new ideas about what's going on or about how to find the problem? Many thanks again by spending your (sure precious) time with this. 2007/7/12, David Smith <[EMAIL PROTECTED]>: I'd recommend dropping the context definition in your server.xml. Under normal conditions you should never have to modify that file except to alter server-wide settings like which ports it listens on. Also looking at your axis2/META-INF/context.xml file, I see the port number is incorrect. Lastly, I would recommend you drop the autoReconnect parameter of your database url and add validationQuery="select 1" to your Resource element. Autoreconnect is of minimal usefullness and validationQuery can test the db connection before your app attemps to use it. --David albert quinn wrote: > Hi ! : > > First of all : excuse my poor english. Second : I'm trying to set up > a MySQL connection pool on Tomcat 5.5.17 (running over Windows XP) to > connect to a remote DB from a web service running on the Axis 2 > deployed in Tomcat. I've read the Tomcat docs and the Tomcat mailing > lists but i've not founded any answers that help me to fix the > problem. I've this in my "conf\server.xml" : > > > . >reloadable="true"> > > name="java:comp/env/jdbc/DB" password="mypassword" > type="javax.sql.DataSource" > url="jdbc:mysql://remoteaddress.com:3306/db?autoReconnect=true" > username="myname"/> > > > > > > > > I've this "C:\Archivos de programa\Apache Software Foundation\Tomcat > 5.5\webapps\axis2\META-INF\context.xml " file : > > > > >WEB-INF/web.xml > > name="jdbc/DB" password="mypassword" type="javax.sql.DataSource" > url="jdbc:mysql://remoteaddress.com:3036/db?autoReconnect=true" > username="myname"/> > > > > I've these lines in "C:\Archivos de programa\Apache Software > Foundation\Tomcat 5.5\webapps\axis2\WEB-INF\web.xml" > > > >a description > > >jdbc/DB > > >javax.sql.DataSource > > >Container > > > > When i call the web service running on Axis 2, after a long time i > get the next Exception message : > > Cannot create PoolableConnectionFactory (Server connection failure > during transaction. Due to underlying exception: > 'java.net.SocketException: java.net.NoRouteToHostException: No route > to host: connect'. > > ** BEGIN NESTED EXCEPTION ** > > java.net.SocketException > MESSAGE: java.net.NoRouteToHostException: No route to host: connect > > STACKTRACE: > > java.net.SocketException: java.net.NoRouteToHostException: No route to > host: connect > >at > com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:156) > > >at com.mysql.jdbc.MysqlIO.(MysqlIO.java:284) > >at com.mysql.jdbc.Connection.createNewIO(Connection.java :2680) > >at com.mysql.jdbc.Connection.(Connection.java:1485) > >at > com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266) > > >at > org.apache.tomcat.dbcp.dbcp.DriverConnectionFactory.createConnection > (DriverConnectionFactory.java:37) > >at > org.apache.tomcat.dbcp.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290) > > >at > org.apache.tomcat.dbcp.dbcp.BasicDataSource.validateConnectionFactory > (BasicDataSource.java:877) > >at > org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:851) > > >at > org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnecti
problem with Tomcat 5.5.17, Axis 2, MySQL 3.1.12, JNDI
Hi ! :
First of all : excuse my poor english. Second : I'm trying to set up
a MySQL connection pool on Tomcat 5.5.17 (running over Windows XP) to
connect to a remote DB from a web service running on the Axis 2
deployed in Tomcat. I've read the Tomcat docs and the Tomcat mailing
lists but i've not founded any answers that help me to fix the
problem. I've this in my "conf\server.xml" :
.
I've this "C:\Archivos de programa\Apache Software Foundation\Tomcat
5.5\webapps\axis2\META-INF\context.xml " file :
WEB-INF/web.xml
I've these lines in "C:\Archivos de programa\Apache Software
Foundation\Tomcat 5.5\webapps\axis2\WEB-INF\web.xml"
a description
jdbc/DB
javax.sql.DataSource
Container
When i call the web service running on Axis 2, after a long time i
get the next Exception message :
Cannot create PoolableConnectionFactory (Server connection failure
during transaction. Due to underlying exception:
'java.net.SocketException: java.net.NoRouteToHostException: No route
to host: connect'.
** BEGIN NESTED EXCEPTION **
java.net.SocketException
MESSAGE: java.net.NoRouteToHostException: No route to host: connect
STACKTRACE:
java.net.SocketException: java.net.NoRouteToHostException: No route to
host: connect
at
com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:156)
at com.mysql.jdbc.MysqlIO.(MysqlIO.java:284)
at com.mysql.jdbc.Connection.createNewIO(Connection.java :2680)
at com.mysql.jdbc.Connection.(Connection.java:1485)
at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266)
at org.apache.tomcat.dbcp.dbcp.DriverConnectionFactory.createConnection
(DriverConnectionFactory.java:37)
at
org.apache.tomcat.dbcp.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.validateConnectionFactory
(BasicDataSource.java:877)
at
org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:851)
at
org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:540)
at code.prueba.PruebaBD.getUserLogin(PruebaBD.java:20)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java
:91)
at
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:39)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:144)
at
org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java:122)
at
org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUtil.java:116)
at
org.apache.axis2.transport.http.AxisServlet$ProcessRESTRequest.processURLRequest
(AxisServlet.java:776)
at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service (HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java
:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke
(StandardHostValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection
(Http11BaseProtocol.java:664)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java
:80)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Unknown Source)
** END NESTED EXCEPTION **
Attempted reconnect 3 times. Giving up.)
I've tried to turn it off the FireWall, but i've got the same
Exception message. The lines in the web service are :
Context oContext = new InitialContext();
DataSource oDataSource = (DataSource)
oContext.lookup("java:comp/env/jdbc/DB");
