Timeouts in org.jboss.test.deployers.seam.test.Seam*ExampleUnitTestCase ----------------------------------------------------------------------- Key: JBAS-7659 URL: https://jira.jboss.org/jira/browse/JBAS-7659 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-6.0.0.M2 SeamDvdExampleUnitTestCase and SeamNumberguessExampleUnitTestCase, both part of the tests-profileservice target, are timing out on the hudson runs. They pass for me locally. Looking through the logs at http://hudson.qa.jboss.com/hudson/job/JBoss-AS-6.0.x-testSuite-sun16/524/... it seems the problem is an inability to resolve an xsd: 2010-01-26 13:23:42,577 DEBUG [org.jbpm.persistence.db.DbPersistenceService] (WorkerThread#0[10.16.95.21:39912]) closing hibernate session 2010-01-26 13:23:42,587 DEBUG [org.jbpm.svc.Services] (WorkerThread#0[10.16.95.21:39912]) closing service 'tx': org.jbpm.tx.TxService@9ddd71 2010-01-26 13:23:42,587 DEBUG [org.jboss.seam.Component] (WorkerThread#0[10.16.95.21:39912]) instantiating Seam component: org.jboss.seam.core.resourceLoader 2010-01-26 13:23:42,587 DEBUG [org.jboss.seam.Component] (WorkerThread#0[10.16.95.21:39912]) initializing new instance of: org.jboss.seam.core.resourceLoader 2010-01-26 13:23:42,587 DEBUG [org.jboss.seam.Component] (WorkerThread#0[10.16.95.21:39912]) done initializing: org.jboss.seam.core.resourceLoader 2010-01-26 13:23:42,588 DEBUG [org.jboss.seam.util.Resources] (WorkerThread#0[10.16.95.21:39912]) Loaded resource from context classloader: newuser.jpdl.xml 2010-01-26 13:23:42,588 DEBUG [org.jbpm.configuration.JbpmContextInfo] (WorkerThread#0[10.16.95.21:39912]) creating jbpm context with service factories '[]' 2010-01-26 13:23:42,588 DEBUG [org.jbpm.JbpmContext] (WorkerThread#0[10.16.95.21:39912]) creating org.jbpm.JbpmContext@1600573 2010-01-26 13:23:42,592 DEBUG [org.jbpm.jpdl.xml.JpdlParser] (WorkerThread#0[10.16.95.21:39912]) resolving schema reference publicId(null) systemId(http://jboss.com/products/seam/pageflow-2.1.xsd) 2010-01-26 13:23:42,592 DEBUG [org.jbpm.jpdl.xml.JpdlParser] (WorkerThread#0[10.16.95.21:39912]) original systemId as input source [bes@besdev tmp]$ grep 13:23:5 server.log | more [bes@besdev tmp]$ grep 13:24 server.log | more [bes@besdev tmp]$ grep 13:25 server.log | more [bes@besdev tmp]$ grep 13:26 server.log | more 2010-01-26 13:26:51,638 WARN [org.jbpm.jpdl.xml.JpdlXmlReader] (WorkerThread#0[10.16.95.21:39912]) process parse warning: line 8: schema_reference.4: Failed to read schema document 'http://jboss.com/products/seam/pageflow-2.1.xsd', because 1) could not f nd the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. 2010-01-26 13:26:51,639 DEBUG [org.jbpm.JbpmContext] (WorkerThread#0[10.16.95.21:39912]) closing jbpmContext org.jbpm.JbpmContext@1600573 2010-01-26 13:26:51,639 DEBUG [org.jboss.seam.Component] (WorkerThread#0[10.16.95.21:39912]) instantiating Seam component: org.jboss.seam.core.resourceLoader 2010-01-26 13:26:51,639 DEBUG [org.jboss.seam.Component] (WorkerThread#0[10.16.95.21:39912]) initializing new instance of: org.jboss.seam.core.resourceLoader 2010-01-26 13:26:51,639 DEBUG [org.jboss.seam.Component] (WorkerThread#0[10.16.95.21:39912]) done initializing: org.jboss.seam.core.resourceLoader 2010-01-26 13:26:51,640 DEBUG [org.jboss.seam.util.Resources] (WorkerThread#0[10.16.95.21:39912]) Loaded resource from context classloader: checkout.jpdl.xml 2010-01-26 13:26:51,640 DEBUG [org.jbpm.configuration.JbpmContextInfo] (WorkerThread#0[10.16.95.21:39912]) creating jbpm context with service factories '[]' 2010-01-26 13:26:51,640 DEBUG [org.jbpm.JbpmContext] (WorkerThread#0[10.16.95.21:39912]) creating org.jbpm.JbpmContext@16701a2 2010-01-26 13:26:51,651 DEBUG [org.jbpm.jpdl.xml.JpdlParser] (WorkerThread#0[10.16.95.21:39912]) resolving schema reference publicId(null) systemId(http://jboss.com/products/seam/pageflow-2.1.xsd) 2010-01-26 13:26:51,651 DEBUG [org.jbpm.jpdl.xml.JpdlParser] (WorkerThread#0[10.16.95.21:39912]) original systemId as input source [bes@besdev tmp]$ grep 13:27 server.log | more [bes@besdev tmp]$ grep 13:28 server.log | more 2010-01-26 13:28:12,890 DEBUG [org.jboss.remoting.transport.socket.ServerThread] (WorkerThread#1[10.16.95.21:35891]) WorkerThread#1[10.16.95.21:35891] closed socketWrapper: ServerSocketWrapper[Socket[addr=/10.16.95.21,port=35891,localport=4446].1615a5f] 2010-01-26 13:28:12,904 DEBUG [org.jboss.remoting.transport.socket.ServerThread] (WorkerThread#2[10.16.95.21:35890]) WorkerThread#2[10.16.95.21:35890] closed socketWrapper: ServerSocketWrapper[Socket[addr=/10.16.95.21,port=35890,localport=4446].743bb0] 2010-01-26 13:28:12,926 DEBUG [org.jboss.profileservice.management.client.upload.StreamingDeploymentTarget] (WorkerThread#1[10.16.95.21:35892]) new StreamingTarget: InvokerLocator [socket://10.16.95.21:4446/?dataType=invocation&enableTcpNoDelay=true&marsh ller=org.jboss.invocation.unified.marshall.InvocationMarshaller&unmarshaller=org.jboss.invocation.unified.marshall.InvocationUnMarshaller] 2010-01-26 13:28:12,953 DEBUG [org.jboss.remoting.transport.socket.ServerThread] (WorkerThread#1[10.16.95.21:35892]) WorkerThread#1[10.16.95.21:35892] closed socketWrapper: ServerSocketWrapper[Socket[addr=/10.16.95.21,port=35892,localport=4446].1898f52] 2010-01-26 13:28:12,986 DEBUG [org.jboss.profileservice.management.upload.remoting.DeployHandler] (WorkerThread#2[10.16.95.21:35893]) invoke, payload: {DeploymentTargetID=names=[jboss-seam-jpa.war], copyContent=false, description=file:/mnt/hudson_workspac /workspace/JBoss-AS-6.0.x-testSuite-sun16/JBossAS/testsuite/output/lib/jboss-seam-jpa.war, clientAddress=/10.16.95.21}, parameter: distribute 2010-01-26 13:28:12,986 INFO [org.jboss.profileservice.management.upload.remoting.DeployHandler] (WorkerThread#2[10.16.95.21:35893]) Begin distribute, content url: file:/mnt/hudson_workspace/workspace/JBoss-AS-6.0.x-testSuite-sun16/JBossAS/testsuite/outp t/lib/jboss-seam-jpa.war The logging beginning at 13:2812 is the next test starting. I suspect an environmental issue on the hudson server. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira