Closed glassfishrobot closed 9 years ago
Reported by arjan_t
@bshannon said: A Java EE Compatible product needs to have a default database, and it needs to be properly configured to achieve a Supported Configuration. But since the database is most likely an external service, controlling the lifecycle of that service seems outside the scope of the Java EE specification. We can't require that it be impossible to shut down the database server while the app server is running, or require that the app server shut down as soon as it notices the database server isn't running. Checking that the default database server is running when the app server starts up seems like a good idea, and probably warrants a warning if it is not, but I don't think it should be required to prevent the app server from starting.
If the database is bundled with the app server, then starting the database when the app server starts seems like a good ease of use feature, but I don't think it can be a requirement.
@bshannon said: We're not going to add this as a requirement.
This issue was imported from java.net JIRA JAVAEE_SPEC-34
Marked as won't fix on Friday, May 22nd 2015, 5:08:49 pm
In Java EE 7 the concept of a default data source was added to the platform. See #4
One specific request in that JIRA was to make sure the database backing this data source is actually available, without the user having to manually start a database that happens to be bundled with the application server:
From #4:
For a next revision of Java EE I would like to ask to take this original request into consideration again. The intend is that just like other platform services like e.g. JNDI, JMS etc the default data source should "simply be there" (as an implementation detail actually starting the backing DB can of course be delayed to the moment of first usage or when the deployment process detects an application is actually using the default data source).
See also GLASSFISH-20666