Re: [JBoss-dev] Does clustering work on OS X?
I'm just running 'all', and am not connecting to anything. -dain On Thursday, April 3, 2003, at 01:12 AM, Stephen Coy wrote: As in just running the all config, or are you actually clustering with something else? Running all certainly works in 3.2 - I've not tried HEAD in a while. In fact, I've run all on a Mac and linux box together without problems using JDK 1.4.1. Steve Coy On Thursday, April 3, 2003, at 04:32 PM, Dain Sundstrom wrote: Does clustering in jboss-head work for anyone on OS X? Whenever I try to shutdown jboss-head on my powerbook the entire os locks up until I unplug my wireless access point and 'killall -9 java'. This can take like 30 minutes to get my laptop responsive again. [12:27:50] dain$ java -version java version 1.4.1_01 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-39) Java HotSpot(TM) Client VM (build 1.4.1_01-14, mixed mode) -dain --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-714240 ] Can't use form-based authentication with clustering
Bugs item #714240, was opened at 2003-04-03 00:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=714240group_id=22866 Category: JBossWeb Group: None Status: Closed Resolution: Duplicate Priority: 5 Submitted By: tim kitchens (tkitchens) Assigned to: Nobody/Anonymous (nobody) Summary: Can't use form-based authentication with clustering Initial Comment: I've tested a clustering with a simple application. When I configure form-based authentication (which works fine for this app without clustering) for this application and try to login, I get an error and cannot log in - you can find the stack trace in the attached text file. Server output from the console: C:\TEMP\jboss-3.0.6-node1\binrun -c all = == . JBoss Bootstrap Environment . JBOSS_HOME: C:\TEMP\jboss-3.0.6-node1\bin\.. . JAVA: C:\tools\jdk1.4.1\bin\java . JAVA_OPTS: -Dprogram.name=run.bat . CLASSPATH: ;C:\tools\jdk1.4.1 \lib\tools.jar;C:\TEMP\jboss-3.0.6-node1\bin\run .jar . = == 17:21:38,181 INFO [Server] JBoss Release: JBoss- 3.0.6 CVSTag=JBoss_3_0_6 It appears that the org.jboss.jetty.security.JBossUserRealm nor any of the classes it references are Serializable. When the server attempts to replicate this object to another node upon authentication, replication fails, since it's not Serializable. This appears to be a bug, since you should be able to use form-based authentication in conjunction with clustering. I have attached the debugger to JBoss and determined that the JBossUserRealm is indeed the problem. OS: Windows 2000, Service Pack 3 JDK: 1.4.1_01 To reproduce: deploy any simple web application that uses form-based authentication and clustering and attempt to login. -- Comment By: Sacha Labourey (slaboure) Date: 2003-04-03 11:03 Message: Logged In: YES user_id=95900 Duplicate of bug 713613 https://sourceforge.net/tracker/? func=detailatid=376685aid=713613group_id=22866 -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=714240group_id=22866 --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] How do I clean up these hsqldb shutdown exceptions?
On 2003.04.03 07:36 [EMAIL PROTECTED] wrote: torsdagen den 3 april 2003 kl 07.32 skrev David Jencks: I'm not sure what your point is, Victor. The exceptions Scott saw were a result of a change I made in the last few days to improve the shutdown behavior of the pools, something I've been somewhat worried about since I wrote them. The fix was to change the mbean dependency between the hslq mbean and the datasource mbeans. My point being a concern for : http://c2.com/cgi/wiki?ComplexityAsDebt I'm well aware of this viewpoint and basically agree with it: another catch-phrase is LOC spent, not LOC written. However, please explain how it is relevant to the refactoring that caused the exceptions to show up. The possible remaining problem is, what happens to connections that are checked out to clients if the db is shut down? For say Oracle, you get a lot of dead connections. For an in-vm java db, it's not clear to me how to make the shutdown wait until all connections are returned. This doesn't have anything to do with hsql AFAIK. One could imagine a reconnect policy negotiated from a service state repository. I can imagine a lot of things, but not how this would provide a reasonable value/complexity tradeoff over the current situation. david jencks --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Does clustering work on OS X?
This has never happened to me, and I have done some (extremely informal) clustering tests by (accidentally) running all on a network with other jboss's running. I still haven't upgraded jdk's however, still on 1.4.1dp10. david jencks On 2003.04.03 02:36 Dain Sundstrom wrote: I'm just running 'all', and am not connecting to anything. -dain On Thursday, April 3, 2003, at 01:12 AM, Stephen Coy wrote: As in just running the all config, or are you actually clustering with something else? Running all certainly works in 3.2 - I've not tried HEAD in a while. In fact, I've run all on a Mac and linux box together without problems using JDK 1.4.1. Steve Coy On Thursday, April 3, 2003, at 04:32 PM, Dain Sundstrom wrote: Does clustering in jboss-head work for anyone on OS X? Whenever I try to shutdown jboss-head on my powerbook the entire os locks up until I unplug my wireless access point and 'killall -9 java'. This can take like 30 minutes to get my laptop responsive again. [12:27:50] dain$ java -version java version 1.4.1_01 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-39) Java HotSpot(TM) Client VM (build 1.4.1_01-14, mixed mode) -dain --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Can't download JBoss
Hi, I've tried since last night (the night of April 2, 2002) to download JBoss 3.0.6. The sourceforge page here: http://prdownloads.sourceforge.net/jboss/jboss-3.0.6.zip?download fails to start the download after I select a proper mirror. Anyone else see this? -- Le __ Post your free ad now! http://personals.yahoo.ca --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Patches-714762 ] Adding Instrumentation Processing Support to JBoss
Patches item #714762, was opened at 2003-04-03 17:18 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376687aid=714762group_id=22866 Category: JBossServer Group: CVS HEAD Status: Open Resolution: None Priority: 5 Submitted By: Rob Dickinson (rob_dickinson) Assigned to: Nobody/Anonymous (nobody) Summary: Adding Instrumentation Processing Support to JBoss Initial Comment: Intercepting application classes at load-time or deploy- time is exceedingly useful for a variety of purposes, chief among them is the flexibility it provides to perform actions dynamically based on specific needs of the JBoss user not anticipated ahead of time by the JBoss source tree. Several application server products (notably BEA WebLogic and MacroMedia JRun) support this concept via a generic facility, and here we propose creating a similar service for JBoss via a few minor changes to the MainDeployer class (org.jboss.deployment.MainDeployer) that we would like to see applied to the main source tree. The attached ZIP file contains a more detailed proposal document as well as file deltas. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376687aid=714762group_id=22866 --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] [ jboss-Patches-714762 ] Adding Instrumentation Processing Support to JBoss
Where is the attached file? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of SourceForge.net Sent: jeudi, 3. avril 2003 19:18 To: [EMAIL PROTECTED] Subject: [JBoss-dev] [ jboss-Patches-714762 ] Adding Instrumentation Processing Support to JBoss Patches item #714762, was opened at 2003-04-03 17:18 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376687aid=7 14762group_id=22866 Category: JBossServer Group: CVS HEAD Status: Open Resolution: None Priority: 5 Submitted By: Rob Dickinson (rob_dickinson) Assigned to: Nobody/Anonymous (nobody) Summary: Adding Instrumentation Processing Support to JBoss Initial Comment: Intercepting application classes at load-time or deploy- time is exceedingly useful for a variety of purposes, chief among them is the flexibility it provides to perform actions dynamically based on specific needs of the JBoss user not anticipated ahead of time by the JBoss source tree. Several application server products (notably BEA WebLogic and MacroMedia JRun) support this concept via a generic facility, and here we propose creating a similar service for JBoss via a few minor changes to the MainDeployer class (org.jboss.deployment.MainDeployer) that we would like to see applied to the main source tree. The attached ZIP file contains a more detailed proposal document as well as file deltas. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376687aid=7 14762group_id=22866 --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Why is JDOM version in JBoss so old
Is there are particular reason JBoss ships with what appears to be the almost 2 year old JDOM b7, instead of the 'current' (about a year old) b8? I've done a search through the mailing lists and couldn't find any reference to this. Upgrading the version in /lib to b8 seems to resolve the MethodNotFoundError my app was getting since it expected b8, without apparently adversely affecting JBoss, but it is still annoying to have to patch JBoss like this. Regards, Colin --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JB4DR1 Deadline MAY 26
Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't be afraid to talk and say who needs help etc. PLgC marcf xx Marc Fleury, Ph.D. President, Founder JBoss Group, LLC xx --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JB4DR1 Deadline MAY 26
I think you are delusional if you think JB4 will be ready for JavaOne. -dain On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote: Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't be afraid to talk and say who needs help etc. PLgC marcf xx Marc Fleury, Ph.D. President, Founder JBoss Group, LLC xx --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Does clustering work on OS X?
Its not working for me on a 2x500 G4. 12:42:37,014 INFO [Server] Starting General Purpose Architecture (GPA)... 12:42:38,034 INFO [ServerInfo] Java version: 1.4.1_01,Apple Computer, Inc. 12:42:38,035 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.1_01-14,Apple Computer, Inc. 12:42:38,036 INFO [ServerInfo] OS-System: Mac OS X 10.2.4,ppc ... 12:43:02,969 INFO [MainDeployer] Package: file:/usr/local/jboss/JBossMain/jboss-head/build/output/jboss-4.0.0alpha/server/all/lib/jboss.jar is already deployed ... looks hung. and a thread dump shows that its stuck trying to exit the vm: DestroyJavaVM prio=5 tid=0x00088ed0 nid=0x48e50 waiting on condition [0..f00802d0] main prio=5 tid=0x0009c720 nid=0x81be0 runnable [f0481000..f0488b70] at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1473) - locked 0x6772a758 (a java.util.Vector) - locked 0x6772a770 (a java.util.Vector) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1389) at java.lang.Runtime.loadLibrary0(Runtime.java:788) - locked 0x67726ba0 (a java.lang.Runtime) at java.lang.System.loadLibrary(System.java:832) at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:50) at java.security.AccessController.doPrivileged(Native Method) at java.awt.Toolkit.loadLibraries(Toolkit.java:1401) at java.awt.Toolkit.clinit(Toolkit.java:1422) at java.awt.Color.clinit(Color.java:250) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:140) at org.jboss.copy.ObjectCopier.class$(ObjectCopier.java:37) at org.jboss.copy.ObjectCopier.init(ObjectCopier.java:37) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:274) at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:909) at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:297) at org.jboss.system.ServiceCreator.install(ServiceCreator.java:173) at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:159) at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:116) at org.jboss.system.ServiceController.install(ServiceController.java:223) - locked 0x67792c90 (a org.jboss.system.ServiceController) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:72) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:45) at org.jboss.mx.server.Invocation.invoke(Invocation.java:70) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:155) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:544) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:172) at $Proxy6.install(Unknown Source) at org.jboss.deployment.SARDeployer.create(SARDeployer.java:189) at org.jboss.deployment.DeploymentInfo.create(DeploymentInfo.java:262) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:72) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:45) at org.jboss.mx.server.Invocation.invoke(Invocation.java:70) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:155) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:544) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:1002) at $Proxy11.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceController.java:301) - locked 0x67792c90 (a org.jboss.system.ServiceController) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at
Re: [JBoss-dev] Does clustering work on OS X?
Hey that is my code Is it not even starting for you? I can remove the ObjectCopier service until I figure out why it is hanging? I don't see why this would effect shutdown. Does this happen when you run the default configuration. Is it a problem to reference awt classes like Color from the server? I can remove all awt references from these classes. I was just trying to support copying of all data objects included in the JDK. -dain On Thursday, April 3, 2003, at 02:58 PM, Scott M Stark wrote: Its not working for me on a 2x500 G4. 12:42:37,014 INFO [Server] Starting General Purpose Architecture (GPA)... 12:42:38,034 INFO [ServerInfo] Java version: 1.4.1_01,Apple Computer, Inc. 12:42:38,035 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.1_01-14,Apple Computer, Inc. 12:42:38,036 INFO [ServerInfo] OS-System: Mac OS X 10.2.4,ppc ... 12:43:02,969 INFO [MainDeployer] Package: file:/usr/local/jboss/JBossMain/jboss-head/build/output/jboss- 4.0.0alpha/server/all/lib/jboss.jar is already deployed ... looks hung. and a thread dump shows that its stuck trying to exit the vm: DestroyJavaVM prio=5 tid=0x00088ed0 nid=0x48e50 waiting on condition [0..f00802d0] main prio=5 tid=0x0009c720 nid=0x81be0 runnable [f0481000..f0488b70] at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1473) - locked 0x6772a758 (a java.util.Vector) - locked 0x6772a770 (a java.util.Vector) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1389) at java.lang.Runtime.loadLibrary0(Runtime.java:788) - locked 0x67726ba0 (a java.lang.Runtime) at java.lang.System.loadLibrary(System.java:832) at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:50) at java.security.AccessController.doPrivileged(Native Method) at java.awt.Toolkit.loadLibraries(Toolkit.java:1401) at java.awt.Toolkit.clinit(Toolkit.java:1422) at java.awt.Color.clinit(Color.java:250) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:140) at org.jboss.copy.ObjectCopier.class$(ObjectCopier.java:37) at org.jboss.copy.ObjectCopier.init(ObjectCopier.java:37) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructor AccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingCon structorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:274) at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:90 9) at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:29 7) at org.jboss.system.ServiceCreator.install(ServiceCreator.java:173) at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurato r.java:159) at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:1 16) at org.jboss.system.ServiceController.install(ServiceController.java:223) - locked 0x67792c90 (a org.jboss.system.ServiceController) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja va:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso rImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.ja va:72) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:45) at org.jboss.mx.server.Invocation.invoke(Invocation.java:70) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.ja va:155) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:544) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:172) at $Proxy6.install(Unknown Source) at org.jboss.deployment.SARDeployer.create(SARDeployer.java:189) at org.jboss.deployment.DeploymentInfo.create(DeploymentInfo.java:262) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja va:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso rImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.ja va:72) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:45) at org.jboss.mx.server.Invocation.invoke(Invocation.java:70) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.ja va:155) at
Re: [JBoss-dev] Does clustering work on OS X?
I've seen the hang sometimes on UFS filesystems, but why the heck is java.awt.Color being loaded in the first place!? On Thursday, Apr 3, 2003, at 12:58 US/Pacific, Scott M Stark wrote: Its not working for me on a 2x500 G4. 12:42:37,014 INFO [Server] Starting General Purpose Architecture (GPA)... 12:42:38,034 INFO [ServerInfo] Java version: 1.4.1_01,Apple Computer, Inc. 12:42:38,035 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.1_01-14,Apple Computer, Inc. 12:42:38,036 INFO [ServerInfo] OS-System: Mac OS X 10.2.4,ppc ... 12:43:02,969 INFO [MainDeployer] Package: file:/usr/local/jboss/JBossMain/jboss-head/build/output/jboss- 4.0.0alpha/server/all/lib/jboss.jar is already deployed ... looks hung. and a thread dump shows that its stuck trying to exit the vm: DestroyJavaVM prio=5 tid=0x00088ed0 nid=0x48e50 waiting on condition [0..f00802d0] main prio=5 tid=0x0009c720 nid=0x81be0 runnable [f0481000..f0488b70] at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1473) - locked 0x6772a758 (a java.util.Vector) - locked 0x6772a770 (a java.util.Vector) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1389) at java.lang.Runtime.loadLibrary0(Runtime.java:788) - locked 0x67726ba0 (a java.lang.Runtime) at java.lang.System.loadLibrary(System.java:832) at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:50) at java.security.AccessController.doPrivileged(Native Method) at java.awt.Toolkit.loadLibraries(Toolkit.java:1401) at java.awt.Toolkit.clinit(Toolkit.java:1422) at java.awt.Color.clinit(Color.java:250) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:140) at org.jboss.copy.ObjectCopier.class$(ObjectCopier.java:37) at org.jboss.copy.ObjectCopier.init(ObjectCopier.java:37) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructor AccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingCon structorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:274) at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:90 9) at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:29 7) at org.jboss.system.ServiceCreator.install(ServiceCreator.java:173) at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurato r.java:159) at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:1 16) at org.jboss.system.ServiceController.install(ServiceController.java:223) - locked 0x67792c90 (a org.jboss.system.ServiceController) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja va:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso rImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.ja va:72) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:45) at org.jboss.mx.server.Invocation.invoke(Invocation.java:70) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.ja va:155) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:544) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:172) at $Proxy6.install(Unknown Source) at org.jboss.deployment.SARDeployer.create(SARDeployer.java:189) at org.jboss.deployment.DeploymentInfo.create(DeploymentInfo.java:262) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja va:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso rImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.ja va:72) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:45) at org.jboss.mx.server.Invocation.invoke(Invocation.java:70) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.ja va:155) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:544) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControlle r.java:1002) at $Proxy11.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceController.java:301) - locked 0x67792c90 (a org.jboss.system.ServiceController) at
RE: [JBoss-dev] JB4DR1 Deadline MAY 26
There's already a lot we can release. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you are delusional if you think JB4 will be ready for JavaOne. -dain On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote: Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't be afraid to talk and say who needs help etc. PLgC marcf xx Marc Fleury, Ph.D. President, Founder JBoss Group, LLC xx --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JB4DR1 Deadline MAY 26
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you are delusional if you think JB4 will be ready for JavaOne. Do you mean JB4 AOP persistence? Acid, security, transactions, cache (!) are all almost ready. Are you saying the new AOP persistence is far from done? What about the old CMP2.0 engine? marcf --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-706494 ] InitialContext missing jndi.properties entries
Bugs item #706494, was opened at 2003-03-19 12:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=706494group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Closed Resolution: Works For Me Priority: 5 Submitted By: Dan Ciarniello (dciarnie) Assigned to: Scott M Stark (starksm) Summary: InitialContext missing jndi.properties entries Initial Comment: OS: Win2K JDK: 1.3.1 The only entries in conf/jndi.properties that are loaded into an InitialContext are javax.naming.factory.initial, java.naming.provider.url and java.naming.factory.url.pkgs. Any other entries are ignored. To test: 1. Add some extra entries to jndi.properties. 2. In an entity bean or a message bean, create an InitialContext and print out its environment. The only entries that are printed out are the ones named above; the extras are not. Note: Using the jmx console to list the system properties shows that all entries in the jndi.properties are loaded into the system property space; they are simply not loaded into the InitialContext. -- Comment By: Scott M Stark (starksm) Date: 2003-04-03 13:52 Message: Logged In: YES user_id=175228 This example works fine for me with the current 3.0 branch: 13:35:43,803 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.3.1_06-b01,Sun Microsystems In c. 13:35:43,803 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 ... 13:35:55,670 INFO [Server] JBoss (MX MicroKernel) [3.0.7RC1 (CVSTag=Branch_3_0 Date=200303180733)] Started in 0m:12s:167ms 13:36:26,735 INFO [STDOUT] 13:36:26,735 INFO [STDOUT] java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory 13:36:26,735 INFO [STDOUT] key2 : b 13:36:26,735 INFO [STDOUT] key1 : a 13:36:26,735 INFO [STDOUT] java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces:org.j boss.naming:org.jnp.interfaces 13:36:26,735 INFO [STDOUT] -- Comment By: Dan Ciarniello (dciarnie) Date: 2003-03-20 15:46 Message: Logged In: YES user_id=529841 Sorry, forgot to check the box for the file upload... -- Comment By: Dan Ciarniello (dciarnie) Date: 2003-03-20 15:45 Message: Logged In: YES user_id=529841 Ok. The attached zip file contains a jar, source code and a sample jndi.properties. 1. Place the jar file in JBOSS_DIR/server/default/deploy 2. Place the jndi.properies in JBOSS_DIR/server/default/conf 3. Start JBoss 4. Run JNDITester.main() The following should appear in the JBoss output: 15:27:06,181 INFO [STDOUT] 15:27:06,181 INFO [STDOUT] java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory 15:27:06,181 INFO [STDOUT] java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces 15:27:06,181 INFO [STDOUT] The two added entries, key1 and key2, are not displayed. Note: I used JBoss-3.0.6 as shipped; nothing else deployed. -- Comment By: Scott M Stark (starksm) Date: 2003-03-19 15:55 Message: Logged In: YES user_id=175228 Alright, so I just threw in two properties and dumped out the InitialContext.env as seen by the ENCServlet unit test case and it sees these properties just fine: 2003-03-19 15:39:58,512 INFO [org.jboss.test.web.servlets.ENCServlet] InitialContext.env: 2003-03-19 15:39:58,512 INFO [org.jboss.test.web.servlets.ENCServlet] Key: myprop.b, value: b 2003-03-19 15:39:58,512 INFO [org.jboss.test.web.servlets.ENCServlet] Key: myprop.a, value: a 2003-03-19 15:39:58,512 INFO [org.jboss.test.web.servlets.ENCServlet] Key: java.naming.factory.initial, value: org.jnp.interfaces.NamingContextFactory 2003-03-19 15:39:58,512 INFO [org.jboss.test.web.servlets.ENCServlet] Key: java .naming.factory.url.pkgs, value: org.jboss.naming:org.jnp.interfaces:org.jboss.naming:org.jnp.interfaces So provide a testcase that demonstrates the problem as it works for me. -- Comment By: Dan Ciarniello (dciarnie) Date: 2003-03-19 14:55 Message: Logged In: YES user_id=529841 But the javadocs also state that all entries in all application resource files (i.e. all files named jndi.properties in the classpath) are also loaded into the Context's environment which is then inherited by other contexts. Does conf/jndi.properties not qualify as an application resource? -- Comment By: Scott M Stark (starksm) Date: 2003-03-19 14:39 Message: Logged In: YES user_id=175228 The only properites loaded into the InitialContext env from a
Re: [JBoss-dev] JB4DR1 Deadline MAY 26
Ok then there are 4 weeks to get the new stuff done? Marc, Bill, sure we could do a release but what difference would it make if the new features are not in it. Is this a release just to show off AOP? What about any of the other new stuff? Just give the users a solid 3.2 and they will be happy. -dain On Thursday, April 3, 2003, at 03:30 PM, Bill Burke wrote: It will be ready and stable. Functionality freeze is May 5th. What functionality doesn't make it by then will be left out of the release. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you are delusional if you think JB4 will be ready for JavaOne. -dain On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote: Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't be afraid to talk and say who needs help etc. PLgC marcf xx Marc Fleury, Ph.D. President, Founder JBoss Group, LLC xx --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
RE: [JBoss-dev] JB4DR1 Deadline MAY 26
It will be ready and stable. Functionality freeze is May 5th. What functionality doesn't make it by then will be left out of the release. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you are delusional if you think JB4 will be ready for JavaOne. -dain On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote: Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't be afraid to talk and say who needs help etc. PLgC marcf xx Marc Fleury, Ph.D. President, Founder JBoss Group, LLC xx --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Does clustering work on OS X?
Those Apple guys are just too big of GUI freaks I guess. This is even over an ssh session so it was not even like I was on the console. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Stefan Reich [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 03, 2003 1:18 PM Subject: Re: [JBoss-dev] Does clustering work on OS X? I've seen the hang sometimes on UFS filesystems, but why the heck is java.awt.Color being loaded in the first place!? --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Oswego util.concurrent jar updated
I updated the Oswego util.concurrent jar in 3.0+ from the rather ancient 1.3.0 version to 1.3.2 as we found some serious concurrency failures in the ConcurrentHashMap and ConcurrentReaderHashMap classes in looking into some JMS load test failures. A bit ironic that the concurrent package was messing up concurrency. Scott Stark Chief Technology Officer JBoss Group, LLC --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Does clustering work on OS X?
I'll comment out the AWT stuff. All the copiers are hard coded right now, but when I add the configuration code, I'll just have the AWT stuff commented out and if someone wants them they can turn them on. I'm still not sure that you are seeing the same problem I am, because the server boots and works fine for me. When I shutdown the entire thing hangs. (again I am not actually clustering, just running the all configuration). -dain On Thursday, April 3, 2003, at 03:49 PM, Scott M Stark wrote: Those Apple guys are just too big of GUI freaks I guess. This is even over an ssh session so it was not even like I was on the console. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Stefan Reich [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 03, 2003 1:18 PM Subject: Re: [JBoss-dev] Does clustering work on OS X? I've seen the hang sometimes on UFS filesystems, but why the heck is java.awt.Color being loaded in the first place!? --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Does clustering work on OS X?
The default config fails in the same way. Deployment appears message up in main as I see the jboss.jar being deployed multiple times. Why are we copying any JDK classes? 14:07:44,356 INFO [SARDeployer] looking for nested deployments in : file:/usr/local/jboss/JBossMain/jboss-head/build/output/jboss-4.0.0alpha/server/default/deploy/object-copier.sar 14:07:44,381 INFO [MainDeployer] Package: file:/usr/local/jboss/JBossMain/jboss-head/build/output/jboss-4.0.0alpha/server/default/lib/jboss.jar is already deployed DestroyJavaVM prio=5 tid=0x00088ed0 nid=0x48e20 waiting on condition [0..f00802d0] main prio=5 tid=0x0009c720 nid=0x81ba0 runnable [f0481000..f0488b70] at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1473) - locked 0x6772a6d8 (a java.util.Vector) - locked 0x6772a6f0 (a java.util.Vector) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1389) at java.lang.Runtime.loadLibrary0(Runtime.java:788) - locked 0x67726b20 (a java.lang.Runtime) at java.lang.System.loadLibrary(System.java:832) at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:50) at java.security.AccessController.doPrivileged(Native Method) at java.awt.Toolkit.loadLibraries(Toolkit.java:1401) at java.awt.Toolkit.clinit(Toolkit.java:1422) at java.awt.Color.clinit(Color.java:250) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:140) at org.jboss.copy.ObjectCopier.class$(ObjectCopier.java:37) at org.jboss.copy.ObjectCopier.init(ObjectCopier.java:37) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:274) at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:909) at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:297) at org.jboss.system.ServiceCreator.install(ServiceCreator.java:173) at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:159) at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:116) at org.jboss.system.ServiceController.install(ServiceController.java:223) - locked 0x67792b00 (a org.jboss.system.ServiceController) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:72) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:45) at org.jboss.mx.server.Invocation.invoke(Invocation.java:70) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:155) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:544) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:172) at $Proxy6.install(Unknown Source) at org.jboss.deployment.SARDeployer.create(SARDeployer.java:189) at org.jboss.deployment.DeploymentInfo.create(DeploymentInfo.java:262) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:72) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:45) at org.jboss.mx.server.Invocation.invoke(Invocation.java:70) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:155) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:544) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:1002) at $Proxy11.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceController.java:301) - locked 0x67792b00 (a org.jboss.system.ServiceController) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:72) at
RE: [JBoss-dev] JB4DR1 Deadline MAY 26
JBoss Remoting AOP + tx, security, versioning, remoting, clustering, txlock, caching DTM (waiting on David's response) EMB (Enterprise Media Beans) JUDDI integration If I can get it done: AOP + EJB (packaged extensions to EJB) and don't forget Nukes! Anybody got anything to add to this list? Who doesn't think they'll be done by May 5th? Who thinks they'll be cutting it close? Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:48 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 Ok then there are 4 weeks to get the new stuff done? Marc, Bill, sure we could do a release but what difference would it make if the new features are not in it. Is this a release just to show off AOP? What about any of the other new stuff? Just give the users a solid 3.2 and they will be happy. -dain On Thursday, April 3, 2003, at 03:30 PM, Bill Burke wrote: It will be ready and stable. Functionality freeze is May 5th. What functionality doesn't make it by then will be left out of the release. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you are delusional if you think JB4 will be ready for JavaOne. -dain On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote: Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't be afraid to talk and say who needs help etc. PLgC marcf xx Marc Fleury, Ph.D. President, Founder JBoss Group, LLC xx --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing
RE: [JBoss-dev] JB4DR1 Deadline MAY 26
What J2EE specification version are you planning to support in JBoss 4.0? J2EE 1.4 is not final as far as I know... -Original Message- From: marc fleury [mailto:[EMAIL PROTECTED] Sent: Thursday, April 03, 2003 3:47 PM To: [EMAIL PROTECTED] Sourceforge. Net Subject: [JBoss-dev] JB4DR1 Deadline MAY 26 Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't be afraid to talk and say who needs help etc. PLgC marcf --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Does clustering work on OS X?
Please remember that using AWT/Swing classes will load a whole bunch of native libraries on most platforms, which increases the memory footprint. It might also not work on headless machines or on regular machines when nobody is logged in, depending on the OS. On Thursday, Apr 3, 2003, at 14:07 US/Pacific, Dain Sundstrom wrote: I'll comment out the AWT stuff. All the copiers are hard coded right now, but when I add the configuration code, I'll just have the AWT stuff commented out and if someone wants them they can turn them on. I'm still not sure that you are seeing the same problem I am, because the server boots and works fine for me. When I shutdown the entire thing hangs. (again I am not actually clustering, just running the all configuration). -dain On Thursday, April 3, 2003, at 03:49 PM, Scott M Stark wrote: Those Apple guys are just too big of GUI freaks I guess. This is even over an ssh session so it was not even like I was on the console. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Stefan Reich [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 03, 2003 1:18 PM Subject: Re: [JBoss-dev] Does clustering work on OS X? I've seen the hang sometimes on UFS filesystems, but why the heck is java.awt.Color being loaded in the first place!? --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[2]: [JBoss-dev] JB4DR1 Deadline MAY 26
BB JBoss Remoting BB AOP + tx, security, versioning, remoting, clustering, txlock, caching BB DTM (waiting on David's response) BB EMB (Enterprise Media Beans) BB JUDDI integration BB If I can get it done: AOP + EJB (packaged extensions to EJB) BB and don't forget Nukes! I would be pleased to participate BB Anybody got anything to add to this list? BB Who doesn't think they'll be done by May 5th? BB Who thinks they'll be cutting it close? BB Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:48 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 Ok then there are 4 weeks to get the new stuff done? Marc, Bill, sure we could do a release but what difference would it make if the new features are not in it. Is this a release just to show off AOP? What about any of the other new stuff? Just give the users a solid 3.2 and they will be happy. -dain On Thursday, April 3, 2003, at 03:30 PM, Bill Burke wrote: It will be ready and stable. Functionality freeze is May 5th. What functionality doesn't make it by then will be left out of the release. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you are delusional if you think JB4 will be ready for JavaOne. -dain On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote: Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't be afraid to talk and say who needs help etc. PLgC marcf xx Marc Fleury, Ph.D. President, Founder JBoss Group, LLC xx --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
[JBoss-dev] [ jboss-Bugs-714934 ] Incomplete Deployment with RC4
Bugs item #714934, was opened at 2003-04-03 22:48
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=714934group_id=22866
Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Dorothy Gantenbein (dgantenbein)
Assigned to: Nobody/Anonymous (nobody)
Summary: Incomplete Deployment with RC4
Initial Comment:
OS: Windows XP Home
JDK: 1.4.1_02
Started after upgrading from 3.2.0 RC1 to 3.2.0 RC4.
Deploy my ear and get the following incomplete
deployment exception (server.log) is attached. Oddly,
this only seems to happen on WinXP. Works on Win2k
and RedHat.
[java] 13:49:49,171 ERROR
[URLDeploymentScanner] MBeanException: Exception
in MBean operation 'checkIncompleteDeployments()'
[java] Cause: Incomplete Deployment listing:
[java] Packages waiting for a deployer:
[java]
[EMAIL PROTECTED] {
url=file:/D:/orca/3r
dparty/jboss/server/developer/deploy/admin.ear/admin-
client.jar }
[java] deployer: null
[java] status: Starting
[java] state: START_SUBDEPLOYMENTS
[java] watch:
file:/D:/orca/3rdparty/jboss/server/developer/deploy/admi
n.
ear/admin-client.jar
[java] lastDeployed: 1049406559799
[java] lastModified: 1049406559779
[java] mbeans:
[java] ]Incompletely deployed packages:
[java] none
[java] MBeans waiting for classes:
[java] none
[java] MBeans waiting for other MBeans:
[java] none
[java] 13:49:49,181 INFO [URLDeploymentScanner]
Started
[java] 13:49:49,351 INFO [MainDeployer] Deployed
package: file:/D:/orca/3r
dparty/jboss/server/developer/conf/jboss-service.xml
[java] 13:49:49,361 INFO [Server] JBoss (MX
MicroKernel) [3.2.0RC4 (build:
CVSTag=JBoss_3_2_0_RC4 date=200303221440)]
Started in 55s:910ms
My ear has the following structure. The ear is expanded
into a directory in JBoss' deploy directory.
admin.ear
|_META-INF
| |_ application.xml
| |_ MANIFEST.MF
|_admin.war (expanded directory)
|_admin.jar (expanded directory for EJBs)
|_asset.sar (archive for service)
|_infra.sar (archive for service)
|_admin-client.jar (archive that is EJB client)
|_cactus.jar and other archives
The application.xml has the following contents...
?xml version=1.0 ?
!DOCTYPE application PUBLIC
-//Sun Microsystems, Inc.//DTD J2EE Application
1.3//EN
http://java.sun.com/dtd/application_1_3.dtd;
application
display-nameAdmin/display-name
module
web
web-uriadmin.war/web-uri
context-root/cfs/context-root
/web
/module
module
ejbadmin.jar/ejb
/module
module
javainfra.sar/java
/module
module
javaasset.sar/java
/module
/application
As another point of information, I get a different
deployment error when I deploy admin.ear as an archive
(versus expanded directory). Then, the deployer cannot
find admin.war.
[java] 14:25:25,663 ERROR
[URLDeploymentScanner] Failed to deploy: org.jbos
s.deployment.scanner.URLDeploymentScanner$Deploye
[EMAIL PROTECTED] url=file:/D:/orc
a/3rdparty/jboss/server/developer/deploy/admin.ear,
deployedLastModified=0 }
[java] org.jboss.deployment.DeploymentException:
exception in init of file:
/D:/orca/3rdparty/jboss/server/developer/deploy/admin.ea
r; - nested throwable: (
org.jboss.deployment.DeploymentException: Failed to
find module file: admin.war)
[java] at org.jboss.deployment.MainDeployer.init
(MainDeployer.java:720)
[java] at
org.jboss.deployment.MainDeployer.deploy
(MainDeployer.java:63
7)
[java] at
org.jboss.deployment.MainDeployer.deploy
(MainDeployer.java:61
3)
[java] at
sun.reflect.GeneratedMethodAccessor23.invoke
(Unknown Source)
[java] at
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMet
hodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke
(Method.java:324)
[java] at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invok
e(Refle
ctedMBeanDispatcher.java:284)
[java] at
org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.ja
va:549)
[java] at org.jboss.mx.util.MBeanProxyExt.invoke
(MBeanProxyExt.java:177
)
[java] at $Proxy7.deploy(Unknown Source)
[java] at
org.jboss.deployment.scanner.URLDeploymentScanner.
deploy(URLD
eploymentScanner.java:404)
[java] at
org.jboss.deployment.scanner.URLDeploymentScanner.
scan(URLDep
loymentScanner.java:545)
[java] at
org.jboss.deployment.scanner.AbstractDeploymentScan
ner$Scanne
rThread.doScan(AbstractDeploymentScanner.java:195)
[java] at
org.jboss.deployment.scanner.AbstractDeploymentScan
ner.startS
ervice(AbstractDeploymentScanner.java:268)
[java] at
org.jboss.system.ServiceMBeanSupport.start
(ServiceMBeanSuppor
t.java:192)
[java] at
sun.reflect.GeneratedMethodAccessor7.invoke
(Unknown Source)
[java] at
RE: [JBoss-dev] JB4DR1 Deadline MAY 26
1.3 Some 1.4 stuff will probably sneek in though. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Igor Fedorenko Sent: Thursday, April 03, 2003 5:31 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 What J2EE specification version are you planning to support in JBoss 4.0? J2EE 1.4 is not final as far as I know... -Original Message- From: marc fleury [mailto:[EMAIL PROTECTED] Sent: Thursday, April 03, 2003 3:47 PM To: [EMAIL PROTECTED] Sourceforge. Net Subject: [JBoss-dev] JB4DR1 Deadline MAY 26 Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't be afraid to talk and say who needs help etc. PLgC marcf --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Does clustering work on OS X?
It is supposed to work fine on JDK 1.4 which is required for JB4. Anyway, I have commented out support for copying them. -dain On Thursday, April 3, 2003, at 04:28 PM, Stefan Reich wrote: Please remember that using AWT/Swing classes will load a whole bunch of native libraries on most platforms, which increases the memory footprint. It might also not work on headless machines or on regular machines when nobody is logged in, depending on the OS. On Thursday, Apr 3, 2003, at 14:07 US/Pacific, Dain Sundstrom wrote: I'll comment out the AWT stuff. All the copiers are hard coded right now, but when I add the configuration code, I'll just have the AWT stuff commented out and if someone wants them they can turn them on. I'm still not sure that you are seeing the same problem I am, because the server boots and works fine for me. When I shutdown the entire thing hangs. (again I am not actually clustering, just running the all configuration). -dain On Thursday, April 3, 2003, at 03:49 PM, Scott M Stark wrote: Those Apple guys are just too big of GUI freaks I guess. This is even over an ssh session so it was not even like I was on the console. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Stefan Reich [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 03, 2003 1:18 PM Subject: Re: [JBoss-dev] Does clustering work on OS X? I've seen the hang sometimes on UFS filesystems, but why the heck is java.awt.Color being loaded in the first place!? --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Oswego util.concurrent jar updated
Can you elaborate on the bugs found in the old package ? Thanks, Yonatan. -Original Message- From: Scott M Stark [mailto:[EMAIL PROTECTED] Sent: Thursday, April 03, 2003 5:02 PM To: [EMAIL PROTECTED] Subject: [JBoss-dev] Oswego util.concurrent jar updated I updated the Oswego util.concurrent jar in 3.0+ from the rather ancient 1.3.0 version to 1.3.2 as we found some serious concurrency failures in the ConcurrentHashMap and ConcurrentReaderHashMap classes in looking into some JMS load test failures. A bit ironic that the concurrent package was messing up concurrency. Scott Stark Chief Technology Officer JBoss Group, LLC --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JB4DR1 Deadline MAY 26
I agree that there is some great stuff in there already. However, being that the AOP transaction, security, remoting, etc. was only recently released in its first iteration, and the fact that JBoss remoting doesn't yet support true callbacks (Jeff says it is coming) there is simply no way I can deliver the new JMS implementation BUILT ON TOP of these services by May 5th! And I'm going to be out basically two weeks between now and then with customers as I know others will be as well. Since the whole point of the JMS rewrite is to take advantage of the core JBoss AOP services, I haven't really had that much time to do so since the services have only recently been released. Therefore, I expect that a May 26th release will ONLY INCLUDE THE OLD JMS CODE which is currently in HEAD. It is the only option with a May 5th deadline in my opinion. If everyone is OK with this and we're committed to that date, then I am must immediately shift my attention from the development of the new code build on top of the AOP framework to the old code currently in HEAD to start working on ensuring JMS 1.1 compliance, stability, etc. as well as applying the HTTP IL code currently only in Branch_3_2 to HEAD. Then, after the May 26th release, I'll continue working on the new JMS code which is build on top of the AOP framework. Comments? Thanks, Nathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Thursday, April 03, 2003 3:22 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 There's already a lot we can release. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you are delusional if you think JB4 will be ready for JavaOne. -dain On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote: Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't be afraid to talk and say who needs help etc. PLgC marcf xx Marc Fleury, Ph.D. President, Founder JBoss Group, LLC xx --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED]
Re: [JBoss-dev] JB4DR1 Deadline MAY 26
I don't think we can support J2EE 1.4 for the DR1 release unless someone gets in and makes whatever changes are required to get our metadata classes to support the XML schemas used in J2EE 1.4. Besides meta data are there other big things in J2EE 1.4 that we haven't addressed yet? -dain On Thursday, April 3, 2003, at 04:30 PM, Igor Fedorenko wrote: What J2EE specification version are you planning to support in JBoss 4.0? J2EE 1.4 is not final as far as I know... -Original Message- From: marc fleury [mailto:[EMAIL PROTECTED] Sent: Thursday, April 03, 2003 3:47 PM To: [EMAIL PROTECTED] Sourceforge. Net Subject: [JBoss-dev] JB4DR1 Deadline MAY 26 Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't be afraid to talk and say who needs help etc. PLgC marcf --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Oswego util.concurrent jar updated
Any chance they'll ever update the package name to get rid of the capital EDU... drives me crazy. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott M Stark Sent: Thursday, April 03, 2003 4:02 PM To: [EMAIL PROTECTED] Subject: [JBoss-dev] Oswego util.concurrent jar updated I updated the Oswego util.concurrent jar in 3.0+ from the rather ancient 1.3.0 version to 1.3.2 as we found some serious concurrency failures in the ConcurrentHashMap and ConcurrentReaderHashMap classes in looking into some JMS load test failures. A bit ironic that the concurrent package was messing up concurrency. Scott Stark Chief Technology Officer JBoss Group, LLC --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JB4DR1 Deadline MAY 26
Persistence will not be done. -dain On Thursday, April 3, 2003, at 04:27 PM, Bill Burke wrote: JBoss Remoting AOP + tx, security, versioning, remoting, clustering, txlock, caching DTM (waiting on David's response) EMB (Enterprise Media Beans) JUDDI integration If I can get it done: AOP + EJB (packaged extensions to EJB) and don't forget Nukes! Anybody got anything to add to this list? Who doesn't think they'll be done by May 5th? Who thinks they'll be cutting it close? Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:48 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 Ok then there are 4 weeks to get the new stuff done? Marc, Bill, sure we could do a release but what difference would it make if the new features are not in it. Is this a release just to show off AOP? What about any of the other new stuff? Just give the users a solid 3.2 and they will be happy. -dain On Thursday, April 3, 2003, at 03:30 PM, Bill Burke wrote: It will be ready and stable. Functionality freeze is May 5th. What functionality doesn't make it by then will be left out of the release. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you are delusional if you think JB4 will be ready for JavaOne. -dain On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote: Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't be afraid to talk and say who needs help etc. PLgC marcf xx Marc Fleury, Ph.D. President, Founder JBoss Group, LLC xx --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JB4DR1 Deadline MAY 26
1.3 with ongoing development for 1.4 marcf -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Igor Fedorenko Sent: Thursday, April 03, 2003 5:31 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 What J2EE specification version are you planning to support in JBoss 4.0? J2EE 1.4 is not final as far as I know... -Original Message- From: marc fleury [mailto:[EMAIL PROTECTED] Sent: Thursday, April 03, 2003 3:47 PM To: [EMAIL PROTECTED] Sourceforge. Net Subject: [JBoss-dev] JB4DR1 Deadline MAY 26 Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't be afraid to talk and say who needs help etc. PLgC marcf --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020 aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JB4DR1 Deadline MAY 26
I'm ok with JMS. I didn't think you could rewrite in such short of time. Especially with Remoting and AOP just now becoming stable. I think this email thread is good because it will allow us to determine whether or not we can release. I still think there is enough functionality. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nathan Phelps Sent: Thursday, April 03, 2003 5:48 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 I agree that there is some great stuff in there already. However, being that the AOP transaction, security, remoting, etc. was only recently released in its first iteration, and the fact that JBoss remoting doesn't yet support true callbacks (Jeff says it is coming) there is simply no way I can deliver the new JMS implementation BUILT ON TOP of these services by May 5th! And I'm going to be out basically two weeks between now and then with customers as I know others will be as well. Since the whole point of the JMS rewrite is to take advantage of the core JBoss AOP services, I haven't really had that much time to do so since the services have only recently been released. Therefore, I expect that a May 26th release will ONLY INCLUDE THE OLD JMS CODE which is currently in HEAD. It is the only option with a May 5th deadline in my opinion. If everyone is OK with this and we're committed to that date, then I am must immediately shift my attention from the development of the new code build on top of the AOP framework to the old code currently in HEAD to start working on ensuring JMS 1.1 compliance, stability, etc. as well as applying the HTTP IL code currently only in Branch_3_2 to HEAD. Then, after the May 26th release, I'll continue working on the new JMS code which is build on top of the AOP framework. Comments? Thanks, Nathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Thursday, April 03, 2003 3:22 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 There's already a lot we can release. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you are delusional if you think JB4 will be ready for JavaOne. -dain On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote: Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are involved in core modules that need to move fast in the coming weeks. Don't
RE: [JBoss-dev] Oswego util.concurrent jar updated
LOL -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Scott M Stark Sent: Thursday, April 03, 2003 5:02 PM To: [EMAIL PROTECTED] Subject: [JBoss-dev] Oswego util.concurrent jar updated I updated the Oswego util.concurrent jar in 3.0+ from the rather ancient 1.3.0 version to 1.3.2 as we found some serious concurrency failures in the ConcurrentHashMap and ConcurrentReaderHashMap classes in looking into some JMS load test failures. A bit ironic that the concurrent package was messing up concurrency. Scott Stark Chief Technology Officer JBoss Group, LLC --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JB4DR1 Deadline MAY 26
Bill Burke wrote: I'm ok with JMS. I didn't think you could rewrite in such short of time. Especially with Remoting and AOP just now becoming stable. I think this email thread is good because it will allow us to determine whether or not we can release. I still think there is enough functionality. With respect to the cache. I have 3 major tasks that need to be done before it is ready: 1. [Bela] Implement pessimistic and optimistic locking (transactability) on a cluster of caches. I should be done by mid April with this 2. [Bill, Bela] (Stupid) integration into an Interceptor (AOP). Here we need to flesh out some of the difficulties we encountered talking on the phone today, e.g. instrumenting collections, primitive types, recursive instrumentation of an object graph etc. 3. [Jeremy, Dain] Integration of the cache into the PersistenceManager. The first version will have the PersistenceManager use the Cache as a replicated in-memory cache. Our use case will initially be shared DB, so all nodes use the same database. At a later stage (probably not JB4) we will provide unshared DBs. This involves some more efforts, e.g. retrieving full DB state for new nodes (from existing nodes). Tasks #1, #2 and #3 can be done in parallel. Although #1 is not yet done, the API will remain the same, so the Cache can already be used (without transactability though). #2 requires some effort by Bill, and Bela (if locking is done before mid-April). Task #3 will be done by Jeremy and Dain. I don't know what issues we will encounter there. Jeremy/Dain, can you comment on this ? -- Bela Ban --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Oswego util.concurrent jar updated
It does not work: ConcurrentHashMap map = ...; Object x = ...; map.put(x, x); Object y = map.remove(x); assert( y != null ) fails sporadically Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Yonatan Lee [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 03, 2003 2:48 PM Subject: RE: [JBoss-dev] Oswego util.concurrent jar updated Can you elaborate on the bugs found in the old package ? Thanks, Yonatan. -Original Message- From: Scott M Stark [mailto:[EMAIL PROTECTED] Sent: Thursday, April 03, 2003 5:02 PM To: [EMAIL PROTECTED] Subject: [JBoss-dev] Oswego util.concurrent jar updated I updated the Oswego util.concurrent jar in 3.0+ from the rather ancient 1.3.0 version to 1.3.2 as we found some serious concurrency failures in the ConcurrentHashMap and ConcurrentReaderHashMap classes in looking into some JMS load test failures. A bit ironic that the concurrent package was messing up concurrency. Scott Stark Chief Technology Officer JBoss Group, LLC --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JB4DR1 Deadline MAY 26
DR1 is a showcase for the geralized services architecture. Its not a showcase for J2EE 1.4 views of these services as this will be built on top of the core. Having the HTTP IL in these release is irrelevant. I'm not porting the RMI/HTTP invokers until the remoting, pooling, proxy+interceptor factories, etc are in place. There is no reason to panic, go back to working on the grand vision of generalized services intersecting with POJOs to give your version of an enterprise application server as per your specification. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Nathan Phelps [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 03, 2003 2:48 PM Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 I agree that there is some great stuff in there already. However, being that the AOP transaction, security, remoting, etc. was only recently released in its first iteration, and the fact that JBoss remoting doesn't yet support true callbacks (Jeff says it is coming) there is simply no way I can deliver the new JMS implementation BUILT ON TOP of these services by May 5th! And I'm going to be out basically two weeks between now and then with customers as I know others will be as well. Since the whole point of the JMS rewrite is to take advantage of the core JBoss AOP services, I haven't really had that much time to do so since the services have only recently been released. Therefore, I expect that a May 26th release will ONLY INCLUDE THE OLD JMS CODE which is currently in HEAD. It is the only option with a May 5th deadline in my opinion. If everyone is OK with this and we're committed to that date, then I am must immediately shift my attention from the development of the new code build on top of the AOP framework to the old code currently in HEAD to start working on ensuring JMS 1.1 compliance, stability, etc. as well as applying the HTTP IL code currently only in Branch_3_2 to HEAD. Then, after the May 26th release, I'll continue working on the new JMS code which is build on top of the AOP framework. Comments? Thanks, Nathan --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JB4DR1 Deadline MAY 26
On Thursday, April 3, 2003, at 05:26 PM, Bela Ban wrote: 3. [Jeremy, Dain] Integration of the cache into the PersistenceManager. The first version will have the PersistenceManager use the Cache as a replicated in-memory cache. Our use case will initially be shared DB, so all nodes use the Our need for caching is very different from what the other two, so I don't think that it can be done in parallel as it requires some very things in the implementation. I'm still not convinced that we don't need a completely different cache from what the rest of the server will use. Of course we will use the same low level APIs, but I think the rest will need to be custom. I know you and Jeremy have been working these issues out, so I'll have to wait and see what happens. same database. At a later stage (probably not JB4) we will provide unshared DBs. This involves some more efforts, e.g. retrieving full DB state for new nodes (from existing nodes). I think this is a third system that will be very different from the other two. I am concerned that if we try to support all of these different requirements we will end up difficult to use and maintain code, but you are a coding Jedi. Anyway, my point is I don't think they can be done in parallel. -dain --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JB4DR1 Deadline MAY 26
--- Dain Sundstrom [EMAIL PROTECTED] wrote: Our need for caching is very different from what the other two, so I don't think that it can be done in parallel as it requires some very things in the implementation. I'm still not convinced that we don't need a completely different cache from what the rest of the server will use. I have discussed the requirements for the cache from the CMP's perspective (PersistenceManager) with Jeremy twice (and we'll meet this Monday again). I think we came up with a workable solution, the first cache iteration was unusable (hashmap based). The new tree-structured cache should suit your requirements much better. For stuff like delete all order items form customer with id=34425, we need some custom functionality, agreed. But I think I have a solution for this, and Jeremy and I will discuss it Monday. Other than that, I *hope* that the current API more or less satisfies your requirements. I think this is a third system that will be very different from the other two. Maybe, but I do hope the cache can be used by both. I am concerned that if we try to support all of these different requirements we will end up difficult to use and maintain code, but you are a coding Jedi. Anyway, my point is I don't think they can be done in parallel. Why not ? If the cache satisfies both requirements I don't see why we could not proceed in parallel. Bela __ Do you Yahoo!? Yahoo! Tax Center - File online, calculators, forms, and more http://tax.yahoo.com --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-676799 ] Missing public ID for jboss-app.dtd in XmlFileLoader
Bugs item #676799, was opened at 2003-01-29 06:31
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=676799group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Stefan Kuehnel (skuehnel)
Assigned to: Scott M Stark (starksm)
Summary: Missing public ID for jboss-app.dtd in XmlFileLoader
Initial Comment:
When adding a DOCTYPE as specified in
${jboss.home}/docs/dtds/jboss-app_3.0.dtd to
jboss-app.xml, the loading of the corresponding EAR
fails. This is because the public id -//JBoss//DTD
J2EE Application 1.3//EN is not listed in
org.jboss.metadata.XmlFileLoader.LocalResolver. A line like
registerDTD(-//JBoss//DTD J2EE Application 1.3//EN,
jboss-app_3_0.dtd);
is needed in the constructor for LocalResolver.
--
Comment By: Scott M Stark (starksm)
Date: 2003-04-03 17:35
Message:
Logged In: YES
user_id=175228
Fixed for 3.0.7
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=676799group_id=22866
---
This SF.net email is sponsored by: ValueWeb:
Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Compound PK using CMR/CMP
Hi, I have created an Entity EJB that maps to a table with a compound PK (both columns are NOT NULL). One of the columns of the PK is a FK to another table representing the many side of a 1-* relationship. Using XDoclet, I can generate what appears to be the proper source and deployment descriptors...all of which deploy to JBoss-4alpha with no problem. The problem comes in when I try to create an instance of the EJB from a client app. A SQLException is thrown, indicating you can not insert NULL into the column. The thread: http://www.mail-archive.com/[EMAIL PROTECTED]/msg03782.html led me to believe this was fixed in 4-alpha. Does anyone have it working yet? Any advice...its driving me crazy. Thanks, -Billy --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JB4DR1 Deadline MAY 26
Jboss Remoting callbacks are in - I wil commit in the next day or so when tom and I finish testing. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Thursday, April 03, 2003 6:06 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 I'm ok with JMS. I didn't think you could rewrite in such short of time. Especially with Remoting and AOP just now becoming stable. I think this email thread is good because it will allow us to determine whether or not we can release. I still think there is enough functionality. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nathan Phelps Sent: Thursday, April 03, 2003 5:48 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 I agree that there is some great stuff in there already. However, being that the AOP transaction, security, remoting, etc. was only recently released in its first iteration, and the fact that JBoss remoting doesn't yet support true callbacks (Jeff says it is coming) there is simply no way I can deliver the new JMS implementation BUILT ON TOP of these services by May 5th! And I'm going to be out basically two weeks between now and then with customers as I know others will be as well. Since the whole point of the JMS rewrite is to take advantage of the core JBoss AOP services, I haven't really had that much time to do so since the services have only recently been released. Therefore, I expect that a May 26th release will ONLY INCLUDE THE OLD JMS CODE which is currently in HEAD. It is the only option with a May 5th deadline in my opinion. If everyone is OK with this and we're committed to that date, then I am must immediately shift my attention from the development of the new code build on top of the AOP framework to the old code currently in HEAD to start working on ensuring JMS 1.1 compliance, stability, etc. as well as applying the HTTP IL code currently only in Branch_3_2 to HEAD. Then, after the May 26th release, I'll continue working on the new JMS code which is build on top of the AOP framework. Comments? Thanks, Nathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Thursday, April 03, 2003 3:22 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 There's already a lot we can release. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you are delusional if you think JB4 will be ready for JavaOne. -dain On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote: Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th
[JBoss-dev] Automated JBoss(Branch_3_0) Testsuite Results: 3-April-2003
Automated JBoss(Branch_3_0) Testsuite Results: 3-April-2003\n\n
begin 644 TESTS-TestSuites.txt
M#0H-DI;W-S(1A:6QY('1EW0@F5S=6QTPT*#0I354U-05)9#0H-DYU
M;6)EB!O9B!T97-TR!R=6XZ( @,3 Y. T*#0HM+2TM+2TM+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+0T*#0I3=6-C97-S9G5L('1E
MW1S.B @( @(#$P.3,-@T*17)R;W)S.B @( @( @( @( @( Q#0H-
MD9A:6QUF5S.B @( @( @( @( @- T*#0HM+2TM+2TM+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+0T*#0H-@T*6W1I;64@;V8@
M=5S=#H@,C P,RTP-TP,RXQ.2TT,2!'351=#0I;:F%V82YV97)S:6]N.B Q
M+C0N,5\P,ET-EMJ879A+G9E;F1O[EMAIL PROTECTED]($UI8W)OWES=5MR!);F,N
M70T*6VIA=F$N=FTN=F5RVEO;CH@,2XT+C%?,#(M8C V70T*6VIA=F$N=FTN
M;[EMAIL PROTECTED](;W13]T*%1-*2!#;EE;[EMAIL PROTECTED];:F%V82YV;2YI
M;F9O.B!M:7AE9!M;V1E70T*6V]S+FYA;64Z(%=I;F1O=W,@,C P,%T-EMO
MRYAF-H.B!X.#9=#0I;;W,N=F5RVEO;[EMAIL PROTECTED]@:'1T#HO
M+W5S97)S+FIB;W-S+F]R9R]^W1AFMS;2]F%N8VA?,U\P+S(P,#,M,#0M
M,#,N,3DM-#$-F9OB!D971A:6QS(]F('1H:7,@=5S=[EMAIL PROTECTED]DY/5$4Z
M($EF('1H97)E(%R92!A;[EMAIL PROTECTED])R;W)S('-H;W=N(%B;W9E([EMAIL PROTECTED]AIR!M
M86EL(ES(]N;'D@:EG:QI9VAT:6YG( T*=AE;2 M(ET(ES($Y/5!I
M;F1I8V%T:6YG('[EMAIL PROTECTED]AE2!A[EMAIL PROTECTED];F@;]O:V5D(%T()Y(%N
M6]N92X-@T*270@:7,@87-S=6UE9!T:%T('=H;V5V97(@;6%K97,@8VAA
M;F=E*',I('1O(IB;W-S('[EMAIL PROTECTED]F5A:R!T:[EMAIL PROTECTED]5S=!W:6QL()E
M(9IEN9R!T:[EMAIL PROTECTED]5S=!OB!J8F]S[EMAIL PROTECTED],@87!PF]PFEA=4A#0H-
MBTM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM
M#0H-@T*#0I$151!24Q3($]($524D]24PT*#0H-@T*4W5I=4Z( @( @
M($)E86Y3=')EW-497-T0V%S90T*55S=#H@( @( @('1EW1$96%D3]C
M:T9R;VU#;EE;G0H;W)G+FIB;W-S+G1EW0N95A9QO8VLN=5S=Y96%N
M4W1R97-S55S=$-AV4I#0I47!E.B @( @( @9F%I;'5R90T*17AC97!T
M:6]N.B @(IU;FET+F9R86UE=V]R:RY!W-EG1I;VY86EL961%G)O@T*
M365SV%G93H@( @(5X5C=5D([EMAIL PROTECTED](1E861L;V-K(9OB!!
M0B!00T*+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM#0H-@T*
M#0I3=6ET93H@( @( @25L;]#;'5S=5R961(='1P4W1R97-S55S=$-A
MV4-E1EW0Z( @( @(!T97-T0TY14]B:F5C=AOFN:F)OW,N=5S
M=YH96QL;RYT97-T+DAE;QO0VQUW1EF5D2'1T%-TF5SU1EW1#87-E
M*0T*5'EP93H@( @( @(9A:6QUF4-D5X8V5P=EO;CH@(!J=6YI=YF
MF%M97=OFLN07-S97)T:6]N1F%I;5D17)R;W(-DUEW-A9V4Z( @(!7
M87,@86)L92!T;R!I;G9O:V4@F5M;W9E#0HM+2TM+2TM+2TM+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2T-@T*#0H-E-U:71E.B @( @(!-:7-S:6YG0VQA
MW-5;FET55S=$-AV4-E1EW0Z( @( @(!T97-T15P;]Y4V5R=FEC
M95=I=AO=71#;%SRAOFN:F)OW,N=5S=YJ;[EMAIL PROTECTED]5S=Y-:7-S:6YG
M0VQAW-5;FET55S=$-AV4I#0I47!E.B @( @( @97)R;W(-D5X8V5P
M=EO;CH@(!OFN:F)OW,N95P;]Y;65N=Y$97!L;WEM96YT17AC97!T
M:6]N#0I-97-S86=E.B @( @:F)OW,N=5S=#IN86UE/6UIW-I;F=C;%S
MW1EW0@:7,@;F]T(')E9VES=5R960N.R M(YEW1E9!T:')O=V%B;4Z
M(AJ879AYM86YA9V5M96YT+DENW1A;F-E3F]T1F]U;F1%-E'1I;VXZ
M(IB;W-S+G1EW0Z;F%M93UM:7-S:6YG8VQAW-T97-T(ES(YO=!R96=I
MW1EF5D+BD-BTM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+0T*
M#0H-@T*4W5I=4Z( @( @(%-E8W5R:71Y56YI=%1EW1#87-E#0I497-T
M.B @( @( @=5S=%-E8W5R94AT='!);G9O:V5R*]R9RYJ8F]SRYT97-T
M+FYA;6EN9RYT97-T+E-E8W5R:71Y56YI=%1EW1#87-E*0T*5'EP93H@( @
M( @(9A:6QUF4-D5X8V5P=EO;CH@(!J=6YI=YFF%M97=OFLN07-S
M97)T:6]N1F%I;5D17)R;W(-DUEW-A9V4Z( @(!3:]U;0@;F]T(AA
[EMAIL PROTECTED];B!A8FQE('1O(QO;VMUAI;G9O:V5RRD-BTM+2TM+2TM+2TM
M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+0T*#0H-@T*4W5I=4Z( @( @(%-E
M8W5R:71Y56YI=%1EW1#87-E#0I497-T.B @( @( @=5S=%-E8W5R94AT
M='!);G9O:V5R1F%I;'5R92AOFN:F)OW,N=5S=YN86UI;FN=5S=Y3
M96-UFET55N:71497-T0V%S92D-E1Y4Z( @( @(!F86EL=7)E#0I%
M-E'1I;VXZ( @:G5N:70N9G)A;65W;W)K+D%SV5R=EO;D9A:6QE9$5R
MF]R#0I-97-S86=E.B @( @4VAO=6QD(YO=!H879E()[EMAIL PROTECTED])L92!T
M;R!L;V]K=7 H:6YV;VMEG,I#0HM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM
,+2TM+2TM+2T-@T*
end
---
This SF.net email is sponsored by: ValueWeb:
Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-713352 ] BigDecimals lose fractional digits
Bugs item #713352, was opened at 2003-04-01 06:29 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=713352group_id=22866 Category: JBossCMP Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Paul Boocock (boocockp) Assigned to: Nobody/Anonymous (nobody) Summary: BigDecimals lose fractional digits Initial Comment: BIgDecimal CMP fields may lose the digits after the decimal point when they are stored in the database. This was observed with: JBoss 3.0.6 Windows 2000 JDK1.4.1_02 Sybase Adaptive Server Enterprise/11.9.2.1 Sybase jConnect 5.5 JDBC driver I believe this problem is caused by using the PreparedStatement.setObject method without the scale parameter, which assumes a scale of zero. I fixed it in my installation by patching org.jboss.ejb.plugins.cmp.jdbc.JDBCUtil to pass the scale of BigDecimals. Fixed version attached. I believe the relevant code in the CVS Head is still the same. -- Comment By: Scott M Stark (starksm) Date: 2003-04-03 21:06 Message: Logged In: YES user_id=175228 There is no attachment. Check the upload box when adding an attachment. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=713352group_id=22866 --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JB4DR1 Deadline MAY 26
Did you guys end up doing it in such a way so that you can use one protocol one way and another protocol the other way like you had mentioned? Secondly, what is really going to be cool when we expose this via AOP remoting... Bill, what are your plans for that? Thanks, Nathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Haynie Sent: Thursday, April 03, 2003 8:21 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 Jboss Remoting callbacks are in - I wil commit in the next day or so when tom and I finish testing. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Thursday, April 03, 2003 6:06 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 I'm ok with JMS. I didn't think you could rewrite in such short of time. Especially with Remoting and AOP just now becoming stable. I think this email thread is good because it will allow us to determine whether or not we can release. I still think there is enough functionality. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nathan Phelps Sent: Thursday, April 03, 2003 5:48 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 I agree that there is some great stuff in there already. However, being that the AOP transaction, security, remoting, etc. was only recently released in its first iteration, and the fact that JBoss remoting doesn't yet support true callbacks (Jeff says it is coming) there is simply no way I can deliver the new JMS implementation BUILT ON TOP of these services by May 5th! And I'm going to be out basically two weeks between now and then with customers as I know others will be as well. Since the whole point of the JMS rewrite is to take advantage of the core JBoss AOP services, I haven't really had that much time to do so since the services have only recently been released. Therefore, I expect that a May 26th release will ONLY INCLUDE THE OLD JMS CODE which is currently in HEAD. It is the only option with a May 5th deadline in my opinion. If everyone is OK with this and we're committed to that date, then I am must immediately shift my attention from the development of the new code build on top of the AOP framework to the old code currently in HEAD to start working on ensuring JMS 1.1 compliance, stability, etc. as well as applying the HTTP IL code currently only in Branch_3_2 to HEAD. Then, after the May 26th release, I'll continue working on the new JMS code which is build on top of the AOP framework. Comments? Thanks, Nathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Thursday, April 03, 2003 3:22 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 There's already a lot we can release. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you are delusional if you think JB4 will be ready for JavaOne. -dain On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote: Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our
Re: [JBoss-dev] Does clustering work on OS X?
3.2 works fine on the same box/JDK. I'm clustering web sessions just fine. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Dain Sundstrom [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 03, 2003 1:13 PM Subject: Re: [JBoss-dev] Does clustering work on OS X? Hey that is my code Is it not even starting for you? I can remove the ObjectCopier service until I figure out why it is hanging? I don't see why this would effect shutdown. Does this happen when you run the default configuration. Is it a problem to reference awt classes like Color from the server? I can remove all awt references from these classes. I was just trying to support copying of all data objects included in the JDK. -dain --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JB4DR1 Deadline MAY 26
We haven't added the different protocols, but that should be easy enough to do and a great idea. I sent bill a note tonight about doing a generic AOP remoting event/listener framework for POJOs. My thought is using generic JavaBean style java.util.EventListener/java.util.EventObject (or bounded properties, etc) so you could dynamically attach remote listeners to regular POJOs to get remote events. Nathan, do you want me to help you with doing a JMSServerInvocationHandler? -- I would like to refactor down the async event stuff in JMX into the base remoting framework so that you just deal with the functionality pieces of listeners/events in the invocation handler. I really need another good subsystem to make sure it gets refactored properly. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nathan Phelps Sent: Thursday, April 03, 2003 11:44 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 Did you guys end up doing it in such a way so that you can use one protocol one way and another protocol the other way like you had mentioned? Secondly, what is really going to be cool when we expose this via AOP remoting... Bill, what are your plans for that? Thanks, Nathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Haynie Sent: Thursday, April 03, 2003 8:21 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 Jboss Remoting callbacks are in - I wil commit in the next day or so when tom and I finish testing. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Thursday, April 03, 2003 6:06 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 I'm ok with JMS. I didn't think you could rewrite in such short of time. Especially with Remoting and AOP just now becoming stable. I think this email thread is good because it will allow us to determine whether or not we can release. I still think there is enough functionality. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nathan Phelps Sent: Thursday, April 03, 2003 5:48 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 I agree that there is some great stuff in there already. However, being that the AOP transaction, security, remoting, etc. was only recently released in its first iteration, and the fact that JBoss remoting doesn't yet support true callbacks (Jeff says it is coming) there is simply no way I can deliver the new JMS implementation BUILT ON TOP of these services by May 5th! And I'm going to be out basically two weeks between now and then with customers as I know others will be as well. Since the whole point of the JMS rewrite is to take advantage of the core JBoss AOP services, I haven't really had that much time to do so since the services have only recently been released. Therefore, I expect that a May 26th release will ONLY INCLUDE THE OLD JMS CODE which is currently in HEAD. It is the only option with a May 5th deadline in my opinion. If everyone is OK with this and we're committed to that date, then I am must immediately shift my attention from the development of the new code build on top of the AOP framework to the old code currently in HEAD to start working on ensuring JMS 1.1 compliance, stability, etc. as well as applying the HTTP IL code currently only in Branch_3_2 to HEAD. Then, after the May 26th release, I'll continue working on the new JMS code which is build on top of the AOP framework. Comments? Thanks, Nathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Thursday, April 03, 2003 3:22 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 There's already a lot we can release. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you are delusional if you think JB4 will be ready for JavaOne. -dain On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote: Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon
RE: [JBoss-dev] Oswego util.concurrent jar updated
by the time they're through JSR..? On Thu, 3 Apr 2003, Nathan Phelps wrote: Any chance they'll ever update the package name to get rid of the capital EDU... drives me crazy. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott M Stark Sent: Thursday, April 03, 2003 4:02 PM To: [EMAIL PROTECTED] Subject: [JBoss-dev] Oswego util.concurrent jar updated I updated the Oswego util.concurrent jar in 3.0+ from the rather ancient 1.3.0 version to 1.3.2 as we found some serious concurrency failures in the ConcurrentHashMap and ConcurrentReaderHashMap classes in looking into some JMS load test failures. A bit ironic that the concurrent package was messing up concurrency. Scott Stark Chief Technology Officer JBoss Group, LLC --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
AW: [JBoss-dev] JB4DR1 Deadline MAY 26
Until 26th of May, I will have a version of W2EE deployment ready (at least the subset of the webservices.xml and jaxrpc-mapping.xml that can be easily mapped via a XSL-driven WebServiceDeployer to the existing web-service.xml/AxisService; deployer hooks in EJBDeployer+WARDeployer-WebServiceDeployer must be coordinated with Bill? And Scott?). I will also have catered for a reasonable auto-registration of web service wsdl in uddi until then. I cannot guarantuee Xdoclet support to generate J2EE1.4 webservices.xml and JAXRPC mappings. Maybe there will be a volunteer for this (one of the xpetstore guys was interested in trying that out?). Maybe the xdoclet team will have something in that direction anyway ... I would delay all web service extensions of JCA and JMS (just a guess from a quick look into the draft) and the tighter integration of the Axis and Jboss invocation stacks then after JB4DR1. CGJ -Ursprüngliche Nachricht- Von: Bill Burke [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 4. April 2003 00:28 An: [EMAIL PROTECTED] Betreff: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 JBoss Remoting AOP + tx, security, versioning, remoting, clustering, txlock, caching DTM (waiting on David's response) EMB (Enterprise Media Beans) JUDDI integration If I can get it done: AOP + EJB (packaged extensions to EJB) and don't forget Nukes! Anybody got anything to add to this list? Who doesn't think they'll be done by May 5th? Who thinks they'll be cutting it close? Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:48 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 Ok then there are 4 weeks to get the new stuff done? Marc, Bill, sure we could do a release but what difference would it make if the new features are not in it. Is this a release just to show off AOP? What about any of the other new stuff? Just give the users a solid 3.2 and they will be happy. -dain On Thursday, April 3, 2003, at 03:30 PM, Bill Burke wrote: It will be ready and stable. Functionality freeze is May 5th. What functionality doesn't make it by then will be left out of the release. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you are delusional if you think JB4 will be ready for JavaOne. -dain On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote: Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and also as a proof of how powerful the approach is we still develop a full J2EE server. Meaning that you can choose to live in the J2EE world work on JBoss J2EE and access all the prepackaged AOP goodies as you have been doing since JBoss2.0. There seems to be a lot of fear at SUN from what I can tell in the press, that we will abandon J2EE. We love J2EE. When really we will support J2EE for the forthcoming future. Never do we talk about abandoning J2EE, we just let the user access core functionality in the open server and think at the AOP level. A more fundamental construct of the framework. The reason we are almost there is that it is also a very old implementation in JBoss. We have been doing it for a long time but never talked/packaged it this way. We make it easy for you to leverage the AOP layer. The implementation is old the way you interact with JBoss is new. It can also be old if you decide to stay at the J2EE level which will be fully supported. But you are now invited to roam in the core JBoss system, in fact you may find it very cozy as you port POJO based applications to JBoss. There will be a stabilization period though. We are making an aggressive push to release JB4 by JavaONE with all our resources dedicated to implementing the final AOP system aspects and porting some of the existing code to that. We're making an aggressive push to release JBoss 4.0 by JavaOne. We're targeting May 26th. That leaves us 2 month from now. I REPEAT TARGET FOR JBOSS4.0 DR1 MAY 26TH To meet this aggressive deadline, we need to set some dates. There will be a functionality freeze, Monday, May 5th. All new functionality commits after May 5th must be approved by either Scott Stark, or Bill Burke. We will not branch May 5th, but instead make the month of May, JBoss 4.0 stability en route to a Developpers Release 1 (DR1). Please think long and hard and fast about your modules. Many of you are
RE: [JBoss-dev] JBoss remoting callbacks [was JB4DR1 Deadline MAY 26]
Jeff made the fix last night and I have not looked at the code yet (he still has it local while we are testing that and some other fixes out). However, my understanding from Jeff is that the invoker client passes its locator to the invoker server if it wishes to receive callbacks. The invoker server will then use that for establishing the connection back to the client to send notifications (callbacks). Given this, it will be pretty easy to make it so the calling code can give the client invoker the locator to use for callbacks, which it then gives the invoker server (and will use its own by default as is now). I can put this in this weekend (if Jeff doesn't beat me to it). It sounds like there won't be enough time to include JMS as one of the invoker transport before the deadline. However, I would personally be interested in working with you on it. Depending on how soon you will have time to start on it, might be wise to make a branch just for the JMS transport, until JB4DR1. -Tom -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nathan Phelps Sent: Thursday, April 03, 2003 11:44 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 Did you guys end up doing it in such a way so that you can use one protocol one way and another protocol the other way like you had mentioned? Secondly, what is really going to be cool when we expose this via AOP remoting... Bill, what are your plans for that? Thanks, Nathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Haynie Sent: Thursday, April 03, 2003 8:21 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 Jboss Remoting callbacks are in - I wil commit in the next day or so when tom and I finish testing. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Thursday, April 03, 2003 6:06 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 I'm ok with JMS. I didn't think you could rewrite in such short of time. Especially with Remoting and AOP just now becoming stable. I think this email thread is good because it will allow us to determine whether or not we can release. I still think there is enough functionality. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nathan Phelps Sent: Thursday, April 03, 2003 5:48 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 I agree that there is some great stuff in there already. However, being that the AOP transaction, security, remoting, etc. was only recently released in its first iteration, and the fact that JBoss remoting doesn't yet support true callbacks (Jeff says it is coming) there is simply no way I can deliver the new JMS implementation BUILT ON TOP of these services by May 5th! And I'm going to be out basically two weeks between now and then with customers as I know others will be as well. Since the whole point of the JMS rewrite is to take advantage of the core JBoss AOP services, I haven't really had that much time to do so since the services have only recently been released. Therefore, I expect that a May 26th release will ONLY INCLUDE THE OLD JMS CODE which is currently in HEAD. It is the only option with a May 5th deadline in my opinion. If everyone is OK with this and we're committed to that date, then I am must immediately shift my attention from the development of the new code build on top of the AOP framework to the old code currently in HEAD to start working on ensuring JMS 1.1 compliance, stability, etc. as well as applying the HTTP IL code currently only in Branch_3_2 to HEAD. Then, after the May 26th release, I'll continue working on the new JMS code which is build on top of the AOP framework. Comments? Thanks, Nathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Thursday, April 03, 2003 3:22 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 There's already a lot we can release. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you are delusional if you think JB4 will be ready for JavaOne. -dain On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote: Guys, We are thinking a lot about the forthcoming JB4 release. It is a truly exciting step for us as we believe we will bring a programming style, whose time has come, to a mass audience. AOP as Bill says is a clear wave for system level services on par with OOP. On top of it and
RE: [JBoss-dev] JBoss remoting callbacks [was JB4DR1 Deadline MAY 26]
Guess Jeff beat me to it ;) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Tom Elrod Sent: Friday, April 04, 2003 1:49 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JBoss remoting callbacks [was JB4DR1 Deadline MAY 26] Jeff made the fix last night and I have not looked at the code yet (he still has it local while we are testing that and some other fixes out). However, my understanding from Jeff is that the invoker client passes its locator to the invoker server if it wishes to receive callbacks. The invoker server will then use that for establishing the connection back to the client to send notifications (callbacks). Given this, it will be pretty easy to make it so the calling code can give the client invoker the locator to use for callbacks, which it then gives the invoker server (and will use its own by default as is now). I can put this in this weekend (if Jeff doesn't beat me to it). It sounds like there won't be enough time to include JMS as one of the invoker transport before the deadline. However, I would personally be interested in working with you on it. Depending on how soon you will have time to start on it, might be wise to make a branch just for the JMS transport, until JB4DR1. -Tom -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nathan Phelps Sent: Thursday, April 03, 2003 11:44 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 Did you guys end up doing it in such a way so that you can use one protocol one way and another protocol the other way like you had mentioned? Secondly, what is really going to be cool when we expose this via AOP remoting... Bill, what are your plans for that? Thanks, Nathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Haynie Sent: Thursday, April 03, 2003 8:21 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 Jboss Remoting callbacks are in - I wil commit in the next day or so when tom and I finish testing. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Thursday, April 03, 2003 6:06 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 I'm ok with JMS. I didn't think you could rewrite in such short of time. Especially with Remoting and AOP just now becoming stable. I think this email thread is good because it will allow us to determine whether or not we can release. I still think there is enough functionality. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Nathan Phelps Sent: Thursday, April 03, 2003 5:48 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 I agree that there is some great stuff in there already. However, being that the AOP transaction, security, remoting, etc. was only recently released in its first iteration, and the fact that JBoss remoting doesn't yet support true callbacks (Jeff says it is coming) there is simply no way I can deliver the new JMS implementation BUILT ON TOP of these services by May 5th! And I'm going to be out basically two weeks between now and then with customers as I know others will be as well. Since the whole point of the JMS rewrite is to take advantage of the core JBoss AOP services, I haven't really had that much time to do so since the services have only recently been released. Therefore, I expect that a May 26th release will ONLY INCLUDE THE OLD JMS CODE which is currently in HEAD. It is the only option with a May 5th deadline in my opinion. If everyone is OK with this and we're committed to that date, then I am must immediately shift my attention from the development of the new code build on top of the AOP framework to the old code currently in HEAD to start working on ensuring JMS 1.1 compliance, stability, etc. as well as applying the HTTP IL code currently only in Branch_3_2 to HEAD. Then, after the May 26th release, I'll continue working on the new JMS code which is build on top of the AOP framework. Comments? Thanks, Nathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Burke Sent: Thursday, April 03, 2003 3:22 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] JB4DR1 Deadline MAY 26 There's already a lot we can release. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dain Sundstrom Sent: Thursday, April 03, 2003 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26 I think you
[JBoss-dev] [ jboss-Bugs-713613 ] Unable to use declarative security with HTTP clustering
Bugs item #713613, was opened at 2003-04-01 16:09 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=713613group_id=22866 Category: JBossWeb Group: v3.2 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Mike Finn (mikefinn) Assigned to: Scott M Stark (starksm) Summary: Unable to use declarative security with HTTP clustering Initial Comment: Basic application w/ declarative security and HTTP session clustering enabled. When I post to j_security_check, I get the stack trace below. When j_security is invoked, I am getting the exception below. I have other applications (not using JAAS) which are working fine in the http session clustered environment. If it matters, I am using mod_jk2 in front as a load balancer. Anyway, I did some digging and a session attribute is being set of type JBossUserPrincipal (inner class to JBossUserRealm), which is in fact not serializable. I have started down the path to making things serializable, but am into stuff that I am not sure should be serializing (such as JaasSecurityManager). I'd be glad to do the fix, but may need some help from Scott/Jules/etc. I am assuming the principal should be in the distributed session. Also, I saw a post in forums that someone had the problem with 3.0.4. I can include an EAR if necessary. mike 14:18:29,541 WARN [jbossweb] WARNING: Exception for /opm/j_security_check java.lang.IllegalArgumentException: distributed attribute value must be Serializable,EJBObject,EJBHome,UserTransaction or Context: mjf860 at org.mortbay.j2ee.session.TypeCheckingInterceptor.setAt tribute(TypeCheckingInterceptor.java:76) at org.mortbay.j2ee.session.StateInterceptor.setAttribute (StateInterceptor.java:78) at org.mortbay.j2ee.session.AroundInterceptor.setAttribute (AroundInterceptor.java:198) at org.mortbay.j2ee.session.StateAdaptor.setAttribute (StateAdaptor.java:249) at org.mortbay.jetty.servlet.FormAuthenticator.authenticate d(FormAuthenticator.java:118) at org.mortbay.http.SecurityConstraint.check (SecurityConstraint.java:401) at org.mortbay.http.HttpContext.checkSecurityConstraints (HttpContext.java:1456) at org.mortbay.jetty.servlet.ServletHttpContext.checkSecuri tyConstraints(ServletHttpContext.java:137) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatc h(WebApplicationHandler.java:235) at org.mortbay.jetty.servlet.ServletHandler.handle (ServletHandler.java:558) at org.mortbay.http.HttpContext.handle (HttpContext.java:1714) -- Comment By: Scott M Stark (starksm) Date: 2003-04-03 23:21 Message: Logged In: YES user_id=175228 JBossUserPrincipal has been made serializable so that it may be placed into distribued or persistent sessions. This change has been made in the 3.2 branch and needs to be merged to 3.0. -- Comment By: Sacha Labourey (slaboure) Date: 2003-04-02 02:03 Message: Logged In: YES user_id=95900 FYI, this doesn't occur if you don't use FORM authentication. This is not dependent on which HTTP Session Replication scheme you use, but, instead, a problem in the Jetty TypeCheckingInterceptor. The best thing would be to try to replicate the credentials+principal as well (i.e. extract the value from the non-serializable classes) as long as possible to allow failover without relogging. -- Comment By: Mike Finn (mikefinn) Date: 2003-04-01 21:01 Message: Logged In: YES user_id=418562 Sorry - version is branch_3_2 as of this afternoon. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=713613group_id=22866 --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Oswego util.concurrent jar updated
By definition it will have to move under java.util.concurrent in JDK 1.5 when the JSR166 is supposed to be released. There is a preliminary javadoc for the JSR here: http://gee.cs.oswego.edu/dl/concurrent/dist/docs/index.html Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Juha-P Lindfors [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 03, 2003 10:41 PM Subject: RE: [JBoss-dev] Oswego util.concurrent jar updated by the time they're through JSR..? On Thu, 3 Apr 2003, Nathan Phelps wrote: Any chance they'll ever update the package name to get rid of the capital EDU... drives me crazy. --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Does clustering work on OS X?
DaIn- I will checkout HEAD and test it, I have a similar configuration... If I can get it to fail, I'll pass it on to a couple of the Java guys at Apple to see what's up. -Hunter From: Dain Sundstrom [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Date: Thu, 3 Apr 2003 09:51:59 -0600 To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] Does clustering work on OS X? I wish I could. I can't even move windows. It just goes into la-la-land. My guess is it is some funk networking thing on OS X with the new VM. -dain On Thursday, April 3, 2003, at 02:49 AM, Sacha Labourey wrote: Hi Dain, I see no reason why it wouldn't work, but you should ask Scott as he has made some clustering testings on X. When the locking occurs, please do a stack thread dump and send it to the ML. Cheers, Sacha -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dain Sundstrom Sent: jeudi, 3. avril 2003 08:32 To: [EMAIL PROTECTED] Subject: [JBoss-dev] Does clustering work on OS X? Does clustering in jboss-head work for anyone on OS X? Whenever I try to shutdown jboss-head on my powerbook the entire os locks up until I unplug my wireless access point and 'killall -9 java'. This can take like 30 minutes to get my laptop responsive again. [12:27:50] dain$ java -version java version 1.4.1_01 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-39) Java HotSpot(TM) Client VM (build 1.4.1_01-14, mixed mode) -dain --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
