2:14 p.m.
Ok, thanks.
Shelly McGowan wrote:
Scott,
There is one currently in progress - almost done. Internal URL can be
viewed at:
http://hudson.qa.jboss.com/hudson/view/JBoss20AS/job/JBoss-AS-5.0.x-TestS...
Once this is done it will be published to https://hudson.jboss.org
Shelly
3:58 p.m.
New subject: JBoss-AS-5.0.x-TestSuite-sun15
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/
After the library repository came in synch again, I triggered both
JBoss-AS-5.0.x-TestSuite-sun15 and later JBoss-AS-5.0.x-TestSuite-sun15-noip.
The latter finished first and it shows more or less the usual numbers ~200 failures with
some transient ones.
The main JBoss-AS-5.0.x-TestSuite-sun15 has already taken 7 hours, 2 hours more than the
usual so maybe it's stuck and needs to be killed.
Scott M Stark wrote:
Ok, thanks.
Shelly McGowan wrote:
> Scott,
>
> There is one currently in progress - almost done. Internal URL can be
> viewed at:
>
>
http://hudson.qa.jboss.com/hudson/view/JBoss20AS/job/JBoss-AS-5.0.x-TestS...
>
>
> Once this is done it will be published to https://hudson.jboss.org
>
>
>
> Shelly
4:09 p.m.
New subject: JBoss-AS-5.0.x-TestSuite-sun15
Taking 7 hours doesn't mean it's stuck:
http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-TestSui...
Note that build #248 (a valid run) took 7 hours on conf2-linux.
Dimitris Andreadis wrote:
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/
After the library repository came in synch again, I triggered both
JBoss-AS-5.0.x-TestSuite-sun15 and later
JBoss-AS-5.0.x-TestSuite-sun15-noip.
The latter finished first and it shows more or less the usual numbers
~200 failures with some transient ones.
The main JBoss-AS-5.0.x-TestSuite-sun15 has already taken 7 hours, 2
hours more than the usual so maybe it's stuck and needs to be killed.
Scott M Stark wrote:
> Ok, thanks.
>
> Shelly McGowan wrote:
>> Scott,
>>
>> There is one currently in progress - almost done. Internal URL can be
>> viewed at:
>>
>>
http://hudson.qa.jboss.com/hudson/view/JBoss20AS/job/JBoss-AS-5.0.x-TestS...
>>
>>
>>
>> Once this is done it will be published to https://hudson.jboss.org
>>
>>
>>
>> Shelly
>
4:22 p.m.
New subject: JBoss-AS-5.0.x-TestSuite-sun15
Yes. That's right. The build was still running.
The testsuite run completed but before publishing and email notification
someone had aborted.
However the results are available on the internal instance.
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
191 failures.
Ryan Campbell wrote:
Taking 7 hours doesn't mean it's stuck:
http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-TestSui...
Note that build #248 (a valid run) took 7 hours on conf2-linux.
Dimitris Andreadis wrote:
> http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/
>
> After the library repository came in synch again, I triggered both
> JBoss-AS-5.0.x-TestSuite-sun15 and later
> JBoss-AS-5.0.x-TestSuite-sun15-noip.
>
> The latter finished first and it shows more or less the usual numbers
> ~200 failures with some transient ones.
>
> The main JBoss-AS-5.0.x-TestSuite-sun15 has already taken 7 hours, 2
> hours more than the usual so maybe it's stuck and needs to be killed.
>
> Scott M Stark wrote:
>
>> Ok, thanks.
>>
>> Shelly McGowan wrote:
>>
>>> Scott,
>>>
>>> There is one currently in progress - almost done. Internal URL can be
>>> viewed at:
>>>
>>>
http://hudson.qa.jboss.com/hudson/view/JBoss20AS/job/JBoss-AS-5.0.x-TestS...
>>>
>>>
>>>
>>> Once this is done it will be published to https://hudson.jboss.org
>>>
>>>
>>>
>>> Shelly
>>>
4:26 p.m.
New subject: JBoss-AS-5.0.x-TestSuite-sun15
Also externally:
http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-TestSui...
Rajesh Rajasekaran wrote:
Yes. That's right. The build was still running.
The testsuite run completed but before publishing and email notification
someone had aborted.
However the results are available on the internal instance.
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
191 failures.
Ryan Campbell wrote:
> Taking 7 hours doesn't mean it's stuck:
>
>
http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-TestSui...
>
>
> Note that build #248 (a valid run) took 7 hours on conf2-linux.
>
>
> Dimitris Andreadis wrote:
>
>> http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/
>>
>> After the library repository came in synch again, I triggered both
>> JBoss-AS-5.0.x-TestSuite-sun15 and later
>> JBoss-AS-5.0.x-TestSuite-sun15-noip.
>>
>> The latter finished first and it shows more or less the usual numbers
>> ~200 failures with some transient ones.
>>
>> The main JBoss-AS-5.0.x-TestSuite-sun15 has already taken 7 hours, 2
>> hours more than the usual so maybe it's stuck and needs to be killed.
>>
>> Scott M Stark wrote:
>>
>>> Ok, thanks.
>>>
>>> Shelly McGowan wrote:
>>>
>>>> Scott,
>>>>
>>>> There is one currently in progress - almost done. Internal URL can be
>>>> viewed at:
>>>>
>>>>
http://hudson.qa.jboss.com/hudson/view/JBoss20AS/job/JBoss-AS-5.0.x-TestS...
>>>>
>>>>
>>>>
>>>>
>>>> Once this is done it will be published to https://hudson.jboss.org
>>>>
>>>>
>>>>
>>>> Shelly
>>>>
>
>
5:10 p.m.
New subject: JBoss-AS-5.0.x-TestSuite-sun15
So all that is left to cleanup is the ProfileServiceUnitTestCase
failures. Still working on whether the ManagedDeployment problem with
the deploy/messaging directory is an api problem that needs to be fixed.
A MC 2.0.0.Beta9 release and another testsuite run is needed at a minimum.
Rajesh Rajasekaran wrote:
Yes. That's right. The build was still running.
The testsuite run completed but before publishing and email notification
someone had aborted.
However the results are available on the internal instance.
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
191 failures.
5:25 p.m.
New subject: JBoss-AS-5.0.x-TestSuite-sun15
Regarding this:
- http://www.jboss.org/index.html?module=bb&op=viewtopic&t=126161
Have you already fixed AnnotationProxy or should I?
Scott M Stark wrote:
So all that is left to cleanup is the ProfileServiceUnitTestCase
failures. Still working on whether the ManagedDeployment problem with
the deploy/messaging directory is an api problem that needs to be fixed.
A MC 2.0.0.Beta9 release and another testsuite run is needed at a minimum.
Rajesh Rajasekaran wrote:
> Yes. That's right. The build was still running.
> The testsuite run completed but before publishing and email notification
> someone had aborted.
> However the results are available on the internal instance.
>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>
>
> 191 failures.
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
5:34 p.m.
New subject: JBoss-AS-5.0.x-TestSuite-sun15
Yes, I have checked in the change.
Ales Justin wrote:
Regarding this:
- http://www.jboss.org/index.html?module=bb&op=viewtopic&t=126161
Have you already fixed AnnotationProxy or should I?
Scott M Stark wrote:
> So all that is left to cleanup is the ProfileServiceUnitTestCase
> failures. Still working on whether the ManagedDeployment problem with
> the deploy/messaging directory is an api problem that needs to be fixed.
> A MC 2.0.0.Beta9 release and another testsuite run is needed at a
> minimum.
12:52 a.m.
New subject: JBoss-AS-5.0.x-TestSuite-sun15
The 2.0.0.Beta9 release is out the tests are passing. Just need a good
testsuite run to branch.
Scott M Stark wrote:
So all that is left to cleanup is the ProfileServiceUnitTestCase
failures. Still working on whether the ManagedDeployment problem with
the deploy/messaging directory is an api problem that needs to be fixed.
A MC 2.0.0.Beta9 release and another testsuite run is needed at a minimum.
Rajesh Rajasekaran wrote:
> Yes. That's right. The build was still running.
> The testsuite run completed but before publishing and email notification
> someone had aborted.
> However the results are available on the internal instance.
>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>
>
> 191 failures.
11:12 a.m.
New subject: Beta3 status - (was: Re: JBoss-AS-5.0.x-TestSuite-sun15)
Trunk is now building again, and there is an in-progress run that needs another 5 hours:
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
Can we get a status of the last tasks?
http://jira.jboss.com/jira/browse/JBAS-4671 - DsDataSourceTemplate (Alexey/Scott)
http://jira.jboss.com/jira/browse/JBAS-5064 - Seam Usage/Testing (Ales)
http://jira.jboss.com/jira/browse/JBAS-5016 - Wikis (Scott)
ThomasD made also a last minute update to juddi/scout. This is being tested now in the
current test run, but I don't know how/if it affects TCK.
He also reported the following regression. Was AbstractAnnotationImpl somehow moved?
NoClassDefFoundError: org/jboss/metadata/annotation/AbstractAnnotationImpl
http://jira.jboss.com/jira/browse/JBAS-5093
We need to wrap-up, ASAP.
/D
Scott M Stark wrote:
The 2.0.0.Beta9 release is out the tests are passing. Just need a
good
testsuite run to branch.
Scott M Stark wrote:
> So all that is left to cleanup is the ProfileServiceUnitTestCase
> failures. Still working on whether the ManagedDeployment problem with
> the deploy/messaging directory is an api problem that needs to be fixed.
> A MC 2.0.0.Beta9 release and another testsuite run is needed at a minimum.
>
> Rajesh Rajasekaran wrote:
>> Yes. That's right. The build was still running.
>> The testsuite run completed but before publishing and email notification
>> someone had aborted.
>> However the results are available on the internal instance.
>>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>>
>>
>> 191 failures.
11:27 a.m.
New subject: Beta3 status -
I need to clarify with Scott an issue I have with managed properties of
collection types in ProfileServiceUnitTestCase. I.e. what values the
admin client has to pass in and get back.
Currently, the client passes a collection of POJOs (as in the MCF
metadata API) but gets back a collection of the corresponding managed
objects.
Dimitris Andreadis wrote:
Trunk is now building again, and there is an in-progress run that
needs
another 5 hours:
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
Can we get a status of the last tasks?
http://jira.jboss.com/jira/browse/JBAS-4671 - DsDataSourceTemplate
(Alexey/Scott)
http://jira.jboss.com/jira/browse/JBAS-5064 - Seam Usage/Testing (Ales)
http://jira.jboss.com/jira/browse/JBAS-5016 - Wikis (Scott)
ThomasD made also a last minute update to juddi/scout. This is being
tested now in the current test run, but I don't know how/if it affects TCK.
He also reported the following regression. Was AbstractAnnotationImpl
somehow moved?
NoClassDefFoundError: org/jboss/metadata/annotation/AbstractAnnotationImpl
http://jira.jboss.com/jira/browse/JBAS-5093
We need to wrap-up, ASAP.
/D
Scott M Stark wrote:
> The 2.0.0.Beta9 release is out the tests are passing. Just need a good
> testsuite run to branch.
>
> Scott M Stark wrote:
>> So all that is left to cleanup is the ProfileServiceUnitTestCase
>> failures. Still working on whether the ManagedDeployment problem with
>> the deploy/messaging directory is an api problem that needs to be fixed.
>> A MC 2.0.0.Beta9 release and another testsuite run is needed at a
>> minimum.
>>
>> Rajesh Rajasekaran wrote:
>>> Yes. That's right. The build was still running.
>>> The testsuite run completed but before publishing and email
>>> notification
>>> someone had aborted.
>>> However the results are available on the internal instance.
>>>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>>>
>>>
>>>
>>> 191 failures.
>
11:49 a.m.
New subject: Beta3 status -
Dimitris Andreadis wrote:
Trunk is now building again, and there is an in-progress run that
needs
another 5 hours:
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
Can we get a status of the last tasks?
http://jira.jboss.com/jira/browse/JBAS-4671 - DsDataSourceTemplate
(Alexey/Scott)
http://jira.jboss.com/jira/browse/JBAS-5064 - Seam Usage/Testing (Ales)
http://jira.jboss.com/jira/browse/JBAS-5016 - Wikis (Scott)
Being updated, should
not hold up the release.
ThomasD made also a last minute update to juddi/scout. This is being
tested now in the current test run, but I don't know how/if it affects TCK.
He also reported the following regression. Was AbstractAnnotationImpl
somehow moved?
NoClassDefFoundError: org/jboss/metadata/annotation/AbstractAnnotationImpl
http://jira.jboss.com/jira/browse/JBAS-5093
No, still in jboss-container.jar
[starksm@succubus testsuite]$ javap -classpath
/home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta3/lib/jboss-container.jar
org.jboss.metadata.annotation.AbstractAnnotationImpl
Compiled from "AbstractAnnotationImpl.java"
public class org.jboss.metadata.annotation.AbstractAnnotationImpl
extends java.lang.Object implements java.lang.annotation.Annotation{
public org.jboss.metadata.annotation.AbstractAnnotationImpl();
public
org.jboss.metadata.annotation.AbstractAnnotationImpl(java.lang.Class);
public java.lang.Class annotationType();
public boolean equals(java.lang.Object);
public int hashCode();
}
The issue says there is a missing jar. It just looks like the
jboss-container-metadata.jar is missing from the jboss repo. I'll update it.
We need to wrap-up, ASAP.
/D
12:07 p.m.
New subject: Beta3 status -
Ok, I see now, both jboss-container-metadata-spi.jar and jboss-container-metadata.jar are
missing.
In my local build I must have been using the ones from Beta7.
Scott M Stark wrote:
Dimitris Andreadis wrote:
> Trunk is now building again, and there is an in-progress run that needs
> another 5 hours:
>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>
>
> Can we get a status of the last tasks?
>
> http://jira.jboss.com/jira/browse/JBAS-4671 - DsDataSourceTemplate
> (Alexey/Scott)
> http://jira.jboss.com/jira/browse/JBAS-5064 - Seam Usage/Testing (Ales)
> http://jira.jboss.com/jira/browse/JBAS-5016 - Wikis (Scott)
Being updated, should not hold up the release.
> ThomasD made also a last minute update to juddi/scout. This is being
> tested now in the current test run, but I don't know how/if it affects TCK.
>
> He also reported the following regression. Was AbstractAnnotationImpl
> somehow moved?
>
> NoClassDefFoundError: org/jboss/metadata/annotation/AbstractAnnotationImpl
> http://jira.jboss.com/jira/browse/JBAS-5093
No, still in jboss-container.jar
[starksm@succubus testsuite]$ javap -classpath
/home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta3/lib/jboss-container.jar
org.jboss.metadata.annotation.AbstractAnnotationImpl
Compiled from "AbstractAnnotationImpl.java"
public class org.jboss.metadata.annotation.AbstractAnnotationImpl
extends java.lang.Object implements java.lang.annotation.Annotation{
public org.jboss.metadata.annotation.AbstractAnnotationImpl();
public
org.jboss.metadata.annotation.AbstractAnnotationImpl(java.lang.Class);
public java.lang.Class annotationType();
public boolean equals(java.lang.Object);
public int hashCode();
}
The issue says there is a missing jar. It just looks like the
jboss-container-metadata.jar is missing from the jboss repo. I'll update it.
> We need to wrap-up, ASAP.
>
> /D
1:13 p.m.
New subject: Beta3 status -
The Scout version update was not recommended. We were using the v0.7
version which was TCK verified.
Dimitris Andreadis wrote:
Trunk is now building again, and there is an in-progress run that
needs
another 5 hours:
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
Can we get a status of the last tasks?
http://jira.jboss.com/jira/browse/JBAS-4671 - DsDataSourceTemplate
(Alexey/Scott)
http://jira.jboss.com/jira/browse/JBAS-5064 - Seam Usage/Testing (Ales)
http://jira.jboss.com/jira/browse/JBAS-5016 - Wikis (Scott)
ThomasD made also a last minute update to juddi/scout. This is being
tested now in the current test run, but I don't know how/if it affects TCK.
He also reported the following regression. Was AbstractAnnotationImpl
somehow moved?
NoClassDefFoundError: org/jboss/metadata/annotation/AbstractAnnotationImpl
http://jira.jboss.com/jira/browse/JBAS-5093
We need to wrap-up, ASAP.
/D
Scott M Stark wrote:
> The 2.0.0.Beta9 release is out the tests are passing. Just need a good
> testsuite run to branch.
>
> Scott M Stark wrote:
>> So all that is left to cleanup is the ProfileServiceUnitTestCase
>> failures. Still working on whether the ManagedDeployment problem with
>> the deploy/messaging directory is an api problem that needs to be fixed.
>> A MC 2.0.0.Beta9 release and another testsuite run is needed at a
>> minimum.
>>
>> Rajesh Rajasekaran wrote:
>>> Yes. That's right. The build was still running.
>>> The testsuite run completed but before publishing and email
>>> notification
>>> someone had aborted.
>>> However the results are available on the internal instance.
>>>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>>>
>>>
>>>
>>> 191 failures.
>
4:35 p.m.
New subject: Beta3 status -
The build has failed due to the seam.xml section. Must be due to an ant
version problem:
BUILD FAILED
/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/build.xml:855:
The following error occurred while executing this line:
/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/imports/sections/seam.xml:12:
The <urn:maven-artifact-ant:dependencies> type doesn't support the
"versionsid" attribute.
testsuite/build.sh works for me, as well as ant 1.6.5 standalone, so
what ant would be used for the build?
Dimitris Andreadis wrote:
Trunk is now building again, and there is an in-progress run that
needs
another 5 hours:
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
Can we get a status of the last tasks?
http://jira.jboss.com/jira/browse/JBAS-4671 - DsDataSourceTemplate
(Alexey/Scott)
http://jira.jboss.com/jira/browse/JBAS-5064 - Seam Usage/Testing (Ales)
http://jira.jboss.com/jira/browse/JBAS-5016 - Wikis (Scott)
ThomasD made also a last minute update to juddi/scout. This is being
tested now in the current test run, but I don't know how/if it affects TCK.
He also reported the following regression. Was AbstractAnnotationImpl
somehow moved?
NoClassDefFoundError: org/jboss/metadata/annotation/AbstractAnnotationImpl
http://jira.jboss.com/jira/browse/JBAS-5093
We need to wrap-up, ASAP.
/D
Scott M Stark wrote:
> The 2.0.0.Beta9 release is out the tests are passing. Just need a good
> testsuite run to branch.
>
> Scott M Stark wrote:
>> So all that is left to cleanup is the ProfileServiceUnitTestCase
>> failures. Still working on whether the ManagedDeployment problem with
>> the deploy/messaging directory is an api problem that needs to be fixed.
>> A MC 2.0.0.Beta9 release and another testsuite run is needed at a
>> minimum.
>>
>> Rajesh Rajasekaran wrote:
>>> Yes. That's right. The build was still running.
>>> The testsuite run completed but before publishing and email
>>> notification
>>> someone had aborted.
>>> However the results are available on the internal instance.
>>>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>>>
>>>
>>>
>>> 191 failures.
>
4:47 p.m.
New subject: Beta3 status -
Shouldn't the build be using the ant that comes bundled with AS? This has failed twice
today
so I've asked Ales to isolate the seam tests so they are not build/run by default,
rather
run then manually for this iteration.
I've also reverted the jboss-juddi upgrade. It came extremely late for Beta3.
Scott M Stark wrote:
The build has failed due to the seam.xml section. Must be due to an
ant
version problem:
BUILD FAILED
/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/build.xml:855:
The following error occurred while executing this line:
/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/imports/sections/seam.xml:12:
The <urn:maven-artifact-ant:dependencies> type doesn't support the
"versionsid" attribute.
testsuite/build.sh works for me, as well as ant 1.6.5 standalone, so
what ant would be used for the build?
Dimitris Andreadis wrote:
> Trunk is now building again, and there is an in-progress run that needs
> another 5 hours:
>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>
>
> Can we get a status of the last tasks?
>
> http://jira.jboss.com/jira/browse/JBAS-4671 - DsDataSourceTemplate
> (Alexey/Scott)
> http://jira.jboss.com/jira/browse/JBAS-5064 - Seam Usage/Testing (Ales)
> http://jira.jboss.com/jira/browse/JBAS-5016 - Wikis (Scott)
>
> ThomasD made also a last minute update to juddi/scout. This is being
> tested now in the current test run, but I don't know how/if it affects TCK.
>
> He also reported the following regression. Was AbstractAnnotationImpl
> somehow moved?
>
> NoClassDefFoundError: org/jboss/metadata/annotation/AbstractAnnotationImpl
> http://jira.jboss.com/jira/browse/JBAS-5093
>
> We need to wrap-up, ASAP.
>
> /D
>
> Scott M Stark wrote:
>> The 2.0.0.Beta9 release is out the tests are passing. Just need a good
>> testsuite run to branch.
>>
>> Scott M Stark wrote:
>>> So all that is left to cleanup is the ProfileServiceUnitTestCase
>>> failures. Still working on whether the ManagedDeployment problem with
>>> the deploy/messaging directory is an api problem that needs to be fixed.
>>> A MC 2.0.0.Beta9 release and another testsuite run is needed at a
>>> minimum.
>>>
>>> Rajesh Rajasekaran wrote:
>>>> Yes. That's right. The build was still running.
>>>> The testsuite run completed but before publishing and email
>>>> notification
>>>> someone had aborted.
>>>> However the results are available on the internal instance.
>>>>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>>>>
>>>>
>>>>
>>>> 191 failures.
1:21 a.m.
New subject: Beta3 status -
The run that picks up mc 2.0.0.beta9, the juddi rollback, etc is done
and looks good. Time to tag.
http://hudson.qa.jboss.com/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15/256/
4:48 p.m.
New subject: Beta3 status -
We have had successful test runs with the seam.xml previously, 254 for
example:
http://hudson.qa.jboss.com/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15/254/...
_jars-seam:
[copy] Copying 5 files to
/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/output/lib
Scott M Stark wrote:
The build has failed due to the seam.xml section. Must be due to an
ant
version problem:
BUILD FAILED
/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/build.xml:855:
The following error occurred while executing this line:
/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/imports/sections/seam.xml:12:
The <urn:maven-artifact-ant:dependencies> type doesn't support the
"versionsid" attribute.
testsuite/build.sh works for me, as well as ant 1.6.5 standalone, so
what ant would be used for the build?
Dimitris Andreadis wrote:
> Trunk is now building again, and there is an in-progress run that needs
> another 5 hours:
>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>
>
> Can we get a status of the last tasks?
>
> http://jira.jboss.com/jira/browse/JBAS-4671 - DsDataSourceTemplate
> (Alexey/Scott)
> http://jira.jboss.com/jira/browse/JBAS-5064 - Seam Usage/Testing (Ales)
> http://jira.jboss.com/jira/browse/JBAS-5016 - Wikis (Scott)
>
> ThomasD made also a last minute update to juddi/scout. This is being
> tested now in the current test run, but I don't know how/if it affects TCK.
>
> He also reported the following regression. Was AbstractAnnotationImpl
> somehow moved?
>
> NoClassDefFoundError: org/jboss/metadata/annotation/AbstractAnnotationImpl
> http://jira.jboss.com/jira/browse/JBAS-5093
>
> We need to wrap-up, ASAP.
>
> /D
>
> Scott M Stark wrote:
>> The 2.0.0.Beta9 release is out the tests are passing. Just need a good
>> testsuite run to branch.
>>
>> Scott M Stark wrote:
>>> So all that is left to cleanup is the ProfileServiceUnitTestCase
>>> failures. Still working on whether the ManagedDeployment problem with
>>> the deploy/messaging directory is an api problem that needs to be fixed.
>>> A MC 2.0.0.Beta9 release and another testsuite run is needed at a
>>> minimum.
>>>
>>> Rajesh Rajasekaran wrote:
>>>> Yes. That's right. The build was still running.
>>>> The testsuite run completed but before publishing and email
>>>> notification
>>>> someone had aborted.
>>>> However the results are available on the internal instance.
>>>>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>>>>
>>>>
>>>>
>>>> 191 failures.
5:03 p.m.
New subject: Beta3 status -
Maybe is related to the setup of maven on the individual boxes, like how the local maven
repository is configured.
Scott M Stark wrote:
We have had successful test runs with the seam.xml previously, 254
for
example:
http://hudson.qa.jboss.com/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15/254/...
_jars-seam:
[copy] Copying 5 files to
/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/output/lib
Scott M Stark wrote:
> The build has failed due to the seam.xml section. Must be due to an ant
> version problem:
>
> BUILD FAILED
>
/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/build.xml:855:
> The following error occurred while executing this line:
>
/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/imports/sections/seam.xml:12:
> The <urn:maven-artifact-ant:dependencies> type doesn't support the
> "versionsid" attribute.
>
> testsuite/build.sh works for me, as well as ant 1.6.5 standalone, so
> what ant would be used for the build?
>
> Dimitris Andreadis wrote:
>> Trunk is now building again, and there is an in-progress run that needs
>> another 5 hours:
>>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>>
>>
>> Can we get a status of the last tasks?
>>
>> http://jira.jboss.com/jira/browse/JBAS-4671 - DsDataSourceTemplate
>> (Alexey/Scott)
>> http://jira.jboss.com/jira/browse/JBAS-5064 - Seam Usage/Testing (Ales)
>> http://jira.jboss.com/jira/browse/JBAS-5016 - Wikis (Scott)
>>
>> ThomasD made also a last minute update to juddi/scout. This is being
>> tested now in the current test run, but I don't know how/if it affects TCK.
>>
>> He also reported the following regression. Was AbstractAnnotationImpl
>> somehow moved?
>>
>> NoClassDefFoundError: org/jboss/metadata/annotation/AbstractAnnotationImpl
>> http://jira.jboss.com/jira/browse/JBAS-5093
>>
>> We need to wrap-up, ASAP.
>>
>> /D
>>
>> Scott M Stark wrote:
>>> The 2.0.0.Beta9 release is out the tests are passing. Just need a good
>>> testsuite run to branch.
>>>
>>> Scott M Stark wrote:
>>>> So all that is left to cleanup is the ProfileServiceUnitTestCase
>>>> failures. Still working on whether the ManagedDeployment problem with
>>>> the deploy/messaging directory is an api problem that needs to be fixed.
>>>> A MC 2.0.0.Beta9 release and another testsuite run is needed at a
>>>> minimum.
>>>>
>>>> Rajesh Rajasekaran wrote:
>>>>> Yes. That's right. The build was still running.
>>>>> The testsuite run completed but before publishing and email
>>>>> notification
>>>>> someone had aborted.
>>>>> However the results are available on the internal instance.
>>>>>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>>>>>
>>>>>
>>>>>
>>>>> 191 failures.
5:23 p.m.
New subject: Beta3 status -
254 & 255 were run on the same box. So I'm not sure why 254 failed and
255 passed.
http://hudson.qa.jboss.com/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15/buil...
Anyway, the no-ip run is about an hour away from completion, and the
normal run is starting again on dev03.
Dimitris Andreadis wrote:
Maybe is related to the setup of maven on the individual boxes, like
how
the local maven repository is configured.
Scott M Stark wrote:
> We have had successful test runs with the seam.xml previously, 254 for
> example:
> http://hudson.qa.jboss.com/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15/254/...
>
>
> _jars-seam:
> [copy] Copying 5 files to
>
/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/output/lib
>
>
>
> Scott M Stark wrote:
>> The build has failed due to the seam.xml section. Must be due to an ant
>> version problem:
>>
>> BUILD FAILED
>>
/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/build.xml:855:
>>
>> The following error occurred while executing this line:
>>
/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/imports/sections/seam.xml:12:
>>
>> The <urn:maven-artifact-ant:dependencies> type doesn't support the
>> "versionsid" attribute.
>>
>> testsuite/build.sh works for me, as well as ant 1.6.5 standalone, so
>> what ant would be used for the build?
>>
>> Dimitris Andreadis wrote:
>>> Trunk is now building again, and there is an in-progress run that needs
>>> another 5 hours:
>>>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>>>
>>>
>>>
>>> Can we get a status of the last tasks?
>>>
>>> http://jira.jboss.com/jira/browse/JBAS-4671 - DsDataSourceTemplate
>>> (Alexey/Scott)
>>> http://jira.jboss.com/jira/browse/JBAS-5064 - Seam Usage/Testing (Ales)
>>> http://jira.jboss.com/jira/browse/JBAS-5016 - Wikis (Scott)
>>>
>>> ThomasD made also a last minute update to juddi/scout. This is being
>>> tested now in the current test run, but I don't know how/if it
>>> affects TCK.
>>>
>>> He also reported the following regression. Was AbstractAnnotationImpl
>>> somehow moved?
>>>
>>> NoClassDefFoundError:
>>> org/jboss/metadata/annotation/AbstractAnnotationImpl
>>> http://jira.jboss.com/jira/browse/JBAS-5093
>>>
>>> We need to wrap-up, ASAP.
>>>
>>> /D
>>>
>>> Scott M Stark wrote:
>>>> The 2.0.0.Beta9 release is out the tests are passing. Just need a good
>>>> testsuite run to branch.
>>>>
>>>> Scott M Stark wrote:
>>>>> So all that is left to cleanup is the ProfileServiceUnitTestCase
>>>>> failures. Still working on whether the ManagedDeployment problem
with
>>>>> the deploy/messaging directory is an api problem that needs to be
>>>>> fixed.
>>>>> A MC 2.0.0.Beta9 release and another testsuite run is needed at a
>>>>> minimum.
>>>>>
>>>>> Rajesh Rajasekaran wrote:
>>>>>> Yes. That's right. The build was still running.
>>>>>> The testsuite run completed but before publishing and email
>>>>>> notification
>>>>>> someone had aborted.
>>>>>> However the results are available on the internal instance.
>>>>>>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> 191 failures.
>
5:49 p.m.
New subject: Beta3 status - Seam examples
When I change <mbean code="org.jboss.ejb.txtimer.EJBTimerServiceImpl">
to use noop PersistencePolicy, everything works fine - for NumberGuess
example.
For Booking, it deploys OK, but when I do a browser hit, it don't get a
response, all I get is a bunch of these:
00:41:18,984 INFO [Contexts] starting up: org.jboss.seam.security.identity
00:41:19,062 INFO [Contexts] starting up: org.jboss.seam.web.session
00:43:17,312 ERROR [STDERR] 20.12.2007 0:43:17
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:vfsfile:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/deploy/jboss-seam-booking.ear/jboss-seam-booking.war/WEB-INF/lib/jboss-seam-ui.jar!/META-INF/s.tag
00:43:17,312 ERROR [STDERR] 20.12.2007 0:43:17
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/tmp/deploy/jboss-seam-booking55101-exp.war/WEB-INF/lib/jboss-seam-ui.jar!/META-INF/s.taglib.xml
00:43:18,796 ERROR [STDERR] 20.12.2007 0:43:18
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:vfsfile:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/deploy/jboss-seam-booking.ear/jboss-seam-booking.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-co
00:43:18,812 ERROR [STDERR] 20.12.2007 0:43:18
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/tmp/deploy/jboss-seam-booking55101-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-core.taglib.xml
00:43:19,078 ERROR [STDERR] 20.12.2007 0:43:19
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:vfsfile:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/deploy/jboss-seam-booking.ear/jboss-seam-booking.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-ht
00:43:19,093 ERROR [STDERR] 20.12.2007 0:43:19
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/tmp/deploy/jboss-seam-booking55101-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-html.taglib.xml
00:43:19,625 ERROR [STDERR] 20.12.2007 0:43:19
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:vfsfile:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/deploy/jboss-seam-booking.ear/jboss-seam-booking.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-ui
00:43:19,640 ERROR [STDERR] 20.12.2007 0:43:19
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/tmp/deploy/jboss-seam-booking55101-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-ui.taglib.xml
00:43:21,343 ERROR [STDERR] 20.12.2007 0:43:21
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:vfsfile:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/deploy/jboss-seam-booking.ear/jboss-seam-booking.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-c
00:43:21,359 ERROR [STDERR] 20.12.2007 0:43:21
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/tmp/deploy/jboss-seam-booking55101-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-core.taglib.xm
00:43:24,921 ERROR [STDERR] 20.12.2007 0:43:24
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:vfsfile:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/deploy/jboss-seam-booking.ear/jboss-seam-booking.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-f
00:43:24,921 ERROR [STDERR] 20.12.2007 0:43:24
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/tmp/deploy/jboss-seam-booking55101-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-fn.taglib.xml
00:43:25,546 ERROR [STDERR] 20.12.2007 0:43:25
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:vfsfile:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/deploy/jboss-seam-booking.ear/jboss-seam-booking.war/WEB-INF/lib/richfaces-ui.jar!/META-INF/a4j.ta
00:43:25,562 ERROR [STDERR] 20.12.2007 0:43:25
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/tmp/deploy/jboss-seam-booking55101-exp.war/WEB-INF/lib/richfaces-ui.jar!/META-INF/a4j.taglib.xml
00:43:25,828 ERROR [STDERR] 20.12.2007 0:43:25
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:vfsfile:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/deploy/jboss-seam-booking.ear/jboss-seam-booking.war/WEB-INF/lib/richfaces-ui.jar!/META-INF/ajax4j
00:43:25,828 ERROR [STDERR] 20.12.2007 0:43:25
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/tmp/deploy/jboss-seam-booking55101-exp.war/WEB-INF/lib/richfaces-ui.jar!/META-INF/ajax4jsf.taglib.xml
00:43:26,640 ERROR [STDERR] 20.12.2007 0:43:26
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:vfsfile:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/deploy/jboss-seam-booking.ear/jboss-seam-booking.war/WEB-INF/lib/richfaces-ui.jar!/META-INF/rich.t
00:43:26,656 ERROR [STDERR] 20.12.2007 0:43:26
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/tmp/deploy/jboss-seam-booking55101-exp.war/WEB-INF/lib/richfaces-ui.jar!/META-INF/rich.taglib.xml
00:43:27,468 ERROR [STDERR] 20.12.2007 0:43:27
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:vfsfile:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/deploy/jboss-seam-booking.ear/jboss-seam-booking.war/WEB-INF/lib/richfaces-ui.jar!/META-INF/richfa
00:43:27,468 ERROR [STDERR] 20.12.2007 0:43:27
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/tmp/deploy/jboss-seam-booking55101-exp.war/WEB-INF/lib/richfaces-ui.jar!/META-INF/richfaces.taglib.xm
00:46:21,656 WARN [arjLoggerI18N]
[com.arjuna.ats.arjuna.coordinator.BasicAction_58] - Abort of action id
a0e3313:85f:4769ab0d:76 invoked while multiple threads active within it.
00:46:21,656 WARN [arjLoggerI18N]
[com.arjuna.ats.arjuna.coordinator.CheckedAction_2] -
CheckedAction::check - atomic action a0e3313:85f:4769ab0d:76 aborting
with 1 threads active!
00:46:32,890 WARN [arjLoggerI18N]
[com.arjuna.ats.arjuna.coordinator.BasicAction_40] - Abort called on
already aborted atomic action a0e3313:85f:4769ab0d:76
00:46:32,890 ERROR [SeamPhaseListener] uncaught exception
java.lang.IllegalStateException: Could not commit transaction
at
org.jboss.seam.jsf.SeamPhaseListener.commitOrRollback(SeamPhaseListener.java:599)
at
org.jboss.seam.jsf.SeamPhaseListener.handleTransactionsAfterPhase(SeamPhaseListener.java:332)
at
org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:233)
at
org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:184)
at
com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:280)
at
com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
at
org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68)
at
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at
org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85)
at
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at
org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
at
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at
org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
at
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at
org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141)
at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281)
at
org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60)
at
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
at
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:189)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:90)
at
org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:96)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:285)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.IllegalStateException:
[com.arjuna.ats.internal.jta.transaction.arjunacore.inactive]
[com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] The
transaction is not active!
at
com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.rollbackAndDisassociate(TransactionImple.java:1473)
at
com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.rollback(BaseTransaction.java:163)
at
com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.rollback(BaseTransactionManagerDelegate.java:126)
at
org.jboss.tm.usertx.client.ServerVMClientUserTransaction.rollback(ServerVMClientUserTransaction.java:141)
at
org.jboss.seam.transaction.UTTransaction.rollback(UTTransaction.java:66)
at
org.jboss.seam.jsf.SeamPhaseListener.commitOrRollback(SeamPhaseListener.java:594)
... 43 more
00:48:53,421 ERROR [STDERR] 20.12.2007 0:48:53
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:vfsfile:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/deploy/jboss-seam-booking.ear/jboss-seam-booking.war/WEB-INF/lib/jboss-seam-ui.jar!/META-INF/s.taglib.xml
00:49:03,203 ERROR [STDERR] 20.12.2007 0:49:03
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/tmp/deploy/jboss-seam-booking55101-exp.war/WEB-INF/lib/jboss-seam-ui.jar!/META-INF/s.taglib.xml
00:49:03,625 ERROR [STDERR] 20.12.2007 0:49:03
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:vfsfile:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/deploy/jboss-seam-booking.ear/jboss-seam-booking.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-core.taglib.xml
00:49:03,625 ERROR [STDERR] 20.12.2007 0:49:03
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/tmp/deploy/jboss-seam-booking55101-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-core.taglib.xml
00:49:03,937 ERROR [STDERR] 20.12.2007 0:49:03
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:vfsfile:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/deploy/jboss-seam-booking.ear/jboss-seam-booking.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-html.taglib.xml
00:49:03,937 ERROR [STDERR] 20.12.2007 0:49:03
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/tmp/deploy/jboss-seam-booking55101-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-html.taglib.xml
00:49:04,625 ERROR [STDERR] 20.12.2007 0:49:04
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:vfsfile:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/deploy/jboss-seam-booking.ear/jboss-seam-booking.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-ui.taglib.xml
00:49:04,625 ERROR [STDERR] 20.12.2007 0:49:04
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/tmp/deploy/jboss-seam-booking55101-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-ui.taglib.xml
00:49:06,546 ERROR [STDERR] 20.12.2007 0:49:06
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:vfsfile:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/deploy/jboss-seam-booking.ear/jboss-seam-booking.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-core.taglib.xml
00:49:06,562 ERROR [STDERR] 20.12.2007 0:49:06
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/tmp/deploy/jboss-seam-booking55101-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-core.taglib.xml
00:49:08,062 ERROR [STDERR] 20.12.2007 0:49:08
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:vfsfile:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/deploy/jboss-seam-booking.ear/jboss-seam-booking.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-fn.taglib.xml
00:49:08,062 ERROR [STDERR] 20.12.2007 0:49:08
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/tmp/deploy/jboss-seam-booking55101-exp.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-fn.taglib.xml
00:49:09,750 ERROR [STDERR] 20.12.2007 0:49:09
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:vfsfile:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/deploy/jboss-seam-booking.ear/jboss-seam-booking.war/WEB-INF/lib/richfaces-ui.jar!/META-INF/a4j.taglib.xml
00:49:09,765 ERROR [STDERR] 20.12.2007 0:49:09
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/tmp/deploy/jboss-seam-booking55101-exp.war/WEB-INF/lib/richfaces-ui.jar!/META-INF/a4j.taglib.xml
00:49:10,984 ERROR [STDERR] 20.12.2007 0:49:10
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:vfsfile:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/deploy/jboss-seam-booking.ear/jboss-seam-booking.war/WEB-INF/lib/richfaces-ui.jar!/META-INF/ajax4jsf.taglib.xml
00:49:11,000 ERROR [STDERR] 20.12.2007 0:49:11
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/tmp/deploy/jboss-seam-booking55101-exp.war/WEB-INF/lib/richfaces-ui.jar!/META-INF/ajax4jsf.taglib.xml
00:49:13,562 ERROR [STDERR] 20.12.2007 0:49:13
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:vfsfile:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/deploy/jboss-seam-booking.ear/jboss-seam-booking.war/WEB-INF/lib/richfaces-ui.jar!/META-INF/rich.taglib.xml
00:49:13,578 ERROR [STDERR] 20.12.2007 0:49:13
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/tmp/deploy/jboss-seam-booking55101-exp.war/WEB-INF/lib/richfaces-ui.jar!/META-INF/rich.taglib.xml
00:49:14,093 ERROR [STDERR] 20.12.2007 0:49:14
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:vfsfile:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/deploy/jboss-seam-booking.ear/jboss-seam-booking.war/WEB-INF/lib/richfaces-ui.jar!/META-INF/richfaces.taglib.xml
00:49:14,109 ERROR [STDERR] 20.12.2007 0:49:14
com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from:
jar:file:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.Beta3/server/all/tmp/deploy/jboss-seam-booking55101-exp.war/WEB-INF/lib/richfaces-ui.jar!/META-INF/richfaces.taglib.xml
5:03 p.m.
New subject: Beta3 status -
Guess they are ran on different machines with different ant env.
Since Pete can't really fully determine the cause of it.
Scott M Stark wrote:
We have had successful test runs with the seam.xml previously, 254
for
example:
http://hudson.qa.jboss.com/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15/254/...
_jars-seam:
[copy] Copying 5 files to
/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/output/lib
Scott M Stark wrote:
> The build has failed due to the seam.xml section. Must be due to an ant
> version problem:
>
> BUILD FAILED
>
/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/build.xml:855:
> The following error occurred while executing this line:
>
/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/imports/sections/seam.xml:12:
> The <urn:maven-artifact-ant:dependencies> type doesn't support the
> "versionsid" attribute.
>
> testsuite/build.sh works for me, as well as ant 1.6.5 standalone, so
> what ant would be used for the build?
>
> Dimitris Andreadis wrote:
>> Trunk is now building again, and there is an in-progress run that needs
>> another 5 hours:
>>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>>
>>
>> Can we get a status of the last tasks?
>>
>> http://jira.jboss.com/jira/browse/JBAS-4671 - DsDataSourceTemplate
>> (Alexey/Scott)
>> http://jira.jboss.com/jira/browse/JBAS-5064 - Seam Usage/Testing (Ales)
>> http://jira.jboss.com/jira/browse/JBAS-5016 - Wikis (Scott)
>>
>> ThomasD made also a last minute update to juddi/scout. This is being
>> tested now in the current test run, but I don't know how/if it affects TCK.
>>
>> He also reported the following regression. Was AbstractAnnotationImpl
>> somehow moved?
>>
>> NoClassDefFoundError: org/jboss/metadata/annotation/AbstractAnnotationImpl
>> http://jira.jboss.com/jira/browse/JBAS-5093
>>
>> We need to wrap-up, ASAP.
>>
>> /D
>>
>> Scott M Stark wrote:
>>> The 2.0.0.Beta9 release is out the tests are passing. Just need a good
>>> testsuite run to branch.
>>>
>>> Scott M Stark wrote:
>>>> So all that is left to cleanup is the ProfileServiceUnitTestCase
>>>> failures. Still working on whether the ManagedDeployment problem with
>>>> the deploy/messaging directory is an api problem that needs to be fixed.
>>>> A MC 2.0.0.Beta9 release and another testsuite run is needed at a
>>>> minimum.
>>>>
>>>> Rajesh Rajasekaran wrote:
>>>>> Yes. That's right. The build was still running.
>>>>> The testsuite run completed but before publishing and email
>>>>> notification
>>>>> someone had aborted.
>>>>> However the results are available on the internal instance.
>>>>>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>>>>>
>>>>>
>>>>>
>>>>> 191 failures.
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
5:09 p.m.
New subject: Beta3 status -
As discussed here
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=125488 I used
maven ant tasks to download the artifacts for the Seam test.
In older versions of maven-ant-tasks.jar the versionsId stuff isn't
implemented. QA lab machines have an older version of
maven-ant-tasks.jar (2.0.5 IIRC) in the ant userlib directory. For some
reason sometimes ant uses the one we tell it to (from thirdparty) and
sometimes from ant's userlib dir. I couldn't isolate why.
I got round this on the Seam Hudson builds by running ant with the
-nouserlib option (which means it always uses the up to date version).
Ales Justin wrote:
Guess they are ran on different machines with different ant env.
Since Pete can't really fully determine the cause of it.
Scott M Stark wrote:
> We have had successful test runs with the seam.xml previously, 254 for
> example:
> http://hudson.qa.jboss.com/hudson/job/JBoss-AS-5.0.x-TestSuite-sun15/254/...
>
>
> _jars-seam:
> [copy] Copying 5 files to
>
/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/output/lib
>
>
>
> Scott M Stark wrote:
>> The build has failed due to the seam.xml section. Must be due to an ant
>> version problem:
>>
>> BUILD FAILED
>>
/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/build.xml:855:
>>
>> The following error occurred while executing this line:
>>
/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/imports/sections/seam.xml:12:
>>
>> The <urn:maven-artifact-ant:dependencies> type doesn't support the
>> "versionsid" attribute.
>>
>> testsuite/build.sh works for me, as well as ant 1.6.5 standalone, so
>> what ant would be used for the build?
>>
>> Dimitris Andreadis wrote:
>>> Trunk is now building again, and there is an in-progress run that needs
>>> another 5 hours:
>>>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>>>
>>>
>>>
>>> Can we get a status of the last tasks?
>>>
>>> http://jira.jboss.com/jira/browse/JBAS-4671 - DsDataSourceTemplate
>>> (Alexey/Scott)
>>> http://jira.jboss.com/jira/browse/JBAS-5064 - Seam Usage/Testing (Ales)
>>> http://jira.jboss.com/jira/browse/JBAS-5016 - Wikis (Scott)
>>>
>>> ThomasD made also a last minute update to juddi/scout. This is being
>>> tested now in the current test run, but I don't know how/if it
>>> affects TCK.
>>>
>>> He also reported the following regression. Was AbstractAnnotationImpl
>>> somehow moved?
>>>
>>> NoClassDefFoundError:
>>> org/jboss/metadata/annotation/AbstractAnnotationImpl
>>> http://jira.jboss.com/jira/browse/JBAS-5093
>>>
>>> We need to wrap-up, ASAP.
>>>
>>> /D
>>>
>>> Scott M Stark wrote:
>>>> The 2.0.0.Beta9 release is out the tests are passing. Just need a good
>>>> testsuite run to branch.
>>>>
>>>> Scott M Stark wrote:
>>>>> So all that is left to cleanup is the ProfileServiceUnitTestCase
>>>>> failures. Still working on whether the ManagedDeployment problem
with
>>>>> the deploy/messaging directory is an api problem that needs to be
>>>>> fixed.
>>>>> A MC 2.0.0.Beta9 release and another testsuite run is needed at a
>>>>> minimum.
>>>>>
>>>>> Rajesh Rajasekaran wrote:
>>>>>> Yes. That's right. The build was still running.
>>>>>> The testsuite run completed but before publishing and email
>>>>>> notification
>>>>>> someone had aborted.
>>>>>> However the results are available on the internal instance.
>>>>>>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> 191 failures.
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
5:28 p.m.
New subject: Beta3 status -
I get this NPE when running Seam examples (tried Booking and
Numberguess, pops in both):
I did delete data directory before running AS instance.
HSQL problem?
00:23:17,203 INFO [EJBContainer] STARTED EJB:
org.jboss.seam.async.TimerServiceDispatcher ejbName: TimerServiceDispatcher
00:23:18,015 INFO [EJBContainer] STOPPED EJB:
org.jboss.seam.async.TimerServiceDispatcher ejbName: TimerServiceDispatcher
00:23:18,015 ERROR [AbstractKernelController] Error installing to Start:
name=jboss.j2ee:ear=jboss-seam-numberguess.ear,jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3
state=Creat
java.lang.NullPointerException
at
org.jboss.ejb.txtimer.EJBTimerServiceImpl.restoreTimers(EJBTimerServiceImpl.java:452)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy89.restoreTimers(Unknown Source)
at
org.jboss.ejb3.timerservice.jboss.JBossTimerServiceFactory.restoreTimerService(JBossTimerServiceFactory.java:121)
at
org.jboss.ejb3.stateless.StatelessContainer.start(StatelessContainer.java:128)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:56)
at
org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:110)
at
org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
at
org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:214)
at
org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:45)
at
org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:108)
at
org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:69)
at
org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221)
at
org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:135)
at
org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:46)
at
org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
at
org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
at
org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:574)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:398)
at
org.jboss.kernel.plugins.dependency.AbstractKernelController.install(AbstractKernelController.java:96)
at
org.jboss.kernel.plugins.dependency.AbstractKernelController.install(AbstractKernelController.java:90)
at
org.jboss.ejb3.MCKernelAbstraction.install(MCKernelAbstraction.java:151)
at
org.jboss.ejb3.Ejb3Deployment.registerEJBContainer(Ejb3Deployment.java:350)
at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:411)
at
org.jboss.ejb3.deployers.EJBStage2Deployer.deploy(EJBStage2Deployer.java:53)
at
org.jboss.ejb3.deployers.EJBStage2Deployer.deploy(EJBStage2Deployer.java:37)
at
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:65)
at
org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:853)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:906)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:794)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:498)
at
org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:506)
at
org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:245)
at
org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131)
at
org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:408)
at org.jboss.Main.boot(Main.java:208)
at org.jboss.Main$1.run(Main.java:534)
at java.lang.Thread.run(Thread.java:595)
*** CONTEXTS IN ERROR: Name -> Error
jboss.j2ee:ear=jboss-seam-numberguess.ear,jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3
-> java.lang.NullPointerException
8:47 p.m.
New subject: Beta3 status -
That refers to a null persistencypolicy as per
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/trunk/server/src/main/...
I am wondering why Carlo added an assert statement rather than a runtime
exception to catch this NPE.
Ales Justin wrote:
I get this NPE when running Seam examples (tried Booking and
Numberguess, pops in both):
I did delete data directory before running AS instance.
HSQL problem?
00:23:17,203 INFO [EJBContainer] STARTED EJB:
org.jboss.seam.async.TimerServiceDispatcher ejbName: TimerServiceDispatcher
00:23:18,015 INFO [EJBContainer] STOPPED EJB:
org.jboss.seam.async.TimerServiceDispatcher ejbName: TimerServiceDispatcher
00:23:18,015 ERROR [AbstractKernelController] Error installing to Start:
name=jboss.j2ee:ear=jboss-seam-numberguess.ear,jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3
state=Creat
java.lang.NullPointerException
at
org.jboss.ejb.txtimer.EJBTimerServiceImpl.restoreTimers(EJBTimerServiceImpl.java:452)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy89.restoreTimers(Unknown Source)
at
org.jboss.ejb3.timerservice.jboss.JBossTimerServiceFactory.restoreTimerService(JBossTimerServiceFactory.java:121)
at
org.jboss.ejb3.stateless.StatelessContainer.start(StatelessContainer.java:128)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:56)
at
org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:110)
at
org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
at
org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:214)
at
org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:45)
at
org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:108)
at
org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:69)
at
org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221)
at
org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:135)
at
org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:46)
at
org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
at
org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
at
org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:574)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:398)
at
org.jboss.kernel.plugins.dependency.AbstractKernelController.install(AbstractKernelController.java:96)
at
org.jboss.kernel.plugins.dependency.AbstractKernelController.install(AbstractKernelController.java:90)
at
org.jboss.ejb3.MCKernelAbstraction.install(MCKernelAbstraction.java:151)
at
org.jboss.ejb3.Ejb3Deployment.registerEJBContainer(Ejb3Deployment.java:350)
at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:411)
at
org.jboss.ejb3.deployers.EJBStage2Deployer.deploy(EJBStage2Deployer.java:53)
at
org.jboss.ejb3.deployers.EJBStage2Deployer.deploy(EJBStage2Deployer.java:37)
at
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:65)
at
org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:853)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:906)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:794)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:498)
at
org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:506)
at
org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:245)
at
org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131)
at
org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:408)
at org.jboss.Main.boot(Main.java:208)
at org.jboss.Main$1.run(Main.java:534)
at java.lang.Thread.run(Thread.java:595)
*** CONTEXTS IN ERROR: Name -> Error
jboss.j2ee:ear=jboss-seam-numberguess.ear,jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3
-> java.lang.NullPointerException
8:50 p.m.
New subject: Beta3 status -
I think maybe the issue is that the EJB3 deployment is being considered
as ejb2. Hence the services defined in deploy/ejb2-timer-service.xml are
kicking in rather than deploy/ejb3-timer-service.xml
Anil Saldhana wrote:
That refers to a null persistencypolicy as per
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/trunk/server/src/main/...
I am wondering why Carlo added an assert statement rather than a runtime
exception to catch this NPE.
Ales Justin wrote:
> I get this NPE when running Seam examples (tried Booking and
> Numberguess, pops in both):
>
> I did delete data directory before running AS instance.
> HSQL problem?
>
>
> 00:23:17,203 INFO [EJBContainer] STARTED EJB:
> org.jboss.seam.async.TimerServiceDispatcher ejbName: TimerServiceDispatcher
> 00:23:18,015 INFO [EJBContainer] STOPPED EJB:
> org.jboss.seam.async.TimerServiceDispatcher ejbName: TimerServiceDispatcher
> 00:23:18,015 ERROR [AbstractKernelController] Error installing to Start:
>
name=jboss.j2ee:ear=jboss-seam-numberguess.ear,jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3
> state=Creat
> java.lang.NullPointerException
> at
>
org.jboss.ejb.txtimer.EJBTimerServiceImpl.restoreTimers(EJBTimerServiceImpl.java:452)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>
> at
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>
> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>
> at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
> at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
> at $Proxy89.restoreTimers(Unknown Source)
> at
>
org.jboss.ejb3.timerservice.jboss.JBossTimerServiceFactory.restoreTimerService(JBossTimerServiceFactory.java:121)
>
> at
> org.jboss.ejb3.stateless.StatelessContainer.start(StatelessContainer.java:128)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>
> at
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
>
org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:56)
>
> at
>
org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:110)
>
> at
>
org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
>
> at
>
org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:214)
>
> at
>
org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:45)
>
> at
>
org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:108)
>
> at
>
org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:69)
>
> at
>
org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221)
>
> at
>
org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:135)
>
> at
>
org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:46)
>
> at
>
org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
>
> at
>
org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
>
> at
>
org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
>
> at
>
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
>
> at
>
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
>
> at
>
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
>
> at
>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
>
> at
>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
>
> at
> org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:574)
>
> at
> org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:398)
>
> at
>
org.jboss.kernel.plugins.dependency.AbstractKernelController.install(AbstractKernelController.java:96)
>
> at
>
org.jboss.kernel.plugins.dependency.AbstractKernelController.install(AbstractKernelController.java:90)
>
> at
> org.jboss.ejb3.MCKernelAbstraction.install(MCKernelAbstraction.java:151)
> at
> org.jboss.ejb3.Ejb3Deployment.registerEJBContainer(Ejb3Deployment.java:350)
> at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:411)
> at
> org.jboss.ejb3.deployers.EJBStage2Deployer.deploy(EJBStage2Deployer.java:53)
>
> at
> org.jboss.ejb3.deployers.EJBStage2Deployer.deploy(EJBStage2Deployer.java:37)
>
> at
>
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:65)
>
> at
>
org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
>
> at
>
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
>
> at
>
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:853)
>
> at
>
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:906)
>
> at
> org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:794)
>
> at
>
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
>
> at
>
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
>
> at
>
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
>
> at
>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
>
> at
>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
>
> at
> org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
>
> at
> org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
>
> at
> org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:498)
>
> at
> org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:506)
>
> at
>
org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:245)
>
> at
>
org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131)
>
> at
> org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:408)
> at org.jboss.Main.boot(Main.java:208)
> at org.jboss.Main$1.run(Main.java:534)
> at java.lang.Thread.run(Thread.java:595)
>
> *** CONTEXTS IN ERROR: Name -> Error
>
>
jboss.j2ee:ear=jboss-seam-numberguess.ear,jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3
> -> java.lang.NullPointerException
>
10:02 p.m.
New subject: Beta3 status - Seam examples
Human Seam example tests :-)
NumberGuess
- default == OK
- all == OK
Booking
- default == OK
- all == OK
DVD
- default == OK
- all == OK
At first we (Dimitris, Pete, me) all had similar problems.
With NumberGuess the Timer NPE, and Facelets NCDFE.
DVD had some problems finding Indexer SFSB.
It now all works for me (clean build), but it's the speed that's
problematic.
Booking and DVD examples are horribly horribly slow. ;-(
We need to look at the cause, cuz it's unbearable.
Couple of minutes to display a page.
Numberguess does a better job, but could do a lot faster, since it's
really trivial.
11:46 p.m.
New subject: Beta3 status - Seam examples
I see the same problem, and it looks like jsp class generation issues.
After 20-30 seconds the thread dump is still showing jsp compilation
going on:
"http-127.0.0.1-8080-2" daemon prio=1 tid=0x0000002ad25ebfb0 nid=0x6135
runnable [0x0000000042f78000..0x0000000042f7fd30]
at java.util.zip.ZipFile.getNextEntry(Native Method)
at java.util.zip.ZipFile.access$700(ZipFile.java:35)
at java.util.zip.ZipFile$3.nextElement(ZipFile.java:421)
- locked <0x0000002ac32fae58> (a java.util.jar.JarFile)
at java.util.zip.ZipFile$3.nextElement(ZipFile.java:415)
at java.util.jar.JarFile$1.nextElement(JarFile.java:221)
at java.util.jar.JarFile$1.nextElement(JarFile.java:220)
at
org.jboss.virtual.plugins.context.jar.AbstractJarHandler.initJarFile(AbstractJarHandler.java:145)
at
org.jboss.virtual.plugins.context.jar.JarHandler.<init>(JarHandler.java:81)
at
org.jboss.virtual.plugins.context.file.FileSystemContext.createVirtualFileHandler(FileSystemContext.java:179)
at
org.jboss.virtual.plugins.context.file.FileHandler.getChildren(FileHandler.java:179)
at
org.jboss.virtual.plugins.context.file.FileSystemContext.createVirtualFileHandler(FileSystemContext.java:239)
at
org.jboss.virtual.plugins.context.file.FileSystemContext.createVirtualFileHandler(FileSystemContext.java:186)
at
org.jboss.virtual.plugins.context.file.FileHandler.createChildHandler(FileHandler.java:216)
at
org.jboss.virtual.plugins.context.AbstractVirtualFileHandler.structuredFindChild(AbstractVirtualFileHandler.java:291)
at
org.jboss.virtual.plugins.context.file.FileHandler.findChild(FileHandler.java:199)
at
org.jboss.virtual.plugins.context.AbstractVFSContext.findChild(AbstractVFSContext.java:118)
at org.jboss.virtual.VFS.findChild(VFS.java:205)
at
org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.resolveVirtualFile(VirtualFileURLConnection.java:96)
at
org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.getVirtualFile(VirtualFileURLConnection.java:109)
- locked <0x0000002ac2fd33b8> (a
org.jboss.virtual.plugins.vfs.VirtualFileURLConnection)
at
org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.getInputStream(VirtualFileURLConnection.java:117)
at java.net.URL.openStream(URL.java:1007)
at sun.misc.URLClassPath$Loader.findResource(URLClassPath.java:472)
at sun.misc.URLClassPath.findResource(URLClassPath.java:142)
at java.net.URLClassLoader$2.run(URLClassLoader.java:362)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findResource(URLClassLoader.java:359)
at java.lang.ClassLoader.getResource(ClassLoader.java:977)
at
org.jboss.mx.loading.RepositoryClassLoader.getResourceLocally(RepositoryClassLoader.java:265)
at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:265)
at
org.jboss.mx.loading.UnifiedClassLoader.loadClassImpl(UnifiedClassLoader.java:290)
- locked <0x0000002aafc31f98> (a
org.jboss.mx.loading.UnifiedClassLoader3)
at
org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:441)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
- locked <0x0000002aafc31f98> (a
org.jboss.mx.loading.UnifiedClassLoader3)
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at
org.jboss.mx.loading.RepositoryClassLoader.findClassLocally(RepositoryClassLoader.java:608)
at
org.jboss.mx.loading.RepositoryClassLoader.findClass(RepositoryClassLoader.java:588)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
- locked <0x0000002aafc31f98> (a
org.jboss.mx.loading.UnifiedClassLoader3)
at
org.jboss.mx.loading.RepositoryClassLoader.loadClassLocally(RepositoryClassLoader.java:225)
at
org.jboss.mx.loading.ClassLoadingTask$ThreadTask.run(ClassLoadingTask.java:131)
at org.jboss.mx.loading.LoadMgr3.nextTask(LoadMgr3.java:399)
at
org.jboss.mx.loading.UnifiedClassLoader.loadClassImpl(UnifiedClassLoader.java:296)
- locked <0x0000002aafc31f98> (a
org.jboss.mx.loading.UnifiedClassLoader3)
at
org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:441)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
- locked <0x0000002aafc31f98> (a
org.jboss.mx.loading.UnifiedClassLoader3)
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at
org.jboss.mx.loading.RepositoryClassLoader.findClassLocally(RepositoryClassLoader.java:608)
at
org.jboss.mx.loading.RepositoryClassLoader.findClass(RepositoryClassLoader.java:588)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
- locked <0x0000002aafc31f98> (a
org.jboss.mx.loading.UnifiedClassLoader3)
at
org.jboss.mx.loading.RepositoryClassLoader.loadClassLocally(RepositoryClassLoader.java:225)
at
org.jboss.mx.loading.ClassLoadingTask$ThreadTask.run(ClassLoadingTask.java:131)
at org.jboss.mx.loading.LoadMgr3.nextTask(LoadMgr3.java:399)
at
org.jboss.mx.loading.UnifiedClassLoader.loadClassImpl(UnifiedClassLoader.java:296)
- locked <0x0000002aafc31f98> (a
org.jboss.mx.loading.UnifiedClassLoader3)
at
org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:441)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
- locked <0x0000002aafc31f98> (a
org.jboss.mx.loading.UnifiedClassLoader3)
at
org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:407)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:308)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:273)
at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:312)
- locked <0x0000002ab95e5a08> (a
org.apache.jasper.servlet.JspServletWrapper)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:337)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:189)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:90)
at
org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:96)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:285)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
Ales Justin wrote:
Human Seam example tests :-)
NumberGuess
- default == OK
- all == OK
Booking
- default == OK
- all == OK
DVD
- default == OK
- all == OK
At first we (Dimitris, Pete, me) all had similar problems.
With NumberGuess the Timer NPE, and Facelets NCDFE.
DVD had some problems finding Indexer SFSB.
It now all works for me (clean build), but it's the speed that's
problematic.
Booking and DVD examples are horribly horribly slow. ;-(
We need to look at the cause, cuz it's unbearable.
Couple of minutes to display a page.
Numberguess does a better job, but could do a lot faster, since it's
really trivial.
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
11:55 p.m.
New subject: Beta3 status - Seam examples
After I have been through the pages, the perf is better, but there still
seems to be too much time spent in vfs access. I'm also seeing tons of
/tmp/nestedjar30171.tmp files, so much so its filling up my /tmp dir. We
definitely need to work on the vfs for the next release.
Scott M Stark wrote:
I see the same problem, and it looks like jsp class generation
issues.
After 20-30 seconds the thread dump is still showing jsp compilation
going on:
5972
days inactive
5974
days old
jboss-development@lists.jboss.org
29 comments
8 participants
participants (8)
-
Ales Justin -
Alexey Loubyansky -
Anil Saldhana -
Dimitris Andreadis -
Pete Muir -
Rajesh Rajasekaran -
Ryan Campbell -
Scott M Stark