(11:27:32 AM) mazz: I just noticed something - installer deletes all JMS messages found in the JMS tables (ConfigurationBean line 521 calls serverInfo.cleanJmsTables). (11:27:50 AM) mazz: what happens if I am installing a new server in an existing cloud and that cloud's other servers are up and running? (11:28:02 AM) mazz: and we are currently processing JMS messages over there? (11:29:46 AM) joseph42: hmm...that's not good (11:30:16 AM) joseph42: is there a way to override that (11:30:30 AM) joseph42: for instances where we're just adding another server? I think we should get rid of this. Now that we fixed our JMS problems before (the OOB cache bug), I don't think we need to blow away the JMS table anymore. If we think we'll still need this, then we must make this optional - with a default being OFF. Otherwise, the user might accidentally destroy our JMS messages being sent by other servers in the cloud.
Even though we shouldn't blindly purge the JMS_MESSAGES table, we should be able to have a way to truncate that table somehow. I just had a case where the server got in a bad state. There ended up 72,000 rows in JMS_MESSAGES. The server fails to properly start with this many messages persisted. Attached is the rhq server log that shows the kinds of messages you get at server startup when this happens.
Because JMS currently uses XA, this is going to be related to RHQ-1017 - if we are to clear the tx object store, we should also purge the JMS_MESSAGES table (and possibly the JMS_TRANSACTIONS table)
This may be related to the "remove XA from JMS configuration" JIRA - RHQ-938. I'm linking this issue just so we don't lose this possible relationship.
making this a blocker for 1.2 since it is related to other blocker issues
priority to major.
Need to document either putting the servers in MM before upgrading/adding or stating that inflight alerts could be lost during upgrade/add of a server
BTW: for the record, the installer never touches the JMS tables anymore... this method still exists for future use, but its never called right now. org.rhq.enterprise.installer.ServerInformation.cleanJmsTables(Properties)
Ok, pushing this to the next release since we aren't actually purging from the JMS tables
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1032 Imported an attachment (id=368483) This bug is related to RHQ-1017 This bug is related to RHQ-938
Stealing this.
Blocking install guide tracker.
(4:44:31 PM) ccrouch: mazz: can this be closed https://bugzilla.redhat.com/show_bug.cgi?id=534215 ? since we're not doing any JMS purging any longer?
this can be closed as per my earlier comments about the installer not purging the jms tables anymore