Messages

1

QueueMetrics installation / Re: 1.5 Startup Problem

« on: December 09, 2008, 20:16:47 »

I don't understand why, but once the server was rebooted (for the second time), the problem went away.  DBTest worked, I was able to update the tables and the system operates as expected.

Do you have any idea what could have caused this?  Is there a problem with the init.d script that would not permit a clean restart?

2

QueueMetrics installation / Re: 1.5 Startup Problem

« on: December 09, 2008, 18:52:42 »

I have reviewed the web.xml and configuration.properties files.  All the settings appear correct.  When restarting, I am still getting a "connection timed out" error:

[root@pbx queuemetrics-1.5.0]# service queuemetrics restart
Stopping QueueMetrics: Using CATALINA_BASE:   /usr/local/queuemetrics/tomcat
Using CATALINA_HOME:   /usr/local/queuemetrics/tomcat
Using CATALINA_TMPDIR: /usr/local/queuemetrics/tomcat/temp
Using JAVA_HOME:       /usr/local/queuemetrics/java
Catalina.stop: java.net.ConnectException: Connection timed out
java.net.ConnectException: Connection timed out
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
        at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
        at java.net.Socket.connect(Socket.java:519)
        at java.net.Socket.connect(Socket.java:469)
        at java.net.Socket.<init>(Socket.java:366)
        at java.net.Socket.<init>(Socket.java:179)
        at org.apache.catalina.startup.Catalina.stopServer(Catalina.java:410)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.apache.catalina.startup.Bootstrap.stopServer(Bootstrap.java:336)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:427)
Starting QueueMetrics:  Using CATALINA_BASE:   /usr/local/queuemetrics/tomcat
Using CATALINA_HOME:   /usr/local/queuemetrics/tomcat
Using CATALINA_TMPDIR: /usr/local/queuemetrics/tomcat/temp
Using JAVA_HOME:       /usr/local/queuemetrics/java
[root@pbx queuemetrics-1.5.0]#

3

QueueMetrics installation / 1.5 Startup Problem

« on: December 09, 2008, 16:09:57 »

I installed v1.5.0 via yum this morning and the following error appears when starting the application:

Alert:
Errore JDBC:java.sql.SQLException: Server connection failure during transaction. Due to underlying exception: 'java.net.SocketException: java.net.ConnectException: Connection timed out'. -  - ** BEGIN NESTED EXCEPTION **  -  - java.net.SocketException - MESSAGE: java.net.ConnectException: Connection timed out -  - STACKTRACE: -  - java.net.SocketException: java.net.ConnectException: Connection timed out -    at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:156) -    at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:284) -    at com.mysql.jdbc.Connection.createNewIO(Connection.java:2680) -    at com.mysql.jdbc.Connection.<init>(Connection.java:1485) -    at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266) -    at java.sql.DriverManager.getConnection(DriverManager.java:525) -    at java.sql.DriverManager.getConnection(DriverManager.java:193) -    at it.loway.tpf.transaction.servlets.LowayTransactionController.serveRequest(Unknown Source) -    at it.loway.tpf.transaction.servlets.LowayTransactionController.serveRequestWrapper(Unknown Source) -    at it.loway.tpf.transaction.servlets.LowayTransactionController.doGet(Unknown Source) -    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:118) -    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.coyote.http11.Http11Processor.process(Http11Processor.java:799) -    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705) -    at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577) -    at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) -    at java.lang.Thread.run(Thread.java:595) -  -  - ** END NESTED EXCEPTION ** -  -  - Attempted reconnect 3 times. Giving up.

Why is this timing out again?  I finally was able to get 1.4.7 to run properly with mySQL, now the upgrade to 1.5.0 appears to have broken everything.

Suggestions?

4

QueueMetrics installation / Re: Unable to Start QueueMetrics

« on: December 08, 2008, 20:58:13 »

That fixed it.  The problem was resolved by adding the server name to the list of hosts for access to the database.  By default, QueueMetrics uses "localhost".  Unfortunately, the way I connect requires either "Any" or the host name to attach. 

Thank you for your help.

5

QueueMetrics installation / Re: Unable to Start QueueMetrics

« on: December 03, 2008, 19:38:10 »

The application worked for a short period of time and now is displaying the following error when I attempt to connect:

"Errore JDBC:java.sql.SQLException: Server connection failure during transaction. Due to underlying exception: 'java.net.SocketException: java.net.ConnectException: Connection timed out'. - - ** BEGIN NESTED EXCEPTION ** - - java.net.SocketException - MESSAGE: java.net.ConnectException: Connection timed out - - STACKTRACE: - - java.net.SocketException: java.net.ConnectException: Connection timed out - 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 java.sql.DriverManager.getConnection(DriverManager.java:525) - at java.sql.DriverManager.getConnection(DriverManager.java:193) - at it.loway.tpf.transaction.servlets.LowayTransactionController.serveRequest(Unknown Source) - at it.loway.tpf.transaction.servlets.LowayTransactionController.serveRequestWrapper(Unknown Source) - at it.loway.tpf.transaction.servlets.LowayTransactionController.doGet(Unknown Source) - 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:118) - 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.coyote.http11.Http11Processor.process(Http11Processor.java:799) - at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705) - at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577) - at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) - at java.lang.Thread.run(Thread.java:595) - - - ** END NESTED EXCEPTION ** - - - Attempted reconnect 3 times. Giving up."

This error occurred after rebooting the server.  Any suggestions?

6

QueueMetrics installation / Re: Unable to Start QueueMetrics

« on: November 13, 2008, 16:41:43 »

It appears that I didn't wait long enough.  The following occurs:

Catalina.stop: java.net.ConnectException: Connection timed out
java.net.ConnectException: Connection timed out
   at java.net.PlainSocketImpl.socketConnect(Native Method)
   at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
   at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
   at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
   at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
   at java.net.Socket.connect(Socket.java:519)
   at java.net.Socket.connect(Socket.java:469)
   at java.net.Socket.<init>(Socket.java:366)
   at java.net.Socket.<init>(Socket.java:179)
   at org.apache.catalina.startup.Catalina.stopServer(Catalina.java:410)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:585)
   at org.apache.catalina.startup.Bootstrap.stopServer(Bootstrap.java:336)
   at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:427)
Starting QueueMetrics:  Using CATALINA_BASE:   /usr/local/queuemetrics/tomcat
Using CATALINA_HOME:   /usr/local/queuemetrics/tomcat
Using CATALINA_TMPDIR: /usr/local/queuemetrics/tomcat/temp
Using JAVA_HOME:       /usr/local/queuemetrics/java

How does QueueMetrics address the local mySQL server and databases.  I am assuming that it is using the root connection or the javadude user name assigned when installing.  Is this a typeo somewhere?  Where do I look?

7

QueueMetrics installation / Re: Unable to Start QueueMetrics

« on: November 13, 2008, 16:38:30 »

Unfortunately, that didn't work.  When executing the restart command, the following appears:

/etc/rc.d/init.d/queuemetrics restart ..

Stopping QueueMetrics: Using CATALINA_BASE:   /usr/local/queuemetrics/tomcat
Using CATALINA_HOME:   /usr/local/queuemetrics/tomcat
Using CATALINA_TMPDIR: /usr/local/queuemetrics/tomcat/temp
Using JAVA_HOME:       /usr/local/queuemetrics/java

... and then it just sits there.  Nothing further appears to occur.  No errors, nothing.

8

QueueMetrics installation / Unable to Start QueueMetrics

« on: November 13, 2008, 04:13:34 »

Server:  CentOS 5.2
Asterisk Version:  1.4.21.2

QueueMetrics installed via YUM.  Installed without issue.

Tomcat Root:  /usr/local/queuemetrics/tomcat/webapps/ROOT/
QueueMetrics Root:  /usr/local/queuemetrics/webapps/queuemetrics-1.4.7/

Logical link queuemetrics exists

Unable to start with http://servername:8080/queuemetrics or http://servername:8080/queuemetrics-1.4.7

Tomcat starts with http://servername:8080 and all servlets appear to be working properly.

QueueMetrics will not start.  I receive "Loading..." and that's it.  What am I missing?