[JBoss-dev] The fix for bug #462253 is not acceptable
The fix for bug[ #462253 ] TextMessage fails for 64k content is not acceptable for 3 reasons: 1. It breaks backward compatibility with previous versions but does not change the SpyTextMessage.serialVersionUID value. Using the 2.4.1 jbossmq jars produces the following exceptions when run with the mdb unit test against a server using the latest 2.4 branch jbossmq jars: [OILServerILService] Client request resulted in a server exception: java.lang.NegativeArraySizeException at java.lang.StringBuffer.init(StringBuffer.java:116) at org.jboss.mq.SpyTextMessage.readExternal(SpyTextMessage.java:76) at org.jboss.mq.SpyMessage.readMessage(SpyMessage.java:589) at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService.java:219) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService.java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService.java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService.java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService.java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService.java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService.java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService.java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService.java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService.java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService.java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService.java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService.java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService.java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService.java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService.java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService.java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService.java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client
[JBoss-dev] CVS update: jbossmq/src/main/org/jboss/mq SpyTextMessage.java
User: starksm
Date: 01/09/30 23:31:58
Modified:src/main/org/jboss/mq Tag: Branch_2_4 SpyTextMessage.java
Log:
Undo the hacky fix for bug 462253
Revision ChangesPath
No revision
No revision
1.2.2.3 +4 -39 jbossmq/src/main/org/jboss/mq/SpyTextMessage.java
Index: SpyTextMessage.java
===
RCS file: /cvsroot/jboss/jbossmq/src/main/org/jboss/mq/SpyTextMessage.java,v
retrieving revision 1.2.2.2
retrieving revision 1.2.2.3
diff -u -r1.2.2.2 -r1.2.2.3
--- SpyTextMessage.java 2001/09/18 21:02:38 1.2.2.2
+++ SpyTextMessage.java 2001/10/01 06:31:58 1.2.2.3
@@ -7,7 +7,6 @@
package org.jboss.mq;
import java.io.*;
-import java.util.ArrayList;
import javax.jms.JMSException;
import javax.jms.MessageNotWriteableException;
@@ -18,7 +17,7 @@
*
* @author Norbert Lataille ([EMAIL PROTECTED])
* @createdAugust 16, 2001
- * @version$Revision: 1.2.2.2 $
+ * @version$Revision: 1.2.2.3 $
*/
public class SpyTextMessage
extends SpyMessage
@@ -29,8 +28,7 @@
String content = null;
private final static long serialVersionUID = 235726945332013953L;
- private final static int chunkSize = 16384;
-
+
// Public
public void setText( String string )
@@ -67,17 +65,7 @@
if ( type == NULL ) {
content = null;
} else {
- // apply workaround for string 64K bug in jdk's 1.3.*
-
- // Read the no. of chunks this message is split into, allocate
- // a StringBuffer that can hold all chunks, read the chunks
- // into the buffer and set 'content' accordingly
- int chunksToRead = in.readInt();
- StringBuffer sb = new StringBuffer(chunkSize * chunksToRead);
- for (int i = 0; i chunksToRead; i++) {
-sb.append( in.readUTF() );
- }
- content = sb.toString();
+ content = in.readUTF();
}
}
@@ -87,31 +75,8 @@
if ( content == null ) {
out.writeByte( NULL );
} else {
- // apply workaround for string 64K bug in jdk's 1.3.*
-
- // Split content into chunks of size 'chunkSize' and assemble
- // the pieces into a Vector ...
- ArrayList v = new ArrayList();
- int contentLength = content.length();
-
- while (contentLength 0) {
-int beginCopy = (v.size()) * chunkSize;
-int endCopy = contentLength = chunkSize ?
- beginCopy + contentLength : beginCopy + chunkSize;
-
-String theChunk = content.substring(beginCopy, endCopy);
-v.add(theChunk);
-
-contentLength -= chunkSize;
- }
-
- // Write out the type (OBJECT), the no. of chunks and finally
- // all chunks that have been assembled previously
out.writeByte( OBJECT );
- out.writeInt(v.size());
- for (int i = 0; i v.size(); i++) {
-out.writeUTF( (String)v.get(i) );
- }
+ out.writeUTF( content );
}
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
AW: [JBoss-dev] RH and -classic
It happens with 3.0.0alpha on Win2000, SUN classic VM, in starting the Jetty service: JBOSS_CLASSPATH=;run.jar [GPA] Microkernel ClassLoaders and Libraries initialized Libraries adding URLClassLoader -425250198 key URL file:/J:/jboss/jboss/build/ou tput/jboss-3.0.0alpha//conf/default/ Libraries adding URLClassLoader -1579336320 key URL file:/J:/jboss/jboss/build/o utput/jboss-3.0.0alpha//lib/ext/log4j.jar Libraries adding URLClassLoader 1538876019 key URL file:/J:/jboss/jboss/build/ou tput/jboss-3.0.0alpha//lib/ext/jboss-spine.jar Looking for the docuemnt I am ok, go figure [root] Started Log4jService, config=file:/J:/jboss/jboss/build/output/jboss-3.0. 0alpha//conf/default/log4j.properties [GPA] General Purpose Architecture [GPA] [GPA] Java version: 1.3.0,Sun Microsystems Inc. [GPA] Java VM: Classic VM 1.3.0-C,Sun Microsystems Inc. [GPA] OS-System: Windows 2000 5.0,x86 [GPA] JBoss Version : 3.0.0alpha(200109281232) [GPA] localDir : J:\jboss\jboss\build\output\jboss-3.0.0alpha [GPA] installationURL : file:/J:/jboss/jboss/build/output/jboss-3.0.0alpha/\ [GPA] configuration : file:/J:/jboss/jboss/build/output/jboss-3.0.0alpha/\conf\d efault\ [GPA] libraries : file:/J:/jboss/jboss/build/output/jboss-3.0.0alpha/\lib\ext\ [GPA] Oh, and remember we love you ... ... snip, snip ... [Default] About to create the beanJBOSS-SYSTEM:service=Jetty [Jetty] connected JBoss and Jetty Log models [Default] Created the beanJBOSS-SYSTEM:service=Jetty [Jetty] set JettyHome to dummy [Jetty] set Configuration to ../conf/default/jetty.xml [Jetty] set WebDefault to ../conf/default/webdefault.xml [Jetty] set UnpackWars to true [Jetty] set PublishMBeans to true [JettyService] Initializing [Jetty] loaded properties from: jetty.properties [ServiceController] java.lang.ClassCircularityError: org/mortbay/util/JarFileRes ource [JettyService] Starting [JettyService] Stopped java.lang.NullPointerException at org.jboss.jetty.JettyService.startService(JettyService.java:214) -Ursprüngliche Nachricht- Von: Jason Dillon [mailto:[EMAIL PROTECTED]] Gesendet: Freitag, 28. September 2001 21:33 An: Jboss-Development (E-Mail) Betreff: Re: [JBoss-dev] RH and -classic ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosspool/src/build build.xml
User: starksm
Date: 01/10/01 00:07:39
Modified:src/build Tag: Branch_2_4 build.xml
Log:
Add jboss.dist location
Revision ChangesPath
No revision
No revision
1.2.2.3 +10 -0 jbosspool/src/build/Attic/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/jbosspool/src/build/Attic/build.xml,v
retrieving revision 1.2.2.2
retrieving revision 1.2.2.3
diff -u -r1.2.2.2 -r1.2.2.3
--- build.xml 2001/09/09 00:37:27 1.2.2.2
+++ build.xml 2001/10/01 07:07:38 1.2.2.3
@@ -5,6 +5,16 @@
!-- == --
project name=JBossPool default=jar basedir=../..
+!-- The location of the JBoss server dist tree. This is
+ needed for compiling JBossCX code sinc there are dependencies
+ on org.jboss.* classes. The default assumes the jbosscx and
+ jboss cvs modules have the same parent directory.
+--
+ property name=jboss.home value=../jboss /
+ property name=jboss.dist value=${jboss.home}/dist /
+ property name=jboss.client value=${jboss.dist}/client /
+ property name=jboss.lib value=${jboss.dist}/lib /
+ property name=jboss.lib.ext value=${jboss.dist}/lib/ext /
property name=Name value=JBossPool/
property name=name value=jbosspool/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: contrib/tomcat/src/build build.xml
User: starksm
Date: 01/10/01 00:08:42
Modified:tomcat/src/build Tag: Branch_2_4 build.xml
Log:
Remove bundle dir in clean target
Revision ChangesPath
No revision
No revision
1.15.2.6 +2 -1 contrib/tomcat/src/build/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/contrib/tomcat/src/build/build.xml,v
retrieving revision 1.15.2.5
retrieving revision 1.15.2.6
diff -u -r1.15.2.5 -r1.15.2.6
--- build.xml 2001/10/01 04:11:57 1.15.2.5
+++ build.xml 2001/10/01 07:08:42 1.15.2.6
@@ -1,5 +1,5 @@
?xml version=1.0 encoding=UTF-8 ?
-!-- $Id: build.xml,v 1.15.2.5 2001/10/01 04:11:57 starksm Exp $ --
+!-- $Id: build.xml,v 1.15.2.6 2001/10/01 07:08:42 starksm Exp $ --
!-- An Ant build file for the tomcat-service jar and the
JBoss/Tomcat bundle. The buildfile requires a JBoss dist
@@ -208,6 +208,7 @@
!-- === --
target name=clean
delete dir=${build.dir}/
+delete dir=${bundle.dir}/
/target
/project
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: contrib/catalina/src/build build.xml
User: starksm
Date: 01/10/01 00:09:32
Modified:catalina/src/build build.xml
Log:
Delete the bundle dir in the clean target
Revision ChangesPath
1.5 +2 -1 contrib/catalina/src/build/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/contrib/catalina/src/build/build.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- build.xml 2001/09/27 01:55:45 1.4
+++ build.xml 2001/10/01 07:09:32 1.5
@@ -1,5 +1,5 @@
?xml version=1.0 encoding=UTF-8 ?
-!-- $Id: build.xml,v 1.4 2001/09/27 01:55:45 starksm Exp $ --
+!-- $Id: build.xml,v 1.5 2001/10/01 07:09:32 starksm Exp $ --
!-- An Ant build file for the catalina-service jar and the
JBoss/Tomcat bundle. The buildfile requires a JBoss dist
@@ -151,6 +151,7 @@
!-- === --
target name=clean
delete dir=${build.dir}/
+delete dir=${bundle.dir}/
/target
/project
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: manual/src/xdocs jbossintro.xml
User: gropi Date: 01/10/01 00:21:50 Modified:src/xdocs jbossintro.xml Log: Ossie J. H. Moore recommended to reword the sentence to make sense. Revision ChangesPath 1.2 +1 -1 manual/src/xdocs/jbossintro.xml Index: jbossintro.xml === RCS file: /cvsroot/jboss/manual/src/xdocs/jbossintro.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- jbossintro.xml2001/08/29 09:19:36 1.1 +++ jbossintro.xml2001/10/01 07:21:50 1.2 @@ -659,7 +659,7 @@ InitialContext jndiContext = new InitialContext(); System.out.println(Got context);/programlisting /para - paraThe jndi.properties file that we will used is that located in the examples/resources/jndi.properties of the + paraThe jndi.properties file we have to use is located in the examples/resources/jndi.properties of the documentation examples distribution. Its contents are:programlistingjava.naming.factory.initial=org.jnp.interfaces.NamingContextFactory java.naming.provider.url=jnp://localhost:1099 java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces/programlistingThis specifies the InitialContextFactory, provider url, and the packages of object factories ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: AW: [JBoss-dev] RH and -classic
I forgot what the question was... --jason On Mon, 1 Oct 2001, Jung , Dr. Christoph wrote: It happens with 3.0.0alpha on Win2000, SUN classic VM, in starting the Jetty service: JBOSS_CLASSPATH=;run.jar [GPA] Microkernel ClassLoaders and Libraries initialized Libraries adding URLClassLoader -425250198 key URL file:/J:/jboss/jboss/build/ou tput/jboss-3.0.0alpha//conf/default/ Libraries adding URLClassLoader -1579336320 key URL file:/J:/jboss/jboss/build/o utput/jboss-3.0.0alpha//lib/ext/log4j.jar Libraries adding URLClassLoader 1538876019 key URL file:/J:/jboss/jboss/build/ou tput/jboss-3.0.0alpha//lib/ext/jboss-spine.jar Looking for the docuemnt I am ok, go figure [root] Started Log4jService, config=file:/J:/jboss/jboss/build/output/jboss-3.0. 0alpha//conf/default/log4j.properties [GPA] General Purpose Architecture [GPA] [GPA] Java version: 1.3.0,Sun Microsystems Inc. [GPA] Java VM: Classic VM 1.3.0-C,Sun Microsystems Inc. [GPA] OS-System: Windows 2000 5.0,x86 [GPA] JBoss Version : 3.0.0alpha(200109281232) [GPA] localDir : J:\jboss\jboss\build\output\jboss-3.0.0alpha [GPA] installationURL : file:/J:/jboss/jboss/build/output/jboss-3.0.0alpha/\ [GPA] configuration : file:/J:/jboss/jboss/build/output/jboss-3.0.0alpha/\conf\d efault\ [GPA] libraries : file:/J:/jboss/jboss/build/output/jboss-3.0.0alpha/\lib\ext\ [GPA] Oh, and remember we love you ... ... snip, snip ... [Default] About to create the beanJBOSS-SYSTEM:service=Jetty [Jetty] connected JBoss and Jetty Log models [Default] Created the beanJBOSS-SYSTEM:service=Jetty [Jetty] set JettyHome to dummy [Jetty] set Configuration to ../conf/default/jetty.xml [Jetty] set WebDefault to ../conf/default/webdefault.xml [Jetty] set UnpackWars to true [Jetty] set PublishMBeans to true [JettyService] Initializing [Jetty] loaded properties from: jetty.properties [ServiceController] java.lang.ClassCircularityError: org/mortbay/util/JarFileRes ource [JettyService] Starting [JettyService] Stopped java.lang.NullPointerException at org.jboss.jetty.JettyService.startService(JettyService.java:214) -Ursprüngliche Nachricht- Von: Jason Dillon [mailto:[EMAIL PROTECTED]] Gesendet: Freitag, 28. September 2001 21:33 An: Jboss-Development (E-Mail) Betreff: Re: [JBoss-dev] RH and -classic ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/client jboss-j2ee.jar jbossmq-client.jar jbosssx-client.jar jnp-client.jar
User: starksm Date: 01/10/01 00:38:19 Modified:src/client Tag: Branch_2_4 jboss-j2ee.jar jbossmq-client.jar jbosssx-client.jar jnp-client.jar Log: Synch up the jars with the JBoss_2_4_2 builds of the jbosscx, jboss-j2ee, jbossmq, jbosspool, jbosssx, jnp modules Revision ChangesPath No revision No revision 1.3.4.2 +187 -192 jboss/src/client/Attic/jboss-j2ee.jar Binary file 1.6.4.5 +772 -754 jboss/src/client/Attic/jbossmq-client.jar Binary file 1.8.2.12 +79 -89jboss/src/client/Attic/jbosssx-client.jar Binary file 1.11.4.5 +63 -65jboss/src/client/Attic/jnp-client.jar Binary file ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/etc/deploy jbosspool-jdbc.rar
User: starksm Date: 01/10/01 00:38:19 Modified:src/etc/deploy Tag: Branch_2_4 jbosspool-jdbc.rar Log: Synch up the jars with the JBoss_2_4_2 builds of the jbosscx, jboss-j2ee, jbossmq, jbosspool, jbosssx, jnp modules Revision ChangesPath No revision No revision 1.1.4.1 +62 -64jboss/src/etc/deploy/Attic/jbosspool-jdbc.rar Binary file ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/lib jboss-j2ee.jar jboss-jaas.jar jboss-jdbc_ext.jar jbosscx.jar jbossmq.jar jbosspool.jar jbosssx.jar jnpserver.jar
User: starksm Date: 01/10/01 00:38:18 Modified:src/lib Tag: Branch_2_4 jboss-j2ee.jar jboss-jaas.jar jboss-jdbc_ext.jar jbosscx.jar jbossmq.jar jbosspool.jar jbosssx.jar jnpserver.jar Log: Synch up the jars with the JBoss_2_4_2 builds of the jbosscx, jboss-j2ee, jbossmq, jbosspool, jbosssx, jnp modules Revision ChangesPath No revision No revision 1.5.4.2 +187 -192 jboss/src/lib/Attic/jboss-j2ee.jar Binary file 1.11.2.13 +166 -173 jboss/src/lib/Attic/jboss-jaas.jar Binary file 1.2.4.2 +26 -22jboss/src/lib/Attic/jboss-jdbc_ext.jar Binary file 1.1.2.2 +133 -186 jboss/src/lib/Attic/jbosscx.jar Binary file 1.8.4.5 +1128 -jboss/src/lib/Attic/jbossmq.jar Binary file 1.1.4.2 +466 -408 jboss/src/lib/Attic/jbosspool.jar Binary file 1.11.2.13 +232 -240 jboss/src/lib/Attic/jbosssx.jar Binary file 1.13.4.5 +96 -102 jboss/src/lib/Attic/jnpserver.jar Binary file ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results
JBoss daily test results SUMMARY Number of tests run: 21 Successful tests: 15 Errors:6 Failures: 0 [time of test: 1 October 2001 9:9 GMT] [java.version: 1.3.1] [java.vendor: Blackdown Java-Linux Team] [java.vm.version: Blackdown-1.3.1-FCS] [java.vm.name: Classic VM] [java.vm.info: green threads, nojit] [os.name: Linux] [os.arch: i386] [os.version: 2.4.3-12] See http://lubega.com for full details 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 [details not shown - as this makes the mail too big to reach the sf mailing list] ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Patches-466763 ] remove misleading xdoclet tag
Patches item #466763, was opened at 2001-10-01 01:44 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376687aid=466763group_id=22866 Category: JBossServer Group: v2.5 Rabbit Hole (unstable) Status: Open Resolution: None Priority: 5 Submitted By: Neale Swinnerton (neales) Assigned to: Nobody/Anonymous (nobody) Summary: remove misleading xdoclet tag Initial Comment: Patch #465992 converted the jboss ejbdoclet usage to xdoclet. Part of this was to convert @ejb:remote-method tags to... @ejb:interface-method type=remote Dmitri Colebatch [EMAIL PROTECTED] pointed out on jboss-dev that the type=remote is optional. In fact the type=remote is an invalid attribute, it should be view-type=remote, which is optional. The method level view-type tag inherits from the class level one, which defaults to view-type=remote xdoclet is silently ignoring the current attribute. This could lead to confusion in the future. This patch removes the invalid and misleading type=remote attribute. Patch created with cvs diff -u ./admin/src/main/org/jboss/admin/beans/AdminServerBean.java ./admin/src/main/org/jboss/admin/beans/SystemMonitorBean.java ./server/src/main/org/jboss/jmx/adaptor/ejb/EJBAdaptorBean.java ejbdoclet.to.xdoclet.patch.2 -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376687aid=466763group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [PATCH] Log4j 1.2alpha compatibility upgrade
Hello,
The included patches allow Jboss (latest CVS-snapshot) to work with log4j 1.2alpa1,
xdoclet-related patches are also included. You can continue to use your own subclass
of Category although this is likely to cause problems if and when you decide to
support the LogManager architecture.
Let me know if you need further clarifications. Regards,
ps: JBoss is pretty awesome. Well done!
--
Ceki Gülcü - http://qos.ch
Index: server/src/main/org/jboss/logging/TracePriority.java
===
RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/logging/TracePriority.java,v
retrieving revision 1.1
diff -u -r1.1 TracePriority.java
--- server/src/main/org/jboss/logging/TracePriority.java2001/09/11 18:35:02
1.1
+++ server/src/main/org/jboss/logging/TracePriority.java2001/10/01 08:12:49
@@ -6,7 +6,7 @@
*/
package org.jboss.logging;
-import org.apache.log4j.Priority;
+import org.apache.log4j.Level;
/** Adds a trace priority that is below the standard log4j DEBUG priority.
This is a custom priority that is 100 below the Priority.DEBUG_INT and
@@ -19,11 +19,11 @@
@author [EMAIL PROTECTED]
@version $Revision: 1.1 $
*/
-public class TracePriority extends Priority
+public class TracePriority extends Level
{
// Constants -
/** The integer representation of the priority, (Priority.DEBUG_INT - 100) */
- public static final int TRACE_INT = Priority.DEBUG_INT - 100;
+ public static final int TRACE_INT = Level.DEBUG_INT - 100;
/** The TRACE priority object singleton */
public static final TracePriority TRACE = new TracePriority(TRACE_INT, TRACE);
@@ -34,27 +34,27 @@
fails, then this method returns the specified default.
@return the Priority object for name if one exists, defaultPriority otherwize.
*/
- public static Priority toPriority(String name, Priority defaultPriority)
+ public static Level toLevel(String name, Level defaultLevel)
{
if( name == null )
return TRACE;
- Priority p = TRACE;
+ Level p = TRACE;
if( name.charAt(0) != 'T' )
- p = Priority.toPriority(name, defaultPriority);
+ p = Level.toLevel(name, defaultLevel);
return p;
}
/** Convert an integer passed as argument to a priority. If the conversion
fails, then this method returns the specified default.
@return the Priority object for i if one exists, defaultPriority otherwize.
*/
- public static Priority toPriority(int i, Priority defaultPriority)
+ public static Level toLevel(int i, Level defaultLevel)
{
- Priority p;
+ Level p;
if( i == TRACE_INT )
p = TRACE;
else
- p = Priority.toPriority(i);
+ p = Level.toLevel(i);
return p;
}
Index: DocletUtil.java
===
RCS file: /cvsroot/xdoclet/xdoclet/core/src/xdoclet/util/DocletUtil.java,v
retrieving revision 1.5
diff -u -r1.5 DocletUtil.java
--- DocletUtil.java 2001/09/04 14:46:27 1.5
+++ DocletUtil.java 2001/10/01 06:47:44
@@ -5,6 +5,7 @@
import java.util.*;
import com.sun.javadoc.*;
import org.apache.log4j.Category;
+import org.apache.log4j.Logger;
/**
* @author Ara Abrahamian ([EMAIL PROTECTED])
@@ -186,9 +187,9 @@
* @param name Description of Parameter
* @returnThe Category value
*/
- protected static Category getCategory( Class clazz, String name )
+ protected static Logger getCategory( Class clazz, String name )
{
- Category cat = Category.getInstance( clazz.getName() + . + name );
+ Logger cat = Logger.getLogger( clazz.getName() + . + name );
return cat;
}
Index: server/src/main/org/jboss/logging/Logger.java
===
RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/logging/Logger.java,v
retrieving revision 1.13
diff -u -r1.13 Logger.java
--- server/src/main/org/jboss/logging/Logger.java 2001/09/11 18:35:02 1.13
+++ server/src/main/org/jboss/logging/Logger.java 2001/10/01 08:16:03
@@ -6,8 +6,9 @@
*/
package org.jboss.logging;
-import org.apache.log4j.Category;
-import org.apache.log4j.spi.CategoryFactory;
+//import org.apache.log4j.Logger;
+//import org.apache.log4j.spi.LoggerFactory;
+import org.apache.log4j.LogManager;
/** A custom log4j Category subclass that add a trace level priority.
* @see #isTraceEnabled
@@ -17,29 +18,29 @@
* @author [EMAIL PROTECTED]
* @version $Revision: 1.13 $
*/
-public class Logger extends Category
+public class Logger extends org.apache.log4j.Logger
{
// Constants -
// Attributes
- private static CategoryFactory factory = new
[JBoss-dev] CVS update: manual/src/xdocs jbossintro.xml
User: gropi Date: 01/10/01 01:57:09 Modified:src/xdocs jbossintro.xml Log: Some more comments on the JNDI service. Revision ChangesPath 1.3 +18 -14manual/src/xdocs/jbossintro.xml Index: jbossintro.xml === RCS file: /cvsroot/jboss/manual/src/xdocs/jbossintro.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- jbossintro.xml2001/10/01 07:21:50 1.2 +++ jbossintro.xml2001/10/01 08:57:09 1.3 @@ -12,6 +12,7 @@ firstnameTobias/firstname surnameFrech/surname /author +email[EMAIL PROTECTED]/email /para para author @@ -37,7 +38,7 @@ titleAbout JBoss/title paraJBoss is an implementation of the EJB 1.1 (and parts of 2.0) specification, that is, it is a server and container for Enterprise JavaBeans. In this it is similar to Sun's -'J2SDK Enterprise Edition' (J2EE), but JBoss the JBoss core server provides only an EJB server. +'J2SDK Enterprise Edition' (J2EE), but the JBoss core server provides only an EJB server. The JBoss core does not include a web container for servlets/JSP pages, although there are bundles available that include either Tomcat or Jetty. @@ -56,7 +57,7 @@ already loaded, JBoss automatically unloads it, then loads the new version. Contrast this with the rigmarole that other J2EE server makes us go through... JBoss is distributed under the LGPL, which means that it's free, even for commercial -work, and is likely to remain that way. You get no support, of course. /para +work, and the LGPL ensures that it remains that way. Id you need support, look at the JBoss website for the various forums. If you want to pay for the support then contact the ulink url = http://www.jboss.org/JBG/support.jsp;JBossGroup LLC/ulink./para paraThis chapter helps get you started using JBoss by describing step-by-step how a simple EJB can be created, deployed and tested on the JBoss server. /para @@ -76,8 +77,8 @@ titleInstalling Ant/title paraYou need Ant to compile and run the example presented in the JBoss documentation. Ant is the standard build tool used by most open source Java projects and is widely being used in commercial -settings as well. You need Ant version 1.3 or latter. You can download the 1.3 binaries for Ant from ulink url = http://jakarta.apache.org/builds/jakarta-ant/release/v1.3/bin/;HERE/ulink. If you have problems finding -binaries at that location try the Ant home page which is located ulink url = http://jakarta.apache.org/ant/index.html;HERE/ulink./para +settings as well. You need Ant version 1.3 or latter. You can download the 1.3 binaries for Ant from ulink url = http://jakarta.apache.org/builds/jakarta-ant/release/v1.3/bin/;this link to the Apache/Jakarta website/ulink. If you have problems finding +binaries at that location try the Ant home page which is located ulink url = http://jakarta.apache.org/ant/index.html;on the Apache/Jakarta website/ulink./para paraOnce you have the Ant distribution unarchive it to create a jakarta-ant-1.3 directory. The Ant documentation is located in the docs/manual directory. You should start with the docs/manual/index.html file and browse through its contents if you want to use Ant. You won't need to know anything about Ant build scripts in order to compile and run @@ -209,16 +210,15 @@ need to specify a CLASSPATH environment variable if you don't normally have to./para paraThe next step will be to download, install and test the JBoss server. At -the time of writing the most recent version of JBoss is 2.2.2. +the time of updating this the most recent version of JBoss is 2.4.1. It doesn't matter where you install JBoss. There is no requirement for root access to -run JBoss as none of the default ports are below the 1024 privaledged port range. +run JBoss as none of the default ports are below the 1024 priveledged port range. You will need to define a JBOSS_DIST environment variable that points to the installation location of the JBoss installation directory. This is required to build and run all of the documentation examples you will download later./para paraJBoss is distributed as a ZIP file. You can download the binary -distribution which contains the latest offical release (which was 2.2.2 -at the time of writing) or a source snapshot with the latest -version from CVS. This documentation mainly is written for the 2.2.2 version./para +distribution which contains the latest offical release or a source snapshot with the latest +version from CVS. This documentation mainly was written for the 2.2.2 version and
AW: AW: [JBoss-dev] RH and -classic
you asked, where the CCE occurred, because you may have encountered that problem already some while ago ... -Ursprüngliche Nachricht- Von: Jason Dillon [mailto:[EMAIL PROTECTED]] Gesendet: Montag, 1. Oktober 2001 09:29 An: '[EMAIL PROTECTED]' Betreff: Re: AW: [JBoss-dev] RH and -classic Diese Nachricht enthält Zeichen, die vom Internet-Dienst nicht unterstützt werden. Zum Lesen doppelklicken Sie auf die beigefügte Anlage. Falls der Text inkorrekt angezeigt wird, speichern Sie die Anlage (Datei, Speichern unter) auf der Festplatte und öffnen Sie sie mit einem Programm, das die Zeichen darstellen kann. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] The rabbit has a bug in its pelt: org.jboss.system.URLClassLoader
Hi there (got currently huge problems with our firewall, prevents a proper bug report :-( Sascha has noticed that the RH startup process sometimes deadlocks in the new classloading scheme especially when he is starting up JavaGroups and his HA MBeans. My hypothesis (see snippets from his thread-dump below) which I´m very convinced of is: - There is some thread T1 (Jboss-Main initialising the HA Service) loading some class via a classloader CL1. That call is dispatched to the ServiceLibrary-MBean which is obtaining a monitor M1 (to ServiceLibrary.classLoaders) in order to consistently search for the class in the registered classLoaders. - There is some concurrent thread T2 (the already started Javagroups-service, I guess) loading some class lazily via CL2.loadClassInternal(String). This (private) method is synchronized on the classloader instance, thx to our beloved SUN programmers! Hence it obtains the monitor (lets call it M2) to CL2 and calls loadClass(String) which is then dispatched to the ServiceLibrary-mbean. - T1 now tries to CL2.loadClassLocally()--java.lang.ClassLoader.loadClass() which is synchronized on CL2, hence tries to obtain M2. - T2 tries to get the monitor M1 in order to enter the ServiceLibraries class search algorithm. The problem is that f**cking private method in java.lang.ClassLoader that is unnecessarily synchronized (the following loadClass is synchronized anyway ...). A workaround could be to always lock on the ServiceLibrary.classLoaders but that may not be very efficient. Anyone got a better idea? CGJ -Ursprüngliche Nachricht- Von: Sacha Labourey [mailto:[EMAIL PROTECTED]] Gesendet: Montag, 1. Oktober 2001 13:33 An: Jung , Dr. Christoph Betreff: RE: Java Classloaders document ... snip ... DownHandler (NAKACK) prio=5 tid=0x81d940 nid=0x9cc waiting for monitor entry [0x99be000..0x99bfdbc] at org.jboss.system.ServiceLibraries.loadClass(ServiceLibraries.java:278) at org.jboss.system.URLClassLoader.loadClass(URLClassLoader.java:145) at org.jboss.system.URLClassLoader.loadClass(URLClassLoader.java:151) at java.lang.ClassLoader.loadClassInternal(Unknown Source) at JavaGroups.NakReceiverWindow.init(NakReceiverWindow.java:147) at ... snip ... main prio=5 tid=0x234f38 nid=0x878 waiting for monitor entry [0x6e000..0x6fc34] at java.lang.ClassLoader.loadClass(Unknown Source) at org.jboss.system.URLClassLoader.loadClassLocally(URLClassLoader.java:163) at org.jboss.system.ServiceLibraries.loadClass(ServiceLibraries.java:292) at org.jboss.system.URLClassLoader.loadClass(URLClassLoader.java:145) at org.jboss.system.URLClassLoader.loadClass(URLClassLoader.java:151) at sun.rmi.server.RemoteProxy.loadClassFromClass(Unknown Source) at sun.rmi.server.RemoteProxy.getSkeleton(Unknown Source) at sun.rmi.server.UnicastServerRef.setSkeleton(Unknown Source) at sun.rmi.server.UnicastServerRef.exportObject(Unknown Source) at sun.rmi.server.UnicastServerRef.exportObject(Unknown Source) at java.rmi.server.UnicastRemoteObject.exportObject(Unknown Source) at java.rmi.server.UnicastRemoteObject.exportObject(Unknown Source) at java.rmi.server.UnicastRemoteObject.exportObject(Unknown Source) at Here is my hypothesis: The deadlock is caused by the interaction of Thread-1 (JavaGroups) lets the VM loading some class lazily (loadClassInternal There are two threads concurrently entering the ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results
JBoss daily test results SUMMARY Number of tests run: 21 Successful tests: 20 Errors:1 Failures: 0 [time of test: 1 October 2001 13:57 GMT] [java.version: 1.3.1] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.3.1-b24] [java.vm.name: Java HotSpot(TM) Server VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.3-12] See http://lubega.com for full details 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 [details not shown - as this makes the mail too big to reach the sf mailing list] ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] The rabbit has a bug in its pelt: org.jboss.system.URLClassLoader
I must correct myself! We have a principle problem, unfortunately, for which I do not have an immediate answer right now: Actually, instead of synchronized(classLoaders) in ServiceLibraries, there would be the need to *atomically* synchronize on all instances of the set in order not to interfere with the ClassLoader.loadClassInternally() calls. But this is not possible with the Java synchronization mechanism, AFAIK. Puzzling, CGJ (BTW: If somebody would offer Voodoo-puppets of SUN developers in the jboss-store, you could make a fortune! If you would additionally provide JBoss-needles, you could even make a bigger one!) -Ursprüngliche Nachricht- Von: Sacha Labourey [mailto:[EMAIL PROTECTED]] Gesendet: Montag, 1. Oktober 2001 15:04 An: Jung , Dr. Christoph Betreff: RE: Java Classloaders document Christoph, I've just read your answer and as I am not yet up-to-date with the new JBoss classloading mechanism, can't be very efficient at commenting your idea... Consequently, I am very confident in what you suggest ;) No, in fact, what you suggest seem very very possible. I may try to synchronize a method from your loading mechanism to see if it solves the problem. Which part should I synchronize? Thank you for your very effective help. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss 3.0
Anyone know of any timescales for the release of JBoss 3.0? TIA ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] The rabbit has a bug in its pelt: org.jboss.system.URLClassLoader
|(BTW: If somebody would offer Voodoo-puppets of SUN developers in the |jboss-store, you could make a fortune! If you would additionally provide |JBoss-needles, you could even make a bigger one!) LOL ^ 10 listen I really want to finish the website but will try to come back to this soon (like tonight or tomorrow) If you feel like getting down... get down, get down, get down, get down don't let anybody stop you baby! marcf | | |-Ursprüngliche Nachricht- |Von: Sacha Labourey [mailto:[EMAIL PROTECTED]] |Gesendet: Montag, 1. Oktober 2001 15:04 |An: Jung , Dr. Christoph |Betreff: RE: Java Classloaders document | | |Christoph, | |I've just read your answer and as I am not yet up-to-date with the new |JBoss |classloading mechanism, can't be very efficient at commenting your idea... |Consequently, I am very confident in what you suggest ;) | |No, in fact, what you suggest seem very very possible. I may try to |synchronize a method from your loading mechanism to see if it solves the |problem. Which part should I synchronize? | |Thank you for your very effective help. | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] [PATCH] Log4j 1.2alpha compatibility upgrade
ceki, Send me a sourceforge account please, marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of Ceki |Gülcü |Sent: Monday, October 01, 2001 4:55 AM |To: [EMAIL PROTECTED] |Subject: [JBoss-dev] [PATCH] Log4j 1.2alpha compatibility upgrade | | | |Hello, | |The included patches allow Jboss (latest CVS-snapshot) to work |with log4j 1.2alpa1, xdoclet-related patches are also included. |You can continue to use your own subclass of Category although |this is likely to cause problems if and when you decide to support |the LogManager architecture. | |Let me know if you need further clarifications. Regards, | |ps: JBoss is pretty awesome. Well done! | |-- |Ceki Gülcü - http://qos.ch | ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JBoss 3.0
RH exists in a space with no time... it just takes us time to materialize it in our punny 3D world. Soon is the word love, marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of Tim |Fox |Sent: Monday, October 01, 2001 9:48 AM |To: [EMAIL PROTECTED] |Subject: [JBoss-dev] JBoss 3.0 | | |Anyone know of any timescales for the release of JBoss 3.0? |TIA | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] as the cvs root becomes more complicated...
we will eventually want to reorganize things to work better with the build system. for example, right now we have a mostly flat namespace in the server, with the exception of 'build'. I suggest that each project have its own highlevel repository, with child modules living beneith it (like how it is checked out). This will serve two main purposes: 1) simplifiy the inclusing of a projects direct child modules. CVSROOT/modules will only have to list external modules (those from other highlevel projects) 2) allowing better organization due to namespace seperation. For example, the jboss-all project should probably be layed out like this: CVSROOT/ jboss/ build/ server/ naming/ ... The website like this: website/ build/ docroot/ survey/ forum/ petstore/ ... The jboss-docs module is currently only a sub-set of jboss-all, so I currently does not need any repo changes. I am not suggesting that this be done now, or even in the near future. I just want to let those interested know that we should make this change eventually, when it is most conveient. The net effect of these changes on users will be having to pull down a fresh copy of the project they are working on. To make this changes is fairly simple, though it is complicated slightly by us not having direct control over the repository files. --jason ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] remove deprecated cvs modules?
sure |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of Jason |Dillon |Sent: Monday, October 01, 2001 4:24 PM |To: [EMAIL PROTECTED] |Subject: [JBoss-dev] remove deprecated cvs modules? | | |is it time to remove the depredated models from CVSROOT/modules as well as |the documenation on the website about them? | |--jason | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: website-forums - Imported sources
User: user57 Date: 01/10/01 13:46:04 Log: o import of the build skeleton for the jboss-website/forums module Status: Vendor Tag: jboss Release Tags: start N website-forums/build.bat N website-forums/build.log N website-forums/build.sh N website-forums/build.xml No conflicts created by this import ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: CVSROOT modules
User: user57 Date: 01/10/01 13:46:58 Modified:.modules Log: o updated jboss-website module list to include forums Revision ChangesPath 1.59 +2 -0 CVSROOT/modules Index: modules === RCS file: /cvsroot/jboss/CVSROOT/modules,v retrieving revision 1.58 retrieving revision 1.59 diff -u -r1.58 -r1.59 --- modules 2001/09/12 01:47:56 1.58 +++ modules 2001/10/01 20:46:58 1.59 @@ -105,10 +105,12 @@ jboss-website-modules-a \ _jboss_website_build \ + _jboss_website_forums \ _jboss_website \ _jboss_manual _jboss_website_build -d buildbuild/website +_jboss_website_forums-d forums website-forums _jboss_website -d website newsite ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: AW: AW: [JBoss-dev] RH and -classic
Jason, I enclose the same error I'm obtaining when trying to debug (I may be a week or so out of date on the sources, but it's the same error on the same service). You can see the CCE on org.mortbay.util.JarFileResource: [AutoDeployer,DEBUG] Received notification of mbean JBOSS-SYSTEM:service=Jetty's deployment. [Default,INFO] Created the beanJBOSS-SYSTEM:service=Jetty [Configurator,DEBUG] JettyHome set to dummy in JBOSS-SYSTEM:service=Jetty [Jetty,INFO] set JettyHome to dummy [Configurator,DEBUG] Configuration set to ../conf/default/jetty.xml in JBOSS-SYSTEM:service=Jetty [Jetty,INFO] set Configuration to ../conf/default/jetty.xml [Configurator,DEBUG] WebDefault set to ../conf/default/webdefault.xml in JBOSS-SYSTEM:service=Jetty [Jetty,INFO] set WebDefault to ../conf/default/webdefault.xml [Configurator,DEBUG] UnpackWars set to true in JBOSS-SYSTEM:service=Jetty [Jetty,INFO] set UnpackWars to true [Configurator,DEBUG] PublishMBeans set to true in JBOSS-SYSTEM:service=Jetty [Jetty,INFO] set PublishMBeans to true [JettyService,INFO] Initializing [Jetty,INFO] loaded properties from: jetty.properties [ServiceController,ERROR] java.lang.ClassCircularityError: org/mortbay/util/JarFileResource [JettyService,INFO] Starting [JettyService,ERROR] Stopped java.lang.NullPointerException at org.jboss.jetty.JettyService.startService(Unknown Source) at org.jboss.system.ServiceMBeanSupport.start(Unknown Source) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.system.ServiceController$ServiceProxy.invoke(Unknown Source) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(Unknown Source) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.deployment.ServiceDeployer.invoke(Unknown Source) at org.jboss.deployment.ServiceDeployer.doDeployment(Unknown Source) at org.jboss.deployment.ServiceDeployer.deploy(Unknown Source) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.deployment.AutoDeployer.deploy(Unknown Source) at org.jboss.deployment.AutoDeployer.run(Unknown Source) at org.jboss.deployment.AutoDeployer.startService(Unknown Source) at org.jboss.system.ServiceMBeanSupport.start(Unknown Source) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.system.ServiceController$ServiceProxy.invoke(Unknown Source) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(Unknown Source) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.deployment.ServiceDeployer.invoke(Unknown Source) at org.jboss.deployment.ServiceDeployer.doDeployment(Unknown Source) at org.jboss.deployment.ServiceDeployer.postRegister(Unknown Source) at com.sun.management.jmx.MBeanServerImpl.postRegisterInvoker(MBeanServerImpl.j ava:2274) at com.sun.management.jmx.MBeanServerImpl.createMBean(MBeanServerImpl.java:532) at org.jboss.Main.init(Unknown Source) at org.jboss.Main$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at org.jboss.Main.main(Unknown Source) [ServiceController,ERROR] java.lang.NullPointerException -Mensaje original- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]En nombre de Jason Dillon Enviado el: lunes, 01 de octubre de 2001 21:14 Para: '[EMAIL PROTECTED]' Asunto: Re: AW: AW: [JBoss-dev] RH and -classic CCE? I only see a NPE from the output you provided. I still can't remember... oh well. Did we want to make the jboss.net stuff part of the jboss-all project? Or is it best left by itself for the moment? --jason On Mon, 1 Oct 2001, Jung , Dr. Christoph wrote: you asked, where the CCE occurred, because you may have encountered that problem already some while ago ... -Ursprüngliche Nachricht- Von: Jason Dillon [mailto:[EMAIL PROTECTED]] Gesendet: Montag, 1. Oktober 2001 09:29 An: '[EMAIL PROTECTED]' Betreff: Re: AW: [JBoss-dev] RH and -classic Diese Nachricht enthält Zeichen, die vom
[JBoss-dev] CVS update: CVSROOT modules
User: user57 Date: 01/10/01 13:52:18 Modified:.modules Log: o removed deprecated modules o added jboss - jboss-all o added docs - jboss-docs o added website - jboss-website Revision ChangesPath 1.60 +4 -30 CVSROOT/modules Index: modules === RCS file: /cvsroot/jboss/CVSROOT/modules,v retrieving revision 1.59 retrieving revision 1.60 diff -u -r1.59 -r1.60 --- modules 2001/10/01 20:46:58 1.59 +++ modules 2001/10/01 20:52:18 1.60 @@ -166,36 +166,10 @@ # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # - -## -## Legacy modules, should use a jboss-* module instead. -## - -jbossjboss -jbossmq jbossmq -jnp jnp -jbosscx jbosscx -manual manual -adminadmin -jboss-j2ee jboss-j2ee -jbossmx jbossmx -jbosspooljbosspool -jbosstestjbosstest - - -## -## Everything else -## - -contrib contrib -zoap zoap -ejx ejx -zola zola -newsite newsite - - ## -## Name-space migration aliases. +## Aliases ## -website -d website newsite +jboss-a jboss-all +docs -a jboss-docs +website -a jboss-website ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite/src/docs cvs.jsp
User: user57 Date: 01/10/01 13:52:45 Modified:src/docs cvs.jsp Log: o updated the list of CVS MODULES (including new aliases). Revision ChangesPath 1.4 +6 -20 newsite/src/docs/cvs.jsp Index: cvs.jsp === RCS file: /cvsroot/jboss/newsite/src/docs/cvs.jsp,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- cvs.jsp 2001/09/28 03:25:43 1.3 +++ cvs.jsp 2001/10/01 20:52:45 1.4 @@ -65,8 +65,8 @@ p class=text The list of available modules has recently changed. Below is a list of the currently supported modules. These modules are created via - CVSROOT/modules, so look there for more information about how they - work. + ttCVSROOT/modules/tt, so look there for more information about how + they work. ul class=text libjboss-all/b: Everything required to build JBoss. @@ -78,26 +78,12 @@ /ul p class=text - The following modules are still available for browsing, but - we recommend that the jboss-* modules be used instead./p + The following aliases are also available. ul class=text - libjboss/b: the main jboss tree - libjbosssx/b: the default security implementation - libcontrib/b: 3rd party contribution to jboss - libcontrib/tomcat/b: The Tomcat 3.2.2 mbean service - libcontrib/jetty/b: The Jetty mbean service - libjbosstest/b: the testsuite for jboss - libzoap/b: an alternative SOAP based invocation - libejx/b: the gui front end of jboss - libjnp/b: the JNDI implementation - libzola/b: the application model - libjbossmq/b: the JMS implementation - libjbosscx/b: the JCA implementation - libjbosspool/b: generic object pool. - A fork from Aaron Mulder's Minerva - libjboss-j2ee/b: J2EE core classes - libmanual/b: JBoss manual + libjboss/b: jboss-all + libdocs/b: jboss-docs + libwebsite/b: jboss-website /ul p class=headCVS Administration Polcies/p ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: website-forums build.log
User: user57 Date: 01/10/01 13:54:29 Removed: .build.log Log: o oops, this does not get checked in ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: manual/src/xdocs/howto howtoejbdoclet.xml
User: ibruell Date: 01/10/01 13:54:42 Modified:src/xdocs/howto howtoejbdoclet.xml Log: Some changings in grammatics. Revision ChangesPath 1.2 +62 -57manual/src/xdocs/howto/howtoejbdoclet.xml Index: howtoejbdoclet.xml === RCS file: /cvsroot/jboss/manual/src/xdocs/howto/howtoejbdoclet.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- howtoejbdoclet.xml2001/08/29 09:19:37 1.1 +++ howtoejbdoclet.xml2001/10/01 20:54:42 1.2 @@ -1,9 +1,10 @@ ?xml version = 1.0 encoding = UTF-8? +!-- $Id: howtoejbdoclet.xml,v 1.2 2001/10/01 20:54:42 ibruell Exp $ -- !-- brief howto for using ejbdoclet -- section id=howtoejbdoclet - titleHow to generate Beans with EJBDoclet (XDoclet)/title - subtitleIn work(!)/subtitle + titleHow to generate Enterprise Java Beans with EJBDoclet (XDoclet)/title + subtitleUnder construction(!)/subtitle paraAuthor: author @@ -14,21 +15,21 @@ /para para -EJBDoclet is a tool, that makes coding of Enterprise JavaBeans much easier. You only -have to code emphasisone/emphasis file to generate automaticly the needed -Interfaces and descriptor files. With the usage of filenameant/filename -and the filenameverifier/filename it is very easy to produce correct Beans. +EJBDoclet is a tool that facilitates coding Enterprise Java Beans. You only +have to code emphasisone/emphasis file to generate automatically the needed +interfaces and descriptor files. By using filenameant/filename +and the filenameverifier/filename it is very easy to produce correct beans. /para para -EJBDoclet is a OpenSource project initiated by Rickard Oberg which stays at +EJBDoclet is an OpenSource project started by Rickard Oberg and located at ulink url=http://sourceforge.net/projects/ejbdoclet; http://sourceforge.net/projects/ejbdoclet/ulink. /para para -EJBDoclet has renamed to XDoclet and a new project with this name was initiated. -For now no release with the new name is available, but all questions about -EJBDoclet and in the future for XDoclet goes to the new mailing lists from -XDoclet hosted at ulink url=http://sourceforge.net/projects/xdoclet; +EJBDoclet has been renamed XDoclet and a new project with this name has been started. +XDoclet 1.0 was released in September 2001. Any questions about +EJBDoclet and XDoclet must go to the new XDoclet mailing lists +hosted at ulink url=http://sourceforge.net/projects/xdoclet; http://sourceforge.net/projects/xdoclet/ulink /para @@ -36,13 +37,13 @@ titleRequirements/title para - You only need to download the ejbdoclet.jar and put it somwhere in you classpath. I - think the usage of ant is very recommend (and for now the only way to use - ejbdoclet!). + You need to download the filenameejbdoclet.jar/filename file and + put it somewhere in you classpath. I think that the use of Ant is highly recommended + (and, for now, it is the only way to use EJBDoclet!). /para para - The tools.jar from the j2sdk is needed to call javadoc, so place it in the - classpath, too. + The filenametools.jar/filename file from the J2SDK is also needed to + call Javadoc, so place it in the classpath, too. /para /section @@ -50,11 +51,11 @@ titleCreating the Bean as a Template/title para - EJBDoclet uses JavaDoc Tags and the JavaDoc mechanism to generate the needed files - out of the template. Here is an example of an Entity Bean class section: + EJBDoclet uses Javadoc tags and the Javadoc mechanism to generate the needed files + out of a emphasistemplate/emphasis. Here there is an example of a section for an + Entity Bean class: programlisting - /** * This is an account bean. It is an example of how to use the EJBDoclet tags. * @@ -89,39 +90,40 @@ calloutlist callout arearefs=ejbdoclet-entity-cmp para -Here is specified that this would be an Entity Bean +Here is where it is specified that this is an Entity Bean /para /callout callout arearefs=ejbdoclet-finder para -Defining the finder methods +Definitions of the finder methods /para /callout callout arearefs=ejbdoclet-envvar para -Easy define envelope vars +Easy definition of environment variables /para /callout callout arearefs=ejbdoclet-ref para -Define references to other beans +
[JBoss-dev] CVS update: website-survey - Imported sources
User: user57 Date: 01/10/01 13:55:33 Log: o import of build skeleton for jboss-website/survey module Status: Vendor Tag: jboss Release Tags: start N website-survey/build.bat N website-survey/build.sh N website-survey/build.xml No conflicts created by this import ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: CVSROOT modules
User: user57 Date: 01/10/01 13:56:14 Modified:.modules Log: o added survey to jboss-website module list Revision ChangesPath 1.61 +2 -0 CVSROOT/modules Index: modules === RCS file: /cvsroot/jboss/CVSROOT/modules,v retrieving revision 1.60 retrieving revision 1.61 diff -u -r1.60 -r1.61 --- modules 2001/10/01 20:52:18 1.60 +++ modules 2001/10/01 20:56:14 1.61 @@ -106,11 +106,13 @@ jboss-website-modules-a \ _jboss_website_build \ _jboss_website_forums \ + _jboss_website_survey \ _jboss_website \ _jboss_manual _jboss_website_build -d buildbuild/website _jboss_website_forums-d forums website-forums +_jboss_website_survey-d survey website-survey _jboss_website -d website newsite ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: AW: AW: [JBoss-dev] RH and -classic
Hi I reported this problem a week or two ago. But recently I got a second CCE later on (not with Jetty). Andy - Original Message - From: Ignacio Coloma [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, October 01, 2001 1:45 PM Subject: RE: AW: AW: [JBoss-dev] RH and -classic Jason, I enclose the same error I'm obtaining when trying to debug (I may be a week or so out of date on the sources, but it's the same error on the same service). You can see the CCE on org.mortbay.util.JarFileResource: [ServiceController,ERROR] java.lang.ClassCircularityError: org/mortbay/util/JarFileResource [JettyService,INFO] Starting [JettyService,ERROR] Stopped java.lang.NullPointerException at org.jboss.jetty.JettyService.startService(Unknown Source) ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] The fix for bug #462253 is not acceptable
Ooops, sounds like I messed up by applying it... Still, lazy hacking, that hurts... I prefer a slight oversight. -Original Message- From: Scott M Stark [mailto:[EMAIL PROTECTED]] Sent: Monday, October 01, 2001 6:34 PM To: [EMAIL PROTECTED] Subject: [JBoss-dev] The fix for bug #462253 is not acceptable The fix for bug[ #462253 ] TextMessage fails for 64k content is not acceptable for 3 reasons: 1. It breaks backward compatibility with previous versions but does not change the SpyTextMessage.serialVersionUID value. Using the 2.4.1 jbossmq jars produces the following exceptions when run with the mdb unit test against a server using the latest 2.4 branch jbossmq jars: [OILServerILService] Client request resulted in a server exception: java.lang.NegativeArraySizeException at java.lang.StringBuffer.init(StringBuffer.java:116) at org.jboss.mq.SpyTextMessage.readExternal(SpyTextMessage.java:76) at org.jboss.mq.SpyMessage.readMessage(SpyMessage.java:589) at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService. java:219) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService. java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService. java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService. java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService. java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService. java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService. java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService. java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService. java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService. java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService. java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService. java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService. java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService. java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService. java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception: java.rmi.RemoteException: Bad method code ! at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService. java:273) at java.lang.Thread.run(Thread.java:484) [OILServerILService] Client request resulted in a server exception:
Re: AW: AW: [JBoss-dev] RH and -classic
I haven't a clue as to why this happens... =( --jason On Mon, 1 Oct 2001, Andreas Schaefer wrote: Hi I reported this problem a week or two ago. But recently I got a second CCE later on (not with Jetty). Andy - Original Message - From: Ignacio Coloma [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, October 01, 2001 1:45 PM Subject: RE: AW: AW: [JBoss-dev] RH and -classic Jason, I enclose the same error I'm obtaining when trying to debug (I may be a week or so out of date on the sources, but it's the same error on the same service). You can see the CCE on org.mortbay.util.JarFileResource: [ServiceController,ERROR] java.lang.ClassCircularityError: org/mortbay/util/JarFileResource [JettyService,INFO] Starting [JettyService,ERROR] Stopped java.lang.NullPointerException at org.jboss.jetty.JettyService.startService(Unknown Source) ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: website-forums/src - New directory
User: user57 Date: 01/10/01 15:20:27 website-forums/src - New directory ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: website-forums/src/lib - New directory
User: user57 Date: 01/10/01 15:20:35 website-forums/src/lib - New directory ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: website-forums/src/metadata - New directory
User: user57 Date: 01/10/01 15:20:37 website-forums/src/metadata - New directory ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: AW: AW: [JBoss-dev] RH and -classic
What does this exception mean... I am confused. --jason On Mon, 1 Oct 2001, Ignacio Coloma wrote: Jason, I enclose the same error I'm obtaining when trying to debug (I may be a week or so out of date on the sources, but it's the same error on the same service). You can see the CCE on org.mortbay.util.JarFileResource: [AutoDeployer,DEBUG] Received notification of mbean JBOSS-SYSTEM:service=Jetty's deployment. [Default,INFO] Created the beanJBOSS-SYSTEM:service=Jetty [Configurator,DEBUG] JettyHome set to dummy in JBOSS-SYSTEM:service=Jetty [Jetty,INFO] set JettyHome to dummy [Configurator,DEBUG] Configuration set to ../conf/default/jetty.xml in JBOSS-SYSTEM:service=Jetty [Jetty,INFO] set Configuration to ../conf/default/jetty.xml [Configurator,DEBUG] WebDefault set to ../conf/default/webdefault.xml in JBOSS-SYSTEM:service=Jetty [Jetty,INFO] set WebDefault to ../conf/default/webdefault.xml [Configurator,DEBUG] UnpackWars set to true in JBOSS-SYSTEM:service=Jetty [Jetty,INFO] set UnpackWars to true [Configurator,DEBUG] PublishMBeans set to true in JBOSS-SYSTEM:service=Jetty [Jetty,INFO] set PublishMBeans to true [JettyService,INFO] Initializing [Jetty,INFO] loaded properties from: jetty.properties [ServiceController,ERROR] java.lang.ClassCircularityError: org/mortbay/util/JarFileResource [JettyService,INFO] Starting [JettyService,ERROR] Stopped java.lang.NullPointerException at org.jboss.jetty.JettyService.startService(Unknown Source) at org.jboss.system.ServiceMBeanSupport.start(Unknown Source) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.system.ServiceController$ServiceProxy.invoke(Unknown Source) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(Unknown Source) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.deployment.ServiceDeployer.invoke(Unknown Source) at org.jboss.deployment.ServiceDeployer.doDeployment(Unknown Source) at org.jboss.deployment.ServiceDeployer.deploy(Unknown Source) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.deployment.AutoDeployer.deploy(Unknown Source) at org.jboss.deployment.AutoDeployer.run(Unknown Source) at org.jboss.deployment.AutoDeployer.startService(Unknown Source) at org.jboss.system.ServiceMBeanSupport.start(Unknown Source) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.system.ServiceController$ServiceProxy.invoke(Unknown Source) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(Unknown Source) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.deployment.ServiceDeployer.invoke(Unknown Source) at org.jboss.deployment.ServiceDeployer.doDeployment(Unknown Source) at org.jboss.deployment.ServiceDeployer.postRegister(Unknown Source) at com.sun.management.jmx.MBeanServerImpl.postRegisterInvoker(MBeanServerImpl.j ava:2274) at com.sun.management.jmx.MBeanServerImpl.createMBean(MBeanServerImpl.java:532) at org.jboss.Main.init(Unknown Source) at org.jboss.Main$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at org.jboss.Main.main(Unknown Source) [ServiceController,ERROR] java.lang.NullPointerException -Mensaje original- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]En nombre de Jason Dillon Enviado el: lunes, 01 de octubre de 2001 21:14 Para: '[EMAIL PROTECTED]' Asunto: Re: AW: AW: [JBoss-dev] RH and -classic CCE? I only see a NPE from the output you provided. I still can't remember... oh well. Did we want to make the jboss.net stuff part of the jboss-all project? Or is it best left by itself for the moment? --jason On Mon, 1 Oct 2001, Jung , Dr. Christoph wrote: you asked, where the CCE occurred, because you may have encountered that problem already some while ago ... -Ursprüngliche Nachricht- Von: Jason Dillon [mailto:[EMAIL PROTECTED]] Gesendet: Montag, 1. Oktober 2001 09:29
Re: AW: [JBoss-dev] RH and -classic
It means something is pretty f'd up as this indicates a class is its own superclass or an interface its own superinterface. We need to create a nasty multi-threaded stress test of the class loader with some complex object graphs spread out across jars to shake out its bugs. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Jason Dillon [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, October 01, 2001 3:36 PM Subject: RE: AW: AW: [JBoss-dev] RH and -classic What does this exception mean... I am confused. --jason On Mon, 1 Oct 2001, Ignacio Coloma wrote: Jason, I enclose the same error I'm obtaining when trying to debug (I may be a week or so out of date on the sources, but it's the same error on the same service). You can see the CCE on org.mortbay.util.JarFileResource: [AutoDeployer,DEBUG] Received notification of mbean JBOSS-SYSTEM:service=Jetty's deployment. [Default,INFO] Created the beanJBOSS-SYSTEM:service=Jetty [Configurator,DEBUG] JettyHome set to dummy in JBOSS-SYSTEM:service=Jetty [Jetty,INFO] set JettyHome to dummy [Configurator,DEBUG] Configuration set to ../conf/default/jetty.xml in JBOSS-SYSTEM:service=Jetty [Jetty,INFO] set Configuration to ../conf/default/jetty.xml [Configurator,DEBUG] WebDefault set to ../conf/default/webdefault.xml in JBOSS-SYSTEM:service=Jetty [Jetty,INFO] set WebDefault to ../conf/default/webdefault.xml [Configurator,DEBUG] UnpackWars set to true in JBOSS-SYSTEM:service=Jetty [Jetty,INFO] set UnpackWars to true [Configurator,DEBUG] PublishMBeans set to true in JBOSS-SYSTEM:service=Jetty [Jetty,INFO] set PublishMBeans to true [JettyService,INFO] Initializing [Jetty,INFO] loaded properties from: jetty.properties [ServiceController,ERROR] java.lang.ClassCircularityError: org/mortbay/util/JarFileResource ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: website-forums build.xml
User: user57
Date: 01/10/01 16:06:01
Modified:.build.xml
Log:
o adding support files required to setup the forums deployable
Revision ChangesPath
1.2 +76 -13website-forums/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/website-forums/build.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- build.xml 2001/10/01 20:46:04 1.1
+++ build.xml 2001/10/01 23:06:01 1.2
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.1 2001/10/01 20:46:04 user57 Exp $ --
+!-- $Id: build.xml,v 1.2 2001/10/01 23:06:01 user57 Exp $ --
project default=main name=JBoss Website/Forums
@@ -174,21 +174,15 @@
!-- Configure the tasks used by this module. --
target name=_configure-tasks unless=configure-tasks.disable
!-- Where source files live --
-property name=source.bin value=${module.source}/bin/
+property name=source.etc value=${module.source}/etc/
property name=source.metadata value=${module.source}/metadata/
-property name=source.examples value=${module.source}/examples/
-property name=source.stylesheets value=${module.source}/stylesheets/
-property name=source.docs value=${module.source}/docs/
-property name=source.xdocs value=${module.source}/xdocs/
+property name=source.lib value=${module.source}/lib/
!-- Where build generated files will go --
-property name=build.bin value=${module.output}/bin/
-property name=build.metadata value=${module.output}/metadata/
-property name=build.snapshots value=${module.output}/snapshots/
-property name=build.docs value=${module.output}/docs/
-property name=build.xdocs value=${module.output}/xdocs/
-property name=build.stylesheets value=${module.output}/stylesheets/
+property name=build.etc value=${module.output}/etc/
property name=build.lib value=${module.output}/lib/
+property name=build.metadata value=${module.output}/metadata/
+property name=build.jive value=${module.output}/jive/
!-- Install/Release structure --
property name=install.id value=${module.name}-${module.version}/
@@ -243,8 +237,41 @@
--
target name=compile
description=Compile all source files.
- depends=init/
+ depends=init,
+ compile-etc,
+ compile-metadata,
+ compile-jive/
+
+ !-- Compile etc files (manifests and such) --
+ target name=compile-etc depends=init
+!-- this property must be set for the config/copy to work --
+require property=jivesoftware.jive.home/
+echoUsing jivesoftware.jive.home: ${jivesoftware.jive.home}/echo
+
+mkdir dir=${build.etc}/
+copy todir=${build.etc} filtering=yes
+ fileset dir=${source.etc}
+ include name=**/*/
+ /fileset
+/copy
+ /target
+ !-- Compile metadata files --
+ target name=compile-metadata depends=init
+mkdir dir=${build.metadata}/
+copy todir=${build.metadata} filtering=yes
+ fileset dir=${source.metadata}
+ include name=**/*/
+ /fileset
+/copy
+ /target
+
+ !-- Extract the Jive distribution --
+ target name=compile-jive depends=init
+mkdir dir=${build.jive}/
+unjar src=${source.lib}/jive.jar dest=${build.jive}/
+ /target
+
!-- == --
!-- Archives --
@@ -255,6 +282,25 @@
--
target name=jars depends=compile description=Builds all jar files.
mkdir dir=${build.lib}/
+
+!-- Build the jive.war --
+war warfile=${build.lib}/jive.war
+ webxml=${build.metadata}/jive-web.xml
+ fileset dir=${build.jive}/application
+include name=*/**/
+ /fileset
+ zipfileset prefix=WEB-INF/classes dir=${build.etc}
+include name=jive_init.properties/
+ /zipfileset
+/war
+
+!-- Build the forums.ear --
+ear earfile=${build.lib}/forums.ear
+ appxml=${build.metadata}/forums-application.xml
+ fileset dir=${build.lib}
+include name=jive.war/
+ /fileset
+/ear
/target
@@ -455,5 +501,22 @@
target name=most depends=jars
description=Builds almost everything./
+
+ !--
+ | Copy some files to the specified jive home, this should not happen
+ | in production, as these files should exist already. This only
+ | servers to help setup testing environemnts. Users will also have
+ | to setup the database as specified in the Jive docs.
+ --
+
[JBoss-dev] CVS update: website-forums/src/lib jive.jar
User: user57 Date: 01/10/01 16:06:01 Added: src/lib jive.jar Log: o adding support files required to setup the forums deployable Revision ChangesPath 1.1 website-forums/src/lib/jive.jar Binary file ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: manual/src/xdocs resource.xml
User: d_jencks Date: 01/10/01 16:11:04 Modified:src/xdocs resource.xml Log: Added some depends elements to examples, thanks Ignacio Revision ChangesPath 1.4 +8 -2 manual/src/xdocs/resource.xml Index: resource.xml === RCS file: /cvsroot/jboss/manual/src/xdocs/resource.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- resource.xml 2001/09/27 05:43:09 1.3 +++ resource.xml 2001/10/01 23:11:04 1.4 @@ -278,14 +278,17 @@ !-- -- !-- = -- -!-- $Id: resource.xml,v 1.3 2001/09/27 05:43:09 d_jencks Exp $ -- +!-- $Id: resource.xml,v 1.4 2001/10/01 23:11:04 d_jencks Exp $ -- server dependsJBOSS-SYSTEM:service=Naming/depends dependsJBOSS-SYSTEM:service=TransactionManager/depends + dependsJCA:service=ConnectionManagerFactoryLoader,name=MinervaSharedLocalCMFactory/depends + dependsJCA:service=RARDeployer/depends + classpath archives= mm.mysql-2.0.4-bin.jar, jbosscx.sar/ @@ -346,12 +349,15 @@ !-- -- !-- = -- -!-- $Id: resource.xml,v 1.3 2001/09/27 05:43:09 d_jencks Exp $ -- +!-- $Id: resource.xml,v 1.4 2001/10/01 23:11:04 d_jencks Exp $ -- server dependsJBOSS-SYSTEM:service=Naming/depends dependsJBOSS-SYSTEM:service=TransactionManager/depends + dependsJCA:service=ConnectionManagerFactoryLoader,name=MinervaSharedLocalCMFactory/depends + dependsJCA:service=RARDeployer/depends + classpath archives= jdbc7.0-1.2.jar, ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite/src/docs main.css
User: user57
Date: 01/10/01 16:48:24
Modified:src/docs main.css
Log:
o adding cvs/rcs id
Revision ChangesPath
1.3 +5 -1 newsite/src/docs/main.css
Index: main.css
===
RCS file: /cvsroot/jboss/newsite/src/docs/main.css,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- main.css 2001/09/29 02:02:37 1.2
+++ main.css 2001/10/01 23:48:24 1.3
@@ -1,4 +1,8 @@
-/* Style Sheet document for the new JBoss website */
+/**
+ * Style Sheet document for the new JBoss website.
+ */
+
+/* $Id: main.css,v 1.3 2001/10/01 23:48:24 user57 Exp $ */
.linkhead { font-family: Arial; font-size: 12px; color: #ff; font-weight:
bold; }
.linkmenu { font-family: Arial; font-size: 12px; color: blue; font-weight: bold;
text-decoration: none; }
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] doco_files - jboss/manual module
can we move the doco_files stuff into the jboss/manual module, since that is what those files are relavent too? This would also make it a bit cleaner to generate the .ear deployables, the manual.ear could contain the examples for that version of the manual. If we do something like this, where everything is selfcontained, then we could deploy different versions of the manual (for 2.0.x and 2.2.x and so on). --jason ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite build.xml
User: user57
Date: 01/10/01 17:15:38
Modified:.build.xml
Log:
o added a default value for jivesoftware.jive.home (which is ~/website/jive)
o setup the build module to pull the generated .ear's, soon those .ear's
might be generated from this module...
o added jboss-mq and jboss-docs to the snapshot list
Revision ChangesPath
1.17 +77 -55newsite/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/newsite/build.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- build.xml 2001/09/30 06:21:36 1.16
+++ build.xml 2001/10/02 00:15:38 1.17
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.16 2001/09/30 06:21:36 schaefera Exp $ --
+!-- $Id: build.xml,v 1.17 2001/10/02 00:15:38 user57 Exp $ --
project default=main name=JBoss/Website
@@ -133,7 +133,7 @@
!-- Module name(s) version --
property name=module.name value=website/
property name=module.Name value=JBoss Website/
-property name=module.version value=unspecified/
+property name=module.version value=DEV/
!-- Invoke the rest of the configuration targets --
call target=_configure-tools/
@@ -273,7 +273,6 @@
!-- Controls for the compile-snapshot target --
property name=snapshot.cvsroot
value=:pserver:[EMAIL PROTECTED]:/cvsroot/jboss/
-property name=snapshot.modules value=jboss-all/
!-- xdoclet --
path id=xdoclet.task.classpath
@@ -284,15 +283,7 @@
/path
property name=xdoclet.task.classpath
refid=xdoclet.task.classpath/
-!-- ejbdoclet --
-!--path id=dreambean.ejbdoclet.task.classpath
- path refid=javac.classpath/
- path refid=survey.classpath/
- pathelement location=${project.root}/tools/lib/ejbdoclet.jar/
-/path
-property name=dreambean.ejbdoclet.task.classpath
- refid=dreambean.ejbdoclet.task.classpath
-/ --
+taskdef name=xdoclet classname=xdoclet.ejb.EjbDocletTask/
/target
@@ -368,13 +359,14 @@
target name=compile-snapshots depends=init unless=snapshot.bypass
mkdir dir=${build.snapshots}/
+echoExporting CVS modules for snaphots.../echo
+
!-- Make sure there is an entry for this cvsroot --
cvspass cvsroot=${snapshot.cvsroot} password=/
-
cvs cvsroot=${snapshot.cvsroot}
- command=-q -r -f -z3 export
+ command=-Q -r -f -z3 export
date=TODAY
- package=jboss-all
+ package=jboss-all jboss-mq jboss-docs
dest=${build.snapshots}/
!-- to keep this simple, these jars task live here --
@@ -394,18 +386,58 @@
/tar
gzip src=${build.lib}/jboss-all-${build.number}.tar
zipfile=${build.lib}/jboss-all-${build.number}.tgz/
+
+!-- build jboss-mq-xxx.zip --
+zip zipfile=${build.lib}/jboss-mq-${build.number}.zip
+ fileset dir=${build.snapshots}
+include name=jboss-mq/**/
+ /fileset
+/zip
+
+!-- build jboss-mq-xxx.tgz --
+tar tarfile=${build.lib}/jboss-mq-${build.number}.tar longfile=gnu
+ basedir=${build.snapshots}
+ includes=jboss-mq/**
+/tar
+gzip src=${build.lib}/jboss-mq-${build.number}.tar
+ zipfile=${build.lib}/jboss-mq-${build.number}.tgz/
-!-- Make the JBoss DTDs available under j2ee/dtd --
+!-- build jboss-docs-xxx.zip --
+zip zipfile=${build.lib}/jboss-docs-${build.number}.zip
+ fileset dir=${build.snapshots}
+include name=jboss-docs/**/
+ /fileset
+/zip
+
+!-- build jboss-docs-xxx.tgz --
+tar tarfile=${build.lib}/jboss-docs-${build.number}.tar longfile=gnu
+ basedir=${build.snapshots}
+ includes=jboss-docs/**
+/tar
+gzip src=${build.lib}/jboss-docs-${build.number}.tar
+ zipfile=${build.lib}/jboss-docs-${build.number}.tgz/
+
+!-- = --
+!-- HACK Make the JBoss DTDs available under j2ee/dtd --
+!-- = --
+
+!--
+ | this should not be dependent on the jboss-all snapshot to function.
+ | perhaps the dtds should be in a seperate module (shared by jboss-all
+ | and jboss-website), or something... this is just bad form!
+ --
+
mkdir dir=${build.docs}/j2ee/dtd/
copy todir=${build.docs}/j2ee/dtd filtering=no
fileset
dir=${build.snapshots}/jboss-all/server/src/resources/org/jboss/metadata
include name=*.dtd/
/fileset
/copy
+
/target
!--
[JBoss-dev] CVS update: build/website build.xml
User: user57
Date: 01/10/01 17:15:38
Modified:website build.xml
Log:
o added a default value for jivesoftware.jive.home (which is ~/website/jive)
o setup the build module to pull the generated .ear's, soon those .ear's
might be generated from this module...
o added jboss-mq and jboss-docs to the snapshot list
Revision ChangesPath
1.11 +91 -120 build/website/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/build/website/build.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- build.xml 2001/09/27 22:44:33 1.10
+++ build.xml 2001/10/02 00:15:38 1.11
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.10 2001/09/27 22:44:33 user57 Exp $ --
+!-- $Id: build.xml,v 1.11 2001/10/02 00:15:38 user57 Exp $ --
project default=main name=JBoss Website/Build
@@ -139,7 +139,7 @@
!-- Module name(s) version --
property name=module.name value=jboss-website/
property name=module.Name value=JBoss Website/
-property name=module.version value=unspecified/
+property name=module.version value=DEV/
!-- Invoke the rest of the configuration targets --
call target=_configure-tools/
@@ -158,87 +158,6 @@
!-- Configure the thirdparty libraries required by this module. --
target name=_configure-libraries unless=configure-libraries.disable
-!-- Java Naming and Directory Interface (JNDI) --
-property name=sun.jndi.root value=${project.thirdparty}/sun/jndi/
-property name=sun.jndi.lib value=${sun.jndi.root}/lib/
-
-!-- Java Management Extensions (JMX) --
-property name=sun.jmx.root value=${project.thirdparty}/sun/jmx/
-property name=sun.jmx.lib value=${sun.jmx.root}/lib/
-
-!-- Java API for XML Processing (JAXP) --
-property name=sun.jaxp.root value=${project.thirdparty}/sun/jaxp/
-property name=sun.jaxp.lib value=${sun.jaxp.root}/lib/
-
-!-- Java Authentication and Authorization Service (JAAS) --
-property name=sun.jaas.root value=${project.thirdparty}/sun/jaas/
-property name=sun.jaas.lib value=${sun.jaas.root}/lib/
-
-!-- JavaBeans Activation Framework (JAF) --
-property name=sun.jaf.root value=${project.thirdparty}/sun/jaf/
-property name=sun.jaf.lib value=${sun.jaf.root}/lib/
-
-!-- JavaMail --
-property name=sun.javamail.root value=${project.thirdparty}/sun/javamail/
-property name=sun.javamail.lib value=${sun.javamail.root}/lib/
-
-!-- Java Transaction Service (JTS) --
-property name=sun.jts.root value=${project.thirdparty}/sun/jts/
-property name=sun.jts.lib value=${sun.jts.root}/lib/
-
-!-- Log4j --
-property name=apache.log4j.root value=${project.thirdparty}/apache/log4j/
-property name=apache.log4j.lib value=${apache.log4j.root}/lib/
-
-!-- EDU.oswego.cs.dl.util.concurrent --
-property name=oswego.concurrent.root
value=${project.thirdparty}/oswego/concurrent/
-property name=oswego.concurrent.lib value=${oswego.concurrent.root}/lib/
-
-!-- JPL-Util --
-property name=gjt.jpl-util.root value=${project.thirdparty}/gjt/jpl-util/
-property name=gjt.jpl-util.lib value=${gjt.jpl-util.root}/lib/
-
-!-- JavaGroups --
-property name=javagroups.javagroups.root
value=${project.thirdparty}/javagroups/javagroups/
-property name=javagroups.javagroups.lib
value=${javagroups.javagroups.root}/lib/
-
-!-- JSR 77 --
-property name=sun.jsr77.root value=${project.thirdparty}/sun/jsr77/
-property name=sun.jsr77.lib value=${sun.jsr77.root}/lib/
-
-!-- gnu.regexp --
-property name=gnu.regexp.root value=${project.thirdparty}/gnu/regexp/
-property name=gnu.regexp.lib value=${gnu.regexp.root}/lib/
-
-!-- Java Secure Socket Extension (JSSE) --
-property name=sun.jsse.root value=${project.thirdparty}/sun/jsse/
-property name=sun.jsse.lib value=${sun.jsse.root}/lib/
-
-!-- Hypersonic SQL --
-property name=hsql.hsql.root value=${project.thirdparty}/hsql/hsql/
-property name=hsql.hsql.lib value=${hsql.hsql.root}/lib/
-
-!-- Instant DB --
-property name=enhydra.instantdb.root
value=${project.thirdparty}/enhydra/instantdb/
-property name=enhydra.instantdb.lib value=${enhydra.instantdb.root}/lib/
-
-!-- Castor --
-property name=exolab.castor.root
value=${project.thirdparty}/exolab/castor/
-property name=exolab.castor.lib value=${exolab.castor.root}/lib/
-
-!-- Tyrex --
-property name=exolab.tyrex.root value=${project.thirdparty}/exolab/tyrex/
-property name=exolab.tyrex.lib
[JBoss-dev] CVS update: build/website/etc local.properties-example
User: user57
Date: 01/10/01 17:15:38
Modified:website/etc local.properties-example
Log:
o added a default value for jivesoftware.jive.home (which is ~/website/jive)
o setup the build module to pull the generated .ear's, soon those .ear's
might be generated from this module...
o added jboss-mq and jboss-docs to the snapshot list
Revision ChangesPath
1.2 +3 -2 build/website/etc/local.properties-example
Index: local.properties-example
===
RCS file: /cvsroot/jboss/build/website/etc/local.properties-example,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- local.properties-example 2001/08/30 22:01:56 1.1
+++ local.properties-example 2001/10/02 00:15:38 1.2
@@ -21,6 +21,7 @@
javac.debug=on
javac.deprecation=on
-### Disable generation of Javadocs ###
+### Where Jive Home Is ##
-javadoc-generated-already=true
+# default to the location on jboss.org
+jivesoftware.jive.home=${user.home}/website/jive
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] doco_files - jboss/manual module
Their location in cvs is irrelevant. All that matters is that the location on the web site doesn't change unless you go through and clean up any links referencing the docs path. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Jason Dillon [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, October 01, 2001 4:55 PM Subject: [JBoss-dev] doco_files - jboss/manual module can we move the doco_files stuff into the jboss/manual module, since that is what those files are relavent too? This would also make it a bit cleaner to generate the .ear deployables, the manual.ear could contain the examples for that version of the manual. If we do something like this, where everything is selfcontained, then we could deploy different versions of the manual (for 2.0.x and 2.2.x and so on). --jason ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: CVSROOT modules
User: user57 Date: 01/10/01 18:01:20 Modified:.modules Log: o jboss/j2ee is required to build the survey for jboss.org Revision ChangesPath 1.62 +1 -0 CVSROOT/modules Index: modules === RCS file: /cvsroot/jboss/CVSROOT/modules,v retrieving revision 1.61 retrieving revision 1.62 diff -u -r1.61 -r1.62 --- modules 2001/10/01 20:56:14 1.61 +++ modules 2001/10/02 01:01:20 1.62 @@ -106,6 +106,7 @@ jboss-website-modules-a \ _jboss_website_build \ _jboss_website_forums \ + _jboss_j2ee \ _jboss_website_survey \ _jboss_website \ _jboss_manual ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbossmq/src/main/org/jboss/mq Connection.java
User: chirino
Date: 01/10/01 20:52:55
Modified:src/main/org/jboss/mq Connection.java
Log:
Reordered the way that I was setting up the ClockDeamon
Revision ChangesPath
1.9 +14 -12jbossmq/src/main/org/jboss/mq/Connection.java
Index: Connection.java
===
RCS file: /cvsroot/jboss/jbossmq/src/main/org/jboss/mq/Connection.java,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- Connection.java 2001/10/01 23:53:33 1.8
+++ Connection.java 2001/10/02 03:52:55 1.9
@@ -38,7 +38,7 @@
*
* @authorNorbert Lataille ([EMAIL PROTECTED])
* @authorHiram Chirino ([EMAIL PROTECTED])
- * @version $Revision: 1.8 $
+ * @version $Revision: 1.9 $
* @created August 16, 2001
*/
public class Connection implements java.io.Serializable, javax.jms.Connection
@@ -1020,18 +1020,20 @@
// ping period is 0.
if( pingPeriod == 0 )
return;
-
- pingTaskId = clockDaemon.executePeriodically(pingPeriod,new PingTask(), true);
- clockDaemon.setThreadFactory(
- new ThreadFactory () {
-public Thread newThread(Runnable r) {
- Thread t = new Thread(threadGroup, r, Connection Monitor Thread);
- t.setDaemon(true);
- return t;
+ if( clockDaemon.getThreadFactory() == null ) {
+ cat.debug(Setting the clockDaemon's thread factory);
+ clockDaemon.setThreadFactory(
+new ThreadFactory () {
+ public Thread newThread(Runnable r) {
+ Thread t = new Thread(threadGroup, r, Connection Monitor
Thread);
+ t.setDaemon(true);
+ return t;
+ }
}
- }
-
- );
+
+ );
+ }
+ pingTaskId = clockDaemon.executePeriodically(pingPeriod,new PingTask(), true);
}
private void stopPingThread() {
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbossmx/src/main/org/jboss/ha/framework/interfaces HAPartition.java HARMIClient.java
User: vlada
Date: 01/10/01 21:05:56
Modified:src/main/org/jboss/ha/framework/interfaces HAPartition.java
HARMIClient.java
Log:
rather than using machine dependent system time to track if client's view of cluster
has changed use logical viewID from cluster
Revision ChangesPath
1.2 +2 -1
jbossmx/src/main/org/jboss/ha/framework/interfaces/HAPartition.java
Index: HAPartition.java
===
RCS file:
/cvsroot/jboss/jbossmx/src/main/org/jboss/ha/framework/interfaces/HAPartition.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- HAPartition.java 2001/09/30 15:19:32 1.1
+++ HAPartition.java 2001/10/02 04:05:56 1.2
@@ -20,7 +20,8 @@
public DistributedReplicantManager getDistributedReplicantManager();
public DistributedState getDistributedStateService ();
-
+ public long getCurrentViewId();
+
// ***
// ***
// RPC multicast communication
1.2 +7 -15
jbossmx/src/main/org/jboss/ha/framework/interfaces/HARMIClient.java
Index: HARMIClient.java
===
RCS file:
/cvsroot/jboss/jbossmx/src/main/org/jboss/ha/framework/interfaces/HARMIClient.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- HARMIClient.java 2001/09/30 15:19:32 1.1
+++ HARMIClient.java 2001/10/02 04:05:56 1.2
@@ -30,7 +30,7 @@
*
* @author a href=mailto:[EMAIL PROTECTED];Sacha Labourey/a
* @author a href=mailto:[EMAIL PROTECTED];Bill Burke/a
- * @version $Revision: 1.1 $
+ * @version $Revision: 1.2 $
*
* pbRevisions:/b
*
@@ -45,7 +45,7 @@
protected String key = null;
protected ArrayList targets = null;
protected LoadBalancePolicy loadBalancePolicy;
- protected transient long tag = 0;
+ protected transient long currentViewId = 0;
protected transient Object local = null;
public HARMIClient ()
@@ -89,16 +89,7 @@
targets.addAll (newTargets);
}
}
-
- public long getTag ()
- {
- return tag;
- }
-
- public void setTag (long tag)
- {
- this.tag = tag;
- }
+
public Object getRemoteTarget ()
{
@@ -139,7 +130,8 @@
}
// nothing found
}
-
+
+
public Method findLocalMethod (Method method, Object[] args) throws Exception
{
return method;
@@ -185,12 +177,12 @@
RemoteMethodInvocation rmi = new RemoteMethodInvocation (null, method,
args);
MarshalledObject mo = new MarshalledObject (rmi);
// Is this step actually necessary? Can I just do
method.invoke(target, args); ?
-HARMIResponse rsp = target.invoke (tag, mo);
+HARMIResponse rsp = target.invoke (currentViewId, mo);
if (rsp.newReplicants != null)
{
System.out.println (new set of replicants);
setTargets (rsp.newReplicants);
- setTag (rsp.tag);
+ currentViewId = rsp.currentViewId;
}
return rsp.response;
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbossmx/src/main/org/jboss/ha/framework/server HAPartitionImpl.java HARMIServerImpl.java
User: vlada
Date: 01/10/01 21:06:47
Modified:src/main/org/jboss/ha/framework/server HAPartitionImpl.java
HARMIServerImpl.java
Log:
rather than using machine dependent system time to track if client's view of cluster
has changed use logical viewID from cluster
Revision ChangesPath
1.2 +10 -3
jbossmx/src/main/org/jboss/ha/framework/server/HAPartitionImpl.java
Index: HAPartitionImpl.java
===
RCS file:
/cvsroot/jboss/jbossmx/src/main/org/jboss/ha/framework/server/HAPartitionImpl.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- HAPartitionImpl.java 2001/09/30 15:20:58 1.1
+++ HAPartitionImpl.java 2001/10/02 04:06:47 1.2
@@ -198,7 +198,12 @@
{
return this.dsManager;
}
-
+
+ public long getCurrentViewId()
+ {
+ return channel.GetView().GetVid().GetId();
+ }
+
// ***
// ***
// RPC multicast communication
@@ -424,8 +429,10 @@
newMembers.add (allMembers.elementAt (i));
return newMembers;
}
-
-
+
+
+
+
///
/**
1.2 +5 -10
jbossmx/src/main/org/jboss/ha/framework/server/HARMIServerImpl.java
Index: HARMIServerImpl.java
===
RCS file:
/cvsroot/jboss/jbossmx/src/main/org/jboss/ha/framework/server/HARMIServerImpl.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- HARMIServerImpl.java 2001/09/30 15:20:58 1.1
+++ HARMIServerImpl.java 2001/10/02 04:06:47 1.2
@@ -40,7 +40,6 @@
DistributedReplicantManager.ReplicantListener
{
protected String replicantName;
- protected long lastSet = System.currentTimeMillis ();
protected ArrayList replicants = new ArrayList ();
protected Object handler;
protected HashMap invokerMap = new HashMap ();
@@ -100,12 +99,8 @@
e.printStackTrace ();
}
}
+
- public long getTag ()
- {
- return lastSet;
- }
-
public Object getLocal () throws Exception
{
return handler;
@@ -121,10 +116,9 @@
replicants.clear ();
replicants.addAll (newReplicants);
}
- lastSet = System.currentTimeMillis ();
}
- public HARMIResponse invoke (long tag, MarshalledObject mimo) throws Exception
+ public HARMIResponse invoke (long clientViewId, MarshalledObject mimo) throws
Exception
{
RemoteMethodInvocation rmi = (RemoteMethodInvocation)mimo.get ();
rmi.setMethodMap (invokerMap);
@@ -133,10 +127,11 @@
try
{
HARMIResponse rsp = new HARMIResponse ();
- if (tag lastSet)
+ long clusterViewId = partition.getCurrentViewId();
+ if (clientViewId != clusterViewId)
{
rsp.newReplicants = new ArrayList (replicants);
-rsp.tag = lastSet;
+rsp.currentViewId = clusterViewId;
}
rsp.response = method.invoke (handler, rmi.getArguments ());
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbossmx/src/main/org/jboss/ha/framework/interfaces HARMIResponse.java
User: vlada Date: 01/10/01 21:06:18 Modified:src/main/org/jboss/ha/framework/interfaces HARMIResponse.java Log: rather than using machine dependent system time to track if client's view of cluster has changed use logical viewID from cluster Revision ChangesPath 1.2 +1 -1 jbossmx/src/main/org/jboss/ha/framework/interfaces/HARMIResponse.java Index: HARMIResponse.java === RCS file: /cvsroot/jboss/jbossmx/src/main/org/jboss/ha/framework/interfaces/HARMIResponse.java,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- HARMIResponse.java2001/09/30 15:19:32 1.1 +++ HARMIResponse.java2001/10/02 04:06:18 1.2 @@ -8,7 +8,7 @@ public ArrayList newReplicants = null; - public long tag = 0; + public long currentViewId = 0; public Object response = null; ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] tracking client's view of cluster using viewID
Hey Bill Sacha, As per our earlier conversation, I made this change in RH. I ran unit test and could not notice any unexpected behaviour. Vladimir Date: Mon, 1 Oct 2001 15:34:08 -0400 From: Bill Burke [EMAIL PROTECTED] To: Vladimir Blagojevic [EMAIL PROTECTED] Cc: Sacha Labourey [EMAIL PROTECTED] Subject: RE: Feedback Yes this is much better. Thanks. Keep it coming... Bill -Original Message- From: Vladimir Blagojevic [mailto:[EMAIL PROTECTED]] Sent: Monday, October 01, 2001 3:02 PM To: Bill Burke Cc: Sacha Labourey Subject: RE: Feedback Hey, viewId, is this a JG thing? Yes, that would probably be better. Yeah it is from JG. All members are in virtual synchrony, all see same views hence viewID is same across members until it changes by join/crash etc. Quick check on API . ViewId as object is retrievable from JChannel which is available from HARMIPartition. I'd use only public long ViewId.getId() to get long value viewId rather than whole object ViewId. Stuff this long value in HARMClient and upon replicant update check if clients viewid long is equal to the one we have on server , if not update client's recipient stubs. Seems ok? Vladimir ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results
JBoss daily test results SUMMARY Number of tests run: 21 Successful tests: 15 Errors:6 Failures: 0 [time of test: 2 October 2001 7:13 GMT] [java.version: 1.3.0] [java.vendor: IBM Corporation] [java.vm.version: 1.3.0] [java.vm.name: Classic VM] [java.vm.info: J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)] [os.name: Linux] [os.arch: x86] [os.version: 2.4.3-12] See http://lubega.com for full details 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 [details not shown - as this makes the mail too big to reach the sf mailing list] ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-467065 ] JAAS module not working w/ 2.4.2 TC4.0
Bugs item #467065, was opened at 2001-10-01 21:16 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=467065group_id=22866 Category: JBossSX Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Jason Vasquez (jpvasquez) Assigned to: Nobody/Anonymous (nobody) Summary: JAAS module not working w/ 2.4.2 TC4.0 Initial Comment: Using the recently released JBoss2.4.2/Tomcat 4.0 bundle, a custom JAAS module that was previously working with bundled JBoss2.4+/Jetty no longer works. When accessing a secured web resource, the JBoss console shows these messages: [JaasSecurityManagerService] Created securityMgr=org.jboss.security.plugins.JaasSecurityMana ger@406258 [JaasSecurityManagerService] setCachePolicy, c=null [JaasSecurityManagerService] Added my_module_config_name, org.jboss.security.plugins.JaasSecurityManager@406258 to map [Default] Bad password for username=null And a 403 error goes to the browser: HTTP Status 403 - Access to the requested resource has been denied JNDIView does show the module added to the java:/jaas tree, so I'm not sure what's going on here. (By the way, if it helps, the custom module is a small extension to the LDAP login module delivered with 2.4.1, which was required to work with our environment) Let me know if I can provide any additional information which might help. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=467065group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
