RE: [JBoss-dev] Any problems vith the cache in 2.4?
Here are some more specifics to the problem: // CASE 1: Doing the following throws a an exception TradingPartner tp = home.findByPrimaryKey(pk); tp.remove(); // CASE 2: But if do this every thing is OK TradingPartner tp = home.findByPrimaryKey(pk); tp.getData(); tp.remove(); Here's the stack trace that I get with CASE 1: [JAWS] Load command executing: SELECT DISP.TRADINGPARTNER.TPID,DISP.TRADINGPARTNER.UPDATETS,DISP.TRADINGPARTNER.UPDATEUSERID,DISP.TRADIN [disp/TradingPartner] TRANSACTION ROLLBACK EXCEPTION:Load failed; nested exception is: java.lang.IllegalArgumentException: object is not an instance of declaring class; nested exception is: java.rmi.ServerException: Load failed; nested exception is: java.lang.IllegalArgumentException: object is not an instance of declaring class [disp/TradingPartner] java.rmi.ServerException: Load failed; nested exception is: [disp/TradingPartner] java.lang.IllegalArgumentException: object is not an instance of declaring class [disp/TradingPartner] java.lang.IllegalArgumentException: object is not an instance of declaring class [disp/TradingPartner] at java.lang.reflect.Field.get(Native Method) [disp/TradingPartner] at org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand.getPkFieldValue(JDBCCommand.java:663) [disp/TradingPartner] at org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand.setPrimaryKeyParameters(JDBCCommand.java:364) [disp/TradingPartner] at org.jboss.ejb.plugins.jaws.jdbc.JDBCLoadEntityCommand.setParameters(JDBCLoadEntityCommand.java:163) [disp/TradingPartner] at org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand.jdbcExecute(JDBCCommand.java:159) [disp/TradingPartner] at org.jboss.ejb.plugins.jaws.jdbc.JDBCLoadEntityCommand.execute(JDBCLoadEntityCommand.java:147) [disp/TradingPartner] at org.jboss.ejb.plugins.jaws.JAWSPersistenceManager.loadEntity(JAWSPersistenceManager.java:156) [disp/TradingPartner] at org.jboss.ejb.plugins.CMPPersistenceManager.loadEntity(CMPPersistenceManager.java:365) [disp/TradingPartner] at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invoke(EntitySynchronizationInterceptor.java:263) [disp/TradingPartner] at org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke(EntityInstanceInterceptor.java:253) [disp/TradingPartner] at org.jboss.ejb.plugins.TxInterceptorCMT.invokeNext(TxInterceptorCMT.java:133) [disp/TradingPartner] at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:298) [disp/TradingPartner] at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:99) [disp/TradingPartner] at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:127) [disp/TradingPartner] at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:195) [disp/TradingPartner] at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:349) [disp/TradingPartner] at org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPContainerInvoker.java:480) [disp/TradingPartner] at org.jboss.ejb.plugins.jrmp.interfaces.GenericProxy.invokeContainer(GenericProxy.java:335) [disp/TradingPartner] at org.jboss.ejb.plugins.jrmp.interfaces.EntityProxy.invoke(EntityProxy.java:133) [disp/TradingPartner] at $Proxy63.remove(Unknown Source) [disp/TradingPartner] at com.commercequest.disp.servlet.TradingPartnerServlet.doEJBDelete(Unknown Source) [disp/TradingPartner] at com.commercequest.disp.servlet.TradingPartnerServlet.service(Unknown Source) . Regards, Hiram From: Hiram Chirino [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] Any problems vith the cache in 2.4? Date: Tue, 10 Jul 2001 01:10:58 -0400 Talking about spooky cache problems, I've run into this problem: I disable the cache by using the 'NoPassivationCachePolicy' and Commit option 'C'. I create a new bean instance. Later I try to remove it but I fail (If you guys want, I'll get you guys a stack trace). I am workin around the problem by loading the bean first by reading some of the values of the fields before I do the remove(). Seems to me like a cache problem since reading some fields makes it happy again. Anybody run into this?? Regards, Hiram From: marc fleury [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] Any problems vith the cache in 2.4? Date: Fri, 6 Jul 2001 08:28:18 -0400 |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of |Lennart Petersson |Sent: Friday, July 06, 2001 4:21 AM |To: [EMAIL PROTECTED] |Subject: SV: [JBoss-dev] Any problems vith the cache in 2.4? | | |Hi! Problem 1 solved by you Vincent - that was the missing |toString() method in the PK class (Should that really matter, why |are JBoss using it in the cache?). that is not correct, we create a safe cache key so something is really spooky marcf | |Problem 2 was no problem, it was the old EJBDoclet passivate bug. |The erroneous component
RE: [JBoss-dev] Any problems vith the cache in 2.4?
I got this one also. It disappeared. I think (not sure) it was because of my bloody hashCode() method. Maybe it is linked to recent changes on cvs version through. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Hiram Chirino Envoyé : mardi 10 juillet 2001 7:11 À : [EMAIL PROTECTED] Objet : RE: [JBoss-dev] Any problems vith the cache in 2.4? Talking about spooky cache problems, I've run into this problem: I disable the cache by using the 'NoPassivationCachePolicy' and Commit option 'C'. I create a new bean instance. Later I try to remove it but I fail (If you guys want, I'll get you guys a stack trace). I am workin around the problem by loading the bean first by reading some of the values of the fields before I do the remove(). Seems to me like a cache problem since reading some fields makes it happy again. Anybody run into this?? Regards, Hiram From: marc fleury [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] Any problems vith the cache in 2.4? Date: Fri, 6 Jul 2001 08:28:18 -0400 |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of |Lennart Petersson |Sent: Friday, July 06, 2001 4:21 AM |To: [EMAIL PROTECTED] |Subject: SV: [JBoss-dev] Any problems vith the cache in 2.4? | | |Hi! Problem 1 solved by you Vincent - that was the missing |toString() method in the PK class (Should that really matter, why |are JBoss using it in the cache?). that is not correct, we create a safe cache key so something is really spooky marcf | |Problem 2 was no problem, it was the old EJBDoclet passivate bug. |The erroneous component was not regenerated with a corrected |EJBDoclet (it was not my component :) | |So that mean that all you guys can keep on with 3.0 :-) | |THANKS! | |/Lennart | |- Original Message - |From: Vincent Harcq [EMAIL PROTECTED] |To: [EMAIL PROTECTED] |Sent: Friday, July 06, 2001 9:05 AM |Subject: RE: [JBoss-dev] Any problems vith the cache in 2.4? | | | Can you try this: | 1. Solution 1 | Add a toString to your PK (hack entitypk.j). | Also put your Cache size very high. | And your overager periods very high as well. | 2. Solution 2. | Set your cache size to 1/1 (min/max) | | Let us know please. | Vincent. | | | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development _ Get your FREE download of MSN Explorer at http://explorer.msn.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Any problems vith the cache in 2.4?
the changes of the cache are found in 2.5. I might retrofit them to 2.4 for other reasons. are you using 2.5 when you say the problems are gone? |I got this one also. |It disappeared. |I think (not sure) it was because of my bloody hashCode() method. |Maybe it is linked to recent changes on cvs version through. marcf ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Any problems vith the cache in 2.4?
Hiram, Can you send a stack trace? Thanks, Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Hiram Chirino Sent: Tuesday, July 10, 2001 1:11 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] Any problems vith the cache in 2.4? Talking about spooky cache problems, I've run into this problem: I disable the cache by using the 'NoPassivationCachePolicy' and Commit option 'C'. I create a new bean instance. Later I try to remove it but I fail (If you guys want, I'll get you guys a stack trace). I am workin around the problem by loading the bean first by reading some of the values of the fields before I do the remove(). Seems to me like a cache problem since reading some fields makes it happy again. Anybody run into this?? Regards, Hiram From: marc fleury [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] Any problems vith the cache in 2.4? Date: Fri, 6 Jul 2001 08:28:18 -0400 |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of |Lennart Petersson |Sent: Friday, July 06, 2001 4:21 AM |To: [EMAIL PROTECTED] |Subject: SV: [JBoss-dev] Any problems vith the cache in 2.4? | | |Hi! Problem 1 solved by you Vincent - that was the missing |toString() method in the PK class (Should that really matter, why |are JBoss using it in the cache?). that is not correct, we create a safe cache key so something is really spooky marcf | |Problem 2 was no problem, it was the old EJBDoclet passivate bug. |The erroneous component was not regenerated with a corrected |EJBDoclet (it was not my component :) | |So that mean that all you guys can keep on with 3.0 :-) | |THANKS! | |/Lennart | |- Original Message - |From: Vincent Harcq [EMAIL PROTECTED] |To: [EMAIL PROTECTED] |Sent: Friday, July 06, 2001 9:05 AM |Subject: RE: [JBoss-dev] Any problems vith the cache in 2.4? | | | Can you try this: | 1. Solution 1 | Add a toString to your PK (hack entitypk.j). | Also put your Cache size very high. | And your overager periods very high as well. | 2. Solution 2. | Set your cache size to 1/1 (min/max) | | Let us know please. | Vincent. | | | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development _ Get your FREE download of MSN Explorer at http://explorer.msn.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Any problems vith the cache in 2.4?
what what bothers me with this on-going discussion: we don't care whether you fuck up your own hashcode or not, we wrap it up and afaik Bill plugged teh last hole there, so that should really be tight as a drum... show me a clear bug repro on this and I will buy it... if it is plain gone then let's burry it. we need closure not impressions. marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of |Vincent Harcq |Sent: Tuesday, July 10, 2001 11:29 AM |To: [EMAIL PROTECTED] |Subject: RE: [JBoss-dev] Any problems vith the cache in 2.4? | | |Yep. |I am working on 2.5. Checked out every week or so. | |But the problem of Hiram is its hashCode of, my hand in the fire. | | the changes of the cache are found in 2.5. I might retrofit them | to 2.4 for | other reasons. | | are you using 2.5 when you say the problems are gone? | | |I got this one also. | |It disappeared. | |I think (not sure) it was because of my bloody hashCode() method. | |Maybe it is linked to recent changes on cvs version through. | | | marcf | | | | ___ | Jboss-development mailing list | [EMAIL PROTECTED] | http://lists.sourceforge.net/lists/listinfo/jboss-development | | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Any problems vith the cache in 2.4?
Yep. I am working on 2.5. Checked out every week or so. But the problem of Hiram is its hashCode of, my hand in the fire. the changes of the cache are found in 2.5. I might retrofit them to 2.4 for other reasons. are you using 2.5 when you say the problems are gone? |I got this one also. |It disappeared. |I think (not sure) it was because of my bloody hashCode() method. |Maybe it is linked to recent changes on cvs version through. marcf ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Any problems vith the cache in 2.4?
I agree, I was a bit too enthousiast on this problem, it will cause confusion. I leave it to you. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de marc fleury Envoyé : mardi 10 juillet 2001 17:42 À : [EMAIL PROTECTED] Objet : RE: [JBoss-dev] Any problems vith the cache in 2.4? what what bothers me with this on-going discussion: we don't care whether you fuck up your own hashcode or not, we wrap it up and afaik Bill plugged teh last hole there, so that should really be tight as a drum... show me a clear bug repro on this and I will buy it... if it is plain gone then let's burry it. we need closure not impressions. marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of |Vincent Harcq |Sent: Tuesday, July 10, 2001 11:29 AM |To: [EMAIL PROTECTED] |Subject: RE: [JBoss-dev] Any problems vith the cache in 2.4? | | |Yep. |I am working on 2.5. Checked out every week or so. | |But the problem of Hiram is its hashCode of, my hand in the fire. | | the changes of the cache are found in 2.5. I might retrofit them | to 2.4 for | other reasons. | | are you using 2.5 when you say the problems are gone? | | |I got this one also. | |It disappeared. | |I think (not sure) it was because of my bloody hashCode() method. | |Maybe it is linked to recent changes on cvs version through. | | | marcf | | | | ___ | Jboss-development mailing list | [EMAIL PROTECTED] | http://lists.sourceforge.net/lists/listinfo/jboss-development | | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Any problems vith the cache in 2.4?
Talking about spooky cache problems, I've run into this problem: I disable the cache by using the 'NoPassivationCachePolicy' and Commit option 'C'. I create a new bean instance. Later I try to remove it but I fail (If you guys want, I'll get you guys a stack trace). I am workin around the problem by loading the bean first by reading some of the values of the fields before I do the remove(). Seems to me like a cache problem since reading some fields makes it happy again. Anybody run into this?? Regards, Hiram From: marc fleury [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] Any problems vith the cache in 2.4? Date: Fri, 6 Jul 2001 08:28:18 -0400 |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of |Lennart Petersson |Sent: Friday, July 06, 2001 4:21 AM |To: [EMAIL PROTECTED] |Subject: SV: [JBoss-dev] Any problems vith the cache in 2.4? | | |Hi! Problem 1 solved by you Vincent - that was the missing |toString() method in the PK class (Should that really matter, why |are JBoss using it in the cache?). that is not correct, we create a safe cache key so something is really spooky marcf | |Problem 2 was no problem, it was the old EJBDoclet passivate bug. |The erroneous component was not regenerated with a corrected |EJBDoclet (it was not my component :) | |So that mean that all you guys can keep on with 3.0 :-) | |THANKS! | |/Lennart | |- Original Message - |From: Vincent Harcq [EMAIL PROTECTED] |To: [EMAIL PROTECTED] |Sent: Friday, July 06, 2001 9:05 AM |Subject: RE: [JBoss-dev] Any problems vith the cache in 2.4? | | | Can you try this: | 1. Solution 1 | Add a toString to your PK (hack entitypk.j). | Also put your Cache size very high. | And your overager periods very high as well. | 2. Solution 2. | Set your cache size to 1/1 (min/max) | | Let us know please. | Vincent. | | | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development _ Get your FREE download of MSN Explorer at http://explorer.msn.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Any problems vith the cache in 2.4?
Can you try this: 1. Solution 1 Add a toString to your PK (hack entitypk.j). Also put your Cache size very high. And your overager periods very high as well. 2. Solution 2. Set your cache size to 1/1 (min/max) Let us know please. Vincent. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Lennart Petersson Envoyé : jeudi 5 juillet 2001 11:55 À : jBoss Developer Objet : [JBoss-dev] Any problems vith the cache in 2.4? Ok, please dont hang me, not now :-) I know that i'm not given you much details and no clean and short testcase but i still wanted to trigger your brains to give me some advice of how to preceed my debugging. Fact: Using CVS brancs 2.4 from 2001-07-04. CMP entity beans, commit option A, tuned updates, using isModified() method, using EJBDoclet code generator (still on 0.95 with some newer patches incorparated - like ejbPassivate() bug). Alwasy using a stateless Session Bean in front of the Entity Bean. All session bean methods that will result in a db update has TX_REQUIRED. All other session bean methods as TX_SUPPORTS. Oracle database and standalone clients. Problem scenario 1: A) Populates a GUI table with data originating from a findAll(). B) User selects one row and details about that entity is looked up using a findByPrimaryKey() C) User change some attribute and this _IS_ stored in database D) User returns to the GUI table wich is repopulated using a findAll() --- Old value is seen E) User selects same row again details about that entity is looked up using a findByPrimaryKey() --- Correct vallue is seen F) Restart client, still old value in GUI table using findAll() but correct value in details frame using findByPrimaryKey. G) Restarting JBoss, now correcte value in both cases. When i'm debugging JBoss i can see that the findAll in D) is getting old values from the cache. If i change cache sizes to min=1 and max=1 the problem i no more! Should i take this for a evidence of JBoss bug rather then a bug i our code? Please note that if i'm doing a test bean and a short testcase for this scenario then i can't reproduce the error. Which as opposed to above makes our app more guilty or? Problem scenario 2: A) Viewing details from an entity in a GUI. B) Waits until the server has been idle from some hour or so. C) Trying to view details from this same entity again --- Now incorrect values are seen. This one i've not debugged att all. Guess that during B) beans are passivated due to them being out aged. Also please not that in this case the session bean in front of entity beans is a stateful bean. Are there anny know problems with caches/pools in JBoss 2.4? Are there any mysterios behavior noted by someon but not yet traced down? Also a bit off-topic: I'm using Bugseeker to debug my code and JBoss. Running on a P3 800 with 512 in memory and it is fu...ng slow!!! What are you using as a debug tool? I'm attaching to JBoss JVM as a remote process but still on same machine, guess i will have better performance if Bugseeker is the one really starting JBoss, havent tried that yet. As it is now debugging is more of a wait then really productive :-( Please, any ideas are welcome! I will complement with more detailes as my own tests progress. This might be what make us Go! or Die! /Lennart === Lennart Petersson www.benefit.se/english [EMAIL PROTECTED] ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Any problems vith the cache in 2.4?
|-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of |Lennart Petersson |Sent: Friday, July 06, 2001 4:21 AM |To: [EMAIL PROTECTED] |Subject: SV: [JBoss-dev] Any problems vith the cache in 2.4? | | |Hi! Problem 1 solved by you Vincent - that was the missing |toString() method in the PK class (Should that really matter, why |are JBoss using it in the cache?). that is not correct, we create a safe cache key so something is really spooky marcf | |Problem 2 was no problem, it was the old EJBDoclet passivate bug. |The erroneous component was not regenerated with a corrected |EJBDoclet (it was not my component :) | |So that mean that all you guys can keep on with 3.0 :-) | |THANKS! | |/Lennart | |- Original Message - |From: Vincent Harcq [EMAIL PROTECTED] |To: [EMAIL PROTECTED] |Sent: Friday, July 06, 2001 9:05 AM |Subject: RE: [JBoss-dev] Any problems vith the cache in 2.4? | | | Can you try this: | 1. Solution 1 | Add a toString to your PK (hack entitypk.j). | Also put your Cache size very high. | And your overager periods very high as well. | 2. Solution 2. | Set your cache size to 1/1 (min/max) | | Let us know please. | Vincent. | | | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Any problems vith the cache in 2.4?
You must not be passing -classic to the jvm running JBoss as I use bugseeker with a dual P3 500 with 512 Mb and its very fast. The jboss command line should be: set DBG=-classic -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,addres s=12345,suspend=y java %DBG% -classpath %CLASSPATH% org.jboss.Main ... Also a bit off-topic: I'm using Bugseeker to debug my code and JBoss. Running on a P3 800 with 512 in memory and it is fu...ng slow!!! What are you using as a debug tool? I'm attaching to JBoss JVM as a remote process but still on same machine, guess i will have better performance if Bugseeker is the one really starting JBoss, havent tried that yet. As it is now debugging is more of a wait then really productive :- ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
