top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Tomcat: Application getting stopped with error code 610 038

+2 votes
319 views

My tomcat web application stopped working after getting following error.

: Poller failed with error [610 038] : [APR does not understand this error code]

Could you please help with what could be root cause of this error.

posted Jan 27, 2015 by Vijay Shukla

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
0 votes
How to deploy a rails application with tomcat: URL

I have built a rails application with jruby. Since I have no experience with deploying a rails application in a production environment, I have spent some time doing a manual deployment on a linux server with tomcat6 as application server.

In essence, I have made a war file of the rails application with help of the warbler gem and deployed that on the linux server. I managed to get it up and running, but not yet exactly as I need it to be.

I have still some configuration issues. I hope you can help me or point me to the right place, since it may be a tomcat question. But I assume there must be some rails/tomcat expertise among the members of this group...

The point is, the URL in the development server is localhost:3000/invoices (using rails server)
The URL in the tomcat production environment is localhost:8080/rails/invoices

I can't seem to figure out how I can change the port and the document root (/invoices instead of /rails/invoices) in tomcat.

Any suggestions?

+1 vote
Getting 405 status from local Tomcat on Windows

I am running Tomcat 7.0.41 on a Windows laptop (8.1 Pro). I recently reinstalled the Windows and since re-installing tomcat and my server application, it runs fine when I connect to it from a web browser.

However, when I tell my desktop client app to connect to the server, it fails on the initial connection with a 405status. I am running the server is debug, from Eclipse, and have put breakpoints in the doGet, doPost, and doPut methods of my ControllerServlet class that extends the java.servlet.http.HttpServlet. None of these breakpoints fire before the client gets back the 405 status. (the client works fine if connecting to the real server running tomcat 6 on an Ubuntu server.)

I can find no place locally where verb filtering is being configured.

Any suggestions?

+3 votes
Tomcat: Getting 404 before the container starts all servlets

After upgrading Tomcat from 6.X to 7.X, our AJAX client receives 404 for 10-15 seconds right after startup. I presume the request is accepted and processed before all servlet are initialized, which is not what you
would expect.

Is this behavior normal for 7.X? Is there a way to configure 7.x to behave like 6.x?

+2 votes
Tomcat: mySQL connector error

I try to run www.icescrum.org on my Tomcat 7 on Ubuntu 12.04 with OpenJDK.

I have installed Tomcat with apt-get and also I have installed the libmysql-java package. On starting Tomcat it reports on a stacktrace log, that the mySQL connector is not found (java.lang.ClassNotFoundException: "com.mysql.jdbc.Driver").

So I have try to create a symlink in Tomcats lib dir to the jar file and try to modify the properties of the search paths:

common.loader=${catalina.base}/lib,${catalina.base}/lib/*.jar,${catalina.home}/lib,
${catalina.home}/lib/*.jar,/var/lib/tomcat7/common/classes,/var/lib/tomcat7/common/*.jar
server.loader=/var/lib/tomcat7/server/classes,/var/lib/tomcat7/server/*.jar
shared.loader=/var/lib/tomcat7/shared/classes,/var/lib/tomcat7/shared/*.jar

The JDBC mySQL Jar is stored under /usr/share/java with two symlinks, I have tried to create a symlink from Tomcats lib dir (/usr/share/tomcat7/lib) to ../../java/mysql.jar but the mySQL is also not loaded. The CATALINA_HOME is set to /usr/share/tomcat7 and the CATALINA_BASE is /var/lib/tomcat7, so imho it should be worked.

How can I create a working IceScrum with mySQL and a shared mySQL connector?

+1 vote
Tomcat closes websocket without any error receiving WebSocket ContinuationFrames

Has anyone had a large WS message sent as the response to an outbound call? We have a scenario where the request causes a 300K WS message to be sent back as the "response". The client is sending multiple WS continuation frames and after a couple of frames are successfully sent, Tomcat just closes the websocket connection. I the response fits in a single frame, it's fine. Where can I look to try and troubleshoot this?

...