March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-924) ClusteredImpl is missing default partition name

by Brian Stansberry (JIRA)

ClusteredImpl is missing default partition name ----------------------------------------------- Key: EJBTHREE-924 URL: http://jira.jboss.com/jira/browse/EJBTHREE-924 Project: EJB 3.0 Issue Type: Bug Components: Clustering Affects Versions: AS 4.2.0 CR1 Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: AS 4.2.0 CR2 org.jboss.annotation.ejb.ClusteredImpl's partition property has a default value of null. Effect is, if you deploy a clustered bean without @Clustered, but instead just use <clustered>true</clustered> in jboss.xml, it doesn't work. You also have to include a <cluster-config> element to specify the partition name, even if you just want the default partition. Solution is to have the ClusteredImpl.partition default value be ${jboss.partition.name:DefaultPartition} -- the same as @Clustered.partition. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4241) Deploying Seam example app into /trunk causes ZipException

by Charles Crouch (JIRA)

Deploying Seam example app into /trunk causes ZipException ---------------------------------------------------------- Key: JBAS-4241 URL: http://jira.jboss.com/jira/browse/JBAS-4241 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Environment: r61655 of /trunk and jboss-seam-1.2.0.PATCH1 Reporter: Charles Crouch Fix For: JBossAS-5.0.0.Beta2 Deploying a modified version of jboss-seam-numberguess.ear into the current Beta2 server causes ZipException's to be thrown during startup and trying to hit http://localhost:8080/seam-numberguess produces 500's. Deploying the same app into Beta1 works fine. Steps to reproduce: 1) Copy jboss-seam-1.2.0.PATCH1\lib\el-api.jar and jboss-seam-1.2.0.PATCH1\lib\el-ri.jar to build\output\jboss-5.0.0.Beta2\server\default\deployers\jbossweb.deployer\jsf-libs 2) Copy cglib-nodep-2.1_3.jar (version probably doesn't matter) to build\output\jboss-5.0.0.Beta2\server\default\lib 3) Copy modified jboss-seam-numberguess.ear to build\output\jboss-5.0.0.Beta2\server\default\deploy 4) Start the server and you get several exceptions like the following... 12:09:11,896 INFO [Catalina] Server startup in 190 ms 12:09:20,769 INFO [MCKernelAbstraction] installing bean: jboss.j2ee:ear=jboss-seam-numberguess.ear,jar=jboss-seam.jar,name=Dispatcher,service=EJB3 with dependencies: 12:09:24,244 INFO [EJBContainer] STARTED EJB: org.jboss.seam.core.Dispatcher ejbName: Dispatcher 12:09:24,484 WARN [JBossTimerServiceFactory] TIMER SERVICE IS NOT INSTALLED 12:09:24,484 INFO [MCKernelAbstraction] installing bean: jboss.j2ee:ear=jboss-seam-numberguess.ear,jar=jboss-seam.jar,name=TransactionListener,service=EJB3 with dependencies: 12:09:26,216 INFO [EJBContainer] STARTED EJB: org.jboss.seam.core.TransactionListener ejbName: TransactionListener 12:09:29,441 INFO [TomcatDeployment] deploy, ctxPath=/invoker, vfsUrl=http-invoker.sar/invoker.war 12:09:35,319 INFO [TomcatDeployment] deploy, ctxPath=/seam-numberguess, vfsUrl=jboss-seam-numberguess.ear/jboss-seam-numberguess.war 12:09:38,895 INFO [ServletContextListener] Welcome to Seam 1.2.0.PATCH1 12:09:38,995 INFO [Scanner] scanning: vfsfile:/C:/usr/projects/current/jboss/trunk/build/output/jboss-5.0.0.Beta2/server/default/deploy/jboss-seam-numberguess.ear/jboss-seam.jar 12:09:38,995 WARN [Scanner] could not read entries java.util.zip.ZipException: The filename, directory name, or volume label syntax is incorrect at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(ZipFile.java:203) at java.util.zip.ZipFile.<init>(ZipFile.java:234) at org.jboss.seam.deployment.Scanner.handleArchive(Scanner.java:110) at org.jboss.seam.deployment.Scanner.scan(Scanner.java:96) at org.jboss.seam.deployment.NamespaceScanner.getPackages(NamespaceScanner.java:34) at org.jboss.seam.init.Initialization.addNamespaces(Initialization.java:590) at org.jboss.seam.init.Initialization.<init>(Initialization.java:80) at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:33) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3854) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
5
0 / 0

[JBoss JIRA] Created: (JBAS-4235) Session ID lost over "secure" connector

by Sergey Zhukov (JIRA)

Session ID lost over "secure" connector --------------------------------------- Key: JBAS-4235 URL: http://jira.jboss.com/jira/browse/JBAS-4235 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.3 SP1 Reporter: Sergey Zhukov Assigned To: Brian Stansberry I'm using AJP or HTTP connector with secure="true" attribute in JBoss cluster environment. On every browser's request, my JSP code got new session id (session.getId()). Also it affects load balancing with sticky sessions, because every new request goes to another node. Try it, by simple index.jsp: <%= session.getId() %> Deploy it as farm application, open in browser and click refresh several times. You'll see new id every time. I've tried this with JBoss 4.0.5 with configuration: 'all'. NOTE: without secure="true" everything works Ok. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-1012) ReplicationQueue invokes callRemoteMethods even when empty

by Brian Stansberry (JIRA)

ReplicationQueue invokes callRemoteMethods even when empty ---------------------------------------------------------- Key: JBCACHE-1012 URL: http://jira.jboss.com/jira/browse/JBCACHE-1012 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Replication Affects Versions: 1.4.1.SP3, 2.0.0.BETA1 Environment: ReplicationQueue doesn't bother to check whether there's anything to replicate before calling cache.callRemoteMethods. Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.0.0.BETA2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

2
4
0 / 0

[JBoss JIRA] Updated: (BPEL-190) web app generation tool

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-190?page=all ] Alejandro Guizar updated BPEL-190: ---------------------------------- Fix Version/s: jBPM BPEL 1.1.1 (was: jBPM BPEL 1.1.GA) > web app generation tool > ----------------------- > > Key: BPEL-190 > URL: http://jira.jboss.com/jira/browse/BPEL-190 > Project: JBoss jBPM BPEL > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.1 beta 1 > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1.1 > > > create a tool for generating web application artifacts -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (BPEL-168) soap header processing

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-168?page=all ] Alejandro Guizar updated BPEL-168: ---------------------------------- Fix Version/s: jBPM BPEL 1.1.GA (was: jBPM BPEL 1.1.1) > soap header processing > ---------------------- > > Key: BPEL-168 > URL: http://jira.jboss.com/jira/browse/BPEL-168 > Project: JBoss jBPM BPEL > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 4 > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1.GA > > > Extract the WSDL message parts carried in SOAP headers and add them to incoming requests. > Ensure this mechanism makes WS-Addressing headers available to the process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (BPEL-144) publish document/literal endpoints

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-144?page=all ] Alejandro Guizar updated BPEL-144: ---------------------------------- Fix Version/s: jBPM BPEL 1.1.GA (was: jBPM BPEL 1.1.1) > publish document/literal endpoints > ---------------------------------- > > Key: BPEL-144 > URL: http://jira.jboss.com/jira/browse/BPEL-144 > Project: JBoss jBPM BPEL > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 4 > Environment: jaxrpc, saaj, w3c dom > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1.GA > > > jBPM BPEL currently generates service WSDL documents and processes SOAP request/response messages only for RPC/literal web services. Enhancing the service generation tool and the JAX-RPC handler to cover the document style is crucial for interoperability, particulary with .NET. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-649) refactor JBRMSServiceServlet to use seperate action classes

by Michael Neale (JIRA)

refactor JBRMSServiceServlet to use seperate action classes ----------------------------------------------------------- Key: JBRULES-649 URL: http://jira.jboss.com/jira/browse/JBRULES-649 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAOP-377) Memory leak in AspectDefinition not causing per-instance advisors to be released

by Kabir Khan (JIRA)

Memory leak in AspectDefinition not causing per-instance advisors to be released -------------------------------------------------------------------------------- Key: JBAOP-377 URL: http://jira.jboss.com/jira/browse/JBAOP-377 Project: JBoss AOP Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.alpha5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-4160) failing org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase

by Dimitris Andreadis (JIRA)

failing org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase --------------------------------------------------------------- Key: JBAS-4160 URL: http://jira.jboss.com/jira/browse/JBAS-4160 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Other Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Priority: Critical Fix For: JBossAS-4.2.0.CR1 The test timeouts. Testsuite: org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec Testcase: unknown took 0 sec Caused an ERROR Timeout occurred junit.framework.AssertionFailedError: Timeout occurred test.log: 2007-02-28 01:59:33,832 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] waitFinished, target=1 2007-02-28 01:59:33,832 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] Begin run 2007-02-28 01:59:33,832 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyStarted, data=test 2007-02-28 01:59:33,832 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyFinished, data=test 2007-02-28 01:59:33,832 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] End run 2007-02-28 01:59:33,832 DEBUG [org.jboss.util.threadpool.BasicThreadPool] stop, immediate=true 2007-02-28 01:59:33,832 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] waitFinished, target=3 2007-02-28 01:59:33,832 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] Begin run 2007-02-28 01:59:33,832 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyStarted, data=test1 2007-02-28 01:59:33,832 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] Begin run 2007-02-28 01:59:33,832 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] Begin run 2007-02-28 01:59:33,832 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyFinished, data=test1 2007-02-28 01:59:33,832 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] End run 2007-02-28 01:59:33,832 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyStarted, data=test2 2007-02-28 01:59:33,832 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyStarted, data=test3 2007-02-28 01:59:33,842 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyFinished, data=test2 2007-02-28 01:59:33,842 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] End run 2007-02-28 01:59:33,842 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyFinished, data=test3 2007-02-28 01:59:33,842 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] End run 2007-02-28 01:59:33,842 DEBUG [org.jboss.util.threadpool.BasicThreadPool] stop, immediate=true 2007-02-28 01:59:33,842 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] waitFinished, target=1 2007-02-28 01:59:33,842 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] Begin run 2007-02-28 01:59:33,842 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyStarted, data=test1 2007-02-28 01:59:33,842 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyFinished, data=test1 2007-02-28 01:59:33,842 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] End run 2007-02-28 01:59:33,842 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] Begin run 2007-02-28 01:59:33,842 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyStarted, data=test2 2007-02-28 01:59:33,842 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyFinished, data=test2 2007-02-28 01:59:33,842 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] End run 2007-02-28 01:59:33,842 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] waitFinished, target=2 2007-02-28 01:59:33,842 DEBUG [org.jboss.util.threadpool.BasicThreadPool] stop, immediate=true 2007-02-28 01:59:33,852 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] waitStarted, target=1 2007-02-28 01:59:33,852 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] Begin run 2007-02-28 01:59:33,852 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyStarted, data=test1 2007-02-28 01:59:33,852 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] waitForReleaseStarted, data=test1 2007-02-28 01:59:33,852 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] waitFinished, target=1 2007-02-28 01:59:33,852 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] Begin run 2007-02-28 01:59:33,852 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyStarted, data=test2 2007-02-28 01:59:33,852 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyFinished, data=test2 2007-02-28 01:59:33,852 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] releaseStarted, data=test1 2007-02-28 01:59:33,852 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] waitFinished, target=2 2007-02-28 01:59:33,852 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] End run 2007-02-28 01:59:33,852 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyFinished, data=test1 2007-02-28 01:59:33,852 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] End run 2007-02-28 01:59:33,852 DEBUG [org.jboss.util.threadpool.BasicThreadPool] stop, immediate=true 2007-02-28 01:59:33,852 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] waitStarted, target=1 2007-02-28 01:59:33,852 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] Begin run 2007-02-28 01:59:33,852 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyStarted, data=test1 2007-02-28 01:59:33,852 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] waitForReleaseStarted, data=test1 2007-02-28 01:59:34,853 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] releaseStarted, data=test1 2007-02-28 01:59:34,853 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] waitFinished, target=2 2007-02-28 01:59:34,853 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyFinished, data=test1 2007-02-28 01:59:34,853 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] End run 2007-02-28 01:59:34,853 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] Begin run 2007-02-28 01:59:34,853 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyStarted, data=test2 2007-02-28 01:59:34,853 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyFinished, data=test2 2007-02-28 01:59:34,853 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] End run 2007-02-28 01:59:34,853 DEBUG [org.jboss.util.threadpool.BasicThreadPool] stop, immediate=true 2007-02-28 01:59:34,853 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] waitStarted, target=1 2007-02-28 01:59:34,853 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] Begin run 2007-02-28 01:59:34,853 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyStarted, data=test1 2007-02-28 01:59:34,853 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] releaseStarted, data=test1 2007-02-28 01:59:34,853 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] waitFinished, target=2 2007-02-28 01:59:34,853 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] waitForReleaseStarted, data=test1 2007-02-28 01:59:34,853 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyFinished, data=test1 2007-02-28 01:59:34,853 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] End run 2007-02-28 01:59:34,853 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] Begin run 2007-02-28 01:59:34,853 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyStarted, data=test2 2007-02-28 01:59:34,853 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyFinished, data=test2 2007-02-28 01:59:34,853 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] End run 2007-02-28 01:59:34,853 DEBUG [org.jboss.util.threadpool.BasicThreadPool] stop, immediate=true 2007-02-28 01:59:34,863 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] waitStarted, target=1 2007-02-28 01:59:34,863 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] Begin run 2007-02-28 01:59:34,863 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyStarted, data=test1 2007-02-28 01:59:34,863 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] releaseStarted, data=test1 2007-02-28 01:59:34,863 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] waitFinished, target=1 2007-02-28 01:59:34,863 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] waitForReleaseStarted, data=test1 2007-02-28 01:59:34,863 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] Begin spin loop 2007-02-28 01:59:34,863 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] Begin sleep 2007-02-28 01:59:44,867 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyFinished, data=test1 2007-02-28 01:59:44,867 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] End run 2007-02-28 01:59:44,867 DEBUG [org.jboss.util.threadpool.BasicThreadPool] stop, immediate=true 2007-02-28 01:59:44,867 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] waitStarted, target=1 2007-02-28 01:59:44,867 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] Begin run 2007-02-28 01:59:44,867 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] notifyStarted, data=test1 2007-02-28 01:59:44,867 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] releaseStarted, data=test1 2007-02-28 01:59:44,867 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] waitForReleaseStarted, data=test1 2007-02-28 01:59:44,867 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] Begin spin loop 2007-02-28 01:59:55,863 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] waitStarted, target=1 2007-02-28 01:59:55,863 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] releaseStarted, data=test2 2007-02-28 01:59:55,863 INFO [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] waitFinished, target=1 2007-02-28 01:59:55,883 WARN [org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase] Caught throwable java.lang.ThreadDeath at java.lang.Thread.stop(Thread.java:698) at org.jboss.util.threadpool.RunnableTaskWrapper.stopTask(RunnableTaskWrapper.java:122) at org.jboss.util.threadpool.BasicThreadPool$TimeoutInfo.stopTask(BasicThreadPool.java:517) at org.jboss.util.threadpool.BasicThreadPool$TimeoutMonitor.run(BasicThreadPool.java:579) at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2007