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

iwreset -ui

rob_liem

I've executed this CLT a couple of times now as sudo on a TS 6.5 SP 2. Both times, it crashed ContentCenter. What could be causing this ?

Find more posts tagged with

Comments

nipper

It looks like you are using the OOTB DB (OpenJMS) how long have you been running with it ? There is a bug where it gets too big and you need to clean it up.

Andy

Migrateduser

Are you using the flatfile DB (1) or some external RDBMS (2)?
Clean the openJMS.* files from the $TSHOME/eventsubsystem if 1
else bump up the max memory (-xmx) for the openJMS start.

Migrateduser

Better to use MySQL or disable eventSubsystem if the RDBMS option is not feasible.

rob_liem

Thx for the reply.

Are you using the flatfile DB (1) or some external RDBMS (2)?
Clean the openJMS.* files from the $TSHOME/eventsubsystem if 1
else bump up the max memory (-xmx) for the openJMS start.

It's running on an external Oracle RDBMS. What do you mean by "cleaning" up the openJSM.* files ? BTW, there are only 2 files of openjms.lg and openjms.db. The file sizes are insignificant.

We've been running w/ this since 2005. BTW, how do you restart openjms ?

nipper

What OS ? In DOS use services.

Unix, I am not certain but it may be iwhome/private/bin/iweventsubd

Migrateduser

Ok. So this is oracle. Probably your DB has over grown and needs a clean up. The oprnJMS.* files were mainly for the flat file. The lock file should go away with the stopping of eventSubsystem. Look at your DB and delete all messages (identified with messageID) in the messages table which do not have entry in the messages_handle table. Also check for the DAS publishing switch off in case you dont use DAS (publishing to teamsite_user topic). These messages are also piled up in DB as DAS subscriber is not there. The numbers of rows for each consumer in the message_handles tells about the pending messages for each consumer (see the consumer table for consumer_ID ).

Migrateduser

Check out following KB articles:
How to Disable the Publish Of DAS Events
Event Subsystem Displays Out of Memory Message While Connecting to Database

rob_liem

Check out following KB articles:
How to Disable the Publish Of DAS Events
Event Subsystem Displays Out of Memory Message While Connecting to Database

Thx. I resolved the OpenJMS issue. The solution is spelled out in your 2nd article. As for your 1st article, what're DAS events ? Do you think this could be responsible for the following error of :
29 Nov 2007 17:17:24,612 WARN - Message property type has no matching table column
29 Nov 2007 17:17:24,612 WARN - Message property type has no matching table column
29 Nov 2007 17:17:25,902 ERROR - Caught CSException in getEvents: com.interwoven.cssdk.common.CSObjectNotFoundException: (Object being looked up was not found)

Migrateduser

Thx. I resolved the OpenJMS issue. The solution is spelled out in your 2nd article. As for your 1st article, what're DAS events ? Do you think this could be responsible for the following error of :
29 Nov 2007 17:17:24,612 WARN - Message property type has no matching table column
29 Nov 2007 17:17:24,612 WARN - Message property type has no matching table column
29 Nov 2007 17:17:25,902 ERROR - Caught CSException in getEvents: com.interwoven.cssdk.common.CSObjectNotFoundException: (Object being looked up was not found)

DAS events are used by the products like OpenDeploy etc. They cause the additional load on the JMS engine if they are not being used and also messages pile up forever in the pre 6.7.1 sp1 releases. Better to disable this in the firstplace.

Migrateduser

Look for the consumers tables your es data base. This will tell you about who all is subscribing to which topics. The DAS topic is teamsite_user and if there are no subscribers to this you can disable this.