nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Interwoven Event Subsystem service will not start

crazydazed

The Interwoven Event Subsystem service starts, but then shuts down less than a minute later. If I look at logs, I find the two below errors. Can anyone help point me in the right direction for troubleshooting as I have failed so far to resolve this issue. Thanks in advance.

..\servletd\logs\iweventproxy.log:
2008-03-03 14:42:50,395 [JMSBridge] ERROR com.interwoven.bridge100 () - Msg: Failed to connect to JNDI provider
2008-03-03 14:47:51,395 [JMSBridge] ERROR com.interwoven.bridge100 () - Unable connect to IWOV JNDI provider.

..\local\logs\eventsubd_err.log:
OpenJMS 0.7.6.1
The OpenJMS Group. (C) 1999-2004. All rights reserved.
http://openjms.sourceforge.net
org.exolab.jms.server.ServerException: org.exolab.jms.persistence.PersistenceException: org.exolab.core.foundation.FailedToCreateDatabaseException: Failed to create database openjms b/cjava.io.StreamCorruptedException: invalid stream header
at org.exolab.core.database.recman.PageManagedDatabase.(PageManagedDatabase.java:118)
at org.exolab.jms.persistence.ObjectAdapter.(ObjectAdapter.java:218)
at org.exolab.jms.persistence.DatabaseService.createJdbmAdapter(DatabaseService.java:258)
at org.exolab.jms.persistence.DatabaseService.(DatabaseService.java:166)
at org.exolab.jms.persistence.DatabaseService.instance(DatabaseService.java:115)
at org.exolab.jms.server.JmsServer.registerServices(JmsServer.java:274)
at org.exolab.jms.server.JmsServer.init(JmsServer.java:185)
at org.exolab.jms.server.JmsServer.main(JmsServer.java:229)

Find more posts tagged with

Comments

moonkhanna

The Interwoven Event Subsystem service starts, but then shuts down less than a minute later. If I look at logs, I find the two below errors. Can anyone help point me in the right direction for troubleshooting as I have failed so far to resolve this issue. Thanks in advance.

..\servletd\logs\iweventproxy.log:
2008-03-03 14:42:50,395 [JMSBridge] ERROR com.interwoven.bridge100 () - Msg: Failed to connect to JNDI provider
2008-03-03 14:47:51,395 [JMSBridge] ERROR com.interwoven.bridge100 () - Unable connect to IWOV JNDI provider.

..\local\logs\eventsubd_err.log:
OpenJMS 0.7.6.1
The OpenJMS Group. (C) 1999-2004. All rights reserved.
http://openjms.sourceforge.net
org.exolab.jms.server.ServerException: org.exolab.jms.persistence.PersistenceException: org.exolab.core.foundation.FailedToCreateDatabaseException: Failed to create database openjms b/cjava.io.StreamCorruptedException: invalid stream header
at org.exolab.core.database.recman.PageManagedDatabase.(PageManagedDatabase.java:118)
at org.exolab.jms.persistence.ObjectAdapter.(ObjectAdapter.java:218)
at org.exolab.jms.persistence.DatabaseService.createJdbmAdapter(DatabaseService.java:258)
at org.exolab.jms.persistence.DatabaseService.(DatabaseService.java:166)
at org.exolab.jms.persistence.DatabaseService.instance(DatabaseService.java:115)
at org.exolab.jms.server.JmsServer.registerServices(JmsServer.java:274)
at org.exolab.jms.server.JmsServer.init(JmsServer.java:185)
at org.exolab.jms.server.JmsServer.main(JmsServer.java:229)

First, you should contact Support. Second, which version SP of TS are you on and on what platform?

Migrateduser

what databse are you using for the eventSubsystem. Note that the flat file DB is not supported for the production. You should delete openjms.* files in the eventSubsystem directory in case the above is true to reinitialize the things. 6.7.1 sp1 comes with the OOTB derby Db and this can be used for the small production environments.
Please upload openjmsconfignew.xml configuration file.
--hemant

dinaish20

hi all

even I am getting error in the iweventproxy.log file.
2008-07-17 14:59:26,529 [JMSBridge] ERROR com.interwoven.bridge100 () - Unable connect to IWOV JNDI provider.
2008-07-17 14:59:26,547 [JMSBridge] ERROR com.interwoven.bridge100 () - Msg: Failed to connect to JNDI provider

I thought the port between teamsite server and db is not opened, so we established that too but error didnt changed........

I am usign TS6.7 with Solaris 10 with Oracle DB 10g Enterprise Edition Release 10.2.0.3.0....
any pointers will help me a lot.....

thanks
dinesh

moonkhanna

hi all

even I am getting error in the iweventproxy.log file.
2008-07-17 14:59:26,529 [JMSBridge] ERROR com.interwoven.bridge100 () - Unable connect to IWOV JNDI provider.
2008-07-17 14:59:26,547 [JMSBridge] ERROR com.interwoven.bridge100 () - Msg: Failed to connect to JNDI provider

I thought the port between teamsite server and db is not opened, so we established that too but error didnt changed........

I am usign TS6.7 with Solaris 10 with Oracle DB 10g Enterprise Edition Release 10.2.0.3.0....
any pointers will help me a lot.....

thanks
dinesh

Did you try the solution pointed out by Hemant as below -

what databse are you using for the eventSubsystem. Note that the flat file DB is not supported for the production. You should delete openjms.* files in the eventSubsystem directory in case the above is true to reinitialize the things. 6.7.1 sp1 comes with the OOTB derby Db and this can be used for the small production environments.
Please upload openjmsconfignew.xml configuration file.
--hemant

dinaish20

Did you try the solution pointed out by Hemant as below -

what databse are you using for the eventSubsystem. Note that the flat file DB is not supported for the production. You should delete openjms.* files in the eventSubsystem directory in case the above is true to reinitialize the things. 6.7.1 sp1 comes with the OOTB derby Db and this can be used for the small production environments.
Please upload openjmsconfignew.xml configuration file.
--hemant

thanks for ur response...
it is oracle db....and i did find any openjms file in iw-home/eventSubsystem directory.... i tired to run eventsubsytem via CLT ...i got the error
http://openjms.sourceforge.net
org.exolab.jms.server.ServerException: org.exolab.jms.persistence.PersistenceException: org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory, cause:
java.sql.SQLException: Protocol violation
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:180)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:222)
...

i was searching this error also couldnt find results in forums....

thanks
dinesh

Faizi

Have you set all the jar for DB Connection file file in "eventsubsystem.properties".

And check the "jmsconfignew.xml" file and put the correct value in

driver="_JDBC_DRIVER_"
url="_JDBC_URL_"
user="_DB_USER_"
password="_DB_PASSWD_"

crazydazed

I just wanted to say sorry for not replying to the threads in regards to my issue, but today was the first notification I got that this thread was updated.

We no longer have the issue. Unfortunately, I cannot find any emails confirming the solution. From memory, I think a reboot of the entire server fixed my problem.

Thanks,
DI

usingsuppressdublicatesandgroupibg.pdf

ResultTable.bmp

dinaish20

Thanks to all for replying

Have you set all the jar for DB Connection file file in "eventsubsystem.properties".

And check the "jmsconfignew.xml" file and put the correct value in

driver="_JDBC_DRIVER_"
url="_JDBC_URL_"
user="_DB_USER_"
password="_DB_PASSWD_"
__________________
abc

yes these values are correct....

driver="oracle.jdbc.driver.OracleDriver"
url="dbc Smiley Surprised

racle:thin:@valizprd219.val.cummins.com:1526:tsevtvp1"
user="*****"
password="****"
maxActive="10"
maxIdle="5"
minIdleTime="1800"
evictionInterval="3600" />

I am able to connect it via toad....

I just wanted to say sorry for not replying to the threads in regards to my issue, but today was the first notification I got that this thread was updated.

We no longer have the issue. Unfortunately, I cannot find any emails confirming the solution. From memory, I think a reboot of the entire server fixed my problem.

Thanks,
DI

today we got our database restarted....but error didnt change.....do u mean restart the db instance or the entire server..(if thr is any difference b/w two)....can we test it be changing db settings now...

thanks and regards
dinesh

Protocol_Settings.rptdesign

suppress.pdf

crazydazed

I am fairly sure that I ended up rebooting the entire box as I did not have luck with rebooting individual services.

I have not done a lot with teamsite and thus, I do not know the answers to any of your other questions. Sorry.

Thanks,
DI