[JBoss-dev] jboss-3.2-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20060321234012 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:235: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:26: Build Successful - Tests completed with errors or failures.Date of build: 03/21/2006 23:40:12Time to build: 49 minutes 24 seconds Unit Tests: (1851) Total Errors and Failures: (1)testUnackedQueueorg.jboss.test.jbossmq.test.UnackedUnitTestCase Modifications since last build: (first 50 of 0)
[JBoss-dev] JBossCache 1.3.0.CR1 released
JBossCache 1.3.0.CR1 has been released. This can be downloaded from http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=102339&release_id=403608 Thanks Rajesh JBoss QA
[JBoss-dev] jboss-cache-testsuite build.46 Build Fixed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060321195049Lbuild.46 BUILD COMPLETE - build.46Date of build: 03/21/2006 19:50:49Time to build: 35 minutes 5 secondsLast changed: 03/21/2006 18:40:19Last log entry: Disabled a bunch of tests Unit Tests: (1369) Total Errors and Failures: (0)All Tests Passed Modifications since last build: (first 50 of 4)1.2modifiedmsurtanitests/functional/org/jboss/cache/loader/DummyCacheLoader.javamore dummy meths1.26modifiedmsurtanisrc/org/jboss/cache/interceptors/CacheLoaderInterceptor.javaAdded deadlock detection unit test and fixed deadlock problem in cache loader interceptor when concurrent node creation occurs1.1addedmsurtanitests/functional/org/jboss/cache/loader/deadlock/ConcurrentCreationDeadlockTest.javaAdded deadlock detection unit test and fixed deadlock problem in cache loader interceptor when concurrent node creation occurs1.2modifiedmsurtanitests/functional/org/jboss/cache/loader/deadlock/ConcurrentCreationDeadlockTest.javaDisabled a bunch of tests
[JBoss-dev] jboss-4.0-testsuite Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20060321182057 BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:224: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-common.xml:148: Exit code: 1 See tests.log in Build Artifacts for details.Date of build: 03/21/2006 18:20:57Time to build: 72 minutes 14 secondsLast changed: 03/21/2006 12:42:34Last log entry: correct trove version Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (first 50 of 1907)1.1.2.4modifiedstarksmtestsuite/src/resources/test-configs/jacc/conf/login-config.xmlAdd a legacy client-login that clears the security association stack on logout1.2.6.2modifiedstarksmtestsuite/src/main/org/jboss/test/cmp2/audit/interfaces/ApplicationCallbackHandler.javaAdd a login method that takes the configuration name1.6.2.33modifiedstarksmtestsuite/imports/server-config.xmlUpdate the create-config/newconf-src attribute description1.2.6.2modifiedstarksmtestsuite/src/main/org/jboss/test/cmp2/audit/beans/AuditSessionBean.javaJBAS-2947, add an updateAuditMappedCheck that uses the old client-login config that clears the security association on logout1.2.6.2modifiedstarksmtestsuite/src/main/org/jboss/test/cmp2/audit/test/AuditUnitTestCase.javaJBAS-2947, add an updateAuditMappedCheck that uses the old client-login config that clears the security association on logout1.406.2.152modifiedstarksmtestsuite/build.xmlJBAS-2947, Use newconf-src="" for the tests-jacc-securitymgr target1.78.2.7modifiedstarksmserver/src/main/org/jboss/ejb/EnterpriseContext.javaJBAS-2947, Clear the bean principal used for getCallerPrincipal and synch with the new call principal in setPrincipal to ensure the getCallerPrincipal is valid for the duration of the call1.78.2.8modifiedstarksmserver/src/main/org/jboss/ejb/EnterpriseContext.javaRemove the System.out debug calls1.78.2.9modifiedstarksmserver/src/main/org/jboss/ejb/EnterpriseContext.javaJBAS-2947, Only set the bean principal via getCallerPrincipal if there is a security domain1.2.2.21modifiedbstansberrytomcat/src/resources/tc5-cluster-service.xml[JBAS-2966] Use optimized UDP config1.1.2.3modifiedbillserver/src/resources/schema/jboss_5_0.xsdno message1.1.4.6modifiedbstansberrytestsuite/src/resources/test-configs/tomcat-sso-cluster/deploy/tc5-cluster-service.xml[JBAS-2966] Use optimized UDP config1.4.6.6modifiedstarksmtestsuite/src/main/org/jboss/test/naming/test/SimpleUnitTestCase.javaJBAS-2744, Use the getServerHost() as the jnp.localAddress value1.1.2.5modifiedbillejb3x/src/main/javax/ejb/ApplicationException.javabackmerge1.1.6.5modifiedbillejb3x/src/main/javax/ejb/AroundInvoke.javabackmerge1.1.2.6modifiedbillejb3x/src/main/javax/ejb/EJBAccessException.javabackmerge1.1.2.6modifiedbillejb3x/src/main/javax/ejb/EJBNoSuchObjectException.javabackmerge1.1.2.6modifiedbillejb3x/src/main/javax/ejb/EJBTransactionRequiredException.javabackmerge1.1.2.6modifiedbillejb3x/src/main/javax/ejb/EJBTransactionRolledbackException.javabackmerge1.1.4.4modifiedbillejb3x/src/main/javax/ejb/ExcludeClassInterceptors.javabackmerge1.1.4.4modifiedbillejb3x/src/main/javax/ejb/ExcludeDefaultInterceptors.javabackmerge1.1.2.5modifiedbillejb3x/src/main/javax/ejb/Init.javabackmerge1.3.2.5modifiedbillejb3x/src/main/javax/ejb/Interceptors.javabackmerge1.1.6.5modifiedbillejb3x/src/main/javax/ejb/InvocationContext.javabackmerge1.2.4.6modifiedbillejb3x/src/main/javax/ejb/Local.javabackmerge1.1.2.3modifiedbillejb3x/src/main/javax/ejb/LocalHome.javabackmerge1.4.4.6modifiedbillejb3x/src/main/javax/ejb/MessageDriven.javabackmerge1.1.6.5modifiedbillejb3x/src/main/javax/ejb/PostActivate.javabackmerge1.1.6.5deletedbillejb3x/src/main/javax/ejb/PostConstruct.javabackmerge1.1.6.5deletedbillejb3x/src/main/javax/ejb/PreDestroy.javabackmerge1.1.6.5modifiedbillejb3x/src/main/javax/ejb/PrePassivate.javabackmerge1.2.4.6modifiedbillejb3x/src/main/javax/ejb/Remote.javabackmerge1.1.2.3modifiedbillejb3x/src/main/javax/ejb/RemoteHome.javabackmerge1.4.4.5modifiedbillejb3x/src/main/javax/ejb/Remove.javabackmerge1.2.4.6modifiedbillejb3x/src/main/javax/ejb/Stateful.javabackmerge1.1.2.6modifiedbillejb3x/src/main/javax/ejb/Stateless.javabackmerge1.1.6.5modifiedbillejb3x/src/main/javax/ejb/Timeout.javabackmerge1.1.6.5modifiedbillejb3x/src/main/javax/ejb/TransactionAttribute.javabackmerge1.5.2.5modifiedbillejb3x/src/main/javax/ejb/TransactionAttributeType.javabackmerge1.3.4.6modifiedbillejb3x/src/main/javax/ejb/TransactionManagement.javabackmerge1.3.4.5modifiedbillejb3x/src/main/javax/ejb/TransactionManagementType.javabackmerge1.2.2.1modifiedbillspring-int/src/main/org/jboss/spring/callback/SpringCallbackListener.javabackmerge1.1.2.3modifiedbillserver/src/resources/schema/ejb-jar_3_0.xsdbackmerge1.1.2.3modifiedb
[JBoss-dev] jboss-cache-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060321170015 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-JBossCache.xml:86: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 03/21/2006 17:00:15Time to build: 43 minutes 0 secondsLast changed: 03/21/2006 13:14:35Last log entry: Added deadlock detection unit test and fixed deadlock problem in cache loader interceptor when concurrent node creation occurs Unit Tests: (1368) Total Errors and Failures: (1)unknownorg.jboss.cache.loader.deadlock.ConcurrentCreationDeadlockTest Modifications since last build: (first 50 of 3)1.2modifiedmsurtanitests/functional/org/jboss/cache/loader/DummyCacheLoader.javamore dummy meths1.26modifiedmsurtanisrc/org/jboss/cache/interceptors/CacheLoaderInterceptor.javaAdded deadlock detection unit test and fixed deadlock problem in cache loader interceptor when concurrent node creation occurs1.1addedmsurtanitests/functional/org/jboss/cache/loader/deadlock/ConcurrentCreationDeadlockTest.javaAdded deadlock detection unit test and fixed deadlock problem in cache loader interceptor when concurrent node creation occurs
Re: [JBoss-dev] 4.0.4
That sounds like a plan. Scott M Stark wrote: Just do a 4.0.5 soon after than. I don't want to push the 4.0.4.GA as Dimitris said people have been waiting on it for a while. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Monday, March 20, 2006 6:54 PM To: jboss-development@lists.sourceforge.net Subject: Re: [JBoss-dev] 4.0.4 It would be cool if we could push GA a bit further after CR2. I would like to do a big push for EJB3 final draft(and my book) compliance with 4.0.4 and need more than 2 weeks as I'm on vacation for 10 days in between. Scott M Stark wrote: Ok. We want the 4.0.4.CR2 out this week and the GA two weeks latter. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Ebersole Sent: Monday, March 20, 2006 2:17 PM To: jboss-development@lists.sourceforge.net Subject: RE: [JBoss-dev] 4.0.4 So provided we do not cause issues with portal, I say we go with a 3.2 final. Specific reasons: (1) Less issues with the version differences between AS and EJB3 (2) JBossCache optimistic locking support (only in 3.2) (3) Javassist support (only in 3.2) (4) Some performance enhancements relating to aggressive connection releasing on JBoss (although this is in 3.1.3 also). The only other real difference between 3.1.3 and 3.2 is the non-transactional stuff. The installer/build option seems a bit late in the game considering a release next week (#1). --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development -- Bill Burke Chief Architect JBoss Inc. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-cache-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache-testsuite?log=log20060321142300 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-JBossCache.xml:86: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 03/21/2006 14:23:00Time to build: 42 minutes 41 secondsLast changed: 03/21/2006 13:14:35Last log entry: Added deadlock detection unit test and fixed deadlock problem in cache loader interceptor when concurrent node creation occurs Unit Tests: (1368) Total Errors and Failures: (1)unknownorg.jboss.cache.loader.deadlock.ConcurrentCreationDeadlockTest Modifications since last build: (first 50 of 2)1.2modifiedmsurtanitests/functional/org/jboss/cache/loader/DummyCacheLoader.javamore dummy meths1.26modifiedmsurtanisrc/org/jboss/cache/interceptors/CacheLoaderInterceptor.javaAdded deadlock detection unit test and fixed deadlock problem in cache loader interceptor when concurrent node creation occurs
[JBoss-dev] Code review
I'm sure others weren't aware of this behaviour, so you might want to check your code: http://jira.jboss.com/jira/browse/JBAS-2973 -- Adrian Brock Chief Scientist JBoss Inc. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0-testsuite Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log2006032121 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:235: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:26: Build Successful - Tests completed with errors or failures.Date of build: 03/21/2006 11:11:21Time to build: 99 minutes 27 secondsLast changed: 03/21/2006 08:02:41Last log entry: [JBAS-2941] - Expose subscriber statistics for queues Unit Tests: (2990) Total Errors and Failures: (24)testENCServletViaInvokerorg.jboss.test.jacc.test.WebIntegrationUnitTestCase(JACC+SecurityMgr)testSingleEventDurationorg.jboss.test.txtimer.test.EntityBeanTestCasetestInstanceAsscociationorg.jboss.test.txtimer.test.EntityBeanTestCasetestEjbTimeoutCallerPrincipalorg.jboss.test.txtimer.test.EntityBeanTestCasetestReturnTimerHandleorg.jboss.test.txtimer.test.EntityBeanTestCasetestRollbackAfterCreateorg.jboss.test.txtimer.test.EntityBeanTestCasetestRollbackAfterCancelorg.jboss.test.txtimer.test.EntityBeanTestCasetestRetryAfterRollbackorg.jboss.test.txtimer.test.EntityBeanTestCasetestTimerRestoredForSessionBeanorg.jboss.test.txtimer.test.PersistentTimerTestCasetestNoneorg.jboss.test.webservice.jbws165.JBWS165TestCasetestWeatherByPlaceNameorg.jboss.test.webservice.jbws381.JBWS381TestCasetestStringArrayorg.jboss.test.webservice.jbws632.JBWS632TestCasetestSendMessageorg.jboss.test.webservice.jbws663.JBWS663BareUnboundTestCasetestEndpointorg.jboss.test.webservice.jbws718.JBWS718TestCasetestLangEmptyAnyorg.jboss.test.webservice.jbws720.JBWS720TestCasetestEmptyLangEmptyAnyorg.jboss.test.webservice.jbws720.JBWS720TestCasetestSOAPMessageToEndpointQueueorg.jboss.test.webservice.samples.ServerSideJMSTestCasetestWithTransportOptionsorg.jboss.test.webservice.secure.SimpleClientSecureTestCasetestWithTransportOptionsorg.jboss.test.webservice.secure.noenv.TransportOptionsTestCasetestWithoutKeystoreorg.jboss.test.webservice.secure.noenv.TransportOptionsTestCasetestEJBClientorg.jboss.test.webservice.ws4eesimple.SimpleClientTestCasetestHelloorg.jboss.test.webservice.wsdlimport.AbsoluteImportTestCasetestAutoDiscoveryorg.jboss.test.cluster.test.HAJndiTestCase(Default-UDP)testAutoDiscoveryorg.jboss.test.cluster.test.HAJndiTestCase(SyncModeNUseJvm-UDP) Modifications since last build: (first 50 of 1897)1.1.2.4modifiedstarksmtestsuite/src/resources/test-configs/jacc/conf/login-config.xmlAdd a legacy client-login that clears the security association stack on logout1.2.6.2modifiedstarksmtestsuite/src/main/org/jboss/test/cmp2/audit/interfaces/ApplicationCallbackHandler.javaAdd a login method that takes the configuration name1.6.2.33modifiedstarksmtestsuite/imports/server-config.xmlUpdate the create-config/newconf-src attribute description1.2.6.2modifiedstarksmtestsuite/src/main/org/jboss/test/cmp2/audit/beans/AuditSessionBean.javaJBAS-2947, add an updateAuditMappedCheck that uses the old client-login config that clears the security association on logout1.2.6.2modifiedstarksmtestsuite/src/main/org/jboss/test/cmp2/audit/test/AuditUnitTestCase.javaJBAS-2947, add an updateAuditMappedCheck that uses the old client-login config that clears the security association on logout1.406.2.152modifiedstarksmtestsuite/build.xmlJBAS-2947, Use newconf-src="" for the tests-jacc-securitymgr target1.78.2.7modifiedstarksmserver/src/main/org/jboss/ejb/EnterpriseContext.javaJBAS-2947, Clear the bean principal used for getCallerPrincipal and synch with the new call principal in setPrincipal to ensure the getCallerPrincipal is valid for the duration of the call1.78.2.8modifiedstarksmserver/src/main/org/jboss/ejb/EnterpriseContext.javaRemove the System.out debug calls1.78.2.9modifiedstarksmserver/src/main/org/jboss/ejb/EnterpriseContext.javaJBAS-2947, Only set the bean principal via getCallerPrincipal if there is a security domain1.2.2.21modifiedbstansberrytomcat/src/resources/tc5-cluster-service.xml[JBAS-2966] Use optimized UDP config1.1.2.3modifiedbillserver/src/resources/schema/jboss_5_0.xsdno message1.1.4.6modifiedbstansberrytestsuite/src/resources/test-configs/tomcat-sso-cluster/deploy/tc5-cluster-service.xml[JBAS-2966] Use optimized UDP config1.4.6.6modifiedstarksmtestsuite/src/main/org/jboss/test/naming/test/SimpleUnitTestCase.javaJBAS-2744, Use the getServerHost() as the jnp.localAddress value1.3.4.6modifiedbillejb3x/src/main/javax/ejb/ActivationConfigProperty.javabackmerge1.1.2.5modifiedbillejb3x/src/main/javax/ejb/ApplicationException.javabackmerge1.1.6.5modifiedbillejb3x/src/main/javax/ejb/AroundInvoke.javabackmerge1.1.2.6modifiedbillejb3x/src/main/javax/ejb/EJBAccessException.javabackmerge1.1.2.6modifiedbillejb3x/src/main/javax/ejb/EJBNoSuchObjectException.javabackmerge1.1.2.6modifiedbillejb3x/src/main/javax/ejb/EJBTransactionRequiredExcept
[JBoss-dev] FW: Viewer for JMX/MBeans
Yes, viewer for JMXConsole would be a nice feature to be added IMO...
For example, a method returning an array of objects could have a viewer
formatting the result properly.
On JbossProfiler I have a method called Class[] getLoadedClasses() on
JVMTIInterface
If I had a way to add a viewer metadata on xmdesc I would be able to
create a nice tool only using JMX-Console.
Clebert
-Original Message-
From: Scott M Stark
Sent: Tuesday, March 21, 2006 11:44 AM
To: Clebert Suconic
Subject: RE: Viewer for JMX/MBeans WAS: [JBoss JIRA] Created:
(JBAS-2972) Find cause of current testsuite OOMEs
We don't have such a notion currently. The way it should be done for the
jmx-console is via an mbean descriptor with a special name ("viewer")
for example as descriptors are the only way to add metadata to an mbean.
> -Original Message-
> From: Clebert Suconic
> Sent: Tuesday, March 21, 2006 9:41 AM
> To: Scott M Stark
> Subject: Viewer for JMX/MBeans WAS: [JBoss JIRA] Created:
> (JBAS-2972) Find cause of current testsuite OOMEs
>
> Hey Scott...
>
> Quick question..
>
> I have a method within JVMTIInterface,
> Class[] getAllClasses()
>
>
>
> Do you know if it's possible to associate a method return
> with some sort of special viewer on the JMXConsole.
>
>
> If you have such feature available, it would be a cool thing.
> I would be able to create a nice ClassLeak tool using only
> JMX-Console (since I have a method getReferenceHolders now,
> it would be possible even to find who is holding the reference)
>
>
> Doing like:
>
> setMethod="setHANamingService">
> The HANamingService service name
> HANamingService
> java.lang.String
> org.jboss.profiler.ResultViewer
>
>
>
>
>
>
> For now I'm asking this as a simple question, because I
> though we have such feature. If we don't, I will feed this in
> some forum.
>
>
>
> Clebert
>
>
> -Original Message-
> From: Scott M Stark (JIRA) [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 21, 2006 11:07 AM
> To: Clebert Suconic
> Subject: [JBoss JIRA] Created: (JBAS-2972) Find cause of
> current testsuite OOMEs
>
> Find cause of current testsuite OOMEs
> -
>
> Key: JBAS-2972
> URL: http://jira.jboss.com/jira/browse/JBAS-2972
> Project: JBoss Application Server
> Type: Task
> Environment:
> http://cruisecontrol.jboss.com:80/cc/artifacts/jboss-4.0-tests
uite/20060320121502/results/index.html
> Reporter: Scott M Stark
> Assigned to: Clebert Suconic
> Priority: Critical
> Fix For: JBossAS-4.0.4.CR2
>
>
> Looking at the the txtimer errors, these are due to previous
> deployments not getting cleaned up due to OOMEs:
>
> 2006-03-20 13:20:21,455 WARN
> [org.jboss.system.ServiceController] Problem start
> ing service jboss.j2ee:jndiName=test/txtimer/TimerTest,service=EJB
> java.lang.OutOfMemoryError
> ...
> 2006-03-20 13:20:25,895 INFO
> [org.jboss.ejb.plugins.StatelessSessionInstancePool]
> Registration is not done -> stop
> 2006-03-20 13:20:25,896 DEBUG
> [org.jboss.ejb.StatelessSessionContainer] Failed to register
> pool as mbean
> javax.management.InstanceAlreadyExistsException:
> jboss.j2ee:jndiName=test/txtimer/TimerTest,plugin=pool,service
> =EJB already registered.
>at
> org.jboss.mx.server.registry.BasicMBeanRegistry.add(BasicMBean
> Registry.java:757)
>at
> org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(
> BasicMBeanRegistry.java:225)
>at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
>at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
> odAccessorImpl.java:25)
>at java.lang.reflect.Method.invoke(Method.java:324)
>at
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedD
> ispatcher.java:155)
>at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
>at
> org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIn
> terceptor.java:133)
>
> We need to find out why there OOMEs.
>
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the
> administrators:
>http://jira.jboss.com/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see:
>http://www.atlassian.com/software/jira
>
>
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] RE: jboss-4.0-testsuite Build Completed With Testsuite Errors
The txtimer errors are due to previous deployments not getting cleaned up due to OOMEs: 2006-03-20 13:20:21,455 WARN [org.jboss.system.ServiceController] Problem start ing service jboss.j2ee:jndiName=test/txtimer/TimerTest,service=EJB java.lang.OutOfMemoryError ... 2006-03-20 13:20:25,895 INFO [org.jboss.ejb.plugins.StatelessSessionInstancePool] Registration is not done -> stop 2006-03-20 13:20:25,896 DEBUG [org.jboss.ejb.StatelessSessionContainer] Failed to register pool as mbean javax.management.InstanceAlreadyExistsException: jboss.j2ee:jndiName=test/txtimer/TimerTest,plugin=pool,service=EJB already registered. at org.jboss.mx.server.registry.BasicMBeanRegistry.add(BasicMBeanRegistry.j ava:757) at org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMBean Registry.java:225) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher. java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor. java:133) http://jira.jboss.com/jira/browse/JBAS-2972 --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-seam-testsuite Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-seam-testsuite?log=log20060321092133 BUILD FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-seam-testsuite.xml:54: /services/cruisecontrol/work/scripts/test-output not found.Date of build: 03/21/2006 09:21:33Time to build: 1 minute 48 secondsLast changed: 03/20/2006 08:29:38Last log entry: added blog example Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (first 50 of 190)1.1addedsbryzak2src/main/org/jboss/seam/remoting/BaseRequestHandler.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.3modifiedsbryzak2src/main/org/jboss/seam/remoting/Call.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.2modifiedsbryzak2src/main/org/jboss/seam/remoting/CallContext.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.3modifiedsbryzak2src/main/org/jboss/seam/remoting/ExecutionHandler.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.4modifiedsbryzak2src/main/org/jboss/seam/remoting/InterfaceGenerator.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.1addedsbryzak2src/main/org/jboss/seam/remoting/PollHandler.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.1addedsbryzak2src/main/org/jboss/seam/remoting/RequestContext.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.1addedsbryzak2src/main/org/jboss/seam/remoting/RequestHandler.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.1addedsbryzak2src/main/org/jboss/seam/remoting/RequestHandlerFactory.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.4modifiedsbryzak2src/main/org/jboss/seam/remoting/SeamRemotingServlet.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.1addedsbryzak2src/main/org/jboss/seam/remoting/SubscriptionHandler.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.2modifiedsbryzak2src/main/org/jboss/seam/remoting/remote.jsRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.1addedsbryzak2src/main/org/jboss/seam/remoting/messaging/PollRequest.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.1addedsbryzak2src/main/org/jboss/seam/remoting/messaging/RemoteSubscriber.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.1addedsbryzak2src/main/org/jboss/seam/remoting/messaging/SubscriptionRegistry.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial version of support for JMS topic subscriptions1.1addedsbryzak2src/main/org/jboss/seam/remoting/messaging/SubscriptionRequest.javaRefactored SeamRemotingServlet, fixed couple of bugs in remote.js, implemented conversation reinstatement, moved call-based context to request level, initial v
[JBoss-dev] microcontainer-head-testsuite build.90 Build Fixed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/microcontainer-head-testsuite?log=log20060321084310Lbuild.90 BUILD COMPLETE - build.90Date of build: 03/21/2006 08:43:10Time to build: 37 minutes 10 secondsLast changed: 03/20/2006 10:56:43Last log entry: [JBMICROCONT-14] When reinstalling an aspect with a dependency, make sure that the aspectdefinition and binding wrappers get updated Unit Tests: (573) Total Errors and Failures: (0)All Tests Passed Modifications since last build: (first 50 of 29)1.12modifiedkkhansrc/main/org/jboss/kernel/plugins/dependency/AbstractKernelControllerContext.javaSome support for mc/aop dependenciesMake prototype Aspect implement Untransformable, since we always need setKernelControllerContext() to be called to initialise the name of the aspect definitionMake sure that when undeploying an advicebinding and the advisor belongs to a sub domain, that we check if it registered with the parent aspect managerWhen setting metadata via the KernelControllerContext, create a per instance bean info with a per instance class adapter1.23modifiedkkhansrc/main/org/jboss/kernel/plugins/dependency/KernelControllerContextActions.javaSome support for mc/aop dependenciesMake prototype Aspect implement Untransformable, since we always need setKernelControllerContext() to be called to initialise the name of the aspect definitionMake sure that when undeploying an advicebinding and the advisor belongs to a sub domain, that we check if it registered with the parent aspect managerWhen setting metadata via the KernelControllerContext, create a per instance bean info with a per instance class adapter1.8modifiedkkhansrc/main/org/jboss/beans/info/plugins/AbstractBeanInfo.javaSome support for mc/aop dependenciesMake prototype Aspect implement Untransformable, since we always need setKernelControllerContext() to be called to initialise the name of the aspect definitionMake sure that when undeploying an advicebinding and the advisor belongs to a sub domain, that we check if it registered with the parent aspect managerWhen setting metadata via the KernelControllerContext, create a per instance bean info with a per instance class adapter1.1addedkkhansrc/main/org/jboss/beans/info/plugins/AbstractInstanceBeanInfo.javaSome support for mc/aop dependenciesMake prototype Aspect implement Untransformable, since we always need setKernelControllerContext() to be called to initialise the name of the aspect definitionMake sure that when undeploying an advicebinding and the advisor belongs to a sub domain, that we check if it registered with the parent aspect managerWhen setting metadata via the KernelControllerContext, create a per instance bean info with a per instance class adapter1.7modifiedkkhansrc/main/org/jboss/beans/info/spi/BeanInfo.javaSome support for mc/aop dependenciesMake prototype Aspect implement Untransformable, since we always need setKernelControllerContext() to be called to initialise the name of the aspect definitionMake sure that when undeploying an advicebinding and the advisor belongs to a sub domain, that we check if it registered with the parent aspect managerWhen setting metadata via the KernelControllerContext, create a per instance bean info with a per instance class adapter1.4modifiedkkhansrc/main/org/jboss/classadapter/plugins/BasicClassAdapter.javaSome support for mc/aop dependenciesMake prototype Aspect implement Untransformable, since we always need setKernelControllerContext() to be called to initialise the name of the aspect definitionMake sure that when undeploying an advicebinding and the advisor belongs to a sub domain, that we check if it registered with the parent aspect managerWhen setting metadata via the KernelControllerContext, create a per instance bean info with a per instance class adapter1.13modifiedkkhansrc/main/org/jboss/classadapter/spi/ClassAdapter.javaSome support for mc/aop dependenciesMake prototype Aspect implement Untransformable, since we always need setKernelControllerContext() to be called to initialise the name of the aspect definitionMake sure that when undeploying an advicebinding and the advisor belongs to a sub domain, that we check if it registered with the parent aspect managerWhen setting metadata via the KernelControllerContext, create a per instance bean info with a per instance class adapter1.5modifiedkkhansrc/main/org/jboss/repository/spi/MetaDataContext.javaSome support for mc/aop dependenciesMake prototype Aspect implement Untransformable, since we always need setKernelControllerContext() to be called to initialise the name of the aspect definitionMake sure that when undeploying an advicebinding and the advisor belongs to a sub domain, that we check if it registered with the parent aspect managerWhen setting metadata via the KernelControllerCont
[JBoss-dev] jboss-remoting-testsuite-1.4 Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.4?log=log20060321081706 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 03/21/2006 08:17:06Time to build: 19 minutes 24 secondsLast changed: 03/21/2006 03:07:10Last log entry: JBREM-338: Force SocketId.getFreePort() to wrap from Integer.MAX_VALUE to 1.Put in wrapping. Also, made a request for a new SocketId wait() if all numbers are in use, and made returnPort() call notifyAll(). Unit Tests: (176) Total Errors and Failures: (20)testServerStartsServer3Client1ClientClosesorg.jboss.test.remoting.transport.multiplex.InvokerGroupTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization) Modifications since last build: (first 50 of 95)1.1addedtelrodsrc/tests/org/jboss/test/remoting/transport/http/timeout/TimeoutClientTest.javaJBREM-329 - added global timeout config property for all transports (client and server).1.1addedtelrodsrc/tests/org/jboss/test/remoting/transport/http/timeout/TimeoutServerTest.javaJBREM-329 - added global timeout config property for all transports (client and server).1.1addedtelrodsrc/tests/org/jboss/test/remoting/transport/http/timeout/TimeoutTestCase.javaJBREM-329 - added global timeout config property for all transports (client and server).1.1addedtelrodsrc/tests/org/jboss/test/remoting/transport/multiplex/timeout/TimeoutClientTest.javaJBREM-329 - added global timeout config property for all transports (client and server).1.1addedtelrodsrc/tests/org/jboss/test/remoting/transport/multiplex/timeout/TimeoutServerTest.javaJBREM-329 - added global timeout config property for all transports (client and server).1.1addedtelrodsrc/tests/org/jboss/test/remoting/transport/multiplex/timeout/TimeoutTestCase.javaJBREM-329 - added global timeout config property for all transports (client and server).1.5modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/multiplex/MultiplexInvokerConfigTestClient.javaJBREM-329 - added global timeout config property for all transports (client and server).1.16modifiedtelrodsrc/tests/org/jboss/test/remoting/transport/multiplex/MultiplexInvokerTestClient.javaJBREM-329 - added global timeout config property for all transports (client and server).1.1addedtelrodsrc/tests/org/jboss/test/remoting/transport/rmi/timeout/TimeoutClientTest.javaJBREM-329 - added global timeout config property for all transports (client and server).1.1addedtelrodsrc/tests/org/jboss/test/remoting/transport/rmi/timeout/TimeoutServerTest.javaJBREM-329 - added global timeout config property for all transports (client and server).1.1addedtelrodsrc/tests/org/jboss/test/remoting/transport/rmi/timeout/TimeoutTestCase.javaJBREM-329 - added global timeout config property for all transports (client and server).1.4modifiedtelrodsrc/tests/org/jboss/test/remoting/
[JBoss-dev] jboss-remoting-testsuite-1.5 Build Completed With Testsuite Errors
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-remoting-testsuite-1.5?log=log20060321065101 TESTS FAILEDAnt Error Message: /services/cruisecontrol/work/scripts/build-jboss-remoting.xml:96: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-common-targets.xml:11: Build Successful - Tests completed with errors or failures.Date of build: 03/21/2006 06:51:01Time to build: 76 minutes 24 secondsLast changed: 12/31/2005 20:37:24Last log entry: JBREM-272:Added tests for (clientPool != null) and (threadPool != null) in cleanup. Unit Tests: (355) Total Errors and Failures: (40)testStartorg.jboss.test.remoting.callback.pull.memory.callbackstore.CallbackStoreCallbackTestCase(java_serialization)testStartorg.jboss.test.remoting.callback.pull.memory.callbackstore.CallbackStoreCallbackTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerConfigTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(java_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(jboss_serialization)unknownorg.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase(jboss_serialization) Modifications since last build: (first 50 of 2224)1.3modifiedtelrodsrc/tests/org/jboss/test/remoting/transporter/TestClient.javaJBREM-276 - changed transporter client to throw original exception from the server implementation instead of wrapping it.1.3modifie
[JBoss-dev] Re: [jboss-cvs] jbosstest ...
There is a perfectly good way to make this configurable
locally without swamping the rest of us with garbage on the console
from crappily written tests.
There is no need for this anyway.
If you write your tests properly using logging,
the output goes to output/log/test.log
And the System.out/err is caught in the xml reports
for each test.
I will revert (AGAIN!).
On Tue, 2006-03-21 at 07:31 -0500, Thomas Diesler wrote:
> User: tdiesler
> Date: 06/03/21 07:31:43
>
> Modified:jbosstest build.xml
> Log:
> force showoutput=true for target one-test
>
> Revision ChangesPath
> 1.545 +2 -2 jbosstest/build.xml
>
> (In the diff below, changes in quantity of whitespace are not shown.)
>
> Index: build.xml
> ===
> RCS file: /cvsroot/jboss/jbosstest/build.xml,v
> retrieving revision 1.544
> retrieving revision 1.545
> diff -u -b -r1.544 -r1.545
> --- build.xml 20 Mar 2006 07:49:32 - 1.544
> +++ build.xml 21 Mar 2006 12:31:43 - 1.545
> @@ -10,7 +10,7 @@
>
>
>
> -
> +
>
> xmlns:server="http://jboss.org/ns/test/ant/server";>
> @@ -2982,7 +2982,7 @@
> haltonfailure="${junit.haltonfailure}"
> fork="${junit.fork}"
> timeout="${junit.timeout}"
> -showoutput="${junit.showoutput}"
> +showoutput="true"
> jvm="${junit.jvm}">
>
>
>
>
>
>
>
> ---
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> ___
> jboss-cvs-commits mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-cvs-commits
--
Adrian Brock
Chief Scientist
JBoss Inc.
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
