Same issue here, although not after migrating, but with the original hsqldb. Anybody has any idea?
Current JBoss version - 5.1.0 GA.
Also, very strange, the error doesn't show up all the time. Restarting the "all" configuration 5 times will throw the error 3 times. 2 times will start ok. Found somewhere a suggestion about playing with the ...-persistence-settings.xml, but no real fix.
In what way is this jBPM related?
Ronald, it took you one month and a half to ask that question?
In case this thread is completely in the wrong place, then you should be able to suggest a better place, like" clustering", "race conditions at startup", "general server issues" or "beginner's corner". More, in case you do have an idea what's going on, you could really write down what you have, and whoever interested will take it from there.
If you really don't have ANY useful suggestion (as your seemingly annoyed answer shows), a more decent approach you could take would be to ignore this thread.
Sorry, no not annoyed at all... Just really wondering. Since the topic explicitly includes jBPM, and jBPM in the latest release supports jms, but I could not make anything up about this.
The trigger was your new post (I do occasionally miss a post)
So if you have more info (kind of what I meant with 'what has this to do with jBPM' (not a native English speaker sorry), please post it here and we are more than willing to help. What was posted is just way to little (hope you can understand that)
thanks Ronald, I can only assume that the original poster encountered the error while playing with the jBPM and then believing it was related. I personally ran into the issue while running the "all" configuration of the JBOSS AS and after I tried to configure some MDBs (so, as far as I know, unrelated to jBPM). Since the original post was in this section of forum, I put my question here as well...
From the little debugging I was able to do and from the fact that the error is inconsistent, I tend to believe there is a race condition which delays - sometimes (when the clustering is "on"?) - the initialization of the "PostOffice" (not sure what that is). In any case, the
postOffice = (PostOffice)JMXAccessor.getJMXAttributeOverSecurity(getServer(), postOfficeObjectName, "Instance");in the ServerPeer class (line 1377) returns null.More debugging when I can get back to this, hopefully soon...ranjix
Obviously, regarding this error, is my fault. There is indeed a race condition, fixable by adding
into the definition of the topics (all/deploy/messaging/destinations-service.xml file). As soon as I put the line in, for each of my topics, the error disappeared. I assume something similar happened in the case of the original poster...
all the best/ranjix
Sorry for not Updating the thread,
null null , you are right , the problem was exactly that. by adding
will solves the problem
Sorry for the wrong heading for the post .