[JBoss JIRA] Created: (JBCACHE-1053) RmiCacheServer thinks it can create a mbean proxy to a CacheImpl
10:47 p.m.
RmiCacheServer thinks it can create a mbean proxy to a CacheImpl
----------------------------------------------------------------
Key: JBCACHE-1053
URL: http://jira.jboss.com/jira/browse/JBCACHE-1053
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.0.0.CR1
Reporter: Brian Stansberry
Assigned To: Manik Surtani
RmiCacheServer.start() has this:
MBeanServer server = JmxUtil.getMBeanServer();
if (cacheName != null && server != null)
{
cache = (CacheImpl) MBeanServerInvocationHandler.newProxyInstance(server,
cacheName, CacheImpl.class, false);
}
There won't be anything registered in JMX that you can proxy with the CacheImpl API.
This could work:
MBeanServer server = JmxUtil.getMBeanServer();
if (cacheName != null && server != null)
{
CacheJmxWrapperMBean wrapper = (CacheJmxWrapperMBean )
MBeanServerInvocationHandler.newProxyInstance(server, cacheName,
CacheJmxWrapperMBean.class, false);
cache = (CacheImpl) wrapper.getCache();
}
In this case, cache is no longer a JMX proxy though, it's a ref to the underlying
cache.
Probably better is just to get rid of this lookup and require injection of the CacheImpl
or the CacheJmxWrapper.
Also, it would be nice if RemoteTreeCacheImpl could delegate to Cache instead of
CacheImpl. Then there's no need to cast the wrapper.getCache() call and it's
simpler to do dependency injection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:49 p.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-1053) RmiCacheServer thinks it can create a mbean proxy to a CacheImpl
[ http://jira.jboss.com/jira/browse/JBCACHE-1053?page=comments#action_12362023 ]
Brian Stansberry commented on JBCACHE-1053:
-------------------------------------------
Same problem applies to TcpCacheServer.
RmiCacheServer thinks it can create a mbean proxy to a CacheImpl
----------------------------------------------------------------
Key: JBCACHE-1053
URL: http://jira.jboss.com/jira/browse/JBCACHE-1053
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.CR1
Reporter: Brian Stansberry
Assigned To: Manik Surtani
RmiCacheServer.start() has this:
MBeanServer server = JmxUtil.getMBeanServer();
if (cacheName != null && server != null)
{
cache = (CacheImpl) MBeanServerInvocationHandler.newProxyInstance(server,
cacheName, CacheImpl.class, false);
}
There won't be anything registered in JMX that you can proxy with the CacheImpl API.
This could work:
MBeanServer server = JmxUtil.getMBeanServer();
if (cacheName != null && server != null)
{
CacheJmxWrapperMBean wrapper = (CacheJmxWrapperMBean )
MBeanServerInvocationHandler.newProxyInstance(server, cacheName,
CacheJmxWrapperMBean.class, false);
cache = (CacheImpl) wrapper.getCache();
}
In this case, cache is no longer a JMX proxy though, it's a ref to the underlying
cache.
Probably better is just to get rid of this lookup and require injection of the CacheImpl
or the CacheJmxWrapper.
Also, it would be nice if RemoteTreeCacheImpl could delegate to Cache instead of
CacheImpl. Then there's no need to cast the wrapper.getCache() call and it's
simpler to do dependency injection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:43 a.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1053) RmiCacheServer thinks it can create a mbean proxy to a CacheImpl
[ http://jira.jboss.com/jira/browse/JBCACHE-1053?page=all ]
Manik Surtani updated JBCACHE-1053:
-----------------------------------
Fix Version/s: 2.0.0.CR2
RMICacheServer/Loader should be deprecated/removed.
Will fix for TCP though.
RmiCacheServer thinks it can create a mbean proxy to a CacheImpl
----------------------------------------------------------------
Key: JBCACHE-1053
URL: http://jira.jboss.com/jira/browse/JBCACHE-1053
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.CR1
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 2.0.0.CR2
RmiCacheServer.start() has this:
MBeanServer server = JmxUtil.getMBeanServer();
if (cacheName != null && server != null)
{
cache = (CacheImpl) MBeanServerInvocationHandler.newProxyInstance(server,
cacheName, CacheImpl.class, false);
}
There won't be anything registered in JMX that you can proxy with the CacheImpl API.
This could work:
MBeanServer server = JmxUtil.getMBeanServer();
if (cacheName != null && server != null)
{
CacheJmxWrapperMBean wrapper = (CacheJmxWrapperMBean )
MBeanServerInvocationHandler.newProxyInstance(server, cacheName,
CacheJmxWrapperMBean.class, false);
cache = (CacheImpl) wrapper.getCache();
}
In this case, cache is no longer a JMX proxy though, it's a ref to the underlying
cache.
Probably better is just to get rid of this lookup and require injection of the CacheImpl
or the CacheJmxWrapper.
Also, it would be nice if RemoteTreeCacheImpl could delegate to Cache instead of
CacheImpl. Then there's no need to cast the wrapper.getCache() call and it's
simpler to do dependency injection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:20 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-1053) RmiCacheServer thinks it can create a mbean proxy to a CacheImpl
[ http://jira.jboss.com/jira/browse/JBCACHE-1053?page=comments#action_12362674 ]
Manik Surtani commented on JBCACHE-1053:
----------------------------------------
Dropping the RMI delegating CL solves the RemoteTreeCacheImpl comment above
RmiCacheServer thinks it can create a mbean proxy to a CacheImpl
----------------------------------------------------------------
Key: JBCACHE-1053
URL: http://jira.jboss.com/jira/browse/JBCACHE-1053
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.CR1
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 2.0.0.CR2
RmiCacheServer.start() has this:
MBeanServer server = JmxUtil.getMBeanServer();
if (cacheName != null && server != null)
{
cache = (CacheImpl) MBeanServerInvocationHandler.newProxyInstance(server,
cacheName, CacheImpl.class, false);
}
There won't be anything registered in JMX that you can proxy with the CacheImpl API.
This could work:
MBeanServer server = JmxUtil.getMBeanServer();
if (cacheName != null && server != null)
{
CacheJmxWrapperMBean wrapper = (CacheJmxWrapperMBean )
MBeanServerInvocationHandler.newProxyInstance(server, cacheName,
CacheJmxWrapperMBean.class, false);
cache = (CacheImpl) wrapper.getCache();
}
In this case, cache is no longer a JMX proxy though, it's a ref to the underlying
cache.
Probably better is just to get rid of this lookup and require injection of the CacheImpl
or the CacheJmxWrapper.
Also, it would be nice if RemoteTreeCacheImpl could delegate to Cache instead of
CacheImpl. Then there's no need to cast the wrapper.getCache() call and it's
simpler to do dependency injection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:22 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-1053) RmiCacheServer thinks it can create a mbean proxy to a CacheImpl
[ http://jira.jboss.com/jira/browse/JBCACHE-1053?page=comments#action_12362676 ]
Manik Surtani commented on JBCACHE-1053:
----------------------------------------
Regarding the TCP cache loader and the lookup, I favour injection over looking up the JMX
wrapper mbean.
I've added a setCache() method instead and have removed the lookup code.
Will need to update docs and examples. Brian, could you update the sample -service.xml
file with an AS 5 style one with the necessary injection?
RmiCacheServer thinks it can create a mbean proxy to a CacheImpl
----------------------------------------------------------------
Key: JBCACHE-1053
URL: http://jira.jboss.com/jira/browse/JBCACHE-1053
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.CR1
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 2.0.0.CR2
RmiCacheServer.start() has this:
MBeanServer server = JmxUtil.getMBeanServer();
if (cacheName != null && server != null)
{
cache = (CacheImpl) MBeanServerInvocationHandler.newProxyInstance(server,
cacheName, CacheImpl.class, false);
}
There won't be anything registered in JMX that you can proxy with the CacheImpl API.
This could work:
MBeanServer server = JmxUtil.getMBeanServer();
if (cacheName != null && server != null)
{
CacheJmxWrapperMBean wrapper = (CacheJmxWrapperMBean )
MBeanServerInvocationHandler.newProxyInstance(server, cacheName,
CacheJmxWrapperMBean.class, false);
cache = (CacheImpl) wrapper.getCache();
}
In this case, cache is no longer a JMX proxy though, it's a ref to the underlying
cache.
Probably better is just to get rid of this lookup and require injection of the CacheImpl
or the CacheJmxWrapper.
Also, it would be nice if RemoteTreeCacheImpl could delegate to Cache instead of
CacheImpl. Then there's no need to cast the wrapper.getCache() call and it's
simpler to do dependency injection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:34 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-1053) RmiCacheServer thinks it can create a mbean proxy to a CacheImpl
[ http://jira.jboss.com/jira/browse/JBCACHE-1053?page=comments#action_12362677 ]
Manik Surtani commented on JBCACHE-1053:
----------------------------------------
Note setCache() takes a CacheSPI.
RmiCacheServer thinks it can create a mbean proxy to a CacheImpl
----------------------------------------------------------------
Key: JBCACHE-1053
URL: http://jira.jboss.com/jira/browse/JBCACHE-1053
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.CR1
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 2.0.0.CR2
RmiCacheServer.start() has this:
MBeanServer server = JmxUtil.getMBeanServer();
if (cacheName != null && server != null)
{
cache = (CacheImpl) MBeanServerInvocationHandler.newProxyInstance(server,
cacheName, CacheImpl.class, false);
}
There won't be anything registered in JMX that you can proxy with the CacheImpl API.
This could work:
MBeanServer server = JmxUtil.getMBeanServer();
if (cacheName != null && server != null)
{
CacheJmxWrapperMBean wrapper = (CacheJmxWrapperMBean )
MBeanServerInvocationHandler.newProxyInstance(server, cacheName,
CacheJmxWrapperMBean.class, false);
cache = (CacheImpl) wrapper.getCache();
}
In this case, cache is no longer a JMX proxy though, it's a ref to the underlying
cache.
Probably better is just to get rid of this lookup and require injection of the CacheImpl
or the CacheJmxWrapper.
Also, it would be nice if RemoteTreeCacheImpl could delegate to Cache instead of
CacheImpl. Then there's no need to cast the wrapper.getCache() call and it's
simpler to do dependency injection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:34 a.m.
New subject: [JBoss JIRA] Assigned: (JBCACHE-1053) RmiCacheServer thinks it can create a mbean proxy to a CacheImpl
[ http://jira.jboss.com/jira/browse/JBCACHE-1053?page=all ]
Manik Surtani reassigned JBCACHE-1053:
--------------------------------------
Assignee: Brian Stansberry (was: Manik Surtani)
RmiCacheServer thinks it can create a mbean proxy to a CacheImpl
----------------------------------------------------------------
Key: JBCACHE-1053
URL: http://jira.jboss.com/jira/browse/JBCACHE-1053
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.CR1
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: 2.0.0.CR2
RmiCacheServer.start() has this:
MBeanServer server = JmxUtil.getMBeanServer();
if (cacheName != null && server != null)
{
cache = (CacheImpl) MBeanServerInvocationHandler.newProxyInstance(server,
cacheName, CacheImpl.class, false);
}
There won't be anything registered in JMX that you can proxy with the CacheImpl API.
This could work:
MBeanServer server = JmxUtil.getMBeanServer();
if (cacheName != null && server != null)
{
CacheJmxWrapperMBean wrapper = (CacheJmxWrapperMBean )
MBeanServerInvocationHandler.newProxyInstance(server, cacheName,
CacheJmxWrapperMBean.class, false);
cache = (CacheImpl) wrapper.getCache();
}
In this case, cache is no longer a JMX proxy though, it's a ref to the underlying
cache.
Probably better is just to get rid of this lookup and require injection of the CacheImpl
or the CacheJmxWrapper.
Also, it would be nice if RemoteTreeCacheImpl could delegate to Cache instead of
CacheImpl. Then there's no need to cast the wrapper.getCache() call and it's
simpler to do dependency injection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:19 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-1053) RmiCacheServer thinks it can create a mbean proxy to a CacheImpl
[ http://jira.jboss.com/jira/browse/JBCACHE-1053?page=comments#action_12362697 ]
Brian Stansberry commented on JBCACHE-1053:
-------------------------------------------
Suire will do. I expect I'll also want to add a setter for a CacheJmxWrapper as well
to make it easy to inject a cache created that way. Internally it will call
CacheJmxWrapper.getCache().
RmiCacheServer thinks it can create a mbean proxy to a CacheImpl
----------------------------------------------------------------
Key: JBCACHE-1053
URL: http://jira.jboss.com/jira/browse/JBCACHE-1053
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.CR1
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: 2.0.0.CR2
RmiCacheServer.start() has this:
MBeanServer server = JmxUtil.getMBeanServer();
if (cacheName != null && server != null)
{
cache = (CacheImpl) MBeanServerInvocationHandler.newProxyInstance(server,
cacheName, CacheImpl.class, false);
}
There won't be anything registered in JMX that you can proxy with the CacheImpl API.
This could work:
MBeanServer server = JmxUtil.getMBeanServer();
if (cacheName != null && server != null)
{
CacheJmxWrapperMBean wrapper = (CacheJmxWrapperMBean )
MBeanServerInvocationHandler.newProxyInstance(server, cacheName,
CacheJmxWrapperMBean.class, false);
cache = (CacheImpl) wrapper.getCache();
}
In this case, cache is no longer a JMX proxy though, it's a ref to the underlying
cache.
Probably better is just to get rid of this lookup and require injection of the CacheImpl
or the CacheJmxWrapper.
Also, it would be nice if RemoteTreeCacheImpl could delegate to Cache instead of
CacheImpl. Then there's no need to cast the wrapper.getCache() call and it's
simpler to do dependency injection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:13 p.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1053) RmiCacheServer and TcpCacheServer try to create an mbean proxy to a CacheImpl
[ http://jira.jboss.com/jira/browse/JBCACHE-1053?page=all ]
Brian Stansberry updated JBCACHE-1053:
--------------------------------------
Summary: RmiCacheServer and TcpCacheServer try to create an mbean proxy to a CacheImpl
(was: RmiCacheServer thinks it can create a mbean proxy to a CacheImpl)
RmiCacheServer and TcpCacheServer try to create an mbean proxy to a
CacheImpl
-----------------------------------------------------------------------------
Key: JBCACHE-1053
URL: http://jira.jboss.com/jira/browse/JBCACHE-1053
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.CR1
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: 2.0.0.CR2
RmiCacheServer.start() has this:
MBeanServer server = JmxUtil.getMBeanServer();
if (cacheName != null && server != null)
{
cache = (CacheImpl) MBeanServerInvocationHandler.newProxyInstance(server,
cacheName, CacheImpl.class, false);
}
There won't be anything registered in JMX that you can proxy with the CacheImpl API.
This could work:
MBeanServer server = JmxUtil.getMBeanServer();
if (cacheName != null && server != null)
{
CacheJmxWrapperMBean wrapper = (CacheJmxWrapperMBean )
MBeanServerInvocationHandler.newProxyInstance(server, cacheName,
CacheJmxWrapperMBean.class, false);
cache = (CacheImpl) wrapper.getCache();
}
In this case, cache is no longer a JMX proxy though, it's a ref to the underlying
cache.
Probably better is just to get rid of this lookup and require injection of the CacheImpl
or the CacheJmxWrapper.
Also, it would be nice if RemoteTreeCacheImpl could delegate to Cache instead of
CacheImpl. Then there's no need to cast the wrapper.getCache() call and it's
simpler to do dependency injection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:38 a.m.
New subject: [JBoss JIRA] Closed: (JBCACHE-1053) RmiCacheServer and TcpCacheServer try to create an mbean proxy to a CacheImpl
[ http://jira.jboss.com/jira/browse/JBCACHE-1053?page=all ]
Brian Stansberry closed JBCACHE-1053.
-------------------------------------
Resolution: Done
RmiCacheServer and TcpCacheServer try to create an mbean proxy to a
CacheImpl
-----------------------------------------------------------------------------
Key: JBCACHE-1053
URL: http://jira.jboss.com/jira/browse/JBCACHE-1053
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.CR1
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: 2.0.0.CR2
RmiCacheServer.start() has this:
MBeanServer server = JmxUtil.getMBeanServer();
if (cacheName != null && server != null)
{
cache = (CacheImpl) MBeanServerInvocationHandler.newProxyInstance(server,
cacheName, CacheImpl.class, false);
}
There won't be anything registered in JMX that you can proxy with the CacheImpl API.
This could work:
MBeanServer server = JmxUtil.getMBeanServer();
if (cacheName != null && server != null)
{
CacheJmxWrapperMBean wrapper = (CacheJmxWrapperMBean )
MBeanServerInvocationHandler.newProxyInstance(server, cacheName,
CacheJmxWrapperMBean.class, false);
cache = (CacheImpl) wrapper.getCache();
}
In this case, cache is no longer a JMX proxy though, it's a ref to the underlying
cache.
Probably better is just to get rid of this lookup and require injection of the CacheImpl
or the CacheJmxWrapper.
Also, it would be nice if RemoteTreeCacheImpl could delegate to Cache instead of
CacheImpl. Then there's no need to cast the wrapper.getCache() call and it's
simpler to do dependency injection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7000
days inactive
7012
days old
9 comments
2 participants
participants (2)
-
Brian Stansberry (JIRA) -
Manik Surtani (JIRA)