My biggest hope for 7.1 was that I would never, ever have another event subsystem issue. Unfortunately, it looks like my nemesis is back to fight another battle.
With 7.1 installed on 32bit W2k3 using MSSQL 2008 as the DB, I noticed shortly after installation that my event subsystem was not running. Thinking it might be an install problem, I looked through the installer log and didn't find anything.
After a lot of grepping, I found the log for it (conveniently located in \ApplicationContainer\server\default\deploy\activemq-ear-5.3.0.ear\activemq-ra.rar [where else would you think it might be?]), and found messages similar to this inside it:
[INDENT] ERROR BrokerService - Failed to start ActiveMQ JMS Message Broker. Reason: java.io.IOException: Failed to get last broker message id: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'ACTIVEMQ_MSGS'.[/INDENT]
I checked the database, and found that I only had two tables, ACTIVEMQ_LOCKS and ACTIVEMQ_ACKS. Further exploration of the log revealed a failure to create the tables. After some research, I discovered that ActiveMQ will initialize the database on startup if it doesn't find the tables it is looking for, but I could not find a clear reason for it to fail to do so (especially since it was creating two of the tables).
Digging in the issue log for ActiveMQ, I found this:
https://issues.apache.org/activemq/browse/AMQ-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55586#action_55586Apparently this issue (or at least one very similar to it) can be caused by an incorrect dataSource attribute on the persistence layer. I am currently waiting to hear back from support about their recommendation for fixing the problem.
Has anyone else run into an issue using MSSQL2008 for the iwevent database, and if so, what did you do to fix it?
I'm currently