How do I know if Event Subsystem is logging to SQL?

TeamSite 6.5 SP2 on Windows 2003
SQL 2000 on separate Windows 2003 server
MS JDBC drivers for SQL 2000 SP3

TeamSite install was configured to use the default (flat file). I used a combination of TeamSite 6.5 Admin Guide, KB articles, and Forum posts to set this up.

The Event Subsystem service starts and the log files appear to show that everything is set up correctly, but I don't see anything being added to the tables.

Find more posts tagged with

Comments

Migrateduser

There should be few entries in the DB tables at the eventsubsystem startup itself, even before the events gets published to it.
See the destination tables for topics.

Also when the events are generated like submit, the entry is made to the messages and messages_handle table. If the subscribers are up then the message is delivered and hence both the tables are cleaned up.
The eventsubsyetem will surelry log the error if there is any. If the above is case for your mesages clean up start the subscribers like search (basically indexer) in debug mode and you can see the entry there for the message received.

Migrateduser

If you have already made the subscriptions (see consumer table), you can stop the subscribers (like search) and hence see the entries being made to both the tables (though you will not be able to read the message there).

Corey_Null

That's what I was afraid of. Nothing is showing up in any of those tables, but there aren't any errors in the eventsubd_err.log file either. Unless anyone has any other ideas, I'll open a ticket with support.

Thanks for the reply.

Migrateduser

What about the "destination" table? If there are entries there at least eventSubD is taking to the DB.

If there are entries in the "consumer" table after you start search with the events enabled, the subscribers are okie.

If there is just the messages table which is empty, look for the proxyservelet logs in the web-app for any errors in publishing. Upload the jmsConfignew.xml, iw_bridge_config.xml (similar name? ) which will be in the Web-inf foler.

Corey_Null

I've opened a ticket with support and am getting ready to do a LiveMeeting with someone. There just isn't any data in any of the tables other than what gets added when you run the SQL querry to build the tables etc.

Migrateduser

>> There just isn't any data in any of the tables other than what gets added when you run the SQL querry to build the tables etc.No data is added from the sql-ddl. These are just the table and indexes creation scripts. If there is any data in the table the eventsubsystem is able to connect and push it into DB.

Replicate2.zip

Corey_Null

>> No data is added from the sql-ddl. These are just the table and indexes creation scripts. If there is any data in the table the eventsubsystem is able to connect and push it into DB.

I understand. My post was a little confusing. The tables and indexes are there. However, there is no data in the tables. Still waiting for support to get back to me on that LiveMeeting.

Migrateduser

CAn you upload your log and config files I pointed above. This should not be happening that it doesnt works and also does not logs errors Smiley Happy

Corey_Null

CAn you upload your log and config files I pointed above.

Do you have more information on the location and specific names (in Windows) of the files (other than jmsconfignew.xml) you are requesting? I've uploaded a new copy (after working with support) of the jmsconfignew.xml. We didn't change much other than some redundant entries (as you can see when compared to the original jmsconfignew.xml that I uploaded in my original post). Still no errors in the logs and no data in the database.

In fact, I'm positive that the event subsystem is connecting to the database because the SQL server would not let me delete the database (because something was attached to it), until after I stopped the event subsystem on the servers that I have configured. Support then had me delete the database and recreate it just in case.

One thing I found a little frustrating is that they (support) didn't know why a couple of my tables were named the way they were. They were named that way because of the MS SQL deadlock workaround (mentioned in other threads). I guess I would have expected them to know that on their own, but I told them about it anyway. I guess I still needed to delete and recreate the datbase as I had used the mssql.sql query to set up my database. Apparently that is for a different version of SQL server by a different 3rd party, not Microsoft. To me, "mssql" would indicate MicroSoft SQL, but they tell me that sqlserver.sql is the correct query to use to set the database up for MS SQL 2000 Server.

This should not be happening that it doesnt works and also does not logs errors .

And therin lies the reason why I created this thread and opened a ticket with Interwoven. Smiley Happy

Migrateduser

See all the database creation scripts in (C:\Interwoven\TeamSite\eventsubsystem\conf\ddl).
There should be none for the mssql (6.7.1). I think you might have confused with the MySQl which is yet another openSource DB.
You need to recreate the DB using the create_sqlserver.sql. Make sure that the deadLock script is there already or run this part manually before any start up.

Also note that there are different set of drivers for the 2000 ad 2005 version of MSSQL which differ in the drivername and connection url.
Sample:

url="jdbc:sqlserver://CPSW2K3:1433;databaseName=events;selectMethod=cursor"

      user="sa"  password="hgaur" maxActive="10" maxIdle="5" minIdleTime="1800"

       evictionInterval="3600"

Your OpenJMS config looks good.
The section AdministeredDestinations should populate all entries in the destination table if all is correct on eventSubsystem start up.
Also delete any openJMS.db, openjms.lock file and Logs in TeamSite\local\logs (eventsubd_err.log,eventsubd_out.log, eventsubd.log ) the in eventSubsystem folder before start.
Upload the log entries and database entries (if any).
--hemant

Corey_Null

I just don't know how to communicate the issue any more clearly than this:

I'm sorry that I got side-tracked on sort of a rant. I'm very familiar with MS SQL and MySQL, and am not confused. We're running TeamSite 6.5 on Windows and in the ddl directory, there are 7 files:
1- create_db2.sql
2- create_mssql.sql
3- create_mysql.sql
4- create_oracle.sql
5- create_sqlserver.sql
6- create_sybase.sql
7- create_sybaseanywhere.sql

Regardless of what should or should not be there, there is a create_mssql.sql file. On my first database, I admit that I was confused, and I ran the mssql.sql file becuase, to me, mssql means MS SQL and the Interwoven documentation didn't specify what file to use for MS SQL Server. I read the Administrator's Guide, but it doesn't say anything about the specific files. It just says to use the file named for the specific vendor's database that you're using.

I have now also read several KB articles and posts before I created this thread. For a list of them, see attached. I now have a DB that was created using the create_sqlserver.sql file and the problem still exists. I'm fairly certain that this isn't just something simple. I'm very good about spending the time to troubleshoot the simple issues and I certainly RTFM, and KB articles, and do search the forums, etc.

See the attached TXT for what I've done (that matters) up to this point. I also deleted the openjms.db file and the lock file. I'm not deleting any logs because I use them for troubleshooting. I will post the resolution once I discover it -hopefully with the help of IWOV Support.

Corey_Null

To fix this in my test environment, which is admittedly in really bad shape, I had to upgrade Log4J from 1.2.7 to 1.2.14 to get it to work. There are now rows of data in the messages table.

In my production environment, I went through the same steps that I've outlined in previous posts, and everything worked without having to upgrade Log4J. Go figure.

Interwoven Consulting is on-site next week to install and configure Report Center.

brizrobbo

Hi,

I've just installed TS 6.7.1 SP1 on a brand new Solaris 10 machine. I've got a similar problem using MySQL for the event reporting subsytem DB. The DB "seems" to be configured correctly as I get no errors in the eventsubd.log (or any other logs for that matter!). However, there are no additional rows showing up in the 'messages' table, despite events occurring.

Has anyone had a similar problem with using MySQL which they have resolved?

Cheers & thanks, Craig

Migrateduser

Hi,

I've just installed TS 6.7.1 SP1 on a brand new Solaris 10 machine. I've got a similar problem using MySQL for the event reporting subsytem DB. The DB "seems" to be configured correctly as I get no errors in the eventsubd.log (or any other logs for that matter!). However, there are no additional rows showing up in the 'messages' table, despite events occurring.

Has anyone had a similar problem with using MySQL which they have resolved?

Cheers & thanks, Craig

I don't recall if the log4j.xml file existed or if I created it, but it could help you out and show you some errors in a log file. Put it in /eventsubsystem/conf off of iwhome and bounce the subsystem. You'll probably want DEBUG to begin with, rather than WARN.

[HTML]

value="%d{HH:mm:ss.SSS} %-5p [%t] - %m\n"/>

value="%d{HH:mm:ss.SSS} %-5p [%t] - %m\n"/>

[/HTML]