Re: [JBoss-dev] anonymous CVS is dead
Hi, The snapshots do not appear to contain the new JMS code. Is there a separate snapshot for this? Thanks, On Thu, 2003-07-10 at 01:07, Scott M Stark wrote: Daily snapshots are available from here: http://jboss.sourceforge.net/snapshots/ -- Michael Barker [EMAIL PROTECTED] --- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing more. Download eval WebKing and get a free book. www.parasoft.com/bulletproofapps ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Antwort: RE: c/s JBossMQ status, was: [JBoss-dev] JBossMQ rewrite
The current JMS rewrite by Nathan, Adrian, and Bela is going quite well and we will be replacing the old system in the fall. Don't work on a codebase that is going to be retired and needs to live in depracated mode for awhile. A refactoring isn't what is needed in the JMS subsystem. I don't want to be pessimistic, but it took quite a long time to stabilize the current JBossMQ. This is especially true for heavy load scenarios. The ongoing JMS rewrite hopefully will bring significant improvements, but first of all it has to proof stability and spec compliance before it is a valid alternative for production usage. Many JMS users will have to / want to stay with JBossMQ for quite a longer than maybe expected ! Therefore ongoing improvements of the existing JBossMQ code have quite a value ( atleast for me as a JMS user, who requires a stable and matured JMS plattform :-) Regards Ulf
[JBoss-dev] [ jboss-Feature Requests-769045 ] XMBeanAware Interface
Feature Requests item #769045, was opened at 2003-07-10 13:09
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376688aid=769045group_id=22866
Category: JBossMX
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Eric Jain (ejain)
Assigned to: Nobody/Anonymous (nobody)
Summary: XMBeanAware Interface
Initial Comment:
Have the XMBean implementation pass a reference to
itself to managed resources that implement the
following interface:
interface XMBeanAware
{
void setXMBean(XMBean xmbean);
}
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376688aid=769045group_id=22866
---
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing more.
Download eval WebKing and get a free book.
www.parasoft.com/bulletproofapps
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] multiple deployment info entries for invoker.war
I noticed that removeDeployer does a first-to-last traversal of deploymentList. I wondered if that was an oversight or part of some strategy that wasn't obvious to me. But, it gets uglier. Commenting MainDeployer.shutdown() produces a batch of warnings from ServiceController.shutdown(), it complains about ignoring a request to stop/destroy/remove nonexistent services. Here's the scenario, as I understand it. startup: - xxx.jar is detected and deployed - service (EjbModule) is created to represent xxx.jar, - jboss.j2ee:service=EjbModule,url=...xxx.jar - xxx.jar contains ejb ABC - EjbModule.createService() creates a container for ABC - EjbModule.createService() creates a service to represent ABC bean container - jboss.j2ee:jndiName=ABC,service=EJB shutdown: - service controller shutdown finds ABC container service and stops/destroys/removes it - since containerServiceContext.dependsOnMe is empty, svc controller removes this context from nameToServiceMap - service controller shutdown finds xxx.jar service and tries to stop it - EjbModule.stopService() tries to stop the ABC container service, again - when svc controller.stop can't find the container context in nameToServiceMap, it whines about a nonexistent service - service controller shutdown tries to destroy xxx.jar service - EjbModule.stopService() tries to destroy the ABC container service, again - when svc controller.destroy still can't find the container context, it whines, again - service controller shutdown tries to remove xxx.jar service - EjbModule.stopService() tries to remove the ABC container service, again - when svc controller.remove still can't find the container context, it whines, again I'm guessing that this issue is masked by MainDeployer.shutdown's undeployment of everything. Since the containers aren't deployed, they aren't explicitly handled by MainDeployer.shutdown. Their jar file is undeployed and takes them along. It will probably show up in a scenario where a container is stopped, then it's jar service is stopped. It looks like declaring the xxx.jar to depend on the containers it creates would prevent the containers from being removed from nameToServiceMap. Though I don't see how - yet - to do that without either exposing ServiceContext in the controller mbean, or changing the bean deployment sequence so that the jars containers are known when its service is created. Reversing the order of service controller shutdown would solve this, but cause other problems. Changing the whine message level (WARN-INFO) would make the message less worrisome, but that addresses the symptom, not the problem. Putting the MainDeployer.shutdown() back with a removeDeployer loop will get rid of all the warnings, but breaks the service life cycle symmetry. Is there a good solution? Or only the lesser of evils? What am I missing? Rod Burgett Senior Software Engineer webMethods, Inc. 3930 Pender Drive Fairfax, VA 22030 USA Ph: 703.460.5819 (tty only) It's all just 0s 1s - the trick is getting them lined up in the proper order -Original Message- From: Scott M Stark [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 08, 2003 1:54 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] multiple deployment info entries for invoker.war Theoretically, but a problem with not using the MainDeployer.shutdown is that the deployment shutdown order will change since the MainDeployer.removeDeployer method is not iterating over the deploymentList in reverse order as is the case for MainDeployer.shutdown. If this is corrected then the shutdown method and the ServerImpl*.shutdownDeployments method seem uneccessary and the MainDeployer.shutdown could call the ServiceController.shutdown. -- Scott Stark Chief Technology Officer JBoss Group, LLC Rod Burgett wrote: I see what you are saying about breaking the mirror, the removal of deployers should be controlled by the deployer services. Code already exists in ServerImpl.ShutdownHook.shutdown() to invoke ServiceController.shutdown(), which walks backwards through it's service list to stop, destroy and remove each. From what you say, this could handle undeploying everything. Currently, nothing actually gets undeployed at that point because MainDeployer.shutdown() gets called, and undeploys everything, before ServiceController.shutdown() is called. So, if service shutdown effectively handles undeployment, and preserves the mirror, is there really a need for MainDeployer to undeploy anything at shutdown? Can MainDeployer do all its housekeeping in destroyService()? Then what's left for shutdown() do? Except maybe ask the service controller to stop the deployer services? Rod Burgett Senior Software Engineer webMethods, Inc. 3930 Pender Drive Fairfax, VA 22030 USA Ph: 703.460.5819 (tty only) It's all just 0s 1s -
[JBoss-dev] [ jboss-Bugs-769139 ] entityCtx.getEJBLocalObject() returns wrong instance
Bugs item #769139, was opened at 2003-07-10 17:03 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=769139group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Alexei Yudichev (sflexus) Assigned to: Nobody/Anonymous (nobody) Summary: entityCtx.getEJBLocalObject() returns wrong instance Initial Comment: I am using Jboss 3.2.1 Sometimes entityContext.getEJBLocalObject() returns local interface of another instance of the same entity bean. I have a superclass for all my entities in application which implements EntityBean's setEntityContext() method and saves entityContext in a field. Inside one of business methods of one of entity beans I check if a primary key constructed from key CMP field(s) matches a primary key obtained from entityContext. getEJBLocalObject().getPrimaryKey(). Sometimes they do not match: entityContext.getEJBLocalObject(). getPrimaryKey() returns primary key of another instance of the same entity bean. I have sometimes situations when user is logged in as one customer and enjoys privileges of another... This happens ~20 times a day with a particular single object for me... I could install some kind of bug trap logging some debug info to help fix the bug. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=769139group_id=22866 --- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing more. Download eval WebKing and get a free book. www.parasoft.com/bulletproofapps ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] ClassCastException from ProxyCompiler$Proxy35.getId(generated)
I was getting these last night on 3.2.1 using JSPs. In my case, I redeployed my EJBs and JSPs and the ClassCastException went away. Hope this helps... Nate -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, July 10, 2003 9:28 AM To: [EMAIL PROTECTED] Subject: [JBoss-dev] ClassCastException from ProxyCompiler$Proxy35.getId(generated) jboss-head from ~ July 1. RedHat 8 JDK 1.4.1 Mysql I have a simple bean that has auto-generated Integer primary keys. MyLocal myLocal = myLocalHome.create(name, description); myLocal.getName(); -- works fine myLocal.getDescription(); -- works fine myLocal.getId(); -- Throws ClassCastException in the proxy. Bean gets created fine. Primary key comes back fine from the SQL insert (verified in log file from debug from JDBCGetGeneratedKeysCreateCommand). But, for some reason, when I call getId() it throws a ClassCastException. Calling getName() and getDescription() work fine. What's wierd, is that I can do a myLocalHome.findAll(), iterate through the returned collection and call getId() on those just fine. It just seems to be when I call getId() on the returned local ejb... Any clues? Thanks, Michael This is being done from a Servlet... --- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing more. Download eval WebKing and get a free book. www.parasoft.com/bulletproofapps ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing more. Download eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] ClassCastException from ProxyCompiler$Proxy35.getId(generated)
Hello Michael, at the moment, I can't comment on why findAll works. The cause, perhapsm is the types mismatch between the one that is used by MySQL driver for generated keys be default and the one you use for primary key column. AFAIK, MySQL's default is java.lang.Integer. Abstracting from vendor-specific types supported in current Branch_3_2. It is not yet ported to HEAD. alex Thursday, July 10, 2003, 6:27:31 PM, MNewcomb MNewcomb wrote: Mtc jboss-head from ~ July 1. Mtc RedHat 8 Mtc JDK 1.4.1 Mtc Mysql Mtc I have a simple bean that has auto-generated Integer primary keys. Mtc MyLocal myLocal = myLocalHome.create(name, description); Mtc myLocal.getName(); -- works fine Mtc myLocal.getDescription(); -- works fine Mtc myLocal.getId(); -- Throws ClassCastException in the proxy. Mtc Bean gets created fine. Primary key comes back fine from the SQL insert Mtc (verified in log file from debug from JDBCGetGeneratedKeysCreateCommand). Mtc But, for some reason, when I call getId() it throws a ClassCastException. Mtc Calling getName() and getDescription() work fine. Mtc What's wierd, is that I can do a myLocalHome.findAll(), iterate through the Mtc returned collection and call getId() on those just fine. Mtc It just seems to be when I call getId() on the returned local ejb... Mtc Any clues? Mtc Thanks, Mtc Michael Mtc This is being done from a Servlet... --- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing more. Download eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] anonymous CVS is dead
Sacha said yesterdays snapshot was truncated. Todays definitely has it: http://jboss.sourceforge.net/snapshots/jboss-head-snapshot.tar.gz -- Scott Stark Chief Technology Officer JBoss Group, LLC Michael Barker wrote: Hi, The snapshots do not appear to contain the new JMS code. Is there a separate snapshot for this? Thanks, --- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing more. Download eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] ClassCastException from ProxyCompiler$Proxy35.getId(generated)
From: Alexey Loubyansky [mailto:[EMAIL PROTECTED] Hello Michael, at the moment, I can't comment on why findAll works. The cause, perhapsm is the types mismatch between the one that is used by MySQL driver for generated keys be default and the one you use for primary key column. AFAIK, MySQL's default is java.lang.Integer. Abstracting from vendor-specific types supported in current Branch_3_2. It is not yet ported to HEAD. You got it. MySQL is returning a Long for their generated keys. In Statement they use Types.BIGINT. Meanwhile, we are mapping to Integer correctly in the normal load process, so, that explains why everything else works. So, what do we do about it? Should JDBCGetGeneratedKeysCreateCommand test for Number and convert to expected type? Or should we urge MySQL to create the type based upon the type of field it is? Thanks, Michael --- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing more. Download eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] ClassCastException from ProxyCompiler$Proxy35.getId(generated)
-Original Message- From: Newcomb, Michael P. So, what do we do about it? Should JDBCGetGeneratedKeysCreateCommand test for Number and convert to expected type? Or should we urge MySQL to create the type based upon the type of field it is? Actually, JDBCGetGeneratedKeysCreateCommand just calls getObject() on the result set. We probably need to run it through whatever code the normal loading process goes through so it will call ResultSet.getInt/Short/Long() based upon the metadata? Michael --- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing more. Download eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss (HEAD/winxp) Test Job Failed to Complete Successfully
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === === [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 2.875 sec [junit] Running org.jboss.test.jca.test.ReentrantUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 5.641 sec [junit] Running org.jboss.test.jca.test.UserTxUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 5.125 sec [junit] Running org.jboss.test.jca.test.WrapperSQLUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 20.422 sec [junit] Running org.jboss.test.jca.test.XAExceptionUnitTestCase [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 14.5 sec [junit] Running org.jboss.test.jca.test.XAResourceUnitTestCase [junit] Tests run: 0, Failures: 0, Errors: 0, Time elapsed: 0.453 sec [junit] Running org.jboss.test.jca.test.XATxConnectionManagerUnitTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 2.391 sec [junit] Running org.jboss.test.jmsra.test.RaQueueUnitTestCase [junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: 1.656 sec [junit] TEST org.jboss.test.jmsra.test.RaQueueUnitTestCase FAILED [junit] Running org.jboss.test.jmsra.test.RaSyncRecUnitTestCase [junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: 33.188 sec [junit] TEST org.jboss.test.jmsra.test.RaSyncRecUnitTestCase FAILED [junit] Running org.jboss.test.jmsra.test.RaTopicUnitTestCase [junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: 3.688 sec [junit] TEST org.jboss.test.jmsra.test.RaTopicUnitTestCase FAILED [junit] Running org.jboss.test.jmx.test.CPManifestUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 9.469 sec [junit] Running org.jboss.test.jmx.test.DeployConnectionManagerUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 5.141 sec [junit] TEST org.jboss.test.jmx.test.DeployConnectionManagerUnitTestCase FAILED [junit] Running org.jboss.test.jmx.test.DeployServiceUnitTestCase [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 6.375 sec [junit] Running org.jboss.test.jmx.test.DeployXMBeanUnitTestCase [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 2.687 sec [junit] Running org.jboss.test.jmx.test.EarDeploymentUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 5.656 sec [junit] Running org.jboss.test.jmx.test.EjbDependencyUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 12.359 sec [junit] Running org.jboss.test.jmx.test.JarInSarJSR77UnitTestCase [junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 4.422 sec [junit] TEST org.jboss.test.jmx.test.JarInSarJSR77UnitTestCase FAILED [junit] Running org.jboss.test.jmx.test.JavaBeanURIResolverUnitTestCase [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1.828 sec [junit] Running org.jboss.test.jmx.test.MBeanDependsOnConnectionManagerUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 2.516 sec [junit] Running org.jboss.test.jmx.test.MBeanDependsOnEJBUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 2.297 sec [junit] Running org.jboss.test.jmx.test.MissingClassUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 2.25 sec [junit] Running org.jboss.test.jmx.test.ServiceRsrcsUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 4.219 sec [junit] Running org.jboss.test.jmx.test.UndeployBrokenPackageUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 11 sec [junit] Running org.jboss.test.jmx.test.UnpackedDeploymentUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 20.141 sec [junit] Running org.jboss.test.jrmp.test.CustomSocketsUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 11.093 sec [junit] TEST org.jboss.test.jrmp.test.CustomSocketsUnitTestCase FAILED [junit] Running org.jboss.test.lock.test.SpinUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 23.421 sec [junit] Running org.jboss.test.mdb.test.MDBUnitTestCase [junit] Tests run: 0, Failures: 0, Errors: 2, Time elapsed: 20.406 sec [junit] TEST org.jboss.test.mdb.test.MDBUnitTestCase FAILED [junit] Running org.jboss.test.naming.test.EjbLinkUnitTestCase [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 14.718 sec [junit] Running org.jboss.test.naming.test.ENCUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 7.266 sec [junit] Running org.jboss.test.naming.test.ExternalContextUnitTestCase
[JBoss-dev] [AUTOMATED] JBoss (HEAD/winxp) Test Results: 96 % ( 786 / 817 ) - nearly there - who is gonna get us to 100%!
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 817 Successful tests: 786 Errors:25 Failures: 6 [time of test: 2003-07-11.00-04 GMT] [java.version: 1.4.1_03] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_03-b02] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Windows XP] [os.arch: x86] [os.version: 5.1] See http://jboss1.kimptoc.net/winxp/logtests/testresults/reports/html//. for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: RemotingUnitTestCase Test:testClusteredRemotingDT2(org.jboss.test.aop.test.RemotingUnitTestCase) Type:error Exception: org.jboss.tm.JBossRollbackException Message: Unable to commit, tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=2c571170edfbf9c6x73a7abxf64e841795x-7fff/101, BranchQual=2c571170edfbf9c6x73a7abxf64e841795x-7fff/] status=STATUS_ROLLEDBACK; - nested throwable: (java.lang.RuntimeException: Unexpected exception in commit of xid: XidImpl [FormatId=257, GlobalId=2c571170edfbf9c6x73a7abxf64e841795x-7fff/101, BranchQual=2c571170edfbf9c6x73a7abxf64e841795x-7fff/1], exception: java.lang.RuntimeException: Error processing InternalInvocation. Unable to process method commit) - Suite: TreeCacheAopUnitTestCase Test:testSet(org.jboss.test.cache.test.aop.TreeCacheAopUnitTestCase) Type:error Exception: java.lang.reflect.UndeclaredThrowableException Message: - Suite: TransientMBeanUnitTestCase Test:testPutTx(org.jboss.test.cache.test.tx.TransientMBeanUnitTestCase) Type:error Exception: java.rmi.ServerException Message: EJBException:; nested exception is: javax.ejb.EJBException: Application Error: tried to enter Stateful bean with different tx context, contextTx: TransactionImpl:XidImpl [FormatId=257, GlobalId=2c571170edfbf9c6x73a7abxf64e841795x-7fff/101, BranchQual=2c571170edfbf9c6x73a7abxf64e841795x-7fff/1], methodTx: null - Suite: TransientMBeanUnitTestCase Test:testRollbackTx(org.jboss.test.cache.test.tx.TransientMBeanUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: MBeanException: org.jboss.cache.LockingException: IdentityLock.attempt(); - nested throwable: (java.lang.InterruptedException) Cause: org.jboss.cache.LockingException: IdentityLock.attempt(); - nested throwable: (java.lang.InterruptedException) - Suite: BmpUnitTestCase Test:testUserTransaction(org.jboss.test.cts.test.BmpUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: - Suite: BmpUnitTestCase Test:testServerFound(org.jboss.test.cts.test.BmpUnitTestCase) Type:error Exception: java.rmi.ServerException Message: RuntimeException; nested exception is: java.lang.RuntimeException: Transaction marked for rollback, possibly a timeout - ===Fri Jul 11 01:53:20 GMTDT 2003 ===CYGWIN_NT-5.1 quarks2 1.3.22(0.78/3/2) 2003-03-18 09:20 i686 unknown unknown Cygwin ===java version 1.4.1_03 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_03-b02) Java HotSpot(TM) Client VM (build 1.4.1_03-b02, mixed mode) --- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing more. Download eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss (HEAD/linux1) Test Job Failed to Complete Successfully
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === === [junit] Running org.jboss.test.jca.test.DeploymentUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 5.942 sec [junit] Running org.jboss.test.jca.test.JCA15AdapterUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 8.797 sec [junit] Running org.jboss.test.jca.test.JDBCStatementTestsConnectionUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 13.142 sec [junit] Running org.jboss.test.jca.test.LocalWrapperCleanupUnitTestCase [junit] Tests run: 6, Failures: 0, Errors: 1, Time elapsed: 20.85 sec [junit] TEST org.jboss.test.jca.test.LocalWrapperCleanupUnitTestCase FAILED [junit] Running org.jboss.test.jca.test.MessageEndpointUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 7.03 sec [junit] Running org.jboss.test.jca.test.ReentrantUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 12.744 sec [junit] Running org.jboss.test.jca.test.UserTxUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 20.084 sec [junit] Running org.jboss.test.jca.test.WrapperSQLUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 4.755 sec [junit] Running org.jboss.test.jca.test.XAExceptionUnitTestCase [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 16.693 sec [junit] Running org.jboss.test.jca.test.XAResourceUnitTestCase [junit] Tests run: 0, Failures: 0, Errors: 0, Time elapsed: 0.767 sec [junit] Running org.jboss.test.jca.test.XATxConnectionManagerUnitTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 6.747 sec [junit] Running org.jboss.test.jmsra.test.RaQueueUnitTestCase [junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: 3.984 sec [junit] TEST org.jboss.test.jmsra.test.RaQueueUnitTestCase FAILED [junit] Running org.jboss.test.jmsra.test.RaSyncRecUnitTestCase [junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: 3.929 sec [junit] TEST org.jboss.test.jmsra.test.RaSyncRecUnitTestCase FAILED [junit] Running org.jboss.test.jmsra.test.RaTopicUnitTestCase [junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: 4.111 sec [junit] TEST org.jboss.test.jmsra.test.RaTopicUnitTestCase FAILED [junit] Running org.jboss.test.jmx.test.CPManifestUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 14.246 sec [junit] Running org.jboss.test.jmx.test.DeployConnectionManagerUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 16.074 sec [junit] TEST org.jboss.test.jmx.test.DeployConnectionManagerUnitTestCase FAILED [junit] Running org.jboss.test.jmx.test.DeployServiceUnitTestCase [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 13.717 sec [junit] Running org.jboss.test.jmx.test.DeployXMBeanUnitTestCase [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 6.774 sec [junit] Running org.jboss.test.jmx.test.EarDeploymentUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 19.86 sec [junit] Running org.jboss.test.jmx.test.EjbDependencyUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 9.364 sec [junit] Running org.jboss.test.jmx.test.JarInSarJSR77UnitTestCase [junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 6.109 sec [junit] TEST org.jboss.test.jmx.test.JarInSarJSR77UnitTestCase FAILED [junit] Running org.jboss.test.jmx.test.JavaBeanURIResolverUnitTestCase [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 5.169 sec [junit] Running org.jboss.test.jmx.test.MBeanDependsOnConnectionManagerUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 4.882 sec [junit] Running org.jboss.test.jmx.test.MBeanDependsOnEJBUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 10.097 sec [junit] Running org.jboss.test.jmx.test.MissingClassUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 5.036 sec [junit] Running org.jboss.test.jmx.test.ServiceRsrcsUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 5.775 sec [junit] Running org.jboss.test.jmx.test.UndeployBrokenPackageUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 23.065 sec [junit] Running org.jboss.test.jmx.test.UnpackedDeploymentUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 16.732 sec [junit] Running org.jboss.test.jrmp.test.CustomSocketsUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 11.677 sec [junit]
[JBoss-dev] [AUTOMATED] JBoss (HEAD/linux1) Test Results: 96 % ( 794 / 826 ) - nearly there - who is gonna get us to 100%!
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 826 Successful tests: 794 Errors:25 Failures: 7 [time of test: 2003-07-11.01-18 GMT] [java.version: 1.4.1_03] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_03-b02] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.20-18.7] See http://jboss1.kimptoc.net/linux1/logtests/testresults/reports/html//. for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: RemotingUnitTestCase Test:testClusteredRemotingDT2(org.jboss.test.aop.test.RemotingUnitTestCase) Type:error Exception: org.jboss.tm.JBossRollbackException Message: Unable to commit, tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=11d1def534ea1be0x123b25cxf64ebc8fedx-7fff/101, BranchQual=11d1def534ea1be0x123b25cxf64ebc8fedx-7fff/] status=STATUS_ROLLEDBACK; - nested throwable: (java.lang.RuntimeException: Unexpected exception in commit of xid: XidImpl [FormatId=257, GlobalId=11d1def534ea1be0x123b25cxf64ebc8fedx-7fff/101, BranchQual=11d1def534ea1be0x123b25cxf64ebc8fedx-7fff/1], exception: java.lang.RuntimeException: Error processing InternalInvocation. Unable to process method commit) - Suite: Scheduler2UnitTestCase Test:testXMLScheduleProvider(org.jboss.test.util.test.Scheduler2UnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: Not enough or too many (19) hits received: 10 - Suite: TreeCacheAopUnitTestCase Test:testSet(org.jboss.test.cache.test.aop.TreeCacheAopUnitTestCase) Type:error Exception: java.lang.reflect.UndeclaredThrowableException Message: - Suite: TransientMBeanUnitTestCase Test:testPutTx(org.jboss.test.cache.test.tx.TransientMBeanUnitTestCase) Type:error Exception: java.rmi.ServerException Message: EJBException:; nested exception is: javax.ejb.EJBException: Application Error: tried to enter Stateful bean with different tx context, contextTx: TransactionImpl:XidImpl [FormatId=257, GlobalId=11d1def534ea1be0x123b25cxf64ebc8fedx-7fff/101, BranchQual=11d1def534ea1be0x123b25cxf64ebc8fedx-7fff/1], methodTx: null - Suite: TransientMBeanUnitTestCase Test:testRollbackTx(org.jboss.test.cache.test.tx.TransientMBeanUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: MBeanException: org.jboss.cache.LockingException: IdentityLock.attempt(); - nested throwable: (java.lang.InterruptedException) Cause: org.jboss.cache.LockingException: IdentityLock.attempt(); - nested throwable: (java.lang.InterruptedException) - Suite: BmpUnitTestCase Test:testUserTransaction(org.jboss.test.cts.test.BmpUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: - ===Fri Jul 11 02:31:07 BST 2003 ===Linux nog 2.4.20-18.7 #1 Thu May 29 08:32:50 EDT 2003 i686 unknown ===java version 1.4.1_03 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_03-b02) Java HotSpot(TM) Client VM (build 1.4.1_03-b02, mixed mode) --- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing more. Download eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 10-July-2003
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 10-July-2003 JBoss daily test results SUMMARY Number of tests run: 1369 Successful tests: 1353 Errors:10 Failures: 6 [time of test: 2003-07-11.01-48 GMT] [java.version: 1.4.1_03] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_03-b02] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.20-18.9custom] Useful resources: - http://jboss.sourceforge.net//junit-results/32/2003-07-11.01-48 for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: ScopingUnitTestCase Test:testSingletons Type:failure Exception: junit.framework.AssertionFailedError Message: checkVersion(V2) is true - Suite: StatefulSessionUnitTestCase Test:testStrictPooling Type:failure Exception: junit.framework.AssertionFailedError Message: SessionInvoker.runEx != null - Suite: EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: ConnectionUnitTestCase Test:unknown Type:error Exception: junit.framework.AssertionFailedError Message: Timeout occurred - Suite: JDBCDriverRedeployUnitTestCase Test:testRedeploy Type:failure Exception: junit.framework.AssertionFailedError Message: This test does not work because of class caching in java.sql.DriverManager - Suite: MissingClassUnitTestCase Test:testDeployServiceWithoutClass Type:error Exception: org.jboss.deployment.DeploymentException Message: create operation failed for package file:/home/jboss/JBoss/cvs/jboss-3.2-snapshot/testsuite/output/lib/missingclass-service.xml; - nested throwable: (javax.management.InstanceNotFoundException: jboss.test:name=missingclasstest is not registered.) - Suite: SimpleUnitTestCase Test:testHaParitionName Type:error Exception: java.lang.NumberFormatException Message: For input string: DefaultPartition - Suite: SecurityUnitTestCase Test:testSecureHttpInvoker Type:failure Exception: junit.framework.AssertionFailedError Message: Should not have been able to lookup(invokers) - Suite: SecurityUnitTestCase Test:testHttpReadonlyLookup Type:failure Exception: junit.framework.AssertionFailedError Message: UndeclaredThrowableException thrown - Suite: SRPUnitTestCase Test:testEchoArgs Type:error Exception: java.lang.reflect.UndeclaredThrowableException Message: - Suite: XMLLoginModulesUnitTestCase Test:testJCACallerIdentity Type:error Exception: javax.security.auth.login.LoginException Message: Error: no CallbackHandler available to collect authentication information - Suite: HelloClusteredHttpStressTestCase Test:testCNFEObject Type:failure Exception: junit.framework.AssertionFailedError Message: Was able to invoke remove - Suite: JSR77SpecUnitTestCase Test:testNavigation Type:error Exception: javax.management.InstanceNotFoundException Message:
[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 10-July-2003
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 10-July-2003 JBoss daily test results SUMMARY Number of tests run: 1388 Successful tests: 1373 Errors:9 Failures: 6 [time of test: 2003-07-11.02-25 GMT] [java.version: 1.4.2] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.2-b28] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.20-18.9custom] Useful resources: - http://jboss.sourceforge.net//junit-results/32/2003-07-11.02-25 for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: ScopingUnitTestCase Test:testSingletons Type:failure Exception: junit.framework.AssertionFailedError Message: checkVersion(V2) is true - Suite: StatefulSessionUnitTestCase Test:testStrictPooling Type:failure Exception: junit.framework.AssertionFailedError Message: SessionInvoker.runEx != null - Suite: EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: JDBCDriverRedeployUnitTestCase Test:testRedeploy Type:failure Exception: junit.framework.AssertionFailedError Message: This test does not work because of class caching in java.sql.DriverManager - Suite: MissingClassUnitTestCase Test:testDeployServiceWithoutClass Type:error Exception: org.jboss.deployment.DeploymentException Message: create operation failed for package file:/home/jboss/JBoss/cvs/jboss-3.2-snapshot/testsuite/output/lib/missingclass-service.xml; - nested throwable: (javax.management.InstanceNotFoundException: jboss.test:name=missingclasstest is not registered.) - Suite: SimpleUnitTestCase Test:testHaParitionName Type:error Exception: java.lang.NumberFormatException Message: For input string: DefaultPartition - Suite: SecurityUnitTestCase Test:testSecureHttpInvoker Type:failure Exception: junit.framework.AssertionFailedError Message: Should not have been able to lookup(invokers) - Suite: SecurityUnitTestCase Test:testHttpReadonlyLookup Type:failure Exception: junit.framework.AssertionFailedError Message: UndeclaredThrowableException thrown - Suite: SRPUnitTestCase Test:testEchoArgs Type:error Exception: java.lang.reflect.UndeclaredThrowableException Message: - Suite: XMLLoginModulesUnitTestCase Test:testJCACallerIdentity Type:error Exception: javax.security.auth.login.LoginException Message: Error: no CallbackHandler available to collect authentication information - Suite: HelloClusteredHttpStressTestCase Test:testCNFEObject Type:failure Exception: junit.framework.AssertionFailedError Message: Was able to invoke remove - Suite: JSR77SpecUnitTestCase Test:testNavigation Type:error Exception: javax.management.InstanceNotFoundException Message: jboss.management.local:J2EEApplication=cts-v1cmp.ear,J2EEServer=Local,j2eeType=EJBModule,name=cts-v1cmp.jar is not registered. -
[JBoss-dev] [AUTOMATED] JBoss (HEAD/linux1) Compilation failed
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === === (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.deployment.EARDeployer' using template file 'jar:file:/home/jbossci/jbossci/jboss-head/thirdparty/xdoclet-xdoclet/lib/xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.jmx.connector.notification.RMINotificationListener' using template file 'jar:file:/home/jbossci/jbossci/jboss-head/thirdparty/xdoclet-xdoclet/lib/xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.jmx.adaptor.xml.XMLTestService' using template file 'jar:file:/home/jbossci/jbossci/jboss-head/thirdparty/xdoclet-xdoclet/lib/xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.ejb.EJBDeployer' using template file 'jar:file:/home/jbossci/jbossci/jboss-head/thirdparty/xdoclet-xdoclet/lib/xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.jmx.connector.notification.JMSNotificationListener' using template file 'jar:file:/home/jbossci/jbossci/jboss-head/thirdparty/xdoclet-xdoclet/lib/xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.naming.NamingService' using template file 'jar:file:/home/jbossci/jbossci/jboss-head/thirdparty/xdoclet-xdoclet/lib/xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.ejb.timer.AbstractTimerSource' using template file 'jar:file:/home/jbossci/jbossci/jboss-head/thirdparty/xdoclet-xdoclet/lib/xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.invocation.local.LocalInvoker' using template file 'jar:file:/home/jbossci/jbossci/jboss-head/thirdparty/xdoclet-xdoclet/lib/xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.web.WebService' using template file 'jar:file:/home/jbossci/jbossci/jboss-head/thirdparty/xdoclet-xdoclet/lib/xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager' using template file 'jar:file:/home/jbossci/jbossci/jboss-head/thirdparty/xdoclet-xdoclet/lib/xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.logging.Log4jSocketServer' using template file 'jar:file:/home/jbossci/jbossci/jboss-head/thirdparty/xdoclet-xdoclet/lib/xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.jmx.connector.notification.PollingNotificationListener' using template file 'jar:file:/home/jbossci/jbossci/jboss-head/thirdparty/xdoclet-xdoclet/lib/xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.jmx.adaptor.xml.XMLAdaptorService' using template file 'jar:file:/home/jbossci/jbossci/jboss-head/thirdparty/xdoclet-xdoclet/lib/xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.jmx.connector.ejb.EJBConnector' using template file 'jar:file:/home/jbossci/jbossci/jboss-head/thirdparty/xdoclet-xdoclet/lib/xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.jmx.adaptor.rmi.RMIAdaptorService' using template file 'jar:file:/home/jbossci/jbossci/jboss-head/thirdparty/xdoclet-xdoclet/lib/xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.naming.ExternalContext' using template file 'jar:file:/home/jbossci/jbossci/jboss-head/thirdparty/xdoclet-xdoclet/lib/xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.aspect.jmx.ManagedAspectFactory' using template file 'jar:file:/home/jbossci/jbossci/jboss-head/thirdparty/xdoclet-xdoclet/lib/xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'.
[JBoss-dev] [AUTOMATED] JBoss (HEAD/winxp) Compilation failed
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === === (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.deployment.EARDeployer' using template file 'jar:file:F:\jboss\jboss-head\thirdparty\xdoclet-xdoclet\lib\xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.jmx.connector.notification.RMINotificationListener' using template file 'jar:file:F:\jboss\jboss-head\thirdparty\xdoclet-xdoclet\lib\xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.jmx.adaptor.xml.XMLTestService' using template file 'jar:file:F:\jboss\jboss-head\thirdparty\xdoclet-xdoclet\lib\xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.ejb.EJBDeployer' using template file 'jar:file:F:\jboss\jboss-head\thirdparty\xdoclet-xdoclet\lib\xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.jmx.connector.notification.JMSNotificationListener' using template file 'jar:file:F:\jboss\jboss-head\thirdparty\xdoclet-xdoclet\lib\xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.naming.NamingService' using template file 'jar:file:F:\jboss\jboss-head\thirdparty\xdoclet-xdoclet\lib\xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.ejb.timer.AbstractTimerSource' using template file 'jar:file:F:\jboss\jboss-head\thirdparty\xdoclet-xdoclet\lib\xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.invocation.local.LocalInvoker' using template file 'jar:file:F:\jboss\jboss-head\thirdparty\xdoclet-xdoclet\lib\xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.web.WebService' using template file 'jar:file:F:\jboss\jboss-head\thirdparty\xdoclet-xdoclet\lib\xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager' using template file 'jar:file:F:\jboss\jboss-head\thirdparty\xdoclet-xdoclet\lib\xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.logging.Log4jSocketServer' using template file 'jar:file:F:\jboss\jboss-head\thirdparty\xdoclet-xdoclet\lib\xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.jmx.connector.notification.PollingNotificationListener' using template file 'jar:file:F:\jboss\jboss-head\thirdparty\xdoclet-xdoclet\lib\xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.jmx.adaptor.xml.XMLAdaptorService' using template file 'jar:file:F:\jboss\jboss-head\thirdparty\xdoclet-xdoclet\lib\xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.jmx.connector.ejb.EJBConnector' using template file 'jar:file:F:\jboss\jboss-head\thirdparty\xdoclet-xdoclet\lib\xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.jmx.adaptor.rmi.RMIAdaptorService' using template file 'jar:file:F:\jboss\jboss-head\thirdparty\xdoclet-xdoclet\lib\xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.naming.ExternalContext' using template file 'jar:file:F:\jboss\jboss-head\thirdparty\xdoclet-xdoclet\lib\xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.aspect.jmx.ManagedAspectFactory' using template file 'jar:file:F:\jboss\jboss-head\thirdparty\xdoclet-xdoclet\lib\xdoclet-jmx-module-jb4.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.naming.NamingAlias' using template file
[JBoss-dev] [ jboss-Bugs-769469 ] Failed to run JSF EA4 jsf-demo.war
Bugs item #769469, was opened at 2003-07-11 12:22 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=769469group_id=22866 Category: JBossWeb Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Willie Vu (willievu) Assigned to: Nobody/Anonymous (nobody) Summary: Failed to run JSF EA4 jsf-demo.war Initial Comment: This war is ok in stand-alone Tomcat 4.1.24-LE-jdk14 but failed in JBoss 3.2.x/Tomcat 4.1.24 bundle. When go to the first page, the exception org.apache.jasper.JasperException: Unable to compile class for JSP at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:478) shows up for the root cause: java.lang.NullPointerException at org.apache.tools.ant.Project.setSystemProperties(Project.java:862) at org.apache.tools.ant.Project.init(Project.java:316) at org.apache.jasper.compiler.Compiler.getProject(Compiler.java:172) The war is attached in http://www.jboss.org/thread.jsp?forum=50thread=36244. Please find the instructions to create the war there. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=769469group_id=22866 --- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing more. Download eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-769139 ] entityCtx.getEJBLocalObject() returns wrong instance
Bugs item #769139, was opened at 2003-07-10 07:03 Message generated for change (Comment added) made by starksm You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=769139group_id=22866 Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Alexei Yudichev (sflexus) Assigned to: Nobody/Anonymous (nobody) Summary: entityCtx.getEJBLocalObject() returns wrong instance Initial Comment: I am using Jboss 3.2.1 Sometimes entityContext.getEJBLocalObject() returns local interface of another instance of the same entity bean. I have a superclass for all my entities in application which implements EntityBean's setEntityContext() method and saves entityContext in a field. Inside one of business methods of one of entity beans I check if a primary key constructed from key CMP field(s) matches a primary key obtained from entityContext. getEJBLocalObject().getPrimaryKey(). Sometimes they do not match: entityContext.getEJBLocalObject(). getPrimaryKey() returns primary key of another instance of the same entity bean. I have sometimes situations when user is logged in as one customer and enjoys privileges of another... This happens ~20 times a day with a particular single object for me... I could install some kind of bug trap logging some debug info to help fix the bug. -- Comment By: Scott M Stark (starksm) Date: 2003-07-10 08:02 Message: Logged In: YES user_id=175228 The best starting point is an example of the bean in question in either source or psuedo code form as well as an outline of the busniess method in question so we can attempt a testcase. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=769139group_id=22866 --- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing more. Download eval WebKing and get a free book. www.parasoft.com/bulletproofapps ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] ClassCastException from ProxyCompiler$Proxy35.getId(generated)
jboss-head from ~ July 1. RedHat 8 JDK 1.4.1 Mysql I have a simple bean that has auto-generated Integer primary keys. MyLocal myLocal = myLocalHome.create(name, description); myLocal.getName(); -- works fine myLocal.getDescription(); -- works fine myLocal.getId(); -- Throws ClassCastException in the proxy. Bean gets created fine. Primary key comes back fine from the SQL insert (verified in log file from debug from JDBCGetGeneratedKeysCreateCommand). But, for some reason, when I call getId() it throws a ClassCastException. Calling getName() and getDescription() work fine. What's wierd, is that I can do a myLocalHome.findAll(), iterate through the returned collection and call getId() on those just fine. It just seems to be when I call getId() on the returned local ejb... Any clues? Thanks, Michael This is being done from a Servlet... --- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing more. Download eval WebKing and get a free book. www.parasoft.com/bulletproofapps ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
