[JBoss-user] JBOSS, ECPerf, JMeter
Hi ! Has someone already run the ECPerf J2ee benchmark with JBOSS-2.4 ?? With what for a driver ??? Can apache JMeter be used for such a driver ?? Thanks /Joel ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Courrier : http://courrier.yahoo.fr ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Hot Deploy Does Not reflect Change.
There is only one new file copied and that is classes12.zip (Oracle thin driver) I am using ant to build jar files. David Jencks [EMAIL PROTECTED] wrote: Just to check the obvious things first... there are no copies of any ofthese classes in lib/ext?david jencksOn 2001.11.01 20:11:31 -0500 vijay jagtap wrote: JBoss-2.4.3_Tomcat-3.2.3 It seems the AppServer is caching the JAR files to some unknown place. If I change the JAR file and redeploy, the changes are Not getting effective. Even I shut down JBoss, machine, still I don't see the new changes made to Bean. I deleted entire tmp folder. NO success. I don't think there any references kept open to Bean since I am running simple test client program. Thanks. - Do You Yahoo!? Find a job, post your resume on Yahoo! Careers. JBoss-2.4.3_Tomcat-3.2.3 It seems the AppServer is caching the JAR files to some unknown place. If I change the JAR file and redeploy, the changes are Not getting effective. Even I shut down JBoss, machine, still I don't see the new changes made to Bean. I deleted entire tmp folder. NO success. I don't think there any references kept open to Bean since I am running simple test client program. Thanks. Do You Yahoo!? Find a job, post your resume on
RE: [JBoss-user] JBOSS, ECPerf, JMeter
ECPerf comes with its own driver/client side application. To run a valid test you must that driver/client application. Good Luck. John M. Carney - [EMAIL PROTECTED] Sr. Software Engineer TowerJ Corporation - http://www.towerj.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of joel cordonnier Sent: Friday, November 02, 2001 7:41 AM To: [EMAIL PROTECTED] Subject: [JBoss-user] JBOSS, ECPerf, JMeter Hi ! Has someone already run the ECPerf J2ee benchmark with JBOSS-2.4 ?? With what for a driver ??? Can apache JMeter be used for such a driver ?? Thanks /Joel ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Courrier : http://courrier.yahoo.fr ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Hot Deploy Does Not reflect Change.
I take some of my words back. ( I had messed up in JBOSS_CLASSPATH var.) I can see changes only when I shut down and restart server. So every time I change bean, I have to restart the server. How to solve this problem ??? David Jencks [EMAIL PROTECTED] wrote: Just to check the obvious things first... there are no copies of any ofthese classes in lib/ext?david jencksOn 2001.11.01 20:11:31 -0500 vijay jagtap wrote: JBoss-2.4.3_Tomcat-3.2.3 It seems the AppServer is caching the JAR files to some unknown place. If I change the JAR file and redeploy, the changes are Not getting effective. Even I shut down JBoss, machine, still I don't see the new changes made to Bean. I deleted entire tmp folder. NO success. I don't think there any references kept open to Bean since I am running simple test client program. Thanks. - Do You Yahoo!? Find a job, post your resume on Yahoo! Careers. JBoss-2.4.3_Tomcat-3.2.3 It seems the AppServer is caching the JAR files to some unknown place. If I change the JAR file and redeploy, the changes are Not getting effective. Even I shut down JBoss, machine, still I don't see the new changes made to Bean. I deleted entire tmp folder. NO success. I don't think there any references kept open to Bean since I am running simple test client program. Thanks. Do You Yahoo!? Find a job, post your resume on
[JBoss-user] DB connection/transactions in the same J2EE transaction context.
I am hoping to find a simple resolution to this problem. I am running JBoss 2.4.3 I have a SLSB that is used for persisting business objects implemented as simple java beans. These beans have alter egos as Entity Beans in the app server. (in fact, corresponding entity beans are simply facades for a copy of the java bean) The SLSB simply determines which class of Entity Bean to use, find it the instance nessecary, and set the underlying business object to that passed into the SLSB. The problem comes when passing a queue of business objects where later objects depend on side effects of the earlier objects within the database. According to the EJB 2.0 spec The Bean Provider can control shareability of the connections acquired from the resource manager connection factory. By default, connections to a resource manager are shareable across other enterprise beans in the application that use the same resource in the same transaction context. The sharing of connections to a resource manager allows the container to optimize the use of connections and enables the container's use of local transaction optimizations. (Section 20.4.1.1) From this I make the assumption (bad word I know) that, under a single (J2EE) transaction context, for the same resource, regardless of which instance of entity bean is being operated on, a connection will be re-used when requested more than once. I am not clear if this applies to multiple entity bean classes, since there references are in a difference namespace, but they do reference the same resource manager underneath everything. The following are snippets from my ejb-jar.xml and jboss.xml files: ejb-jar.xml resource-ref res-ref-namejdbc/jts.Connection/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth res-sharing-scopeSharable/res-sharing-scope /resource-ref jboss.xml resource-ref res-ref-namejdbc/jts.Connection/res-ref-name resource-namejts.sempraDev/resource-name /resource-ref resource-manager res-class=org.jboss.ejb.deployment.JDBCResource res-namejts.sempraDev/res-name res-jndi-namejava:/jts.sempraDev/res-jndi-name /resource-manager All of my beans have a trans-attribute of Required for all methods that affect the state of objects and a default of Supports for everything else. What appears to be happening is that there is no guaruntee that the same db connection will be used throughout the context of a single transaction, even within the same entity bean class. This is causing changes to be performed under one db transaction and subsequent changes that depend on the db side effects of the earlier changes to be performed under a seperate db transaction. The subsequent db transactions cannot see the earlier changes to the db and fail, rolling back the entire set of db transactions. When the business objects are submitted one at a time from the client everything works fine. It is only when a queue of business objects are submitted that the problem exists. From what I have understood about JBoss, this part of the EJB 2.0 specification has been in place for some timel. Correct me if I am wrong. Any help/clarification would be appreciated. Karl Koster [EMAIL PROTECTED] Sempra Energy Trading 203-355-5182 ** This e-mail contains privileged attorney-client communications and/or confidential information, and is only for the use by the intended recipient. Receipt by an unintended recipient does not constitute a waiver of any applicable privilege. Reading, disclosure, discussion, dissemination, distribution or copying of this information by anyone other than the intended recipient or his or her employees or agents is strictly prohibited. If you have received this communication in error, please immediately notify us and delete the original material from your computer. Sempra Energy Trading Corp. (SET) is not the same company as SDGE or SoCalGas, the utilities owned by SET's parent company. SET is not regulated by the California Public Utilities Commission and you do not have to buy SET's products and services to continue to receive quality regulated service from the utilities. ** ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] DB connection/transactions in the same J2EE transaction context.
If you are depending on the changes being sent to the db in a certain order.. this may not be happening, I'm not sure. I think right before the end of the transaction all ejbStore methods get called, but perhaps not in any particular order. If you are using non xa connections (local transactions in the spec) then jboss is in fact putting all the work on one transaction through one connection - or it wouldn't be one transaction. With an xa capable driver, it is not supposed to matter... which doesn't mean the driver is implemented correctly. david jencks On 2001.11.02 14:06:29 -0500 Karl Koster wrote: I am hoping to find a simple resolution to this problem. I am running JBoss 2.4.3 I have a SLSB that is used for persisting business objects implemented as simple java beans. These beans have alter egos as Entity Beans in the app server. (in fact, corresponding entity beans are simply facades for a copy of the java bean) The SLSB simply determines which class of Entity Bean to use, find it the instance nessecary, and set the underlying business object to that passed into the SLSB. The problem comes when passing a queue of business objects where later objects depend on side effects of the earlier objects within the database. According to the EJB 2.0 spec The Bean Provider can control shareability of the connections acquired from the resource manager connection factory. By default, connections to a resource manager are shareable across other enterprise beans in the application that use the same resource in the same transaction context. The sharing of connections to a resource manager allows the container to optimize the use of connections and enables the container's use of local transaction optimizations. (Section 20.4.1.1) From this I make the assumption (bad word I know) that, under a single (J2EE) transaction context, for the same resource, regardless of which instance of entity bean is being operated on, a connection will be re-used when requested more than once. I am not clear if this applies to multiple entity bean classes, since there references are in a difference namespace, but they do reference the same resource manager underneath everything. The following are snippets from my ejb-jar.xml and jboss.xml files: ejb-jar.xml resource-ref res-ref-namejdbc/jts.Connection/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth res-sharing-scopeSharable/res-sharing-scope /resource-ref jboss.xml resource-ref res-ref-namejdbc/jts.Connection/res-ref-name resource-namejts.sempraDev/resource-name /resource-ref resource-manager res-class=org.jboss.ejb.deployment.JDBCResource res-namejts.sempraDev/res-name res-jndi-namejava:/jts.sempraDev/res-jndi-name /resource-manager All of my beans have a trans-attribute of Required for all methods that affect the state of objects and a default of Supports for everything else. What appears to be happening is that there is no guaruntee that the same db connection will be used throughout the context of a single transaction, even within the same entity bean class. This is causing changes to be performed under one db transaction and subsequent changes that depend on the db side effects of the earlier changes to be performed under a seperate db transaction. The subsequent db transactions cannot see the earlier changes to the db and fail, rolling back the entire set of db transactions. When the business objects are submitted one at a time from the client everything works fine. It is only when a queue of business objects are submitted that the problem exists. From what I have understood about JBoss, this part of the EJB 2.0 specification has been in place for some timel. Correct me if I am wrong. Any help/clarification would be appreciated. Karl Koster [EMAIL PROTECTED] Sempra Energy Trading 203-355-5182 ** This e-mail contains privileged attorney-client communications and/or confidential information, and is only for the use by the intended recipient. Receipt by an unintended recipient does not constitute a waiver of any applicable privilege. Reading, disclosure, discussion, dissemination, distribution or copying of this information by anyone other than the intended recipient or his or her employees or agents is strictly prohibited. If you have received this communication in error, please immediately notify us and delete the original material from your computer. Sempra Energy Trading Corp. (SET) is not the same company as SDGE or SoCalGas, the utilities owned by SET's parent company. SET is not regulated by the California Public Utilities Commission and you do not have to buy SET's products and services to continue to receive quality regulated service from the
Re: [JBoss-user] DB connection/transactions in the same J2EE transaction context.
David Jencks wrote: If you are depending on the changes being sent to the db in a certain order.. this may not be happening, I'm not sure. I think right before the end of the transaction all ejbStore methods get called, but perhaps not in any particular order. I believe that 2.4.3 has Bill's fix that forces ejbStores to be called before any finder is called. Not in any specific order, however. -danch ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] DB connection/transactions in the same J2EE transaction context.
To add a little more information to this scenario. The connection pool is using the oracle jdbc 1.1.1 driver using the org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl wrapper for the DataSource. (We have issues with the jdbc 1.2 driver not related to this) We tested this scenario with just two business objects of the same class. The first object created a side effect that the second business object depended on. We put calls to a logging facility (not log4j) to provide a detailed view of what was going on. The calls where ordered correctly. However, the db connection instance was not the same when the second persistance request was made. Karl Koster [EMAIL PROTECTED] Sempra Energy Trading 203-355-5182 If you are depending on the changes being sent to the db in a certain order.. this may not be happening, I'm not sure. I think right before the end of the transaction all ejbStore methods get called, but perhaps not in any particular order. If you are using non xa connections (local transactions in the spec) then jboss is in fact putting all the work on one transaction through one connection - or it wouldn't be one transaction. With an xa capable driver, it is not supposed to matter... which doesn't mean the driver is implemented correctly. david jencks On 2001.11.02 14:06:29 -0500 Karl Koster wrote: I am hoping to find a simple resolution to this problem. I am running JBoss 2.4.3 I have a SLSB that is used for persisting business objects implemented as simple java beans. These beans have alter egos as Entity Beans in the app server. (in fact, corresponding entity beans are simply facades for a copy of the java bean) The SLSB simply determines which class of Entity Bean to use, find it the instance nessecary, and set the underlying business object to that passed into the SLSB. The problem comes when passing a queue of business objects where later objects depend on side effects of the earlier objects within the database. According to the EJB 2.0 spec The Bean Provider can control shareability of the connections acquired from the resource manager connection factory. By default, connections to a resource manager are shareable across other enterprise beans in the application that use the same resource in the same transaction context. The sharing of connections to a resource manager allows the container to optimize the use of connections and enables the container's use of local transaction optimizations. (Section 20.4.1.1) From this I make the assumption (bad word I know) that, under a single (J2EE) transaction context, for the same resource, regardless of which instance of entity bean is being operated on, a connection will be re-used when requested more than once. I am not clear if this applies to multiple entity bean classes, since there references are in a difference namespace, but they do reference the same resource manager underneath everything. The following are snippets from my ejb-jar.xml and jboss.xml files: ejb-jar.xml resource-ref res-ref-namejdbc/jts.Connection/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth res-sharing-scopeSharable/res-sharing-scope /resource-ref jboss.xml resource-ref res-ref-namejdbc/jts.Connection/res-ref-name resource-namejts.sempraDev/resource-name /resource-ref resource-manager res-class=org.jboss.ejb.deployment.JDBCResource res-namejts.sempraDev/res-name res-jndi-namejava:/jts.sempraDev/res-jndi-name /resource-manager All of my beans have a trans-attribute of Required for all methods that affect the state of objects and a default of Supports for everything else. What appears to be happening is that there is no guaruntee that the same db connection will be used throughout the context of a single transaction, even within the same entity bean class. This is causing changes to be performed under one db transaction and subsequent changes that depend on the db side effects of the earlier changes to be performed under a seperate db transaction. The subsequent db transactions cannot see the earlier changes to the db and fail, rolling back the entire set of db transactions. When the business objects are submitted one at a time from the client everything works fine. It is only when a queue of business objects are submitted that the problem exists. From what I have understood about JBoss, this part of the EJB 2.0 specification has been in place for some timel. Correct me if I am wrong. Any help/clarification would be appreciated. Karl Koster [EMAIL PROTECTED] Sempra Energy Trading 203-355-5182 ** This e-mail contains privileged attorney-client communications and/or confidential information, and is only for the use by the intended recipient. Receipt
RE: [JBoss-user] DB connection/transactions in the same J2EE transaction context.
If this is the case, it should still work. The SLSB iterates through a list of business objects, finds there enterprise equivalent (findByPrimaryKey), sets the state and moves on to the next. Since the SLSB does not return before either saving all business object states or the first exception is thrown (i.e. TX rollback) A finder invokation would occur between each store. Unless I misunderstand what you are describing. To simplify this is the order of events. SLSB.saveBusinessObjects(List objs); for each obj in objs findEnterpriseEntity setEnterpriseEntityState end end The SLSB.saveBusinessObjects method has a tx attribute of Required as do all the state setters. All other methods use Supports. -Original Message- From: danch [mailto:[EMAIL PROTECTED]] Sent: Friday, November 02, 2001 3:12 PM To: David Jencks Cc: [EMAIL PROTECTED] Subject: Re: [JBoss-user] DB connection/transactions in the same J2EE transaction context. David Jencks wrote: If you are depending on the changes being sent to the db in a certain order.. this may not be happening, I'm not sure. I think right before the end of the transaction all ejbStore methods get called, but perhaps not in any particular order. I believe that 2.4.3 has Bill's fix that forces ejbStores to be called before any finder is called. Not in any specific order, however. -danch ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ** This e-mail contains privileged attorney-client communications and/or confidential information, and is only for the use by the intended recipient. Receipt by an unintended recipient does not constitute a waiver of any applicable privilege. Reading, disclosure, discussion, dissemination, distribution or copying of this information by anyone other than the intended recipient or his or her employees or agents is strictly prohibited. If you have received this communication in error, please immediately notify us and delete the original material from your computer. Sempra Energy Trading Corp. (SET) is not the same company as SDGE or SoCalGas, the utilities owned by SET's parent company. SET is not regulated by the California Public Utilities Commission and you do not have to buy SET's products and services to continue to receive quality regulated service from the utilities. ** ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] DB connection/transactions in the same J2EE transaction context.
I fucked up my backmerge from 3.0 to 2.4.3. Only 2.4.4(when it comes out), or Branch_2_4 synchs the database on a find or remove call. In 2.4.4 and 3.0, all beans of all types involved within a transaction will be synchronized with the database on a finder or remove call. Also, they will be synchronized in the same order in which they became part of the transaction. Please get latest from Branch_2_4 to get these changes. I'm sorry I screwed up the backmerge Regards, Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of danch Sent: Friday, November 02, 2001 3:12 PM To: David Jencks Cc: [EMAIL PROTECTED] Subject: Re: [JBoss-user] DB connection/transactions in the same J2EE transaction context. David Jencks wrote: If you are depending on the changes being sent to the db in a certain order.. this may not be happening, I'm not sure. I think right before the end of the transaction all ejbStore methods get called, but perhaps not in any particular order. I believe that 2.4.3 has Bill's fix that forces ejbStores to be called before any finder is called. Not in any specific order, however. -danch ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Log4j HELP!
First try different logging levels. You went from debug, which prints everything, to error, which prints very little (only fatal produces less.) Try info. Also, look at your log4j.properties. In a production environment, I would suggest the DailyRollingFileAppender and ConsoleAppender if you want it. Note that you can have different settings for each appender. So you can have debug for your file appender and fatal for your console appender. Finally, after setting log4j.properties how you want it, take a look at jboss.jcml. Some components can have their messaging fine-tuned. For example, XADataSourceLoader has setting for LoggingEnabled. Setting it to true will turn on more detailed logging, setting it to false will give less logging. - Original Message - From: Ferguson, Doug [EMAIL PROTECTED] To: JBoss User (E-mail) [EMAIL PROTECTED] Sent: Friday, November 02, 2001 1:04 PM Subject: [JBoss-user] Log4j HELP! Can anyone give me a quick ramp up for how to configure log4j with jboss. I have been messing around with it and I can't quite figure it out. For instance I while back I wanted to remove all the extraneous messages from jboss and I got input that if I made the following change... log4j.rootCategory=DEFAULT, DEBUG, Console --- log4j.rootCategory=ERROR, Console But the problem is that this hosed everything, for instance I no longer get verifier messages. I was curious how I can get a little more fine grained control. 1) My main goal is to reduce the ammount that is printed at deployment and run. For instance I would like messages from J2EE Deployer Default, Verifier, AutoDeployer But the 3000 messages that print out saying loading security manager are a pain in the neck 2) I would like to be able to add traces to the logs, but that seems to not work ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Hot Deploy Does Not reflect Change.
The traditional source of this type of problem is that you have your bean class somewhere in the classpath that JBoss is using. Make sure that the only instance of your bean class is in the jar in the deploy directory. If it is elsewhere, JBoss may be running that copy instead of the one in the deploy directory. Remember not to have a copy in jboss/lib/ext either. - Original Message - From: vijay jagtap To: [EMAIL PROTECTED] Sent: Friday, November 02, 2001 12:34 PM Subject: Re: [JBoss-user] Hot Deploy Does Not reflect Change. I take some of my words back. ( I had messed up in JBOSS_CLASSPATH var.) I can see changes only when I shut down and restart server. So every time I change bean, I have to restart the server. How to solve this problem ??? David Jencks [EMAIL PROTECTED] wrote: Just to check the obvious things first... there are no copies of any ofthese classes in lib/ext?david jencksOn 2001.11.01 20:11:31 -0500 vijay jagtap wrote: JBoss-2.4.3_Tomcat-3.2.3 It seems the AppServer is caching the JAR files to some unknown place. If I change the JAR file and redeploy, the changes are Not getting effective. Even I shut down JBoss, machine, still I don't see the new changes made to Bean. I deleted entire tmp folder. NO success. I don't think there any references kept open to Bean since I am running simple test client program. Thanks. - Do You Yahoo!? Find a job, post your resume on Yahoo! Careers. JBoss-2.4.3_Tomcat-3.2.3 It seems the AppServer is caching the JAR files to some unknown place. If I change the JAR file and redeploy, the changes are Not getting effective. Even I shut down JBoss, machine, still I don't see the new changes made to Bean. I deleted entire tmp folder. NO success. I don't think there any references kept open to Bean since I am running simple test client program. Thanks. Do You Yahoo!? Find a job, post your resume on
[JBoss-user] Browsing JNDI Provider (JNP) via NetBeans
Title: Browsing JNDI Provider (JNP) via NetBeans Has anyone been able to browser the JBoss directory through NetBeans and have a suggestion for what I'm missing? I added jnp-client.jar to the lib/ext for netbeans and configured the provider; at least it tells me it's defined. When I try to connect a node is created to browse but nothing shows up when I expand the structure, I just get a folder with a red x box. If I give a bogus context it complains instead of creating a node to browser from so I believe it is connecting correctly. * Using the JNDIViewer I can see that my beans are deployed and in the structure where I am looking for them. * The sun provider works for other applications in the past. Using the New JNDI Context I enter the following: Context Label: customer JNDI Context Factory: org.jnp.interfaces.NamingContextFactory JNDI Initial Context: localhost:1099 (also tried jnp://localhost:1099 with the same results) Context Root: customer Other Properties: java.naming.factory.url.pkgs=org.jboss.naming the JNDIViewer shows +-customer +-- Account Thanks, John Moore
Re: [JBoss-user] How to deploy webclient in JBoss_Tomcat
Hi Kiran, I have been working with JBoss for a while and as a matter of fact, I have written a guide to programming J2EE apps using JBoss. If you want you can grab it a copy the document and the software (a forum system) at: http://devraj.org/projects/freeforums/ I also delivered a lecture on programming with J2EE at Charles Sturt University Australia and am hoping to make a copy of that online in a few days. Hope this helps. Devraj At 10:03 AM 11/3/2001 +0530, you wrote: Hello Everybody, I am new to Jboss tomcat server (JBoss-2.4.3_Tomcat3.2.3)...i hv just executed the given example in the documentation (ie.interest example). i am facing problems in executing webclient verstion of that..can u please tell me the deployment procedure, how to deploy a war/ear file in the server. I am very thank full to you if any one can help me in this... I am also strugling a lot to understand build.xml in the example..is there any easy way to understand how to use Ant (like writing build.xml, jaws.xml and ejb-jar.xml etc) ? Thanks in advance Kiran.
[JBoss-user] Reconecting to DB Server
Hi all, I have a DB Server runing Oracle 8i and 2 Jboss servers. All is working ok wit connection pool. If I need to restart the oracle server the jboss connection pols are stoping to work. Where is the problem? Exist any method (or config option) to reconnect this jboss pools? I can not restart any time the 2 jboss servers after restarting oracle server. Many thanks in advance. _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
