[JBoss-dev] Ulf Schroeter/BDF/Mobilcom ist außer Haus.
Ich werde ab 08.03.2004 nicht im Büro sein. Ich kehre zurück am 22.03.2004. Ich werde Ihre Nachricht nach meiner Rückkehr beantworten. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Ulf Schroeter/BDF/Mobilcom ist außer Haus.
Ich werde ab 08.03.2004 nicht im Büro sein. Ich kehre zurück am 22.03.2004. Ich werde Ihre Nachricht nach meiner Rückkehr beantworten. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Ulf Schroeter/BDF/Mobilcom ist außer Haus.
Ich werde ab 08.03.2004 nicht im Büro sein. Ich kehre zurück am 22.03.2004. Ich werde Ihre Nachricht nach meiner Rückkehr beantworten. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Ulf Schroeter/BDF/Mobilcom ist außer Haus.
Ich werde ab 08.03.2004 nicht im Büro sein. Ich kehre zurück am 22.03.2004. Ich werde Ihre Nachricht nach meiner Rückkehr beantworten. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Ulf Schroeter/BDF/Mobilcom ist außer Haus.
Ich werde ab 08.03.2004 nicht im Büro sein. Ich kehre zurück am 22.03.2004. Ich werde Ihre Nachricht nach meiner Rückkehr beantworten. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Antwort: RE: c/s JBossMQ status, was: [JBoss-dev] JBossMQ rewrite
The current JMS rewrite by Nathan, Adrian, and Bela is going quite well and we will be replacing the old system in the fall. Don't work on a codebase that is going to be retired and needs to live in depracated mode for awhile. A refactoring isn't what is needed in the JMS subsystem. I don't want to be pessimistic, but it took quite a long time to stabilize the current JBossMQ. This is especially true for heavy load scenarios. The ongoing JMS rewrite hopefully will bring significant improvements, but first of all it has to proof stability and spec compliance before it is a valid alternative for production usage. Many JMS users will have to / want to stay with JBossMQ for quite a longer than maybe expected ! Therefore ongoing improvements of the existing JBossMQ code have quite a value ( atleast for me as a JMS user, who requires a stable and matured JMS plattform :-) Regards Ulf
Antwort: Re: [JBoss-dev] Re: default web server
Hi Frank, can you give some more detailed informations about your 'much better' experiences with Jetty ? Would be interesting ! Regards Ulf Frank Morton [EMAIL PROTECTED] Gesendet von: [EMAIL PROTECTED] 27.06.2003 03:05 Bitte antworten an jboss-development An:[EMAIL PROTECTED] Kopie: Thema:Re: [JBoss-dev] Re: default web server We will continue to use Jetty no matter. Our experience has been much better with Jetty than Tomcat. On Thursday, June 26, 2003, at 06:30 PM, Greg Wilkins wrote: Scott M Stark wrote: Simply because Tomcat is the defacto standard and the default choice for most of our users and I'm not happy with the level of integration we currently offer. For those of you who are using Jetty and are happy with that choice, I just want to assure you that regardless of what decisions the JBoss Group make, that Jetty in JBoss will continue to be supported by a strong open source community sponsored by Mort Bay and commercial support will be available for it from the core developers network. So we are continuing to develop and support the jetty sar for JBoss and hopefully it will continue to live in the JBoss project (although we may want to review the duplicate source tree issue). The intent will be to keep the web container services totally pluggable so that you can simple drop in the web sar of *your* choice. regards -- /** * Greg Wilkins * Partner * Core Developers Network **/ There's a difference between knowing the path and walking the path - morpheus --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] default web server
Has jetty been replaced by tomcat-41 (jbossweb-tomcat41.sar) as default webserver in latest Branch_3_2 ? Regards Ulf
[JBoss-dev] performance drop
When running a grinder entity bean loadtest against JBoss-3.2.2RC2 we realize a significant performance drop ever 60 seconds for 2-5 seconds. Obviously there is some periodic background processing. Has anybody an idea what kind of process is causing this drop ( garbage collector ? ) Regards Ulf
Antwort: RE: [JBoss-dev] performance drop
Thanks for the link , but GC was just meant as illustration :-) In fact I think that most probably another JBoss internal background process is causing this drop Healey, Alex [EMAIL PROTECTED] Gesendet von: [EMAIL PROTECTED] 24.06.2003 12:57 Bitte antworten an jboss-development An:'[EMAIL PROTECTED]' [EMAIL PROTECTED] Kopie: Thema:RE: [JBoss-dev] performance drop Have a look at this article if you want to investigate gc performance. http://developer.java.sun.com/developer/technicalArticles/Programming/turbo/ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 24 June 2003 11:47 To: [EMAIL PROTECTED] Subject: [JBoss-dev] performance drop When running a grinder entity bean loadtest against JBoss-3.2.2RC2 we realize a significant performance drop ever 60 seconds for 2-5 seconds. Obviously there is some periodic background processing. Has anybody an idea what kind of process is causing this drop ( garbage collector ? ) Regards Ulf -- If you have received this e-mail in error or wish to read our e-mail disclaimer statement and monitoring policy, please refer to http://www.drkw.com/disc/email/ or contact the sender. --
Antwort: RE: [JBoss-dev] JBossMQ rewrite
Hi Nathan, thanks for the information. I already have seen your first CVS code. Is there any further information available about the planed design and feature set ? You already gave some interesting insights about the p2p feature. When using jms in an enterprise production environment - as we would like to do - the following aspects are of even more importance ( and most of these isues are not handled very well in the current JBossMQ implementation ) (1) EFFICIENT handling of large / high numbers of PERSISTENT topic and queue messages (2) message redelivery / message throttling clustering / failover (3) messaging system monitoring / administration I there a way to participate in the your ongoing rewrite ? Regards Ulf Nathan Phelps [EMAIL PROTECTED] Gesendet von: [EMAIL PROTECTED] 15.06.2003 00:00 Bitte antworten an jboss-development An:[EMAIL PROTECTED] Kopie: Thema:RE: [JBoss-dev] JBossMQ rewrite JBossMQthe current code basewill continue to ship with JBoss 3.2 which is, and will remain for some time, the production version. Therefore, making changes to the current code base IS NOT worthless. However, I am working on a brand new implementation with assistance from Adrian, Bela, Bill, Tom Elrod, and Troy Daley. The framework code has recently been checked in to the jboss-jms module in CVS. It is early, but a start. In addition to the traditional client-server oriented JMS we're working on, at Bela's suggestion, I was able to implement a pure p2p implementation of the JMS topic messaging domain that does non-durable subscribers over JavaGroups. At Bill's request, we're going to get this code out there quickly (July). To my knowledge this will be the first pure p2p (server-less) JMS implementation in open source and it will provide very fast in-firewall publish and subscribe over multicast. Thanks, Nathan Phelps JMS/JBoss (Reloaded) Project Lead JBoss Group, L.L.C. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, June 13, 2003 4:45 AM To: [EMAIL PROTECTED] Subject: [JBoss-dev] JBossMQ rewrite Can anyone give me some informations about the current state of the announced rewrite of JBossMQ for JBoss 4 ? Does it still make sense to implement needed features on the current JBossMQ implementation ? I don't want to spend time on something that gets nuked in short time :-) Regards Ulf --- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBossMQ rewrite
Can anyone give me some informations about the current state of the announced rewrite of JBossMQ for JBoss 4 ? Does it still make sense to implement needed features on the current JBossMQ implementation ? I don't want to spend time on something that gets nuked in short time :-) Regards Ulf
[JBoss-dev] JSR77 OBJECT_NAME
JSR77 specifies in JSR77.3.1.1.1 parent-j2eeType as required key property for OBJECT_NAME. I don't see this property as part of the ObjectName attribute of a managed object via JMX console. Just filtered or not implemented ? Regards Ulf
[JBoss-dev] JSR77 OBJECT_NAME
Please forget last question, I think I got it ! ( Sometimes reading the next page helps :-) Sorry Ulf
[JBoss-dev] Updates to CVS-Branch and CVS-Head
Should all updates (bugfix/feature) for a branch also be applied to HEAD ? There are some updates that have only been applied to Branch_3_2, although they don't seem to be specific only for that Branch. According to my ( not very sophisticated... ) understanding of JBoss branch policy these updates will be lost for the next upcomming branch ( because that branch uses HEAD as starting point ) ?!? Regards Ulf
Antwort: RE: [JBoss-dev] Updates to CVS-Branch and CVS-Head
Ok, but just for info: is my assumption right, that updates to a branch without also applying them to HEAD will not show up in the following branch ? Regards Ulf Adrian Brock [EMAIL PROTECTED] Gesendet von: [EMAIL PROTECTED] 06.06.2003 13:39 Bitte antworten an jboss-development An:[EMAIL PROTECTED] Kopie: Thema:RE: [JBoss-dev] Updates to CVS-Branch and CVS-Head Hi Ulf, People use different strategies. Some apply fixes at the same time, others apply them in bulk. I tend to mix the two, keeping the diffs of things I've not applied to head. Regards, Adrian Adrian Brock Director of Support Back Office JBoss Group, LLC -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: 06 June 2003 12:25 To: [EMAIL PROTECTED] Subject: [JBoss-dev] Updates to CVS-Branch and CVS-Head Should all updates (bugfix/feature) for a branch also be applied to HEAD ? There are some updates that have only been applied to Branch_3_2, although they don't seem to be specific only for that Branch. According to my ( not very sophisticated... ) understanding of JBoss branch policy these updates will be lost for the next upcomming branch ( because that branch uses HEAD as starting point ) ?!? Regards Ulf --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS-Update fails
When trying to update my local JBoss-Head-CVS-snapshot from within Eclipse on Windows2000 I get the following ( I gues Eclipse) error message The resource 'thirdparty/jython/jython/lib/' could not be created because another resource exists whose path differs only by case The cvs output log until error is: cvs update -C -d -P /jboss-dev-Head/thirdparty/jython cvs server: Updating thirdparty/jython cvs server: Updating thirdparty/jython/jython cvs server: Updating thirdparty/jython/jython/Lib cvs server: Updating thirdparty/jython/jython/Lib/encodings cvs server: Updating thirdparty/jython/jython/Lib/pawt cvs server: Updating thirdparty/jython/jython/Lib/test cvs server: Updating thirdparty/jython/jython/Lib/xml cvs server: Updating thirdparty/jython/jython/Lib/xml/dom cvs server: Updating thirdparty/jython/jython/Lib/xml/dom/ext cvs server: Updating thirdparty/jython/jython/Lib/xml/dom/ext/reader cvs server: Updating thirdparty/jython/jython/Lib/xml/dom/html cvs server: Updating thirdparty/jython/jython/Lib/xml/parsers cvs server: Updating thirdparty/jython/jython/Lib/xml/parsers/xmlproc cvs server: Updating thirdparty/jython/jython/Lib/xml/sax cvs server: Updating thirdparty/jython/jython/Lib/xml/sax/drivers2 cvs server: Updating thirdparty/jython/jython/Lib/xml/utils cvs server: Updating thirdparty/jython/jython/Tools cvs server: Updating thirdparty/jython/jython/Tools/freeze cvs server: Updating thirdparty/jython/jython/Tools/jythonc cvs server: Updating thirdparty/jython/jython/Tools/jythonc/jast cvs server: Updating thirdparty/jython/jython/bin cvs server: Updating thirdparty/jython/jython/jython cvs server: Updating thirdparty/jython/jython/jython/Lib cvs server: Updating thirdparty/jython/jython/jython/Lib/encodings cvs server: Updating thirdparty/jython/jython/jython/Lib/pawt cvs server: Updating thirdparty/jython/jython/jython/Lib/test cvs server: Updating thirdparty/jython/jython/jython/Lib/xml cvs server: Updating thirdparty/jython/jython/jython/Lib/xml/dom cvs server: Updating thirdparty/jython/jython/jython/Lib/xml/dom/ext cvs server: Updating thirdparty/jython/jython/jython/Lib/xml/dom/ext/reader cvs server: Updating thirdparty/jython/jython/jython/Lib/xml/dom/html cvs server: Updating thirdparty/jython/jython/jython/Lib/xml/parsers cvs server: Updating thirdparty/jython/jython/jython/Lib/xml/parsers/xmlproc cvs server: Updating thirdparty/jython/jython/jython/Lib/xml/sax cvs server: Updating thirdparty/jython/jython/jython/Lib/xml/sax/drivers2 cvs server: Updating thirdparty/jython/jython/jython/Lib/xml/utils cvs server: Updating thirdparty/jython/jython/jython/Tools cvs server: Updating thirdparty/jython/jython/jython/Tools/freeze cvs server: Updating thirdparty/jython/jython/jython/Tools/jythonc cvs server: Updating thirdparty/jython/jython/jython/Tools/jythonc/jast cvs server: Updating thirdparty/jython/jython/jython/bin cvs server: Updating thirdparty/jython/jython/jython/l_i_b_ cvs server: Updating thirdparty/jython/jython/jython/lib cvs server: Updating thirdparty/jython/jython/lib U thirdparty/jython/jython/lib/jython.jar failed due to an internal error (took 0:25.997) *** Any ideas how to solve this problem ? Deleting the local jython subdirectory before trying to update didn't work. Regards Ulf
