From: umashankar.verma <do-...@jb...> - 2006-01-12 17:12:56
|
Hi, I'm facing problem when i'm trying to move from HSQL to File Persistence.I copied the null-persistence-service.xml from docs/examles/jms directory.I made required changes to set Delegate Persistence Manager..but did not work out..Can anyone help me out on this.. Exception Detail ----- 11:26:04,135 WARN [JMSContainerInvoker] JMS provider failure detected: javax.naming.NameNotFoundException: XAConnectionFactory not bound at org.jnp.server.NamingServer.getBinding(NamingServer.java:514) ------------------ Please find the contents of file which i am using for FilePersistence.. null-persistence-service.xml ============================================= <?xml version="1.0" encoding="UTF-8"?> <!-- $Id: null-persistence-service.xml,v 1.2.6.1 2005/03/14 19:18:48 ejort Exp $ --> <!-- ==================================================================== --> <!-- Persistence and caching using MSSQL --> <!-- IMPORTANT: Remove hsqldb-jdbc2-service.xml --> <!-- Provided by ma...@ma... --> <!-- ==================================================================== --> <!-- | The destination manager is the core service within JBossMQ --> <!-- --> <!-- <depends optional-attribute-name="MessageCache">jboss.mq:service=MessageCache--> <!-- <depends optional-attribute-name="PersistenceManager">jboss.mq:service=PersistenceManager--> <!-- <depends optional-attribute-name="StateManager">jboss.mq:service=StateManager--> <!-- If using a delegate persistence manager, use the in memory cache store --> <!-- for temporary queues/topics (uncomment to enable) --> <!--attribute name="TemporaryInMemory">true</attribute--> <!-- --> <!-- | The MessageCache decides where to put JBossMQ message that | are sitting around waiting to be consumed by a client. | | The memory marks are in Megabytes. Once the JVM memory usage hits | the high memory mark, the old messages in the cache will start getting | stored in the DataDirectory. As memory usage gets closer to the | Max memory mark, the amount of message kept in the memory cache aproaches 0. --> <!-- 50 60 jboss.mq:service=CacheStore --> <!-- This PersistenceManager does not store messages to disk --> <!-- All persistence requests are ignored and the cache store is in memory --> <!-- --> <!-- Use org.jboss.mq.pm.none.NewPersistenceManager to enable the --> <!-- optimized topic persistence with or without a jdbc3 delegate --> <!-- --> <!-- A delegate persistence manager can be configured --> <!-- The delegate will be used unless the queue/topic is configured with --> <!-- true --> <!-- An optional delegate for real persistence of some destinations e.g. jdbc2 --> <depends optional-attribute-name="DelegatePM">jboss.mq:service=FilePersistenceManager =============================================== file-persistence-service.xml =============================================== <?xml version="1.0" encoding="UTF-8"?> <!-- $Id: null-persistence-service.xml,v 1.2.6.1 2005/03/14 19:18:48 ejort Exp $ --> <!-- ==================================================================== --> <!-- Persistence and caching using MSSQL --> <!-- IMPORTANT: Remove hsqldb-jdbc2-service.xml --> <!-- Provided by ma...@ma... --> <!-- ==================================================================== --> <!-- | The destination manager is the core service within JBossMQ --> <depends optional-attribute-name="MessageCache">jboss.mq:service=MessageCache <depends optional-attribute-name="PersistenceManager">jboss.mq:service=PersistenceManager <depends optional-attribute-name="StateManager">jboss.mq:service=StateManager <!-- If using a delegate persistence manager, use the in memory cache store --> <!-- for temporary queues/topics (uncomment to enable) --> <!--attribute name="TemporaryInMemory">true</attribute--> <!-- | The MessageCache decides where to put JBossMQ message that | are sitting around waiting to be consumed by a client. | | The memory marks are in Megabytes. Once the JVM memory usage hits | the high memory mark, the old messages in the cache will start getting | stored in the DataDirectory. As memory usage gets closer to the | Max memory mark, the amount of message kept in the memory cache aproaches 0. --> 50 60 <depends optional-attribute-name="CacheStore">jboss.mq:service=CacheStore <depends optional-attribute-name="CacheStore">jboss.mq:service=FilePersistenceManager <!-- | The CacheStore decides where to store JBossMQ message that | that the MessageCache has decided to move in secondary storage. | | Now you can specify a absolute path by using an ULR like: | file:///c:/temp | ATTENTION: the directory MUST exists because it will not be | created. --> data/jbossmq <!-- This PersistenceManager does not store messages to disk --> <!-- All persistence requests are ignored and the cache store is in memory --> <!-- --> <!-- Use org.jboss.mq.pm.none.NewPersistenceManager to enable the --> <!-- optimized topic persistence with or without a jdbc3 delegate --> <!-- --> <!-- A delegate persistence manager can be configured --> <!-- The delegate will be used unless the queue/topic is configured with --> <!-- true --> data/jbossmq/file 100 <depends optional-attribute-name="MessageCache">jboss.mq:service=MessageCache <!-- An optional delegate for real persistence of some destinations e.g. jdbc2 --> <!-- depends optional-attribute-name="DelegatePM">jboss.mq:service=SomePersistenceManager</depends--> ================================== View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3917179#3917179 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3917179 |