Reporting database no getting updated

Successfully installed and configured teamsite reporting and crystal a few weeks ago. I was able to view one test report.

On two occasions now, I have found that the reporting database only gets updated after I have done a teamsite server restart.

I am running teamsite 6.5 sp 2 on windows 2003 server.

Extract from tsreport.log is below.....

WARN - Could not create JNDI context: javax.naming.NamingException: Failed to connect to JNDI provider [Root exception is java.net.ConnectException: Connection refused: connect]
19 Dec 2006 21:44:20,359

20 Dec 2006 15:22:37,875 ERROR - Error processing message
java.sql.SQLException: Io exception: Connection reset by peer: socket write error
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:180)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:222)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:335)
at oracle.jdbc.driver.OracleStatement.(OracleStatement.java:503)
at oracle.jdbc.driver.OracleConnection.privateCreateStatement(OracleConnection.java:683)
at oracle.jdbc.driver.OracleConnection.createStatement(OracleConnection.java:560)
at com.interwoven.tsreport.server.EventsSummaryTable.insert(EventsSummaryTable.java:66)
at com.interwoven.tsreport.server.TCoreMessage.handleMessage(TCoreMessage.java:29)
at com.interwoven.tsreport.server.TeamsiteListener.onMessage(TeamsiteListener.java:113)
at com.interwoven.tsreport.server.JmsListener.run(JmsListener.java:153)
at java.lang.Thread.run(Thread.java:534)

Any ideas on this one?

Find more posts tagged with

Comments

Migrateduser

Hi Rabs,
The reports are based on the TeamSite events coming throgh the TeamSite eventSubsystem by JMS messaging. Please ensure before starting the resport server that the eventsubsystem is up and the report Database server is running.
--hemant

Bill Klish

One of my clients just went through a bad experience with reporting/event sub system.

Our problem was the eventsubsystem was dying with out of memory errors, causing a backup of all messages, causing teamsite to not come back up, etc. We had 1.3 million events that were queued to be processed.

There are 2 KB articles you should look for, one which tells you how to prevent the out of memory error and a second which turns off DAS event publishing (unless of course you are using DAS).

We were using a MySQL 5 database to handle the events and reporting, not sure what you are using or if it matters.

From the looks of the error, it could be a network configuration issue. Can you login to your databases from a command line client from your teamsite server?

Migrateduser

What is the platform you have the database on and what is the teamSite version ?