1:41 p.m.
AFAIK there is no longer a need to have a default datasource.
- JMS is based on HornetQ and did not use a DB
- EJBtimers are using local filesystem for persistence
So I removed the module without any error.
My question is whether h2db is still not recommended for production
environment and if not the reason. Still bugs or only the
memory-consumption and cluster issues?
- Wolf
2:05 p.m.
In the transactions team we did some quickstarts to demonstrate XA
recovery. We found that H2 was not fully XA compliant so it is
definitely not recommended for production use.
If you pull it from EAP we will need to update the READMEs for some of
the quickstarts.
Mike
AFAIK there is no longer a need to have a default datasource.
- JMS is based on HornetQ and did not use a DB
- EJBtimers are using local filesystem for persistence
So I removed the module without any error.
My question is whether h2db is still not recommended for production
environment and if not the reason. Still bugs or only the
memory-consumption and cluster issues?
- Wolf
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
2:19 p.m.
I believe it will still be there for examples and quistarts, but marked as unsupported.
On 08/03/2012 15:05, Michael Musgrove wrote:
In the transactions team we did some quickstarts to demonstrate XA
recovery. We found that H2 was not fully XA compliant so it is
definitely not recommended for production use.
If you pull it from EAP we will need to update the READMEs for some of
the quickstarts.
Mike
> AFAIK there is no longer a need to have a default datasource.
> - JMS is based on HornetQ and did not use a DB
> - EJBtimers are using local filesystem for persistence
>
> So I removed the module without any error.
>
> My question is whether h2db is still not recommended for production
> environment and if not the reason. Still bugs or only the
> memory-consumption and cluster issues?
>
> - Wolf
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Dimitris Andreadis
Software Engineering Manager
JBoss Application Server
by Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
http://dandreadis.blogspot.com/
2:29 p.m.
On 03/08/2012 07:41 AM, Wolf-Dieter Fink wrote:
AFAIK there is no longer a need to have a default datasource.
- JMS is based on HornetQ and did not use a DB
- EJBtimers are using local filesystem for persistence
So I removed the module without any error.
My question is whether h2db is still not recommended for production
environment and if not the reason. Still bugs or only the
memory-consumption and cluster issues?
H2 is included to allow a quick start for examples, and it isn't needed
- as you state - in order for the application server to work.
For a list of supported databases check the JBoss Enterprise Application
Platform documentation.
Best regards,
Jesper
4440
days inactive
4440
days old
3 comments
4 participants
participants (4)
-
Dimitris Andreadis -
Jesper Pedersen -
Michael Musgrove -
Wolf-Dieter Fink