Websphere’s “may be hung”..

Got this interesting case in Support today.

Jira 3.13.3, WebSphere 6.1, Oracle10g 10.2.0.1.0
I attempted to upgrade from 3.12.3 to 3.13.3. I backed up the data from 3.12.3 via the administration function. I installed 3.13.3 successfully and configured it and everything was good. However whenever I try to reimport the backed up data the system sits there forever. WebSphere reports eventually that a thread has been active for too long and may be hung, and that’s the last I hear.

This is from the Websphere log:

******************************************************************************
JIRA 3.13.3 build: 344 (Enterprise Edition) started. You can now access JIRA through your web browser.
******************************************************************************************************
…
[5/5/09 10:16:45:674 EST] 000000fc ServletWrappe I SRVE0242I: [atlassian-jira-3_13_3_oracle_websphere_NewJira_war] [/jira.3.13.3] [global.css]: Initialization successful.
[5/5/09 10:16:52:714 EST] 00000167 ServletWrappe I SRVE0242I: [atlassian-jira-3_13_3_oracle_websphere_NewJira_war] [/jira.3.13.3] [/views/setup-import.jsp]: Initialization successful.
[5/5/09 10:17:54:442 EST] 00000167 SystemOut O 2009-05-05 10:17:54,442 WebContainer : 65 INFO [jira.action.admin.DataImport] Running data import

[5/5/09 10:17:54:442 EST] 00000167 QuartzSchedul I org.quartz.core.QuartzScheduler shutdown Scheduler JiraQuartzScheduler_$_NON_CLUSTERED shutting down.
[5/5/09 10:17:54:442 EST] 00000167 QuartzSchedul I org.quartz.core.QuartzScheduler pause Scheduler JiraQuartzScheduler_$_NON_CLUSTERED paused.
[5/5/09 10:17:54:452 EST] 00000167 QuartzSchedul I org.quartz.core.QuartzScheduler shutdown Scheduler JiraQuartzScheduler_$_NON_CLUSTERED shutdown complete.
[5/5/09 10:17:54:513 EST] 00000167 SystemOut O 2009-05-05 10:17:54,513 WebContainer : 65 INFO [jira.action.admin.DataImport] Importing data..

[5/5/09 10:17:54:663 EST] 00000167 SystemOut O 2009-05-05 10:17:54,663 WebContainer : 65 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser

[5/5/09 10:18:08:002 EST] 00000167 SystemOut O 2009-05-05 10:18:08,002 WebContainer : 65 INFO [jira.action.admin.DataImport] XML successfully parsed

[5/5/09 10:18:08:002 EST] 00000167 SystemOut O 2009-05-05 10:18:08,002 WebContainer : 65 INFO [jira.action.admin.DataImport] Removing all entries from the database.

[5/5/09 10:18:08:002 EST] 00000167 SharedPool I J2CA0086W: Shareable connection MCWrapper id 32703270 Managed connection WSRdbManagedConnectionImpl@19f619f6 State:STATE_TRAN_WRAPPER_INUSE
from resource jdbc/NewJira was used within a local transaction containment boundary.
[5/5/09 10:18:35:111 EST] 00000167 SystemOut O 2009-05-05 10:18:35,111 WebContainer : 65 INFO [jira.action.admin.DataImport] All entries removed.

[5/5/09 10:18:35:111 EST] 00000167 SystemOut O 2009-05-05 10:18:35,111 WebContainer : 65 INFO [jira.action.admin.DataImport] Started storing 129034 Generic Values

[5/5/09 10:33:22:968 EST] 00000029 ThreadMonitor W WSVR0605W: Thread “WebContainer : 65″ (00000167) has been active for 928906 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung.
…

Hung or not hung? Quite sure that JIRA would take longer than 15 minutes to redeploy 129034 entities. Would it?

Links:

* http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/index.jsp?topic=/com.ibm.iea.was_v6/was/6.0/PD/WASv6_Hung_Thread_Detection/player.html
* http://www-01.ibm.com/support/docview.wss?uid=swg21212442