[JBoss-dev] Destroying cmp BEAN instances
Title: Nachricht Hello, may somebody tell me, how i can force the container of the app server to destroy some instances of cmp beans? (Sorry, if this question is foolish, but I'm new in developing with EJBs and JBOSS) thanx bjoern
[JBoss-dev] [ jboss-Bugs-504827 ] Example in the doc not comform to DTD
Bugs item #504827, was opened at 2002-01-17 04:00 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=504827group_id=22866 Category: CatalinaBundle Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Guillaume Coté (gcote) Assigned to: Scott M Stark (starksm) Summary: Example in the doc not comform to DTD Initial Comment: I download the last version of the doc on flashline. If you take page the DTD for the jboss.jcml file (figure 2-3 page 40), it says that only a attribute can contain a config tag. If you look to example on page 316 and 318, thay put the config tag in the mbean tag, not in a attribute tag. (BTW, I haven't succeded in stating a warp connector using either syntax. If anyway can point me where is the source code for that config thing, so I can read it directly). -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=504827group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-502025 ] JBoss fail to start
Bugs item #502025, was opened at 2002-01-10 12:37 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=502025group_id=22866 Category: JBossServer Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ronan-Yann Lorin (ryl) Assigned to: Nobody/Anonymous (nobody) Summary: JBoss fail to start Initial Comment: It appears that when an XA/JDBC connection can't be established at startup, the server hang and never starts. I guess this is due to a connection test just atfer binding the name in JNDI. Code looks like that: datasource.getConnection().close(); It seems that the exception is not correctly catched. -- Comment By: Ronan-Yann Lorin (ryl) Date: 2002-01-17 05:18 Message: Logged In: YES user_id=74340 You're right. Adding attribute name=BlockingTimeout1/attribute to the confing file, JBoss will be able to start after a timeout of 10 secs and throwning an exception. -- Comment By: David Jencks (d_jencks) Date: 2002-01-10 14:30 Message: Logged In: YES user_id=60525 Is this line of code actually throwing an exception? Normally it does not, it just hangs. Set BlockingTimeout to a nonzero value and you will get an exception instead. Blocking timeout is nonzero by default in jboss 3. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=502025group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-504481 ] INSERTING AN ALREADY EXISTING BEAN
Bugs item #504481, was opened at 2002-01-16 08:58 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=504481group_id=22866 Category: JBossCMP Group: v2.4 (stable) Status: Open Resolution: None Priority: 9 Submitted By: Shravan (cskreddy74) Assigned to: Bill Burke (patriot1burke) Summary: INSERTING AN ALREADY EXISTING BEAN Initial Comment: Hi, I get this error ehen I am trying to insert the record into the database form the bean, basically I deleted the record from the database manually and tried to insert it from the bean, I read the article from the previous postings, but could not figure out how it works.. please have a look at the smalll code of the CMP bean which is attached as .zip files and help me . javax.transaction.TransactionRolledbackException: INSERTING AN ALREADY EXISTING BEAN, ID = 1; nested exception is: java.lang.IllegalStateException: INSERTING AN ALREADY EXISTING BEAN, ID = 1 Thanks in advance Shravan -- Comment By: Shravan (cskreddy74) Date: 2002-01-17 06:38 Message: Logged In: YES user_id=260502 hi patriot1burke, I have a scenario wherein my database is accessed from an legacy system or from an other no-java application which is updating hte database constantly and when data is changed in database how do I make to reflect in the jboss server automatically... I mean atleast how to reduce teh cache time or how to disable the caching etc. -- Comment By: Bill Burke (patriot1burke) Date: 2002-01-16 12:49 Message: Logged In: YES user_id=176497 If you create a bean through EJB, then delete it manually from the database, then try to create it again you will fail in this way because JBoss still has the bean in cache. I'm closing this bug. It is not a bug. You are using it incorrectly. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=504481group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Destroying cmp BEAN instances
Title: Nachricht You mean clear the cache? The caches are not exposed through mbeans, so there is no way to do this. Please log a feature request at sourceforge -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Björn BlumSent: Thursday, January 17, 2002 3:51 AMTo: JBOSS DEVSubject: [JBoss-dev] Destroying cmp BEAN instances Hello, may somebody tell me, how i can force the container of the app server to destroy some instances of cmp beans? (Sorry, if this question is foolish, but I'm new in developing with EJBs and JBOSS) thanx bjoern
RE: [JBoss-dev] Destroying cmp BEAN instances
Title: Nachricht Bill didn't you say you wanted to tackle that problem? Seems like I won't be able to finish the deployer so you have 10 days :) marcf -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Bill BurkeSent: Thursday, January 17, 2002 7:08 AMTo: 'Björn Blum'; 'JBOSS DEV'Subject: RE: [JBoss-dev] Destroying cmp BEAN instances You mean clear the cache? The caches are not exposed through mbeans, so there is no way to do this. Please log a feature request at sourceforge -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Björn BlumSent: Thursday, January 17, 2002 3:51 AMTo: JBOSS DEVSubject: [JBoss-dev] Destroying cmp BEAN instances Hello, may somebody tell me, how i can force the container of the app server to destroy some instances of cmp beans? (Sorry, if this question is foolish, but I'm new in developing with EJBs and JBOSS) thanx bjoern
RE: [JBoss-dev] out of memory
Colin. Christian Riege found the problem.
-Original Message-
From: Colin Daly [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 09, 2002 9:16 PM
To: Bill Burke; [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] out of memory
Hi Bill,
thank you for the quick response.
to answer your question, i'm not
doing the import within one transaction.
the client repeatedly calls the createTestAddress
method on the stateless session bean.
i reduced the entity cache size from 1000 to 10
and confirmed that the problem remained.
i've noticed that if i remove the address entity
after creation by adding
addressEJB.remove();
to the end of createTestAddress, the problem
disappears. This is consistent with what you
said about the locks remaining while the entity
remained cached.
My question then is, if I don't call remove on
the entity bean, how do the beans ever get
removed from the cache.
/**
* @ejb:interface-method
*/
public void createTestAddress() throws RemoteException
{
try {
AddressModel address = new AddressModel(new
AddressEJBData(null,
line1, line2, false, suburb, state, postcode, country));
AddressEJBLocal addressEJB =
createAddress(address);
} catch (Exception e) {
throw new RemoteException(error creating test
address, e);
}
}
private AddressEJBLocal createAddress(AddressModel
theAddressModel)
throws NamingException, CreateException, SQLException
{
AddressEJBLocal address =
AddressEJBUtil.getLocalHome().create(
theAddressModel.getLine1(),
theAddressModel.getLine2(),
theAddressModel.getPOBox(), theAddressModel.getSuburb(),
theAddressModel.getState(), theAddressModel.getPostcode(),
theAddressModel.getCountry());
return address;
}
Colin.
On Wed, 9 Jan 2002 10:52, you wrote:
The locks will stay in memory as long as the EntityBean is
cached. How
many Entity Beans are you querying and loading up? Make
sure you're not
doing this in one transaction. Also, Remember. Stateless
bean methods are
Required by default. If you do your sucking your
Entities within a
Stateless bean call, you may be overloading it. Can you
send me the test
case creates this problem?
- Original Message -
From: Colin Daly [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, January 09, 2002 12:41 AM
Subject: [JBoss-dev] out of memory
Hi all,
we are running JBoss-2.4.4_Tomcat-4.0.1-beta/jboss
with version 1.0 of the persistence manager from MVCSoft.
after experiencing OutOfMemory problems with a batch
program which sucks data out of a legacy database and
into postgresql through the EJB layer, i ran up Optimizeit
and discovered that the source of the leak is instances
of the following class are never getting garbage collected.
org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock
I wrote a simple test client which just repeatedly called a
stateless session bean method called createAddress which
creates a simple cmp (no cmr) entity bean. The same
problem occurred. Please refer to the attached file (data.txt)
for the allocation backtrace of
org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock
in this simple test.
I've tried debugging this but to be perfectly honest I'm
a little out of my depth here. It appears the reference
counts for the locks never reaches zero and therefore
the removeLockRef in the BeanLockManager never
actually removes the lock from the map.
If anyone can help me on this, I would really appreciate
it. I'm not quite sure what to do next. Any suggestions
would be great.
regards,
Colin Daly.
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-504827 ] Example in the doc not comform to DTD
Bugs item #504827, was opened at 2002-01-17 04:00 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=504827group_id=22866 Category: CatalinaBundle Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Guillaume Coté (gcote) Assigned to: Scott M Stark (starksm) Summary: Example in the doc not comform to DTD Initial Comment: I download the last version of the doc on flashline. If you take page the DTD for the jboss.jcml file (figure 2-3 page 40), it says that only a attribute can contain a config tag. If you look to example on page 316 and 318, thay put the config tag in the mbean tag, not in a attribute tag. (BTW, I haven't succeded in stating a warp connector using either syntax. If anyway can point me where is the source code for that config thing, so I can read it directly). -- Comment By: Guillaume Coté (gcote) Date: 2002-01-17 06:40 Message: Logged In: YES user_id=15328 After futher testing, I got the following working in 2.4.4 (but not in 2.4.3) mbean code=org.jboss.web.catalina.EmbeddedCatalinaServiceSX name=DefaultDomain:service=EmbeddedTomcat attribute name=Config Connector className=org.apache.catalina.connector.warp.WarpConnector port=8008 minProcessors=5 maxProcessors=75 enableLookups=true acceptCount=10 debug=0/ /attribute /mbean Source code seem to be in org.jboss.configuration.ConfigurationService, there is no occurence of child in that file. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=504827group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-504481 ] INSERTING AN ALREADY EXISTING BEAN
Bugs item #504481, was opened at 2002-01-16 08:58 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=504481group_id=22866 Category: JBossCMP Group: v2.4 (stable) Status: Closed Resolution: None Priority: 9 Submitted By: Shravan (cskreddy74) Assigned to: Andreas Schaefer (schaefera) Summary: INSERTING AN ALREADY EXISTING BEAN Initial Comment: Hi, I get this error ehen I am trying to insert the record into the database form the bean, basically I deleted the record from the database manually and tried to insert it from the bean, I read the article from the previous postings, but could not figure out how it works.. please have a look at the smalll code of the CMP bean which is attached as .zip files and help me . javax.transaction.TransactionRolledbackException: INSERTING AN ALREADY EXISTING BEAN, ID = 1; nested exception is: java.lang.IllegalStateException: INSERTING AN ALREADY EXISTING BEAN, ID = 1 Thanks in advance Shravan -- Comment By: Bill Burke (patriot1burke) Date: 2002-01-16 12:49 Message: Logged In: YES user_id=176497 If you create a bean through EJB, then delete it manually from the database, then try to create it again you will fail in this way because JBoss still has the bean in cache. I'm closing this bug. It is not a bug. You are using it incorrectly. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=504481group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-504481 ] INSERTING AN ALREADY EXISTING BEAN
Bugs item #504481, was opened at 2002-01-16 08:58 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=504481group_id=22866 Category: JBossCMP Group: v2.4 (stable) Status: Closed Resolution: None Priority: 9 Submitted By: Shravan (cskreddy74) Assigned to: Andreas Schaefer (schaefera) Summary: INSERTING AN ALREADY EXISTING BEAN Initial Comment: Hi, I get this error ehen I am trying to insert the record into the database form the bean, basically I deleted the record from the database manually and tried to insert it from the bean, I read the article from the previous postings, but could not figure out how it works.. please have a look at the smalll code of the CMP bean which is attached as .zip files and help me . javax.transaction.TransactionRolledbackException: INSERTING AN ALREADY EXISTING BEAN, ID = 1; nested exception is: java.lang.IllegalStateException: INSERTING AN ALREADY EXISTING BEAN, ID = 1 Thanks in advance Shravan -- Comment By: Shravan (cskreddy74) Date: 2002-01-17 06:38 Message: Logged In: YES user_id=260502 hi patriot1burke, I have a scenario wherein my database is accessed from an legacy system or from an other no-java application which is updating hte database constantly and when data is changed in database how do I make to reflect in the jboss server automatically... I mean atleast how to reduce teh cache time or how to disable the caching etc. -- Comment By: Bill Burke (patriot1burke) Date: 2002-01-16 12:49 Message: Logged In: YES user_id=176497 If you create a bean through EJB, then delete it manually from the database, then try to create it again you will fail in this way because JBoss still has the bean in cache. I'm closing this bug. It is not a bug. You are using it incorrectly. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=504481group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-504481 ] INSERTING AN ALREADY EXISTING BEAN
Bugs item #504481, was opened at 2002-01-16 08:58 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=504481group_id=22866 Category: JBossCMP Group: v2.4 (stable) Status: Closed Resolution: Invalid Priority: 9 Submitted By: Shravan (cskreddy74) Assigned to: Bill Burke (patriot1burke) Summary: INSERTING AN ALREADY EXISTING BEAN Initial Comment: Hi, I get this error ehen I am trying to insert the record into the database form the bean, basically I deleted the record from the database manually and tried to insert it from the bean, I read the article from the previous postings, but could not figure out how it works.. please have a look at the smalll code of the CMP bean which is attached as .zip files and help me . javax.transaction.TransactionRolledbackException: INSERTING AN ALREADY EXISTING BEAN, ID = 1; nested exception is: java.lang.IllegalStateException: INSERTING AN ALREADY EXISTING BEAN, ID = 1 Thanks in advance Shravan -- Comment By: Christian Riege (lqd) Date: 2002-01-17 07:15 Message: Logged In: YES user_id=176671 this is not a bug, CLOSING INVALID. Using commit-option C does the job. -- Comment By: Bill Burke (patriot1burke) Date: 2002-01-17 07:04 Message: Logged In: YES user_id=176497 I think using commit option 'C' will work. Look in standardjboss.xml for commit-option it is 'A' by default. Commit option 'C' will passivate the Entity Bean at the end of every transaction. -- Comment By: Shravan (cskreddy74) Date: 2002-01-17 06:38 Message: Logged In: YES user_id=260502 hi patriot1burke, I have a scenario wherein my database is accessed from an legacy system or from an other no-java application which is updating hte database constantly and when data is changed in database how do I make to reflect in the jboss server automatically... I mean atleast how to reduce teh cache time or how to disable the caching etc. -- Comment By: Bill Burke (patriot1burke) Date: 2002-01-16 12:49 Message: Logged In: YES user_id=176497 If you create a bean through EJB, then delete it manually from the database, then try to create it again you will fail in this way because JBoss still has the bean in cache. I'm closing this bug. It is not a bug. You are using it incorrectly. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=504481group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/main/org/jboss/ejb/plugins/cmp/jdbc/ejbql EJBQLParser.java
User: dsundstrom
Date: 02/01/17 08:46:31
Modified:src/main/org/jboss/ejb/plugins/cmp/jdbc/ejbql
EJBQLParser.java
Log:
Changed the location function optional third parameter default to 1.
Revision ChangesPath
1.9 +1 -1
jboss/src/main/org/jboss/ejb/plugins/cmp/jdbc/ejbql/EJBQLParser.java
Index: EJBQLParser.java
===
RCS file:
/cvsroot/jboss/jboss/src/main/org/jboss/ejb/plugins/cmp/jdbc/ejbql/EJBQLParser.java,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- EJBQLParser.java 2001/11/13 22:26:25 1.8
+++ EJBQLParser.java 2002/01/17 16:46:31 1.9
@@ -919,7 +919,7 @@
if(param1.equalsIgnoreCase(LOCATE)) {
param1 = param2;
param2 = param3;
- param3 = 0;
+ param3 = 1;
} else {
a.pop(); // pop the token LOCATE
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-504481 ] INSERTING AN ALREADY EXISTING BEAN
Bugs item #504481, was opened at 2002-01-16 08:58 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=504481group_id=22866 Category: JBossCMP Group: v2.4 (stable) Status: Open Resolution: None Priority: 9 Submitted By: Shravan (cskreddy74) Assigned to: Bill Burke (patriot1burke) Summary: INSERTING AN ALREADY EXISTING BEAN Initial Comment: Hi, I get this error ehen I am trying to insert the record into the database form the bean, basically I deleted the record from the database manually and tried to insert it from the bean, I read the article from the previous postings, but could not figure out how it works.. please have a look at the smalll code of the CMP bean which is attached as .zip files and help me . javax.transaction.TransactionRolledbackException: INSERTING AN ALREADY EXISTING BEAN, ID = 1; nested exception is: java.lang.IllegalStateException: INSERTING AN ALREADY EXISTING BEAN, ID = 1 Thanks in advance Shravan -- Comment By: Bill Burke (patriot1burke) Date: 2002-01-17 07:04 Message: Logged In: YES user_id=176497 I think using commit option 'C' will work. Look in standardjboss.xml for commit-option it is 'A' by default. Commit option 'C' will passivate the Entity Bean at the end of every transaction. -- Comment By: Shravan (cskreddy74) Date: 2002-01-17 06:38 Message: Logged In: YES user_id=260502 hi patriot1burke, I have a scenario wherein my database is accessed from an legacy system or from an other no-java application which is updating hte database constantly and when data is changed in database how do I make to reflect in the jboss server automatically... I mean atleast how to reduce teh cache time or how to disable the caching etc. -- Comment By: Bill Burke (patriot1burke) Date: 2002-01-16 12:49 Message: Logged In: YES user_id=176497 If you create a bean through EJB, then delete it manually from the database, then try to create it again you will fail in this way because JBoss still has the bean in cache. I'm closing this bug. It is not a bug. You are using it incorrectly. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=504481group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-504895 ] missing removal of lock on Entity Beans
Bugs item #504895, was opened at 2002-01-17 07:12 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=504895group_id=22866 Category: JBossCMP Group: v2.4 (stable) Status: Open Resolution: None Priority: 7 Submitted By: Christian Riege (lqd) Assigned to: Bill Burke (patriot1burke) Summary: missing removal of lock on Entity Beans Initial Comment: hi, short: JBoss eats my memory :) long: there is a problem with the caching/locking of Entity Beans. It seems that the passivation of an Entity Bean does not call removeRef() on the BeanLockManager thus holding the object permanently in the cache. If I call a 'remove()' on my Entity Bean, everything is OK and the entry is removed from the Cache, but passivation fails to do this thus making the cache grow over time. -- Comment By: Christian Riege (lqd) Date: 2002-01-17 07:35 Message: Logged In: YES user_id=176671 i think we've got the bug, its in AbstractInstanceCache. patch is attached, we're testing this right now ... -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=504895group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-504895 ] missing removal of lock on Entity Beans
Bugs item #504895, was opened at 2002-01-17 07:12 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=504895group_id=22866 Category: JBossCMP Group: v2.4 (stable) Status: Open Resolution: None Priority: 7 Submitted By: Christian Riege (lqd) Assigned to: Bill Burke (patriot1burke) Summary: missing removal of lock on Entity Beans Initial Comment: hi, short: JBoss eats my memory :) long: there is a problem with the caching/locking of Entity Beans. It seems that the passivation of an Entity Bean does not call removeRef() on the BeanLockManager thus holding the object permanently in the cache. If I call a 'remove()' on my Entity Bean, everything is OK and the entry is removed from the Cache, but passivation fails to do this thus making the cache grow over time. -- Comment By: Christian Riege (lqd) Date: 2002-01-17 07:35 Message: Logged In: YES user_id=176671 i think we've got the bug, its in AbstractInstanceCache. patch is attached, we're testing this right now ... -- Comment By: Christian Riege (lqd) Date: 2002-01-17 07:35 Message: Logged In: YES user_id=176671 i think we've got the bug, its in AbstractInstanceCache. patch is attached, we're testing this right now ... -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=504895group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-504895 ] missing removal of lock on Entity Beans
Bugs item #504895, was opened at 2002-01-17 07:12 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=504895group_id=22866 Category: JBossCMP Group: v2.4 (stable) Status: Open Resolution: None Priority: 7 Submitted By: Christian Riege (lqd) Assigned to: Bill Burke (patriot1burke) Summary: missing removal of lock on Entity Beans Initial Comment: hi, short: JBoss eats my memory :) long: there is a problem with the caching/locking of Entity Beans. It seems that the passivation of an Entity Bean does not call removeRef() on the BeanLockManager thus holding the object permanently in the cache. If I call a 'remove()' on my Entity Bean, everything is OK and the entry is removed from the Cache, but passivation fails to do this thus making the cache grow over time. -- Comment By: Bill Burke (patriot1burke) Date: 2002-01-17 07:44 Message: Logged In: YES user_id=176497 Are you commiting this bug, or should I? Thanks for finding this. -- Comment By: Christian Riege (lqd) Date: 2002-01-17 07:35 Message: Logged In: YES user_id=176671 i think we've got the bug, its in AbstractInstanceCache. patch is attached, we're testing this right now ... -- Comment By: Christian Riege (lqd) Date: 2002-01-17 07:35 Message: Logged In: YES user_id=176671 i think we've got the bug, its in AbstractInstanceCache. patch is attached, we're testing this right now ... -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=504895group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-504895 ] missing removal of lock on Entity Beans
Bugs item #504895, was opened at 2002-01-17 07:12 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=504895group_id=22866 Category: JBossCMP Group: v2.4 (stable) Status: Open Resolution: None Priority: 7 Submitted By: Christian Riege (lqd) Assigned to: Bill Burke (patriot1burke) Summary: missing removal of lock on Entity Beans Initial Comment: hi, short: JBoss eats my memory :) long: there is a problem with the caching/locking of Entity Beans. It seems that the passivation of an Entity Bean does not call removeRef() on the BeanLockManager thus holding the object permanently in the cache. If I call a 'remove()' on my Entity Bean, everything is OK and the entry is removed from the Cache, but passivation fails to do this thus making the cache grow over time. -- Comment By: Christian Riege (lqd) Date: 2002-01-17 08:03 Message: Logged In: YES user_id=176671 attached patch fails; the removal of the lock has to be done later (in the PassivationJob). We have another fix in hand, testing this right now. [deleting attached patch] -- Comment By: Bill Burke (patriot1burke) Date: 2002-01-17 07:44 Message: Logged In: YES user_id=176497 Are you commiting this bug, or should I? Thanks for finding this. -- Comment By: Christian Riege (lqd) Date: 2002-01-17 07:35 Message: Logged In: YES user_id=176671 i think we've got the bug, its in AbstractInstanceCache. patch is attached, we're testing this right now ... -- Comment By: Christian Riege (lqd) Date: 2002-01-17 07:35 Message: Logged In: YES user_id=176671 i think we've got the bug, its in AbstractInstanceCache. patch is attached, we're testing this right now ... -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=504895group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/main/org/jboss/ejb/plugins/jms JMSContainerInvoker.java
User: chirino
Date: 02/01/17 09:18:31
Modified:src/main/org/jboss/ejb/plugins/jms JMSContainerInvoker.java
Log:
Enhanced so that the MDB deploys even if the JMS provider is not running
when it gets deployed. It will jump into recovery thread that trys to re-establish
it's connection to the JMS provider.
Revision ChangesPath
1.42 +34 -10
jboss/src/main/org/jboss/ejb/plugins/jms/JMSContainerInvoker.java
Index: JMSContainerInvoker.java
===
RCS file:
/cvsroot/jboss/jboss/src/main/org/jboss/ejb/plugins/jms/JMSContainerInvoker.java,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -r1.41 -r1.42
--- JMSContainerInvoker.java 2002/01/08 22:27:15 1.41
+++ JMSContainerInvoker.java 2002/01/17 17:18:30 1.42
@@ -56,7 +56,7 @@
* /a
* @authora href=mailto:[EMAIL PROTECTED];Marc Fleury/a
* @authora href=mailto:[EMAIL PROTECTED];Jason Dillon/a
- * @version $Revision: 1.41 $
+ * @version $Revision: 1.42 $
*/
public class JMSContainerInvoker
implements ContainerInvoker, XmlLoadable
@@ -399,6 +399,29 @@
serverSessionPoolFactoryJNDI = java:/ + serverSessionPoolFactoryJNDI;
}
}
+
+ /**
+* Initialize the container invoker. Sets up a connection, a server session
+* pool and a connection consumer for the configured destination.
+*
+* Any JMSExceptions produced while initializing will be assumed to be
+* caused due to JMS Provider failure.
+*
+* @throws Exception Failed to initalize.
+*/
+ public void create() throws Exception {
+ exListener = new ExceptionListenerImpl(this);
+ try {
+ innerCreate();
+ } catch ( final JMSException e ) {
+ // start a thread up to handle recovering the connection.
+ new Thread() {
+ public void run() {
+ exListener.onException(e);
+ }
+ }.start();
+ }
+ }
/**
* Initialize the container invoker. Sets up a connection, a server session
@@ -406,7 +429,7 @@
*
* @throws Exception Failed to initalize.
*/
- public void create() throws Exception
+ public void innerCreate() throws Exception
{
boolean debug = log.isDebugEnabled();
@@ -631,9 +654,10 @@
{
if (log.isDebugEnabled())
log.debug(Starting JMSContainerInvoker for bean + beanName);
- exListener = new ExceptionListenerImpl(this);
- connection.setExceptionListener(exListener);
- connection.start();
+ if( connection != null ) {
+ connection.setExceptionListener(exListener);
+ connection.start();
+ }
}
/**
@@ -1010,11 +1034,11 @@
{
currentThread = Thread.currentThread();
- log.warn(MDB lost connection to provider, ex);
+ log.warn(JMS provider failure detected: , ex);
boolean tryIt = true;
while (tryIt notStoped)
{
-log.info(MDB Trying to reconnect...);
+log.info(Trying to reconnect to JMS provider);
try
{
try
@@ -1030,14 +1054,14 @@
// Reboot container
invoker.innerStop();
invoker.destroy();
- invoker.create();
+ invoker.innerCreate();
invoker.start();
tryIt = false;
- log.info(OK - reconnected);
+ log.info(Reconnected to JMS provider);
}
catch (Exception e)
{
- log.error(MDB error reconnecting, e);
+ log.error(Reconnect failed: JMS provider failure detected:, e);
}
}
currentThread = null;
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/main/org/jboss/ejb/plugins AbstractInstanceCache.java
User: lqd
Date: 02/01/17 09:39:35
Modified:src/main/org/jboss/ejb/plugins Tag: Branch_2_4
AbstractInstanceCache.java
Log:
fix for SF bug #504895: removeLockRef() is not called when release()-ing
the bean
Revision ChangesPath
No revision
No revision
1.10.2.7 +5 -1 jboss/src/main/org/jboss/ejb/plugins/AbstractInstanceCache.java
Index: AbstractInstanceCache.java
===
RCS file:
/cvsroot/jboss/jboss/src/main/org/jboss/ejb/plugins/AbstractInstanceCache.java,v
retrieving revision 1.10.2.6
retrieving revision 1.10.2.7
diff -u -r1.10.2.6 -r1.10.2.7
--- AbstractInstanceCache.java2001/12/03 21:47:55 1.10.2.6
+++ AbstractInstanceCache.java2002/01/17 17:39:35 1.10.2.7
@@ -64,7 +64,7 @@
* @author a href=[EMAIL PROTECTED]Marc Fleury/a
* @author a href=[EMAIL PROTECTED]Scott Stark/a
*
- * @version $Revision: 1.10.2.6 $
+ * @version $Revision: 1.10.2.7 $
*
* pbRevisions:/b
*
@@ -287,6 +287,7 @@
if (getCache().peek(id) != null)
{
getCache().remove(id);
+getContainer().getLockManager().removeLockRef(id);
}
// This call, executed anyway, leaves door open to multiple scheduling
// of the same context, which I take care in other places, in
@@ -890,3 +891,6 @@
return m_executed;
}
}
+/*
+vim:tabstop=3:expandtab:shiftwidth=3
+*/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Destroying cmp BEAN instances
Title: Message forums WILL be back online, we have a machine at DenverOnline that will take care of static website, and we are getting a machine at Rackspace that will do nothing but forums on RAID 1 and all. We are getting the machine tomorrow, I will try to salvage the data from the forums. the new installation is fully redundant with DAT tape rotation taken care of by rackspace etc etc, I will let you know on the data restoring as soon as I know marcf -Original Message-From: Vincent Harcq [mailto:[EMAIL PROTECTED]]Sent: Thursday, January 17, 2002 9:38 AMTo: 'marc fleury'; [EMAIL PROTECTED]; 'Björn Blum'; 'JBOSS DEV'Subject: RE: [JBoss-dev] Destroying cmp BEAN instances As somebody point me on (defunct) Forums, calling a methodthat simply throws an RunTimeException should unvalidate the CMP Bean. spec cersion="2.0" chapter="18.6" In EJB 2.0 and 1.1, all non-application exceptions thrown by the instance result in the rollback of the transaction in which the instance executed, and in discarding the instance. /spec Having an MBean could be simpler anyway. With that feature inside the container, would you find useful to have something like invalidation-target a la Seppuku ?https://sourceforge.net/tracker/?func=detailaid=502757group_id=22866atid=376688 Vincent -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of marc fleurySent: jeudi 17 janvier 2002 19:16To: [EMAIL PROTECTED]; 'Björn Blum'; 'JBOSS DEV'Subject: RE: [JBoss-dev] Destroying cmp BEAN instances Bill didn't you say you wanted to tackle that problem? Seems like I won't be able to finish the deployer so you have 10 days :) marcf -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Bill BurkeSent: Thursday, January 17, 2002 7:08 AMTo: 'Björn Blum'; 'JBOSS DEV'Subject: RE: [JBoss-dev] Destroying cmp BEAN instances You mean clear the cache? The caches are not exposed through mbeans, so there is no way to do this. Please log a feature request at sourceforge -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Björn BlumSent: Thursday, January 17, 2002 3:51 AMTo: JBOSS DEVSubject: [JBoss-dev] Destroying cmp BEAN instances Hello, may somebody tell me, how i can force the container of the app server to destroy some instances of cmp beans? (Sorry, if this question is foolish, but I'm new in developing with EJBs and JBOSS) thanx bjoern
[JBoss-dev] [ jboss-Bugs-504625 ] Generation of SQL for Locate() incorrect
Bugs item #504625, was opened at 2002-01-16 14:03 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=504625group_id=22866 Category: JBossCMP Group: v3.0 Rabbit Hole Status: Closed Resolution: Fixed Priority: 5 Submitted By: Basil Vandegriend (basilv) Assigned to: Dain Sundstrom (dsundstrom) Summary: Generation of SQL for Locate() incorrect Initial Comment: The SQL generated from EJB-QL with a Locate() statement is incorrect. In particular, if the 3rd argument (start position) is not specified, JBoss supplies a default of '0'. However, I believe that a default of '1' is actually correct. While the EJB spec does not specify the behavior of the Locate() function, a footnote references Appendix A in the book JDBC API Tutorial and Reference, 2nd edition. In this book, the behavior of Locate() is described as being based on an one-based index. As further evidence, in running the query on a Oracle 8i database, the default value of '0' for the start position did not work, while a value of '1' did work. Here are some details: EJB-QL statement: ![CDATA[SELECT OBJECT(c) FROM Customer AS c WHERE LOCATE(c.firstName, ?1) 0]] -- Generated SQL (from server log file) (using the Oracle8 type mapping): Executing SQL: SELECT t1_c.ID FROM ex2Customer t1_c WHERE instr(t1_c.firstName, ?, 0) 0 Version information (from server log file): 2002-01-16 14:45:42,431 INFO [org.jboss.system.GPA] Java version: 1.3.1,Sun Microsystems Inc. 2002-01-16 14:45:42,431 INFO [org.jboss.system.GPA] Java VM: Java HotSpot(TM) Client VM 1.3.1-b24,Sun Microsystems Inc. 2002-01-16 14:45:42,441 INFO [org.jboss.system.GPA] OS-System: Windows NT 4.0,x86 2002-01-16 14:45:42,441 INFO [org.jboss.system.GPA] JBoss Version: 3.0.0alpha(200112121023) Attached is the JBoss server log showing the SQL generation resulting from attempting to execute the find method with the EJB-QL shown above. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=504625group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Destroying cmp BEAN instances
Title: Message As somebody point me on (defunct) Forums, calling a methodthat simply throws an RunTimeException should unvalidate the CMP Bean. spec cersion="2.0" chapter="18.6" In EJB 2.0 and 1.1, all non-application exceptions thrown by the instance result in the rollback of the transaction in which the instance executed, and in discarding the instance. /spec Having an MBean could be simpler anyway. With that feature inside the container, would you find useful to have something like invalidation-target a la Seppuku ?https://sourceforge.net/tracker/?func=detailaid=502757group_id=22866atid=376688 Vincent -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of marc fleurySent: jeudi 17 janvier 2002 19:16To: [EMAIL PROTECTED]; 'Björn Blum'; 'JBOSS DEV'Subject: RE: [JBoss-dev] Destroying cmp BEAN instances Bill didn't you say you wanted to tackle that problem? Seems like I won't be able to finish the deployer so you have 10 days :) marcf -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Bill BurkeSent: Thursday, January 17, 2002 7:08 AMTo: 'Björn Blum'; 'JBOSS DEV'Subject: RE: [JBoss-dev] Destroying cmp BEAN instances You mean clear the cache? The caches are not exposed through mbeans, so there is no way to do this. Please log a feature request at sourceforge -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Björn BlumSent: Thursday, January 17, 2002 3:51 AMTo: JBOSS DEVSubject: [JBoss-dev] Destroying cmp BEAN instances Hello, may somebody tell me, how i can force the container of the app server to destroy some instances of cmp beans? (Sorry, if this question is foolish, but I'm new in developing with EJBs and JBOSS) thanx bjoern
[JBoss-dev] More relationship stuff
I've pulled the latest jboss head and I am testing a 1-1 uni directional
relationship. The database tables are already created. So I have
create table test_cust (
test_cust_id int PRIMARY KEY,
billing_address_id int
);
create table test_address (
test_address_id int PRIMARY KEY,
an_address varchar(50)
);
So TestCust ..
TestCust {
AddressLocal getAddress();
void setAddress(AddressLocal l);
}
jbosscmp-jdbc.xml
sniped ..
ejb-relation
ejb-relation-nameUni_1_to_1/ejb-relation-name
foreign-key-mapping
ejb-relationship-role
ejb-relationship-role-nameCust_has_an_address/ejb-relationship-role-name
fk-constrainttrue/fk-constraint
foreign-key-fields
foreign-key-field
field-nametest_address_id/field-name
column-namebilling_address_id/column-name
/foreign-key-field
/foreign-key-fields
/ejb-relationship-role
ejb-relationship-role
ejb-relationship-role-nameAddr_has_no_idea_of_TestCust/ejb-relationship-role-name
/ejb-relationship-role
/foreign-key-mapping
/ejb-relation
So everything looks cool until it tries to add the address
INSERT INTO test_address (test_address_id, an_address, TestCust_address)
VALUES (?, ?, ?)
It looks like jboss is throwing in a CMR field even though it is only a
1-1 uni directional relationship.
Bug?
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Fwd: ScanMail Message: To Sender, sensitive content found andaction t aken.]
he, upon my last CVS commit (and the following e-mail by SF) I got the attached reply. who the fuck (!) are these clowns? sorry for the spam ;) christian ---BeginMessage--- Trend SMEX Content Filter has detected sensitive content. Place = [EMAIL PROTECTED]; ; Sender = Christian Riege Subject = [JBoss-dev] CVS update: jboss/src/main/org/jboss/ejb/plugins AbstractInstanceCache.java Delivery Time = January 17, 2002 (Thursday) 11:43:13 Policy = Anti-Spam Action on this mail = Quarantine message Warning message from administrator: Anti-Spam filter has blocked a junk mail! ---End Message---
RE: [JBoss-dev] More relationship stuff
Directionality of a relationship has nothing to do with fk mappings. The
reason you are getting FKs in your address table is because you did not tell
the engine to not create them. Add the following to the
Addr_has_no_idea_of_TestCust role:
foreign-key-fields/
-dain
-Original Message-
From: Dave Smith [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 17, 2002 1:08 PM
To: [EMAIL PROTECTED]
Subject: [JBoss-dev] More relationship stuff
I've pulled the latest jboss head and I am testing a 1-1 uni
directional
relationship. The database tables are already created. So I have
create table test_cust (
test_cust_id int PRIMARY KEY,
billing_address_id int
);
create table test_address (
test_address_id int PRIMARY KEY,
an_address varchar(50)
);
So TestCust ..
TestCust {
AddressLocal getAddress();
void setAddress(AddressLocal l);
}
jbosscmp-jdbc.xml
sniped ..
ejb-relation
ejb-relation-nameUni_1_to_1/ejb-relation-name
foreign-key-mapping
ejb-relationship-role
ejb-relationship-role-nameCust_has_an_address/ejb-relations
hip-role-name
fk-constrainttrue/fk-constraint
foreign-key-fields
foreign-key-field
field-nametest_address_id/field-name
column-namebilling_address_id/column-name
/foreign-key-field
/foreign-key-fields
/ejb-relationship-role
ejb-relationship-role
ejb-relationship-role-nameAddr_has_no_idea_of_TestCust/ejb-
relationship-role-name
/ejb-relationship-role
/foreign-key-mapping
/ejb-relation
So everything looks cool until it tries to add the address
INSERT INTO test_address (test_address_id, an_address,
TestCust_address)
VALUES (?, ?, ?)
It looks like jboss is throwing in a CMR field even though it
is only a
1-1 uni directional relationship.
Bug?
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Source code editors
Hi, I was just wondering if any of you guys have found any open source Java IDE that was worth using in developing Jboss. Emacs is too new for me. I can't stand vi because it beeps at me way too often. Forte CE is way too slow at start up and plus I wants us to create a new project. Any suggestions? Sincerely, - Khoa Do ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [Fwd: ScanMail Message: To Sender, sensitive content found and action t aken.]
Me to. Guess I said pulled? Christian Riege wrote: he, upon my last CVS commit (and the following e-mail by SF) I got the attached reply. who the fuck (!) are these clowns? sorry for the spam ;) christian Subject: ScanMail Message: To Sender, sensitive content found and action t aken. From: System Attendant [EMAIL PROTECTED] Date: Thu, 17 Jan 2002 11:43:15 -0600 To: 'Christian Riege' [EMAIL PROTECTED] Trend SMEX Content Filter has detected sensitive content. Place = [EMAIL PROTECTED]; ; Sender = Christian Riege Subject = [JBoss-dev] CVS update: jboss/src/main/org/jboss/ejb/plugins AbstractInstanceCache.java Delivery Time = January 17, 2002 (Thursday) 11:43:13 Policy = Anti-Spam Action on this mail = Quarantine message Warning message from administrator: Anti-Spam filter has blocked a junk mail! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Source code editors
Pico is a fairly easy editor to deal with, but it's assinine in its insertion of carriage returns willy-nilly, and that can get you in trouble. I haven't used Forte much...can't you edit individual files without starting a new project? I know you can in most commercial IDEs. At least, I've been able to do so with JBuilder and VisualAge. You have to fiddle with them if you want to compile under them, though...you're going to run into that with most IDEs. I guess if you're looking for a really plain editor, then use XEmacs or one of the other GUI Emcacs that have drop-down menus for most of the major keystroke combos. After a while, you get used to emacs. Really. :) -Original Message- From: Khoa Do [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 17, 2002 2:26 PM To: Jboss-Development@Lists. Sourceforge. Net Subject: [JBoss-dev] Source code editors Hi, I was just wondering if any of you guys have found any open source Java IDE that was worth using in developing Jboss. Emacs is too new for me. I can't stand vi because it beeps at me way too often. Forte CE is way too slow at start up and plus I wants us to create a new project. Any suggestions? Sincerely, - Khoa Do ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Source code editors
Thank you. I will try to give emacs a shot. It just that I can't get used to the having to type a control-XX to do something that I can do with a mouse. I use MS Visual studio a lot so I am used to the IDE and the project explorer with all the pretty objects and their graphical attributes. -Original Message- From: Rhett Aultman [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 17, 2002 11:39 AM To: Jboss-Development@Lists. Sourceforge. Net Subject: RE: [JBoss-dev] Source code editors Pico is a fairly easy editor to deal with, but it's assinine in its insertion of carriage returns willy-nilly, and that can get you in trouble. I haven't used Forte much...can't you edit individual files without starting a new project? I know you can in most commercial IDEs. At least, I've been able to do so with JBuilder and VisualAge. You have to fiddle with them if you want to compile under them, though...you're going to run into that with most IDEs. I guess if you're looking for a really plain editor, then use XEmacs or one of the other GUI Emcacs that have drop-down menus for most of the major keystroke combos. After a while, you get used to emacs. Really. :) ... ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-505029 ] WarpConnector isn't using the good dir
Bugs item #505029, was opened at 2002-01-17 11:17 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=505029group_id=22866 Category: CatalinaBundle Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Guillaume Coté (gcote) Assigned to: Scott M Stark (starksm) Summary: WarpConnector isn't using the good dir Initial Comment: I modify the mbean entry for Catalina in jboss.jcml so it looks like that : mbean code=org.jboss.web.catalina.EmbeddedCatalinaServiceSX name=DefaultDomain:service=EmbeddedTomcat attribute name=Config Connector className=org.apache.catalina.connector.warp.WarpConnector port=8008 minProcessors=5 maxProcessors=75 enableLookups=true acceptCount=10 debug=999/ /attribute /mbean It start a WarpConnector well, but when it received a request, he looks for the file in the $JBOSS/catalina/webapps instead of looking in the war. But request received directly in http from catalina are correctly processed from the war. I can get my application to work in I copy the content of the webapp in that directory (but I cannot do hot-deployement anymore), but not the JAAS. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=505029group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Training spots at Boston
Guys, we have 3 last minutes cancellations. We can still squeeze you in if any of you are interested in coming. Let us know marcf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Source code editors
Buy a MacOS X machine and run ProjectBuilder. Works really great for Java... An IDE that isn't obtrusive, highly customizable, with lots of keyboard shortcuts. From: Khoa Do [EMAIL PROTECTED] Date: Thu, 17 Jan 2002 12:04:34 -0800 To: 'Rhett Aultman' [EMAIL PROTECTED] Cc: Jboss-Development@Lists. Sourceforge. Net[EMAIL PROTECTED] Subject: RE: [JBoss-dev] Source code editors Thank you. I will try to give emacs a shot. It just that I can't get used to the having to type a control-XX to do something that I can do with a mouse. I use MS Visual studio a lot so I am used to the IDE and the project explorer with all the pretty objects and their graphical attributes. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Fwd: Re: The penny drops - JBoss Repository Selector
FYI I think jboss-dev is the most appropriate forum for this discussion. I will follow up with an answer to Adrian here. Regards, Ceki List-Id: Log4J Developers List log4j-dev.jakarta.apache.org Reply-To: Log4J Developers List [EMAIL PROTECTED] Delivered-To: mailing list [EMAIL PROTECTED] X-Originating-IP: [195.212.13.8] Reply-To: [EMAIL PROTECTED] From: Adrian Brock [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: The penny drops - JBoss Repository Selector Date: Thu, 17 Jan 2002 16:56:02 + X-OriginalArrivalTime: 17 Jan 2002 16:56:03.0039 (UTC) FILETIME=[D8CE06F0:01C19F77] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi Ceki, I'm trying to reduce the length of my posts, this one will probably break that rule :-( Re: Repositories I'll try explaining this from the beginning. We basically agree but I'm not getting my point across about multiple repositories. Maybe I'm missing one of your points as well? :-) First, here is what JBoss does at the moment. Nearly the first thing that happens is to deploy an MBean called Log4JService. This has the task of locating the property file and sets up the configureAndWatch. So we have one hierarchy for all logging. The problem we are trying to solve is what happens when something doesn't like the JBoss configuration and tries to reconfigure log4j. A related issue (not the original problem raised on log4j-user) is that a user wants to take a component that already does logging and put it in its own hierarchy/configuration. There are two types of deployment within JBoss. 1) A service, such as embedded Tomcat. These could provide an internal mechanism for configuring log4j, it maybe useful for them to run in a different hierarchy. 2) An application. This is the original problem. The application wants to have a completely separate hierarchy and configuration to JBoss. The easy solution is every time I see a new ClassLoader in the RepositorySelector, create a new LoggerRepository. The configuration will either be specified at deployment or I use a fallback configuration. When something tries to reconfigure log4j it will be playing in its own backyard so problem solved. :-) But there are 50+ services in the default configuration of JBoss. Probably only the Web Server may want to reconfigure. The rest just want to use the JBoss hierarchy and configuration. I would like to let them share the same repository rather than creating 50 watchdog threads. Now the extra complication I introduced. The deployer may want all their applications running in the repository/hierarchy, but not the JBoss one. Again it would be wasteful to create a repository for each application when they are all sharing. I am not saying this is what will happen. As you said each applcation may want to specify its own log4j.properties. In this case, they each get a repository. Am I on the right track, have I over complicated this? Maybe I'm concentrating too much on the 5% instead of the 95%? I'll pickup the how to specify the url/configurator problem once I've nailed the RepositorySelector. I know what the configuration is, it's just where to put it. JBoss.xml is one idea but that don't exist for for pure web-apps :-( Unrelated point: I spotted this in log4j-1.2alpha6 javadocs org.apache.log4j.varia.PriorityMatchFilter is deprecated to itself, recursive deprecation :-) Regards, Adrian ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Re: The penny drops - JBoss Repository Selector
The problem *I* am interested in solving is to let each application have in its own independent logging universe. I don't see a problem with JBoss components sharing one logging universe (that of JBoss). The case of Tomcat or any other servlet container is very interesting because the user's servlet code is part of the user's application. Consequently, servlets should log on the logging universe of larger application. With the Weblogic 6.1 classloading scheme, this is very easy to accomplish. In the Weblogic 6.1 classloader hierarchy EJBs have a classloader which is also the parent of the web-application (WAR) classloader. Thus, servlet code naturally log using the log4j classes loaded by the EJB classloader. In other words, one logging universe for the whole application. I am not familiar with JBoss way of organizing the classloader hierarchy although I would like to learn. Anyway, some entity has to know at some point in time which WAR is associated with which (EJB) JAR. That entity can easily set the oops... Jboss embeds the whole of Tomcat/Jetter/whatever. OK then how can the servlets in an application access the *local* interface of entity beans? Do you know what I am talking about? Has this issue been addressed in JBoss 3.0? Regards, Ceki At 16:56 17.01.2002 +, Adrian Brock [EMAIL PROTECTED] wrote: Hi Ceki, I'm trying to reduce the length of my posts, this one will probably break that rule :-( Re: Repositories I'll try explaining this from the beginning. We basically agree but I'm not getting my point across about multiple repositories. Maybe I'm missing one of your points as well? :-) First, here is what JBoss does at the moment. Nearly the first thing that happens is to deploy an MBean called Log4JService. This has the task of locating the property file and sets up the configureAndWatch. So we have one hierarchy for all logging. The problem we are trying to solve is what happens when something doesn't like the JBoss configuration and tries to reconfigure log4j. A related issue (not the original problem raised on log4j-user) is that a user wants to take a component that already does logging and put it in its own hierarchy/configuration. There are two types of deployment within JBoss. 1) A service, such as embedded Tomcat. These could provide an internal mechanism for configuring log4j, it maybe useful for them to run in a different hierarchy. 2) An application. This is the original problem. The application wants to have a completely separate hierarchy and configuration to JBoss. The easy solution is every time I see a new ClassLoader in the RepositorySelector, create a new LoggerRepository. The configuration will either be specified at deployment or I use a fallback configuration. When something tries to reconfigure log4j it will be playing in its own backyard so problem solved. :-) But there are 50+ services in the default configuration of JBoss. Probably only the Web Server may want to reconfigure. The rest just want to use the JBoss hierarchy and configuration. I would like to let them share the same repository rather than creating 50 watchdog threads. Now the extra complication I introduced. The deployer may want all their applications running in the repository/hierarchy, but not the JBoss one. Again it would be wasteful to create a repository for each application when they are all sharing. I am not saying this is what will happen. As you said each applcation may want to specify its own log4j.properties. In this case, they each get a repository. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/main/org/jboss/management/j2ee JDBCDataSource.java SingleJBossServerManagement.java
User: schaefera
Date: 02/01/17 13:57:27
Modified:src/main/org/jboss/management/j2ee JDBCDataSource.java
SingleJBossServerManagement.java
Log:
Ajusted JSR-77 to the new JBoss JMX naming and the Scheduler now can be restarted
and will keep the schedule and allows an easier date input for Initial Start Date
Revision ChangesPath
1.6 +39 -39jboss/src/main/org/jboss/management/j2ee/JDBCDataSource.java
Index: JDBCDataSource.java
===
RCS file:
/cvsroot/jboss/jboss/src/main/org/jboss/management/j2ee/JDBCDataSource.java,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- JDBCDataSource.java 2001/12/10 06:27:49 1.5
+++ JDBCDataSource.java 2002/01/17 21:57:27 1.6
@@ -24,7 +24,7 @@
* {@link javax.management.j2ee.JDBCDataSource JDBCDataSource}.
*
* @author a href=mailto:[EMAIL PROTECTED];Andreas Schaefer/a.
- * @version $Revision: 1.5 $
+ * @version $Revision: 1.6 $
*
* pbRevisions:/b
*
@@ -185,22 +185,22 @@
public int getState() {
return mState;
}
-
- public void startService() {
+
+ /**
+* This method is only overwriten because to catch the exception
+* which is not specified in {@link javax.management.j2ee.StateManageable
+* StateManageable} interface.
+**/
+ public void start()
+ {
try {
- getServer().invoke(
-mService,
-start,
-new Object[] {},
-new String[] {}
- );
+ super.start();
}
- catch( JMException jme ) {
- //AS ToDo: later on we have to define what happens when service could not
be started
- jme.printStackTrace();
+ catch( Exception e ) {
+ getLog().error( start failed, e );
}
}
-
+
public void startRecursive() {
// No recursive start here
try {
@@ -211,21 +211,6 @@
}
}
- public void stopService() {
- try {
- getServer().invoke(
-mService,
-stop,
-new Object[] {},
-new String[] {}
- );
- }
- catch( JMException jme ) {
- //AS ToDo: later on we have to define what happens when service could not
be started
- jme.printStackTrace();
- }
- }
-
// javax.management.j2ee.JDBCDataSource implementation -
public ObjectName getJdbcDriver()
@@ -272,21 +257,36 @@
// ServiceMBeanSupport overrides -
- /**
-* This method is only overwriten because to catch the exception
-* which is not specified in {@link javax.management.j2ee.StateManageable
-* StateManageable} interface.
-**/
- public void start()
- {
+ public void startService() {
try {
- super.start();
+ getServer().invoke(
+mService,
+start,
+new Object[] {},
+new String[] {}
+ );
}
- catch( Exception e ) {
- getLog().error( start failed, e );
+ catch( JMException jme ) {
+ //AS ToDo: later on we have to define what happens when service could not
be started
+ jme.printStackTrace();
}
}
-
+
+ public void stopService() {
+ try {
+ getServer().invoke(
+mService,
+stop,
+new Object[] {},
+new String[] {}
+ );
+ }
+ catch( JMException jme ) {
+ //AS ToDo: later on we have to define what happens when service could not
be started
+ jme.printStackTrace();
+ }
+ }
+
// java.lang.Object overrides
public String toString() {
1.8 +2 -2
jboss/src/main/org/jboss/management/j2ee/SingleJBossServerManagement.java
Index: SingleJBossServerManagement.java
===
RCS file:
/cvsroot/jboss/jboss/src/main/org/jboss/management/j2ee/SingleJBossServerManagement.java,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- SingleJBossServerManagement.java 2002/01/03 04:00:59 1.7
+++ SingleJBossServerManagement.java 2002/01/17 21:57:27 1.8
@@ -23,7 +23,7 @@
* Represents the single JBoss server management domain
*
* @author a href=mailto:[EMAIL PROTECTED];Andreas Schaefer/a.
- * @version $Revision: 1.7 $
+ * @version $Revision: 1.8 $
*
* pbRevisions:/b
*
@@ -46,7 +46,7 @@
public SingleJBossServerManagement()
throws MalformedObjectNameException, InvalidParentException
{
- super( SingleJBoss
[JBoss-dev] CVS update: jboss/src/etc/conf/default jboss-service.xml
User: schaefera Date: 02/01/17 13:57:26 Modified:src/etc/conf/default jboss-service.xml Log: Ajusted JSR-77 to the new JBoss JMX naming and the Scheduler now can be restarted and will keep the schedule and allows an easier date input for Initial Start Date Revision ChangesPath 1.22 +11 -15jboss/src/etc/conf/default/jboss-service.xml Index: jboss-service.xml === RCS file: /cvsroot/jboss/jboss/src/etc/conf/default/jboss-service.xml,v retrieving revision 1.21 retrieving revision 1.22 diff -u -r1.21 -r1.22 --- jboss-service.xml 2002/01/04 00:11:35 1.21 +++ jboss-service.xml 2002/01/17 21:57:22 1.22 @@ -1,6 +1,6 @@ ?xml version=1.0 encoding=UTF-8? !DOCTYPE server -!-- $Id: jboss-service.xml,v 1.21 2002/01/04 00:11:35 user57 Exp $ -- +!-- $Id: jboss-service.xml,v 1.22 2002/01/17 21:57:22 schaefera Exp $ -- !-- = -- !-- -- @@ -33,10 +33,8 @@ !-- JSR-77 Single JBoss Server Management Domain -- !-- -- - !-- TODO: rename jmx domain to jboss.management.single -- - mbean code=org.jboss.management.j2ee.SingleJBossServerManagement - name=SingleJBoss:type=J2EEDomain,name=Manager + name=jboss.management.single:type=J2EEDomain,name=Manager /mbean !-- -- @@ -142,19 +140,17 @@ !-- Scheduler Service-- !-- -- - !-- Uncomment this to enable Scheduling + !-- Uncomment this to enable Scheduling - - mbean code=org.jboss.util.Scheduler name=jboss:service=Scheduler -constructor - arg type=java.lang.String value=:server=Scheduler/ - arg type=java.lang.String value=org.jboss.util.Scheduler$SchedulableExample/ - arg type=java.lang.String value=Schedulabe Test,12345/ - arg type=java.lang.String value=java.lang.String,int/ - arg type=long value=0/ - arg type=long value=1/ - arg type=long value=-1/ -/constructor +attribute name=StartAtStartuptrue/attribute +attribute name=SchedulableClassorg.jboss.util.Scheduler$SchedulableExample/attribute +attribute name=SchedulableArgumentsSchedulabe Test,12345/attribute +attribute name=SchedulableArgumentTypesjava.lang.String,int/attribute +attribute name=InitialStartDate0/attribute +attribute name=SchedulePeriod1/attribute +attribute name=InitialRepetitions-1/attribute /mbean - -- + !- - -- !-- Uncomment this and set up according to manual to add Castor JDO service mbean code=org.jboss.jdo.castor.CastorJDOImpl ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/main/org/jboss/util Scheduler.java SchedulerMBean.java
User: schaefera
Date: 02/01/17 13:57:27
Modified:src/main/org/jboss/util Scheduler.java SchedulerMBean.java
Log:
Ajusted JSR-77 to the new JBoss JMX naming and the Scheduler now can be restarted
and will keep the schedule and allows an easier date input for Initial Start Date
Revision ChangesPath
1.15 +122 -134 jboss/src/main/org/jboss/util/Scheduler.java
Index: Scheduler.java
===
RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/util/Scheduler.java,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- Scheduler.java2002/01/09 21:49:11 1.14
+++ Scheduler.java2002/01/17 21:57:27 1.15
@@ -7,6 +7,8 @@
package org.jboss.util;
import java.lang.reflect.Constructor;
+import java.text.DateFormat;
+import java.text.SimpleDateFormat;
import java.security.InvalidParameterException;
import java.util.ArrayList;
import java.util.Collection;
@@ -31,7 +33,7 @@
import javax.naming.NameNotFoundException;
import javax.naming.Reference;
import javax.naming.StringRefAddr;
-
+import org.jboss.logging.Logger;
import org.jboss.naming.NonSerializableFactory;
import org.jboss.system.ServiceMBeanSupport;
@@ -64,6 +66,20 @@
* liMBean is not bind/unbind to JNDI server anymore/li
* /ul
* /p
+* pb20020117 Andy:/b
+* ul
+* liChange the behaviour when the Start Date is in the past. Now the
+* Scheduler will behave as the Schedule is never stopped and find
+* the next available time to start with respect to the settings.
+* Therefore you can restart JBoss without adjust your Schedule
+* every time. BUT you will still loose the calls during the Schedule
+* was donw./li
+* liAdded parsing capabilities to setInitialStartDate. Now NOW: current time,
+* and a string in a format the SimpleDataFormat understand in your environment
+* (US: m/d/yy h:m a) but of course the time in ms since 1/1/1970./li
+* liSome fixes like the stopping a Schedule even if it already stopped etc./li
+* /ul
+* /p
**/
public class Scheduler
extends ServiceMBeanSupport
@@ -81,7 +97,8 @@
// Members
// -
- private String mName;
+ /** Class logger. */
+ private static final Logger log = Logger.getLogger( Scheduler.class );
private long mActualSchedulePeriod;
private long mRemainingRepetitions = 0;
@@ -100,47 +117,36 @@
private String[] mSchedulableArgumentList = new String[ 0 ];
private String mSchedulableArgumentTypes;
private Class[] mSchedulableArgumentTypeList = new Class[ 0 ];
+ private DateFormat mDateFormatter;
private Date mStartDate;
+ private String mStartDateString;
private long mSchedulePeriod;
private long mInitialRepetitions;
// -
// Constructors
// -
-
+
/**
* Default (no-args) Constructor
**/
public Scheduler()
{
- mName = null;
- }
-
- /**
-* Constructor with the necessary attributes to be set
-*
-* @param pName Name of the MBean
-**/
- public Scheduler( String pName )
- {
- mName = pName;
}
-
+
/**
* Constructor with the necessary attributes to be set
*
* @param pName Name of the MBean
**/
public Scheduler(
- String pName,
String pSchedulableClass,
String pInitArguments,
String pInitTypes,
- long pInitialStartDate,
+ String pInitialStartDate,
long pSchedulePeriod,
long pNumberOfRepetitions
) {
- mName = pName;
setStartAtStartup( true );
setSchedulableClass( pSchedulableClass );
setSchedulableArguments( pInitArguments );
@@ -160,16 +166,19 @@
try {
// Check the given attributes if correct
if( mSchedulableClass == null ) {
+ log.debug( Schedulable Class is not set );
throw new InvalidParameterException(
Schedulable Class must be set
);
}
if( mSchedulableArgumentList.length !=
mSchedulableArgumentTypeList.length ) {
+ log.debug( Schedulable Class Arguments and Types do not match in
length );
throw new InvalidParameterException(
Schedulable Class Arguments and Types do not match in length
);
}
if( mSchedulePeriod = 0 ) {
+ log.debug( Schedule Period is less than 0 (ms) );
throw new InvalidParameterException(
[JBoss-dev] [ jboss-Bugs-478090 ] EJBLocalHome interface NOT passivateable
Bugs item #478090, was opened at 2001-11-04 13:20
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=478090group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Peter Levart (plevart)
Assigned to: Andreas Schaefer (schaefera)
Summary: EJBLocalHome interface NOT passivateable
Initial Comment:
The EJB 2.0 spec says about SFSBs (in 7.4.1, page 71) that
references to EJBLocalHome interfaces can be left in the
non-transient fields to be passivated by the container.
Well, I get following exception thrown when my SFSB gets
passivated:
PassivatorQueue [ERROR] EXCEPTION
java.rmi.ServerException: Could not passivate; nested
exception is:
java.io.NotSerializableException:
org.jboss.ejb.plugins.local.BaseLocalContainerInvoker$HomeProxy
java.io.NotSerializableException:
org.jboss.ejb.plugins.local.BaseLocalContainerInvoker$HomeProxy
at
java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1148)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at
java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1827)
at
java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:480)
at
java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1214)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at
java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1827)
at
java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:480)
at
java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1214)
at
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at
org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager.passivateSession(StatefulSessionFilePersistenceManager.java:286)
at
org.jboss.ejb.plugins.StatefulSessionInstanceCache.passivate(StatefulSessionInstanceCache.java:68)
at
org.jboss.ejb.plugins.AbstractInstanceCache$1.execute(AbstractInstanceCache.java:711)
at
org.jboss.util.WorkerQueue$QueueLoop.run(WorkerQueue.java:199)
at java.lang.Thread.run(Thread.java:484)
--
Comment By: Nobody/Anonymous (nobody)
Date: 2002-01-17 14:26
Message:
Logged In: NO
What is the status of this bug? It still exists in the
container, causing major problems.
--
Comment By: Peter Levart (plevart)
Date: 2001-11-04 14:51
Message:
Logged In: YES
user_id=346981
The place where this is missing from are
org.jboss.ejb.plugins.SessionObjectInputStream and
org.jboss.ejb.plugins.SessionObjectOutputStream but for them to
be able to serialize/deserialize local interfaces some support has
to be added to the framework. I propose the following:
Create 4 new interfaces that will be used internally by the JBoss:
//
// analogue to javax.ejb.Handle but for local interfaces
//
public interface LocalHandle extends java.io.Serializable {
// obtain EJBLocalObject reference represented by this
handle
public EJBLocalObject getEJBLocalObject();
}
//
// analogue to javax.ejb.HomeHandle but for local interfaces
//
public interface LocalHomeHandle extends java.io.Serializable {
// obtain EJBLocalHome reference represented by this
handle
public EJBLocalHome getEJBLocalHome();
}
//
// extension to javax.ejb.EJBLocalObject interface that adds a
method to obtain a handle
//
public interface EJBossLocalObject extends
javax.ejb.EJBLocalObject {
// obtain a LocalHandle for this EJBossLocalObject
public LocalHandle getLocalHandle();
}
//
// extension to javax.ejb.EJBLocalHome interface that adds a
method to obtain a handle
//
public interface EJBossLocalHome extends
javax.ejb.EJBLocalHome {
// obtain a LocalHomeHandle for this EJBossLocalHome
public LocalHomeHandle getLocalHomeHandle();
}
... then use EJBossLocalObject EJBossLocalHome for the
various implementation classes internally in JBoss instead of
standard EJBLocalObject EJBLocalHome (for proxies) and create
some analogues implementations of LocalHandle and
LocalHomeHandle interfaces as done with remote interfaces in
org.jboss.ejb.plugins.jrmp package...
--
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=478090group_id=22866
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Re: The penny drops - JBoss Repository Selector
2.x uses the weblogic way of classloading (i.e. jar as parent of war). We ran into problems and limitations about a year ago, also where in the picture are services. The classloading scheme is about to be changed when I commit the Unified Deployer (JBossDeployer). It essentially shares the classes through the URLClassloader of JBoss3.0. This goes for *everything* applications, server modules, services, wars, everything. However in our case I am not sure I understand how log4j gets to its classes. can you expand on the thus servlet code naturally log using the log4j classes loaded by the EJB classloader. How is the logging setup done? what classes does it get? why is the parent delegation model in the picture here. please let me know marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of Ceki |Gulcu |Sent: Thursday, January 17, 2002 1:37 PM |To: [EMAIL PROTECTED] |Subject: Re: [JBoss-dev] Re: The penny drops - JBoss Repository Selector | | | |The problem *I* am interested in solving is to let each application |have in its own independent logging universe. I don't see a problem |with JBoss components sharing one logging universe (that of JBoss). | |The case of Tomcat or any other servlet container is very interesting |because the user's servlet code is part of the user's |application. Consequently, servlets should log on the logging universe |of larger application. | |With the Weblogic 6.1 classloading scheme, this is very easy to |accomplish. In the Weblogic 6.1 classloader hierarchy EJBs have a |classloader which is also the parent of the web-application (WAR) |classloader. Thus, servlet code naturally log using the log4j classes |loaded by the EJB classloader. In other words, one logging universe |for the whole application. | |I am not familiar with JBoss way of organizing the classloader hierarchy |although I would like to learn. | |Anyway, some entity has to know at some point in time which WAR is |associated with which (EJB) JAR. That entity can easily set the | |oops... | |Jboss embeds the whole of Tomcat/Jetter/whatever. OK then how can the |servlets in an application access the *local* interface of entity |beans? | |Do you know what I am talking about? Has this issue been addressed in |JBoss 3.0? Regards, Ceki | | |At 16:56 17.01.2002 +, Adrian Brock [EMAIL PROTECTED] wrote: |Hi Ceki, | |I'm trying to reduce the length of my posts, this one will probably |break that rule :-( | |Re: Repositories |I'll try explaining this from the beginning. We basically agree |but I'm not getting my point across about multiple repositories. |Maybe I'm missing one of your points as well? :-) | |First, here is what JBoss does at the moment. |Nearly the first thing that happens is to deploy an MBean called |Log4JService. This has the task of locating the property file |and sets up the configureAndWatch. |So we have one hierarchy for all logging. | |The problem we are trying to solve is what happens when something |doesn't like the JBoss configuration and tries to reconfigure log4j. | |A related issue (not the original problem raised on log4j-user) is that |a user wants to take a component that already does logging and put it in |its own hierarchy/configuration. | |There are two types of deployment within JBoss. |1) A service, such as embedded Tomcat. |These could provide an internal mechanism for configuring log4j, it |maybe useful for them to run in a different hierarchy. |2) An application. This is the original problem. The application wants |to have a completely separate hierarchy and configuration to JBoss. | |The easy solution is every time I see a new ClassLoader in the |RepositorySelector, create a new LoggerRepository. |The configuration will either be specified at deployment or I |use a fallback configuration. |When something tries to reconfigure log4j it will be playing in its own |backyard so problem solved. :-) | |But there are 50+ services in the default configuration of JBoss. |Probably only the Web Server may want to reconfigure. The rest just |want to use the JBoss hierarchy and configuration. I would like |to let them share the same repository rather than creating 50 |watchdog threads. | |Now the extra complication I introduced. |The deployer may want all their applications running in the |repository/hierarchy, but not the JBoss one. |Again it would be wasteful to create a repository for each |application when they are all sharing. |I am not saying this is what will happen. As you said each applcation |may want to specify its own log4j.properties. In this case, they |each get a repository. | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Scheduler Updates
Hi Geeks For the current CVS head (JBoss 3.0) I made some changes to the Scheduler: 1) When you set an Initial Start Date in the past the Scheduler will check if now can be reached by the period and repetition. If it can then the Scheduler will start there and reduce the repetition appropriate. If not then it will not start. If it is an endless loop then the Scheduler will always be restarted. 2) The initial start date can now be set either - milliseconds since 1/1/1970 - NOW meaning now - Date string which can be parsed by SimpleDateFormat which depends on your environment 3) Adjusted the jboss.jcml to set the values of the Scheduler by attributes and not by constructor arguments. 4) The remaning repetitions in the Schedulable.perform() was one call to high. Now it is the correct remaining repetitions. Have fun x Andreas Schaefer Senior Consultant JBoss Group, LLC x ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Scheduler Updates
So what does the correct -service.xml mbean entry look like? I started using this last night and found the documentation way off but the jboss-service.xml had the correct xml to get the stuff started (it had a constructor tag under the main mbean tab). Thanks dain -Original Message- From: Andreas Schaefer [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 17, 2002 4:42 PM To: [EMAIL PROTECTED] Subject: [JBoss-dev] Scheduler Updates Hi Geeks For the current CVS head (JBoss 3.0) I made some changes to the Scheduler: 1) When you set an Initial Start Date in the past the Scheduler will check if now can be reached by the period and repetition. If it can then the Scheduler will start there and reduce the repetition appropriate. If not then it will not start. If it is an endless loop then the Scheduler will always be restarted. 2) The initial start date can now be set either - milliseconds since 1/1/1970 - NOW meaning now - Date string which can be parsed by SimpleDateFormat which depends on your environment 3) Adjusted the jboss.jcml to set the values of the Scheduler by attributes and not by constructor arguments. 4) The remaning repetitions in the Schedulable.perform() was one call to high. Now it is the correct remaining repetitions. Have fun x Andreas Schaefer Senior Consultant JBoss Group, LLC x ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Re: The penny drops - JBoss Repository Selector
At 17:28 17.01.2002 -0800, marc fleury wrote: 2.x uses the weblogic way of classloading (i.e. jar as parent of war). We ran into problems and limitations about a year ago, also where in the picture are services. The classloading scheme is about to be changed when I commit the Unified Deployer (JBossDeployer). It essentially shares the classes through the URLClassloader of JBoss3.0. This goes for *everything* applications, server modules, services, wars, everything. However in our case I am not sure I understand how log4j gets to its classes. can you expand on the thus servlet code naturally log using the log4j classes loaded by the EJB classloader. How is the logging setup done? what classes does it get? why is the parent delegation model in the picture here. Well, it really simple. In the case of Weblogic which does not use log4j for its own logging, each application (that uses log4j) gets a different copy of log4j classes loaded into memory. It follows that Each log4j copy can be used and configured separately. In other words, distinct jars uses distinct log4j copies. Now, since the war classloader is a child of the jar classloader, everything seen by the parent (jar) classloader is seen by the war classloader. Thus, the servlet part uses the same log4j copy as the jar (ejb) part. Does this explain why the delegation model is in the picture? Oh, btw, I am assuming log4j is *not* in the classpath. Regards, Ceki ps: For those on jboss-dev who did not follow the beginning of this discussion on log4j-dev, here are the relevant threads: http://marc.theaimsgroup.com/?t=10107551141r=1w=2 http://marc.theaimsgroup.com/?t=10111351264r=1w=2 please let me know marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of Ceki |Gulcu |Sent: Thursday, January 17, 2002 1:37 PM |To: [EMAIL PROTECTED] |Subject: Re: [JBoss-dev] Re: The penny drops - JBoss Repository Selector | | | |The problem *I* am interested in solving is to let each application |have in its own independent logging universe. I don't see a problem |with JBoss components sharing one logging universe (that of JBoss). | |The case of Tomcat or any other servlet container is very interesting |because the user's servlet code is part of the user's |application. Consequently, servlets should log on the logging universe |of larger application. | |With the Weblogic 6.1 classloading scheme, this is very easy to |accomplish. In the Weblogic 6.1 classloader hierarchy EJBs have a |classloader which is also the parent of the web-application (WAR) |classloader. Thus, servlet code naturally log using the log4j classes |loaded by the EJB classloader. In other words, one logging universe |for the whole application. | |I am not familiar with JBoss way of organizing the classloader hierarchy |although I would like to learn. | |Anyway, some entity has to know at some point in time which WAR is |associated with which (EJB) JAR. That entity can easily set the | |oops... | |Jboss embeds the whole of Tomcat/Jetter/whatever. OK then how can the |servlets in an application access the *local* interface of entity |beans? | |Do you know what I am talking about? Has this issue been addressed in |JBoss 3.0? Regards, Ceki | | |At 16:56 17.01.2002 +, Adrian Brock [EMAIL PROTECTED] wrote: |Hi Ceki, | |I'm trying to reduce the length of my posts, this one will probably |break that rule :-( | |Re: Repositories |I'll try explaining this from the beginning. We basically agree |but I'm not getting my point across about multiple repositories. |Maybe I'm missing one of your points as well? :-) | |First, here is what JBoss does at the moment. |Nearly the first thing that happens is to deploy an MBean called |Log4JService. This has the task of locating the property file |and sets up the configureAndWatch. |So we have one hierarchy for all logging. | |The problem we are trying to solve is what happens when something |doesn't like the JBoss configuration and tries to reconfigure log4j. | |A related issue (not the original problem raised on log4j-user) is that |a user wants to take a component that already does logging and put it in |its own hierarchy/configuration. | |There are two types of deployment within JBoss. |1) A service, such as embedded Tomcat. |These could provide an internal mechanism for configuring log4j, it |maybe useful for them to run in a different hierarchy. |2) An application. This is the original problem. The application wants |to have a completely separate hierarchy and configuration to JBoss. | |The easy solution is every time I see a new ClassLoader in the |RepositorySelector, create a new LoggerRepository. |The configuration will either be specified at deployment or I |use a fallback configuration. |When something tries to reconfigure log4j it will be playing in its own |backyard so problem solved. :-) | |But there are 50+ services in the default configuration of JBoss. |Probably only the Web Server may
RE: [JBoss-dev] Re: The penny drops - JBoss Repository Selector
|Well, it really simple. In the case of Weblogic which does not use |log4j for its own logging, each application (that uses log4j) gets a |different copy of log4j classes loaded into memory. It follows that how, how is the gets a different copy. i don't want to hear about the parent delegation model, What does that mean, from a class you do log.log(something) and how do you get the first reference. You seem to imply that there is a ContextClassLoader.getClass(log4j) or what? |Each log4j copy can be used and configured separately. In other words, |distinct jars uses distinct log4j copies. what I want to see is the code that sets up the reference you are using and I will be able to tell you |Now, since the war classloader is a child of the jar classloader, |everything seen by the parent (jar) classloader is seen by the war |classloader. Thus, the servlet part uses the same log4j copy as the |jar (ejb) part. Does this explain why the delegation model is in the |picture? no, it doesn't explain why you set up the reference and its configuration through the classloader. i want to hear about the getResourceAsStream(configuration) and the first reference to log4j, or the getClass or the classforname (god forbid) not the flaky parent delegation model which we understand perfectly (and go beyond in jboss3.0)... marcf | |Oh, btw, I am assuming log4j is *not* in the classpath. | |Regards, Ceki | |ps: For those on jboss-dev who did not follow the beginning of this |discussion on log4j-dev, here are the relevant threads: | |http://marc.theaimsgroup.com/?t=10107551141r=1w=2 |http://marc.theaimsgroup.com/?t=10111351264r=1w=2 | | | |please let me know | |marcf | ||-Original Message- ||From: [EMAIL PROTECTED] ||[mailto:[EMAIL PROTECTED]]On Behalf Of Ceki ||Gulcu ||Sent: Thursday, January 17, 2002 1:37 PM ||To: [EMAIL PROTECTED] ||Subject: Re: [JBoss-dev] Re: The penny drops - JBoss Repository Selector || || || ||The problem *I* am interested in solving is to let each application ||have in its own independent logging universe. I don't see a problem ||with JBoss components sharing one logging universe (that of JBoss). || ||The case of Tomcat or any other servlet container is very interesting ||because the user's servlet code is part of the user's ||application. Consequently, servlets should log on the logging universe ||of larger application. || ||With the Weblogic 6.1 classloading scheme, this is very easy to ||accomplish. In the Weblogic 6.1 classloader hierarchy EJBs have a ||classloader which is also the parent of the web-application (WAR) ||classloader. Thus, servlet code naturally log using the log4j classes ||loaded by the EJB classloader. In other words, one logging universe ||for the whole application. || ||I am not familiar with JBoss way of organizing the classloader hierarchy ||although I would like to learn. || ||Anyway, some entity has to know at some point in time which WAR is ||associated with which (EJB) JAR. That entity can easily set the || ||oops... || ||Jboss embeds the whole of Tomcat/Jetter/whatever. OK then how can the ||servlets in an application access the *local* interface of entity ||beans? || ||Do you know what I am talking about? Has this issue been addressed in ||JBoss 3.0? Regards, Ceki || || ||At 16:56 17.01.2002 +, Adrian Brock [EMAIL PROTECTED] wrote: ||Hi Ceki, || ||I'm trying to reduce the length of my posts, this one will probably ||break that rule :-( || ||Re: Repositories ||I'll try explaining this from the beginning. We basically agree ||but I'm not getting my point across about multiple repositories. ||Maybe I'm missing one of your points as well? :-) || ||First, here is what JBoss does at the moment. ||Nearly the first thing that happens is to deploy an MBean called ||Log4JService. This has the task of locating the property file ||and sets up the configureAndWatch. ||So we have one hierarchy for all logging. || ||The problem we are trying to solve is what happens when something ||doesn't like the JBoss configuration and tries to reconfigure log4j. || ||A related issue (not the original problem raised on log4j-user) is that ||a user wants to take a component that already does logging and put it in ||its own hierarchy/configuration. || ||There are two types of deployment within JBoss. ||1) A service, such as embedded Tomcat. ||These could provide an internal mechanism for configuring log4j, it ||maybe useful for them to run in a different hierarchy. ||2) An application. This is the original problem. The application wants ||to have a completely separate hierarchy and configuration to JBoss. || ||The easy solution is every time I see a new ClassLoader in the ||RepositorySelector, create a new LoggerRepository. ||The configuration will either be specified at deployment or I ||use a fallback configuration. ||When something tries to reconfigure log4j it will be playing in its own ||backyard so problem solved. :-) || ||But there are 50+ services in the
Re: [JBoss-dev] Source code editors
Try AnyJ, unless you are doing commercial development it is free. It is also free for evaluation. See their license. The IDE is quite fast (way much smaller than JBuilder) and has some very useful features. I think, I've heard about it from Marc in one of his e-mails. - Anatoly Akkerman Computer Science Dept. Courant Institute of Mathematical Sciences, NYU 715 Broadway, #719 Tel: 212 998-3493 New York, NY 10003 Fax: 212 995-4123 - ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jmx/src/main/test/compliance ComplianceSUITE.java
User: squirest Date: 02/01/17 17:12:22 Modified:src/main/test/compliance ComplianceSUITE.java Log: testsuite updates, mostly related to standard MBeanInfo Revision ChangesPath 1.3 +7 -8 jmx/src/main/test/compliance/ComplianceSUITE.java Index: ComplianceSUITE.java === RCS file: /cvsroot/jboss/jmx/src/main/test/compliance/ComplianceSUITE.java,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- ComplianceSUITE.java 2002/01/16 11:37:44 1.2 +++ ComplianceSUITE.java 2002/01/18 01:12:22 1.3 @@ -12,7 +12,7 @@ /** * Everything under test.compliance is a set of unit tests - * which bmust/b pass 100% against the JMX RI. + * which should pass as much as possible against the JMX RI * * Additions to this package are welcome/encouraged - adding a * test that fails is a great way to communicate a bug ;-) @@ -21,13 +21,12 @@ * consider providing a testcase prior to making code changes * in the impl itself - ala XP. * - * bThe only restriction is to make sure everything in - * test.compliance passes 100% against the RI./b (in case - * I didn't make that clear enough already) + * The only restriction is that if the tests don't succeed against + * the RI, the test error message should indicate that the test + * will fail on the RI (preferred way) or at least comment the testcase + * stating expected failures. Either way, you should comment the code + * justifying why the test is valid despite failing against the RI. * - * FIXME - need to provide a way to run these suites against the - * RI and the JBoss impl via ant - * * @author a href=mailto:[EMAIL PROTECTED];Trevor Squires/a. */ @@ -47,7 +46,7 @@ suite.addTest(test.compliance.registration.RegistrationSUITE.suite()); suite.addTest(test.compliance.server.ServerSUITE.suite()); suite.addTest(test.compliance.modelmbean.ModelMBeanSUITE.suite()); - + return suite; } } ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jmx/src/main/test/compliance/standard/support Torture.java TortureMBean.java Trivial.java TrivialMBean.java
User: squirest
Date: 02/01/17 17:12:23
Modified:src/main/test/compliance/standard/support Trivial.java
TrivialMBean.java
Added: src/main/test/compliance/standard/support Torture.java
TortureMBean.java
Log:
testsuite updates, mostly related to standard MBeanInfo
Revision ChangesPath
1.2 +28 -28jmx/src/main/test/compliance/standard/support/Trivial.java
Index: Trivial.java
===
RCS file: /cvsroot/jboss/jmx/src/main/test/compliance/standard/support/Trivial.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Trivial.java 2001/12/20 01:50:59 1.1
+++ Trivial.java 2002/01/18 01:12:23 1.2
@@ -1,28 +1,28 @@
-/*
- * JBoss, the OpenSource J2EE webOS
- *
- * Distributable under LGPL license.
- * See terms of license at gnu.org.
- */
-
-package test.compliance.standard.support;
-
-public class Trivial implements TrivialMBean
-{
- private String something = null;
- private boolean anAttribute = true;
-
- public void setSomething(String thing)
- {
- this.something = thing;
- }
-
- public String getSomething()
- {
- return something;
- }
-
- public void doOperation()
- {
- }
-}
+/*
+ * JBoss, the OpenSource J2EE webOS
+ *
+ * Distributable under LGPL license.
+ * See terms of license at gnu.org.
+ */
+
+package test.compliance.standard.support;
+
+public class Trivial implements TrivialMBean
+{
+ private String something = null;
+ private boolean anAttribute = true;
+
+ public void setSomething(String thing)
+ {
+ this.something = thing;
+ }
+
+ public String getSomething()
+ {
+ return something;
+ }
+
+ public void doOperation(String arg)
+ {
+ }
+}
1.2 +17 -17jmx/src/main/test/compliance/standard/support/TrivialMBean.java
Index: TrivialMBean.java
===
RCS file:
/cvsroot/jboss/jmx/src/main/test/compliance/standard/support/TrivialMBean.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- TrivialMBean.java 2001/12/20 01:50:59 1.1
+++ TrivialMBean.java 2002/01/18 01:12:23 1.2
@@ -1,17 +1,17 @@
-/*
- * JBoss, the OpenSource J2EE webOS
- *
- * Distributable under LGPL license.
- * See terms of license at gnu.org.
- */
-
-package test.compliance.standard.support;
-
-public interface TrivialMBean
-{
- void setSomething(String thing);
-
- String getSomething();
-
- void doOperation();
-}
+/*
+ * JBoss, the OpenSource J2EE webOS
+ *
+ * Distributable under LGPL license.
+ * See terms of license at gnu.org.
+ */
+
+package test.compliance.standard.support;
+
+public interface TrivialMBean
+{
+ void setSomething(String thing);
+
+ String getSomething();
+
+ void doOperation(String arg);
+}
1.1 jmx/src/main/test/compliance/standard/support/Torture.java
Index: Torture.java
===
/*
* JBoss, the OpenSource J2EE webOS
*
* Distributable under LGPL license.
* See terms of license at gnu.org.
*/
package test.compliance.standard.support;
/**
* @author a href=mailto:[EMAIL PROTECTED];Trevor Squires/a.
*/
public class Torture implements TortureMBean
{
public Torture()
{
}
public Torture(String[][] something)
{
}
Torture(int foo)
{
}
protected Torture(String wibble)
{
}
private Torture(double trouble)
{
}
public String getNiceString()
{
return null;
}
public void setNiceString(String nice)
{
}
public boolean isNiceBoolean()
{
return false;
}
public void setNiceBoolean(boolean nice)
{
}
public void setInt(int foo)
{
}
public void setIntArray(int[] foo)
{
}
public void setNestedIntArray(int[][][] foo)
{
}
public void setInteger(Integer foo)
{
}
public void setIntegerArray(Integer[] foo)
{
}
public void setNestedIntegerArray(Integer[][][] foo)
{
}
public int getMyinteger()
{
return 0;
}
public int[] getMyintegerArray()
{
return new int[0];
}
public int[][][] getMyNestedintegerArray()
{
return new int[0][][];
}
public Integer getMyInteger()
{
return null;
}
public Integer[] getMyIntegerArray()
{
return new Integer[0];
}
public Integer[][][] getMyNestedIntegerArray()
{
return
[JBoss-dev] CVS update: jmx/src/main/test/compliance/standard AttributeInfoTEST.java ConstructorInfoTEST.java InfoTortureSUITE.java InfoTortureTEST.java OperationInfoTEST.java SpuriousAttributeTEST.java StandardSUITE.java TrivialTEST.java
User: squirest
Date: 02/01/17 17:12:23
Modified:src/main/test/compliance/standard StandardSUITE.java
TrivialTEST.java
Added: src/main/test/compliance/standard AttributeInfoTEST.java
ConstructorInfoTEST.java InfoTortureSUITE.java
InfoTortureTEST.java OperationInfoTEST.java
SpuriousAttributeTEST.java
Log:
testsuite updates, mostly related to standard MBeanInfo
Revision ChangesPath
1.2 +5 -1 jmx/src/main/test/compliance/standard/StandardSUITE.java
Index: StandardSUITE.java
===
RCS file: /cvsroot/jboss/jmx/src/main/test/compliance/standard/StandardSUITE.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- StandardSUITE.java2001/12/20 01:50:59 1.1
+++ StandardSUITE.java2002/01/18 01:12:22 1.2
@@ -10,6 +10,10 @@
import junit.framework.Test;
import junit.framework.TestSuite;
+/**
+ * @author a href=mailto:[EMAIL PROTECTED];Trevor Squires/a.
+ */
+
public class StandardSUITE extends TestSuite
{
public static void main(String[] args)
@@ -22,8 +26,8 @@
TestSuite suite = new TestSuite(StandardMBean Tests);
suite.addTest(new TestSuite(TrivialTEST.class));
+ suite.addTest(InfoTortureSUITE.suite());
return suite;
}
-
}
1.2 +114 -10 jmx/src/main/test/compliance/standard/TrivialTEST.java
Index: TrivialTEST.java
===
RCS file: /cvsroot/jboss/jmx/src/main/test/compliance/standard/TrivialTEST.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- TrivialTEST.java 2001/12/20 01:50:59 1.1
+++ TrivialTEST.java 2002/01/18 01:12:22 1.2
@@ -10,11 +10,28 @@
import junit.framework.TestCase;
import test.compliance.standard.support.Trivial;
+import javax.management.InstanceAlreadyExistsException;
+import javax.management.InstanceNotFoundException;
+import javax.management.IntrospectionException;
+import javax.management.MBeanAttributeInfo;
+import javax.management.MBeanConstructorInfo;
+import javax.management.MBeanInfo;
+import javax.management.MBeanNotificationInfo;
+import javax.management.MBeanOperationInfo;
+import javax.management.MBeanParameterInfo;
+import javax.management.MBeanRegistrationException;
import javax.management.MBeanServer;
import javax.management.MBeanServerFactory;
+import javax.management.MalformedObjectNameException;
+import javax.management.NotCompliantMBeanException;
import javax.management.ObjectInstance;
import javax.management.ObjectName;
+import javax.management.ReflectionException;
+/**
+ * @author a href=mailto:[EMAIL PROTECTED];Trevor Squires/a.
+ */
+
public class TrivialTEST extends TestCase
{
public TrivialTEST(String s)
@@ -39,14 +56,101 @@
}
assertTrue(expected server to report it as registered,
server.isRegistered(name));
}
+
+ public void testConstructorInfo()
+ {
+ MBeanInfo info = getTrivialInfo();
+
+ MBeanConstructorInfo[] constructors = info.getConstructors();
+ assertEquals(constructor list length, 1, constructors.length);
+
+ // I really don't feel like reflecting to get the name of the constructor,
+ // it should just be the name of the class right?
+ assertEquals(constructor name, Trivial.class.getName(),
constructors[0].getName());
+
+ MBeanParameterInfo[] params = constructors[0].getSignature();
+ assertEquals(constructor signature length, 0, params.length);
+ }
+
+ public void testAttributeInfo()
+ {
+ MBeanInfo info = getTrivialInfo();
+
+ MBeanAttributeInfo[] attributes = info.getAttributes();
+ assertEquals(attribute list length, 1, attributes.length);
+ assertEquals(attribute name, Something, attributes[0].getName());
+ assertEquals(attribute type, String.class.getName(),
attributes[0].getType());
+ assertEquals(attribute readable, true, attributes[0].isReadable());
+ assertEquals(attribute writable, true, attributes[0].isWritable());
+ assertEquals(attribute isIs, false, attributes[0].isIs());
+ }
+
+ public void testOperationInfo()
+ {
+ MBeanInfo info = getTrivialInfo();
+
+ MBeanOperationInfo[] operations = info.getOperations();
+ assertEquals(operations list length, 1, operations.length);
+ assertEquals(operation name, doOperation, operations[0].getName());
+ assertEquals(operation return type, Void.TYPE.getName(),
operations[0].getReturnType());
+ assertEquals(operation impact, MBeanOperationInfo.UNKNOWN,
operations[0].getImpact());
+
+ MBeanParameterInfo[] params =
[JBoss-dev] CVS update: jmx/src/main/javax/management MBeanOperationInfo.java
User: squirest
Date: 02/01/17 17:14:13
Modified:src/main/javax/management MBeanOperationInfo.java
Log:
changed public static final int values to be the same as in the RI so that
code compiled using the RI will still work against jboss-jmx
Revision ChangesPath
1.4 +87 -87jmx/src/main/javax/management/MBeanOperationInfo.java
Index: MBeanOperationInfo.java
===
RCS file: /cvsroot/jboss/jmx/src/main/javax/management/MBeanOperationInfo.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- MBeanOperationInfo.java 2001/12/11 21:19:47 1.3
+++ MBeanOperationInfo.java 2002/01/18 01:14:13 1.4
@@ -1,87 +1,87 @@
-/*
- * JBoss, the OpenSource J2EE webOS
- *
- * Distributable under LGPL license.
- * See terms of license at gnu.org.
- */
-package javax.management;
-
-/**
- * Describes an operation exposed by an MBean
- *
- * This implementation protects its immutability by taking shallow clones of all
arrays
- * supplied in constructors and by returning shallow array clones in getXXX()
methods.
- *
- * @author a href=mailto:[EMAIL PROTECTED];Juha Lindfors/a.
- * @author a href=mailto:[EMAIL PROTECTED];Trevor Squires/a.
- *
- * @version $Revision: 1.3 $
- */
-public class MBeanOperationInfo extends MBeanFeatureInfo
- implements java.io.Serializable, Cloneable
-{
-
- // Attributes
- public static final int INFO= 0x1234;
- public static final int ACTION = 0x332;
- public static final int ACTION_INFO = 0xabcd;
- public static final int UNKNOWN = 0xdead;
-
- protected int impact = UNKNOWN;
- protected MBeanParameterInfo[] signature = null;
- protected String returnType = null;
-
- // Constructors --
- public MBeanOperationInfo(java.lang.String description,
- java.lang.reflect.Method method)
- {
- super(method.getName(), description);
- this.returnType = method.getReturnType().getName();
-
- Class[] sign = method.getParameterTypes();
- signature = new MBeanParameterInfo[sign.length];
-
- for (int i = 0; i sign.length; ++i)
- {
- String name = sign[i].getName();
- signature[i] = new MBeanParameterInfo(name, name, MBean Operation
Parameter.);
- }
- }
-
- public MBeanOperationInfo(String name, String description,
- MBeanParameterInfo[] signature,
- String returnType, int impact)
- {
- super(name, description);
- this.signature = (null == signature) ? new MBeanParameterInfo[0] :
(MBeanParameterInfo[]) signature.clone();
- this.returnType = returnType;
- this.impact = impact;
- }
-
- // Public
- public String getReturnType()
- {
- return returnType;
- }
-
- public MBeanParameterInfo[] getSignature()
- {
- return (MBeanParameterInfo[]) signature.clone();
- }
-
- public int getImpact()
- {
- return impact;
- }
-
- // Cloneable implementation --
- public java.lang.Object clone() throws CloneNotSupportedException
- {
- MBeanOperationInfo clone = (MBeanOperationInfo) super.clone();
- clone.signature = getSignature();
- clone.returnType = getReturnType();
- clone.impact = getImpact();
-
- return clone;
- }
-}
+/*
+ * JBoss, the OpenSource J2EE webOS
+ *
+ * Distributable under LGPL license.
+ * See terms of license at gnu.org.
+ */
+package javax.management;
+
+/**
+ * Describes an operation exposed by an MBean
+ *
+ * This implementation protects its immutability by taking shallow clones of all
arrays
+ * supplied in constructors and by returning shallow array clones in getXXX()
methods.
+ *
+ * @author a href=mailto:[EMAIL PROTECTED];Juha Lindfors/a.
+ * @author a href=mailto:[EMAIL PROTECTED];Trevor Squires/a.
+ *
+ * @version $Revision: 1.4 $
+ */
+public class MBeanOperationInfo extends MBeanFeatureInfo
+ implements java.io.Serializable, Cloneable
+{
+
+ // Attributes
+ public static final int INFO= 0;
+ public static final int ACTION = 1;
+ public static final int ACTION_INFO = 2;
+ public static final int UNKNOWN = 3;
+
+ protected int impact = UNKNOWN;
+ protected MBeanParameterInfo[] signature = null;
+ protected String returnType = null;
+
+ // Constructors --
+ public MBeanOperationInfo(java.lang.String description,
+
[JBoss-dev] CVS update: jmx/src/main/test/compliance/objectname PatternTEST.java
User: squirest
Date: 02/01/17 17:12:22
Modified:src/main/test/compliance/objectname PatternTEST.java
Log:
testsuite updates, mostly related to standard MBeanInfo
Revision ChangesPath
1.4 +152 -149 jmx/src/main/test/compliance/objectname/PatternTEST.java
Index: PatternTEST.java
===
RCS file: /cvsroot/jboss/jmx/src/main/test/compliance/objectname/PatternTEST.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- PatternTEST.java 2002/01/16 23:38:21 1.3
+++ PatternTEST.java 2002/01/18 01:12:22 1.4
@@ -1,149 +1,152 @@
-/*
- * JBoss, the OpenSource J2EE webOS
- *
- * Distributable under LGPL license.
- * See terms of license at gnu.org.
- */
-
-package test.compliance.objectname;
-
-import junit.framework.TestCase;
-
-import javax.management.MalformedObjectNameException;
-import javax.management.ObjectName;
-
-public class PatternTEST extends TestCase
-{
- public PatternTEST(String s)
- {
- super(s);
- }
-
- public void testBasicDomainPattern()
- {
- String nameArg = *:key1=val1,key2=val2;
- ObjectName name = constructSafely(nameArg);
- assertTrue(isPattern should be true, name.isPattern());
- assertEquals(toString should be: ' + nameArg + ', nameArg,
name.toString());
- assertTrue(isPropertyPattern should be false, !name.isPropertyPattern());
- assertEquals(*, name.getDomain());
- }
-
- public void testBasicDomainPatternExtra()
- {
- String nameArg = **:key1=val1,key2=val2;
- ObjectName name = constructSafely(nameArg);
- assertTrue(isPattern should be true, name.isPattern());
- assertEquals(toString should be: ' + nameArg + ', nameArg,
name.toString());
- assertTrue(isPropertyPattern should be false, !name.isPropertyPattern());
- assertEquals(**, name.getDomain());
- }
-
- public void testPartialDomainPattern()
- {
- String nameArg = *domain:key1=val1,key2=val2;
- ObjectName name = constructSafely(nameArg);
- assertTrue(isPattern should be true, name.isPattern());
- assertEquals(toString should be: ' + nameArg + ', nameArg,
name.toString());
- assertTrue(isPropertyPattern should be false, !name.isPropertyPattern());
- assertEquals(*domain, name.getDomain());
- }
-
- public void testHarderPartialDomainPattern()
- {
- String nameArg = d*n:key1=val1,key2=val2;
- ObjectName name = constructSafely(nameArg);
- assertTrue(isPattern should be true, name.isPattern());
- assertEquals(toString should be: ' + nameArg + ', nameArg,
name.toString());
- assertTrue(isPropertyPattern should be false, !name.isPropertyPattern());
- assertEquals(d*n, name.getDomain());
- }
-
- public void testHarderPartialDomainPatternExtra()
- {
- String nameArg = d**n:key1=val1,key2=val2;
- ObjectName name = constructSafely(nameArg);
- assertTrue(isPattern should be true, name.isPattern());
- assertEquals(toString should be: ' + nameArg + ', nameArg,
name.toString());
- assertTrue(isPropertyPattern should be false, !name.isPropertyPattern());
- assertEquals(d**n, name.getDomain());
- }
-
- public void testPositionalDomainPattern()
- {
- String nameArg = do??in:key1=val1,key2=val2;
- ObjectName name = constructSafely(nameArg);
- assertTrue(isPattern should be true, name.isPattern());
- assertEquals(toString should be: ' + nameArg + ', nameArg,
name.toString());
- assertTrue(isPropertyPattern should be false, !name.isPropertyPattern());
- assertEquals(do??in, name.getDomain());
- }
-
- public void testPatternOnly()
- {
- String nameArg = *:*;
- ObjectName name = constructSafely(nameArg);
- assertTrue(isPattern should be true, name.isPattern());
- assertTrue(isPropertyPattern should be true, name.isPropertyPattern());
- assertEquals(FAILS IN RI, nameArg, name.getCanonicalName());
- }
-
- public void testKeyPatternOnly()
- {
- String nameArg = domain:*;
- ObjectName name = constructSafely(nameArg);
- assertTrue(isPattern should be true, name.isPattern());
- assertTrue(isPropertyPattern should be true, name.isPropertyPattern());
- assertEquals(FAILS IN RI, nameArg, name.getCanonicalName());
- assertTrue(key properties hash should be zero size, 0 ==
name.getKeyPropertyList().size());
- }
-
- public void testPartialKeyPattern()
- {
- String nameArg = domain:key2=val2,*,key1=val1;
- ObjectName name = constructSafely(nameArg);
- assertTrue(isPattern should be true, name.isPattern());
- assertTrue(isPropertyPattern should be true, name.isPropertyPattern());
-
[JBoss-dev] CVS update: jmx/src/main/org/jboss/mx/metadata StandardMetaData.java
User: squirest
Date: 02/01/17 17:20:08
Modified:src/main/org/jboss/mx/metadata StandardMetaData.java
Log:
ugly little interim fixes so that it passes compliance tests - this code will
show up on radar again when I add the non-compliant-mbean tests
Revision ChangesPath
1.4 +54 -46jmx/src/main/org/jboss/mx/metadata/StandardMetaData.java
Index: StandardMetaData.java
===
RCS file: /cvsroot/jboss/jmx/src/main/org/jboss/mx/metadata/StandardMetaData.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- StandardMetaData.java 2002/01/12 20:05:51 1.3
+++ StandardMetaData.java 2002/01/18 01:20:08 1.4
@@ -1,26 +1,29 @@
/*
- * LGPL
+ * JBoss, the OpenSource J2EE webOS
+ *
+ * Distributable under LGPL license.
+ * See terms of license at gnu.org.
*/
-package org.jboss.mx.metadata;
-
-import java.util.Map;
-import java.util.HashMap;
-import java.util.Iterator;
-import java.util.List;
-import java.util.ArrayList;
-import java.lang.reflect.Method;
-import java.lang.reflect.Constructor;
-
-import javax.management.NotCompliantMBeanException;
-import javax.management.IntrospectionException;
-import javax.management.MBeanInfo;
-import javax.management.MBeanAttributeInfo;
-import javax.management.MBeanOperationInfo;
-import javax.management.MBeanConstructorInfo;
-import javax.management.MBeanNotificationInfo;
-import javax.management.NotificationBroadcaster;
-
-import javax.management.modelmbean.ModelMBeanAttributeInfo;
+package org.jboss.mx.metadata;
+
+import java.util.Map;
+import java.util.HashMap;
+import java.util.Iterator;
+import java.util.List;
+import java.util.ArrayList;
+import java.lang.reflect.Method;
+import java.lang.reflect.Constructor;
+
+import javax.management.NotCompliantMBeanException;
+import javax.management.IntrospectionException;
+import javax.management.MBeanInfo;
+import javax.management.MBeanAttributeInfo;
+import javax.management.MBeanOperationInfo;
+import javax.management.MBeanConstructorInfo;
+import javax.management.MBeanNotificationInfo;
+import javax.management.NotificationBroadcaster;
+
+import javax.management.modelmbean.ModelMBeanAttributeInfo;
import javax.management.modelmbean.ModelMBeanOperationInfo;
import javax.management.modelmbean.ModelMBeanNotificationInfo;
import javax.management.modelmbean.ModelMBeanConstructorInfo;
@@ -29,25 +32,29 @@
import org.jboss.mx.server.StandardMBeanInvoker;
+/**
+ * @author a href=mailto:[EMAIL PROTECTED];Juha Lindfors/a.
+ * @author a href=mailto:[EMAIL PROTECTED];Trevor Squires/a.
+ */
public class StandardMetaData implements MetaDataBuilder
{
// Attributes
private Object resource = null;
private boolean isModelMetaData = false;
-
+
// Constructors --
public StandardMetaData(Object resource)
{
this.resource = resource;
}
- public StandardMetaData(Object resource, boolean isModelMetaData)
+ public StandardMetaData(Object resource, boolean isModelMetaData)
{
this(resource);
this.isModelMetaData = isModelMetaData;
}
-
+
// MetaDataBuilder implementation
public MBeanInfo build() throws NotCompliantMBeanException
{
@@ -66,12 +73,13 @@
{
String methodName = methods[i].getName();
Class[] signature = methods[i].getParameterTypes();
-
-if (methodName.startsWith(set))
+Class returnType = methods[i].getReturnType();
+
+if (methodName.startsWith(set) signature.length == 1 returnType
== Void.TYPE)
setters.put(methodName.substring(3, methodName.length()),
methods[i]);
-else if (methodName.startsWith(get) signature.length == 0)
+else if (methodName.startsWith(get) signature.length == 0
returnType != Void.TYPE)
getters.put(methodName.substring(3, methodName.length()),
methods[i]);
-else if (methodName.startsWith(is) signature.length == 0)
+else if (methodName.startsWith(is) signature.length == 0
(returnType == Boolean.class || returnType == Boolean.TYPE))
getters.put(methodName.substring(2, methodName.length()),
methods[i]);
else
operInfo.add(new MBeanOperationInfo(MBean Operation., methods[i]));
@@ -112,28 +120,28 @@
(MBeanOperationInfo[])operInfo.toArray(new MBeanOperationInfo[0]),
notifInfo
);
-
+
if (isModelMetaData)
return
[JBoss-dev] Automated JBoss Testsuite Results
JBoss daily test results SUMMARY Number of tests run: 270 Successful tests: 267 Errors:1 Failures: 2 [time of test: 18 January 2002 2:53 GMT] [java.version: 1.3.0] [java.vendor: IBM Corporation] [java.vm.version: 1.3.0] [java.vm.name: Classic VM] [java.vm.info: J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)] [os.name: Linux] [os.arch: x86] [os.version: 2.4.9-12] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS [details not shown - as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite. Its easy, just run the target 'run-basic-testsuite' from the main build.xml. PPS Come on people - there were a few days back in July 2001 when we had ZERO tests failing! Oh, and thanks - remember we love you too! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results
JBoss daily test results SUMMARY Number of tests run: 270 Successful tests: 268 Errors:1 Failures: 1 [time of test: 18 January 2002 3:23 GMT] [java.version: 1.3.1] [java.vendor: Blackdown Java-Linux Team] [java.vm.version: Blackdown-1.3.1-FCS] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-12] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS [details not shown - as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite. Its easy, just run the target 'run-basic-testsuite' from the main build.xml. PPS Come on people - there were a few days back in July 2001 when we had ZERO tests failing! Oh, and thanks - remember we love you too! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results
JBoss daily test results SUMMARY Number of tests run: 270 Successful tests: 268 Errors:1 Failures: 1 [time of test: 18 January 2002 4:11 GMT] [java.version: 1.3.1] [java.vendor: Blackdown Java-Linux Team] [java.vm.version: Blackdown-1.3.1-FCS] [java.vm.name: Classic VM] [java.vm.info: green threads, nojit] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-12] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS [details not shown - as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite. Its easy, just run the target 'run-basic-testsuite' from the main build.xml. PPS Come on people - there were a few days back in July 2001 when we had ZERO tests failing! Oh, and thanks - remember we love you too! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results
JBoss daily test results SUMMARY Number of tests run: 270 Successful tests: 268 Errors:1 Failures: 1 [time of test: 18 January 2002 4:59 GMT] [java.version: 1.3.1] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.3.1-b24] [java.vm.name: Java HotSpot(TM) Server VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-12] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS [details not shown - as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite. Its easy, just run the target 'run-basic-testsuite' from the main build.xml. PPS Come on people - there were a few days back in July 2001 when we had ZERO tests failing! Oh, and thanks - remember we love you too! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Chkconfig script for RedHat based LINUXes, 2nd edition...
here it is: jboss script has some major changes in functionality and there is an optional but useful /etc/jboss.conf file added. look through the sources... cheers ivan ps. remove .dat if there it is appended to the files. these should be called simply jboss and jboss.conf __ Do You Yahoo!? Send FREE video emails in Yahoo! Mail! http://promo.yahoo.com/videomail/ jboss Description: jboss jboss.conf Description: jboss.conf
