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; } } }

TeamSite production server is down 6.7.2 SP2 due to some issue with EventSubsystem.

gopi123

Hi,

We are not sure why database issue is occuring same issue we got on last Monday so we disabled EventSubsystem and try to restarted the TS server and did iwreset -a and then TeamSite is up.

Today again it is trying to connect the Eventsubsystem which is disabled in iw.cfg file we are not sure what may be the issue. Please find below the log from eventsubsystem log.

Please check and help me as early as possible this is production server. Any ideas and let me know how to resolve......

iweventsubd: ---------- STARTING: Tue Aug 5 10:44:58 EDT 2014

EVENTSUBD_HOME is set to /usr/iw-home/eventsubsystem

OpenJMS 0.7.6.1

http://openjms.sourceforge.net

org.exolab.jms.server.ServerException: org.exolab.jms.persistence.PersistenceException: org.apache.commons.dbcp.SQLNestedException: Borrow prepareStatement from pool failed, cause:

java.sql.SQLException: Schema 'USR' does not exist

at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source)

at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)

at org.apache.derby.client.am.Connection.prepareStatement(Unknown Source)

at org.apache.commons.dbcp.PoolingConnection.makeObject(PoolingConnection.java:223)

at org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:792)

at org.apache.commons.dbcp.PoolingConnection.prepareStatement(PoolingConnection.java:130)

at org.apache.commons.dbcp.DelegatingConnection.prepareStatement(DelegatingConnection.java:216)

at org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.prepareStatement(PoolingDataSource.java:323)

at org.exolab.jms.persistence.RDBMSAdapter.getSchemaVersion(RDBMSAdapter.java:875)

at org.exolab.jms.persistence.RDBMSAdapter.<init>(RDBMSAdapter.java:182)

at org.exolab.jms.persistence.DatabaseService.createRdbmsAdapter(DatabaseService.java:236)

at org.exolab.jms.persistence.DatabaseService.<init>(DatabaseService.java:163)

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)

Caused by: org.apache.derby.client.am.SqlException: Schema 'USR' does not exist

at org.apache.derby.client.am.Statement.completeSqlca(Unknown Source)

at org.apache.derby.client.net.NetStatementReply.parsePrepareError(Unknown Source)

at org.apache.derby.client.net.NetStatementReply.parsePRPSQLSTTreply(Unknown Source)

at org.apache.derby.client.net.NetStatementReply.readPrepareDescribeOutput(Unknown Source)

at org.apache.derby.client.net.StatementReply.readPrepareDescribeOutput(Unknown Source)

at org.apache.derby.client.net.NetStatement.readPrepareDescribeOutput_(Unknown Source)

at org.apache.derby.client.am.Statement.readPrepareDescribeOutput(Unknown Source)

at org.apache.derby.client.am.PreparedStatement.readPrepareDescribeInputOutput(Unknown Source)

at org.apache.derby.client.am.PreparedStatement.flowPrepareDescribeInputOutput(Unknown Source)

at org.apache.derby.client.am.PreparedStatement.prepare(Unknown Source)

at org.apache.derby.client.am.Connection.prepareStatementX(Unknown Source)

... 14 more

Find more posts tagged with

Comments

Reji Varghese

Trying stopping eventsubsystem, iweventsubd
Stop OpenDeploy. I have seen instances where eventsubsytem is hooked to the OpenDeploy process

Truncate the following tables from the schema configure in jmsconfignew.xml

TRUNCATE TABLE message_handles;
TRUNCATE TABLE messages;

Start OpenDeploy

Check for any errors !

gopi123

I am not able to connect to database at all using "usr". I tried to connect using sql developer by giving values from jmsconfignew.xml. How Can i truncate the tables what is the way to do that....

Thanks for your quick response. If I truncate at any possible nothing to worry right because eventsusbsystem is not neccessary for Teamsite.

Appreciate your help!!!!!

Regards

Gopi

Rick Poulin

Sounds like the issue is with your database and not teamsite. Contact your DBAs and inquire about the status of this schema, and if any permissions might have changed recently.

Didn't notice that the stack trace pointed to derby, as mentioned by nipper below. Your DB probably crapped out. Derby still exists, so you might be able to find some legacy documentation and figure out how to resurrect it.. but you should be planning your TS upgrade pronto.

nipper

You will need to find someone with the authority to log into the DB and make the changes.

Now one point, in 6.7.2 (which has been EOL for multiple years) turning off eventsubsystem WAS NOT done in iw.cfg, no matter the flag that existed, it didn't work.

I would suggest get a DBA that can help with Derby. You can call support, but 6.7.2 is EOL and Derby is not a supported DB anymore, so your chances of help are slim.

gopi123

Please let me know is this the right way I am connecting the Derby database. When I am trying to test in my Dev box no message is coming as successful is any message will prompt or it is success.

ij>connect 'jdbc:derby://localhost:1527//usr/iwhome/eventsubsystem/openjmsdb;create=false;;user=usr;password=usr';

This is the DB config file

<RdbmsDatabaseConfiguration

driver="org.apache.derby.jdbc.ClientDriver"

url="jdbc:derby://localhost:1527//usr/iw-home/eventsubsystem/openjmsdb;create=true"

user="usr"

password="usr"

maxActive="10"

maxIdle="5"

minIdleTime="1800"

evictionInterval="3600" />

</DatabaseConfiguration>

Reji Varghese

Looks like its database is located on your local filesystem.

How is the disk space on the filesystem, /usr/iw-home/eventsubsystem/openjmsdb. Does it have enough space ?

Look if there are any files by these names or at this location ?

gopi123

We have a plan to upgrade to 7.4.1 from current version but in the mean time we need to support current production server 6.7.2 version.

I am able to connect to Derby Db in prod but not able to see any tables in my DB is that any specific reason or i need to start event subsystem to look at the tables.

ken-inwprd01>pwd
/usr/iw-home/derby/bin
ken-inwprd01>./ij
ij version 10.2
ij> connect 'jdbc:derby://localhost:1527//usr/iw-home/eventsubsystem/openjmsdb;create=true;user=usr;password=usr';
ij> show tables;
TABLE_SCHEM |TABLE_NAME |REMARKS
------------------------------------------------------------------------

0 rows selected
ij>

If I am able to connect to Derby DB why in the logs it says

org.exolab.jms.server.ServerException: org.exolab.jms.persistence.PersistenceException: org.apache.commons.dbcp.SQLNestedException: Borrow prepareStatement from pool failed, cause:

java.sql.SQLException: Schema 'USR' does not exist

Reji Varghese

Do you have DAS enabled ? That could be the reason why DAS events are being published to the eventsubsystem.

If DAS is not used, disable it.

There should be a place where all the iwevents are stored, like /iw-home/local/logs/iwevents/. It would be a good idea to delete all the files under this directory.

Kalam

Hi Gopi,

Take the backup of /Interwoven/TeamSite/eventsubsystem/openjmsdb.

Rebuild the eventsubsystem db, Stop the teamsite and eventsubsystem by deleting the /Interwoven/TeamSite/eventsubsystem/openjmsdb.

Restart the teamsite to create a new DB

If still you get the error, execute the following

Now /etc/init.d/iw.derby stop
/Interwoven/TeamSite/private/bin/iweventsubd stop
cd /apps/Interwoven/TeamSite/derby/bin

./ij
connect 'jdbc:derby://localhost:1527//apps/Interwoven/TeamSite/eventsubsystem/openjmsdb;create=false;user=usr;';
run '/apps/Interwoven/TeamSite/eventsubsystem/conf/ddl/create_derby.sql';
exit;
/apps/Interwoven/TeamSite/private/bin/iweventsubd start
/etc/init.d/iw.derby start

gopi123

We are using DataDeploy to update metadata in Database so we are enabled DAS.

As of now we stoped OpenDeploy , stoped Eventsubsystem and restarted the Teamsite , did iwreset -a and after that Teamsite is up and running.

But I am not sure this issue will occur again.... if it occurs again I can recreate the Derby DB once again is that make sense..

Please let me know.

Regards

Gopi

nipper

> We are using DataDeploy to update metadata in Database so we are enabled DAS.

Just because you use DD does not mean you use DAS. You probably don't. You can turn that off in the odbase.xml file.

gopi123

we recreated the Derby Database tables with the given steps and it got created but when we start eventsubsystem it is throwing an error.

Everyweek on Monday our production server is gowing down and we are trying to follow the some of the steps to TS up

1. Stop opendeploy

2. Stop event subsystem (which is not currently woring because of this everytime it is trying to connect the DB which is causing the TS down)

3. Stop Teamsite

4. Restart the TS

5. Running the iwreset -a

6. Able to login to TS UI and statting opendeploy.

We are using the above steps for timebeing but we want to resolve the above issue permanently so we are trying to create Derby DB and want to run Event subsystem but once we create Db tables the event subsystem is still not running when we start.

Please let me know what may be the issue and are we missing any steps hee.

EVENTSUBD_HOME is set to /usr/iw-home/eventsubsystem

OpenJMS 0.7.6.1

http://openjms.sourceforge.net

org.exolab.jms.server.ServerException: org.exolab.jms.persistence.PersistenceException: java.sql.SQLException: An SQL data change is not permitted for a read-only connection, user or database.

at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source)

at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)

at org.apache.derby.client.am.PreparedStatement.executeUpdate(Unknown Source)

at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:233)

at org.exolab.jms.persistence.RDBMSAdapter.initSchemaVersion(RDBMSAdapter.java:908)

at org.exolab.jms.persistence.RDBMSAdapter.<init>(RDBMSAdapter.java:184)

at org.exolab.jms.persistence.DatabaseService.createRdbmsAdapter(DatabaseService.java:236)

at org.exolab.jms.persistence.DatabaseService.<init>(DatabaseService.java:163)

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)

Caused by: org.apache.derby.client.am.SqlException: An SQL data change is not permitted for a read-only connection, user or database.

at org.apache.derby.client.am.Statement.completeExecute(Unknown Source)

at org.apache.derby.client.net.NetStatementReply.parseEXCSQLSTTreply(Unknown Source)

at org.apache.derby.client.net.NetStatementReply.readExecute(Unknown Source)

at org.apache.derby.client.net.StatementReply.readExecute(Unknown Source)

at org.apache.derby.client.net.NetPreparedStatement.readExecute_(Unknown Source)

at org.apache.derby.client.am.PreparedStatement.readExecute(Unknown Source)

at org.apache.derby.client.am.PreparedStatement.flowExecute(Unknown Source)

at org.apache.derby.client.am.PreparedStatement.executeUpdateX(Unknown Source)

nipper

The log is telling. The DB is either down or not configured correctly. I would suspect that the user that ESS uses to connect to Derby does not have DBO authority or something like that.

Keep in front of your DBA because they are the ones who can fix this.