Hi! AFAIK that table is part of the effort to provide HA Shared Store feature when a JDBC Journal is configured, hence I suppose that the same issue would be likely to happen for the other JDBC Journal tables as well.
The solutions I see are: 1 - have the user granted to create/modify schema in order to have the whole JDBC features working properly 2 - manually create the missing table(s) (it is not the best EVER solution but it solves the issue) IMO having proper granted users would be the best one. I hope this could help :) Cheers, Franz Il giorno ven 26 gen 2018 alle ore 09:52 Archibald <arch...@gmx.net> ha scritto: > Hi all, > > 2.4.0 introduced a new table NODE_MANAGER_STORE. This table is being > created > on startup if it doesn't exist. > But if it does exist but is empty server fails to start (seen on a oracle > database) with > > 08:43:20,510 INFO [org.apache.activemq.artemis.integration.bootstrap] > AMQ101000: Starting ActiveMQ Artemis Server > activemq_1 | can't write NODE_ID on the JDBC Node Manager Store! > > The issue is that the database user it is not always allowed (has the > proper > grants) to create/modify a schema. > > Can this be fixed? > > Thanks, > Archibald > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html >
