E1 Export process very very slow and doesn't respond

Harsha_Sai_Manju_Sree

Hi,

We are facing strange issue for the first time. Since 3 days, the export process is horribly slow. It doesn't respond and is taking **** lot of time. For 200 objects, the export processing like "Processed 15 of 169 objects." started after 35 min.

For bigger projects, this takes more than an hr and at times, this doesnt even respond. After lot of debugging, I got hold of below error at the time of export in the vgndomain log.

Error:

####<Sep 29, 2010 10:49:48 AM UTC> <Error> <WebLogicServer> <us97uap199ampxb> <VgnVCMServer> <weblogic.health.CoreHealthMonitor> <<WLS Kernel>> <> <BEA-000337> <ExecuteThread: '12' for queue: 'weblogic.kernel.Default' has been busy for "888" seconds working on the request "Http Request: /vgn-wcm-up/secure/hierarchybase/getXML.jsp", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
####<Sep 29, 2010 10:49:48 AM UTC> <Error> <WebLogicServer> <us97uap199ampxb> <VgnVCMServer> <weblogic.health.CoreHealthMonitor> <<WLS Kernel>> <> <BEA-000337> <ExecuteThread: '19' for queue: 'weblogic.kernel.Default' has been busy for "888" seconds working on the request "Http Request: /vgn-wcm-up/secure/hierarchybase/getXML.jsp", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
####<Sep 29, 2010 11:00:26 AM UTC> <Error> <WebLogicServer> <us97uap199ampxb> <VgnVCMServer> <weblogic.health.CoreHealthMonitor> <<WLS Kernel>> <> <BEA-000337> <ExecuteThread: '12' for queue: 'weblogic.kernel.Default' has been busy for "1,526" seconds working on the request "Http Request: /vgn-wcm-up/secure/hierarchybase/getXML.jsp", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
####<Sep 29, 2010 11:00:26 AM UTC> <Error> <WebLogicServer> <us97uap199ampxb> <VgnVCMServer> <weblogic.health.CoreHealthMonitor> <<WLS Kernel>> <> <BEA-000337> <ExecuteThread: '25' for queue: 'weblogic.kernel.Default' has been busy for "1,009" seconds working on the request "com.vignette.as.server.ejb.ImportExportOpsBean_n2s9k0_EOImpl", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
####<Sep 29, 2010 11:00:26 AM UTC> <Error> <WebLogicServer> <us97uap199ampxb> <VgnVCMServer> <weblogic.health.CoreHealthMonitor> <<WLS Kernel>> <> <BEA-000337> <ExecuteThread: '9' for queue: 'weblogic.kernel.Default' has been busy for "1,223" seconds working on the request "Http Request: /vgn-wcm-up/secure/hierarchybase/getXML.jsp", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
####<Sep 29, 2010 11:00:26 AM UTC> <Error> <WebLogicServer> <us97uap199ampxb> <VgnVCMServer> <weblogic.health.CoreHealthMonitor> <<WLS Kernel>> <> <BEA-000337> <ExecuteThread: '19' for queue: 'weblogic.kernel.Default' has been busy for "1,525" seconds working on the request "Http Request: /vgn-wcm-up/secure/hierarchybase/getXML.jsp", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
 

 

Appreciate any help please...

GANESHKUMAR_JEYAPRAKASH

Dear Members/Readers,

As we have build an Custom Utility around the Vignette API to extract the GUID's from VCM and build/create/generate the XML's for Each content GUID's, which holds all the information like metadata,version,classifications pertaining to that GUID. As we are having roughly 7039 content id in our QA env,while running our utility for entire records (7039) we are able to run it for approx  for 1000 -2000 odd records, and our custom appplication gets into halted/hangup stage. And nothing is been processed further.

After 35 mins of halt/idle time, the VCM server seems to be up and our utility picks up processing the records from where it has left. And the total time it has taken to run the utility for the entire 7039 records is arounf 3 hours.

As it seems to be some form of perfromance issue, as well as the exception/error at the web logic server side also.when browsed in to the VgnVCMServer_output.log, we were able to get the below mentioned error.

--------------------------------

<Dec 10, 2013 10:08:33 PM EST> <Error> <WebLogicServer> <BEA-000337> <ExecuteThread: '23' for queue: 'weblogic.kernel.Default' has been busy for "1,061" seconds working on the request "connection144.session145", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
<Dec 10, 2013 10:18:33 PM EST> <Error> <WebLogicServer> <BEA-000337> <ExecuteThread: '23' for queue: 'weblogic.kernel.Default' has been busy for "1,661" seconds working on the request "connection144.session145", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
<Dec 10, 2013 10:27:43 PM EST> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM SYSIBM.SYSDUMMY1" set up for pool "VgnPool" failed with exception: "java.sql.SQLException: [Vignette Corp.][DB2 JDBC Driver]Connection timed out".>
<Dec 11, 2013 3:18:33 AM EST> <Error> <WebLogicServer> <BEA-000337> <ExecuteThread: '10' for queue: 'weblogic.kernel.Default' has been busy for "1,030" seconds working on the request "com.vignette.as.server.ejb.SiteOpsBean_o3ciu8_EOImpl", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
<Dec 11, 2013 3:28:33 AM EST> <Error> <WebLogicServer> <BEA-000337> <ExecuteThread: '10' for queue: 'weblogic.kernel.Default' has been busy for "1,630" seconds working on the request "com.vignette.as.server.ejb.SiteOpsBean_o3ciu8_EOImpl", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
<Dec 11, 2013 3:37:10 AM EST> <Error> <JDBC> <BEA-001112> <Test "SELECT 1 FROM SYSIBM.SYSDUMMY1" set up for pool "VgnPoolXA" failed with exception: "javax.transaction.xa.XAException: [Vignette Corp.][DB2 JDBC Driver]XAStart failed.".>

------------------------------------

Would request for any quick help and assistance on the above issue.

Appreciate any form of help in the above aspect.