Bugs item #861428, was opened at 2003-12-16 18:38 Message generated for change (Comment added) made by bwang00 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=861428&group_id=22866
Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Greg Jacobi (gjacobi) >Assigned to: Ben Wang (bwang00) Summary: TreeCache object has overloaded setter methods for CacheMode Initial Comment: "bela" asked that I submit this bug based on the following post in the JBossCache forum at jboss.org: I did a little more research on why I cannot deploy the TreeCache mBean in jboss3.2.3. This is what I did: I took the as-is replSync-service.xml file, wrapped it in a .sar file and I placed it in the 'all' container. I started jboss (version=3.2.3). I got the following error: status: Deployment FAILED reason: create operation failed for package file:/C:/jboss/server/webster/deploy/CacheService.sar; - Nested throwable: (org.jboss.deployment.DeploymentException: overloaded type for attribute set: CacheMode; - nested throwable: (javax.management.NotCompliantMBeanException: overloaded type for attribute set: CacheMode)) After some review, it appears that there is a problem with the TreeCache MBean in the fact that it has multiple TreeCache.setCacheMode methods (one takes an int and one takes a string). The object StandardMetaData looks like it is inspecting the TreeCache class and it does not like multiple 'set' methods for the same paramater. So, my guess is that the problem is one of four things (I am hoping you can help me close in on which one it is). 1) I deployed it wrong. 2) TreeCache has a bug and one of the setter methods for setCacheMode should be removed or changed. 3) StandardMetaData has a bug, it should allow the overloaded setter methods. 4) Something else is wrong within jboss (catch all reason to make it sound like I covered all the bases :) Any ideas? Thanks, Greg bela's response was: Yes, you are correct - we have an overloaded setCacheMode() setter. We allow this when we run outside the container (we have our own XMLConfigurator), but inside the container, the deployer bean fails. What to do ? I can create a separate setCacheModeStr() method, so we avoid overloading. Please create a bug report on SourceForge, and I'll fix this. Bela ---------------------------------------------------------------------- >Comment By: Ben Wang (bwang00) Date: 2003-12-23 00:17 Message: Logged In: YES user_id=718568 Fixed in both 3.2 and head. Solution is to declare only one MBean method. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=861428&group_id=22866 ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
