trunk testsuite status| JBoss.org Content Archive (Read Only)

15. Re: trunk testsuite status

starksm64 Mar 23, 2007 2:28 AM (in response to starksm64)

The leak is related to the 1.2.0.SP.snapshot.aop2beta version of jbm. If I revert back to 1.2.0.GA the tests run to completion:

...
[server:stop] Shutting down server: all
[server:stop] Shutting down server: /usr/java/jdk1.5.0_09/bin/java -cp /home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta2/bin/shutdown.jar:/home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta2/client/jbossall-client.jar:/home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta2/client/jboss-common.jar org.jboss.Shutdown --server jnp://localhost:1099 --shutdown
[server:stop] shutdownTimeout will be=45

BUILD SUCCESSFUL
Total time: 42 minutes 6 seconds

16. Re: trunk testsuite status

kabirkhan Mar 23, 2007 11:42 AM (in response to starksm64)

I fixed some leaks in aop 2 this morning related to the use of PER_INSTANCE scoped aspects, which I see messaging is using. I've added a new aop snapshot containing this fix to the repository. This *should* be fine to use with the 1.2.0.SP.snapshot.aop2beta. Unless I'm totally off the mark there are no changes in the woven code created by aop alpha3 and the current snapshot.

17. Re: trunk testsuite status

clebert.suconic Mar 23, 2007 1:17 PM (in response to starksm64)

this should be compatible... I think there is no problem on upgrading the dependency.

BTW: Is there a way of woven format being fixed between AOP 1.x and AOP 2.0? (at least aop classes compiled using 1.X should run fine on AOP 2.0 IMO.

18. Re: trunk testsuite status

kabirkhan Mar 23, 2007 1:25 PM (in response to starksm64)

AOP 2.0 uses a different weaving model "Generated Advisor". You can select the old one by passing in the old instrumentor into aopc, which at least should fix the memory leaks.

 <aopc optimized="${optimized}" compilerclasspathref="aop.task.classpath">
 ....
 <sysproperty key="jboss.aop.instrumentor" value="org.jboss.aop.instrument.ClassicInstrumentor"/>
 ....
 </aopc>

However, as I mentioned elsewhere compatibilty of woven classes across releases completely slipped my mind until the cache guys mentioned it so YMMV. I'll take a look though

19. Re: trunk testsuite status

starksm64 Mar 23, 2007 2:23 PM (in response to starksm64)

"kabir.khan@jboss.com" wrote:
I fixed some leaks in aop 2 this morning related to the use of PER_INSTANCE scoped aspects, which I see messaging is using. I've added a new aop snapshot containing this fix to the repository. This *should* be fine to use with the 1.2.0.SP.snapshot.aop2beta. Unless I'm totally off the mark there are no changes in the woven code created by aop alpha3 and the current snapshot.

This is beyond the 2.0.0.alpha4 and in the current snapshot?

20. Re: trunk testsuite status

starksm64 Mar 23, 2007 9:02 PM (in response to starksm64)

I tried running with:

aop: 2.0.0.alpha4
jbm: 1.2.0.SP.snapshot.aop2beta
remoting: 2.2.0.GA

and the run did complete although there still were OMEs. Apparently it got further along and limped to completion. I then ran with:

aop: snapshot
jbm: 1.2.0.SP.snapshot.aop2beta
remoting: 2.2.0.GA

and the run completed without OMEs. So there are both aop and remoting leaks that are fixed in these latter versions. Can you create an 2.0.0.alpha5 release of aop Kabir.

21. Re: trunk testsuite status

anil.saldhana Mar 23, 2007 9:48 PM (in response to starksm64)

Is the test suite totally unusable now? In the afternoon, I tried running the target "tests-jacc-security". Had OOME. Jacc server config did not start.

Scott, should we wait till the leaks are fixed with Kabir's proposed new 2.0.0.alpha5?

22. Re: trunk testsuite status

starksm64 Mar 23, 2007 11:03 PM (in response to starksm64)

That test runs to completion for me, but has many errors. Its not affected by the memory leak issue.

[starksm@succubus testsuite]$ ant tests-jacc-security
Buildfile: build.xml
Overriding previous definition of reference to jboss.test.classpath

tests-jacc-security:
 [echo] creating jacc config
 [copy] Copying 187 files to /home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta2/server/jacc
 [echo] Overwriting config descriptors
 [copy] Copying 7 files to /home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta2/server/jacc
[server:start] Starting server "jacc" with command:
[server:start] /usr/java/jdk1.5.0_09/bin/java -cp /home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta2/bin/run.jar:/usr/java/jdk1.5.0_09/lib/tools.jar org.jboss.Main -c jacc -b localhost
 [echo] Starting patternset=jacc.includes config=JACC
 [junit] Running org.jboss.test.cmp2.audit.test.AuditUnitTestCase
 [junit] Tests run: 7, Failures: 7, Errors: 0, Time elapsed: 3.659 sec
 [junit] Test org.jboss.test.cmp2.audit.test.AuditUnitTestCase FAILED
 [junit] Running org.jboss.test.cmp2.cmrstress.CMRStressTestCase
 [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.319 sec
 [junit] Test org.jboss.test.cmp2.cmrstress.CMRStressTestCase FAILED
 [junit] Running org.jboss.test.cmp2.cmrtransaction.test.CMRTransactionUnitTestCase
 [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.288 sec
 [junit] Test org.jboss.test.cmp2.cmrtransaction.test.CMRTransactionUnitTestCase FAILED
 [junit] Running org.jboss.test.cmp2.commerce.CompleteUnitTestCase
 [junit] Tests run: 32, Failures: 0, Errors: 31, Time elapsed: 2.404 sec
 [junit] Test org.jboss.test.cmp2.commerce.CompleteUnitTestCase FAILED
 [junit] Running org.jboss.test.cmp2.perf.test.PerfUnitTestCase
 [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.325 sec
 [junit] Test org.jboss.test.cmp2.perf.test.PerfUnitTestCase FAILED
 [junit] Running org.jboss.test.cmp2.relationship.RelationshipUnitTestCase
 [junit] Tests run: 21, Failures: 0, Errors: 21, Time elapsed: 2.141 sec
 [junit] Test org.jboss.test.cmp2.relationship.RelationshipUnitTestCase FAILED
 [junit] Running org.jboss.test.cmp2.simple.SimpleUnitTestCase
 [junit] Tests run: 44, Failures: 0, Errors: 44, Time elapsed: 1.214 sec
 [junit] Test org.jboss.test.cmp2.simple.SimpleUnitTestCase FAILED
 [junit] Running org.jboss.test.jacc.test.CallerInRoleUnitTestCase
 [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 1.152 sec
 [junit] Test org.jboss.test.jacc.test.CallerInRoleUnitTestCase FAILED
 [junit] Running org.jboss.test.jacc.test.EJBSpecUnitTestCase
 [junit] Tests run: 23, Failures: 2, Errors: 20, Time elapsed: 4.275 sec
 [junit] Test org.jboss.test.jacc.test.EJBSpecUnitTestCase FAILED
 [junit] Running org.jboss.test.jacc.test.FormAuthUnitTestCase
 [junit] Tests run: 5, Failures: 4, Errors: 0, Time elapsed: 3.477 sec
 [junit] Test org.jboss.test.jacc.test.FormAuthUnitTestCase FAILED
 [junit] Running org.jboss.test.jacc.test.JMXConsoleUnitTestCase
 [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 3.171 sec
 [junit] Running org.jboss.test.jacc.test.MissingMethodUnitTestCase
 [junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 1.359 sec
 [junit] Test org.jboss.test.jacc.test.MissingMethodUnitTestCase FAILED
 [junit] Running org.jboss.test.jacc.test.WebConstraintsUnitTestCase
 [junit] Tests run: 4, Failures: 0, Errors: 3, Time elapsed: 0.768 sec
 [junit] Test org.jboss.test.jacc.test.WebConstraintsUnitTestCase FAILED
 [junit] Running org.jboss.test.jacc.test.WebIntegrationUnitTestCase
 [junit] Tests run: 37, Failures: 2, Errors: 22, Time elapsed: 4.829 sec
 [junit] Test org.jboss.test.jacc.test.WebIntegrationUnitTestCase FAILED
 [junit] Running org.jboss.test.jacc.test.WebPermissionsValidationTestCase
 [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 0.579 sec
 [junit] Test org.jboss.test.jacc.test.WebPermissionsValidationTestCase FAILED
 [junit] Running org.jboss.test.web.test.UserInRoleUnitTestCase
 [junit] Tests run: 4, Failures: 0, Errors: 3, Time elapsed: 0.973 sec
 [junit] Test org.jboss.test.web.test.UserInRoleUnitTestCase FAILED
 [junit] Running org.jboss.test.webservice.jbws309.JBWS309TestCase
 [junit] Tests run: 5, Failures: 0, Errors: 5, Time elapsed: 4.478 sec
 [junit] Test org.jboss.test.webservice.jbws309.JBWS309TestCase FAILED
[server:stop] Shutting down server: jacc
[server:stop] Shutting down server: /usr/java/jdk1.5.0_09/bin/java -cp /home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta2/bin/shutdown.jar:/home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta2/client/jbossall-client.jar:/home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta2/client/jboss-common.jar org.jboss.Shutdown --server jnp://localhost:1099 --shutdown
[server:stop] shutdownTimeout will be=45

23. Re: trunk testsuite status

anil.saldhana Mar 24, 2007 1:27 AM (in response to starksm64)

This is after I checked out the workspace and did a clean build(nuked third party etc).

2007-03-24 00:22:45,046 DEBUG [org.jboss.system.server.profileservice.ServerImpl] Failed to start
java.lang.OutOfMemoryError: Java heap space
2007-03-24 00:22:45,046 ERROR [STDERR] Exception in thread "main"
2007-03-24 00:22:45,046 ERROR [STDERR] java.lang.OutOfMemoryError: Java heap space

Maybe you are trying with different thirdparty libraries for aop/remoting that are different from what are in build-thirdparty.xml

asaldhana~/JB5/trunk/testsuite>ant tests-jacc-security
Buildfile: build.xml
Overriding previous definition of reference to jboss.test.classpath

tests-jacc-security:
 [echo] creating jacc config
 [copy] Copying 187 files to C:\cygwin\home\asaldhana\JB5\trunk\build\output
\jboss-5.0.0.Beta2\server\jacc
 [echo] Overwriting config descriptors
 [copy] Copying 6 files to C:\cygwin\home\asaldhana\JB5\trunk\build\output\j
boss-5.0.0.Beta2\server\jacc
[server:start] Starting server "jacc" with command:
[server:start] C:\Java\jdk1.5.0_10\bin\java -cp C:\cygwin\home\asaldhana\JB5\tru
nk\build\output\jboss-5.0.0.Beta2\bin\run.jar;c:\java\jdk1.5.0_10\lib\tools.jar
 org.jboss.Main -c jacc -b localhost

BUILD FAILED
C:\cygwin\home\asaldhana\JB5\trunk\testsuite\build.xml:2341: Error starting serv
er "jacc": Server failed to start; see logs. exit code: 0

Total time: 2 minutes 42 seconds
asaldhana~/JB5/trunk/testsuite>

24. Re: trunk testsuite status

ccrouch Mar 24, 2007 9:55 AM (in response to starksm64)

Anil
I don't think this is anything to do with Scott's environment, cruisecontrol is also running the /trunk testsuite to completion:

http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-testsuite-1.5?log=log20070323220318

You can see the "(JACC)" tests running and failing.

The last checkin cruisecontrol included was r61639. According to http://fisheye.jboss.com/changelog/JBossAS/ the only commit since then to trunk was

61651 by scott.stark@jboss.org on 24 March 2007, 00:47:02 -0400 (8 hours ago) Correct the web app object name for the root context

trunk/server/src/main/org/jboss/web/deployers/AbstractWarDeployer.java

which doesn't look like it should cause the problems you are seeing.

Cheers

25. Re: trunk testsuite status

kabirkhan Mar 26, 2007 11:39 AM (in response to starksm64)

"scott.stark@jboss.org" wrote:
"kabir.khan@jboss.com" wrote:
I fixed some leaks in aop 2 this morning related to the use of PER_INSTANCE scoped aspects, which I see messaging is using. I've added a new aop snapshot containing this fix to the repository. This *should* be fine to use with the 1.2.0.SP.snapshot.aop2beta. Unless I'm totally off the mark there are no changes in the woven code created by aop alpha3 and the current snapshot.

This is beyond the 2.0.0.alpha4 and in the current snapshot?

Sorry did not see this before now. Yes, the fix is in the current snapshot, which is newer than alpha4

26. Re: trunk testsuite status

kabirkhan Mar 26, 2007 11:45 AM (in response to starksm64)

"clebert.suconic@jboss.com" wrote:
this should be compatible... I think there is no problem on upgrading the dependency.

BTW: Is there a way of woven format being fixed between AOP 1.x and AOP 2.0? (at least aop classes compiled using 1.X should run fine on AOP 2.0 IMO.

Let's discuss this here
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031647#4031647

27. Re: trunk testsuite status

starksm64 Mar 26, 2007 8:59 PM (in response to starksm64)

The WebIntegrationUnitTestCase is now in descent shape. Of the 4 errors 2 are minor JBAS-3883, JBAS-4253 and the other 2 are issues with the new VDF not failing bad deployments. That will be postponed to the next beta.

[starksm@succubus testsuite]$
ant -Dtest=org.jboss.test.web.test.WebIntegrationUnitTestCase -Dnojars=t
Buildfile: build.xml
Overriding previous definition of reference to jboss.test.classpath

one-test:
 [mkdir] Created dir: /home/svn/JBossHead/jboss-head/testsuite/output/log
 [junit] Running org.jboss.test.web.test.WebIntegrationUnitTestCase
 [junit] Found log4j.xml: file:/home/svn/JBossHead/jboss-head/testsuite/output/resources/log4j.xml
 [junit] Tests run: 36, Failures: 2, Errors: 2, Time elapsed: 15.711 sec
 [junit] Test org.jboss.test.web.test.WebIntegrationUnitTestCase FAILED

BUILD SUCCESSFUL
Total time: 18 seconds

28. Re: trunk testsuite status

anil.saldhana Mar 27, 2007 6:29 PM (in response to starksm64)

With a new checkout of trunk, the test suite server config is still choking with heap space errors. This is on windows. I have 2gig ram.

ant tests-jacc-security

The 4.2 test suite runs fine for the afore mentioned target.

Scott/Charles, have you tried running any of the server configs on windows?

I do not think the following jira issue is relevant but is close to what I am talking about.
http://jira.jboss.com/jira/browse/JBAS-4216

29. Re: trunk testsuite status

starksm64 Mar 27, 2007 7:49 PM (in response to starksm64)

I have not been so I tried it and do see th OMEs. I have not looked into why this is.

[log]$ grep OutOfM server.log
java.lang.OutOfMemoryError: Java heap space
Caused by: java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
2007-03-27 16:32:44,187 ERROR [STDERR] java.lang.OutOfMemoryError: Java heap spa
ce
2007-03-27 16:33:07,000 ERROR [STDERR] java.lang.OutOfMemoryError: Java heap spa
ce
2007-03-27 16:33:07,796 ERROR [STDERR] java.lang.OutOfMemoryError: Java heap spa
ce
2007-03-27 16:33:08,609 ERROR [STDERR] java.lang.OutOfMemoryError: Java heap spa
ce
2007-03-27 16:33:11,828 ERROR [STDERR] java.lang.OutOfMemoryError: Java heap spa
ce
2007-03-27 16:33:17,031 ERROR [STDERR] java.lang.OutOfMemoryError: Java heap spa
ce
2007-03-27 16:33:20,265 ERROR [STDERR] java.lang.OutOfMemoryError: Java heap spa
ce
2007-03-27 16:33:26,656 ERROR [STDERR] java.lang.OutOfMemoryError: Java heap spa
ce
2007-03-27 16:33:29,906 ERROR [STDERR] java.lang.OutOfMemoryError: Java heap spa
ce
java.lang.OutOfMemoryError: Java heap space