[JBoss-dev] [ jboss-Bugs-732728 ] File PersistenceManager broken in 3.2.1

[SourceForge.net <no...@so...>]

Bugs item #732728, was opened at 2003-05-05 08:04
Message generated for change (Comment added) made by starksm
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=732728&group_id=22866

Category: JBossMQ
Group: v3.2
>Status: Closed
Resolution: Invalid
Priority: 5
Submitted By: Corby (corby)
Assigned to: Nobody/Anonymous (nobody)
Summary: File PersistenceManager broken in 3.2.1

Initial Comment:
This problem did not exist in 3.2.0, but does exist in 
3.2.1. Easy to replicate. In jms/jbossmq-service.xml, 
simply comment out the jdbc2 Persistence Manager, 
and uncomment the file Persistence manager.

Server fails on startup with the following trace ( I am 
running Win2K, Sun jdk1.4.1_01). The problem appears 
to be related to recent code changes made by David.

java.lang.ClassCastException
        at org.jboss.mq.server.MessageCache.startService
(MessageCache.java:432)
        at org.jboss.system.ServiceMBeanSupport.start
(ServiceMBeanSupport.java:1
92)
        at sun.reflect.GeneratedMethodAccessor35.invoke
(Unknown Source)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at 
org.jboss.mx.capability.ReflectedMBeanDispatcher.invok
e(ReflectedMBea
nDispatcher.java:284)
        at org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.java:549)
        at 
org.jboss.system.ServiceController$ServiceProxy.invoke
(ServiceControl
ler.java:966)
        at $Proxy12.start(Unknown Source)
        at org.jboss.system.ServiceController.start
(ServiceController.java:392)
        at sun.reflect.GeneratedMethodAccessor7.invoke
(Unknown Source)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at 
org.jboss.mx.capability.ReflectedMBeanDispatcher.invok
e(ReflectedMBea
nDispatcher.java:284)
        at org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.java:549)
        at org.jboss.mx.util.MBeanProxyExt.invoke
(MBeanProxyExt.java:177)
        at $Proxy5.start(Unknown Source)
        at org.jboss.deployment.SARDeployer.start
(SARDeployer.java:226)
        at org.jboss.deployment.MainDeployer.start
(MainDeployer.java:832)
        at org.jboss.deployment.MainDeployer.start
(MainDeployer.java:824)
        at org.jboss.deployment.MainDeployer.deploy
(MainDeployer.java:640)
        at org.jboss.deployment.MainDeployer.deploy
(MainDeployer.java:613)
        at sun.reflect.GeneratedMethodAccessor26.invoke
(Unknown Source)



----------------------------------------------------------------------

>Comment By: Scott M Stark (starksm)
Date: 2003-05-05 10:01

Message:
Logged In: YES 
user_id=175228

Uh, I did try it or I would not have closed it. You have the
CacheStore attribute declared twice. Fix your config:

<mbean code="org.jboss.mq.server.MessageCache"
	 name="jboss.mq:service=MessageCache">
<attribute name="HighMemoryMark">500</attribute>
<attribute name="MaxMemoryMark">600</attribute>
<depends
optional-attribute-name="CacheStore">jboss.mq:service=CacheStore</de
pends>
</mbean>

----------------------------------------------------------------------

Comment By: Corby (corby)
Date: 2003-05-05 09:53

Message:
Logged In: YES 
user_id=25032

Please try it, Scott. I made the following changes to the 
DEFAULT server on 3.2.1

1) Commented JDBC Persistence Manager
2) Uncommented out file persistence manager
3) Made the MessageCache changes as described:

<mbean code="org.jboss.mq.server.MessageCache"
	 name="jboss.mq:service=MessageCache">
<attribute name="HighMemoryMark">500</attribute>
<attribute name="MaxMemoryMark">600</attribute>
		<depends optional-attribute-
name="CacheStore">jboss.mq:service=CacheStore</depends
>
<attribute 
name="CacheStore">jboss.mq:service=PersistenceManager<
/attribute>
</mbean>

4) Made sure CacheStore was pointing to a valid directory

And I still got the stacktrace. This is very easy to replicate.



----------------------------------------------------------------------

Comment By: Scott M Stark (starksm)
Date: 2003-05-05 08:50

Message:
Logged In: YES 
user_id=175228

As documented in the jbossmq-service.xml file:

ATTENTION: When the "file" or "rollinglogged" Persistence
Manager is used you have to set the "CacheStore" to the
CacheStore (the commented out line) and not to the PM itself.

This works fine with the file pm:
  <mbean code="org.jboss.mq.server.MessageCache"
    name="jboss.mq:service=MessageCache">
    <attribute name="HighMemoryMark">500</attribute>
    <attribute name="MaxMemoryMark">600</attribute>
    <attribute
name="CacheStore">jboss.mq:service=CacheStore</attribute>
  </mbean>


----------------------------------------------------------------------

Comment By: Corby (corby)
Date: 2003-05-05 08:21

Message:
Logged In: YES 
user_id=25032

I was right the first time. Even after setting the CacheStore 
settings and dependencies correctly, I get the enclosed 
stacktrace. File PersistenceManager is screwed.


----------------------------------------------------------------------

Comment By: Corby (corby)
Date: 2003-05-05 08:09

Message:
Logged In: YES 
user_id=25032

Sorry, my bad, ignore.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=732728&group_id=22866