Re: [JBoss-dev] Webconsole Snapshot Recording of JMX attributes
Sacha, do you remember what drove your decision to use Swing for the management tree in the web console? The reason why I am asking is because we (in our company) had to go through a long and painful round of experiments and prototypes comparing the feasibility of DHTML vs Swing for a big project. One of the prototypes showed how to efficiently implement dynamic tree that updates some of its nodes over time. At the end, DHTML came ahead because of its better cross-browser, cross-platform availability, compared to java plug-ins. Although it is much less pleasent to code to. Ivelin --- Bill Burke <[EMAIL PROTECTED]> wrote: > The web-console framework is Sacha's baby. I've > just added shit. > > Ivelin Ivanov wrote: > > > Cool. > > I assume this is a feature of the web console, not > the > > jmx console? > > > > BTW, how did you make the decision to use a java > > applet in the web console vs. dhtml? > > > > Ivelin > > > > > > --- Bill Burke <[EMAIL PROTECTED]> wrote: > > > >>Hi all, > >> > >>I just committed the ability to do snapshot > >>recordings of any JMX > >>attribute within the web-console. > >> > >>To use it, you right-click a JMX attribute and > >>choose the "create > >>snapshot" item. > >> > >> From there you can start/stop snapshotting. > Review > >>the dataset and > >>Graph the dataset. > >> > >>This is currently only available in Branch_3_2 and > >>will be released with > >>3.2.4 (or the next RC of 3.2.4) > >> > >>Regards, > >> > >> > >>Bill > >> > >> > >> > >> > >> > >> > > > > > --- > > > >>This SF.net email is sponsored by: IBM Linux > >>Tutorials. > >>Become an expert in LINUX or just sharpen your > >>skills. Sign up for IBM's > >>Free Linux Tutorials. Learn everything from the > >>bash shell to sys admin. > >>Click now! > >> > > > > > http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > > > >>___ > >>JBoss-Development mailing list > >>[EMAIL PROTECTED] > >> > > > > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > > > > --- > > This SF.net email is sponsored by: IBM Linux > Tutorials. > > Become an expert in LINUX or just sharpen your > skills. Sign up for IBM's > > Free Linux Tutorials. Learn everything from the > bash shell to sys admin. > > Click now! > http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > > ___ > > JBoss-Development mailing list > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > -- > > Bill Burke > Chief Architect > JBoss Group LLC. > > > > > > --- > This SF.net email is sponsored by: IBM Linux > Tutorials. > Become an expert in LINUX or just sharpen your > skills. Sign up for IBM's > Free Linux Tutorials. Learn everything from the > bash shell to sys admin. > Click now! > http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > ___ > JBoss-Development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Web integration (clustering) updates
Hi, I saw some updates here to the web clustering code from Thomas: User: tpeuss Date: 04/01/04 03:54:01 Modified:src/main/org/jboss/web/tomcat/session Tag: Branch_3_2 ClusterManager.java ClusteredSession.java Log: Change for bug #863113. This patch adds a new configuration option (UseLocalCache) to the clustering code. Setting this option to false forces the clustering code to look into the distributed store on every access and to replicate the session on every access. This is useful in a non-sticky session environment but costs performance. By default this option is true. IMO, the TC 5 code which I ported should be kept in sync (it's in src/main/org/jboss/web/tomcat/tc5/session). Also, would it be possible to test it so that the TC 5 integration has the same features as TC 4.1 ? I don't quite have the right setup myself. Would it be possible to switch to TC 5 for JB 3.2.4 (assuming there's someone to test and bugfix the clustering code) ? I did add the JSR 77 stats, so the web console works and has the same stats as with TC 4.1 now. BTW, what about the classloading failure I posted two days ago ? I did find a workaround for it but it's not very clean. -- x Rémy Maucherat Senior Developer & Consultant JBoss Group (Europe) SàRL x --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] New JBoss Monitoring services
Scott, Bill, what do you guys think? Does a native wrapper make sense for restart or it is better to keep it pure java and get away without restarting the vm? Jeff's reasoning makes sense to me. On the other hand though a native ingredient may reduce the overall perception that JBoss is platform independent all the way. If you noticed the Web Sphere announcement, they list a dozen operating systems as certified. Ivelin --- Jeff Haynie <[EMAIL PROTECTED]> wrote: > The java wrapper uses native code to start the JVM > and handles natively > restart, etc. You basically implement simple Java > class that has a > start and stop method and we just then call the > appropriate method in > Server to control jboss - which then goes through > the normal lifecycle. > > The trick, however, is to continue to notify the > service controller of > your status -- which the java wrapper stuff exposes > a java method to > give him hints on start / stop status. This is > important in windows > services to get the appopriate status and to make > sure the Windows > Service Manager doesn't think you're ignoring him. > > Jeff > > > > Ivelin Ivanov wrote: > > >Would it use native code to restart the JBoss > services > >or would it just ask the deployers to undeploy and > >redeploy all services? > > > >Ivelin > > > > > > > >--- Jeff Haynie <[EMAIL PROTECTED]> wrote: > > > > > >>We use > >>http://wrapper.tanukisoftware.org/doc/english/ > with > >>JBoss on both > >>Windows and Linux and it handles all of this > >>out-of-the-box (restart > >>failure, retry logic, etc.) > >> > >>I would recommend it instead of rolling your own. > >>They've even got a > >>MBean for managing restarts, etc. > >> > >>I'll be glad to contribute / patch our jboss > >>startup/shutdown wrapper > >>around ServerImpl that controls the service > manager > >>lifecycle if it > >>would help. > >> > >>Jeff > >> > >>Ivelin Ivanov wrote: > >> > >> > > > > > --- > This SF.net email is sponsored by: IBM Linux > Tutorials. > Become an expert in LINUX or just sharpen your > skills. Sign up for IBM's > Free Linux Tutorials. Learn everything from the > bash shell to sys admin. > Click now! > http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > ___ > JBoss-Development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss Test Results: 95 % ( 1462 / 1536 ) - nearly there - who is gonna get us to 100%!. JBoss (HEAD/linux1/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Wed Jan 7 04:43:00 GMT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 1536 Successful tests: 1462 Errors:56 Failures: 18 [time of test: 2004-01-07.02-52 GMT] [java.version: 1.4.2_01] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.2_01-b06] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.20-27.7] Useful resources: - http://jboss.kimptoc.net/linux1/1.4.2_01/logtests/testresults/reports/html//2004-01-07.02-52 for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: org.jboss.test.cache.test.local.TxConcurrentUnitTestCase Test:unknown Type:error Exception: junit.framework.AssertionFailedError Message: Timeout occurred - Suite: org.jboss.test.classloader.test.ScopingUnitTestCase Test:testWarXmlOverrides Type:error Exception: java.net.MalformedURLException Message: no protocol: /home/jbossci/jbossci2/jboss-head-test/testsuite/output/lib/oldxerces.war - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testSetUp Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyCMPField Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyEntityCMPFieldChange Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyEntityCreate Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] === Wed Jan 7 04:43:00 GMT 2004 === Linux nog.kimptoc.net 2.4.20-27.7 #1 Thu Dec 11 15:04:48 EST 2003 i686 unknown === java -version java version "1.4.2_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_01-b06) Java HotSpot(TM) Client VM (build 1.4.2_01-b06, mixed mode) --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] New JBoss Monitoring services
Does it have threshold and alert notification as well? Tom was telling me about your stuff. Let us know what you want to contribute and how it can/would fit. FYI, the graphing stuff was butt easy to do. www.jfree.org Thanks, Bill Jeff Haynie wrote: We also have written a native (via JNI) library for getting all the system level information such as CPU load, handles, threads, memory, etc. and we have a framework that fires JMX snapshot notifications (configurable). Our management server then monitors these snapshots and our analytics server records them in a DB for trending. Our management GUI (in Swing) can display near real-time machine information for each jboss server on the network - all with graphing, etc. much like task manager in Windows. I can potentially contribute some of this if helpful too. Jeff Ivelin Ivanov wrote: Very nice, Bill. Email notifications when memoty is low will be very useful. Is there a CPU utilization monitor as well? Scott and I talked some time ago about a heart watch service which will restart the server when the memory is too low or the CPU is pegged for too long. Your work will be of help. Do you have some thoughts what is an appropriate way to restart the server. Not restart the JVM, but just undeploy everything and deploy it again. Ivelin --- Jae Gangemi <[EMAIL PROTECTED]> wrote: agreed - i can't wait to start playing w/ it. any proposed ETA for 3.2.4? -jae -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ben Sabrin Sent: Tuesday, January 06, 2004 3:00 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] New JBoss Monitoring services Well done Bill, this is good stuff:) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Friday, December 12, 2003 4:24 PM To: Jboss-Dev; JBoss 2; [EMAIL PROTECTED] Subject: [JBoss-dev] New JBoss Monitoring services This will be released in JBoss 3.2.4, but it is now available in 3.2 branch: cvs checkout -r Branch_3_2 jboss-3.2 I've also attached some screen shots JBoss Monitoring In JBoss 3.2.4, we've implemented some new JMX MBean monitoring and a nice GUI around this infrastructure as well as a way to plug in how alerts are processed. Why didn't we use the JMX Gauge and String monitors that come implemented with the JMX spec? 3 reasons: 1. They are not integrated with our Service architecture 2. They have no way of determining which monitors have sent an alert and are currently disabled because an alert was reached 3. They have no way of reseting an alert So, what infrastructure have we built? First let's look at configuring a JMX MBean monitor through the plain old -service.xml interface that you would to create any MBean. All Monitors are MBeans that start a thread to watch the values of another MBean's attribute. When a monitoring threshold is reached, the MOnitor will send out an MBean Notification to a set of registered listeners. Currently in JBoss, the are two types of listeners, a dumb Console listener, and an Email listener which will send out an email whenever an alert is received. Of course, the messages are fully configurable. Numeric Attribute Monitors The first type of monitor is a org.jboss.monitor.ThresholdMonitor that is used to track Numberic MBean attributes. Here is an example configuration of a monitor of free available memory. It will send a JMX Notification when free memory goes below one megabyte. The MBean it is watching over that has this particular stat is jboss.system:type=ServerInfo. File: FreeMemory_Monitor-service.xml FreeMemory Monitor name="ObservedObject">jboss.system:type=ServerInfo FreeMemory 100 1 1000 true jboss.alerts:service=ConsoleAlertListener -list-element> jboss.alerts:service=EmailAlertListener ist-element> Let's walk through each attribute: FreeMemory The display name in which this monitor will be shown in the web-console. If you create monitors by hand you can have it managed by the web-console if you have one monitor defined in one file only and the name of the file is the same name as the monitor and the file lives in ./deploy/management/monitors/ So The above example the filename should be FreeMemory_Monitor-service.xml, notice that whitespace is substituted with an '_' charater. name="ObservedObject">jboss.system:type=ServerInfo FreeMemory These are the MBean and the MBean attribute this monitor will watch. If the MBean is a ServiceMBean then you should make this a so that this monitor doesn't start before the watched MBean is loaded. 100 1 The Threshold is the value threshold of the attribute. The CompareTo is a numeric value, -1 means > (greater than), 0 means = (equal), 1 means (less than). These are the same values used by Java comparators. So in this example, when the FreeMemory attribute is less than 100 a JMX notification will be sent. 1000 Th
Re: [JBoss-dev] If JSR-77 stats were mbeans...
No, they are available as datastructure I thought? Sacha Labourey wrote: But it is already like that, no?!? - Original Message - From: "Bill Burke" <[EMAIL PROTECTED]> To: "Jboss-Dev" <[EMAIL PROTECTED]> Sent: Tuesday, January 06, 2004 11:52 PM Subject: [JBoss-dev] If JSR-77 stats were mbeans... If JSR-77 stats were mbeans then we could use all the monitoring, snapshotting and graphing features. Is it feasible to make current MBeans that manage EJBs, JMS, etc... implement the JSR-77 interfaces and expose these stats as JMX attributes? Just a thought and I haven't put any research at all to see whether this was feasible or not. Just thought I would throw it out. Bill -- Bill Burke Chief Architect JBoss Group LLC. --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development -- Bill Burke Chief Architect JBoss Group LLC. --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Webconsole Snapshot Recording of JMX attributes
The web-console framework is Sacha's baby. I've just added shit. Ivelin Ivanov wrote: Cool. I assume this is a feature of the web console, not the jmx console? BTW, how did you make the decision to use a java applet in the web console vs. dhtml? Ivelin --- Bill Burke <[EMAIL PROTECTED]> wrote: Hi all, I just committed the ability to do snapshot recordings of any JMX attribute within the web-console. To use it, you right-click a JMX attribute and choose the "create snapshot" item. From there you can start/stop snapshotting. Review the dataset and Graph the dataset. This is currently only available in Branch_3_2 and will be released with 3.2.4 (or the next RC of 3.2.4) Regards, Bill --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development -- Bill Burke Chief Architect JBoss Group LLC. --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] New JBoss Monitoring services
The java wrapper uses native code to start the JVM and handles natively restart, etc. You basically implement simple Java class that has a start and stop method and we just then call the appropriate method in Server to control jboss - which then goes through the normal lifecycle. The trick, however, is to continue to notify the service controller of your status -- which the java wrapper stuff exposes a java method to give him hints on start / stop status. This is important in windows services to get the appopriate status and to make sure the Windows Service Manager doesn't think you're ignoring him. Jeff Ivelin Ivanov wrote: Would it use native code to restart the JBoss services or would it just ask the deployers to undeploy and redeploy all services? Ivelin --- Jeff Haynie <[EMAIL PROTECTED]> wrote: We use http://wrapper.tanukisoftware.org/doc/english/ with JBoss on both Windows and Linux and it handles all of this out-of-the-box (restart failure, retry logic, etc.) I would recommend it instead of rolling your own. They've even got a MBean for managing restarts, etc. I'll be glad to contribute / patch our jboss startup/shutdown wrapper around ServerImpl that controls the service manager lifecycle if it would help. Jeff Ivelin Ivanov wrote: --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] New JBoss Monitoring services
Would it use native code to restart the JBoss services or would it just ask the deployers to undeploy and redeploy all services? Ivelin --- Jeff Haynie <[EMAIL PROTECTED]> wrote: > We use > http://wrapper.tanukisoftware.org/doc/english/ with > JBoss on both > Windows and Linux and it handles all of this > out-of-the-box (restart > failure, retry logic, etc.) > > I would recommend it instead of rolling your own. > They've even got a > MBean for managing restarts, etc. > > I'll be glad to contribute / patch our jboss > startup/shutdown wrapper > around ServerImpl that controls the service manager > lifecycle if it > would help. > > Jeff > > Ivelin Ivanov wrote: > > >Very nice, Bill. > > > >Email notifications when memoty is low will be very > >useful. > > > >Is there a CPU utilization monitor as well? > > > >Scott and I talked some time ago about a heart > watch > >service which will restart the server when the > memory > >is too low or the CPU is pegged for too long. > > > >Your work will be of help. > > > >Do you have some thoughts what is an appropriate > way > >to restart the server. Not restart the JVM, but > just > >undeploy everything and deploy it again. > > > > > >Ivelin > > > > > >--- Jae Gangemi <[EMAIL PROTECTED]> wrote: > > > > > >> agreed - i can't wait to start playing w/ it. > >> > >> any proposed ETA for 3.2.4? > >> > >>-jae > >> > >>-Original Message- > >>From: > [EMAIL PROTECTED] > >> > >> > >> > >[mailto:[EMAIL PROTECTED] > > > > > >>On Behalf Of Ben > >>Sabrin > >>Sent: Tuesday, January 06, 2004 3:00 PM > >>To: [EMAIL PROTECTED] > >>Subject: RE: [JBoss-dev] New JBoss Monitoring > >>services > >> > >> > >>Well done Bill, this is good stuff:) > >> > >>-Original Message- > >>From: > [EMAIL PROTECTED] > >> > >> > >> > >[mailto:[EMAIL PROTECTED] > > > > > >>On Behalf Of Bill > >>Burke > >>Sent: Friday, December 12, 2003 4:24 PM > >>To: Jboss-Dev; JBoss 2; [EMAIL PROTECTED] > >>Subject: [JBoss-dev] New JBoss Monitoring services > >> > >>This will be released in JBoss 3.2.4, but it is > now > >>available in 3.2 > >>branch: cvs checkout -r Branch_3_2 jboss-3.2 > >> > >>I've also attached some screen shots > >> > >> > >>JBoss Monitoring > >> > >>In JBoss 3.2.4, we've implemented some new JMX > MBean > >>monitoring and a > >>nice GUI around this infrastructure as well as a > way > >>to plug in how > >>alerts are processed. Why didn't we use the JMX > >>Gauge and String > >>monitors that come implemented with the JMX spec? > 3 > >>reasons: > >> > >>1. They are not integrated with our Service > >>architecture > >>2. They have no way of determining which monitors > >>have sent an alert and > >>are currently disabled because an alert was > reached > >>3. They have no way > >>of reseting an alert > >> > >>So, what infrastructure have we built? First > let's > >>look at configuring > >>a JMX MBean monitor through the plain old > >>-service.xml interface that > >>you would to create any MBean. > >> > >>All Monitors are MBeans that start a thread to > watch > >>the values of > >>another MBean's attribute. When a monitoring > >>threshold is reached, the > >>MOnitor will send out an MBean Notification to a > set > >>of registered > >>listeners. Currently in JBoss, the are two types > of > >>listeners, a dumb > >>Console listener, and an Email listener which will > >>send out an email > >>whenever an alert is received. Of course, the > >>messages are fully > >>configurable. > >> > >> > >>Numeric Attribute Monitors > >>The first type of monitor is a > >>org.jboss.monitor.ThresholdMonitor that > >>is used to track Numberic MBean attributes. Here > is > >>an example > >>configuration of a monitor of free available > memory. > >> It will send a JMX > >> > >>Notification when free memory goes below one > >>megabyte. The MBean it is > >>watching over that has this particular stat is > >>jboss.system:type=ServerInfo. > >> > >>File: FreeMemory_Monitor-service.xml > >> > >> > >> > >> >>name="jboss.monitor:service=FreeMemory"> > >> FreeMemory > >>Monitor > >>>> > >> > >> > >name="ObservedObject">jboss.system:type=ServerInfo > > > > > >>>>name="ObservedAttribute">FreeMemory > >> 100 > >> 1 > >> 1000 > >> true > >>>>optional-attribute-name="AlertListeners"> > >> > >> > >> > >> > >jboss.alerts:service=ConsoleAlertListener > > > > >>-list-element> > >> > >> > >> > >> > >jboss.alerts:service=EmailAlertListener > > > > >>ist-element> > >> > >> > === message truncated === --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] ht
Re: [JBoss-dev] New JBoss Monitoring services
We also have written a native (via JNI) library for getting all the system level information such as CPU load, handles, threads, memory, etc. and we have a framework that fires JMX snapshot notifications (configurable). Our management server then monitors these snapshots and our analytics server records them in a DB for trending. Our management GUI (in Swing) can display near real-time machine information for each jboss server on the network - all with graphing, etc. much like task manager in Windows. I can potentially contribute some of this if helpful too. Jeff Ivelin Ivanov wrote: Very nice, Bill. Email notifications when memoty is low will be very useful. Is there a CPU utilization monitor as well? Scott and I talked some time ago about a heart watch service which will restart the server when the memory is too low or the CPU is pegged for too long. Your work will be of help. Do you have some thoughts what is an appropriate way to restart the server. Not restart the JVM, but just undeploy everything and deploy it again. Ivelin --- Jae Gangemi <[EMAIL PROTECTED]> wrote: agreed - i can't wait to start playing w/ it. any proposed ETA for 3.2.4? -jae -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ben Sabrin Sent: Tuesday, January 06, 2004 3:00 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] New JBoss Monitoring services Well done Bill, this is good stuff:) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Friday, December 12, 2003 4:24 PM To: Jboss-Dev; JBoss 2; [EMAIL PROTECTED] Subject: [JBoss-dev] New JBoss Monitoring services This will be released in JBoss 3.2.4, but it is now available in 3.2 branch: cvs checkout -r Branch_3_2 jboss-3.2 I've also attached some screen shots JBoss Monitoring In JBoss 3.2.4, we've implemented some new JMX MBean monitoring and a nice GUI around this infrastructure as well as a way to plug in how alerts are processed. Why didn't we use the JMX Gauge and String monitors that come implemented with the JMX spec? 3 reasons: 1. They are not integrated with our Service architecture 2. They have no way of determining which monitors have sent an alert and are currently disabled because an alert was reached 3. They have no way of reseting an alert So, what infrastructure have we built? First let's look at configuring a JMX MBean monitor through the plain old -service.xml interface that you would to create any MBean. All Monitors are MBeans that start a thread to watch the values of another MBean's attribute. When a monitoring threshold is reached, the MOnitor will send out an MBean Notification to a set of registered listeners. Currently in JBoss, the are two types of listeners, a dumb Console listener, and an Email listener which will send out an email whenever an alert is received. Of course, the messages are fully configurable. Numeric Attribute Monitors The first type of monitor is a org.jboss.monitor.ThresholdMonitor that is used to track Numberic MBean attributes. Here is an example configuration of a monitor of free available memory. It will send a JMX Notification when free memory goes below one megabyte. The MBean it is watching over that has this particular stat is jboss.system:type=ServerInfo. File: FreeMemory_Monitor-service.xml FreeMemory Monitor name="ObservedObject">jboss.system:type=ServerInfo FreeMemory 100 1 1000 true jboss.alerts:service=ConsoleAlertListener -list-element> jboss.alerts:service=EmailAlertListener ist-element> Let's walk through each attribute: FreeMemory The display name in which this monitor will be shown in the web-console. If you create monitors by hand you can have it managed by the web-console if you have one monitor defined in one file only and the name of the file is the same name as the monitor and the file lives in ./deploy/management/monitors/ So The above example the filename should be FreeMemory_Monitor-service.xml, notice that whitespace is substituted with an '_' charater. name="ObservedObject">jboss.system:type=ServerInfo FreeMemory These are the MBean and the MBean attribute this monitor will watch. If the MBean is a ServiceMBean then you should make this a so that this monitor doesn't start before the watched MBean is loaded. 100 1 The Threshold is the value threshold of the attribute. The CompareTo is a numeric value, -1 means > (greater than), 0 means = (equal), 1 means (less than). These are the same values used by Java comparators. So in this example, when the FreeMemory attribute is less than 100 a JMX notification will be sent. 1000 The MBean creates a thread that will wake up every so often to check the threshold against the MBean attribute it is watching. The Period is the time in milliseconds this thread will sleep. true Enabled determi
Re: [JBoss-dev] New JBoss Monitoring services
We use http://wrapper.tanukisoftware.org/doc/english/ with JBoss on both Windows and Linux and it handles all of this out-of-the-box (restart failure, retry logic, etc.) I would recommend it instead of rolling your own. They've even got a MBean for managing restarts, etc. I'll be glad to contribute / patch our jboss startup/shutdown wrapper around ServerImpl that controls the service manager lifecycle if it would help. Jeff Ivelin Ivanov wrote: Very nice, Bill. Email notifications when memoty is low will be very useful. Is there a CPU utilization monitor as well? Scott and I talked some time ago about a heart watch service which will restart the server when the memory is too low or the CPU is pegged for too long. Your work will be of help. Do you have some thoughts what is an appropriate way to restart the server. Not restart the JVM, but just undeploy everything and deploy it again. Ivelin --- Jae Gangemi <[EMAIL PROTECTED]> wrote: agreed - i can't wait to start playing w/ it. any proposed ETA for 3.2.4? -jae -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ben Sabrin Sent: Tuesday, January 06, 2004 3:00 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] New JBoss Monitoring services Well done Bill, this is good stuff:) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Friday, December 12, 2003 4:24 PM To: Jboss-Dev; JBoss 2; [EMAIL PROTECTED] Subject: [JBoss-dev] New JBoss Monitoring services This will be released in JBoss 3.2.4, but it is now available in 3.2 branch: cvs checkout -r Branch_3_2 jboss-3.2 I've also attached some screen shots JBoss Monitoring In JBoss 3.2.4, we've implemented some new JMX MBean monitoring and a nice GUI around this infrastructure as well as a way to plug in how alerts are processed. Why didn't we use the JMX Gauge and String monitors that come implemented with the JMX spec? 3 reasons: 1. They are not integrated with our Service architecture 2. They have no way of determining which monitors have sent an alert and are currently disabled because an alert was reached 3. They have no way of reseting an alert So, what infrastructure have we built? First let's look at configuring a JMX MBean monitor through the plain old -service.xml interface that you would to create any MBean. All Monitors are MBeans that start a thread to watch the values of another MBean's attribute. When a monitoring threshold is reached, the MOnitor will send out an MBean Notification to a set of registered listeners. Currently in JBoss, the are two types of listeners, a dumb Console listener, and an Email listener which will send out an email whenever an alert is received. Of course, the messages are fully configurable. Numeric Attribute Monitors The first type of monitor is a org.jboss.monitor.ThresholdMonitor that is used to track Numberic MBean attributes. Here is an example configuration of a monitor of free available memory. It will send a JMX Notification when free memory goes below one megabyte. The MBean it is watching over that has this particular stat is jboss.system:type=ServerInfo. File: FreeMemory_Monitor-service.xml FreeMemory Monitor name="ObservedObject">jboss.system:type=ServerInfo FreeMemory 100 1 1000 true jboss.alerts:service=ConsoleAlertListener -list-element> jboss.alerts:service=EmailAlertListener ist-element> Let's walk through each attribute: FreeMemory The display name in which this monitor will be shown in the web-console. If you create monitors by hand you can have it managed by the web-console if you have one monitor defined in one file only and the name of the file is the same name as the monitor and the file lives in ./deploy/management/monitors/ So The above example the filename should be FreeMemory_Monitor-service.xml, notice that whitespace is substituted with an '_' charater. name="ObservedObject">jboss.system:type=ServerInfo FreeMemory These are the MBean and the MBean attribute this monitor will watch. If the MBean is a ServiceMBean then you should make this a so that this monitor doesn't start before the watched MBean is loaded. 100 1 The Threshold is the value threshold of the attribute. The CompareTo is a numeric value, -1 means > (greater than), 0 means = (equal), 1 means (less than). These are the same values used by Java comparators. So in this example, when the FreeMemory attribute is less than 100 a JMX notification will be sent. 1000 The MBean creates a thread that will wake up every so often to check the threshold against the MBean attribute it is watching. The Period is the time in milliseconds this thread will sleep. true Enabled determines whether or not this monitor should actually monitor. It is the on/off switch of the monitor. jboss.alerts:service=ConsoleAlertLis
[JBoss-dev] JBoss Test Results: 95 % ( 1492 / 1564 ) - nearly there - who is gonna get us to 100%!. JBoss (HEAD/winxp/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Wed Jan 7 03:03:22 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 1564 Successful tests: 1492 Errors:54 Failures: 18 [time of test: 2004-01-07.02-13 GMT] [java.version: 1.4.2_01] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.2_01-b06] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Windows XP] [os.arch: x86] [os.version: 5.1] Useful resources: - http://jboss.kimptoc.net/winxp/1.4.2_01/logtests/testresults/reports/html//2004-01-07.02-13 for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: org.jboss.test.cache.test.local.TxConcurrentUnitTestCase Test:unknown Type:error Exception: junit.framework.AssertionFailedError Message: Timeout occurred - Suite: org.jboss.test.classloader.test.ScopingUnitTestCase Test:testWarXmlOverrides Type:error Exception: java.net.MalformedURLException Message: unknown protocol: d - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testSetUp Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyCMPField Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyEntityCMPFieldChange Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyEntityCreate Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] === Wed Jan 7 03:03:22 GMTST 2004 === CYGWIN_NT-5.1 quarks2 1.5.4(0.94/3/2) 2003-09-12 23:08 i686 unknown unknown Cygwin === java -version java version "1.4.2_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_01-b06) Java HotSpot(TM) Client VM (build 1.4.2_01-b06, mixed mode) --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] New JBoss Monitoring services
Very nice, Bill. Email notifications when memoty is low will be very useful. Is there a CPU utilization monitor as well? Scott and I talked some time ago about a heart watch service which will restart the server when the memory is too low or the CPU is pegged for too long. Your work will be of help. Do you have some thoughts what is an appropriate way to restart the server. Not restart the JVM, but just undeploy everything and deploy it again. Ivelin --- Jae Gangemi <[EMAIL PROTECTED]> wrote: > > agreed - i can't wait to start playing w/ it. > > any proposed ETA for 3.2.4? > > -jae > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > On Behalf Of Ben > Sabrin > Sent: Tuesday, January 06, 2004 3:00 PM > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-dev] New JBoss Monitoring > services > > > Well done Bill, this is good stuff:) > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > On Behalf Of Bill > Burke > Sent: Friday, December 12, 2003 4:24 PM > To: Jboss-Dev; JBoss 2; [EMAIL PROTECTED] > Subject: [JBoss-dev] New JBoss Monitoring services > > This will be released in JBoss 3.2.4, but it is now > available in 3.2 > branch: cvs checkout -r Branch_3_2 jboss-3.2 > > I've also attached some screen shots > > > JBoss Monitoring > > In JBoss 3.2.4, we've implemented some new JMX MBean > monitoring and a > nice GUI around this infrastructure as well as a way > to plug in how > alerts are processed. Why didn't we use the JMX > Gauge and String > monitors that come implemented with the JMX spec? 3 > reasons: > > 1. They are not integrated with our Service > architecture > 2. They have no way of determining which monitors > have sent an alert and > are currently disabled because an alert was reached > 3. They have no way > of reseting an alert > > So, what infrastructure have we built? First let's > look at configuring > a JMX MBean monitor through the plain old > -service.xml interface that > you would to create any MBean. > > All Monitors are MBeans that start a thread to watch > the values of > another MBean's attribute. When a monitoring > threshold is reached, the > MOnitor will send out an MBean Notification to a set > of registered > listeners. Currently in JBoss, the are two types of > listeners, a dumb > Console listener, and an Email listener which will > send out an email > whenever an alert is received. Of course, the > messages are fully > configurable. > > > Numeric Attribute Monitors > The first type of monitor is a > org.jboss.monitor.ThresholdMonitor that > is used to track Numberic MBean attributes. Here is > an example > configuration of a monitor of free available memory. > It will send a JMX > > Notification when free memory goes below one > megabyte. The MBean it is > watching over that has this particular stat is > jboss.system:type=ServerInfo. > > File: FreeMemory_Monitor-service.xml > > > > name="jboss.monitor:service=FreeMemory"> >FreeMemory > Monitor > name="ObservedObject">jboss.system:type=ServerInfo > name="ObservedAttribute">FreeMemory >100 >1 >1000 >true > optional-attribute-name="AlertListeners"> > > jboss.alerts:service=ConsoleAlertListener -list-element> > > jboss.alerts:service=EmailAlertListener ist-element> > > > > > Let's walk through each attribute: > > name="MonitorName">FreeMemory > > The display name in which this monitor will be shown > in the web-console. > > If you create monitors by hand you can have it > managed by the > web-console if you have one monitor defined in one > file only and the > name of the file is the same name as the monitor and > the file lives in > ./deploy/management/monitors/ So The above example > the filename should > be FreeMemory_Monitor-service.xml, notice that > whitespace is substituted > > with an '_' charater. > > > name="ObservedObject">jboss.system:type=ServerInfo > name="ObservedAttribute">FreeMemory > > These are the MBean and the MBean attribute this > monitor will watch. If > > the MBean is a ServiceMBean then you should make > this a optional-attribute> so that this monitor doesn't > start before the > watched MBean is loaded. > >100 >1 > > The Threshold is the value threshold of the > attribute. The CompareTo is > > a numeric value, -1 means > (greater than), 0 means > = (equal), 1 means > (less than). These are the same values used by Java > comparators. So in > > this example, when the FreeMemory attribute is less > than 100 a JMX > notification will be sent. > >1000 > > The MBean creates a thread that will wake up every > so often to check the > > threshold against the MBean attribute it is > watching. The Period is the > > time in milliseconds this thread will sleep. > > >true > > Enabled determines whether or not this monitor > should actually monitor. > It is the on/off sw
RE: [JBoss-dev] New JBoss Monitoring services
Very nice, Bill. Email notifications when memoty is low will be very useful. Is there a CPU utilization monitor as well? Scott and I talked some time ago about a heart watch service which will restart the server when the memory is too low or the CPU is pegged for too long. Your work will be of help. Do you have some thoughts what is an appropriate way to restart the server. Not restart the JVM, but just undeploy everything and deploy it again. Ivelin --- Jae Gangemi <[EMAIL PROTECTED]> wrote: > > agreed - i can't wait to start playing w/ it. > > any proposed ETA for 3.2.4? > > -jae > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > On Behalf Of Ben > Sabrin > Sent: Tuesday, January 06, 2004 3:00 PM > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-dev] New JBoss Monitoring > services > > > Well done Bill, this is good stuff:) > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > On Behalf Of Bill > Burke > Sent: Friday, December 12, 2003 4:24 PM > To: Jboss-Dev; JBoss 2; [EMAIL PROTECTED] > Subject: [JBoss-dev] New JBoss Monitoring services > > This will be released in JBoss 3.2.4, but it is now > available in 3.2 > branch: cvs checkout -r Branch_3_2 jboss-3.2 > > I've also attached some screen shots > > > JBoss Monitoring > > In JBoss 3.2.4, we've implemented some new JMX MBean > monitoring and a > nice GUI around this infrastructure as well as a way > to plug in how > alerts are processed. Why didn't we use the JMX > Gauge and String > monitors that come implemented with the JMX spec? 3 > reasons: > > 1. They are not integrated with our Service > architecture > 2. They have no way of determining which monitors > have sent an alert and > are currently disabled because an alert was reached > 3. They have no way > of reseting an alert > > So, what infrastructure have we built? First let's > look at configuring > a JMX MBean monitor through the plain old > -service.xml interface that > you would to create any MBean. > > All Monitors are MBeans that start a thread to watch > the values of > another MBean's attribute. When a monitoring > threshold is reached, the > MOnitor will send out an MBean Notification to a set > of registered > listeners. Currently in JBoss, the are two types of > listeners, a dumb > Console listener, and an Email listener which will > send out an email > whenever an alert is received. Of course, the > messages are fully > configurable. > > > Numeric Attribute Monitors > The first type of monitor is a > org.jboss.monitor.ThresholdMonitor that > is used to track Numberic MBean attributes. Here is > an example > configuration of a monitor of free available memory. > It will send a JMX > > Notification when free memory goes below one > megabyte. The MBean it is > watching over that has this particular stat is > jboss.system:type=ServerInfo. > > File: FreeMemory_Monitor-service.xml > > > > name="jboss.monitor:service=FreeMemory"> >FreeMemory > Monitor > name="ObservedObject">jboss.system:type=ServerInfo > name="ObservedAttribute">FreeMemory >100 >1 >1000 >true > optional-attribute-name="AlertListeners"> > > jboss.alerts:service=ConsoleAlertListener -list-element> > > jboss.alerts:service=EmailAlertListener ist-element> > > > > > Let's walk through each attribute: > > name="MonitorName">FreeMemory > > The display name in which this monitor will be shown > in the web-console. > > If you create monitors by hand you can have it > managed by the > web-console if you have one monitor defined in one > file only and the > name of the file is the same name as the monitor and > the file lives in > ./deploy/management/monitors/ So The above example > the filename should > be FreeMemory_Monitor-service.xml, notice that > whitespace is substituted > > with an '_' charater. > > > name="ObservedObject">jboss.system:type=ServerInfo > name="ObservedAttribute">FreeMemory > > These are the MBean and the MBean attribute this > monitor will watch. If > > the MBean is a ServiceMBean then you should make > this a optional-attribute> so that this monitor doesn't > start before the > watched MBean is loaded. > >100 >1 > > The Threshold is the value threshold of the > attribute. The CompareTo is > > a numeric value, -1 means > (greater than), 0 means > = (equal), 1 means > (less than). These are the same values used by Java > comparators. So in > > this example, when the FreeMemory attribute is less > than 100 a JMX > notification will be sent. > >1000 > > The MBean creates a thread that will wake up every > so often to check the > > threshold against the MBean attribute it is > watching. The Period is the > > time in milliseconds this thread will sleep. > > >true > > Enabled determines whether or not this monitor > should actually monitor. > It is the on/off sw
Re: [JBoss-dev] Webconsole Snapshot Recording of JMX attributes
Cool. I assume this is a feature of the web console, not the jmx console? BTW, how did you make the decision to use a java applet in the web console vs. dhtml? Ivelin --- Bill Burke <[EMAIL PROTECTED]> wrote: > Hi all, > > I just committed the ability to do snapshot > recordings of any JMX > attribute within the web-console. > > To use it, you right-click a JMX attribute and > choose the "create > snapshot" item. > > From there you can start/stop snapshotting. Review > the dataset and > Graph the dataset. > > This is currently only available in Branch_3_2 and > will be released with > 3.2.4 (or the next RC of 3.2.4) > > Regards, > > > Bill > > > > > > --- > This SF.net email is sponsored by: IBM Linux > Tutorials. > Become an expert in LINUX or just sharpen your > skills. Sign up for IBM's > Free Linux Tutorials. Learn everything from the > bash shell to sys admin. > Click now! > http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > ___ > JBoss-Development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss Test Results: 95 % ( 1463 / 1536 ) - nearly there - who is gonna get us to 100%!. JBoss (HEAD/linux1/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Wed Jan 7 02:23:38 GMT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 1536 Successful tests: 1463 Errors:56 Failures: 17 [time of test: 2004-01-07.00-44 GMT] [java.version: 1.4.1_05] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_05-b01] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.20-27.7] Useful resources: - http://jboss.kimptoc.net/linux1/1.4.1_05/logtests/testresults/reports/html//2004-01-07.00-44 for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: org.jboss.test.cache.test.local.TxConcurrentUnitTestCase Test:unknown Type:error Exception: junit.framework.AssertionFailedError Message: Timeout occurred - Suite: org.jboss.test.classloader.test.ScopingUnitTestCase Test:testWarXmlOverrides Type:error Exception: java.net.MalformedURLException Message: no protocol: /home/jbossci/jbossci2/jboss-head-test/testsuite/output/lib/oldxerces.war - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testSetUp Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyCMPField Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyEntityCMPFieldChange Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyEntityCreate Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] === Wed Jan 7 02:23:38 GMT 2004 === Linux nog.kimptoc.net 2.4.20-27.7 #1 Thu Dec 11 15:04:48 EST 2003 i686 unknown === java -version java version "1.4.1_05" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_05-b01) Java HotSpot(TM) Client VM (build 1.4.1_05-b01, mixed mode) --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss Test Results: 95 % ( 1492 / 1565 ) - nearly there - who is gonna get us to 100%!. JBoss (HEAD/winxp/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Wed Jan 7 01:36:52 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 1565 Successful tests: 1492 Errors:54 Failures: 19 [time of test: 2004-01-07.00-48 GMT] [java.version: 1.4.1_05] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_05-b01] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Windows XP] [os.arch: x86] [os.version: 5.1] Useful resources: - http://jboss.kimptoc.net/winxp/1.4.1_05/logtests/testresults/reports/html//2004-01-07.00-48 for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: org.jboss.test.classloader.test.ScopingUnitTestCase Test:testWarXmlOverrides Type:error Exception: java.net.MalformedURLException Message: unknown protocol: d - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testSetUp Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyCMPField Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyEntityCMPFieldChange Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyEntityCreate Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlySetFK Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] === Wed Jan 7 01:36:53 GMTST 2004 === CYGWIN_NT-5.1 quarks2 1.5.4(0.94/3/2) 2003-09-12 23:08 i686 unknown unknown Cygwin === java -version java version "1.4.1_05" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_05-b01) Java HotSpot(TM) Client VM (build 1.4.1_05-b01, mixed mode) --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/linux1/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Jan 6 23:23:52 GMT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-classes: [mkdir] Created dir: /home/jbossci/jbossci2/jboss-head/naming/output/classes [javac] Compiling 15 source files to /home/jbossci/jbossci2/jboss-head/naming/output/classes compile-rmi: [rmic] RMI Compiling 1 class to /home/jbossci/jbossci2/jboss-head/naming/output/classes compile-etc: [mkdir] Created dir: /home/jbossci/jbossci2/jboss-head/naming/output/etc [copy] Copying 4 files to /home/jbossci/jbossci2/jboss-head/naming/output/etc compile: [mkdir] Created dir: /home/jbossci/jbossci2/jboss-head/naming/output/lib [jar] Building jar: /home/jbossci/jbossci2/jboss-head/naming/output/lib/jnpserver.jar [jar] Building jar: /home/jbossci/jbossci2/jboss-head/naming/output/lib/jnp-client.jar [jar] Building jar: /home/jbossci/jbossci2/jboss-head/naming/output/lib/jnp-tests.jar [touch] Creating /home/jbossci/jbossci2/jboss-head/naming/output/build-marker most: == == Finished with 'most' in module 'naming'. == _module-naming-most: [copy] Copying 1 file to /home/jbossci/jbossci2/jboss-head/build/output/testbuild/lib [copy] Copying 1 file to /home/jbossci/jbossci2/jboss-head/build/output/testbuild/client == == Executing 'most' in module 'remoting'... == _buildmagic:init: configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: /home/jbossci/jbossci2/jboss-head/remoting/output/gen-src (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:/home/jbossci/jbossci2/jboss-head/thirdparty/xdoclet/xdoclet/lib/xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:/home/jbossci/jbossci2/jboss-head/thirdparty/xdoclet/xdoclet/lib/xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:/home/jbossci/jbossci2/jboss-head/thirdparty/xdoclet/xdoclet/lib/xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:/home/jbossci/jbossci2/jboss-head/thirdparty/xdoclet/xdoclet/lib/xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:/home/jbossci/jbossci2/jboss-head/thirdparty/xdoclet/xdoclet/lib/xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:/home/jbossci/jbossci2/jboss-head/thirdparty/xdoclet/xdoclet/lib/xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. INFO:Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: /home/jbossci/jbossci2/jboss-head/remoting/src/main/org/jboss/remoting/transport/Connector.java -->
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/linux1/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Jan 6 23:21:50 GMT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-classes: [mkdir] Created dir: /home/jbossci/jbossci2/jboss-head/naming/output/classes [javac] Compiling 15 source files to /home/jbossci/jbossci2/jboss-head/naming/output/classes compile-rmi: [rmic] RMI Compiling 1 class to /home/jbossci/jbossci2/jboss-head/naming/output/classes compile-etc: [mkdir] Created dir: /home/jbossci/jbossci2/jboss-head/naming/output/etc [copy] Copying 4 files to /home/jbossci/jbossci2/jboss-head/naming/output/etc compile: [mkdir] Created dir: /home/jbossci/jbossci2/jboss-head/naming/output/lib [jar] Building jar: /home/jbossci/jbossci2/jboss-head/naming/output/lib/jnpserver.jar [jar] Building jar: /home/jbossci/jbossci2/jboss-head/naming/output/lib/jnp-client.jar [jar] Building jar: /home/jbossci/jbossci2/jboss-head/naming/output/lib/jnp-tests.jar [touch] Creating /home/jbossci/jbossci2/jboss-head/naming/output/build-marker most: == == Finished with 'most' in module 'naming'. == _module-naming-most: [copy] Copying 1 file to /home/jbossci/jbossci2/jboss-head/build/output/testbuild/lib [copy] Copying 1 file to /home/jbossci/jbossci2/jboss-head/build/output/testbuild/client == == Executing 'most' in module 'remoting'... == _buildmagic:init: configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: /home/jbossci/jbossci2/jboss-head/remoting/output/gen-src (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:/home/jbossci/jbossci2/jboss-head/thirdparty/xdoclet/xdoclet/lib/xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:/home/jbossci/jbossci2/jboss-head/thirdparty/xdoclet/xdoclet/lib/xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:/home/jbossci/jbossci2/jboss-head/thirdparty/xdoclet/xdoclet/lib/xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:/home/jbossci/jbossci2/jboss-head/thirdparty/xdoclet/xdoclet/lib/xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:/home/jbossci/jbossci2/jboss-head/thirdparty/xdoclet/xdoclet/lib/xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:/home/jbossci/jbossci2/jboss-head/thirdparty/xdoclet/xdoclet/lib/xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. INFO:Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: /home/jbossci/jbossci2/jboss-head/remoting/src/main/org/jboss/remoting/transport/Connector.java -->
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Jan 6 23:18:33 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\classes [javac] Compiling 15 source files to D:\jboss\jboss-head\naming\output\classes compile-rmi: [rmic] RMI Compiling 1 class to D:\jboss\jboss-head\naming\output\classes compile-etc: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\etc [copy] Copying 4 files to D:\jboss\jboss-head\naming\output\etc compile: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\lib [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnpserver.jar [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnp-client.jar [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnp-tests.jar [touch] Creating D:\jboss\jboss-head\naming\output\build-marker most: == == Finished with 'most' in module 'naming'. == _module-naming-most: [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\lib [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\client == == Executing 'most' in module 'remoting'... == _buildmagic:init: configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\gen-src (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. INFO:Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\transport\Connector.java --> ConnectorMBean qualified to org.jboss.remoting.transport.ConnectorMBean compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\classes [javac] Compiling 114 source files to D:\jboss\jboss-head\remoting\output\classes D:\jboss\jboss-head\remoting\src\main\o
RE: [JBoss-dev] If JSR-77 stats were mbeans...
I am not sure but I don't think all the stats for JMS have been implemented. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sacha Labourey Sent: 06 January 2004 23:05 To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] If JSR-77 stats were mbeans... But it is already like that, no?!? - Original Message - From: "Bill Burke" <[EMAIL PROTECTED]> To: "Jboss-Dev" <[EMAIL PROTECTED]> Sent: Tuesday, January 06, 2004 11:52 PM Subject: [JBoss-dev] If JSR-77 stats were mbeans... > If JSR-77 stats were mbeans then we could use all the monitoring, > snapshotting and graphing features. Is it feasible to make current > MBeans that manage EJBs, JMS, etc... implement the JSR-77 interfaces and > expose these stats as JMX attributes? Just a thought and I haven't put > any research at all to see whether this was feasible or not. Just > thought I would throw it out. > > Bill > > -- > > Bill Burke > Chief Architect > JBoss Group LLC. > > > > > > --- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > ___ > JBoss-Development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.3.1_09) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Jan 6 23:16:56 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\classes [javac] Compiling 15 source files to D:\jboss\jboss-head\naming\output\classes compile-rmi: [rmic] RMI Compiling 1 class to D:\jboss\jboss-head\naming\output\classes compile-etc: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\etc [copy] Copying 4 files to D:\jboss\jboss-head\naming\output\etc compile: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\lib [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnpserver.jar [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnp-client.jar [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnp-tests.jar [touch] Creating D:\jboss\jboss-head\naming\output\build-marker most: == == Finished with 'most' in module 'naming'. == _module-naming-most: [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\lib [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\client == == Executing 'most' in module 'remoting'... == _buildmagic:init: configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\gen-src (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. INFO:Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\transport\Connector.java --> ConnectorMBean qualified to org.jboss.remoting.transport.ConnectorMBean compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\classes [javac] Compiling 114 source files to D:\jboss\jboss-head\remoting\output\classes D:\jboss\jboss-head\remoting\src\main\o
Re: [JBoss-dev] If JSR-77 stats were mbeans...
But it is already like that, no?!? - Original Message - From: "Bill Burke" <[EMAIL PROTECTED]> To: "Jboss-Dev" <[EMAIL PROTECTED]> Sent: Tuesday, January 06, 2004 11:52 PM Subject: [JBoss-dev] If JSR-77 stats were mbeans... > If JSR-77 stats were mbeans then we could use all the monitoring, > snapshotting and graphing features. Is it feasible to make current > MBeans that manage EJBs, JMS, etc... implement the JSR-77 interfaces and > expose these stats as JMX attributes? Just a thought and I haven't put > any research at all to see whether this was feasible or not. Just > thought I would throw it out. > > Bill > > -- > > Bill Burke > Chief Architect > JBoss Group LLC. > > > > > > --- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > ___ > JBoss-Development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] If JSR-77 stats were mbeans...
If JSR-77 stats were mbeans then we could use all the monitoring, snapshotting and graphing features. Is it feasible to make current MBeans that manage EJBs, JMS, etc... implement the JSR-77 interfaces and expose these stats as JMX attributes? Just a thought and I haven't put any research at all to see whether this was feasible or not. Just thought I would throw it out. Bill -- Bill Burke Chief Architect JBoss Group LLC. --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] default entity bean locking
Adrian Brock wrote: On Tue, 2004-01-06 at 22:19, Bill Burke wrote: Currently the default entity bean locking strategy is Commit 'B' plus pessimistic. If we're going to default to 'B', can we default to multi instance? +1 from me It doesn't make sense to serialize access to a "shared" instance whose data won't be reused anyway. Yeah, you can rely on DB connection's tx isolation if you're worried about concurrency in 'B' with multi-instance. Its only utility is in CMP. i.e. ignore the server's request to reload data for an already associated bean. Regards, Adrian Bill -- Bill Burke Chief Architect JBoss Group LLC. --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] default entity bean locking
On Tue, 2004-01-06 at 22:19, Bill Burke wrote: > Currently the default entity bean locking strategy is Commit 'B' plus > pessimistic. If we're going to default to 'B', can we default to multi > instance? > +1 from me It doesn't make sense to serialize access to a "shared" instance whose data won't be reused anyway. Its only utility is in CMP. i.e. ignore the server's request to reload data for an already associated bean. Regards, Adrian > Bill -- Adrian Brock Director of Support Back Office JBoss Group, LLC --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] default entity bean locking
Currently the default entity bean locking strategy is Commit 'B' plus pessimistic. If we're going to default to 'B', can we default to multi instance? Bill -- Bill Burke Chief Architect JBoss Group LLC. --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 6-January-2004
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 6-January-2004 JBoss daily test results SUMMARY Number of tests run: 1606 Successful tests: 1571 Errors:27 Failures: 8 [time of test: 2004-01-06.19-45 GMT] [java.version: 1.4.1_03] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_03-b02] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.20-9smp] Useful resources: - http://jboss.sourceforge.net//junit-results/32/2004-01-06.19-45 for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: org.jboss.test.cache.test.local.TxConcurrentUnitTestCase Test:testConcurrentAccess Type:failure Exception: junit.framework.AssertionFailedError Message: expected:<765> but was:<1000> - Suite: org.jboss.test.cts.test.StatefulSessionUnitTestCase Test:testStrictPooling Type:failure Exception: junit.framework.AssertionFailedError Message: SessionInvoker.runEx != null - Suite: org.jboss.test.exception.EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: org.jboss.test.exception.EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: org.jboss.test.exception.EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: org.jboss.test.exception.EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: org.jboss.test.jmx.test.DeployXMBeanUnitTestCase Test:testUserXMBeanPersistentValues Type:failure Exception: junit.framework.AssertionFailedError Message: value == UpdatedAttr1Value, value=Att1InitialValue - Suite: org.jboss.test.naming.test.SimpleUnitTestCase Test:testNameChanges Type:failure Exception: junit.framework.AssertionFailedError Message: name.equals(copy), name=jmx - Suite: org.jboss.test.webservice.external.ExternalUnitTestCase Test:testFederated Type:error Exception: org.apache.axis.AxisFault Message: Our connection to the Altavista BabelFish site has been cut. This service will remain down indefinitely until an alternate translation engine can be found. We apologize for any inconvenience. - Suite: org.jboss.test.naming.test.SecurityUnitTestCase Test:testSecureHttpInvoker Type:failure Exception: junit.framework.AssertionFailedError Message: Should not have been able to lookup(invokers) - Suite: org.jboss.test.security.test.HttpsUnitTestCase Test:testHttpsURL Type:error Exception: java.io.IOException Message: Failed to readURL, ex=Default SSL context init failed: Algorithm SunX509 not available - Suite: org.jboss.test.security.test.SRPLoginModuleUnitTestCase Test:unknown Type:error Exception: org.jboss.deployment.DeploymentException Message: create operation failed for package file:/cvs/JBoss3.2/jboss-3.2/testsuite/output/lib/security-srp.sar; - nested throwable: (org.jboss.deployment.DeploymentException: org.jboss.test.security.interceptors.SRPCacheInterceptor; - nested throwable: (java.lang.InstantiationException: org.jboss.test.security.interceptors.SRPCacheInterceptor)) - Suite: org.jboss.test.security.test.SRPUnitTestCase Test:unknown Type:error Exception: org.jboss.deployment.DeploymentException Message: create operation failed for package file:/cvs/JBoss3.2/jboss-3.2/build/output
[JBoss-dev] Webconsole Snapshot Recording of JMX attributes
Hi all, I just committed the ability to do snapshot recordings of any JMX attribute within the web-console. To use it, you right-click a JMX attribute and choose the "create snapshot" item. From there you can start/stop snapshotting. Review the dataset and Graph the dataset. This is currently only available in Branch_3_2 and will be released with 3.2.4 (or the next RC of 3.2.4) Regards, Bill --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Feature Requests-871916 ] Make Local deployer non-modal
Feature Requests item #871916, was opened at 2004-01-06 20:36 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376688&aid=871916&group_id=22866 Category: JBoss-IDE Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jarkko Lietolahti (jappe) Assigned to: Nobody/Anonymous (nobody) Summary: Make Local deployer non-modal Initial Comment: Currently, when using local deployer Eclipse "hangs" until the deploment has been completed. This causes it to be impossible to debug application during deployment. Because Eclipse in hang on the local deployeyr message window and jboss is struct in a breakpoint which is hit when the application is deployed. Also it's frustrating to be able not to do anything with Eclipse while your application (EAR/WAR) is being deployed. In short; make local deployer return control back to eclipse as soon as possible. Maybe track deployment using the Progress-view etc... -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376688&aid=871916&group_id=22866 --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.3.1_09) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Jan 6 20:17:28 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-etc: [mkdir] Created dir: D:\jboss\jboss-head\jboss.net\output\etc [copy] Copying 3 files to D:\jboss\jboss-head\jboss.net\output\etc compile-resources: [mkdir] Created dir: D:\jboss\jboss-head\jboss.net\output\resources [copy] Copying 13 files to D:\jboss\jboss-head\jboss.net\output\resources webdoclet: [mkdir] Created dir: D:\jboss\jboss-head\jboss.net\output\resources\taglib\META-INF - Running Generating flash.tld. compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\jboss.net\output\classes\main [javac] Compiling 49 source files to D:\jboss\jboss-head\jboss.net\output\classes\main 6 warnings [mkdir] Created dir: D:\jboss\jboss-head\jboss.net\output\classes\tools [javac] Compiling 3 source files to D:\jboss\jboss-head\jboss.net\output\classes\tools compile: [mkdir] Created dir: D:\jboss\jboss-head\jboss.net\output\lib [jar] Building jar: D:\jboss\jboss-head\jboss.net\output\lib\jboss-net.jar [jar] Building jar: D:\jboss\jboss-head\jboss.net\output\lib\jboss-net.sar [jar] Building jar: D:\jboss\jboss-head\jboss.net\output\lib\jboss-net-client.jar [jar] Building jar: D:\jboss\jboss-head\jboss.net\output\lib\jboss-net-taglib.jar [jar] Building jar: D:\jboss\jboss-head\jboss.net\output\lib\xdoclet-module-jboss-net.jar [mkdir] Created dir: D:\jboss\jboss-head\jboss.net\output\bin [touch] Creating D:\jboss\jboss-head\jboss.net\output\build-marker most: == == Finished with 'most' in module 'jboss.net'. == _module-jboss.net-most: [copy] Copying 2 files to D:\jboss\jboss-head\build\output\testbuild\client [mkdir] Created dir: D:\jboss\jboss-head\build\output\testbuild\server\all\deploy\jboss-net.sar [unjar] Expanding: D:\jboss\jboss-head\jboss.net\output\lib\jboss-net.sar into D:\jboss\jboss-head\build\output\testbuild\server\all\deploy\jboss-net.sar == == Executing 'most' in module 'iiop'... == _buildmagic:init: configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\iiop\output\classes\main [javac] Compiling 92 source files to D:\jboss\jboss-head\iiop\output\classes\main D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLServerSocketFactory.java:101: cannot resolve symbol symbol : method setWantClientAuth (boolean) location: class javax.net.ssl.SSLServerSocket s.setWantClientAuth(request_mutual_auth); ^ D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLServerSocketFactory.java:115: cannot resolve symbol symbol : method setWantClientAuth (boolean) location: class javax.net.ssl.SSLServerSocket s.setWantClientAuth(request_mutual_auth); ^ D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLServerSocketFactory.java:132: cannot resolve symbol symbol : method setWantClientAuth (boolean) location: class javax.net.ssl.SSLServerSocket s.setWantClientAuth(request_mutual_auth); ^ 3 errors 4 warnings BUILD FAILED file:D:/jboss/jboss-head/iiop/build.xml:189: Compile failed; see the compiler error output for details. Total time: 3 minutes 50 seconds === Tue Jan 6 20:17:28 GMTST 2004 === CYGWIN_NT-5.1 quarks2 1.5.4(0.94/3/2) 2003-09-12 23:08 i686 unknown unknown Cygwin === java -version java version "1.3.1_09" Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_09-b03) Java HotSpot(TM) Client VM (build 1.3.1_09-b03, mixed mode) --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials
RE: [JBoss-dev] New JBoss Monitoring services
agreed - i can't wait to start playing w/ it. any proposed ETA for 3.2.4? -jae -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ben Sabrin Sent: Tuesday, January 06, 2004 3:00 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] New JBoss Monitoring services Well done Bill, this is good stuff:) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Friday, December 12, 2003 4:24 PM To: Jboss-Dev; JBoss 2; [EMAIL PROTECTED] Subject: [JBoss-dev] New JBoss Monitoring services This will be released in JBoss 3.2.4, but it is now available in 3.2 branch: cvs checkout -r Branch_3_2 jboss-3.2 I've also attached some screen shots JBoss Monitoring In JBoss 3.2.4, we've implemented some new JMX MBean monitoring and a nice GUI around this infrastructure as well as a way to plug in how alerts are processed. Why didn't we use the JMX Gauge and String monitors that come implemented with the JMX spec? 3 reasons: 1. They are not integrated with our Service architecture 2. They have no way of determining which monitors have sent an alert and are currently disabled because an alert was reached 3. They have no way of reseting an alert So, what infrastructure have we built? First let's look at configuring a JMX MBean monitor through the plain old -service.xml interface that you would to create any MBean. All Monitors are MBeans that start a thread to watch the values of another MBean's attribute. When a monitoring threshold is reached, the MOnitor will send out an MBean Notification to a set of registered listeners. Currently in JBoss, the are two types of listeners, a dumb Console listener, and an Email listener which will send out an email whenever an alert is received. Of course, the messages are fully configurable. Numeric Attribute Monitors The first type of monitor is a org.jboss.monitor.ThresholdMonitor that is used to track Numberic MBean attributes. Here is an example configuration of a monitor of free available memory. It will send a JMX Notification when free memory goes below one megabyte. The MBean it is watching over that has this particular stat is jboss.system:type=ServerInfo. File: FreeMemory_Monitor-service.xml FreeMemory Monitor jboss.system:type=ServerInfo FreeMemory 100 1 1000 true jboss.alerts:service=ConsoleAlertListener jboss.alerts:service=EmailAlertListener Let's walk through each attribute: FreeMemory The display name in which this monitor will be shown in the web-console. If you create monitors by hand you can have it managed by the web-console if you have one monitor defined in one file only and the name of the file is the same name as the monitor and the file lives in ./deploy/management/monitors/ So The above example the filename should be FreeMemory_Monitor-service.xml, notice that whitespace is substituted with an '_' charater. jboss.system:type=ServerInfo FreeMemory These are the MBean and the MBean attribute this monitor will watch. If the MBean is a ServiceMBean then you should make this a so that this monitor doesn't start before the watched MBean is loaded. 100 1 The Threshold is the value threshold of the attribute. The CompareTo is a numeric value, -1 means > (greater than), 0 means = (equal), 1 means (less than). These are the same values used by Java comparators. So in this example, when the FreeMemory attribute is less than 100 a JMX notification will be sent. 1000 The MBean creates a thread that will wake up every so often to check the threshold against the MBean attribute it is watching. The Period is the time in milliseconds this thread will sleep. true Enabled determines whether or not this monitor should actually monitor. It is the on/off switch of the monitor. jboss.alerts:service=ConsoleAlertListener jboss.alerts:service=EmailAlertListener When the threshold is triggered, the Monitor will send JMX NOtification to all registered listeners. For this particular MOnitor, a Console and Email listener have been registered. We'll look into how to configure the Email and Console listener in a bit, but when a threshold is breached, a message will be sent to the JBoss console (System.out via the ConsoleAlertListener) and via an Email with the EmailAlertListener. That's it! StringThresholdMonitor You can also monitor string values: BindAddress Monitor jboss:service=Naming BindAddress jboss.alerts:service=ConsoleAlertListener 0.0.0.0 1000 true true The config is the same as Threshold except that there is an "EqualityTriggersAlert" attribute. If this is true and the attribute equals the Threshold value, then an alert will be triggered EmailAlertListener To configure email you must 1) Configure ./deploy/mail-service.xml to work with your mail server 2) Edit ./dep
RE: [JBoss-dev] New JBoss Monitoring services
Well done Bill, this is good stuff:) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Friday, December 12, 2003 4:24 PM To: Jboss-Dev; JBoss 2; [EMAIL PROTECTED] Subject: [JBoss-dev] New JBoss Monitoring services This will be released in JBoss 3.2.4, but it is now available in 3.2 branch: cvs checkout -r Branch_3_2 jboss-3.2 I've also attached some screen shots JBoss Monitoring In JBoss 3.2.4, we've implemented some new JMX MBean monitoring and a nice GUI around this infrastructure as well as a way to plug in how alerts are processed. Why didn't we use the JMX Gauge and String monitors that come implemented with the JMX spec? 3 reasons: 1. They are not integrated with our Service architecture 2. They have no way of determining which monitors have sent an alert and are currently disabled because an alert was reached 3. They have no way of reseting an alert So, what infrastructure have we built? First let's look at configuring a JMX MBean monitor through the plain old -service.xml interface that you would to create any MBean. All Monitors are MBeans that start a thread to watch the values of another MBean's attribute. When a monitoring threshold is reached, the MOnitor will send out an MBean Notification to a set of registered listeners. Currently in JBoss, the are two types of listeners, a dumb Console listener, and an Email listener which will send out an email whenever an alert is received. Of course, the messages are fully configurable. Numeric Attribute Monitors The first type of monitor is a org.jboss.monitor.ThresholdMonitor that is used to track Numberic MBean attributes. Here is an example configuration of a monitor of free available memory. It will send a JMX Notification when free memory goes below one megabyte. The MBean it is watching over that has this particular stat is jboss.system:type=ServerInfo. File: FreeMemory_Monitor-service.xml FreeMemory Monitor jboss.system:type=ServerInfo FreeMemory 100 1 1000 true jboss.alerts:service=ConsoleAlertListener jboss.alerts:service=EmailAlertListener Let's walk through each attribute: FreeMemory The display name in which this monitor will be shown in the web-console. If you create monitors by hand you can have it managed by the web-console if you have one monitor defined in one file only and the name of the file is the same name as the monitor and the file lives in ./deploy/management/monitors/ So The above example the filename should be FreeMemory_Monitor-service.xml, notice that whitespace is substituted with an '_' charater. jboss.system:type=ServerInfo FreeMemory These are the MBean and the MBean attribute this monitor will watch. If the MBean is a ServiceMBean then you should make this a so that this monitor doesn't start before the watched MBean is loaded. 100 1 The Threshold is the value threshold of the attribute. The CompareTo is a numeric value, -1 means > (greater than), 0 means = (equal), 1 means (less than). These are the same values used by Java comparators. So in this example, when the FreeMemory attribute is less than 100 a JMX notification will be sent. 1000 The MBean creates a thread that will wake up every so often to check the threshold against the MBean attribute it is watching. The Period is the time in milliseconds this thread will sleep. true Enabled determines whether or not this monitor should actually monitor. It is the on/off switch of the monitor. jboss.alerts:service=ConsoleAlertListener jboss.alerts:service=EmailAlertListener When the threshold is triggered, the Monitor will send JMX NOtification to all registered listeners. For this particular MOnitor, a Console and Email listener have been registered. We'll look into how to configure the Email and Console listener in a bit, but when a threshold is breached, a message will be sent to the JBoss console (System.out via the ConsoleAlertListener) and via an Email with the EmailAlertListener. That's it! StringThresholdMonitor You can also monitor string values: BindAddress Monitor jboss:service=Naming BindAddress jboss.alerts:service=ConsoleAlertListener 0.0.0.0 1000 true true The config is the same as Threshold except that there is an "EqualityTriggersAlert" attribute. If this is true and the attribute equals the Threshold value, then an alert will be triggered EmailAlertListener To configure email you must 1) Configure ./deploy/mail-service.xml to work with your mail server 2) Edit ./deploy/monitoring-service.xml and uncomment out the EmailAlertListener: monitoring-service.xml: Console Alert Let's walk through each attribute of the email listener. Email Alert This is the display name of the Listener within the web-console gui. [EMAIL PROTECTED]
Re: [JBoss-dev] Remoting and NAT traversal, advanced network
Scott M Stark eloquently wrote the following on 1/6/2004 1:44 PM: The MBeanTracker appears to be a composite of the proxy factory and lookup services currently used and is where the NAT configuration would have to be I would guess. Does this layer support: - A client side interceptor stack - Specifying the class loader used for locating classes on the server side This is what is needed to look to the remoting framework as a replacement for the current proxy factory/detached invoker mechanism. Doesn't have a client side interceptor concept yet - although would be easy to add. I know this is something David Jenks started talking about before and I'm not sure if he did any work in that area. Right now there is some trivial automated class downloading that happens if you make an invocation and the class (either way) doesn't exist - but not well integrated in the UCL and needs to be better thought out. --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Remoting and NAT traversal, advanced network
The MBeanTracker appears to be a composite of the proxy factory and
lookup
services currently used and is where the NAT configuration would have to
be I would guess. Does this layer support:
- A client side interceptor stack
- Specifying the class loader used for locating classes on the server
side
This is what is needed to look to the remoting framework as a
replacement
for the current proxy factory/detached invoker mechanism.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jeff
Haynie
Sent: Monday, January 05, 2004 7:34 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Remoting and NAT traversal, advanced network
In the remoting framework, there are three main components: a transport,
a detector and a network registry. (among others .. but these are the
biggest)
The transport encapsulates the client and server components necessary
for communication for a given protocol between two endpoints.
The detector is a specific protocol/mechanism for handling discovery and
failure of zero or more endpoints based on a domain (or a cluster,
partition, whatever you'd like to call it - a logical grouping of
machines with the same name).
For transports, we have sockets (TCP), RMI, SOAP.
For detectors, we have multicast, JNDI.
The next major component is the network registry which receives
detection notifications (or you can call it directly to enlist servers)
which keeps a network map of all machines (and their identity and valid
transports and how to communicate with them) within the same logical
domain.
In JMX remoting, a simple proxy is created for the JMX subsystem (you
can have other subsystems such as AOP, JMS, etc.) which uses a transport
(unknown to the proxy) to communicate with the remote MBeanServer.
This allows you to mix and match transports, detection/failure
mechanisms and subsystems that use the framework.
In AOP Remoting, you can simply instrument an object, given a remote
locator (which could be obtained via detection) and then make remote
method calls against it w/o RMI stubs, etc.
We make heavy use of something called an MBeanTracker which is in JMX
Remoting.
You can give the mbean tracker a set of interfaces, query expression,
and any combination/ lack thereof and he will automatically give you
back a callback for things such as register, unregister, notification
and a MBeanLocator which can be turned into a proxy to that object.
For example:
MBeanTracker tracker=new MBeanTracker(getServer(), new
Class[]{Server.class}, null, false, null, true, new
MBeanTrackerActionAdapter()
{
public void mbeanRegistered (MBeanLocator locator)
{
System.out.println("I found a new JBoss server at: "+locator+" on
the network");
// cast to a server proxy that implements the Server interface
Server server = (Server)locator.narrow(Server.class);
// look ma... no hands, I just shutdown your jboss server remotely
server.shutdown();
}
public void mbeanUnregistered (MBeanLocator locator)
{
System.out.println("I lost a JBoss server at: "+locator+" on the
network");
}
public void mbeanNotification (MBeanLocator locator, Notification
notification, Object handback)
{
System.out.println("JBoss server at: "+locator+" sent a
notification: "+notification);
}
});
It's as simple as that. You can deal with network transparency (in a
novel way), failure, detection, etc. in short-order - with very little
code - but very very powerful.
And, no Marc, this isn't relegated to just JMX as Bill demonstrates with
AOP Remoting. This should be used for JMS, EJB and all the other
subsystem layers. ;)
Jeff
---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.3.1_09) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Jan 6 17:27:55 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === == _module-jboss.net-most: [copy] Copying 2 files to D:\jboss\jboss-head\build\output\testbuild\client [mkdir] Created dir: D:\jboss\jboss-head\build\output\testbuild\server\all\deploy\jboss-net.sar [unjar] Expanding: D:\jboss\jboss-head\jboss.net\output\lib\jboss-net.sar into D:\jboss\jboss-head\build\output\testbuild\server\all\deploy\jboss-net.sar == == Executing 'most' in module 'iiop'... == _buildmagic:init: configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\iiop\output\classes\main [javac] Compiling 92 source files to D:\jboss\jboss-head\iiop\output\classes\main D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLServerSocketFactory.java:15: cannot resolve symbol symbol : class SSLServerSocket location: package ssl import javax.net.ssl.SSLServerSocket; ^ D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLSocketFactory.java:15: cannot resolve symbol symbol : class SSLSocket location: package ssl import javax.net.ssl.SSLSocket; ^ D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLServerSocketFactory.java:61: cannot access javax.net.ssl.SSLServerSocketFactory file javax\net\ssl\SSLServerSocketFactory.class not found domainFactory = new DomainServerSocketFactory(securityDomain); ^ D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLServerSocketFactory.java:97: cannot resolve symbol symbol : class SSLServerSocket location: class org.jboss.iiop.jacorb.SSLServerSocketFactory SSLServerSocket s = ^ D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLServerSocketFactory.java:98: cannot resolve symbol symbol : class SSLServerSocket location: class org.jboss.iiop.jacorb.SSLServerSocketFactory (SSLServerSocket)domainFactory.createServerSocket(port); ^ D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLServerSocketFactory.java:111: cannot resolve symbol symbol : class SSLServerSocket location: class org.jboss.iiop.jacorb.SSLServerSocketFactory SSLServerSocket s = ^ D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLServerSocketFactory.java:112: cannot resolve symbol symbol : class SSLServerSocket location: class org.jboss.iiop.jacorb.SSLServerSocketFactory (SSLServerSocket)domainFactory.createServerSocket(port, backlog); ^ D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLServerSocketFactory.java:127: cannot resolve symbol symbol : class SSLServerSocket location: class org.jboss.iiop.jacorb.SSLServerSocketFactory SSLServerSocket s = ^ D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLServerSocketFactory.java:128: cannot resolve symbol symbol : class SSLServerSocket location: class org.jboss.iiop.jacorb.SSLServerSocketFactory (SSLServerSocket)domainFactory.createServerSocket(port, ^ D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLServerSocketFactory.java:141: cannot resolve symbol symbol : class SSLServerSocket location: class org.jboss.iiop.jacorb.SSLServerSocketFactory return (s instanceof SSLServerSocket); ^ D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLSocketFactory.java:58: cannot access javax.net.ssl.SSLSocketFactory file javax\net\ssl\SSLSocketFactory.class not found domainFactory = new DomainSocketFactory(securityDomain); ^ D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLSocketFactory.java:80: cannot resolve symbol symbol : class SSLSocket location: class org.jboss.iiop.jacorb.SSLSocketFactory return (s instanceof SSLSocket); ^ 12 errors 4 warnings BUILD FAILED file:D:/jboss/jboss-head/iiop/build.xml:188: Compile failed; see the compiler error output for details. Total time: 3 minu
[JBoss-dev] [ jboss-Bugs-870942 ] Classloader problem with ear file
Bugs item #870942, was opened at 2004-01-05 08:54 Message generated for change (Comment added) made by swolfangel You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=870942&group_id=22866 Category: JBossMX Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Steve Wolfangel (swolfangel) Assigned to: Scott M Stark (starksm) Summary: Classloader problem with ear file Initial Comment: Hello, I have an ear file that contains 2 stateless session beans and all the 3rd party jars required by the beans. The 3rd party jars contain older jdom classes than the jdom jar included in the jboss lib dir. I have a unique classloader setup (in the jboss-app.xml file) but I am having problems with jdom. It is finding the jboss jdom classes instead of the ones included in the ear. when I change the jboss-app.xml file to contain the following lines: com.metamatrix:loader=MM.ear java2ParentDelegation=false I get a NoClassDefFoundError. java.lang.NoClassDefFoundError: java/sql/SQLException This class is in the rt.jar file in the jdk! I was under the impression that setting java2ParentDelegation to false meant that if the class was not found using the local classloader then the parent classloader would be called. In a nutshell, when I have java2ParentDelegation set to true, I get the jdom problem, when I have java2ParentDelegation set to false I am unable to see classes that are in the rt.jar file. Here is the output when starting the server. [Server] Starting JBoss (MX MicroKernel)... [Server] Release ID: JBoss [WonderLand] 3.2.3 (build: CVSTag=JBoss_3_2_3 date=200311301445) [Server] Home Dir: D:\mm40\jb32\server\jboss [Server] Home URL: file:/D:/mm40/jb32/server/jboss/ [Server] Library URL: file:/D:/mm40/jb32/server/jboss/lib/ [Server] Patch URL: null [Server] Server Name: metamatrix [Server] Server Home Dir: D:\mm40\jb32 \server\jboss\server\metamatrix [Server] Server Home URL: file:/D:/mm40/jb32/server/jboss/server/metamatrix/ [Server] Server Data Dir: D:\mm40\jb32 \server\jboss\server\metamatrix\data [Server] Server Temp Dir: D:\mm40\jb32 \server\jboss\server\metamatrix\tmp [Server] Server Config URL: file:/D:/mm40/jb32/server/jboss/server/metamatrix/conf/ [Server] Server Library URL: file:/D:/mm40/jb32/server/jboss/server/metamatrix/lib/ [Server] Root Deployment Filename: jboss-service.xml [Server] Starting General Purpose Architecture (GPA)... [ServerInfo] Java version: 1.4.2,Sun Microsystems Inc. [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.2-b28,Sun Microsystems Inc. [ServerInfo] OS-System: Windows XP 5.1,x86 -- >Comment By: Steve Wolfangel (swolfangel) Date: 2004-01-06 10:39 Message: Logged In: YES user_id=541224 Is there any thing else I can do to help troubleshoot this problem? -- Comment By: Steve Wolfangel (swolfangel) Date: 2004-01-05 11:09 Message: Logged In: YES user_id=541224 Attached log.zip file containing ucl.log and server.log -- Comment By: Scott M Stark (starksm) Date: 2004-01-05 10:40 Message: Logged In: YES user_id=175228 Next step, add the following to the conf/log4j.xml and send me the resulting server.log and ucl.log zipped up as the ucl.log can be large: [EMAIL PROTECTED] -- Comment By: Scott M Stark (starksm) Date: 2004-01-05 10:33 Message: Logged In: YES user_id=175228 Yes, and there is a testcase in 3.2 for replacing the xml parser with a different version of xerces for example, using this approach. The problem with overriding the various xml related classes is that these are used all over and not all contexts are correctly limiting the scope of the classes they use. Presumably this is the case for the jdom usage. -- Comment By: Steve Wolfangel (swolfangel) Date: 2004-01-05 09:41 Message: Logged In: YES user_id=541224 Replacing the jdom.jar file got me past this problem. I am still interested in finding the correct solution since there is a chance I could have similar problems in the future. Am I correct by assuming that by setting up my own classloader and setting java2ParentDelegation to false in the jboss-app file is the correct approach? -- Comment By: Steve Wolfangel (swolfangel) Date: 2004-01-05 09:25 Message: Logged In: YES user_id=541224 I added the server.log file that contains the complete stack trace of the NoClassDefFound error. -- Comment By: Scott M Star
Re: [JBoss-dev] [ jboss-Bugs-871649 ] Problem with source of JMX Notifications
OK, good catch. If you extended the Notification object it would fail. I was trying to avoid modifying the real source - but I guess there's no choice. Fix is in. Jeff Adrian Brock wrote: Hi Jeff, You cannot implement it like this: // make a copy of the notification, replacing with the real source of the event Notification n = new Notification(notification.getType(),source,notification.getSequenceNumber(),notification.getTimeStamp(),notification.getMessage()); n.setUserData(notification.getUserData()); return this.delegate.isNotificationEnabled(n); The filter will likely rely upon the type of the Notification which is lost in this implementation. The big problem is that notifications are not required to be clonable, so the only thing you can do is setSource() on the notification with the ObjectName (changing the source for subsequent notification listeners). This is a known issue with the spec. See NotificationListenerProxy. Regards, Adrian On Tue, 2004-01-06 at 14:18, SourceForge.net wrote: Bugs item #871649, was opened at 2004-01-06 08:16 Message generated for change (Comment added) made by jhaynie You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=871649&group_id=22866 Category: JBossMX Group: v3.2 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Jeff Haynie (jhaynie) Assigned to: Jeff Haynie (jhaynie) Summary: Problem with source of JMX Notifications Initial Comment: According to the JMX spec, the source of a Notification must be of type ObjectName. At line 420 in ServerImpl: Notification msg = new Notification (START_NOTIFICATION_TYPE, this, 1); should be changed to: Notification msg = new Notification (START_NOTIFICATION_TYPE, ServerImplMBean.OBJECT_NAME, 1); We should also update JMX to check this (although I thought it did before - maybe its happening at the at a higher level in the BasicMBeanRegistry). The problem is that the ListenerRegistration in the NotificationBroadcasterSupport.sendNotification() will evaluate the NotificationFilter before being dispatched up to the listener. The listener is being wrapped at a higher level by the mbean server using the NotificationListenerProxy which sets the source - but this happens after the filter is applied -- which causes problems if you're checking the ObjectName in the filter. An easy enough fix for this particular problem is just to do above. However, I'm worried we'll still see this in other places. Another thought is to wrap the MBeanServerListenerRegistration (which creates NotificationListenerProxy) and pass in a proxy to the filter, such that it will set the appropriate source using the MBeanServerListenerRegistration and then delegate to the appropriate filter. The other thing is to enforce in our Notification implementation ObjectName in setSource and the constructor -- which according to the JMX spec we're suppose to throw an IllegalArgumentException. -- Comment By: Jeff Haynie (jhaynie) Date: 2004-01-06 09:18 Message: Logged In: YES user_id=4529 This is implemented in 3.2 branch. -- Comment By: Adrian Brock (ejort) Date: 2004-01-06 08:50 Message: Logged In: YES user_id=9459 Yes, go ahead. Regards, Adrian -- Comment By: Jeff Haynie (jhaynie) Date: 2004-01-06 08:44 Message: Logged In: YES user_id=4529 OK, looking at the JMX 1.2 spec javadoc for Notification, it states: "The Notification class represents a notification emitted by an MBean. It contains a reference to the source MBean: if the notification has been forwarded through the MBean server, this is the object name of the MBean. If the listener has registered directly with the MBean, this is either the object name or a direct reference to the MBean. It is strongly recommended that notification senders use the object name rather than a reference to the MBean object as the source." In my case, and in the case for jboss mx, we're not registering directly with the mbean. I like the idea of filter proxy since it would enforce the ObjectName externally and still allow either ObjectName or direct reference in the implementation of an MBean. Is this something you would like me to apply? -- Comment By: Adrian Brock (ejort) Date: 2004-01-06 08:34 Message: Logged In: YES user_id=9459 The only requirement from the spec is that notification listeners registered through the MBeanServer receive notifications with the ObjectName they registered against. Direct notifications (i.e. where you register directly with the MBean) are not required to use the ObjectName, but direct notifications are frowned upon. You cannot setSource() a normal object but there is no such requir
Re: [JBoss-dev] [ jboss-Bugs-871649 ] Problem with source of JMX Notifications
Hi Jeff, You cannot implement it like this: // make a copy of the notification, replacing with the real source of the event Notification n = new Notification(notification.getType(),source,notification.getSequenceNumber(),notification.getTimeStamp(),notification.getMessage()); n.setUserData(notification.getUserData()); return this.delegate.isNotificationEnabled(n); The filter will likely rely upon the type of the Notification which is lost in this implementation. The big problem is that notifications are not required to be clonable, so the only thing you can do is setSource() on the notification with the ObjectName (changing the source for subsequent notification listeners). This is a known issue with the spec. See NotificationListenerProxy. Regards, Adrian On Tue, 2004-01-06 at 14:18, SourceForge.net wrote: > Bugs item #871649, was opened at 2004-01-06 08:16 > Message generated for change (Comment added) made by jhaynie > You can respond by visiting: > https://sourceforge.net/tracker/?func=detail&atid=376685&aid=871649&group_id=22866 > > Category: JBossMX > Group: v3.2 > >Status: Closed > >Resolution: Fixed > Priority: 5 > Submitted By: Jeff Haynie (jhaynie) > Assigned to: Jeff Haynie (jhaynie) > Summary: Problem with source of JMX Notifications > > Initial Comment: > According to the JMX spec, the source of a Notification > must be of type ObjectName. > > At line 420 in ServerImpl: > > Notification msg = new Notification > (START_NOTIFICATION_TYPE, this, 1); > > should be changed to: > > Notification msg = new Notification > (START_NOTIFICATION_TYPE, > ServerImplMBean.OBJECT_NAME, 1); > > > We should also update JMX to check this (although I > thought it did before - maybe its happening at the at a > higher level in the BasicMBeanRegistry). > > The problem is that the ListenerRegistration in the > NotificationBroadcasterSupport.sendNotification() will > evaluate the NotificationFilter before being dispatched > up to the listener. The listener is being wrapped at a > higher level by the mbean server using the > NotificationListenerProxy which sets the source - but > this happens after the filter is applied -- which causes > problems if you're checking the ObjectName in the filter. > > An easy enough fix for this particular problem is just to > do above. However, I'm worried we'll still see this in > other places. Another thought is to wrap the > MBeanServerListenerRegistration (which creates > NotificationListenerProxy) and pass in a proxy to the > filter, such that it will set the appropriate source using > the MBeanServerListenerRegistration and then delegate > to the appropriate filter. > > The other thing is to enforce in our Notification > implementation ObjectName in setSource and the > constructor -- which according to the JMX spec we're > suppose to throw an IllegalArgumentException. > > -- > > >Comment By: Jeff Haynie (jhaynie) > Date: 2004-01-06 09:18 > > Message: > Logged In: YES > user_id=4529 > > This is implemented in 3.2 branch. > > -- > > Comment By: Adrian Brock (ejort) > Date: 2004-01-06 08:50 > > Message: > Logged In: YES > user_id=9459 > > Yes, go ahead. > > Regards, > Adrian > > -- > > Comment By: Jeff Haynie (jhaynie) > Date: 2004-01-06 08:44 > > Message: > Logged In: YES > user_id=4529 > > OK, looking at the JMX 1.2 spec javadoc for Notification, it > states: > > "The Notification class represents a notification emitted by an > MBean. It contains a reference to the source MBean: if the > notification has been forwarded through the MBean server, > this is the object name of the MBean. If the listener has > registered directly with the MBean, this is either the > object name or a direct reference to the MBean. > > It is strongly recommended that notification senders use the > object name rather than a reference to the MBean object as > the source." > > > In my case, and in the case for jboss mx, we're not > registering directly with the mbean. I like the idea of > filter proxy since it would enforce the ObjectName > externally and still allow either ObjectName or direct > reference in the implementation of an MBean. > > Is this something you would like me to apply? > > > > -- > > Comment By: Adrian Brock (ejort) > Date: 2004-01-06 08:34 > > Message: > Logged In: YES > user_id=9459 > > The only requirement from the spec is that notification > listeners > registered through the MBeanServer receive notifications > with the ObjectName they registered against. > > Direct notifications (i.e. where you register directly with > the MBean) > are not required to use the ObjectName, > but direct notifications are frowned up
[JBoss-dev] [ jboss-Bugs-871649 ] Problem with source of JMX Notifications
Bugs item #871649, was opened at 2004-01-06 08:16 Message generated for change (Comment added) made by jhaynie You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=871649&group_id=22866 Category: JBossMX Group: v3.2 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Jeff Haynie (jhaynie) Assigned to: Jeff Haynie (jhaynie) Summary: Problem with source of JMX Notifications Initial Comment: According to the JMX spec, the source of a Notification must be of type ObjectName. At line 420 in ServerImpl: Notification msg = new Notification (START_NOTIFICATION_TYPE, this, 1); should be changed to: Notification msg = new Notification (START_NOTIFICATION_TYPE, ServerImplMBean.OBJECT_NAME, 1); We should also update JMX to check this (although I thought it did before - maybe its happening at the at a higher level in the BasicMBeanRegistry). The problem is that the ListenerRegistration in the NotificationBroadcasterSupport.sendNotification() will evaluate the NotificationFilter before being dispatched up to the listener. The listener is being wrapped at a higher level by the mbean server using the NotificationListenerProxy which sets the source - but this happens after the filter is applied -- which causes problems if you're checking the ObjectName in the filter. An easy enough fix for this particular problem is just to do above. However, I'm worried we'll still see this in other places. Another thought is to wrap the MBeanServerListenerRegistration (which creates NotificationListenerProxy) and pass in a proxy to the filter, such that it will set the appropriate source using the MBeanServerListenerRegistration and then delegate to the appropriate filter. The other thing is to enforce in our Notification implementation ObjectName in setSource and the constructor -- which according to the JMX spec we're suppose to throw an IllegalArgumentException. -- >Comment By: Jeff Haynie (jhaynie) Date: 2004-01-06 09:18 Message: Logged In: YES user_id=4529 This is implemented in 3.2 branch. -- Comment By: Adrian Brock (ejort) Date: 2004-01-06 08:50 Message: Logged In: YES user_id=9459 Yes, go ahead. Regards, Adrian -- Comment By: Jeff Haynie (jhaynie) Date: 2004-01-06 08:44 Message: Logged In: YES user_id=4529 OK, looking at the JMX 1.2 spec javadoc for Notification, it states: "The Notification class represents a notification emitted by an MBean. It contains a reference to the source MBean: if the notification has been forwarded through the MBean server, this is the object name of the MBean. If the listener has registered directly with the MBean, this is either the object name or a direct reference to the MBean. It is strongly recommended that notification senders use the object name rather than a reference to the MBean object as the source." In my case, and in the case for jboss mx, we're not registering directly with the mbean. I like the idea of filter proxy since it would enforce the ObjectName externally and still allow either ObjectName or direct reference in the implementation of an MBean. Is this something you would like me to apply? -- Comment By: Adrian Brock (ejort) Date: 2004-01-06 08:34 Message: Logged In: YES user_id=9459 The only requirement from the spec is that notification listeners registered through the MBeanServer receive notifications with the ObjectName they registered against. Direct notifications (i.e. where you register directly with the MBean) are not required to use the ObjectName, but direct notifications are frowned upon. You cannot setSource() a normal object but there is no such requirement on the constructor. Unless the broadcaster also implements MBeanRegistration it does not know its own ObjectName. One way to fix the problem would be to add a NotificationFilterProxy that replaces the source with the ObjectName in the same way that is done for the NotificationListener. Regards, Adrian -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=871649&group_id=22866 --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.3.1_09) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Jan 6 14:12:21 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === == _module-jboss.net-most: [copy] Copying 2 files to D:\jboss\jboss-head\build\output\testbuild\client [mkdir] Created dir: D:\jboss\jboss-head\build\output\testbuild\server\all\deploy\jboss-net.sar [unjar] Expanding: D:\jboss\jboss-head\jboss.net\output\lib\jboss-net.sar into D:\jboss\jboss-head\build\output\testbuild\server\all\deploy\jboss-net.sar == == Executing 'most' in module 'iiop'... == _buildmagic:init: configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\iiop\output\classes\main [javac] Compiling 92 source files to D:\jboss\jboss-head\iiop\output\classes\main D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLServerSocketFactory.java:15: cannot resolve symbol symbol : class SSLServerSocket location: package ssl import javax.net.ssl.SSLServerSocket; ^ D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLSocketFactory.java:15: cannot resolve symbol symbol : class SSLSocket location: package ssl import javax.net.ssl.SSLSocket; ^ D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLServerSocketFactory.java:61: cannot access javax.net.ssl.SSLServerSocketFactory file javax\net\ssl\SSLServerSocketFactory.class not found domainFactory = new DomainServerSocketFactory(securityDomain); ^ D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLServerSocketFactory.java:97: cannot resolve symbol symbol : class SSLServerSocket location: class org.jboss.iiop.jacorb.SSLServerSocketFactory SSLServerSocket s = ^ D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLServerSocketFactory.java:98: cannot resolve symbol symbol : class SSLServerSocket location: class org.jboss.iiop.jacorb.SSLServerSocketFactory (SSLServerSocket)domainFactory.createServerSocket(port); ^ D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLServerSocketFactory.java:111: cannot resolve symbol symbol : class SSLServerSocket location: class org.jboss.iiop.jacorb.SSLServerSocketFactory SSLServerSocket s = ^ D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLServerSocketFactory.java:112: cannot resolve symbol symbol : class SSLServerSocket location: class org.jboss.iiop.jacorb.SSLServerSocketFactory (SSLServerSocket)domainFactory.createServerSocket(port, backlog); ^ D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLServerSocketFactory.java:127: cannot resolve symbol symbol : class SSLServerSocket location: class org.jboss.iiop.jacorb.SSLServerSocketFactory SSLServerSocket s = ^ D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLServerSocketFactory.java:128: cannot resolve symbol symbol : class SSLServerSocket location: class org.jboss.iiop.jacorb.SSLServerSocketFactory (SSLServerSocket)domainFactory.createServerSocket(port, ^ D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLServerSocketFactory.java:141: cannot resolve symbol symbol : class SSLServerSocket location: class org.jboss.iiop.jacorb.SSLServerSocketFactory return (s instanceof SSLServerSocket); ^ D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLSocketFactory.java:58: cannot access javax.net.ssl.SSLSocketFactory file javax\net\ssl\SSLSocketFactory.class not found domainFactory = new DomainSocketFactory(securityDomain); ^ D:\jboss\jboss-head\iiop\src\main\org\jboss\iiop\jacorb\SSLSocketFactory.java:80: cannot resolve symbol symbol : class SSLSocket location: class org.jboss.iiop.jacorb.SSLSocketFactory return (s instanceof SSLSocket); ^ 12 errors 4 warnings BUILD FAILED file:D:/jboss/jboss-head/iiop/build.xml:188: Compile failed; see the compiler error output for details. Total time: 3 minu
[JBoss-dev] Possible vulnerability with http trace
See: http://www.kb.cert.org/vuls/id/867593 Are we affected with tomcat/jetty as well? Heiko
[JBoss-dev] [ jboss-Bugs-871649 ] Problem with source of JMX Notifications
Bugs item #871649, was opened at 2004-01-06 13:16 Message generated for change (Comment added) made by ejort You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=871649&group_id=22866 Category: JBossMX Group: v3.2 Status: Open >Resolution: Accepted Priority: 5 Submitted By: Jeff Haynie (jhaynie) >Assigned to: Jeff Haynie (jhaynie) Summary: Problem with source of JMX Notifications Initial Comment: According to the JMX spec, the source of a Notification must be of type ObjectName. At line 420 in ServerImpl: Notification msg = new Notification (START_NOTIFICATION_TYPE, this, 1); should be changed to: Notification msg = new Notification (START_NOTIFICATION_TYPE, ServerImplMBean.OBJECT_NAME, 1); We should also update JMX to check this (although I thought it did before - maybe its happening at the at a higher level in the BasicMBeanRegistry). The problem is that the ListenerRegistration in the NotificationBroadcasterSupport.sendNotification() will evaluate the NotificationFilter before being dispatched up to the listener. The listener is being wrapped at a higher level by the mbean server using the NotificationListenerProxy which sets the source - but this happens after the filter is applied -- which causes problems if you're checking the ObjectName in the filter. An easy enough fix for this particular problem is just to do above. However, I'm worried we'll still see this in other places. Another thought is to wrap the MBeanServerListenerRegistration (which creates NotificationListenerProxy) and pass in a proxy to the filter, such that it will set the appropriate source using the MBeanServerListenerRegistration and then delegate to the appropriate filter. The other thing is to enforce in our Notification implementation ObjectName in setSource and the constructor -- which according to the JMX spec we're suppose to throw an IllegalArgumentException. -- >Comment By: Adrian Brock (ejort) Date: 2004-01-06 13:50 Message: Logged In: YES user_id=9459 Yes, go ahead. Regards, Adrian -- Comment By: Jeff Haynie (jhaynie) Date: 2004-01-06 13:44 Message: Logged In: YES user_id=4529 OK, looking at the JMX 1.2 spec javadoc for Notification, it states: "The Notification class represents a notification emitted by an MBean. It contains a reference to the source MBean: if the notification has been forwarded through the MBean server, this is the object name of the MBean. If the listener has registered directly with the MBean, this is either the object name or a direct reference to the MBean. It is strongly recommended that notification senders use the object name rather than a reference to the MBean object as the source." In my case, and in the case for jboss mx, we're not registering directly with the mbean. I like the idea of filter proxy since it would enforce the ObjectName externally and still allow either ObjectName or direct reference in the implementation of an MBean. Is this something you would like me to apply? -- Comment By: Adrian Brock (ejort) Date: 2004-01-06 13:34 Message: Logged In: YES user_id=9459 The only requirement from the spec is that notification listeners registered through the MBeanServer receive notifications with the ObjectName they registered against. Direct notifications (i.e. where you register directly with the MBean) are not required to use the ObjectName, but direct notifications are frowned upon. You cannot setSource() a normal object but there is no such requirement on the constructor. Unless the broadcaster also implements MBeanRegistration it does not know its own ObjectName. One way to fix the problem would be to add a NotificationFilterProxy that replaces the source with the ObjectName in the same way that is done for the NotificationListener. Regards, Adrian -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=871649&group_id=22866 --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-871649 ] Problem with source of JMX Notifications
Bugs item #871649, was opened at 2004-01-06 08:16 Message generated for change (Comment added) made by jhaynie You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=871649&group_id=22866 Category: JBossMX Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Jeff Haynie (jhaynie) Assigned to: Nobody/Anonymous (nobody) Summary: Problem with source of JMX Notifications Initial Comment: According to the JMX spec, the source of a Notification must be of type ObjectName. At line 420 in ServerImpl: Notification msg = new Notification (START_NOTIFICATION_TYPE, this, 1); should be changed to: Notification msg = new Notification (START_NOTIFICATION_TYPE, ServerImplMBean.OBJECT_NAME, 1); We should also update JMX to check this (although I thought it did before - maybe its happening at the at a higher level in the BasicMBeanRegistry). The problem is that the ListenerRegistration in the NotificationBroadcasterSupport.sendNotification() will evaluate the NotificationFilter before being dispatched up to the listener. The listener is being wrapped at a higher level by the mbean server using the NotificationListenerProxy which sets the source - but this happens after the filter is applied -- which causes problems if you're checking the ObjectName in the filter. An easy enough fix for this particular problem is just to do above. However, I'm worried we'll still see this in other places. Another thought is to wrap the MBeanServerListenerRegistration (which creates NotificationListenerProxy) and pass in a proxy to the filter, such that it will set the appropriate source using the MBeanServerListenerRegistration and then delegate to the appropriate filter. The other thing is to enforce in our Notification implementation ObjectName in setSource and the constructor -- which according to the JMX spec we're suppose to throw an IllegalArgumentException. -- >Comment By: Jeff Haynie (jhaynie) Date: 2004-01-06 08:44 Message: Logged In: YES user_id=4529 OK, looking at the JMX 1.2 spec javadoc for Notification, it states: "The Notification class represents a notification emitted by an MBean. It contains a reference to the source MBean: if the notification has been forwarded through the MBean server, this is the object name of the MBean. If the listener has registered directly with the MBean, this is either the object name or a direct reference to the MBean. It is strongly recommended that notification senders use the object name rather than a reference to the MBean object as the source." In my case, and in the case for jboss mx, we're not registering directly with the mbean. I like the idea of filter proxy since it would enforce the ObjectName externally and still allow either ObjectName or direct reference in the implementation of an MBean. Is this something you would like me to apply? -- Comment By: Adrian Brock (ejort) Date: 2004-01-06 08:34 Message: Logged In: YES user_id=9459 The only requirement from the spec is that notification listeners registered through the MBeanServer receive notifications with the ObjectName they registered against. Direct notifications (i.e. where you register directly with the MBean) are not required to use the ObjectName, but direct notifications are frowned upon. You cannot setSource() a normal object but there is no such requirement on the constructor. Unless the broadcaster also implements MBeanRegistration it does not know its own ObjectName. One way to fix the problem would be to add a NotificationFilterProxy that replaces the source with the ObjectName in the same way that is done for the NotificationListener. Regards, Adrian -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=871649&group_id=22866 --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-871649 ] Problem with source of JMX Notifications
Bugs item #871649, was opened at 2004-01-06 13:16 Message generated for change (Comment added) made by ejort You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=871649&group_id=22866 Category: JBossMX Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Jeff Haynie (jhaynie) Assigned to: Nobody/Anonymous (nobody) Summary: Problem with source of JMX Notifications Initial Comment: According to the JMX spec, the source of a Notification must be of type ObjectName. At line 420 in ServerImpl: Notification msg = new Notification (START_NOTIFICATION_TYPE, this, 1); should be changed to: Notification msg = new Notification (START_NOTIFICATION_TYPE, ServerImplMBean.OBJECT_NAME, 1); We should also update JMX to check this (although I thought it did before - maybe its happening at the at a higher level in the BasicMBeanRegistry). The problem is that the ListenerRegistration in the NotificationBroadcasterSupport.sendNotification() will evaluate the NotificationFilter before being dispatched up to the listener. The listener is being wrapped at a higher level by the mbean server using the NotificationListenerProxy which sets the source - but this happens after the filter is applied -- which causes problems if you're checking the ObjectName in the filter. An easy enough fix for this particular problem is just to do above. However, I'm worried we'll still see this in other places. Another thought is to wrap the MBeanServerListenerRegistration (which creates NotificationListenerProxy) and pass in a proxy to the filter, such that it will set the appropriate source using the MBeanServerListenerRegistration and then delegate to the appropriate filter. The other thing is to enforce in our Notification implementation ObjectName in setSource and the constructor -- which according to the JMX spec we're suppose to throw an IllegalArgumentException. -- >Comment By: Adrian Brock (ejort) Date: 2004-01-06 13:34 Message: Logged In: YES user_id=9459 The only requirement from the spec is that notification listeners registered through the MBeanServer receive notifications with the ObjectName they registered against. Direct notifications (i.e. where you register directly with the MBean) are not required to use the ObjectName, but direct notifications are frowned upon. You cannot setSource() a normal object but there is no such requirement on the constructor. Unless the broadcaster also implements MBeanRegistration it does not know its own ObjectName. One way to fix the problem would be to add a NotificationFilterProxy that replaces the source with the ObjectName in the same way that is done for the NotificationListener. Regards, Adrian -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=871649&group_id=22866 --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-871649 ] Problem with source of JMX Notifications
Bugs item #871649, was opened at 2004-01-06 08:16 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=871649&group_id=22866 Category: JBossMX Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Jeff Haynie (jhaynie) Assigned to: Nobody/Anonymous (nobody) Summary: Problem with source of JMX Notifications Initial Comment: According to the JMX spec, the source of a Notification must be of type ObjectName. At line 420 in ServerImpl: Notification msg = new Notification (START_NOTIFICATION_TYPE, this, 1); should be changed to: Notification msg = new Notification (START_NOTIFICATION_TYPE, ServerImplMBean.OBJECT_NAME, 1); We should also update JMX to check this (although I thought it did before - maybe its happening at the at a higher level in the BasicMBeanRegistry). The problem is that the ListenerRegistration in the NotificationBroadcasterSupport.sendNotification() will evaluate the NotificationFilter before being dispatched up to the listener. The listener is being wrapped at a higher level by the mbean server using the NotificationListenerProxy which sets the source - but this happens after the filter is applied -- which causes problems if you're checking the ObjectName in the filter. An easy enough fix for this particular problem is just to do above. However, I'm worried we'll still see this in other places. Another thought is to wrap the MBeanServerListenerRegistration (which creates NotificationListenerProxy) and pass in a proxy to the filter, such that it will set the appropriate source using the MBeanServerListenerRegistration and then delegate to the appropriate filter. The other thing is to enforce in our Notification implementation ObjectName in setSource and the constructor -- which according to the JMX spec we're suppose to throw an IllegalArgumentException. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=871649&group_id=22866 --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.3.1_09) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Jan 6 12:11:21 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === _buildmagic:init: init: compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\classes [javac] Compiling 15 source files to D:\jboss\jboss-head\naming\output\classes compile-rmi: [rmic] RMI Compiling 1 class to D:\jboss\jboss-head\naming\output\classes compile-etc: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\etc [copy] Copying 4 files to D:\jboss\jboss-head\naming\output\etc compile: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\lib [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnpserver.jar [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnp-client.jar [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnp-tests.jar [touch] Creating D:\jboss\jboss-head\naming\output\build-marker most: == == Finished with 'most' in module 'naming'. == _module-naming-most: [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\lib [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\client == == Executing 'most' in module 'remoting'... == _buildmagic:init: configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\gen-src (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. INFO:Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\transport\Connector.java --> ConnectorMBean qualified to org.jboss.remoting.transport.ConnectorMBean compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\classes [javac] Compiling 114 source files to D:\jboss\jboss-head\remoting\output\classes D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\detection\multicast\MulticastDetector.java:278: cannot resolve symbol symbol : method isClosed
RE: [JBoss-dev] ServiceController MBean unload ordering
Every service would have to have a dependency on the remoting service in order for it to be the last to be shutdown. Otherwise, you can create your own java.util.Comparator impl using the URLDeploymentScanner URLComparator attribute to order the content of deploy however you want to ensure remoting is started first, stopped last. Scott Stark Chief Technology Officer JBoss Group, LLC -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Haynie Sent: Monday, January 05, 2004 7:37 PM To: [EMAIL PROTECTED] Subject: [JBoss-dev] ServiceController MBean unload ordering Obscure question: Is there a way to instruct the ServiceController to unload an MBean (as near) at the end of the lifecycle of all the other mbeans? Use case: In remoting, ideally you want to have the remoting framework load at the last possible minute so that notifications from all the other mbeans will be attempted to be delivered before the server is shutdown. --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.3.1_09) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Jan 6 10:15:31 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === _buildmagic:init: init: compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\classes [javac] Compiling 15 source files to D:\jboss\jboss-head\naming\output\classes compile-rmi: [rmic] RMI Compiling 1 class to D:\jboss\jboss-head\naming\output\classes compile-etc: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\etc [copy] Copying 4 files to D:\jboss\jboss-head\naming\output\etc compile: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\lib [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnpserver.jar [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnp-client.jar [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnp-tests.jar [touch] Creating D:\jboss\jboss-head\naming\output\build-marker most: == == Finished with 'most' in module 'naming'. == _module-naming-most: [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\lib [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\client == == Executing 'most' in module 'remoting'... == _buildmagic:init: configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\gen-src (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. INFO:Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\transport\Connector.java --> ConnectorMBean qualified to org.jboss.remoting.transport.ConnectorMBean compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\classes [javac] Compiling 114 source files to D:\jboss\jboss-head\remoting\output\classes D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\detection\multicast\MulticastDetector.java:278: cannot resolve symbol symbol : method isClosed
RE: [JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 5-January-2004
It passes for me with yesterday's clean check out. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Scott M Stark > Sent: Monday, January 05, 2004 4:32 PM > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-dev] Automated JBoss(Branch_3_2 > WonderLand) Testsuite Results: 5-January-2004 > > What are these exceptions showing up in the > org.jboss.test.deadlock.test.BeanStressTestCase? > > 06:25:53,725 ERROR [LogInterceptor] EJBException, causedBy: > java.sql.SQLException: Unexpected token: FROM in statement > [SELECT FROM NEXTGENREENTNOTSUP WHERE (name='1')] > at org.hsqldb.Trace.getError(Unknown Source) > at org.hsqldb.jdbcResultSet.(Unknown Source) > at org.hsqldb.jdbcConnection.executeStandalone(Unknown Source) > at org.hsqldb.jdbcConnection.execute(Unknown Source) > at org.hsqldb.jdbcStatement.fetchResult(Unknown Source) > at org.hsqldb.jdbcStatement.executeQuery(Unknown Source) > at > org.hsqldb.jdbcPreparedStatement.executeQuery(Unknown Source) > at > org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.execu > teQuery(Wr > appedPreparedStatement.java:304) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.execute(J > DBCLoadEnt > ityCommand.java:155) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadEntityCommand.execute(J > DBCLoadEnt > ityCommand.java:72) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.loadEntity(JDB > CStoreMana > ger.java:620) > at > org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.loadEntity(JDB > CStoreMana > ger.java:602) > at > org.jboss.ejb.plugins.CMPPersistenceManager.loadEntity(CMPPers > istenceMan > ager.java:381) > > > > Scott Stark > Chief Technology Officer > JBoss Group, LLC > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of [EMAIL PROTECTED] > Sent: Monday, January 05, 2004 6:28 AM > To: [EMAIL PROTECTED] > Subject: [JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite > Results: 5-January-2004 > > Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: > 5-January-2004 > > > JBoss daily test results > > SUMMARY > > Number of tests run: 1633 > > > > Successful tests: 1598 > > Errors:22 > > Failures: 13 > > > > > > --- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign > up for IBM's Free Linux Tutorials. Learn everything from the > bash shell to sys admin. > Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=ick > ___ > JBoss-Development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] EOL for JDK 1.4.1
>From http://java.sun.com/j2se/1.4.1/download.html: Products listed on this page have begun the Sun End of Life (EOL) process. The EOL transition period is from July 15, 2003 until January 15, 2004. With this notice, customers should now begin to move to current product versions. During the EOL transition period, the products will be supported as per existing customer support agreements. After this period, these products will no longer be supported by Sun. Scott Stark Chief Technology Officer JBoss Group, LLC --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 6-January-2004
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 6-January-2004 JBoss daily test results SUMMARY Number of tests run: 1626 Successful tests: 1589 Errors:22 Failures: 15 [time of test: 2004-01-06.09-23 GMT] [java.version: 1.4.2_03] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.2_03-b02] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.20-9smp] Useful resources: - http://jboss.sourceforge.net//junit-results/32/2004-01-06.09-23 for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: org.jboss.test.cache.test.local.ConcurrentUnitTestCase Test:testConcurrentAccessWithRWLock Type:failure Exception: junit.framework.AssertionFailedError Message: expected:<1001> but was:<1000> - Suite: org.jboss.test.exception.EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: org.jboss.test.exception.EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: org.jboss.test.exception.EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: org.jboss.test.exception.EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: org.jboss.test.jmx.test.DeployXMBeanUnitTestCase Test:testUserXMBeanPersistentValues Type:failure Exception: junit.framework.AssertionFailedError Message: value == UpdatedAttr1Value, value=Att1InitialValue - Suite: org.jboss.test.jmx.test.DeployXMBeanUnitTestCase Test:testSecuredJndiXMBean Type:error Exception: java.lang.RuntimeException Message: java.lang.SecurityException: Failed to authenticate principal: jduke - Suite: org.jboss.test.jmx.test.DeployXMBeanUnitTestCase Test:testPersistentJndiXMBean Type:error Exception: java.lang.RuntimeException Message: java.lang.SecurityException: Failed to authenticate principal: jduke - Suite: org.jboss.test.jmx.test.JMXInvokerUnitTestCase Test:testGetSomething Type:error Exception: javax.management.InstanceNotFoundException Message: jboss.test:service=InvokerTest is not registered. - Suite: org.jboss.test.jmx.test.JMXInvokerUnitTestCase Test:testGetCustom Type:error Exception: javax.management.InstanceNotFoundException Message: jboss.test:service=InvokerTest is not registered. - Suite: org.jboss.test.jmx.test.JMXInvokerUnitTestCase Test:testSetCustom Type:error Exception: javax.management.MBeanException Message: javax.management.InstanceNotFoundException: jboss.test:service=InvokerTest is not registered. - Suite: org.jboss.test.jmx.test.JMXInvokerUnitTestCase Test:testNotification Type:error Exception: java.lang.reflect.UndeclaredThrowableException Message: - Suite: org.jboss.test.jmx.test.JMXInvokerUnitTestCase Test:testServerFound Type:error Exception: org.jboss.deployment.DeploymentException Message: create operation failed for package file:/home/starksm/JBoss/jboss-3.2/build/output/jboss-3.2.4RC1/server/all/tmp/deploy/tmp38744invoker-adaptor-test.ear-contents/invoker-adaptor-test.sar; - nested throwable: (org.jboss.deployment.DeploymentException: Unhandled throwable propagated to the invoker by null getMBeanInfo:InvocationException: Cause: java.lang.SecurityException: Caller=null is not jduke; - nested throwable: (java.lang.R
RE: [JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.3.1_09) [AUTOMATED]
3.2 requires JDK 1.3 to compile so do not use JDK 1.4 specific
features like RuntimeException("Error resolving methods", e);
Use the org.jboss.util.NestedRuntimeException.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Sunday, January 04, 2004 12:10 PM
To: [EMAIL PROTECTED]
Subject: [JBoss-dev] Compilation Failed! JBoss
(Branch_3_2/winxp/1.3.1_09) [AUTOMATED]
_default:compile-classes:
[mkdir] Created dir: D:\jboss\jboss-head\jmx-remoting\output\classes
[javac] Compiling 19 source files to
D:\jboss\jboss-head\jmx-remoting\output\classes
D:\jboss\jboss-head\jmx-remoting\src\main\org\jboss\mx\remoting\JMXSubsy
stemInvocationHandler.java:87: cannot resolve symbol symbol :
constructor RuntimeException (java.lang.String,java.lang.Exception)
location: class java.lang.RuntimeException
throw new RuntimeException("Error resolving methods", e);
^
1 error
BUILD FAILED
file:D:/jboss/jboss-head/jmx-remoting/../tools/etc/buildmagic/buildmagic
.ent:403: Compile failed; see the compiler error output for details.
---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss Test Results: 95 % ( 1647 / 1725 ) - nearly there - who is gonna get us to 100%!. JBoss (HEAD/linux1/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Jan 6 02:40:46 GMT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 1725 Successful tests: 1647 Errors:59 Failures: 19 [time of test: 2004-01-06.00-45 GMT] [java.version: 1.4.1_05] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_05-b01] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.20-27.7] Useful resources: - http://jboss.kimptoc.net/linux1/1.4.1_05/logtests/testresults/reports/html//2004-01-06.00-45 for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: org.jboss.test.cache.test.local.TxConcurrentUnitTestCase Test:unknown Type:error Exception: junit.framework.AssertionFailedError Message: Timeout occurred - Suite: org.jboss.test.classloader.test.ScopingUnitTestCase Test:testWarXmlOverrides Type:error Exception: java.net.MalformedURLException Message: no protocol: /home/jbossci/jbossci2/jboss-head-test/testsuite/output/lib/oldxerces.war - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testSetUp Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyCMPField Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyEntityCMPFieldChange Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyEntityCreate Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] === Tue Jan 6 02:40:46 GMT 2004 === Linux nog.kimptoc.net 2.4.20-27.7 #1 Thu Dec 11 15:04:48 EST 2003 i686 unknown === java -version java version "1.4.1_05" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_05-b01) Java HotSpot(TM) Client VM (build 1.4.1_05-b01, mixed mode) --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.3.1_09) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sun Jan 4 20:09:54 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\gen-src (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. INFO:Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\transport\Connector.java --> ConnectorMBean qualified to org.jboss.remoting.transport.ConnectorMBean compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\classes [javac] Compiling 114 source files to D:\jboss\jboss-head\remoting\output\classes 2 warnings compile-rmi: [rmic] RMI Compiling 1 class to D:\jboss\jboss-head\remoting\output\classes compile-etc: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\etc [copy] Copying 3 files to D:\jboss\jboss-head\remoting\output\etc compile: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\lib [jar] Building jar: D:\jboss\jboss-head\remoting\output\lib\jboss-remoting.jar [touch] Creating D:\jboss\jboss-head\remoting\output\build-marker most: == == Finished with 'most' in module 'remoting'. == _module-remoting-most: [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\all\lib [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\all\deploy [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\default\lib [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\default\deploy == == Executing 'most' in module 'jmx-remoting'... == _buildmagic:init: configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: output: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: D:\jboss\jboss-head\jmx-remoting\output\gen-src _default:compile-classe
[JBoss-dev] JBoss Test Results: 57 % ( 421 / 727 ) - skipping class too much. JBoss (HEAD/linux1/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sun Jan 4 10:22:26 GMT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 727 Successful tests: 421 Errors:263 Failures: 43 [time of test: 2004-01-04.10-10 GMT] [java.version: 1.4.2_01] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.2_01-b06] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.20-27.7] Useful resources: - http://jboss.kimptoc.net/linux1/1.4.2_01/logtests/testresults/reports/html//2004-01-04.10-10 for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: VersionedObjectUnitTestCase Test:unknown Type:error Exception: junit.framework.AssertionFailedError Message: Timeout occurred - Suite: ScopingUnitTestCase Test:testSingletons Type:failure Exception: junit.framework.AssertionFailedError Message: checkVersion(V2) is true - Suite: CompleteUnitTestCase Test:unknown Type:error Exception: junit.framework.AssertionFailedError Message: Timeout occurred - Suite: RelationshipSchemaUnitTestCase Test:testAB_OneToOne_Bi_Table Type:failure Exception: net.sourceforge.junitejb.RemoteAssertionFailedError Message: expected:<1> but was:<0> - Suite: RelationshipSchemaUnitTestCase Test:testAB_OneToOne_Bi_FK Type:failure Exception: net.sourceforge.junitejb.RemoteAssertionFailedError Message: expected:<2> but was:<0> - Suite: RelationshipSchemaUnitTestCase Test:testAB_OneToOne_Uni_Table Type:failure Exception: net.sourceforge.junitejb.RemoteAssertionFailedError Message: expected:<1> but was:<0> === Sun Jan 4 10:22:26 GMT 2004 === Linux nog.kimptoc.net 2.4.20-27.7 #1 Thu Dec 11 15:04:48 EST 2003 i686 unknown === java -version java version "1.4.2_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_01-b06) Java HotSpot(TM) Client VM (build 1.4.2_01-b06, mixed mode) --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.3.1_09) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sun Jan 4 10:18:34 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\gen-src (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. INFO:Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\transport\Connector.java --> ConnectorMBean qualified to org.jboss.remoting.transport.ConnectorMBean compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\classes [javac] Compiling 114 source files to D:\jboss\jboss-head\remoting\output\classes 2 warnings compile-rmi: [rmic] RMI Compiling 1 class to D:\jboss\jboss-head\remoting\output\classes compile-etc: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\etc [copy] Copying 3 files to D:\jboss\jboss-head\remoting\output\etc compile: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\lib [jar] Building jar: D:\jboss\jboss-head\remoting\output\lib\jboss-remoting.jar [touch] Creating D:\jboss\jboss-head\remoting\output\build-marker most: == == Finished with 'most' in module 'remoting'. == _module-remoting-most: [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\all\lib [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\all\deploy [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\default\lib [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\default\deploy == == Executing 'most' in module 'jmx-remoting'... == _buildmagic:init: configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: output: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: D:\jboss\jboss-head\jmx-remoting\output\gen-src _default:compile-classe
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.3.1_09) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Mon Jan 5 14:08:45 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === _buildmagic:init: init: compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\classes [javac] Compiling 15 source files to D:\jboss\jboss-head\naming\output\classes compile-rmi: [rmic] RMI Compiling 1 class to D:\jboss\jboss-head\naming\output\classes compile-etc: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\etc [copy] Copying 4 files to D:\jboss\jboss-head\naming\output\etc compile: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\lib [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnpserver.jar [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnp-client.jar [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnp-tests.jar [touch] Creating D:\jboss\jboss-head\naming\output\build-marker most: == == Finished with 'most' in module 'naming'. == _module-naming-most: [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\lib [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\client == == Executing 'most' in module 'remoting'... == _buildmagic:init: configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\gen-src (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. INFO:Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\transport\Connector.java --> ConnectorMBean qualified to org.jboss.remoting.transport.ConnectorMBean compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\classes [javac] Compiling 114 source files to D:\jboss\jboss-head\remoting\output\classes D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\detection\multicast\MulticastDetector.java:272: cannot resolve symbol symbol : method isClosed
[JBoss-dev] Test Job Failed to Complete Successfully (or we gave up on it...)! JBoss (HEAD/linux1/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sun Jan 4 10:10:20 GMT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === [junit] Tests run: 4, Failures: 0, Errors: 1, Time elapsed: 92.172 sec [junit] TEST org.jboss.test.cts.test.CtsCmp2UnitTestCase FAILED [junit] Running org.jboss.test.cts.test.IndependentJarsUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 3, Time elapsed: 6.955 sec [junit] TEST org.jboss.test.cts.test.IndependentJarsUnitTestCase FAILED [junit] Running org.jboss.test.cts.test.MDBUnitTestCase [junit] Tests run: 2, Failures: 1, Errors: 1, Time elapsed: 29.445 sec [junit] TEST org.jboss.test.cts.test.MDBUnitTestCase FAILED [junit] Running org.jboss.test.cts.test.StatefulSessionUnitTestCase [junit] Tests run: 19, Failures: 0, Errors: 19, Time elapsed: 9.079 sec [junit] TEST org.jboss.test.cts.test.StatefulSessionUnitTestCase FAILED [junit] Running org.jboss.test.cts.test.StatelessSessionUnitTestCase [junit] Tests run: 8, Failures: 0, Errors: 8, Time elapsed: 7.337 sec [junit] TEST org.jboss.test.cts.test.StatelessSessionUnitTestCase FAILED [junit] Running org.jboss.test.dbtest.test.DbTypesUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 23.717 sec [junit] Running org.jboss.test.ejbconf.test.MetaDataUnitTestCase [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 3.642 sec [junit] Running org.jboss.test.ejbconf.test.ReadOnlyUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 8.32 sec [junit] Running org.jboss.test.entity.test.EJBLoadUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 3.707 sec [junit] Running org.jboss.test.entity.test.EntityUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 6.247 sec [junit] Running org.jboss.test.entity.test.PathologicalUnitTestCase [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 8.002 sec [junit] Running org.jboss.test.entityexc.test.EntityExcUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 7.557 sec [junit] Running org.jboss.test.exception.EntityExceptionUnitTestCase [junit] Tests run: 62, Failures: 0, Errors: 62, Time elapsed: 13.334 sec [junit] TEST org.jboss.test.exception.EntityExceptionUnitTestCase FAILED [junit] Running org.jboss.test.exception.ExceptionUnitTestCase [junit] Tests run: 27, Failures: 0, Errors: 27, Time elapsed: 9.292 sec [junit] TEST org.jboss.test.exception.ExceptionUnitTestCase FAILED [junit] Running org.jboss.test.ha.jmx.test.HAServiceMBeanSupportUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.638 sec [junit] Running org.jboss.test.ha.singleton.test.HASingletonControllerUnitTestCase [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 5.454 sec [junit] Running org.jboss.test.ha.singleton.test.HASingletonSupportUnitTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 5.844 sec [junit] Running org.jboss.test.hello.test.HelloCachedUnitTestCase [junit] TEST org.jboss.test.hello.test.HelloCachedUnitTestCase FAILED (timeout) [junit] Running org.jboss.test.idgen.test.IdGenUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 48.932 sec [junit] Running org.jboss.test.invokers.test.MultiInvokersUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 18.627 sec [junit] Running org.jboss.test.jbossmq.test.DestinationFullUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.375 sec [junit] Running org.jboss.test.jbossmq.test.HTTPConnectionUnitTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 9.559 sec [junit] Running org.jboss.test.jbossmq.test.HTTPJBossMQUnitTestCase [junit] Tests run: 19, Failures: 0, Errors: 0, Time elapsed: 126.91 sec [junit] Running org.jboss.test.jbossmq.test.JBossSessionRecoverUnitTestCase [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 13.49 sec [junit] Running org.jboss.test.jbossmq.test.LargeMessageUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 32.535 sec [junit] Running org.jboss.test.jbossmq.test.MessageBodyUnitTestCase [junit] Tests run: 6, Failures: 0, Errors: 0, Time el
[JBoss-dev] JBoss Test Results: 65 % ( 698 / 1067 ) - could do better. JBoss (HEAD/linux1/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Mon Jan 5 07:10:08 GMT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 1067 Successful tests: 698 Errors:346 Failures: 23 [time of test: 2004-01-05.00-42 GMT] [java.version: 1.4.1_05] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_05-b01] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.20-27.7] Useful resources: - http://jboss.kimptoc.net/linux1/1.4.1_05/logtests/testresults/reports/html//2004-01-05.00-42 for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: SchedulerUnitTestCase Test:unknown Type:error Exception: junit.framework.AssertionFailedError Message: Timeout occurred - Suite: TxConcurrentUnitTestCase Test:unknown Type:error Exception: junit.framework.AssertionFailedError Message: Timeout occurred - Suite: ScopingUnitTestCase Test:testWarXmlOverrides Type:error Exception: java.net.MalformedURLException Message: no protocol: /home/jbossci/jbossci2/jboss-head-test/testsuite/output/lib/oldxerces.war - Suite: ReadonlyUnitTestCase Test:testSetUp Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: ReadonlyUnitTestCase Test:testReadonlyCMPField Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: ReadonlyUnitTestCase Test:testReadonlyEntityCMPFieldChange Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] === Mon Jan 5 07:10:08 GMT 2004 === Linux nog.kimptoc.net 2.4.20-27.7 #1 Thu Dec 11 15:04:48 EST 2003 i686 unknown === java -version java version "1.4.1_05" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_05-b01) Java HotSpot(TM) Client VM (build 1.4.1_05-b01, mixed mode) --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss Test Results: 95 % ( 1490 / 1565 ) - nearly there - who is gonna get us to 100%!. JBoss (HEAD/winxp/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Mon Jan 5 01:38:18 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 1565 Successful tests: 1490 Errors:56 Failures: 19 [time of test: 2004-01-05.00-51 GMT] [java.version: 1.4.1_05] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_05-b01] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Windows XP] [os.arch: x86] [os.version: 5.1] Useful resources: - http://jboss.kimptoc.net/winxp/1.4.1_05/logtests/testresults/reports/html//2004-01-05.00-51 for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: ScopingUnitTestCase Test:testWarXmlOverrides Type:error Exception: java.net.MalformedURLException Message: unknown protocol: d - Suite: ReadonlyUnitTestCase Test:testSetUp Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: ReadonlyUnitTestCase Test:testReadonlyCMPField Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: ReadonlyUnitTestCase Test:testReadonlyEntityCMPFieldChange Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: ReadonlyUnitTestCase Test:testReadonlyEntityCreate Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: ReadonlyUnitTestCase Test:testReadonlySetFK Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] === Mon Jan 5 01:38:18 GMTST 2004 === CYGWIN_NT-5.1 quarks2 1.5.4(0.94/3/2) 2003-09-12 23:08 i686 unknown unknown Cygwin === java -version java version "1.4.1_05" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_05-b01) Java HotSpot(TM) Client VM (build 1.4.1_05-b01, mixed mode) --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss Test Results: 95 % ( 1491 / 1565 ) - nearly there - who is gonna get us to 100%!. JBoss (HEAD/winxp/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Mon Jan 5 03:00:07 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 1565 Successful tests: 1491 Errors:55 Failures: 19 [time of test: 2004-01-05.02-12 GMT] [java.version: 1.4.2_01] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.2_01-b06] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Windows XP] [os.arch: x86] [os.version: 5.1] Useful resources: - http://jboss.kimptoc.net/winxp/1.4.2_01/logtests/testresults/reports/html//2004-01-05.02-12 for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: ScopingUnitTestCase Test:testWarXmlOverrides Type:error Exception: java.net.MalformedURLException Message: unknown protocol: d - Suite: ReadonlyUnitTestCase Test:testSetUp Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: ReadonlyUnitTestCase Test:testReadonlyCMPField Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: ReadonlyUnitTestCase Test:testReadonlyEntityCMPFieldChange Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: ReadonlyUnitTestCase Test:testReadonlyEntityCreate Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: ReadonlyUnitTestCase Test:testReadonlySetFK Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] === Mon Jan 5 03:00:07 GMTST 2004 === CYGWIN_NT-5.1 quarks2 1.5.4(0.94/3/2) 2003-09-12 23:08 i686 unknown unknown Cygwin === java -version java version "1.4.2_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_01-b06) Java HotSpot(TM) Client VM (build 1.4.2_01-b06, mixed mode) --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss Test Results: 95 % ( 1682 / 1754 ) - nearly there - who is gonna get us to 100%!. JBoss (HEAD/winxp/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Jan 6 01:40:26 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 1754 Successful tests: 1682 Errors:54 Failures: 18 [time of test: 2004-01-06.00-48 GMT] [java.version: 1.4.1_05] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_05-b01] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Windows XP] [os.arch: x86] [os.version: 5.1] Useful resources: - http://jboss.kimptoc.net/winxp/1.4.1_05/logtests/testresults/reports/html//2004-01-06.00-48 for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: org.jboss.test.classloader.test.ScopingUnitTestCase Test:testWarXmlOverrides Type:error Exception: java.net.MalformedURLException Message: unknown protocol: d - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testSetUp Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyCMPField Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyEntityCMPFieldChange Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyEntityCreate Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlySetFK Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] === Tue Jan 6 01:40:27 GMTST 2004 === CYGWIN_NT-5.1 quarks2 1.5.4(0.94/3/2) 2003-09-12 23:08 i686 unknown unknown Cygwin === java -version java version "1.4.1_05" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_05-b01) Java HotSpot(TM) Client VM (build 1.4.1_05-b01, mixed mode) --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss Shutdown Failed! JBoss (HEAD/linux1/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sun Jan 4 10:11:35 GMT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === 10:11:30,428 WARN [NamingContext] Failed to connect to localhost:1099 javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:215) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1181) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:514) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507) at javax.naming.InitialContext.lookup(InitialContext.java:347) at org.jboss.Shutdown.main(Shutdown.java:182) Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:190) ... 5 more Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158) at java.net.Socket.connect(Socket.java:452) at java.net.Socket.connect(Socket.java:402) at java.net.Socket.(Socket.java:309) at java.net.Socket.(Socket.java:211) at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:69) at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:62) at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:186) ... 5 more Exception in thread "main" javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1115) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1192) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:514) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507) at javax.naming.InitialContext.lookup(InitialContext.java:347) at org.jboss.Shutdown.main(Shutdown.java:182) Caused by: java.net.SocketTimeoutException: Receive timed out at java.net.PlainDatagramSocketImpl.receive(Native Method) at java.net.DatagramSocket.receive(DatagramSocket.java:711) at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1093) ... 5 more JBOSS SHUTDOWN FAILED === Sun Jan 4 10:11:35 GMT 2004 === Linux nog.kimptoc.net 2.4.20-27.7 #1 Thu Dec 11 15:04:48 EST 2003 i686 unknown === java -version java version "1.4.2_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_01-b06) Java HotSpot(TM) Client VM (build 1.4.2_01-b06, mixed mode) --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.3.1_09) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sun Jan 4 12:50:31 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\gen-src (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. INFO:Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\transport\Connector.java --> ConnectorMBean qualified to org.jboss.remoting.transport.ConnectorMBean compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\classes [javac] Compiling 114 source files to D:\jboss\jboss-head\remoting\output\classes 2 warnings compile-rmi: [rmic] RMI Compiling 1 class to D:\jboss\jboss-head\remoting\output\classes compile-etc: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\etc [copy] Copying 3 files to D:\jboss\jboss-head\remoting\output\etc compile: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\lib [jar] Building jar: D:\jboss\jboss-head\remoting\output\lib\jboss-remoting.jar [touch] Creating D:\jboss\jboss-head\remoting\output\build-marker most: == == Finished with 'most' in module 'remoting'. == _module-remoting-most: [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\all\lib [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\all\deploy [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\default\lib [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\default\deploy == == Executing 'most' in module 'jmx-remoting'... == _buildmagic:init: configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: output: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: D:\jboss\jboss-head\jmx-remoting\output\gen-src _default:compile-classe
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.3.1_09) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Mon Jan 5 20:32:51 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === _buildmagic:init: init: compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\classes [javac] Compiling 15 source files to D:\jboss\jboss-head\naming\output\classes compile-rmi: [rmic] RMI Compiling 1 class to D:\jboss\jboss-head\naming\output\classes compile-etc: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\etc [copy] Copying 4 files to D:\jboss\jboss-head\naming\output\etc compile: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\lib [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnpserver.jar [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnp-client.jar [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnp-tests.jar [touch] Creating D:\jboss\jboss-head\naming\output\build-marker most: == == Finished with 'most' in module 'naming'. == _module-naming-most: [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\lib [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\client == == Executing 'most' in module 'remoting'... == _buildmagic:init: configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\gen-src (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. INFO:Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\transport\Connector.java --> ConnectorMBean qualified to org.jboss.remoting.transport.ConnectorMBean compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\classes [javac] Compiling 114 source files to D:\jboss\jboss-head\remoting\output\classes D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\detection\multicast\MulticastDetector.java:272: cannot resolve symbol symbol : method isClosed
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.3.1_09) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Mon Jan 5 17:38:24 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === _buildmagic:init: init: compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\classes [javac] Compiling 15 source files to D:\jboss\jboss-head\naming\output\classes compile-rmi: [rmic] RMI Compiling 1 class to D:\jboss\jboss-head\naming\output\classes compile-etc: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\etc [copy] Copying 4 files to D:\jboss\jboss-head\naming\output\etc compile: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\lib [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnpserver.jar [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnp-client.jar [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnp-tests.jar [touch] Creating D:\jboss\jboss-head\naming\output\build-marker most: == == Finished with 'most' in module 'naming'. == _module-naming-most: [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\lib [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\client == == Executing 'most' in module 'remoting'... == _buildmagic:init: configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\gen-src (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. INFO:Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\transport\Connector.java --> ConnectorMBean qualified to org.jboss.remoting.transport.ConnectorMBean compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\classes [javac] Compiling 114 source files to D:\jboss\jboss-head\remoting\output\classes D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\detection\multicast\MulticastDetector.java:272: cannot resolve symbol symbol : method isClosed
[JBoss-dev] JBoss Test Results: % ( / ) - . JBoss (HEAD/linux1/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sun Jan 4 07:21:52 GMT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === === Sun Jan 4 07:21:52 GMT 2004 === Linux nog.kimptoc.net 2.4.20-27.7 #1 Thu Dec 11 15:04:48 EST 2003 i686 unknown === java -version java version "1.4.1_05" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_05-b01) Java HotSpot(TM) Client VM (build 1.4.1_05-b01, mixed mode) --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.3.1_09) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Jan 6 08:04:45 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === _buildmagic:init: init: compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\classes [javac] Compiling 15 source files to D:\jboss\jboss-head\naming\output\classes compile-rmi: [rmic] RMI Compiling 1 class to D:\jboss\jboss-head\naming\output\classes compile-etc: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\etc [copy] Copying 4 files to D:\jboss\jboss-head\naming\output\etc compile: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\lib [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnpserver.jar [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnp-client.jar [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnp-tests.jar [touch] Creating D:\jboss\jboss-head\naming\output\build-marker most: == == Finished with 'most' in module 'naming'. == _module-naming-most: [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\lib [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\client == == Executing 'most' in module 'remoting'... == _buildmagic:init: configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\gen-src (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. INFO:Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\transport\Connector.java --> ConnectorMBean qualified to org.jboss.remoting.transport.ConnectorMBean compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\classes [javac] Compiling 114 source files to D:\jboss\jboss-head\remoting\output\classes D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\detection\multicast\MulticastDetector.java:272: cannot resolve symbol symbol : method isClosed
[JBoss-dev] Test Job Failed to Complete Successfully (or we gave up on it...)! JBoss (HEAD/linux1/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Mon Jan 5 10:10:24 GMT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === [junit] Running org.jboss.test.cmp2.dbschema.relationship.RelationshipSchemaUnitTestCase [junit] Tests run: 12, Failures: 0, Errors: 0, Time elapsed: 27.096 sec [junit] Running org.jboss.test.cmp2.ejbselect.EJBSelectUnitTestCase [junit] Tests run: 19, Failures: 0, Errors: 0, Time elapsed: 12.071 sec [junit] Running org.jboss.test.cmp2.enum.test.EnumUnitTestCase [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 5.72 sec [junit] Running org.jboss.test.cmp2.fkmapping.test.FKMappingUnitTestCase [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 13.384 sec [junit] Running org.jboss.test.cmp2.fkstackoverflow.test.FKStackOverflowUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 45.268 sec [junit] Running org.jboss.test.cmp2.idxandusersql.test.IdxAndUsersqlUnitTestCase [junit] TEST org.jboss.test.cmp2.idxandusersql.test.IdxAndUsersqlUnitTestCase FAILED (timeout) [junit] Running org.jboss.test.cmp2.keygen.test.KeyGenerationUnitTestCase [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 30.414 sec [junit] Running org.jboss.test.cmp2.lob.LOBUnitTestCase [junit] Tests run: 19, Failures: 0, Errors: 0, Time elapsed: 35.294 sec [junit] Running org.jboss.test.cmp2.optimisticlock.test.OptimisticLockUnitTestCase [junit] TEST org.jboss.test.cmp2.optimisticlock.test.OptimisticLockUnitTestCase FAILED (timeout) [junit] Running org.jboss.test.cmp2.passivation.test.EntityPassivationUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 143.35 sec [junit] Running org.jboss.test.cmp2.perf.test.PerfUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 137.566 sec [junit] Running org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase [junit] Tests run: 8, Failures: 0, Errors: 8, Time elapsed: 12.045 sec [junit] TEST org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase FAILED [junit] Running org.jboss.test.cmp2.relationship.RelationshipUnitTestCase [junit] Tests run: 21, Failures: 21, Errors: 0, Time elapsed: 17.016 sec [junit] TEST org.jboss.test.cmp2.relationship.RelationshipUnitTestCase FAILED [junit] Running org.jboss.test.cmp2.simple.PageSizeUnitTestCase [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 7.83 sec [junit] TEST org.jboss.test.cmp2.simple.PageSizeUnitTestCase FAILED [junit] Running org.jboss.test.cmp2.simple.SimpleUnitTestCase [junit] Tests run: 44, Failures: 0, Errors: 44, Time elapsed: 9.238 sec [junit] TEST org.jboss.test.cmp2.simple.SimpleUnitTestCase FAILED [junit] Running org.jboss.test.cts.test.BmpUnitTestCase [junit] Tests run: 12, Failures: 0, Errors: 12, Time elapsed: 25.92 sec [junit] TEST org.jboss.test.cts.test.BmpUnitTestCase FAILED [junit] Running org.jboss.test.cts.test.CmpUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 3, Time elapsed: 75.314 sec [junit] TEST org.jboss.test.cts.test.CmpUnitTestCase FAILED [junit] Running org.jboss.test.cts.test.CtsCmp2UnitTestCase [junit] TEST org.jboss.test.cts.test.CtsCmp2UnitTestCase FAILED (timeout) [junit] Running org.jboss.test.cts.test.IndependentJarsUnitTestCase [junit] Tests run: 3, Failures: 0, Errors: 3, Time elapsed: 22.463 sec [junit] TEST org.jboss.test.cts.test.IndependentJarsUnitTestCase FAILED [junit] Running org.jboss.test.cts.test.MDBUnitTestCase [junit] Tests run: 2, Failures: 1, Errors: 1, Time elapsed: 74.108 sec [junit] TEST org.jboss.test.cts.test.MDBUnitTestCase FAILED [junit] Running org.jboss.test.cts.test.StatefulSessionUnitTestCase [junit] Tests run: 19, Failures: 0, Errors: 19, Time elapsed: 14.638 sec [junit] TEST org.jboss.test.cts.test.StatefulSessionUnitTestCase FAILED [junit] Running org.jboss.test.cts.test.StatelessSessionUnitTestCase [junit] Tests run: 8, Failures: 0, Errors: 8, Time elapsed: 39.574 sec [junit] TEST org.jboss.test.cts.test.StatelessSessionUnitTestCase FAILED [junit] Running org.jboss.test.dbtest.test.DbTypesUnitTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 39.431 sec [junit] Running org.jboss.test.ejbconf.test.MetaDataUnitTestCase
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.3.1_09) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Mon Jan 5 23:41:33 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === _buildmagic:init: init: compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\classes [javac] Compiling 15 source files to D:\jboss\jboss-head\naming\output\classes compile-rmi: [rmic] RMI Compiling 1 class to D:\jboss\jboss-head\naming\output\classes compile-etc: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\etc [copy] Copying 4 files to D:\jboss\jboss-head\naming\output\etc compile: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\lib [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnpserver.jar [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnp-client.jar [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnp-tests.jar [touch] Creating D:\jboss\jboss-head\naming\output\build-marker most: == == Finished with 'most' in module 'naming'. == _module-naming-most: [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\lib [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\client == == Executing 'most' in module 'remoting'... == _buildmagic:init: configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\gen-src (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. INFO:Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\transport\Connector.java --> ConnectorMBean qualified to org.jboss.remoting.transport.ConnectorMBean compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\classes [javac] Compiling 114 source files to D:\jboss\jboss-head\remoting\output\classes D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\detection\multicast\MulticastDetector.java:272: cannot resolve symbol symbol : method isClosed
[JBoss-dev] JBoss Test Results: 95 % ( 1674 / 1753 ) - nearly there - who is gonna get us to 100%!. JBoss (HEAD/winxp/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Jan 6 03:09:19 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 1753 Successful tests: 1674 Errors:61 Failures: 18 [time of test: 2004-01-06.02-14 GMT] [java.version: 1.4.2_01] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.2_01-b06] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Windows XP] [os.arch: x86] [os.version: 5.1] Useful resources: - http://jboss.kimptoc.net/winxp/1.4.2_01/logtests/testresults/reports/html//2004-01-06.02-14 for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: org.jboss.test.cache.test.local.TxConcurrentUnitTestCase Test:unknown Type:error Exception: junit.framework.AssertionFailedError Message: Timeout occurred - Suite: org.jboss.test.classloader.test.ScopingUnitTestCase Test:testWarXmlOverrides Type:error Exception: java.net.MalformedURLException Message: unknown protocol: d - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testSetUp Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyCMPField Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyEntityCMPFieldChange Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyEntityCreate Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] === Tue Jan 6 03:09:19 GMTST 2004 === CYGWIN_NT-5.1 quarks2 1.5.4(0.94/3/2) 2003-09-12 23:08 i686 unknown unknown Cygwin === java -version java version "1.4.2_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_01-b06) Java HotSpot(TM) Client VM (build 1.4.2_01-b06, mixed mode) --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/linux1/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Mon Jan 5 10:38:25 GMT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === 10:38 Jan 05 java version "1.4.2_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_01-b06) Java HotSpot(TM) Client VM (build 1.4.2_01-b06, mixed mode) Searching for build.xml ... Buildfile: /home/jbossci/jbossci2/jboss-head/build/build.xml _buildmagic:init: Trying to override old definition of task property _buildmagic:init:local-properties: _buildmagic:init:buildlog: configure: Caught exception (org.apache.tools.ant.BuildException) while expanding apache.tomcat41.classpath: /home/jbossci/jbossci2/jboss-head/thirdparty/apache-tomcat41 not found. Caught exception (org.apache.tools.ant.BuildException) while expanding apache.tomcat50.classpath: /home/jbossci/jbossci2/jboss-head/thirdparty/apache-tomcat50 not found. Caught exception (org.apache.tools.ant.BuildException) while expanding beanshell.beanshell.classpath: /home/jbossci/jbossci2/jboss-head/thirdparty/beanshell-beanshell/lib not found. [echo] groups: default [echo] modules: common,jmx,system,naming,remoting,aop,j2ee,transaction,server,security,messaging,connector,cluster,jetty,varia,jboss.net,iiop,management,tomcat,console,cache,compatibility,aspects,media init: _buildmagic:modules:most: == == Executing 'most' in module 'common'... == _buildmagic:init: configure: Caught exception (org.apache.tools.ant.BuildException) while expanding apache.tomcat41.classpath: /home/jbossci/jbossci2/jboss-head/thirdparty/apache-tomcat41 not found. Caught exception (org.apache.tools.ant.BuildException) while expanding apache.tomcat50.classpath: /home/jbossci/jbossci2/jboss-head/thirdparty/apache-tomcat50 not found. Caught exception (org.apache.tools.ant.BuildException) while expanding beanshell.beanshell.classpath: /home/jbossci/jbossci2/jboss-head/thirdparty/beanshell-beanshell/lib not found. Overriding previous definition of reference to xdoclet.task.classpath Caught exception (org.apache.tools.ant.BuildException) while expanding xdoclet.task.classpath: /home/jbossci/jbossci2/jboss-head/thirdparty/xdoclet-xdoclet/lib not found. BUILD FAILED file:/home/jbossci/jbossci2/jboss-head/common/build.xml:159: /home/jbossci/jbossci2/jboss-head/thirdparty/xdoclet-xdoclet/lib not found. Total time: 5 seconds === Mon Jan 5 10:38:25 GMT 2004 === Linux nog.kimptoc.net 2.4.20-27.7 #1 Thu Dec 11 15:04:48 EST 2003 i686 unknown === java -version java version "1.4.2_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_01-b06) Java HotSpot(TM) Client VM (build 1.4.2_01-b06, mixed mode) --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss Shutdown Failed! JBoss (HEAD/linux1/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Mon Jan 5 10:11:46 GMT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === 10:11:41,470 WARN [NamingContext] Failed to connect to localhost:1099 javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:215) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1181) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:514) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507) at javax.naming.InitialContext.lookup(InitialContext.java:347) at org.jboss.Shutdown.main(Shutdown.java:182) Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:190) ... 5 more Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158) at java.net.Socket.connect(Socket.java:452) at java.net.Socket.connect(Socket.java:402) at java.net.Socket.(Socket.java:309) at java.net.Socket.(Socket.java:211) at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:69) at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:62) at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:186) ... 5 more Exception in thread "main" javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1115) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1192) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:514) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507) at javax.naming.InitialContext.lookup(InitialContext.java:347) at org.jboss.Shutdown.main(Shutdown.java:182) Caused by: java.net.SocketTimeoutException: Receive timed out at java.net.PlainDatagramSocketImpl.receive(Native Method) at java.net.DatagramSocket.receive(DatagramSocket.java:711) at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1093) ... 5 more JBOSS SHUTDOWN FAILED === Mon Jan 5 10:11:46 GMT 2004 === Linux nog.kimptoc.net 2.4.20-27.7 #1 Thu Dec 11 15:04:48 EST 2003 i686 unknown === java -version java version "1.4.2_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_01-b06) Java HotSpot(TM) Client VM (build 1.4.2_01-b06, mixed mode) --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.3.1_09) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Mon Jan 5 12:19:34 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === _buildmagic:init: init: compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\classes [javac] Compiling 15 source files to D:\jboss\jboss-head\naming\output\classes compile-rmi: [rmic] RMI Compiling 1 class to D:\jboss\jboss-head\naming\output\classes compile-etc: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\etc [copy] Copying 4 files to D:\jboss\jboss-head\naming\output\etc compile: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\lib [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnpserver.jar [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnp-client.jar [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnp-tests.jar [touch] Creating D:\jboss\jboss-head\naming\output\build-marker most: == == Finished with 'most' in module 'naming'. == _module-naming-most: [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\lib [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\client == == Executing 'most' in module 'remoting'... == _buildmagic:init: configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\gen-src (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. INFO:Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\transport\Connector.java --> ConnectorMBean qualified to org.jboss.remoting.transport.ConnectorMBean compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\classes [javac] Compiling 114 source files to D:\jboss\jboss-head\remoting\output\classes D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\detection\multicast\MulticastDetector.java:272: cannot resolve symbol symbol : method isClosed
[JBoss-dev] JBoss Test Results: 95 % ( 1630 / 1711 ) - nearly there - who is gonna get us to 100%!. JBoss (HEAD/linux1/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Tue Jan 6 05:32:25 GMT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 1711 Successful tests: 1630 Errors:61 Failures: 20 [time of test: 2004-01-06.03-09 GMT] [java.version: 1.4.2_01] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.2_01-b06] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.20-27.7] Useful resources: - http://jboss.kimptoc.net/linux1/1.4.2_01/logtests/testresults/reports/html//2004-01-06.03-09 for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: org.jboss.test.cache.test.local.TxConcurrentUnitTestCase Test:unknown Type:error Exception: junit.framework.AssertionFailedError Message: Timeout occurred - Suite: org.jboss.test.classloader.test.ScopingUnitTestCase Test:testWarXmlOverrides Type:error Exception: java.net.MalformedURLException Message: no protocol: /home/jbossci/jbossci2/jboss-head-test/testsuite/output/lib/oldxerces.war - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testSetUp Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyCMPField Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyEntityCMPFieldChange Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] - Suite: org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase Test:testReadonlyEntityCreate Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Column not found: ID in statement [INSERT INTO Publisher (id, name) VALUES (1,'O''Reilly & Associates')] === Tue Jan 6 05:32:25 GMT 2004 === Linux nog.kimptoc.net 2.4.20-27.7 #1 Thu Dec 11 15:04:48 EST 2003 i686 unknown === java -version java version "1.4.2_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_01-b06) Java HotSpot(TM) Client VM (build 1.4.2_01-b06, mixed mode) --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.3.1_09) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Mon Jan 5 10:15:38 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === _buildmagic:init: init: compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\classes [javac] Compiling 15 source files to D:\jboss\jboss-head\naming\output\classes compile-rmi: [rmic] RMI Compiling 1 class to D:\jboss\jboss-head\naming\output\classes compile-etc: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\etc [copy] Copying 4 files to D:\jboss\jboss-head\naming\output\etc compile: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\lib [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnpserver.jar [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnp-client.jar [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnp-tests.jar [touch] Creating D:\jboss\jboss-head\naming\output\build-marker most: == == Finished with 'most' in module 'naming'. == _module-naming-most: [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\lib [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\client == == Executing 'most' in module 'remoting'... == _buildmagic:init: configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\gen-src (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. INFO:Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\transport\Connector.java --> ConnectorMBean qualified to org.jboss.remoting.transport.ConnectorMBean compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\classes [javac] Compiling 114 source files to D:\jboss\jboss-head\remoting\output\classes D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\detection\multicast\MulticastDetector.java:272: cannot resolve symbol symbol : method isClosed
[JBoss-dev] JBoss Test Results: 58 % ( 316 / 538 ) - skipping class too much. JBoss (HEAD/linux1/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Mon Jan 5 10:22:30 GMT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 538 Successful tests: 316 Errors:200 Failures: 22 [time of test: 2004-01-05.10-10 GMT] [java.version: 1.4.2_01] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.2_01-b06] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.20-27.7] Useful resources: - http://jboss.kimptoc.net/linux1/1.4.2_01/logtests/testresults/reports/html//2004-01-05.10-10 for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: AOPUnitTestCase Test:unknown Type:error Exception: junit.framework.AssertionFailedError Message: Timeout occurred - Suite: RemotingUnitTestCase Test:unknown Type:error Exception: junit.framework.AssertionFailedError Message: Timeout occurred - Suite: SecurityUnitTestCase Test:unknown Type:error Exception: junit.framework.AssertionFailedError Message: Timeout occurred - Suite: TxLockUnitTestCase Test:unknown Type:error Exception: junit.framework.AssertionFailedError Message: Timeout occurred - Suite: VersionedObjectUnitTestCase Test:testAll Type:error Exception: javax.management.RuntimeMBeanException Message: java.lang.RuntimeException: loader constraints violated when linking org/jboss/test/aop/bean/Address class - Suite: VersionedObjectUnitTestCase Test:testServerFound Type:error Exception: org.jboss.deployment.IncompleteDeploymentException Message: === Mon Jan 5 10:22:30 GMT 2004 === Linux nog.kimptoc.net 2.4.20-27.7 #1 Thu Dec 11 15:04:48 EST 2003 i686 unknown === java -version java version "1.4.2_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_01-b06) Java HotSpot(TM) Client VM (build 1.4.2_01-b06, mixed mode) --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.3.1_09) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Mon Jan 5 08:10:45 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === _buildmagic:init: init: compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\classes [javac] Compiling 15 source files to D:\jboss\jboss-head\naming\output\classes compile-rmi: [rmic] RMI Compiling 1 class to D:\jboss\jboss-head\naming\output\classes compile-etc: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\etc [copy] Copying 4 files to D:\jboss\jboss-head\naming\output\etc compile: [mkdir] Created dir: D:\jboss\jboss-head\naming\output\lib [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnpserver.jar [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnp-client.jar [jar] Building jar: D:\jboss\jboss-head\naming\output\lib\jnp-tests.jar [touch] Creating D:\jboss\jboss-head\naming\output\build-marker most: == == Finished with 'most' in module 'naming'. == _module-naming-most: [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\lib [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\client == == Executing 'most' in module 'remoting'... == _buildmagic:init: configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\gen-src (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. INFO:Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\transport\Connector.java --> ConnectorMBean qualified to org.jboss.remoting.transport.ConnectorMBean compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\classes [javac] Compiling 114 source files to D:\jboss\jboss-head\remoting\output\classes D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\detection\multicast\MulticastDetector.java:272: cannot resolve symbol symbol : method isClosed
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.3.1_09) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sun Jan 4 17:33:12 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\gen-src (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. INFO:Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\transport\Connector.java --> ConnectorMBean qualified to org.jboss.remoting.transport.ConnectorMBean compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\classes [javac] Compiling 114 source files to D:\jboss\jboss-head\remoting\output\classes 2 warnings compile-rmi: [rmic] RMI Compiling 1 class to D:\jboss\jboss-head\remoting\output\classes compile-etc: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\etc [copy] Copying 3 files to D:\jboss\jboss-head\remoting\output\etc compile: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\lib [jar] Building jar: D:\jboss\jboss-head\remoting\output\lib\jboss-remoting.jar [touch] Creating D:\jboss\jboss-head\remoting\output\build-marker most: == == Finished with 'most' in module 'remoting'. == _module-remoting-most: [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\all\lib [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\all\deploy [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\default\lib [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\default\deploy == == Executing 'most' in module 'jmx-remoting'... == _buildmagic:init: configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: output: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: D:\jboss\jboss-head\jmx-remoting\output\gen-src _default:compile-classe
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.3.1_09) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sun Jan 4 08:07:13 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\gen-src (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. INFO:Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\transport\Connector.java --> ConnectorMBean qualified to org.jboss.remoting.transport.ConnectorMBean compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\classes [javac] Compiling 114 source files to D:\jboss\jboss-head\remoting\output\classes 2 warnings compile-rmi: [rmic] RMI Compiling 1 class to D:\jboss\jboss-head\remoting\output\classes compile-etc: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\etc [copy] Copying 3 files to D:\jboss\jboss-head\remoting\output\etc compile: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\lib [jar] Building jar: D:\jboss\jboss-head\remoting\output\lib\jboss-remoting.jar [touch] Creating D:\jboss\jboss-head\remoting\output\build-marker most: == == Finished with 'most' in module 'remoting'. == _module-remoting-most: [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\all\lib [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\all\deploy [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\default\lib [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\default\deploy == == Executing 'most' in module 'jmx-remoting'... == _buildmagic:init: configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: output: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: D:\jboss\jboss-head\jmx-remoting\output\gen-src _default:compile-classe
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/linux1/1.4.1_05) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Mon Jan 5 10:37:57 GMT 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === 10:37 Jan 05 java version "1.4.1_05" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_05-b01) Java HotSpot(TM) Client VM (build 1.4.1_05-b01, mixed mode) Searching for build.xml ... Buildfile: /home/jbossci/jbossci2/jboss-head/build/build.xml _buildmagic:init: Trying to override old definition of task property _buildmagic:init:local-properties: _buildmagic:init:buildlog: configure: Caught exception (org.apache.tools.ant.BuildException) while expanding apache.tomcat41.classpath: /home/jbossci/jbossci2/jboss-head/thirdparty/apache-tomcat41 not found. Caught exception (org.apache.tools.ant.BuildException) while expanding apache.tomcat50.classpath: /home/jbossci/jbossci2/jboss-head/thirdparty/apache-tomcat50 not found. Caught exception (org.apache.tools.ant.BuildException) while expanding beanshell.beanshell.classpath: /home/jbossci/jbossci2/jboss-head/thirdparty/beanshell-beanshell/lib not found. [echo] groups: default [echo] modules: common,jmx,system,naming,remoting,aop,j2ee,transaction,server,security,messaging,connector,cluster,jetty,varia,jboss.net,iiop,management,tomcat,console,cache,compatibility,aspects,media init: _buildmagic:modules:most: == == Executing 'most' in module 'common'... == _buildmagic:init: configure: Caught exception (org.apache.tools.ant.BuildException) while expanding apache.tomcat41.classpath: /home/jbossci/jbossci2/jboss-head/thirdparty/apache-tomcat41 not found. Caught exception (org.apache.tools.ant.BuildException) while expanding apache.tomcat50.classpath: /home/jbossci/jbossci2/jboss-head/thirdparty/apache-tomcat50 not found. Caught exception (org.apache.tools.ant.BuildException) while expanding beanshell.beanshell.classpath: /home/jbossci/jbossci2/jboss-head/thirdparty/beanshell-beanshell/lib not found. Overriding previous definition of reference to xdoclet.task.classpath Caught exception (org.apache.tools.ant.BuildException) while expanding xdoclet.task.classpath: /home/jbossci/jbossci2/jboss-head/thirdparty/xdoclet-xdoclet/lib not found. BUILD FAILED file:/home/jbossci/jbossci2/jboss-head/common/build.xml:159: /home/jbossci/jbossci2/jboss-head/thirdparty/xdoclet-xdoclet/lib not found. Total time: 6 seconds === Mon Jan 5 10:37:57 GMT 2004 === Linux nog.kimptoc.net 2.4.20-27.7 #1 Thu Dec 11 15:04:48 EST 2003 i686 unknown === java -version java version "1.4.1_05" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_05-b01) Java HotSpot(TM) Client VM (build 1.4.1_05-b01, mixed mode) --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Compilation Failed! JBoss (Branch_3_2/winxp/1.3.1_09) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Sun Jan 4 23:09:45 GMTST 2004 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: jars: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\gen-src (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jmx-module-jb3.jar!/xdoclet/modules/jmx/resources/mbean.xdt'. (XDocletMain.start 45 ) Running (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ServerInterceptorChain' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.transport.Connector' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. (TemplateSubTask.engineStarted 788 ) Generating output for 'org.jboss.remoting.ClientInvokerAdapter' using template file 'jar:file:D:\jboss\jboss-head\thirdparty\xdoclet\xdoclet\lib\xdoclet-jboss-module-jb3.jar!/xdoclet/modules/jboss/jmx/resources/jbossmx-xml-descriptor.xdt'. INFO:Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: D:\jboss\jboss-head\remoting\src\main\org\jboss\remoting\transport\Connector.java --> ConnectorMBean qualified to org.jboss.remoting.transport.ConnectorMBean compile-classes: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\classes [javac] Compiling 114 source files to D:\jboss\jboss-head\remoting\output\classes 2 warnings compile-rmi: [rmic] RMI Compiling 1 class to D:\jboss\jboss-head\remoting\output\classes compile-etc: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\etc [copy] Copying 3 files to D:\jboss\jboss-head\remoting\output\etc compile: [mkdir] Created dir: D:\jboss\jboss-head\remoting\output\lib [jar] Building jar: D:\jboss\jboss-head\remoting\output\lib\jboss-remoting.jar [touch] Creating D:\jboss\jboss-head\remoting\output\build-marker most: == == Finished with 'most' in module 'remoting'. == _module-remoting-most: [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\all\lib [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\all\deploy [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\default\lib [copy] Copying 1 file to D:\jboss\jboss-head\build\output\testbuild\server\default\deploy == == Executing 'most' in module 'jmx-remoting'... == _buildmagic:init: configure: xdoclet-task-classpath-check: init: _buildmagic:build-bypass-checker: _buildmagic:build-bypass-notice: _buildmagic:build-bypass-check: output: _buildmagic:init: init: compile-mbean-sources: [mkdir] Created dir: D:\jboss\jboss-head\jmx-remoting\output\gen-src _default:compile-classe
