]
Matt Accola updated JBCACHE-1514:
---------------------------------
Attachment: JBossCacheCustomService.jar
When registering this Custom Service in WebSphere the classpath must also include:
commons-logging.jar
jbosscache-core.jar
jboss-common-core.jar
jcip-annotations.jar
jgroups.jar
Problems Binding JBoss Cache Instance in JNDI
---------------------------------------------
Key: JBCACHE-1514
URL:
https://jira.jboss.org/jira/browse/JBCACHE-1514
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.2.2.GA
Environment: WebSphere 6.1.0.17
Reporter: Matt Accola
Assignee: Manik Surtani
Attachments: JBossCacheCustomService.jar
Attempting to create a JBoss Cache instance and bind to JNDI for use by multiple
applications.
In WebSphere 6.1 the best way to do this is to create a Custom Service,
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/co....
I have attached a simple Custom Service which creates a new cache instance from an XML
configuration file, obtains an InitialContext and attempts to bind the
org.jboss.cache.Cache reference. The Custom Service is in the attached
JBossCacheCustomService.jar.
When I try to start the server I get the following error:
com.ibm.ws.naming.util.CannotBindObjectException: Object is not of any type which can be
bound. As described in the WebSphere 6.1 Info Center,
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/co...
, this is because the object which is being bound is not Serializable.
I have also attached the complete log of the server startup.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: