Win a copy of The Business Blockchain this week in the Cloud forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

error in Debian

 
Natalia Lopez
Ranch Hand
Posts: 41
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi everybody
I had a webapp that work ok in Windows with tomcat 5 and mysql but I receive the error below when I try to deploy the same application in Debian with tomcat 4 and mysql

Initializing Hibernate
Finished Initializing Hibernate
java.lang.RuntimeException: Cannot open connection
at newsandevents.db.Singleton.listNews(Singleton.java:64)
at newsandevents.control.GestionNews.listNewsTitles(GestionNews.java:37)
at unnoba.Commands.GeneralCommands.IndexCommand.execute(IndexCommand.java:23)
at unnoba.GUIManagement.Controller.processRequest(Controller.java:43)
at unnoba.GUIManagement.Controller.doGet(Controller.java:67)
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:237)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:300)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:374)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743)
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:675)
at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
at java.lang.Thread.run(Thread.java:534)


The only difference is that with win I had tomcat 5 and with DEbian tomcat 4
King regards

Naty
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hmm. The stack trace says "at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)". Didn't you say that this stack trace came on the Debian system with Tomcat 4?
 
Natalia Lopez
Ranch Hand
Posts: 41
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes you are right, sorry
The version in Debian is also 5.0.27
 
David Harkness
Ranch Hand
Posts: 1646
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Natalia Lopez:
java.lang.RuntimeException: Cannot open connection
at newsandevents.db.Singleton.listNews(Singleton.java:64)
If newsandevents.db.Singleton is a class from your project, I highly suggest that you reconsider your exception-handling methodology. Either use the built-in exception chaining feature, roll your own, or log the caught exception before tossing it in the floor.

Likely you are having issues with how your JNDI data source is configured as others have had similar trouble in this forum. But without the original stack trace, we can only guess. Is the database up and receiving connections? Did you configure the DS correctly? Can you connect from a simple single-class test program running on the same machine?
 
Natalia Lopez
Ranch Hand
Posts: 41
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes you are right!!!
I was having some problems to add logs in linux, I can't find anything but with the network administrator guy, we did a good job.
We had a problem with the user of the database that hasn't got all the necesaries privilegies.
Thanks a lot for your help!

Naty
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic