Best practices for creating JMS tables in JBoss EAP
Issue
-
We are curious about the best practices surrounding the creation of the database tables to support a jms queue.
-
- The default settings create the tables on startup which works but generates a lot of error messages on subsequent startups.
-
- What about creating the tables before starting?
-
- What about upgrades where the table structure may change?
-
- Should the JMS tables be in a schema by themselves or in the same schema with the application tables?
-
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 4.3
- 5.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
