[JBoss-dev] [ jboss-Bugs-670650 ] EJBVerifier20 PrimaryKey test bug
Bugs item #670650, was opened at 2003-01-19 13:38
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=670650&group_id=22866
Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Lutz Walter (luwasoft)
Assigned to: Nobody/Anonymous (nobody)
Summary: EJBVerifier20 PrimaryKey test bug
Initial Comment:
Version JBoss 3.0.5(stable) and JBoss 3.2.0RC1
OS independent, JDK independent
The EJBVerifier20 does a missleading verification on
PrimaryKey's.
To verifiy if the PrimaryKeyClass has a "suitable
implementation of the equals(Object other) method"
(12.2.12.c) it does:
>from EJBVerifier20.java
cls = classloader.loadClass(entity.getPrimaryKeyClass());
one = cls.newInstance();
two = cls.newInstance();
if( !one.equals(two) ) {
if( cmp ) {
fireSpecViolationEvent( entity,
new Section("10.6.13.c"));
} else {
fireSpecViolationEvent( entity,
new Section("12.2.12.c"));
}
Please correct me if i am wrong but as far as i know, a
uninitialized PrimaryKey should never equal to another,
even if the other is in the same uninitialized state.
So, this is not the right test to verify this.
In JBoss 3.0.5 this results only in some "INFO"
messages during deployment, in JBoss 3.2.0RC1 the
EJBDeployer does not deploy EJBs with those PKs that
fail this test
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=670650&group_id=22866
---
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-615667 ] SQLException storing Oracle LONG
Bugs item #615667, was opened at 2002-09-27 20:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=615667&group_id=22866 Category: JBossCMP Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Chris Bonham (bonhamcm) Assigned to: Nobody/Anonymous (nobody) Summary: SQLException storing Oracle LONG Initial Comment: I'm using JBoss 3.0.2 W2K with JDK 1.3.1_04, Oracle 9i and the Thin drivers. I have a EJB 2.0 bean that uses an Oracle LONG field in its table. Reading from it is fine, but when I try to insert a record greater than 4000 characters, I get this error: [org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreEntityComma nd.SnippetCache] Executing SQL: UPDATE CACHE SET CONTENT=?, lastmodifytime=?, timetodie=? WHERE id=? 2002-09-27 14:49:47,838 ERROR [org.jboss.ejb.GlobalTxEntityMap] Store failed on entity: 4633 javax.ejb.EJBException: Internal error setting parameters for field htmlAndHeaderContent; CausedByException is: Data size bigger than max size for this type: 34130 at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCAbstractCMP FieldBridge.setArgumentParameters (JDBCAbstractCMPFieldBridge.java:289) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCAbstractCMP FieldBridge.setInstanceParameters (JDBCAbstractCMPFieldBridge.java:262) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreEntityComman d.execute(JDBCStoreEntityCommand.java:85) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.store Entity(JDBCStoreManager.java:589) at org.jboss.ejb.plugins.CMPPersistenceManager.storeEnti ty(CMPPersistenceManager.java:458) at org.jboss.resource.connectionmanager.CachedConnectio nInterceptor.storeEntity (CachedConnectionInterceptor.java:388) at org.jboss.ejb.EntityContainer.storeEntity (EntityContainer.java:705) at org.jboss.ejb.GlobalTxEntityMap.syncEntities (GlobalTxEntityMap.java:99) at org.jboss.ejb.EntityContainer.synchronizeEntitiesWithinT ransaction(EntityContainer.java:172) at org.jboss.ejb.EntityContainer.findLocal (EntityContainer.java:604) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.ejb.EntityContainer$ContainerInterceptor.invoke Home(EntityContainer.java:1116) at org.jboss.ejb.plugins.AbstractInterceptor.invokeHome (AbstractInterceptor.java:73) at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.inv okeHome(EntitySynchronizationInterceptor.java:209) at org.jboss.resource.connectionmanager.CachedConnectio nInterceptor.invokeHome (CachedConnectionInterceptor.java:215) at org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHo me(EntityInstanceInterceptor.java:88) at org.jboss.ejb.plugins.EntityLockInterceptor.invokeHome (EntityLockInterceptor.java:79) at org.jboss.ejb.plugins.EntityCreationInterceptor.invokeHo me(EntityCreationInterceptor.java:44) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext (AbstractTxInterceptor.java:111) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransacti ons(TxInterceptorCMT.java:178) at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome (TxInterceptorCMT.java:52) at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome (SecurityInterceptor.java:105) at org.jboss.ejb.plugins.LogInterceptor.invokeHome (LogInterceptor.java:129) at org.jboss.ejb.EntityContainer.invokeHome (EntityContainer.java:487) at org.jboss.ejb.plugins.local.BaseLocalContainerInvoker.inv okeHome(BaseLocalContainerInvoker.java:230) at org.jboss.ejb.plugins.local.LocalHomeProxy.invoke (LocalHomeProxy.java:110) at $Proxy46.findByKey(Unknown Source) at **private** at java.lang.reflect.Method.invoke(Native Method) at org.jboss.ejb.StatelessSessionContainer$ContainerInterc eptor.invoke(StatelessSessionContainer.java:660) at org.jboss.resource.connectionmanager.CachedConnectio nInterceptor.invoke (CachedConnectionInterceptor.java:186) at org.jboss.ejb.plugins.StatelessSessionInstanceIntercept or.invoke(StatelessSessionInstanceInterceptor.java:77) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext (AbstractTxInterceptor.java:107) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransacti ons(TxInterceptorCMT.java:178) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke (TxInterceptorCMT.java:60) at org.jboss.ejb.plugins.SecurityInterceptor.invoke (SecurityInterceptor.java:130) at org.jboss.ejb.plugins.LogInterceptor.invoke (LogInterceptor.java:203) at org.jboss.ejb.StatelessSessionContainer.invoke (StatelessSessionContainer.java:313) at org.jboss.ejb.plugins.local.BaseLocalContainerInvoker.inv oke(BaseLocalContainerInvoker.java:301) at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke (StatelessSessionProxy.java:81) at $Proxy67.getConfigurationValue(
Re: [JBoss-dev] Transaction propagation change
David Jencks wrote: On Thursday, January 16, 2003, at 09:10 AM, Barlow, Dustin wrote: Let me simplify the example to demonstrate my real point. (and hopefully this is a better example) In the 3.x series of JBoss, there isn't a way to have one SSB with a transaction attribute of Required call another SSB with a transaction attribute of Required on a second jboss instance and have both of those beans enlist in any kind of "native" JBoss transaction. If you stay within one instance of JBoss, you are fine, but the moment you start to really do n-tier designs with tight transaction integration (ie XA), that is when problems arise with this NotSerializable exception. I do know that the 3.x series only supports local transaction, but my overall point is that I just don't understand why a distributed transaction has not been a "native" feature of JBoss from the beginning being that it seems to me that it would be fundamental to n-tier designs. I presume there is a good reason for this. I just don't know/see what that reason would be. the only reason is that no one has previously written a distributed tx manager. I wrote the basic stuff we need in jboss 4, it should even work with the trunk invoker. Can you describe this "basic stuff" a little? I am considering implementing distributed tx. I looked into the code and I have some implementation ideas in mind, but I would like to know what is your plan here and I definitely do not want to repeat something that is already done. -- Igor Fedorenko Think smart. Think automated. Think Dynamics. www.thinkdynamics.com --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-657311 ] Resource Contention - Leaking Handles
Bugs item #657311, was opened at 2002-12-21 16:16 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=657311&group_id=22866 Category: None Group: None >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Dennis Cartier (dcartier) Assigned to: Nobody/Anonymous (nobody) Summary: Resource Contention - Leaking Handles Initial Comment: I have noticed some odd files appearing in the /tmp directory of my Linux JBoss machines. They are all named ddtbX.tmp Eg. ddtb48340.tmp ddtb48349.tmp ddtb48358.tmp ddtb48367.tmp ... When I check the output of lsof, it appears that close to all of the java processes running each have every one of the ddtb files open. This quickly adds up to thousands of open files. Each one of the ddtb files are 0 bytes long, so there is not even anything in them. I have tried deleting them while JBoss reamins running, no ill effects were observed, but lsof still shows the java process having them open even after they are gone. It appears to be only under load that the files are created. Idle servers do not seem to generate these files. I am just worried that over a period of time, this will cause the JBoss servers to eventually fail. Can anyone shed any light on this? Particulars: JBoss 3.0.4 Tomcat 4.1.12 Debian Stable Linux Kernel 2.4.19 Sun 1.4.0_02 JVM -- >Comment By: Dennis Cartier (dcartier) Date: 2003-01-19 11:54 Message: Logged In: YES user_id=673615 I found the problem in my code. Dangling JDBC objects are responsible. Case Closed. Please see: http://www.jboss.org/forums/thread.jsp?nav=false&forum=61&thread=24687&start=0&msRange=15 -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=657311&group_id=22866 --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-669043 ] JBoss 3.0.5 throws exceptions on startup with IBM JDK 1.4.0
Bugs item #669043, was opened at 2003-01-16 08:28 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=669043&group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Stefan Kuehnel (skuehnel) Assigned to: Nobody/Anonymous (nobody) Summary: JBoss 3.0.5 throws exceptions on startup with IBM JDK 1.4.0 Initial Comment: Not sure if IBM JVM 1.4.0 is supported, but I understand JBOss used to work with 1.3. Just tried to test the new 3.0.5 with IBM JVM 1.4.0 and it failed with the exceptions below. System info: 14:03:21,498 INFO [ServerInfo] Java version: 1.4.0,IBM Corporation 14:03:21,504 INFO [ServerInfo] Java VM: Classic VM 1.4.0,IBM Corporation 14:03:21,510 INFO [ServerInfo] OS-System: Linux 2.4.18-17.7.x,x86 Exceptions: 14:03:27,372 ERROR [MainDeployer] could not create deployment: file:/usr/local/jboss-3.0.5_tomcat-4.1.18/server/frontis/conf/jboss-service.xml org.jboss.deployment.DeploymentException: instantiating org.jboss.varia.property.PropertyEditorManagerService failed: java.lang.NoClassDefFoundError: org/jboss/net/protocol/jar/Handler (wrong name: org/jboss/varia/property/PropertyEditorManagerService); - nested throwable: (RuntimeErrorException: instantiating org.jboss.varia.property.PropertyEditorManagerService failed: java.lang.NoClassDefFoundError: org/jboss/net/protocol/jar/Handler (wrong name: org/jboss/varia/property/PropertyEditorManagerService) Cause: java.lang.NoClassDefFoundError: org/jboss/net/protocol/jar/Handler (wrong name: org/jboss/varia/property/PropertyEditorManagerService)) at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:153) at org.jboss.system.ServiceController.install(ServiceController.java:231) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:40) at java.lang.reflect.Method.invoke(Method.java:335) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy2.install(Unknown Source) at org.jboss.deployment.SARDeployer.create(SARDeployer.java:189) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:766) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:626) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:591) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:575) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:40) at java.lang.reflect.Method.invoke(Method.java:335) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:325) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:222) at org.jboss.Main.boot(Main.java:148) at org.jboss.Main$1.run(Main.java:381) at java.lang.Thread.run(Thread.java:566) Caused by: RuntimeErrorException: instantiating org.jboss.varia.property.PropertyEditorManagerService failed: java.lang.NoClassDefFoundError: org/jboss/net/protocol/jar/Handler (wrong name: org/jboss/varia/property/PropertyEditorManagerService) Cause: java.lang.NoClassDefFoundError: org/jboss/net/protocol/jar/Handler (wrong name: org/jboss/varia/property/PropertyEditorManagerService) at org.jboss.mx.server.MBeanServerImpl.handleInstantiateExceptions(MBeanServerImpl.java:883) at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:816) at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:266) at org.jboss.mx.server.MBeanServerImpl.createMBean(MBeanServerImpl.java:293) at org.jboss.system.ServiceCreator.install(ServiceCreator.java:86) at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:165) at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:128) ... 25 more 14:03:27,499 ERROR [Server] start failed org.jboss.deployment.DeploymentException: instantiating org.jboss.varia.property.PropertyEditorManagerService failed: java.lang.NoClassDefFoundError: org/jboss/net/protocol/jar/Handler (wrong name: org/jboss/varia/property/PropertyEditorManagerService); - nested throwable: (RuntimeErrorException: instantiating org.jboss.varia.property.Prop
[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 == == Finished 'most' in module 'common'. == == _module-common-most: [mkdir] Created dir: /home/jboss/jbossci/jboss-head/build/output/testbuild/lib [copy] Copying 1 file to /home/jboss/jbossci/jboss-head/build/output/testbuild/lib [mkdir] Created dir: /home/jboss/jbossci/jboss-head/build/output/testbuild/client [copy] Copying 1 file to /home/jboss/jbossci/jboss-head/build/output/testbuild/client [copy] Copying 5 files to /home/jboss/jbossci/jboss-head/build/output/testbuild/lib == == == Executing 'most' in module 'jmx'... == == configure-modules: Overriding previous definition of reference to jboss.naming.classpath compile-mbean-sources: [mkdir] Created dir: /home/jboss/jbossci/jboss-head/jmx/output/gen/classes _default:compile-classes: [mkdir] Created dir: /home/jboss/jbossci/jboss-head/jmx/output/classes [depend] Deleted 0 out of date files in 0 seconds [javac] Compiling 656 source files to /home/jboss/jbossci/jboss-head/jmx/output/classes /home/jboss/jbossci/jboss-head/jmx/src/main/javax/management/MBeanServerInvocationHandler.java:280: cannot resolve symbol symbol : method getCause () location: class javax.management.MBeanException throw exception.getCause(); ^ /home/jboss/jbossci/jboss-head/jmx/src/main/javax/management/MBeanServerInvocationHandler.java:305: cannot resolve symbol symbol : method getCause () location: class javax.management.MBeanException throw exception.getCause(); ^ /home/jboss/jbossci/jboss-head/jmx/src/main/javax/management/MBeanServerInvocationHandler.java:331: cannot resolve symbol symbol : method getCause () location: class javax.management.MBeanException throw exception.getCause(); ^ 3 errors BUILD FAILED file:/home/jboss/jbossci/jboss-head/jmx/../tools/etc/buildfragments/targets.ent:45: Compile failed; see the compiler error output for details. Total time: 28 seconds --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-669161 ] Jetty for 3.0.5 release giving null Session IDs
Bugs item #669161, was opened at 2003-01-16 16:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=669161&group_id=22866 Category: JBossWeb Group: v3.0 Rabbit Hole Status: Closed Resolution: None Priority: 5 Submitted By: J. Rhett Aultman (cuplan) Assigned to: Nobody/Anonymous (nobody) Summary: Jetty for 3.0.5 release giving null Session IDs Initial Comment: We have recently started using JBoss 3.0.5 and have noticed that the version of Jetty bundled with this release is giving out null session ids as a default behavior. Please advise. -- Comment By: Greg Wilkins (gregwilkins) Date: 2003-01-19 19:48 Message: Logged In: YES user_id=44062 This was actually a feature request as part of support for single sign on. If a session ID is offered - but that session does not exist, then it is used as the new session ID. So long as you use the session status to check if the session is new or not, this should not give you a problem. What is the scenario where it is giving you problems? Eitherway, I'll probably make this behaviour optional in the next release. -- Comment By: J. Rhett Aultman (cuplan) Date: 2003-01-17 19:37 Message: Logged In: YES user_id=132788 It should be noted that the suggested version of Jetty continued to give us session problems. In that particular case, Jetty was improperly assigning session IDs that should have been invalidated. Just a heads-up when selecting a version of Jetty to replace the default one with. -- Comment By: J. Rhett Aultman (cuplan) Date: 2003-01-16 18:06 Message: Logged In: YES user_id=132788 Many thanks for the fast and thorough response! -- Comment By: Greg Wilkins (gregwilkins) Date: 2003-01-16 17:37 Message: Logged In: YES user_id=44062 This bug was introduced with some session optimizations. It is already fixed in CVS head of Jetty, JBoss 3.0 and JBoss 3.2 A replacement jbossweb.sar will be available shortly. Alternatly you can grab the jetty 4.2.5 jar and drop that into your current jbossweb.sar. Details of how to do that are in the jetty/jboss FAQ: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/contrib/jetty/FAQ?rev=HEAD&content-type=text/vnd.viewcvs-markup -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=669161&group_id=22866 --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss(Branch_3_0) Testsuite Results: 19-January-2003
JBoss daily test results SUMMARY Number of tests run: 1010 Successful tests: 1006 Errors:2 Failures: 2 [time of test: 2003-01-19.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.3] See http://users.jboss.org/~starksm/Branch_3_0/2003-01-19.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: BaseConnectionManagerUnitTestCase Test:testFillToMin(org.jboss.test.jca.test.BaseConnectionManagerUnitTestCase) Type:failure Exception: junit.framework.AssertionFailedError Message: Wrong number of connections counted: 1 - Suite: LocalWrapperCleanupUnitTestCase Test: testAutoCommitOffInRemoteUserTx(org.jboss.test.jca.test.LocalWrapperCleanupUnitTestCase) Type:error Exception: java.rmi.ServerException Message: RemoteException occurred in server thread; nested exception is: java.rmi.ServerException: EJBException:; nested exception is: javax.ejb.EJBException: Row committed, autocommit still on! - 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: 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: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Patches-670835 ] Adds Xml based Invocation Layer to JBossMQ
Patches item #670835, was opened at 2003-01-19 17:29 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376687&aid=670835&group_id=22866 Category: JBossMQ Group: CVS HEAD Status: Open Resolution: None Priority: 5 Submitted By: John Fawcett (fawce) Assigned to: Nobody/Anonymous (nobody) Summary: Adds Xml based Invocation Layer to JBossMQ Initial Comment: Adds xml based Invocation Layer to Jbossmq Please let me know if I can be of any help with integrating the XIL into jboss-head. Details on the structure of the XIL protocol, the current C# client impl, and testsuite results are available at: csil.sourceforge.net - new packages in messaging module: org.jboss.mq.il.xil org.jboss.mq.il.xil.encoding - new packages in testsuite module (primarily ports of org.jboss.test.jbossmq, to run over xil): org.jboss.test.tamale.* For some reason, diff is corrupting the thirdparty jar nanoxml.jar, so I have excluded it from the patch and attached it seperately. To apply patch from directory above jboss-head: mkdir ./jboss-head/thirdparty/nanoxml-nanoxml mkdir ./jboss-head/thirdparty/nanoxml-nanoxml/lib (copy the attached nanoxml.jar into the above directory) patch -u -p 4 -i xil.patch affected files: build/build.xml messaging/build.xml messaging/src/etc/server/default/deploy/jbossmq- service.xml messaging/src/etc/server/cluster/deploy/jbossmq- service.xml messaging/src/main/org/jboss/mq/AcknowledgementReq uest.java messaging/src/main/org/jboss/mq/AuthenticationReques t.java messaging/src/main/org/jboss/mq/BrowseRequest.java messaging/src/main/org/jboss/mq/BrowseResponse.java messaging/src/main/org/jboss/mq/ClientID.java messaging/src/main/org/jboss/mq/ClientReceiveRequest. java messaging/src/main/org/jboss/mq/Connection.java messaging/src/main/org/jboss/mq/ConnectionToken.java messaging/src/main/org/jboss/mq/DurableSubscriptionID .java messaging/src/main/org/jboss/mq/GenericConnectionFa ctory.java messaging/src/main/org/jboss/mq/MessagePool.java messaging/src/main/org/jboss/mq/Ping.java messaging/src/main/org/jboss/mq/ReceiveRequest.java messaging/src/main/org/jboss/mq/SessionID.java messaging/src/main/org/jboss/mq/SpyBytesMessage.jav a messaging/src/main/org/jboss/mq/SpyConnectionMetaD ata.java messaging/src/main/org/jboss/mq/SpyConsumer.java messaging/src/main/org/jboss/mq/SpyDestination.java messaging/src/main/org/jboss/mq/SpyEncapsulatedMes sage.java messaging/src/main/org/jboss/mq/SpyJMSException.jav a messaging/src/main/org/jboss/mq/SpyMapMessage.java messaging/src/main/org/jboss/mq/SpyMessage.java messaging/src/main/org/jboss/mq/SpyMessageConsum er.java messaging/src/main/org/jboss/mq/SpyMessageProducer .java messaging/src/main/org/jboss/mq/SpyObjectMessage.ja va messaging/src/main/org/jboss/mq/SpyQueue.java messaging/src/main/org/jboss/mq/SpyQueueBrowser.jav a messaging/src/main/org/jboss/mq/SpyQueueReceiver.jav a messaging/src/main/org/jboss/mq/SpyQueueSender.java messaging/src/main/org/jboss/mq/SpySession.java messaging/src/main/org/jboss/mq/SpyStreamMessage.j ava messaging/src/main/org/jboss/mq/SpyTemporaryQueue.j ava messaging/src/main/org/jboss/mq/SpyTemporaryTopic.ja va messaging/src/main/org/jboss/mq/SpyTextMessage.java messaging/src/main/org/jboss/mq/SpyTopic.java messaging/src/main/org/jboss/mq/SpyTopicPublisher.jav a messaging/src/main/org/jboss/mq/SpyTopicSubscriber.ja va messaging/src/main/org/jboss/mq/SpyXAConnection.java messaging/src/main/org/jboss/mq/SpyXAConnectionFact ory.java messaging/src/main/org/jboss/mq/SpyXAResource.java messaging/src/main/org/jboss/mq/SpyXAResourceMana ger.java messaging/src/main/org/jboss/mq/Subscription.java messaging/src/main/org/jboss/mq/SubscriptionID.java messaging/src/main/org/jboss/mq/TransactionRequest.ja va messaging/src/main/org/jboss/mq/il/xil/XILClientIL.java messaging/src/main/org/jboss/mq/il/xil/XILClientILService .java messaging/src/main/org/jboss/mq/il/xil/XILReturnStatus.j ava messaging/src/main/org/jboss/mq/il/xil/XILServerIL.java messaging/src/main/org/jboss/mq/il/xil/XILServerILFactor y.java messaging/src/main/org/jboss/mq/il/xil/XILServerILServic e.java messaging/src/main/org/jboss/mq/il/xil/encoding/Acknow ledgementRequestXml.java messaging/src/main/org/jboss/mq/il/xil/encoding/Authent icationRequestXml.java messaging/src/main/org/jboss/mq/il/xil/encoding/Browse RequestXml.java messaging/src/main/org/jboss/mq/il/xil/encoding/Browse ResponseXml.java messaging/src/main/org/jboss/mq/il/xil/encoding/ClientID Xml.java messaging/src/main/org/jboss/mq/il/xil/encoding/ClientR eceiveRequestXml.java messaging/src/main/org/jboss/mq/il/xil/encoding/Connec tionTokenXml.java messaging/src/main/org/jboss/mq/il/xil/encoding/Destina tionXml.java messaging/src/main/org/jboss/mq/il/xil/encoding/Durable SubscriptionIDXml.java messaging/src/main/org/jboss/mq/il/xil/encoding/Enabled Xml.java messaging/src/main/org/jboss/mq/il/xil/encoding/Encode r.java messaging/src/main/org/jboss/m
[JBoss-dev] [ jboss-Bugs-668291 ] Jasper in release 3.0.5 is
Bugs item #668291, was opened at 2003-01-15 13:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=668291&group_id=22866 Category: JBossWeb Group: v3.0 Rabbit Hole >Status: Pending Resolution: None Priority: 5 Submitted By: Brian Bannister (beoch) Assigned to: Jules Gosnell (jules_gosnell) Summary: Jasper in release 3.0.5 is Initial Comment: Windows 2000 JDK 1.4.1_01 JBoss 3.0.5 I'm getting JSP compile errors that do not occur in JBoss 3.0.4. Jasper complains that it can't find a class that is definately in the deployed war. Using the same ear on JBoss 3.0.4 I get no problems. The traces from JBoss-3.0.5 and JBoss-3.0.4 are attached, as well as the war manifest showing the class that Jasper can't find. The exception thrown is: Time: 13:42:55 Priority: WARN Thread: PoolThread- 4 NDC: null Category: org.jboss.jbossweb Location: org.jboss.logging.Logger.warn(Logger.java:167) Message: WARNING: Exception for http://192.223.0.59:8080/itochu/newsticker/view/45/dyna micMedia/x-news-ticker.jsp org.apache.jasper.JasperException: Unable to compile class for JSPNote: sun.tools.javac.Main has been deprecated. An error occurred at line: 2 in the jsp file: /45/dynamicMedia/x-news-ticker.jsp Generated servlet error: C:\DOCUME~1\brianb\LOCALS~1 \Temp\Jetty_0_0_0_0_8080__itochu_newsticker\45 \dynamicMedia\x_0002dnews_0002dticker$jsp.java:65: Class com.activesky.itochu.newsticker.view.NewsTickerView not found. com.activesky.itochu.newsticker.view.NewsTickerView viewParameter = null; ^ An error occurred at line: 2 in the jsp file: /45/dynamicMedia/x-news-ticker.jsp Generated servlet error: C:\DOCUME~1\brianb\LOCALS~1 \Temp\Jetty_0_0_0_0_8080__itochu_newsticker\45 \dynamicMedia\x_0002dnews_0002dticker$jsp.java:68: Class com.activesky.itochu.newsticker.view.NewsTickerView not found. viewParameter= (com.activesky.itochu.newsticker.view.NewsTickerView) ^ An error occurred at line: 2 in the jsp file: /45/dynamicMedia/x-news-ticker.jsp Generated servlet error: C:\DOCUME~1\brianb\LOCALS~1 \Temp\Jetty_0_0_0_0_8080__itochu_newsticker\45 \dynamicMedia\x_0002dnews_0002dticker$jsp.java:73: Class com.activesky.itochu.newsticker.view.NewsTickerView not found. viewParameter = (com.activesky.itochu.newsticker.view.NewsTickerView) java.beans.Beans.instantiate(this.getClass ().getClassLoader (), "com.activesky.itochu.newsticker.view.NewsTickerVie w"); ^ 3 errors, 1 warning at org.apache.jasper.compiler.Compiler.compile (Compiler.java:289) at org.apache.jasper.servlet.JspServlet.loadJSP (JspServlet.java:548) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.l oadIfNecessary(JspServlet.java:176) at org.apache.jasper.servlet.JspServlet$JspServletWrapper. service(JspServlet.java:188) at org.apache.jasper.servlet.JspServlet.serviceJspFile (JspServlet.java:381) at org.apache.jasper.servlet.JspServlet.service (JspServlet.java:473) at javax.servlet.http.HttpServlet.service (HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle (ServletHolder.java:360) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatc h(WebApplicationHandler.java:280) at org.mortbay.jetty.servlet.Dispatcher.dispatch (Dispatcher.java:194) at org.mortbay.jetty.servlet.Dispatcher.forward (Dispatcher.java:129) at com.activesky.servlet.FrontController.doGet (FrontController.java:46) at javax.servlet.http.HttpServlet.service (HttpServlet.java:740) at javax.servlet.http.HttpServlet.service (HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle (ServletHolder.java:360) at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.d oFilter(WebApplicationHandler.java:328) at com.activesky.aserver.mbroker.MediaBrokerFilter.doFilte r(MediaBrokerFilter.java:138) at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.d oFilter(WebApplicationHandler.java:320) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatc h(WebApplicationHandler.java:272) at org.mortbay.jetty.servlet.ServletHandler.handle (ServletHandler.java:553) at org.mortbay.http.HttpContext.handle (HttpContext.java:1656) at org.mortbay.jetty.servlet.WebApplicationContext.handle (WebApplicationContext.java:549) at org.mortbay.http.HttpContext.handle (HttpContext.java:1606) at org.mortbay.http.HttpServer.service (HttpServer.java:862) at org.jboss.jetty.Jetty.service(Jetty.java:497) at org.mortbay.http.HttpConnection.service (HttpConnection.java:752) at org.mortbay.http.HttpConnection.handleNext (HttpConnection.java:916) at org.mortbay.http.HttpConnection.hand
[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 output: [mkdir] Created dir: /home/jboss/jbossci/jboss-head/aop/output/lib [jar] Building jar: /home/jboss/jbossci/jboss-head/aop/output/lib/jboss-aop.jar == == == Finished 'most' in module 'aop'. == == _module-aop-most: [copy] Copying 1 file to /home/jboss/jbossci/jboss-head/build/output/testbuild/lib [copy] Copying 1 file to /home/jboss/jbossci/jboss-head/build/output/testbuild/lib == == == Executing 'most' in module 'cache'... == == configure-modules: Overriding previous definition of reference to jboss.naming.classpath compile-mbean-sources: [mkdir] Created dir: /home/jboss/jbossci/jboss-head/cache/output/gen/classes Running INFO: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. However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: org.jboss.cache.CacheImplMBean --> ServiceMBean qualified to ServiceMBean org.jboss.cache.EvictionPolicy --> Service qualified to Service _default:compile-classes: [mkdir] Created dir: /home/jboss/jbossci/jboss-head/cache/output/classes [depend] Deleted 0 out of date files in 0 seconds [javac] Compiling 18 source files to /home/jboss/jbossci/jboss-head/cache/output/classes /home/jboss/jbossci/jboss-head/cache/src/main/org/jboss/cache/CacheException.java:38: cannot resolve symbol symbol : constructor Exception (java.lang.String,java.lang.Throwable) location: class java.lang.Exception super(msg, cause); ^ 1 error BUILD FAILED file:/home/jboss/jbossci/jboss-head/cache/../tools/etc/buildfragments/targets.ent:45: Compile failed; see the compiler error output for details. Total time: 53 seconds --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ 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 output: [mkdir] Created dir: /home/jboss/jbossci/jboss-head/aop/output/lib [jar] Building jar: /home/jboss/jbossci/jboss-head/aop/output/lib/jboss-aop.jar == == == Finished 'most' in module 'aop'. == == _module-aop-most: [copy] Copying 1 file to /home/jboss/jbossci/jboss-head/build/output/testbuild/lib [copy] Copying 1 file to /home/jboss/jbossci/jboss-head/build/output/testbuild/lib == == == Executing 'most' in module 'cache'... == == configure-modules: Overriding previous definition of reference to jboss.naming.classpath compile-mbean-sources: [mkdir] Created dir: /home/jboss/jbossci/jboss-head/cache/output/gen/classes Running INFO: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. However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: org.jboss.cache.CacheImplMBean --> ServiceMBean qualified to ServiceMBean org.jboss.cache.EvictionPolicy --> Service qualified to Service _default:compile-classes: [mkdir] Created dir: /home/jboss/jbossci/jboss-head/cache/output/classes [depend] Deleted 0 out of date files in 0 seconds [javac] Compiling 18 source files to /home/jboss/jbossci/jboss-head/cache/output/classes /home/jboss/jbossci/jboss-head/cache/src/main/org/jboss/cache/CacheException.java:38: cannot resolve symbol symbol : constructor Exception (java.lang.String,java.lang.Throwable) location: class java.lang.Exception super(msg, cause); ^ 1 error BUILD FAILED file:/home/jboss/jbossci/jboss-head/cache/../tools/etc/buildfragments/targets.ent:45: Compile failed; see the compiler error output for details. Total time: 52 seconds --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
