RE: [JBoss-dev] MDB tests in HEAD
Did this mail just make it to the list ? Ouch... --jason On Sun, 23 Feb 2003, marc fleury wrote: he is bck marcf -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Dillon Sent: Wednesday, July 10, 2002 9:05 PM To: [EMAIL PROTECTED] Subject: [JBoss-dev] MDB tests in HEAD I am porting the changes I made to 3.0 back to HEAD (DLQHandler uses JMSProviderAdapter to attach to resources). After merging those changes I noticed that the MDB tests were very, very noisy. but reported no errors or failures. I doubled checked a clean copy of HEAD and it performs the same when running: ./testsuite/build.sh one-test -Dnojars=t -Dtest=org.jboss.test.mdb.test.MDBUnitTestCase I am seeing lots of ERROR and WARNs related to XA sessions: 2002-07-10 17:52:38,740 ERROR [org.jboss.jms.asf.StdServerSession] failed to commit/rollback javax.transaction.xa.XAException at org.jboss.mq.SpyXAResource.commit(SpyXAResource.java:105) at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession. java:289) at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage( SpyMessage Consumer.java:561) at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer. java:377) at org.jboss.mq.SpySession.run(SpySession.java:252) at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:177) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Poo ledExecuto r.java:642) at java.lang.Thread.run(Thread.java:479) . 2002-07-10 17:52:42,606 WARN [org.jboss.tm.TxCapsule] XAException: tx=XidImpl [FormatId=257, GlobalId=sanity.planet57.com//1536, BranchQual=] errorCode=XAER_RMERR javax.transaction.xa.XAException at org.jboss.mq.SpyXAResource.commit(SpyXAResource.java:105) at org.jboss.tm.TxCapsule.commitResources(TxCapsule.java:1651) at org.jboss.tm.TxCapsule.commit(TxCapsule.java:361) at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:73) at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession. java:319) at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage( SpyMessage Consumer.java:561) at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer. java:377) at org.jboss.mq.SpySession.run(SpySession.java:252) at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:177) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Poo ledExecuto r.java:642) at java.lang.Thread.run(Thread.java:479) * * * Are these errors normal? Or is the MDB sub-system unhappy? --jason --- This sf.net email is sponsored by:ThinkGeek Two, two, TWO treats in one. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Too many open files-errors
I am having problems to get JBoss run for longer than 1 week. Then the
OS (Linux 2.4.x) throws Too many open files-errors.
Environment used:
- RedHat Linux 7.2 on a SMP-machine.
- BEA JRockit 8 (we are using JRockit because we see excessive GC-pauses
(500s !!) with the Sun JDK), heap-size 1.2GB
- JBoss 3.0.3 (tried JBoss 3.0.6, too) with Tomcat 4.0.6
A first investigation with the lsof (list open files) showed that the
JVM has opened 140.000 files! I then had a look which files were open.
One that is opened 100.000 times is one called
${jboss.home}/server/default/tmp/deploy/.../conf/jboss-service.xml. Can
someone give me a hint where in the code this file is opened? I patched
one place in JBoss already. That brought down the inital file open count
to 10.000. So we now run into problems a little later.
Comments welcome
Thomas
---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] HttpProxyServlet?
Scott M Stark wrote:
Thomas Peuss is working on a load balancer that would encompass this. You
can see if there is code that is usable for you task.
The code is only in HEAD for now. You find the code at
{jboss.src}/varia/src/main/org/jboss/web/loadbalancer/. The compiled
service is ${jboss.src}/varia/output/lib/loadbalancer.sar. The config
file is easy to understand. I am currently working on the SSL-listener.
Comments welcome.
CU
Thomas
---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-691673 ] Jboss 3.0.6 and up Installation Problem with IBM JDK 1.4.
Bugs item #691673, was opened at 2003-02-23 09:32 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=691673group_id=22866 Category: CatalinaBundle Group: None Status: Open Resolution: None Priority: 5 Submitted By: Irakli (idumali) Assigned to: Scott M Stark (starksm) Summary: Jboss 3.0.6 and up Installation Problem with IBM JDK 1.4. Initial Comment: JBoss 3.0.6+Tomcat bundle is not working with IBM Java SDK 1.4 (would not start, throwing error in startup log). JBoss 3.0.4+Tomcat bundle did not have any such issue on the same machine. This is true for both Linux and Windows installations (we tried both). There are number of posts from different other users on JBoss forum, too. No answer from JBoss guys, as yet, though. This is quite a problem as IBM JDK works faster and better than SUN JDK - from our practical experience, at least. Can somebody address this, please? People reported the same problem with JBoss 3.2 RC2 on JBoss forum. Thanks -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=691673group_id=22866 --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Too many open files-errors
I don't know what could be opening the copy of the conf/jboss-service.xml file
so many times. Can you modify the File source to see what is opening this file
and pick it up with the bootclasspath option.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
- Original Message -
From: Thomas Peuss [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, February 23, 2003 2:42 AM
Subject: [JBoss-dev] Too many open files-errors
I am having problems to get JBoss run for longer than 1 week. Then the
OS (Linux 2.4.x) throws Too many open files-errors.
Environment used:
- RedHat Linux 7.2 on a SMP-machine.
- BEA JRockit 8 (we are using JRockit because we see excessive GC-pauses
(500s !!) with the Sun JDK), heap-size 1.2GB
- JBoss 3.0.3 (tried JBoss 3.0.6, too) with Tomcat 4.0.6
A first investigation with the lsof (list open files) showed that the
JVM has opened 140.000 files! I then had a look which files were open.
One that is opened 100.000 times is one called
${jboss.home}/server/default/tmp/deploy/.../conf/jboss-service.xml. Can
someone give me a hint where in the code this file is opened? I patched
one place in JBoss already. That brought down the inital file open count
to 10.000. So we now run into problems a little later.
Comments welcome
Thomas
---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-691673 ] Jboss 3.0.6 and up Installation Problem with IBM JDK 1.4.
Bugs item #691673, was opened at 2003-02-23 06:32 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=691673group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Pending Resolution: Later Priority: 5 Submitted By: Irakli (idumali) Assigned to: Scott M Stark (starksm) Summary: Jboss 3.0.6 and up Installation Problem with IBM JDK 1.4. Initial Comment: JBoss 3.0.6+Tomcat bundle is not working with IBM Java SDK 1.4 (would not start, throwing error in startup log). JBoss 3.0.4+Tomcat bundle did not have any such issue on the same machine. This is true for both Linux and Windows installations (we tried both). There are number of posts from different other users on JBoss forum, too. No answer from JBoss guys, as yet, though. This is quite a problem as IBM JDK works faster and better than SUN JDK - from our practical experience, at least. Can somebody address this, please? People reported the same problem with JBoss 3.2 RC2 on JBoss forum. Thanks -- Comment By: Scott M Stark (starksm) Date: 2003-02-23 09:58 Message: Logged In: YES user_id=175228 This appears to be either a bug in the Sun jdk1.4.1 compiler used to build the release not generating 1.4 compatible code, or a bug in the IBM 1.4 VM. The release will not even build with the IBM 1.4 JDK. To workaround the problem obtain the source code for the release and compile with the Sun JDK 1.3.1 compiler. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=691673group_id=22866 --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Patches-691765 ] run.bat fails with space in JAVA_HOME
Patches item #691765, was opened at 2003-02-23 12:59 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376687aid=691765group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Nathan Hoover (twisty7867) Assigned to: Nobody/Anonymous (nobody) Summary: run.bat fails with space in JAVA_HOME Initial Comment: bin/run.bat fails when there is a space in the path of the JAVA_HOME environment variable, such as when the JDK is installed in the Program Files folder. Simple fix - add quotes around %JAVA% on line that starts the VM. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376687aid=691765group_id=22866 --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 23-February-2003
JBoss daily test results SUMMARY Number of tests run: 1116 Successful tests: 1110 Errors:6 Failures: 0 [time of test: 2003-02-23.18-00 GMT] [java.version: 1.3.1_05] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.3.1_05-b02] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Windows 2000] [os.arch: x86] [os.version: 5.0] Useful resources: - http://users.jboss.org/~starksm/Branch_3_2/2003-02-23.18-00 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: SecurityUnitTestCase Test:runValidDynDurSub(org.jboss.test.jbossmq.test.SecurityUnitTestCase) Type:error Exception: java.lang.InternalError Message: Test timeout - Suite: DeployXMBeanUnitTestCase Test:testDeployUserXMBean(org.jboss.test.jmx.test.DeployXMBeanUnitTestCase) Type:error Exception: org.jboss.deployment.DeploymentException Message: create operation failed for package file:/C:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/user-xmbean.sar; - nested throwable: (org.jboss.deployment.DeploymentException: Error parsing the XML file: org.xml.sax.SAXParseException: Attribute persistPolicy with value Never must have a value from the list NEVER ONUPDATE NOMOREOFTENTHAN ONTIMER .; - nested throwable: (javax.management.NotCompliantMBeanException: Error parsing the XML file: org.xml.sax.SAXParseException: Attribute persistPolicy with value Never must have a value from the list NEVER ONUPDATE NOMOREOFTENTHAN ONTIMER .)) - Suite: MissingClassUnitTestCase Test: testDeployServiceWithoutClass(org.jboss.test.jmx.test.MissingClassUnitTestCase) Type:error Exception: org.jboss.deployment.DeploymentException Message: create operation failed for package file:/C:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - nested throwable: (javax.management.InstanceNotFoundException: jboss.test:name=missingclasstest is not registered.) - Suite: JSR77SpecUnitTestCase Test:testNavigation(org.jboss.test.management.test.JSR77SpecUnitTestCase) 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. - Suite: HttpsUnitTestCase Test:testJSSE(org.jboss.test.security.test.HttpsUnitTestCase) Type:error Exception: java.net.BindException Message: Address in use: JVM_Bind - Suite: SRPUnitTestCase Test:testEchoArgs(org.jboss.test.security.test.SRPUnitTestCase) Type:error Exception: java.lang.reflect.UndeclaredThrowableException Message: - --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 23-February-2003
Of these errors, I think 2 are won't fix. MissingClassUnitTestCase would require a nasty backport from head that I don't want to do. Perhaps we should remove or disable the test? DeployXMBeanUnitTestCase is breaking because the xdoclet version used to build 3.2 has the wrong version of the xmbean_1_0.dtd bundled in it. Fixing this would require (or be best done) by upgrading to a more current version of xdoclet. This requires changing all our build files to remove the formerly deprecated and now disallowed xdoclet source=blah usage. I'm not thrilled about doing this either. david jencks On 2003.02.23 13:56 [EMAIL PROTECTED] wrote: JBoss daily test results SUMMARY Number of tests run: 1116 Successful tests: 1110 Errors:6 Failures: 0 [time of test: 2003-02-23.18-00 GMT] [java.version: 1.3.1_05] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.3.1_05-b02] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Windows 2000] [os.arch: x86] [os.version: 5.0] Useful resources: - http://users.jboss.org/~starksm/Branch_3_2/2003-02-23.18-00 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: SecurityUnitTestCase Test:runValidDynDurSub(org.jboss.test.jbossmq.test.SecurityUnitTestCase) Type:error Exception: java.lang.InternalError Message: Test timeout - Suite: DeployXMBeanUnitTestCase Test:testDeployUserXMBean(org.jboss.test.jmx.test.DeployXMBeanUnitTestCase) Type:error Exception: org.jboss.deployment.DeploymentException Message: create operation failed for package file:/C:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/user-xmbean.sar; - nested throwable: (org.jboss.deployment.DeploymentException: Error parsing the XML file: org.xml.sax.SAXParseException: Attribute persistPolicy with value Never must have a value from the list NEVER ONUPDATE NOMOREOFTENTHAN ONTIMER .; - nested throwable: (javax.management.NotCompliantMBeanException: Error parsing the XML file: org.xml.sax.SAXParseException: Attribute persistPolicy with value Never must have a value from the list NEVER ONUPDATE NOMOREOFTENTHAN ONTIMER .)) - Suite: MissingClassUnitTestCase Test: testDeployServiceWithoutClass(org.jboss.test.jmx.test.MissingClassUnitTestCase) Type:error Exception: org.jboss.deployment.DeploymentException Message: create operation failed for package file:/C:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/missingclass-service.xml; - nested throwable: (javax.management.InstanceNotFoundException: jboss.test:name=missingclasstest is not registered.) - Suite: JSR77SpecUnitTestCase Test:testNavigation(org.jboss.test.management.test.JSR77SpecUnitTestCase) 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. - Suite: HttpsUnitTestCase Test:testJSSE(org.jboss.test.security.test.HttpsUnitTestCase) Type:error Exception: java.net.BindException Message: Address in use: JVM_Bind - Suite: SRPUnitTestCase Test:testEchoArgs(org.jboss.test.security.test.SRPUnitTestCase) Type:error Exception: java.lang.reflect.UndeclaredThrowableException Message: - --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED]
[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
= ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS= = JAVA VERSION DETAILS java version 1.3.1_06 Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_06-b01) Java HotSpot(TM) Server VM (build 1.3.1_06-b01, mixed mode) = HERE ARE THE LAST 50 LINES OF THE LOG FILE org.jboss.ejb.EJBDeployer -- EJBDeployerMBean qualified to EJBDeployerMBean org.jboss.ejb.ContainerPlugin -- Service qualified to Service org.jboss.ejb.InstanceCache -- StatisticsProvider qualified to StatisticsProvider org.jboss.ejb.EntityEnterpriseContext -- EJBContextImpl qualified to EJBContextImpl org.jboss.invocation.Invoker -- Remote qualified to Remote org.jboss.ejb.StatefulSessionContainer -- AbstractContainerInterceptor qualified to AbstractContainerInterceptor org.jboss.ejb.EjbModule -- EjbModuleMBean qualified to EjbModuleMBean org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager -- StatefulSessionFilePersistenceManagerMBean qualified to StatefulSessionFilePersistenceManagerMBean org.jboss.ejb.timer.AbstractTimerSource -- AbstractTimerSourceMBean qualified to AbstractTimerSourceMBean org.jboss.ejb.timer.FilePersistenceManager -- FilePersistenceManagerMBean qualified to FilePersistenceManagerMBean org.jboss.ejb.timer.SchedulerTimerSource -- SchedulerTimerSourceMBean qualified to SchedulerTimerSourceMBean org.jboss.invocation.InvokerXAResource -- InvokerXAResourceMBean qualified to InvokerXAResourceMBean org.jboss.invocation.XATerminatorContainer -- XATerminatorContainerMBean qualified to XATerminatorContainerMBean org.jboss.invocation.http.server.HttpInvokerMBean -- ServiceMBean qualified to ServiceMBean org.jboss.invocation.local.LocalInvoker -- LocalInvokerMBean qualified to LocalInvokerMBean org.jboss.invocation.jrmp.server.JRMPInvoker -- JRMPInvokerMBean qualified to JRMPInvokerMBean org.jboss.invocation.pooled.server.PooledInvoker -- PooledInvokerMBean qualified to PooledInvokerMBean org.jboss.invocation.trunk.client.ConnectionManager -- ConnectionManagerMBean qualified to ConnectionManagerMBean org.jboss.invocation.trunk.client.TrunkInvokerProxy -- TrunkInvokerProxyMBean qualified to TrunkInvokerProxyMBean org.jboss.invocation.trunk.server.TrunkInvoker -- TrunkInvokerMBean qualified to TrunkInvokerMBean org.jboss.jms.asf.ServerSessionPoolLoader -- ServerSessionPoolLoaderMBean qualified to ServerSessionPoolLoaderMBean org.jboss.jms.jndi.JMSProviderLoader -- JMSProviderLoaderMBean qualified to JMSProviderLoaderMBean org.jboss.jmx.connector.RemoteMBeanServer -- MBeanServer qualified to MBeanServer org.jboss.jmx.connector.notification.JMSNotificationListener -- JMSNotificationListenerMBean qualified to JMSNotificationListenerMBean org.jboss.jmx.connector.notification.RMINotificationListener -- RMINotificationListenerMBean qualified to RMINotificationListenerMBean org.jboss.jmx.adaptor.rmi.RMIAdaptorService -- RMIAdaptorServiceMBean qualified to RMIAdaptorServiceMBean org.jboss.jmx.adaptor.xml.XMLAdaptorService -- XMLAdaptorServiceMBean qualified to XMLAdaptorServiceMBean org.jboss.jmx.adaptor.xml.XMLTestService -- XMLTestServiceMBean qualified to XMLTestServiceMBean org.jboss.jmx.connector.rmi.RMIConnectorImpl -- RMIConnectorImplMBean qualified to RMIConnectorImplMBean org.jboss.jmx.connector.ejb.EJBConnector -- EJBConnectorMBean qualified to EJBConnectorMBean org.jboss.jmx.connector.ConnectorFactoryService -- ConnectorFactoryServiceMBean qualified to ConnectorFactoryServiceMBean org.jboss.jmx.connector.notification.PollingNotificationListener -- PollingNotificationListenerMBean qualified to PollingNotificationListenerMBean org.jboss.logging.Log4jService -- Log4jServiceMBean qualified to Log4jServiceMBean org.jboss.logging.Log4jSocketServer -- Log4jSocketServerMBean qualified to Log4jSocketServerMBean org.jboss.naming.ExternalContext -- ExternalContextMBean qualified to ExternalContextMBean org.jboss.naming.JNDIView -- JNDIViewMBean qualified to JNDIViewMBean org.jboss.naming.NamingAlias -- NamingAliasMBean qualified to NamingAliasMBean org.jboss.naming.NamingService -- NamingServiceMBean qualified to NamingServiceMBean org.jboss.web.AbstractWebContainer -- AbstractWebContainerMBean qualified to AbstractWebContainerMBean WARNING: Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. Since at least one package is imported, it is impossible for xjavadoc to figure out what package the referred classes belong to. The classes are: org.jboss.web.WebService -- WebServiceMBean qualified to WebServiceMBean BUILD FAILED
[JBoss-dev] Automated JBoss(Branch_3_0) Testsuite Results: 23-February-2003
JBoss daily test results SUMMARY Number of tests run: 1049 Successful tests: 1045 Errors:1 Failures: 3 [time of test: 2003-02-23.12-05 GMT] [java.version: 1.3.1] [java.vendor: Apple Computer, Inc.] [java.vm.version: 1.3.1_03-69] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Mac OS X] [os.arch: ppc] [os.version: 10.2.4] See http://users.jboss.org/~starksm/Branch_3_0/2003-02-23.12-05 for details 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: MissingClassUnitTestCase Test: testDeployServiceWithoutClass(org.jboss.test.jmx.test.MissingClassUnitTestCase) Type:error Exception: org.jboss.deployment.DeploymentException Message: jboss.test:name=missingclasstest is not registered.; - nested throwable: (javax.management.InstanceNotFoundException: jboss.test:name=missingclasstest is not registered.) - Suite: SecurityUnitTestCase Test:testSecureHttpInvoker(org.jboss.test.naming.test.SecurityUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: Should not have been able to lookup(invokers) - Suite: SecurityUnitTestCase Test: testSecureHttpInvokerFailure(org.jboss.test.naming.test.SecurityUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: Should not have been able to lookup(invokers) - Suite: BeanStressTestCase Test:testDeadLockFromClient(org.jboss.test.deadlock.test.BeanStressTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: expected a client deadlock for AB BA - --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-691673 ] Jboss 3.0.6 and up Installation Problem with IBM JDK 1.4.
Bugs item #691673, was opened at 2003-02-23 09:32 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=691673group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: Later Priority: 5 Submitted By: Irakli (idumali) Assigned to: Scott M Stark (starksm) Summary: Jboss 3.0.6 and up Installation Problem with IBM JDK 1.4. Initial Comment: JBoss 3.0.6+Tomcat bundle is not working with IBM Java SDK 1.4 (would not start, throwing error in startup log). JBoss 3.0.4+Tomcat bundle did not have any such issue on the same machine. This is true for both Linux and Windows installations (we tried both). There are number of posts from different other users on JBoss forum, too. No answer from JBoss guys, as yet, though. This is quite a problem as IBM JDK works faster and better than SUN JDK - from our practical experience, at least. Can somebody address this, please? People reported the same problem with JBoss 3.2 RC2 on JBoss forum. Thanks -- Comment By: Irakli (idumali) Date: 2003-02-23 17:45 Message: Logged In: YES user_id=718846 Thanks for a quick follow-up. I am sorry but, I think the root of the problem is deeper - in the source code of JBoss, which somehow appears to be incompatible with IBM JDK, begining from the version 3.0.6, because (as you also noted) source does not even compile with IBM JDK 1.4. Of course, it may well be IBM's fault, for non-full compatibility with standards (or may not be), but that does not help does it? Regarding your solution - did it work for you? To compile with Sun JDK 1.3.1 and then run on IBM JDK 1.4??? I do apoligize, but you probabely understand how odd it dounds. Thanks -- Comment By: Scott M Stark (starksm) Date: 2003-02-23 12:58 Message: Logged In: YES user_id=175228 This appears to be either a bug in the Sun jdk1.4.1 compiler used to build the release not generating 1.4 compatible code, or a bug in the IBM 1.4 VM. The release will not even build with the IBM 1.4 JDK. To workaround the problem obtain the source code for the release and compile with the Sun JDK 1.3.1 compiler. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=691673group_id=22866 --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] TxInterceptor split is still the best thing since sliced bread
I am getting really tired of doing this you guys. I'll try taking a look at it, in the meantime can we burry the hatchets? If the case is that grey it probably means there isn't a good answer, I will talk with Scott in Vegas. cheer up guys, the road is still long, marcf -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Jencks Sent: Saturday, February 22, 2003 11:48 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] TxInterceptor split is still the best thing since sliced bread This is really boring and unpleasant, bill. We don't seem to have a shared understanding of how interceptors ought to work with local and remote calls. Most of your comments make no sense to me, and I think contrariwise. I'll try to explain my view one more time, and I'll write an interceptor framework that satisfies my understanding of what is needed for mbeans, ejbs, remoting, and aop (which I don't understand all that well). If you don't like it and I can't understand your objections, I'll let you indulge your previously expressed wish to write a transaction manager. You might also get that wish fulfilled if you say the following is obvious. I thought it was, but I don't think we have agreed on it. I'm writing it down to try to form a basis for discussion, which is currently missing. == Dave's mental model for invocations. Lets assume first you already have something representing the object you are interested in (such as an ejb Remote interface object, mbean thingy, aop-ized object, or some kind of proxy). Items marked with a * might be removed for non-remotable objects. Key to symbols: \/ interceptor chain invokeNext() calls. \/ || method/field access/... calls whose nature may vary depending on the application and that are not part of the interceptor/invocation framework. \/ \/ calls between segments. These are of the form invoke(invocation) on a particular object found by the current interceptor. .. sequence of interceptors in a chain. || || transport mechanism. For a remote object, this is the boundary between client and server. === Some program does something on the object \/ || The Object \/ || Something that knows about interceptor chains and metadata. It looks at the method (or field access, ...) call and its environment and determines what interceptor chain to use. It constructs an Invocation object that includes an iterator over the selected chain, the method call data, and some metadata. Then it starts the invocation down the chain. I will call this a Container. I believe it corresponds to your aop Advisor(s). \/ Several interceptors (client side interceptors specific to the object/class you are calling) . \/ * Transport selector interceptor. This examines the metadata and picks a transport endpoint. It calls invoke(invocation) on the selected transport endpoint. It does not call invocation.invokeNext(), so this may be the end of the use of the original interceptor iterator. \/ \/ * Transport endpoint. If this is a local do nothing transport, it may simply call invocation.invokeNext(). Otherwise, it replaces the interceptor iterator with one for the client side transport interceptor stack. \/ * Several interceptors (client side interceptors specific to the transport endpoint you are calling. Examples would include the XAResource representing a remote jboss instance (whenever the branch is created, you still need an XAResource, and it needs to know about the method calls), and the clustering thingy that picks a remote server) \/ * client side end of the transport. I believe this is essentially the remoting framework. || || || * server side end of the transport. This may include some kind of relationship with a thread pool. Lets assume the work is dispatched with a thread, no matter how it is picked and how synchronous/asynchronous it is. Anyway, the reconstituted invocation object has its interceptor iterator replaced with one for the transport specific server side interceptors \/ * Several interceptors (server side interceptors specific to the transport. In my current dtm implementation, one of these would import an xid in the invocation into the server side tm) . * Target selector. Based on the metadata, this interceptor picks and locates a target object, and calls invoke(invocation) on it. This is the end of the transport specific server side interceptor chain. \/ \/ * Server side target object. This is analogous to the current server side ejb Container object. It replaces the invocation's interceptor iterator and starts it off by calling
[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
= ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS= = JAVA VERSION DETAILS java version 1.3.1_06 Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_06-b01) Java HotSpot(TM) Server VM (build 1.3.1_06-b01, mixed mode) = HERE ARE THE LAST 50 LINES OF THE LOG FILE org.jboss.ejb.EJBDeployer -- EJBDeployerMBean qualified to EJBDeployerMBean org.jboss.ejb.ContainerPlugin -- Service qualified to Service org.jboss.ejb.InstanceCache -- StatisticsProvider qualified to StatisticsProvider org.jboss.ejb.EntityEnterpriseContext -- EJBContextImpl qualified to EJBContextImpl org.jboss.invocation.Invoker -- Remote qualified to Remote org.jboss.ejb.StatefulSessionContainer -- AbstractContainerInterceptor qualified to AbstractContainerInterceptor org.jboss.ejb.EjbModule -- EjbModuleMBean qualified to EjbModuleMBean org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager -- StatefulSessionFilePersistenceManagerMBean qualified to StatefulSessionFilePersistenceManagerMBean org.jboss.ejb.timer.AbstractTimerSource -- AbstractTimerSourceMBean qualified to AbstractTimerSourceMBean org.jboss.ejb.timer.FilePersistenceManager -- FilePersistenceManagerMBean qualified to FilePersistenceManagerMBean org.jboss.ejb.timer.SchedulerTimerSource -- SchedulerTimerSourceMBean qualified to SchedulerTimerSourceMBean org.jboss.invocation.InvokerXAResource -- InvokerXAResourceMBean qualified to InvokerXAResourceMBean org.jboss.invocation.XATerminatorContainer -- XATerminatorContainerMBean qualified to XATerminatorContainerMBean org.jboss.invocation.http.server.HttpInvokerMBean -- ServiceMBean qualified to ServiceMBean org.jboss.invocation.local.LocalInvoker -- LocalInvokerMBean qualified to LocalInvokerMBean org.jboss.invocation.jrmp.server.JRMPInvoker -- JRMPInvokerMBean qualified to JRMPInvokerMBean org.jboss.invocation.pooled.server.PooledInvoker -- PooledInvokerMBean qualified to PooledInvokerMBean org.jboss.invocation.trunk.client.ConnectionManager -- ConnectionManagerMBean qualified to ConnectionManagerMBean org.jboss.invocation.trunk.client.TrunkInvokerProxy -- TrunkInvokerProxyMBean qualified to TrunkInvokerProxyMBean org.jboss.invocation.trunk.server.TrunkInvoker -- TrunkInvokerMBean qualified to TrunkInvokerMBean org.jboss.jms.asf.ServerSessionPoolLoader -- ServerSessionPoolLoaderMBean qualified to ServerSessionPoolLoaderMBean org.jboss.jms.jndi.JMSProviderLoader -- JMSProviderLoaderMBean qualified to JMSProviderLoaderMBean org.jboss.jmx.connector.RemoteMBeanServer -- MBeanServer qualified to MBeanServer org.jboss.jmx.connector.notification.JMSNotificationListener -- JMSNotificationListenerMBean qualified to JMSNotificationListenerMBean org.jboss.jmx.connector.notification.RMINotificationListener -- RMINotificationListenerMBean qualified to RMINotificationListenerMBean org.jboss.jmx.adaptor.rmi.RMIAdaptorService -- RMIAdaptorServiceMBean qualified to RMIAdaptorServiceMBean org.jboss.jmx.adaptor.xml.XMLAdaptorService -- XMLAdaptorServiceMBean qualified to XMLAdaptorServiceMBean org.jboss.jmx.adaptor.xml.XMLTestService -- XMLTestServiceMBean qualified to XMLTestServiceMBean org.jboss.jmx.connector.rmi.RMIConnectorImpl -- RMIConnectorImplMBean qualified to RMIConnectorImplMBean org.jboss.jmx.connector.ejb.EJBConnector -- EJBConnectorMBean qualified to EJBConnectorMBean org.jboss.jmx.connector.ConnectorFactoryService -- ConnectorFactoryServiceMBean qualified to ConnectorFactoryServiceMBean org.jboss.jmx.connector.notification.PollingNotificationListener -- PollingNotificationListenerMBean qualified to PollingNotificationListenerMBean org.jboss.logging.Log4jService -- Log4jServiceMBean qualified to Log4jServiceMBean org.jboss.logging.Log4jSocketServer -- Log4jSocketServerMBean qualified to Log4jSocketServerMBean org.jboss.naming.ExternalContext -- ExternalContextMBean qualified to ExternalContextMBean org.jboss.naming.JNDIView -- JNDIViewMBean qualified to JNDIViewMBean org.jboss.naming.NamingAlias -- NamingAliasMBean qualified to NamingAliasMBean org.jboss.naming.NamingService -- NamingServiceMBean qualified to NamingServiceMBean org.jboss.web.AbstractWebContainer -- AbstractWebContainerMBean qualified to AbstractWebContainerMBean WARNING: Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. Since at least one package is imported, it is impossible for xjavadoc to figure out what package the referred classes belong to. The classes are: org.jboss.web.WebService -- WebServiceMBean qualified to WebServiceMBean BUILD FAILED
[JBoss-dev] why there are two javaURLContextFactory.java?
Hi, Rickard In the jndi.properties file, there is such a line: java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces who can explain to me that under what situation the first prefix org.jboss.naming will be used and under what situation, the second one (org.jnp.interfaces) will be used? I am confused by the fact that there is two javaURLContextFactory.java file . One is org.jboss.naming.java.javaURLContextFactory.java, the other is org.jnp.interfaces.java.javaURLContextFactory.java. What rules the jboss follow will follow to use one of them? I trace the source code, i find that it seems that org.jboss.naming.java.javaURLContext will be used when the iniCtx.lookup(java:) is called during the startService of the NamingService.java. But if i write my own simple testing program which simulate the starting up of naming service, the org.jnp.interfaces.java.javaURLContext is always called. WHY Thanks a lot! yang --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] invite to irc channel of jboss
Hi, we invite you to join the irc channel of jboss! I hope you can give advice and get more developers there for jboss project. Steps: (1) download xchat and install it. (2) in the server list, add new server : irc.redhat.com with port 6667 (3) /join #jboss We are waiting for you! yang --- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
= ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS= = JAVA VERSION DETAILS java version 1.3.1_06 Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_06-b01) Java HotSpot(TM) Server VM (build 1.3.1_06-b01, mixed mode) = HERE ARE THE LAST 50 LINES OF THE LOG FILE org.jboss.ejb.EJBDeployer -- EJBDeployerMBean qualified to EJBDeployerMBean org.jboss.ejb.ContainerPlugin -- Service qualified to Service org.jboss.ejb.InstanceCache -- StatisticsProvider qualified to StatisticsProvider org.jboss.ejb.EntityEnterpriseContext -- EJBContextImpl qualified to EJBContextImpl org.jboss.invocation.Invoker -- Remote qualified to Remote org.jboss.ejb.StatefulSessionContainer -- AbstractContainerInterceptor qualified to AbstractContainerInterceptor org.jboss.ejb.EjbModule -- EjbModuleMBean qualified to EjbModuleMBean org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager -- StatefulSessionFilePersistenceManagerMBean qualified to StatefulSessionFilePersistenceManagerMBean org.jboss.ejb.timer.AbstractTimerSource -- AbstractTimerSourceMBean qualified to AbstractTimerSourceMBean org.jboss.ejb.timer.FilePersistenceManager -- FilePersistenceManagerMBean qualified to FilePersistenceManagerMBean org.jboss.ejb.timer.SchedulerTimerSource -- SchedulerTimerSourceMBean qualified to SchedulerTimerSourceMBean org.jboss.invocation.InvokerXAResource -- InvokerXAResourceMBean qualified to InvokerXAResourceMBean org.jboss.invocation.XATerminatorContainer -- XATerminatorContainerMBean qualified to XATerminatorContainerMBean org.jboss.invocation.http.server.HttpInvokerMBean -- ServiceMBean qualified to ServiceMBean org.jboss.invocation.local.LocalInvoker -- LocalInvokerMBean qualified to LocalInvokerMBean org.jboss.invocation.jrmp.server.JRMPInvoker -- JRMPInvokerMBean qualified to JRMPInvokerMBean org.jboss.invocation.pooled.server.PooledInvoker -- PooledInvokerMBean qualified to PooledInvokerMBean org.jboss.invocation.trunk.client.ConnectionManager -- ConnectionManagerMBean qualified to ConnectionManagerMBean org.jboss.invocation.trunk.client.TrunkInvokerProxy -- TrunkInvokerProxyMBean qualified to TrunkInvokerProxyMBean org.jboss.invocation.trunk.server.TrunkInvoker -- TrunkInvokerMBean qualified to TrunkInvokerMBean org.jboss.jms.asf.ServerSessionPoolLoader -- ServerSessionPoolLoaderMBean qualified to ServerSessionPoolLoaderMBean org.jboss.jms.jndi.JMSProviderLoader -- JMSProviderLoaderMBean qualified to JMSProviderLoaderMBean org.jboss.jmx.connector.RemoteMBeanServer -- MBeanServer qualified to MBeanServer org.jboss.jmx.connector.notification.JMSNotificationListener -- JMSNotificationListenerMBean qualified to JMSNotificationListenerMBean org.jboss.jmx.connector.notification.RMINotificationListener -- RMINotificationListenerMBean qualified to RMINotificationListenerMBean org.jboss.jmx.adaptor.rmi.RMIAdaptorService -- RMIAdaptorServiceMBean qualified to RMIAdaptorServiceMBean org.jboss.jmx.adaptor.xml.XMLAdaptorService -- XMLAdaptorServiceMBean qualified to XMLAdaptorServiceMBean org.jboss.jmx.adaptor.xml.XMLTestService -- XMLTestServiceMBean qualified to XMLTestServiceMBean org.jboss.jmx.connector.rmi.RMIConnectorImpl -- RMIConnectorImplMBean qualified to RMIConnectorImplMBean org.jboss.jmx.connector.ejb.EJBConnector -- EJBConnectorMBean qualified to EJBConnectorMBean org.jboss.jmx.connector.ConnectorFactoryService -- ConnectorFactoryServiceMBean qualified to ConnectorFactoryServiceMBean org.jboss.jmx.connector.notification.PollingNotificationListener -- PollingNotificationListenerMBean qualified to PollingNotificationListenerMBean org.jboss.logging.Log4jService -- Log4jServiceMBean qualified to Log4jServiceMBean org.jboss.logging.Log4jSocketServer -- Log4jSocketServerMBean qualified to Log4jSocketServerMBean org.jboss.naming.ExternalContext -- ExternalContextMBean qualified to ExternalContextMBean org.jboss.naming.JNDIView -- JNDIViewMBean qualified to JNDIViewMBean org.jboss.naming.NamingAlias -- NamingAliasMBean qualified to NamingAliasMBean org.jboss.naming.NamingService -- NamingServiceMBean qualified to NamingServiceMBean org.jboss.web.AbstractWebContainer -- AbstractWebContainerMBean qualified to AbstractWebContainerMBean WARNING: Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. Since at least one package is imported, it is impossible for xjavadoc to figure out what package the referred classes belong to. The classes are: org.jboss.web.WebService -- WebServiceMBean qualified to WebServiceMBean BUILD FAILED
[JBoss-dev] test
--- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
