Re: HA-JDBC via tomee.xml Resource factory/cluster properties ignored
No idea why you have a NPE but do you know http://rmannibucau.wordpress.com/2013/04/26/tomeeopenejb-and-failover-of-datasources/? Isnt it what you desire more or less? Le 3 nov. 2013 05:11, Howard W. Smith, Jr. smithh032...@gmail.com a écrit : trying to get it done via tomee.xml, ha-jdbc-cluster.xml, and java option -Dha-jdbc... seems to help, but i definitely need help...i been reporting my progress with this on ha-jdbc forum[1]... i hope to get some help with this, soon. [1] https://sourceforge.net/p/ha-jdbc/discussion/383396/thread/5f4dc302/ On Sat, Nov 2, 2013 at 3:44 PM, Howard W. Smith, Jr. smithh032...@gmail.com wrote: okay, I'm seeing what you said (not get jta as easily, when using context.xml). thanks. On Sat, Nov 2, 2013 at 3:39 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: If you use context.xml youll not get as easily jta. You can set Resource attribute class-name to the impl class and setXxx using xxx as property attribute (factory for instance) Le 2 nov. 2013 18:10, Howard W. Smith, Jr. smithh032...@gmail.com a écrit : Per [Avoid properties conflict when configuring TomEE DataSource][1], I added ignoreDefaultValues=true to Resource in tomee.xml, Resource id=jdbc/mcmsJta type=javax.sql.DataSource JdbcDriver net.sf.hajdbc.sql.DataSource IgnoreDefaultValues true JtaManaged true jmxEnabled true LogSql false /Resource and the result are the [exceptions in the log file][2]. the exceptions seem to prove that I need to add the following to Resource .../ cluster=... factory=... can you please advise how I can add these two parameters to Resource .../ in tomee.xml, or should I revert to META-INF/context.xml? [1]: http://rmannibucau.wordpress.com/2012/11/08/avoid-properties-conflict-when-configuring-tomee-datasource/ [2]: https://gist.github.com/smithh032772/7279765#file-log3-txt On Sat, Nov 2, 2013 at 11:09 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Why workaround? That how it works
Re: [test resources] persistence.xml
Hi
Both are in the classpath for different ejbmodule so that s ok.
Maybe have a look to altdd to use test.persistence.xml in src/main/resources
Le 3 nov. 2013 00:00, Matthias Wessendorf mat...@apache.org a écrit :
Hi,
when running unit tests - where I have a
src/test/resources/META-INF/persistence.xml file - I am wondering why the
one in src/main is also included.
Wouldn't the one in test be the 'right' one ?
See also [1]
-Matthias
[1]
https://github.com/matzew/tomee/blob/trunk/examples/jpa-hibernate/src/test/resources/META-INF/persistence.xml
From the LOG (note the 'PersistenceUnit(name=movie-unit-TEST' and the
'PersistenceUnit(name=movie-unit'):
INFO - Configuring PersistenceUnit(name=movie-unit-TEST,
provider=org.hibernate.ejb.HibernatePersistence)
INFO - Auto-creating a Resource with id 'movieDatabaseNonJta' of type
'DataSource for 'movie-unit-TEST'.
INFO - Configuring Service(id=movieDatabaseNonJta, type=Resource,
provider-id=movieDatabase)
INFO - Creating Resource(id=movieDatabaseNonJta)
INFO - Adjusting PersistenceUnit movie-unit-TEST non-jta-data-source to
Resource ID 'movieDatabaseNonJta' from 'movieDatabaseUnmanaged'
INFO - Configuring PersistenceUnit(name=movie-unit,
provider=org.hibernate.ejb.HibernatePersistence)
INFO - Adjusting PersistenceUnit movie-unit non-jta-data-source to
Resource ID 'movieDatabaseNonJta' from 'movieDatabaseUnmanaged'
INFO - Enterprise application
/Users/matzew/TEMP/TomEEFix/examples/jpa-hibernate loaded.
INFO - Assembling app: /Users/matzew/TEMP/TomEEFix/examples/jpa-hibernate
INFO - HV01: Hibernate Validator 4.3.0.Final
INFO - HV02: Ignoring XML configuration.
INFO - HV02: Ignoring XML configuration.
INFO - HCANN01: Hibernate Commons Annotations {4.0.1.Final}
INFO - HHH000412: Hibernate Core {4.1.8.Final}
INFO - HHH000206: hibernate.properties not found
INFO - HHH21: Bytecode provider name : javassist
INFO - HHH000204: Processing PersistenceUnitInfo [
name: movie-unit-TEST
...]
INFO - HHH000130: Instantiating explicit connection provider:
org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
INFO - HHH000400: Using dialect: org.hibernate.dialect.HSQLDialect
INFO - HHH000268: Transaction strategy:
org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory
INFO - HHH000397: Using ASTQueryTranslatorFactory
INFO - HHH000227: Running hbm2ddl schema export
INFO - HHH000230: Schema export complete
INFO - PersistenceUnit(name=movie-unit-TEST,
provider=org.hibernate.ejb.HibernatePersistence) - provider time 2143ms
INFO - HHH000204: Processing PersistenceUnitInfo [
name: movie-unit
...]
INFO - HHH000130: Instantiating explicit connection provider:
org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
INFO - HHH000400: Using dialect: org.hibernate.dialect.HSQLDialect
INFO - HHH000268: Transaction strategy:
org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory
INFO - HHH000397: Using ASTQueryTranslatorFactory
INFO - HHH000227: Running hbm2ddl schema export
INFO - HHH000230: Schema export complete
INFO - PersistenceUnit(name=movie-unit,
provider=org.hibernate.ejb.HibernatePersistence) - provider time 673ms
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
Re: [test resources] persistence.xml
Hrm,
for me using a src/main/resources/META-INF/test.persistence.xml feels a
bit wrong, especially since test-ware should be stored w/in src/test,
like src/test/resources/META-INF/persistence.xml;
-Matthias
On Sun, Nov 3, 2013 at 9:17 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote:
Hi
Both are in the classpath for different ejbmodule so that s ok.
Maybe have a look to altdd to use test.persistence.xml in
src/main/resources
Le 3 nov. 2013 00:00, Matthias Wessendorf mat...@apache.org a écrit :
Hi,
when running unit tests - where I have a
src/test/resources/META-INF/persistence.xml file - I am wondering why the
one in src/main is also included.
Wouldn't the one in test be the 'right' one ?
See also [1]
-Matthias
[1]
https://github.com/matzew/tomee/blob/trunk/examples/jpa-hibernate/src/test/resources/META-INF/persistence.xml
From the LOG (note the 'PersistenceUnit(name=movie-unit-TEST' and the
'PersistenceUnit(name=movie-unit'):
INFO - Configuring PersistenceUnit(name=movie-unit-TEST,
provider=org.hibernate.ejb.HibernatePersistence)
INFO - Auto-creating a Resource with id 'movieDatabaseNonJta' of type
'DataSource for 'movie-unit-TEST'.
INFO - Configuring Service(id=movieDatabaseNonJta, type=Resource,
provider-id=movieDatabase)
INFO - Creating Resource(id=movieDatabaseNonJta)
INFO - Adjusting PersistenceUnit movie-unit-TEST non-jta-data-source to
Resource ID 'movieDatabaseNonJta' from 'movieDatabaseUnmanaged'
INFO - Configuring PersistenceUnit(name=movie-unit,
provider=org.hibernate.ejb.HibernatePersistence)
INFO - Adjusting PersistenceUnit movie-unit non-jta-data-source to
Resource ID 'movieDatabaseNonJta' from 'movieDatabaseUnmanaged'
INFO - Enterprise application
/Users/matzew/TEMP/TomEEFix/examples/jpa-hibernate loaded.
INFO - Assembling app: /Users/matzew/TEMP/TomEEFix/examples/jpa-hibernate
INFO - HV01: Hibernate Validator 4.3.0.Final
INFO - HV02: Ignoring XML configuration.
INFO - HV02: Ignoring XML configuration.
INFO - HCANN01: Hibernate Commons Annotations {4.0.1.Final}
INFO - HHH000412: Hibernate Core {4.1.8.Final}
INFO - HHH000206: hibernate.properties not found
INFO - HHH21: Bytecode provider name : javassist
INFO - HHH000204: Processing PersistenceUnitInfo [
name: movie-unit-TEST
...]
INFO - HHH000130: Instantiating explicit connection provider:
org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
INFO - HHH000400: Using dialect: org.hibernate.dialect.HSQLDialect
INFO - HHH000268: Transaction strategy:
org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory
INFO - HHH000397: Using ASTQueryTranslatorFactory
INFO - HHH000227: Running hbm2ddl schema export
INFO - HHH000230: Schema export complete
INFO - PersistenceUnit(name=movie-unit-TEST,
provider=org.hibernate.ejb.HibernatePersistence) - provider time 2143ms
INFO - HHH000204: Processing PersistenceUnitInfo [
name: movie-unit
...]
INFO - HHH000130: Instantiating explicit connection provider:
org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
INFO - HHH000400: Using dialect: org.hibernate.dialect.HSQLDialect
INFO - HHH000268: Transaction strategy:
org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory
INFO - HHH000397: Using ASTQueryTranslatorFactory
INFO - HHH000227: Running hbm2ddl schema export
INFO - HHH000230: Schema export complete
INFO - PersistenceUnit(name=movie-unit,
provider=org.hibernate.ejb.HibernatePersistence) - provider time 673ms
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
Re: [test resources] persistence.xml
So use arquillian or applicationcomposer.
You use EJBContainer i think which is a standalone solution and not a test
one. That said you can exclude the resource configuring mvn jar plugin
Le 3 nov. 2013 09:41, Matthias Wessendorf mat...@apache.org a écrit :
Hrm,
for me using a src/main/resources/META-INF/test.persistence.xml feels a
bit wrong, especially since test-ware should be stored w/in src/test,
like src/test/resources/META-INF/persistence.xml;
-Matthias
On Sun, Nov 3, 2013 at 9:17 AM, Romain Manni-Bucau rmannibu...@gmail.com
wrote:
Hi
Both are in the classpath for different ejbmodule so that s ok.
Maybe have a look to altdd to use test.persistence.xml in
src/main/resources
Le 3 nov. 2013 00:00, Matthias Wessendorf mat...@apache.org a écrit
:
Hi,
when running unit tests - where I have a
src/test/resources/META-INF/persistence.xml file - I am wondering why
the
one in src/main is also included.
Wouldn't the one in test be the 'right' one ?
See also [1]
-Matthias
[1]
https://github.com/matzew/tomee/blob/trunk/examples/jpa-hibernate/src/test/resources/META-INF/persistence.xml
From the LOG (note the 'PersistenceUnit(name=movie-unit-TEST' and the
'PersistenceUnit(name=movie-unit'):
INFO - Configuring PersistenceUnit(name=movie-unit-TEST,
provider=org.hibernate.ejb.HibernatePersistence)
INFO - Auto-creating a Resource with id 'movieDatabaseNonJta' of type
'DataSource for 'movie-unit-TEST'.
INFO - Configuring Service(id=movieDatabaseNonJta, type=Resource,
provider-id=movieDatabase)
INFO - Creating Resource(id=movieDatabaseNonJta)
INFO - Adjusting PersistenceUnit movie-unit-TEST non-jta-data-source
to
Resource ID 'movieDatabaseNonJta' from 'movieDatabaseUnmanaged'
INFO - Configuring PersistenceUnit(name=movie-unit,
provider=org.hibernate.ejb.HibernatePersistence)
INFO - Adjusting PersistenceUnit movie-unit non-jta-data-source to
Resource ID 'movieDatabaseNonJta' from 'movieDatabaseUnmanaged'
INFO - Enterprise application
/Users/matzew/TEMP/TomEEFix/examples/jpa-hibernate loaded.
INFO - Assembling app:
/Users/matzew/TEMP/TomEEFix/examples/jpa-hibernate
INFO - HV01: Hibernate Validator 4.3.0.Final
INFO - HV02: Ignoring XML configuration.
INFO - HV02: Ignoring XML configuration.
INFO - HCANN01: Hibernate Commons Annotations {4.0.1.Final}
INFO - HHH000412: Hibernate Core {4.1.8.Final}
INFO - HHH000206: hibernate.properties not found
INFO - HHH21: Bytecode provider name : javassist
INFO - HHH000204: Processing PersistenceUnitInfo [
name: movie-unit-TEST
...]
INFO - HHH000130: Instantiating explicit connection provider:
org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
INFO - HHH000400: Using dialect: org.hibernate.dialect.HSQLDialect
INFO - HHH000268: Transaction strategy:
org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory
INFO - HHH000397: Using ASTQueryTranslatorFactory
INFO - HHH000227: Running hbm2ddl schema export
INFO - HHH000230: Schema export complete
INFO - PersistenceUnit(name=movie-unit-TEST,
provider=org.hibernate.ejb.HibernatePersistence) - provider time 2143ms
INFO - HHH000204: Processing PersistenceUnitInfo [
name: movie-unit
...]
INFO - HHH000130: Instantiating explicit connection provider:
org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
INFO - HHH000400: Using dialect: org.hibernate.dialect.HSQLDialect
INFO - HHH000268: Transaction strategy:
org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory
INFO - HHH000397: Using ASTQueryTranslatorFactory
INFO - HHH000227: Running hbm2ddl schema export
INFO - HHH000230: Schema export complete
INFO - PersistenceUnit(name=movie-unit,
provider=org.hibernate.ejb.HibernatePersistence) - provider time 673ms
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
Re: HA-JDBC via tomee.xml Resource factory/cluster properties ignored
I believe that is exactly what I want. I wish I knew about that earlier, so I could have tried that earlier, and my preference is to do /use the tomee easy way, always, and as much as possible. Thanks Romain. I like the dynamic datasources too. Is there a test case (on trunk) available for both the fail over and dynamic datasources, separately, so I can evaluate both? Please reply with URL of those test cases, if available. Thanks. If I may ask, was this added to tomee after seeing tomee users mentioning or interested in something like this. Definitely a great idea and feature to add to the great tomee. :-) On Nov 3, 2013 3:15 AM, Romain Manni-Bucau rmannibu...@gmail.com wrote: No idea why you have a NPE but do you know http://rmannibucau.wordpress.com/2013/04/26/tomeeopenejb-and-failover-of-datasources/ ? Isnt it what you desire more or less? Le 3 nov. 2013 05:11, Howard W. Smith, Jr. smithh032...@gmail.com a écrit : trying to get it done via tomee.xml, ha-jdbc-cluster.xml, and java option -Dha-jdbc... seems to help, but i definitely need help...i been reporting my progress with this on ha-jdbc forum[1]... i hope to get some help with this, soon. [1] https://sourceforge.net/p/ha-jdbc/discussion/383396/thread/5f4dc302/ On Sat, Nov 2, 2013 at 3:44 PM, Howard W. Smith, Jr. smithh032...@gmail.com wrote: okay, I'm seeing what you said (not get jta as easily, when using context.xml). thanks. On Sat, Nov 2, 2013 at 3:39 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: If you use context.xml youll not get as easily jta. You can set Resource attribute class-name to the impl class and setXxx using xxx as property attribute (factory for instance) Le 2 nov. 2013 18:10, Howard W. Smith, Jr. smithh032...@gmail.com a écrit : Per [Avoid properties conflict when configuring TomEE DataSource][1], I added ignoreDefaultValues=true to Resource in tomee.xml, Resource id=jdbc/mcmsJta type=javax.sql.DataSource JdbcDriver net.sf.hajdbc.sql.DataSource IgnoreDefaultValues true JtaManaged true jmxEnabled true LogSql false /Resource and the result are the [exceptions in the log file][2]. the exceptions seem to prove that I need to add the following to Resource .../ cluster=... factory=... can you please advise how I can add these two parameters to Resource .../ in tomee.xml, or should I revert to META-INF/context.xml? [1]: http://rmannibucau.wordpress.com/2012/11/08/avoid-properties-conflict-when-configuring-tomee-datasource/ [2]: https://gist.github.com/smithh032772/7279765#file-log3-txt On Sat, Nov 2, 2013 at 11:09 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Why workaround? That how it works
Re: HA-JDBC via tomee.xml Resource factory/cluster properties ignored
okay, i just found this on tomee examples page, http://tomee.apache.org/examples-trunk/dynamic-datasource-routing/README.html On Sun, Nov 3, 2013 at 5:46 AM, Howard W. Smith, Jr. smithh032...@gmail.com wrote: I believe that is exactly what I want. I wish I knew about that earlier, so I could have tried that earlier, and my preference is to do /use the tomee easy way, always, and as much as possible. Thanks Romain. I like the dynamic datasources too. Is there a test case (on trunk) available for both the fail over and dynamic datasources, separately, so I can evaluate both? Please reply with URL of those test cases, if available. Thanks. If I may ask, was this added to tomee after seeing tomee users mentioning or interested in something like this. Definitely a great idea and feature to add to the great tomee. :-) On Nov 3, 2013 3:15 AM, Romain Manni-Bucau rmannibu...@gmail.com wrote: No idea why you have a NPE but do you know http://rmannibucau.wordpress.com/2013/04/26/tomeeopenejb-and-failover-of-datasources/ ? Isnt it what you desire more or less? Le 3 nov. 2013 05:11, Howard W. Smith, Jr. smithh032...@gmail.com a écrit : trying to get it done via tomee.xml, ha-jdbc-cluster.xml, and java option -Dha-jdbc... seems to help, but i definitely need help...i been reporting my progress with this on ha-jdbc forum[1]... i hope to get some help with this, soon. [1] https://sourceforge.net/p/ha-jdbc/discussion/383396/thread/5f4dc302/ On Sat, Nov 2, 2013 at 3:44 PM, Howard W. Smith, Jr. smithh032...@gmail.com wrote: okay, I'm seeing what you said (not get jta as easily, when using context.xml). thanks. On Sat, Nov 2, 2013 at 3:39 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: If you use context.xml youll not get as easily jta. You can set Resource attribute class-name to the impl class and setXxx using xxx as property attribute (factory for instance) Le 2 nov. 2013 18:10, Howard W. Smith, Jr. smithh032...@gmail.com a écrit : Per [Avoid properties conflict when configuring TomEE DataSource][1], I added ignoreDefaultValues=true to Resource in tomee.xml, Resource id=jdbc/mcmsJta type=javax.sql.DataSource JdbcDriver net.sf.hajdbc.sql.DataSource IgnoreDefaultValues true JtaManaged true jmxEnabled true LogSql false /Resource and the result are the [exceptions in the log file][2]. the exceptions seem to prove that I need to add the following to Resource .../ cluster=... factory=... can you please advise how I can add these two parameters to Resource .../ in tomee.xml, or should I revert to META-INF/context.xml? [1]: http://rmannibucau.wordpress.com/2012/11/08/avoid-properties-conflict-when-configuring-tomee-datasource/ [2]: https://gist.github.com/smithh032772/7279765#file-log3-txt On Sat, Nov 2, 2013 at 11:09 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Why workaround? That how it works
Re: MySQL resource in Tomee 1.5.2
Just so that I am understanding this correctly, would it be possible for you to provide a resources.xml sample, the web.xml snippet and a small code for datasource from initialcontext lookup - ?? Mine are here :- Resources.xml ( in WEB-INF folder of deployed war) Resource id=jdbc/localDB type=javax.sql.DataSource JdbcDriver com.mysql.jdbc.Driver JdbcUrl jdbc:mysql://localhost:3306/localdatabase MaxActive 100 MaxIdle 30 MaxWait 1 UserName username Password password /Resource web.xml ( in WEB-INF folder of deployed war) resource-ref descriptionMySQL Connection/description res-ref-namejdbc/locallDB/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth /resource-ref Code to lookup and use datasource InitialContext ic = new InitialContext(); Context envCtx = (Context) ic.lookup(java:comp/env); DataSource ds = (DataSource)envCtx.lookup(jdbc/localDB); -- View this message in context: http://openejb.979440.n4.nabble.com/MySQL-resource-in-Tomee-1-5-2-tp4665872p4665892.html Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: MySQL resource in Tomee 1.5.2
Hi Romain, If I understand you correctly, you are saying that id and resource name do not match Here :- Resource id=quot;lt;bjdbc/localDB* type=javax.sql.DataSource JdbcDriver com.mysql.jdbc.Driver JdbcUrl jdbc:mysql://localhost:3306/localdb MaxActive 100 MaxIdle 30 MaxWait 1 and resource-ref descriptionMySQL Connection/description res-ref-name*jdbc/localDB*/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth /resource-ref isn't resourcename = jdbc/localDB same as id=jdbc/localDB What exactly is the prefix that you are mentioning to be added in resources.xml? -- View this message in context: http://openejb.979440.n4.nabble.com/MySQL-resource-in-Tomee-1-5-2-tp4665872p4665891.html Sent from the OpenEJB User mailing list archive at Nabble.com.
How to serve static page with restful services in TomEE plus 1.6?
Hello everyone,
I’m developing a html5 application with a restful service generated using
Netbeans.
After modifying some configuration xml files like removing jersey
serverlethttp://stackoverflow.com/questions/10583563/how-can-i-integrate-jersey-with-tomee-openejb,
changing xmlns to “
http://java.sun.com/xml/ns/persistence“ and configuring jta-data-source in
persistence.xml. The service finally worked. But I cannot access my web
files in the web root directory. Anyone knows why?
Here is my source files:
web.xml
?xml version=1.0 encoding=UTF-8?web-app version=3.0
xmlns=http://java.sun.com/xml/ns/javaee;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd;
session-config
session-timeout
30
/session-timeout
/session-config
filter
filter-namecross-origin/filter-name
filter-classorg.apache.catalina.filters.CorsFilter/filter-class
/filter
filter-mapping
filter-namecross-origin/filter-name
url-pattern/api/*/url-pattern
/filter-mapping
/web-app
persistence.xml
?xml version=1.0 encoding=UTF-8?persistence version=2.1
xmlns=http://java.sun.com/xml/ns/persistence;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/persistence
http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/persistence/persistence_2_1.xsd;
persistence-unit name=TongYiMenHuRestServicePU transaction-type=JTA
providerorg.apache.openjpa.persistence.PersistenceProviderImpl/provider
jta-data-sourcetongyimenhu/jta-data-source!--
non-jta-data-sourcetongyimenhu-nonjta/non-jta-data-source--
classcom.tongyimenhu.entities.Type/class
exclude-unlisted-classesfalse/exclude-unlisted-classes
/persistence-unit
/persistence
context.xml
?xml version=1.0 encoding=UTF-8?
Context antiJARLocking=true path=/tymh/
Type.java
/*
* To change this template, choose Tools | Templates
* and open the template in the editor.
*/package com.tongyimenhu.entities;
import java.io.Serializable;import javax.persistence.Basic;import
javax.persistence.Column;import javax.persistence.Entity;import
javax.persistence.GeneratedValue;import
javax.persistence.GenerationType;import javax.persistence.Id;import
javax.persistence.NamedQueries;import
javax.persistence.NamedQuery;import javax.persistence.Table;import
javax.validation.constraints.NotNull;import
javax.validation.constraints.Size;import
javax.xml.bind.annotation.XmlRootElement;
/**
*
* @author yeyanbo
*/@Entity@Table(name = type)@XmlRootElement@NamedQueries({
@NamedQuery(name = Type.findAll, query = SELECT t FROM Type t),
@NamedQuery(name = Type.findByTypeId, query = SELECT t FROM
Type t WHERE t.typeId = :typeId),
@NamedQuery(name = Type.findByTypeName, query = SELECT t FROM
Type t WHERE t.typeName = :typeName),
@NamedQuery(name = Type.findByTypeAudit, query = SELECT t FROM
Type t WHERE t.typeAudit = :typeAudit),
@NamedQuery(name = Type.findByTypeDescrib, query = SELECT t
FROM Type t WHERE t.typeDescrib = :typeDescrib)})public class Type
implements Serializable {
private static final long serialVersionUID = 1L;
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
@Basic(optional = false)
@Column(name = type_id)
private Integer typeId;
@Basic(optional = false)
@NotNull
@Size(min = 1, max = 35)
@Column(name = type_name)
private String typeName;
@Column(name = type_audit)
private Integer typeAudit;
@Size(max = 50)
@Column(name = type_describ)
private String typeDescrib;
public Type() {
}
public Type(Integer typeId) {
this.typeId = typeId;
}
public Type(Integer typeId, String typeName) {
this.typeId = typeId;
this.typeName = typeName;
}
public Integer getTypeId() {
return typeId;
}
public void setTypeId(Integer typeId) {
this.typeId = typeId;
}
public String getTypeName() {
return typeName;
}
public void setTypeName(String typeName) {
this.typeName = typeName;
}
public Integer getTypeAudit() {
return typeAudit;
}
public void setTypeAudit(Integer typeAudit) {
this.typeAudit = typeAudit;
}
public String getTypeDescrib() {
return typeDescrib;
}
public void setTypeDescrib(String typeDescrib) {
this.typeDescrib = typeDescrib;
}
@Override
public int hashCode() {
int hash = 0;
hash += (typeId != null ? typeId.hashCode() : 0);
return hash;
}
@Override
public boolean equals(Object object) {
// TODO: Warning - this method won't work in the case the id
fields are not set
if (!(object instanceof Type)) {
return false;
}
Type other = (Type) object;
if ((this.typeId == null other.typeId != null) ||
(this.typeId != null
Re: How to serve static page with restful services in TomEE plus 1.6?
Hi Does https://issues.apache.org/jira/i#browse/TOMEE-728?issueKey=TOMEE-728amp;serverRenderedViewIssue=truehelp? Le 3 nov. 2013 13:17, Yanbo Ye yeyanbo...@gmail.com a écrit :
Re: MySQL resource in Tomee 1.5.2
Hi It was the app id (war name by default). In all cases it is written in the logs when the resource is created Le 3 nov. 2013 13:04, asif.tmcp asif.t...@gmail.com a écrit : Hi Romain, If I understand you correctly, you are saying that id and resource name do not match Here :- Resource id=quot;lt;bjdbc/localDB* type=javax.sql.DataSource JdbcDriver com.mysql.jdbc.Driver JdbcUrl jdbc:mysql://localhost:3306/localdb MaxActive 100 MaxIdle 30 MaxWait 1 and resource-ref descriptionMySQL Connection/description res-ref-name*jdbc/localDB*/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth /resource-ref isn't resourcename = jdbc/localDB same as id=jdbc/localDB What exactly is the prefix that you are mentioning to be added in resources.xml? -- View this message in context: http://openejb.979440.n4.nabble.com/MySQL-resource-in-Tomee-1-5-2-tp4665872p4665891.html Sent from the OpenEJB User mailing list archive at Nabble.com.
Using TomEE/OpenEJB and failover of datasources
First of all, thanks Romain for recommending the following, and for that I will gladly start a new thread. :) TomEE/OpenEJB and failover of datasources[1] which references [OpenEJB] Dynamic Datasource[2] but I found the following TomEE example: [TomEE] Dynamic Datasource Routing[3] So, before I begin, my questions are as follows: 1. I recognized that failover[1] says that the idea is to 'reuse' dynamic datasource. Does this mean that we should code openejb[2] or tomee[3] dynamic datasource, first, and then reference accordingly via failover[1]? 2. or failover[1] requires no coding on our part? only developer needs to setup the failover 'config'? 3. also, tomee[3] dynamic datasource routing recommends openejb.xml (instead of tomee.xml). can openejb.xml cofiguration be placed in tomee.xml, too, or not? 4. okay, never mind, I was abouto ask for some clarification about META-INF/org.router/service-jar.xml, but I 'found' service-jar.xml on trunk[4]. :) [1] http://rmannibucau.wordpress.com/2013/04/26/tomeeopenejb-and-failover-of-datasources/ [2] http://tomee.apache.org/dynamic-datasource.html [3] http://tomee.apache.org/examples-trunk/dynamic-datasource-routing/README.html [4] http://svn.apache.org/repos/asf/tomee/tomee/trunk/examples/dynamic-datasource-routing/src/main/resources/META-INF/org.router/service-jar.xml
Re: Using TomEE/OpenEJB and failover of datasources
Hi Failover is native but to customiee the algo you can code anything you want Tomee.xml is openejb.xml Service-jar.xml is today useless (see my post) Le 3 nov. 2013 14:55, Howard W. Smith, Jr. smithh032...@gmail.com a écrit : First of all, thanks Romain for recommending the following, and for that I will gladly start a new thread. :) TomEE/OpenEJB and failover of datasources[1] which references [OpenEJB] Dynamic Datasource[2] but I found the following TomEE example: [TomEE] Dynamic Datasource Routing[3] So, before I begin, my questions are as follows: 1. I recognized that failover[1] says that the idea is to 'reuse' dynamic datasource. Does this mean that we should code openejb[2] or tomee[3] dynamic datasource, first, and then reference accordingly via failover[1]? 2. or failover[1] requires no coding on our part? only developer needs to setup the failover 'config'? 3. also, tomee[3] dynamic datasource routing recommends openejb.xml (instead of tomee.xml). can openejb.xml cofiguration be placed in tomee.xml, too, or not? 4. okay, never mind, I was abouto ask for some clarification about META-INF/org.router/service-jar.xml, but I 'found' service-jar.xml on trunk[4]. :) [1] http://rmannibucau.wordpress.com/2013/04/26/tomeeopenejb-and-failover-of-datasources/ [2] http://tomee.apache.org/dynamic-datasource.html [3] http://tomee.apache.org/examples-trunk/dynamic-datasource-routing/README.html [4] http://svn.apache.org/repos/asf/tomee/tomee/trunk/examples/dynamic-datasource-routing/src/main/resources/META-INF/org.router/service-jar.xml
Re: Using TomEE/OpenEJB and failover of datasources
So, the following replaces service-jar.xml (as per your post)? Resource id=jdbc/ds type=DataSource provider=RoutedDataSource router = failover-router /Resource and if I wanted to use the 'strategy' parameter, I would add to Resource as demonstrated below? Resource id=jdbc/ds type=DataSource provider=RoutedDataSource router = failover-router strategy = random /Resource On Sun, Nov 3, 2013 at 8:58 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hi Failover is native but to customiee the algo you can code anything you want Tomee.xml is openejb.xml Service-jar.xml is today useless (see my post) Le 3 nov. 2013 14:55, Howard W. Smith, Jr. smithh032...@gmail.com a écrit : First of all, thanks Romain for recommending the following, and for that I will gladly start a new thread. :) TomEE/OpenEJB and failover of datasources[1] which references [OpenEJB] Dynamic Datasource[2] but I found the following TomEE example: [TomEE] Dynamic Datasource Routing[3] So, before I begin, my questions are as follows: 1. I recognized that failover[1] says that the idea is to 'reuse' dynamic datasource. Does this mean that we should code openejb[2] or tomee[3] dynamic datasource, first, and then reference accordingly via failover[1]? 2. or failover[1] requires no coding on our part? only developer needs to setup the failover 'config'? 3. also, tomee[3] dynamic datasource routing recommends openejb.xml (instead of tomee.xml). can openejb.xml cofiguration be placed in tomee.xml, too, or not? 4. okay, never mind, I was abouto ask for some clarification about META-INF/org.router/service-jar.xml, but I 'found' service-jar.xml on trunk[4]. :) [1] http://rmannibucau.wordpress.com/2013/04/26/tomeeopenejb-and-failover-of-datasources/ [2] http://tomee.apache.org/dynamic-datasource.html [3] http://tomee.apache.org/examples-trunk/dynamic-datasource-routing/README.html [4] http://svn.apache.org/repos/asf/tomee/tomee/trunk/examples/dynamic-datasource-routing/src/main/resources/META-INF/org.router/service-jar.xml
Re: Using TomEE/OpenEJB and failover of datasources
okay, i set it up as your post demonstrated, I tested already, and I see no issues. it's time to test this in production. :) thanks romain! like i said in the other thread, I wish I knew about this earlier. On Sun, Nov 3, 2013 at 9:16 AM, Howard W. Smith, Jr. smithh032...@gmail.com wrote: So, the following replaces service-jar.xml (as per your post)? Resource id=jdbc/ds type=DataSource provider=RoutedDataSource router = failover-router /Resource and if I wanted to use the 'strategy' parameter, I would add to Resource as demonstrated below? Resource id=jdbc/ds type=DataSource provider=RoutedDataSource router = failover-router strategy = random /Resource On Sun, Nov 3, 2013 at 8:58 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hi Failover is native but to customiee the algo you can code anything you want Tomee.xml is openejb.xml Service-jar.xml is today useless (see my post) Le 3 nov. 2013 14:55, Howard W. Smith, Jr. smithh032...@gmail.com a écrit : First of all, thanks Romain for recommending the following, and for that I will gladly start a new thread. :) TomEE/OpenEJB and failover of datasources[1] which references [OpenEJB] Dynamic Datasource[2] but I found the following TomEE example: [TomEE] Dynamic Datasource Routing[3] So, before I begin, my questions are as follows: 1. I recognized that failover[1] says that the idea is to 'reuse' dynamic datasource. Does this mean that we should code openejb[2] or tomee[3] dynamic datasource, first, and then reference accordingly via failover[1]? 2. or failover[1] requires no coding on our part? only developer needs to setup the failover 'config'? 3. also, tomee[3] dynamic datasource routing recommends openejb.xml (instead of tomee.xml). can openejb.xml cofiguration be placed in tomee.xml, too, or not? 4. okay, never mind, I was abouto ask for some clarification about META-INF/org.router/service-jar.xml, but I 'found' service-jar.xml on trunk[4]. :) [1] http://rmannibucau.wordpress.com/2013/04/26/tomeeopenejb-and-failover-of-datasources/ [2] http://tomee.apache.org/dynamic-datasource.html [3] http://tomee.apache.org/examples-trunk/dynamic-datasource-routing/README.html [4] http://svn.apache.org/repos/asf/tomee/tomee/trunk/examples/dynamic-datasource-routing/src/main/resources/META-INF/org.router/service-jar.xml
Re: Using TomEE/OpenEJB and failover of datasources
just as next time. If not already there, no issue to add a feature or to propose it by yourself ;-) New committers always welcome. 2013/11/3 Howard W. Smith, Jr. smithh032...@gmail.com okay, i set it up as your post demonstrated, I tested already, and I see no issues. it's time to test this in production. :) thanks romain! like i said in the other thread, I wish I knew about this earlier. On Sun, Nov 3, 2013 at 9:16 AM, Howard W. Smith, Jr. smithh032...@gmail.com wrote: So, the following replaces service-jar.xml (as per your post)? Resource id=jdbc/ds type=DataSource provider=RoutedDataSource router = failover-router /Resource and if I wanted to use the 'strategy' parameter, I would add to Resource as demonstrated below? Resource id=jdbc/ds type=DataSource provider=RoutedDataSource router = failover-router strategy = random /Resource On Sun, Nov 3, 2013 at 8:58 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hi Failover is native but to customiee the algo you can code anything you want Tomee.xml is openejb.xml Service-jar.xml is today useless (see my post) Le 3 nov. 2013 14:55, Howard W. Smith, Jr. smithh032...@gmail.com a écrit : First of all, thanks Romain for recommending the following, and for that I will gladly start a new thread. :) TomEE/OpenEJB and failover of datasources[1] which references [OpenEJB] Dynamic Datasource[2] but I found the following TomEE example: [TomEE] Dynamic Datasource Routing[3] So, before I begin, my questions are as follows: 1. I recognized that failover[1] says that the idea is to 'reuse' dynamic datasource. Does this mean that we should code openejb[2] or tomee[3] dynamic datasource, first, and then reference accordingly via failover[1]? 2. or failover[1] requires no coding on our part? only developer needs to setup the failover 'config'? 3. also, tomee[3] dynamic datasource routing recommends openejb.xml (instead of tomee.xml). can openejb.xml cofiguration be placed in tomee.xml, too, or not? 4. okay, never mind, I was abouto ask for some clarification about META-INF/org.router/service-jar.xml, but I 'found' service-jar.xml on trunk[4]. :) [1] http://rmannibucau.wordpress.com/2013/04/26/tomeeopenejb-and-failover-of-datasources/ [2] http://tomee.apache.org/dynamic-datasource.html [3] http://tomee.apache.org/examples-trunk/dynamic-datasource-routing/README.html [4] http://svn.apache.org/repos/asf/tomee/tomee/trunk/examples/dynamic-datasource-routing/src/main/resources/META-INF/org.router/service-jar.xml -- Jean-Louis
Re: Using TomEE/OpenEJB and failover of datasources
thanks Jean-Louis... i'm still learning via tomee (committers). :) On Sun, Nov 3, 2013 at 10:00 AM, Jean-Louis MONTEIRO jeano...@gmail.comwrote: just as next time. If not already there, no issue to add a feature or to propose it by yourself ;-) New committers always welcome. 2013/11/3 Howard W. Smith, Jr. smithh032...@gmail.com okay, i set it up as your post demonstrated, I tested already, and I see no issues. it's time to test this in production. :) thanks romain! like i said in the other thread, I wish I knew about this earlier. On Sun, Nov 3, 2013 at 9:16 AM, Howard W. Smith, Jr. smithh032...@gmail.com wrote: So, the following replaces service-jar.xml (as per your post)? Resource id=jdbc/ds type=DataSource provider=RoutedDataSource router = failover-router /Resource and if I wanted to use the 'strategy' parameter, I would add to Resource as demonstrated below? Resource id=jdbc/ds type=DataSource provider=RoutedDataSource router = failover-router strategy = random /Resource On Sun, Nov 3, 2013 at 8:58 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hi Failover is native but to customiee the algo you can code anything you want Tomee.xml is openejb.xml Service-jar.xml is today useless (see my post) Le 3 nov. 2013 14:55, Howard W. Smith, Jr. smithh032...@gmail.com a écrit : First of all, thanks Romain for recommending the following, and for that I will gladly start a new thread. :) TomEE/OpenEJB and failover of datasources[1] which references [OpenEJB] Dynamic Datasource[2] but I found the following TomEE example: [TomEE] Dynamic Datasource Routing[3] So, before I begin, my questions are as follows: 1. I recognized that failover[1] says that the idea is to 'reuse' dynamic datasource. Does this mean that we should code openejb[2] or tomee[3] dynamic datasource, first, and then reference accordingly via failover[1]? 2. or failover[1] requires no coding on our part? only developer needs to setup the failover 'config'? 3. also, tomee[3] dynamic datasource routing recommends openejb.xml (instead of tomee.xml). can openejb.xml cofiguration be placed in tomee.xml, too, or not? 4. okay, never mind, I was abouto ask for some clarification about META-INF/org.router/service-jar.xml, but I 'found' service-jar.xml on trunk[4]. :) [1] http://rmannibucau.wordpress.com/2013/04/26/tomeeopenejb-and-failover-of-datasources/ [2] http://tomee.apache.org/dynamic-datasource.html [3] http://tomee.apache.org/examples-trunk/dynamic-datasource-routing/README.html [4] http://svn.apache.org/repos/asf/tomee/tomee/trunk/examples/dynamic-datasource-routing/src/main/resources/META-INF/org.router/service-jar.xml -- Jean-Louis
Re: Using TomEE/OpenEJB and failover of datasources
That's great but I'm pretty sure, you know much more than a lot of people. 2013/11/3 Howard W. Smith, Jr. smithh032...@gmail.com thanks Jean-Louis... i'm still learning via tomee (committers). :) On Sun, Nov 3, 2013 at 10:00 AM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: just as next time. If not already there, no issue to add a feature or to propose it by yourself ;-) New committers always welcome. 2013/11/3 Howard W. Smith, Jr. smithh032...@gmail.com okay, i set it up as your post demonstrated, I tested already, and I see no issues. it's time to test this in production. :) thanks romain! like i said in the other thread, I wish I knew about this earlier. On Sun, Nov 3, 2013 at 9:16 AM, Howard W. Smith, Jr. smithh032...@gmail.com wrote: So, the following replaces service-jar.xml (as per your post)? Resource id=jdbc/ds type=DataSource provider=RoutedDataSource router = failover-router /Resource and if I wanted to use the 'strategy' parameter, I would add to Resource as demonstrated below? Resource id=jdbc/ds type=DataSource provider=RoutedDataSource router = failover-router strategy = random /Resource On Sun, Nov 3, 2013 at 8:58 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hi Failover is native but to customiee the algo you can code anything you want Tomee.xml is openejb.xml Service-jar.xml is today useless (see my post) Le 3 nov. 2013 14:55, Howard W. Smith, Jr. smithh032...@gmail.com a écrit : First of all, thanks Romain for recommending the following, and for that I will gladly start a new thread. :) TomEE/OpenEJB and failover of datasources[1] which references [OpenEJB] Dynamic Datasource[2] but I found the following TomEE example: [TomEE] Dynamic Datasource Routing[3] So, before I begin, my questions are as follows: 1. I recognized that failover[1] says that the idea is to 'reuse' dynamic datasource. Does this mean that we should code openejb[2] or tomee[3] dynamic datasource, first, and then reference accordingly via failover[1]? 2. or failover[1] requires no coding on our part? only developer needs to setup the failover 'config'? 3. also, tomee[3] dynamic datasource routing recommends openejb.xml (instead of tomee.xml). can openejb.xml cofiguration be placed in tomee.xml, too, or not? 4. okay, never mind, I was abouto ask for some clarification about META-INF/org.router/service-jar.xml, but I 'found' service-jar.xml on trunk[4]. :) [1] http://rmannibucau.wordpress.com/2013/04/26/tomeeopenejb-and-failover-of-datasources/ [2] http://tomee.apache.org/dynamic-datasource.html [3] http://tomee.apache.org/examples-trunk/dynamic-datasource-routing/README.html [4] http://svn.apache.org/repos/asf/tomee/tomee/trunk/examples/dynamic-datasource-routing/src/main/resources/META-INF/org.router/service-jar.xml -- Jean-Louis -- Jean-Louis
Re: Using TomEE/OpenEJB and failover of datasources
thanks Jean-Louis... it remains to be seen. :) On Sun, Nov 3, 2013 at 10:14 AM, Jean-Louis MONTEIRO jeano...@gmail.comwrote: That's great but I'm pretty sure, you know much more than a lot of people. 2013/11/3 Howard W. Smith, Jr. smithh032...@gmail.com thanks Jean-Louis... i'm still learning via tomee (committers). :) On Sun, Nov 3, 2013 at 10:00 AM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: just as next time. If not already there, no issue to add a feature or to propose it by yourself ;-) New committers always welcome. 2013/11/3 Howard W. Smith, Jr. smithh032...@gmail.com okay, i set it up as your post demonstrated, I tested already, and I see no issues. it's time to test this in production. :) thanks romain! like i said in the other thread, I wish I knew about this earlier. On Sun, Nov 3, 2013 at 9:16 AM, Howard W. Smith, Jr. smithh032...@gmail.com wrote: So, the following replaces service-jar.xml (as per your post)? Resource id=jdbc/ds type=DataSource provider=RoutedDataSource router = failover-router /Resource and if I wanted to use the 'strategy' parameter, I would add to Resource as demonstrated below? Resource id=jdbc/ds type=DataSource provider=RoutedDataSource router = failover-router strategy = random /Resource On Sun, Nov 3, 2013 at 8:58 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hi Failover is native but to customiee the algo you can code anything you want Tomee.xml is openejb.xml Service-jar.xml is today useless (see my post) Le 3 nov. 2013 14:55, Howard W. Smith, Jr. smithh032...@gmail.com a écrit : First of all, thanks Romain for recommending the following, and for that I will gladly start a new thread. :) TomEE/OpenEJB and failover of datasources[1] which references [OpenEJB] Dynamic Datasource[2] but I found the following TomEE example: [TomEE] Dynamic Datasource Routing[3] So, before I begin, my questions are as follows: 1. I recognized that failover[1] says that the idea is to 'reuse' dynamic datasource. Does this mean that we should code openejb[2] or tomee[3] dynamic datasource, first, and then reference accordingly via failover[1]? 2. or failover[1] requires no coding on our part? only developer needs to setup the failover 'config'? 3. also, tomee[3] dynamic datasource routing recommends openejb.xml (instead of tomee.xml). can openejb.xml cofiguration be placed in tomee.xml, too, or not? 4. okay, never mind, I was abouto ask for some clarification about META-INF/org.router/service-jar.xml, but I 'found' service-jar.xml on trunk[4]. :) [1] http://rmannibucau.wordpress.com/2013/04/26/tomeeopenejb-and-failover-of-datasources/ [2] http://tomee.apache.org/dynamic-datasource.html [3] http://tomee.apache.org/examples-trunk/dynamic-datasource-routing/README.html [4] http://svn.apache.org/repos/asf/tomee/tomee/trunk/examples/dynamic-datasource-routing/src/main/resources/META-INF/org.router/service-jar.xml -- Jean-Louis -- Jean-Louis
Re: Using TomEE/OpenEJB and failover of datasources
FYI, I just stopped my local tomee, and recognized that my @Application @PreDestroy has my code that stops Apache Derby prior to main and fallback datasources are closed. is this okay? Nov 03, 2013 10:12:48 AM org.apache.catalina.core.StandardServer await INFO: A valid shutdown command was received via the shutdown port. Stopping the Server instance. Nov 03, 2013 10:12:48 AM org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler [http-nio-8080] Nov 03, 2013 10:12:48 AM org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler [ajp-bio-8009] Nov 03, 2013 10:12:48 AM org.apache.catalina.core.StandardService stopInternal INFO: Stopping service Catalina Nov 03, 2013 10:12:48 AM pf.LoginFilter destroy INFO: ... Nov 03, 2013 10:12:48 AM org.apache.openejb.assembler.classic.Assembler destroyApplication INFO: Undeploying app: C:\apache-tomee-plus-1.6.0-SNAPSHOT\webapps\mcmsweb Nov 03, 2013 10:12:48 AM pf.ApplicationScopeBean destroy INFO: BEGIN Nov 03, 2013 10:12:48 AM utils.database.DerbyUtil shutdown INFO: DerbyUtil.java: shutdown() invoked Nov 03, 2013 10:12:48 AM utils.database.DerbyUtil loadDriver INFO: DerbyUtil.java: loadDriver(): Loaded driver (org.apache.derby.jdbc.EmbeddedDriver) successfully Nov 03, 2013 10:12:48 AM utils.database.DerbyUtil shutdown INFO: DerbyUtil.java: shutdown(): Derby shut down normally Nov 03, 2013 10:12:48 AM pf.ApplicationScopeBean destroy INFO: gCalUtil.shutdown() completed Nov 03, 2013 10:12:48 AM pf.ApplicationScopeBean destroy INFO: jodConverter.shutdown() completed Nov 03, 2013 10:12:48 AM mdb.ApplicationMessageBean shutdown INFO: ApplicationMessageBean.shutdown() BEGIN Nov 03, 2013 10:12:48 AM mdb.ApplicationMessageBean shutdown INFO: ApplicationMessageBean.shutdown() END Nov 03, 2013 10:12:48 AM pf.ApplicationScopeBean destroy INFO: applicationMessageBean.shutdown() completed Nov 03, 2013 10:12:48 AM pf.ThreadLocalImmolater immolate INFO: immolated 305 values in ThreadLocals Nov 03, 2013 10:12:48 AM pf.ApplicationScopeBean destroy INFO: END Nov 03, 2013 10:12:48 AM org.apache.activemq.ra.ActiveMQEndpointWorker stop INFO: Stopping Nov 03, 2013 10:12:48 AM org.apache.activemq.ra.ActiveMQEndpointWorker stop INFO: Stopping [EL Info]: 2013-11-03 10:12:48.682--ServerSession(1206174612)--file:/C:/apache-tomee-plus-1.6.0-SNAPSHOT/webapps/mcmsweb/WEB-INF/classes/_mcmsPU logout successful Nov 03, 2013 10:12:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/mcmsweb] appears to have started a thread named [PoolIdleReleaseTimer] but has failed to stop it. This is very likely to create a memory leak. Nov 03, 2013 10:12:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/mcmsweb] appears to have started a thread named [ActiveMQ VMTransport: vm://localhost#5-5] but has failed to stop it. This is very likely to create a memory leak. Nov 03, 2013 10:12:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/mcmsweb] appears to have started a thread named [ActiveMQ VMTransport: vm://localhost#5-6] but has failed to stop it. This is very likely to create a memory leak. Nov 03, 2013 10:12:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/mcmsweb] appears to have started a thread named [ActiveMQ VMTransport: vm://localhost#4-4] but has failed to stop it. This is very likely to create a memory leak. Nov 03, 2013 10:12:57 AM org.apache.coyote.AbstractProtocol stop INFO: Stopping ProtocolHandler [http-nio-8080] Nov 03, 2013 10:12:57 AM org.apache.coyote.AbstractProtocol stop INFO: Stopping ProtocolHandler [ajp-bio-8009] Nov 03, 2013 10:12:57 AM org.apache.openejb.server.SimpleServiceManager stop INFO: Stopping server services Nov 03, 2013 10:12:57 AM org.quartz.core.QuartzScheduler shutdown INFO: Scheduler OpenEJB-TimerService-Scheduler_$_OpenEJB shutting down. Nov 03, 2013 10:12:57 AM org.quartz.core.QuartzScheduler standby INFO: Scheduler OpenEJB-TimerService-Scheduler_$_OpenEJB paused. Nov 03, 2013 10:12:57 AM org.quartz.core.QuartzScheduler unregisterJMX INFO: Scheduler unregistered from name 'quartz:type=QuartzScheduler,name=OpenEJB-TimerService-Scheduler,instance=OpenEJB' in the local MBeanServer. Nov 03, 2013 10:12:57 AM org.quartz.core.QuartzScheduler shutdown INFO: Scheduler OpenEJB-TimerService-Scheduler_$_OpenEJB shutdown complete. Nov 03, 2013 10:12:57 AM org.apache.openejb.assembler.classic.Assembler destroyApplication INFO: Undeploying app: openejb Nov 03, 2013 10:12:57 AM org.apache.openejb.assembler.classic.Assembler destroyResource INFO: Closing DataSource: main Nov 03, 2013 10:12:57 AM org.apache.openejb.assembler.classic.Assembler destroyResource INFO: Closing DataSource: fallback Nov 03, 2013 10:12:57 AM org.apache.openejb.assembler.classic.Assembler destroyResource INFO: Stopping ResourceAdapter: Default JMS Resource Adapter Nov 03, 2013
Re: Using TomEE/OpenEJB and failover of datasources
i guess my question really is... since I stop derby before main fallback datasources are closed, is it likely that this might interrupt data integrity? is it possible that I will lose data since my app stops derby prior to tomee/openejb failover stops datasources...at tomee shutdown/stop? On Sun, Nov 3, 2013 at 10:18 AM, Howard W. Smith, Jr. smithh032...@gmail.com wrote: FYI, I just stopped my local tomee, and recognized that my @Application @PreDestroy has my code that stops Apache Derby prior to main and fallback datasources are closed. is this okay? Nov 03, 2013 10:12:48 AM org.apache.catalina.core.StandardServer await INFO: A valid shutdown command was received via the shutdown port. Stopping the Server instance. Nov 03, 2013 10:12:48 AM org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler [http-nio-8080] Nov 03, 2013 10:12:48 AM org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler [ajp-bio-8009] Nov 03, 2013 10:12:48 AM org.apache.catalina.core.StandardService stopInternal INFO: Stopping service Catalina Nov 03, 2013 10:12:48 AM pf.LoginFilter destroy INFO: ... Nov 03, 2013 10:12:48 AM org.apache.openejb.assembler.classic.Assembler destroyApplication INFO: Undeploying app: C:\apache-tomee-plus-1.6.0-SNAPSHOT\webapps\mcmsweb Nov 03, 2013 10:12:48 AM pf.ApplicationScopeBean destroy INFO: BEGIN Nov 03, 2013 10:12:48 AM utils.database.DerbyUtil shutdown INFO: DerbyUtil.java: shutdown() invoked Nov 03, 2013 10:12:48 AM utils.database.DerbyUtil loadDriver INFO: DerbyUtil.java: loadDriver(): Loaded driver (org.apache.derby.jdbc.EmbeddedDriver) successfully Nov 03, 2013 10:12:48 AM utils.database.DerbyUtil shutdown INFO: DerbyUtil.java: shutdown(): Derby shut down normally Nov 03, 2013 10:12:48 AM pf.ApplicationScopeBean destroy INFO: gCalUtil.shutdown() completed Nov 03, 2013 10:12:48 AM pf.ApplicationScopeBean destroy INFO: jodConverter.shutdown() completed Nov 03, 2013 10:12:48 AM mdb.ApplicationMessageBean shutdown INFO: ApplicationMessageBean.shutdown() BEGIN Nov 03, 2013 10:12:48 AM mdb.ApplicationMessageBean shutdown INFO: ApplicationMessageBean.shutdown() END Nov 03, 2013 10:12:48 AM pf.ApplicationScopeBean destroy INFO: applicationMessageBean.shutdown() completed Nov 03, 2013 10:12:48 AM pf.ThreadLocalImmolater immolate INFO: immolated 305 values in ThreadLocals Nov 03, 2013 10:12:48 AM pf.ApplicationScopeBean destroy INFO: END Nov 03, 2013 10:12:48 AM org.apache.activemq.ra.ActiveMQEndpointWorker stop INFO: Stopping Nov 03, 2013 10:12:48 AM org.apache.activemq.ra.ActiveMQEndpointWorker stop INFO: Stopping [EL Info]: 2013-11-03 10:12:48.682--ServerSession(1206174612)--file:/C:/apache-tomee-plus-1.6.0-SNAPSHOT/webapps/mcmsweb/WEB-INF/classes/_mcmsPU logout successful Nov 03, 2013 10:12:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/mcmsweb] appears to have started a thread named [PoolIdleReleaseTimer] but has failed to stop it. This is very likely to create a memory leak. Nov 03, 2013 10:12:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/mcmsweb] appears to have started a thread named [ActiveMQ VMTransport: vm://localhost#5-5] but has failed to stop it. This is very likely to create a memory leak. Nov 03, 2013 10:12:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/mcmsweb] appears to have started a thread named [ActiveMQ VMTransport: vm://localhost#5-6] but has failed to stop it. This is very likely to create a memory leak. Nov 03, 2013 10:12:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/mcmsweb] appears to have started a thread named [ActiveMQ VMTransport: vm://localhost#4-4] but has failed to stop it. This is very likely to create a memory leak. Nov 03, 2013 10:12:57 AM org.apache.coyote.AbstractProtocol stop INFO: Stopping ProtocolHandler [http-nio-8080] Nov 03, 2013 10:12:57 AM org.apache.coyote.AbstractProtocol stop INFO: Stopping ProtocolHandler [ajp-bio-8009] Nov 03, 2013 10:12:57 AM org.apache.openejb.server.SimpleServiceManager stop INFO: Stopping server services Nov 03, 2013 10:12:57 AM org.quartz.core.QuartzScheduler shutdown INFO: Scheduler OpenEJB-TimerService-Scheduler_$_OpenEJB shutting down. Nov 03, 2013 10:12:57 AM org.quartz.core.QuartzScheduler standby INFO: Scheduler OpenEJB-TimerService-Scheduler_$_OpenEJB paused. Nov 03, 2013 10:12:57 AM org.quartz.core.QuartzScheduler unregisterJMX INFO: Scheduler unregistered from name 'quartz:type=QuartzScheduler,name=OpenEJB-TimerService-Scheduler,instance=OpenEJB' in the local MBeanServer. Nov 03, 2013 10:12:57 AM org.quartz.core.QuartzScheduler shutdown INFO: Scheduler OpenEJB-TimerService-Scheduler_$_OpenEJB shutdown complete. Nov 03, 2013 10:12:57 AM
Re: Using TomEE/OpenEJB and failover of datasources
lookhttp://svn.apache.org/repos/asf/tomee/tomee/trunk/container/openejb-core/src/main/java/org/apache/openejb/resource/jdbc/router/FailOverRouter.java last method it can still be enhanced a lot Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/11/3 Howard W. Smith, Jr. smithh032...@gmail.com: okay, and one last question, is there a bit more documentation on the following, so we can know what to expect, and the implementation is quite sound, working as designed and no known issues with the following? ul lidefault: the first is used while possible and others datasources are just backup, this is typically the failover case/li lirandom: any datasource of the list is used/li lireverse: between two call to a method the list is reversed/li liround-robin[%N]: round robin between datasources, you can specify how many step you browse between two calls using N (default is 1)/li /ul i saw the limitations on the referenced pages (dynamic datasources), but I didn't see any known issues in your/Romain's post/blog. please excuse my ignorance, if I have not heard or seen much chatter about this on the mail list. I usually try to pay attention to almost all tomee emails, especially those that interest me the most. :) On Sun, Nov 3, 2013 at 10:22 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: If you dont use it then thats ok. We close the pool then, not connections Le 3 nov. 2013 16:19, Howard W. Smith, Jr. smithh032...@gmail.com a écrit : FYI, I just stopped my local tomee, and recognized that my @Application @PreDestroy has my code that stops Apache Derby prior to main and fallback datasources are closed. is this okay? Nov 03, 2013 10:12:48 AM org.apache.catalina.core.StandardServer await INFO: A valid shutdown command was received via the shutdown port. Stopping the Server instance. Nov 03, 2013 10:12:48 AM org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler [http-nio-8080] Nov 03, 2013 10:12:48 AM org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler [ajp-bio-8009] Nov 03, 2013 10:12:48 AM org.apache.catalina.core.StandardService stopInternal INFO: Stopping service Catalina Nov 03, 2013 10:12:48 AM pf.LoginFilter destroy INFO: ... Nov 03, 2013 10:12:48 AM org.apache.openejb.assembler.classic.Assembler destroyApplication INFO: Undeploying app: C:\apache-tomee-plus-1.6.0-SNAPSHOT\webapps\mcmsweb Nov 03, 2013 10:12:48 AM pf.ApplicationScopeBean destroy INFO: BEGIN Nov 03, 2013 10:12:48 AM utils.database.DerbyUtil shutdown INFO: DerbyUtil.java: shutdown() invoked Nov 03, 2013 10:12:48 AM utils.database.DerbyUtil loadDriver INFO: DerbyUtil.java: loadDriver(): Loaded driver (org.apache.derby.jdbc.EmbeddedDriver) successfully Nov 03, 2013 10:12:48 AM utils.database.DerbyUtil shutdown INFO: DerbyUtil.java: shutdown(): Derby shut down normally Nov 03, 2013 10:12:48 AM pf.ApplicationScopeBean destroy INFO: gCalUtil.shutdown() completed Nov 03, 2013 10:12:48 AM pf.ApplicationScopeBean destroy INFO: jodConverter.shutdown() completed Nov 03, 2013 10:12:48 AM mdb.ApplicationMessageBean shutdown INFO: ApplicationMessageBean.shutdown() BEGIN Nov 03, 2013 10:12:48 AM mdb.ApplicationMessageBean shutdown INFO: ApplicationMessageBean.shutdown() END Nov 03, 2013 10:12:48 AM pf.ApplicationScopeBean destroy INFO: applicationMessageBean.shutdown() completed Nov 03, 2013 10:12:48 AM pf.ThreadLocalImmolater immolate INFO: immolated 305 values in ThreadLocals Nov 03, 2013 10:12:48 AM pf.ApplicationScopeBean destroy INFO: END Nov 03, 2013 10:12:48 AM org.apache.activemq.ra.ActiveMQEndpointWorker stop INFO: Stopping Nov 03, 2013 10:12:48 AM org.apache.activemq.ra.ActiveMQEndpointWorker stop INFO: Stopping [EL Info]: 2013-11-03 10:12:48.682--ServerSession(1206174612)--file:/C:/apache-tomee-plus-1.6.0-SNAPSHOT/webapps/mcmsweb/WEB-INF/classes/_mcmsPU logout successful Nov 03, 2013 10:12:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/mcmsweb] appears to have started a thread named [PoolIdleReleaseTimer] but has failed to stop it. This is very likely to create a memory leak. Nov 03, 2013 10:12:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/mcmsweb] appears to have started a thread named [ActiveMQ VMTransport: vm://localhost#5-5] but has failed to stop it. This is very likely to create a memory leak. Nov 03, 2013 10:12:49 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/mcmsweb] appears to have started a thread named [ActiveMQ VMTransport: vm://localhost#5-6] but has failed to stop it. This is very likely to create a memory leak. Nov 03, 2013 10:12:49 AM
Re: Using TomEE/OpenEJB and failover of datasources
Interesting. thanks Jean-Louis. Let me share some things. When I saw Romain's response on the other thread that informed me about tomee/openejb failover via dynamic datasource(s), I saw his post/blog mention load-balancing, and that is what attracted me the most to this feature. So, after I added it to my tomee.xml (earlier this morning, my time), I wanted to test the 'load-balancing' just a bit, I started a long-running query that searches multiple tables for a certain string (varchar type), and after starting that query, I did a multiple-table commit of at least 4 rows in an 'orders' table that is related to many other tables. the commit consists of doing non-read-only queries that read 'orders' and the multiple tables, and then copies the data (or insert the data into multiple tables). i was quite impressed that the commit took less than 2 seconds maybe (on my development server), which is not as fast as my production server, and plus, my drive is drastically fragmented, since I have been doing JSF web app development for 2 years straight, building building building and have not defragged or reformatted (or replaced) my hard drive... the commit occurred during the long-running query, and the query finished some # of seconds after I was mouth-wide-opened (shocked) at the fact that the data committed 'during' the long-running query. but you know what? what was more even a shock to me was this... all of the above was on my test/development server (locally here at my home), so before updating production server (at another location), I decided to login to production app, and run the same test. please note/remember, production app was 'not' configured to use tomee/openejb failover via dynamic datasource(s). when I ran the same test, while connected (remotely) to the production app, the test results were...exactly the same. that was very shocking. that is why my earlier response... that it works... i was not so 'excited' as I am 'usually'. lol...please continue to listen... i had wrote a very shocking email, and was very excited to report that the 1st test (on development server) was very impressive, but then after I ran the same test (remotely) against the production server (that does not have tomee failover), I backspace'd my response, and changed my response to a less-excited tone. i know that i have strived to make my app perform well, and I just want the database to not be the bottleneck in the app. after performing the remote test against production server, I went ahead and configured tomee/openejb failover via dynamic datasources on the production server (in tomee.xml), and copied the database, once, so now the app is connected to 2 databases. I want to test tomee/openejb failover via dynamic datasources by running it...in production, on production server, and see what the test results will be. can/shall i assume that this is a form of replication? Jean-Louis, you mentioned something like it targets the readonly requirement and I think you said transactions are not shared. i assume the data is replicated somehow. right? thanks for listening and responding. :) On Sun, Nov 3, 2013 at 10:51 AM, Jean-Louis MONTEIRO jeano...@gmail.comwrote: Well, we pushed that feature some years ago already. We mainly used it to implement a failover mechanism, or to implement kinda cloud features, I mean having each customer data in different databases. Also the read mostly pattern AFAIR. Restrictions are mainly transactions not shared and not wrapping connections from more than one datasource. The cache configuration must be well configured to not cache stale data. But it clearly depends on the use case. Hope that helps. JLouis 2013/11/3 Howard W. Smith, Jr. smithh032...@gmail.com okay, and one last question, is there a bit more documentation on the following, so we can know what to expect, and the implementation is quite sound, working as designed and no known issues with the following? ul lidefault: the first is used while possible and others datasources are just backup, this is typically the failover case/li lirandom: any datasource of the list is used/li lireverse: between two call to a method the list is reversed/li liround-robin[%N]: round robin between datasources, you can specify how many step you browse between two calls using N (default is 1)/li /ul i saw the limitations on the referenced pages (dynamic datasources), but I didn't see any known issues in your/Romain's post/blog. please excuse my ignorance, if I have not heard or seen much chatter about this on the mail list. I usually try to pay attention to almost all tomee emails, especially those that interest me the most. :) On Sun, Nov 3, 2013 at 10:22 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: If you dont use it then thats ok. We close the pool then, not connections Le 3 nov. 2013 16:19, Howard W. Smith, Jr. smithh032...@gmail.com a écrit : FYI,
Re: Using TomEE/OpenEJB and failover of datasources
interesting. I can definitely use this as a reference if (ever) necessary, thanks. which brings me to my next question, // // take care next strategies can break multiple calls on the facade // it is only intended to be used for connection selection // I recognized that in the code. I know I make many calls to @Stateless @EJB facade objects to read/write data from/to database, and I also configured tomcat jdbc pool to allow for many connections...in/via tomee.xml Resource .../. so, my question... what is the rule of thumb when configuring jdbc pool and tomee/openejb failover via dynamic datasources? on my development/test server, I have the following: Resource id=jdbc/main type=javax.sql.DataSource JdbcDriver org.apache.derby.jdbc.EmbeddedDriver JdbcUrl jdbc:derby:C:/javadb/databases/mcmsdev;create=true UserName Password JtaManaged true jmxEnabled true LogSql false InitialSize 10 MaxActive 100 MaxIdle 30 MaxWait 1 minIdle 10 suspectTimeout 60 removeAbandoned true removeAbandonedTimeout 180 timeBetweenEvictionRunsMillis 3 jdbcInterceptors=StatementCache(max=128) /Resource Resource id=jdbc/fallback type=javax.sql.DataSource JdbcDriver org.apache.derby.jdbc.EmbeddedDriver JdbcUrl jdbc:derby:C:/javadb/databases/mcms;create=true UserName Password JtaManaged true jmxEnabled true LogSql false InitialSize 10 MaxActive 100 MaxIdle 30 MaxWait 1 minIdle 10 suspectTimeout 60 removeAbandoned true removeAbandonedTimeout 180 timeBetweenEvictionRunsMillis 3 jdbcInterceptors=StatementCache(max=128) /Resource Resource id=failover-router class-name=org.apache.openejb.resource.jdbc.router.FailOverRouter datasourceNames = jdbc/main,jdbc/fallback /Resource Resource id=jdbc/mcmsJta type=DataSource provider=RoutedDataSource router = failover-router /Resource should I be configuring tomcat jdbc pooling on the dynamic datasources, or on the routed datasource? also, I recognized something in the log file, since RoutedDataSource has no URL, the following shows up in the log when starting TomEE: INFO: Creating Resource(id=jdbc/mcmsJta) Nov 03, 2013 9:19:04 AM org.apache.openejb.assembler.classic.Assembler createResource INFO: can't find url for jdbc/mcmsJta will not monitor it On Sun, Nov 3, 2013 at 10:52 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: lookhttp:// svn.apache.org/repos/asf/tomee/tomee/trunk/container/openejb-core/src/main/java/org/apache/openejb/resource/jdbc/router/FailOverRouter.java last method it can still be enhanced a lot Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/11/3 Howard W. Smith, Jr. smithh032...@gmail.com: okay, and one last question, is there a bit more documentation on the following, so we can know what to expect, and the implementation is quite sound, working as designed and no known issues with the following? ul lidefault: the first is used while possible and others datasources are just backup, this is typically the failover case/li lirandom: any datasource of the list is used/li lireverse: between two call to a method the list is reversed/li liround-robin[%N]: round robin between datasources, you can specify how many step you browse between two calls using N (default is 1)/li /ul i saw the limitations on the referenced pages (dynamic datasources), but I didn't see any known issues in your/Romain's post/blog. please excuse my ignorance, if I have not heard or seen much chatter about this on the mail list. I usually try to pay attention to almost all tomee emails, especially those that interest me the most. :) On Sun, Nov 3, 2013 at 10:22 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: If you dont use it then thats ok. We close the pool then, not connections Le 3 nov. 2013 16:19, Howard W. Smith, Jr. smithh032...@gmail.com a écrit : FYI, I just stopped my local tomee, and recognized that my @Application @PreDestroy has my code that stops Apache Derby prior to main and fallback datasources are closed. is this okay? Nov 03, 2013 10:12:48 AM org.apache.catalina.core.StandardServer await INFO: A valid shutdown command was received via the shutdown port. Stopping the Server instance. Nov 03, 2013 10:12:48 AM org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler [http-nio-8080] Nov 03, 2013 10:12:48 AM org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler [ajp-bio-8009] Nov 03, 2013 10:12:48 AM org.apache.catalina.core.StandardService stopInternal INFO: Stopping service Catalina Nov 03, 2013 10:12:48 AM pf.LoginFilter destroy INFO: ... Nov 03, 2013 10:12:48 AM org.apache.openejb.assembler.classic.Assembler destroyApplication INFO: Undeploying
Re: Using TomEE/OpenEJB and failover of datasources
Failover is a facase over normal resources. Only these resource can/should be pooled Le 3 nov. 2013 21:51, Howard W. Smith, Jr. smithh032...@gmail.com a écrit : interesting. I can definitely use this as a reference if (ever) necessary, thanks. which brings me to my next question, // // take care next strategies can break multiple calls on the facade // it is only intended to be used for connection selection // I recognized that in the code. I know I make many calls to @Stateless @EJB facade objects to read/write data from/to database, and I also configured tomcat jdbc pool to allow for many connections...in/via tomee.xml Resource .../. so, my question... what is the rule of thumb when configuring jdbc pool and tomee/openejb failover via dynamic datasources? on my development/test server, I have the following: Resource id=jdbc/main type=javax.sql.DataSource JdbcDriver org.apache.derby.jdbc.EmbeddedDriver JdbcUrl jdbc:derby:C:/javadb/databases/mcmsdev;create=true UserName Password JtaManaged true jmxEnabled true LogSql false InitialSize 10 MaxActive 100 MaxIdle 30 MaxWait 1 minIdle 10 suspectTimeout 60 removeAbandoned true removeAbandonedTimeout 180 timeBetweenEvictionRunsMillis 3 jdbcInterceptors=StatementCache(max=128) /Resource Resource id=jdbc/fallback type=javax.sql.DataSource JdbcDriver org.apache.derby.jdbc.EmbeddedDriver JdbcUrl jdbc:derby:C:/javadb/databases/mcms;create=true UserName Password JtaManaged true jmxEnabled true LogSql false InitialSize 10 MaxActive 100 MaxIdle 30 MaxWait 1 minIdle 10 suspectTimeout 60 removeAbandoned true removeAbandonedTimeout 180 timeBetweenEvictionRunsMillis 3 jdbcInterceptors=StatementCache(max=128) /Resource Resource id=failover-router class-name=org.apache.openejb.resource.jdbc.router.FailOverRouter datasourceNames = jdbc/main,jdbc/fallback /Resource Resource id=jdbc/mcmsJta type=DataSource provider=RoutedDataSource router = failover-router /Resource should I be configuring tomcat jdbc pooling on the dynamic datasources, or on the routed datasource? also, I recognized something in the log file, since RoutedDataSource has no URL, the following shows up in the log when starting TomEE: INFO: Creating Resource(id=jdbc/mcmsJta) Nov 03, 2013 9:19:04 AM org.apache.openejb.assembler.classic.Assembler createResource INFO: can't find url for jdbc/mcmsJta will not monitor it On Sun, Nov 3, 2013 at 10:52 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: lookhttp:// svn.apache.org/repos/asf/tomee/tomee/trunk/container/openejb-core/src/main/java/org/apache/openejb/resource/jdbc/router/FailOverRouter.java last method it can still be enhanced a lot Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/11/3 Howard W. Smith, Jr. smithh032...@gmail.com: okay, and one last question, is there a bit more documentation on the following, so we can know what to expect, and the implementation is quite sound, working as designed and no known issues with the following? ul lidefault: the first is used while possible and others datasources are just backup, this is typically the failover case/li lirandom: any datasource of the list is used/li lireverse: between two call to a method the list is reversed/li liround-robin[%N]: round robin between datasources, you can specify how many step you browse between two calls using N (default is 1)/li /ul i saw the limitations on the referenced pages (dynamic datasources), but I didn't see any known issues in your/Romain's post/blog. please excuse my ignorance, if I have not heard or seen much chatter about this on the mail list. I usually try to pay attention to almost all tomee emails, especially those that interest me the most. :) On Sun, Nov 3, 2013 at 10:22 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: If you dont use it then thats ok. We close the pool then, not connections Le 3 nov. 2013 16:19, Howard W. Smith, Jr. smithh032...@gmail.com a écrit : FYI, I just stopped my local tomee, and recognized that my @Application @PreDestroy has my code that stops Apache Derby prior to main and fallback datasources are closed. is this okay? Nov 03, 2013 10:12:48 AM org.apache.catalina.core.StandardServer await INFO: A valid shutdown command was received via the shutdown port. Stopping the Server instance. Nov 03, 2013 10:12:48 AM org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler [http-nio-8080] Nov 03, 2013 10:12:48 AM org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler [ajp-bio-8009]
Re: Using TomEE/OpenEJB and failover of datasources
okay, good. that shows that I understood your blog/post, correctly, and add this to my app, accordingly. thanks! On Sun, Nov 3, 2013 at 4:20 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Failover is a facase over normal resources. Only these resource can/should be pooled Le 3 nov. 2013 21:51, Howard W. Smith, Jr. smithh032...@gmail.com a écrit : interesting. I can definitely use this as a reference if (ever) necessary, thanks. which brings me to my next question, // // take care next strategies can break multiple calls on the facade // it is only intended to be used for connection selection // I recognized that in the code. I know I make many calls to @Stateless @EJB facade objects to read/write data from/to database, and I also configured tomcat jdbc pool to allow for many connections...in/via tomee.xml Resource .../. so, my question... what is the rule of thumb when configuring jdbc pool and tomee/openejb failover via dynamic datasources? on my development/test server, I have the following: Resource id=jdbc/main type=javax.sql.DataSource JdbcDriver org.apache.derby.jdbc.EmbeddedDriver JdbcUrl jdbc:derby:C:/javadb/databases/mcmsdev;create=true UserName Password JtaManaged true jmxEnabled true LogSql false InitialSize 10 MaxActive 100 MaxIdle 30 MaxWait 1 minIdle 10 suspectTimeout 60 removeAbandoned true removeAbandonedTimeout 180 timeBetweenEvictionRunsMillis 3 jdbcInterceptors=StatementCache(max=128) /Resource Resource id=jdbc/fallback type=javax.sql.DataSource JdbcDriver org.apache.derby.jdbc.EmbeddedDriver JdbcUrl jdbc:derby:C:/javadb/databases/mcms;create=true UserName Password JtaManaged true jmxEnabled true LogSql false InitialSize 10 MaxActive 100 MaxIdle 30 MaxWait 1 minIdle 10 suspectTimeout 60 removeAbandoned true removeAbandonedTimeout 180 timeBetweenEvictionRunsMillis 3 jdbcInterceptors=StatementCache(max=128) /Resource Resource id=failover-router class-name=org.apache.openejb.resource.jdbc.router.FailOverRouter datasourceNames = jdbc/main,jdbc/fallback /Resource Resource id=jdbc/mcmsJta type=DataSource provider=RoutedDataSource router = failover-router /Resource should I be configuring tomcat jdbc pooling on the dynamic datasources, or on the routed datasource? also, I recognized something in the log file, since RoutedDataSource has no URL, the following shows up in the log when starting TomEE: INFO: Creating Resource(id=jdbc/mcmsJta) Nov 03, 2013 9:19:04 AM org.apache.openejb.assembler.classic.Assembler createResource INFO: can't find url for jdbc/mcmsJta will not monitor it On Sun, Nov 3, 2013 at 10:52 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: lookhttp:// svn.apache.org/repos/asf/tomee/tomee/trunk/container/openejb-core/src/main/java/org/apache/openejb/resource/jdbc/router/FailOverRouter.java last method it can still be enhanced a lot Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/11/3 Howard W. Smith, Jr. smithh032...@gmail.com: okay, and one last question, is there a bit more documentation on the following, so we can know what to expect, and the implementation is quite sound, working as designed and no known issues with the following? ul lidefault: the first is used while possible and others datasources are just backup, this is typically the failover case/li lirandom: any datasource of the list is used/li lireverse: between two call to a method the list is reversed/li liround-robin[%N]: round robin between datasources, you can specify how many step you browse between two calls using N (default is 1)/li /ul i saw the limitations on the referenced pages (dynamic datasources), but I didn't see any known issues in your/Romain's post/blog. please excuse my ignorance, if I have not heard or seen much chatter about this on the mail list. I usually try to pay attention to almost all tomee emails, especially those that interest me the most. :) On Sun, Nov 3, 2013 at 10:22 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: If you dont use it then thats ok. We close the pool then, not connections Le 3 nov. 2013 16:19, Howard W. Smith, Jr. smithh032...@gmail.com a écrit : FYI, I just stopped my local tomee, and recognized that my @Application @PreDestroy has my code that stops Apache Derby prior to main and fallback datasources are closed. is this okay? Nov 03, 2013 10:12:48 AM
Re: 1.6.0 release plans?
Hi, Is TomEE 1.6 release candidate something feasible this upcoming week (week 45) ? I can have large non-reg testing with our apps as soon as this release candidate is available... Thanks, Alex. On Wed, Oct 30, 2013 at 12:37 PM, Howard W. Smith, Jr. smithh032...@gmail.com wrote: understood, thanks. :) On Wed, Oct 30, 2013 at 7:34 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: this has been discussed on a lot of threads, we target 1.6 ATM then see to do a +1 version (2, 5 maybe 7, still under discussion) but this one will be obviously based on tomcat 8 + the whole apache EE 7 stack Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/10/30 Howard W. Smith, Jr. smithh032...@gmail.com: interesting response. well, tomcat 8 + myfaces 2.2 + some other components = tomee (javaee 7), right? tomcat 8 and myfaces 2.2 have already released. does tomee 1.7 (snapshot) = (possible) javaee 7 version/release? On Wed, Oct 30, 2013 at 1:46 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: When tomee will target javaee 7 Le 30 oct. 2013 05:26, Howard W. Smith, Jr. smithh032...@gmail.com a écrit : Mark, since you mentioned somewhat of a road map, maybe you, Romain, or one of the others can tell us when will MyFaces 2.2 be bundled with tomee(+) ? I would love to start using MyFaces 2.2 with tomee, but i don't want to use that until it is bundled in ZIP file. just a personal preference of mine. On Tue, Oct 29, 2013 at 4:16 PM, Mark Struberg strub...@yahoo.de wrote: yup, gonna start with cutting the actual release in a few hours. The next projects on the list are xbean and OpenWebBeans. LieGrue, strub - Original Message - From: Romain Manni-Bucau rmannibu...@gmail.com To: users@tomee.apache.org users@tomee.apache.org Cc: Sent: Tuesday, 29 October 2013, 17:14 Subject: Re: 1.6.0 release plans? Hi OpenJPA release work started, Jira are almost closed and the release should start soon Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/10/29 Alex The Rocker alex.m3...@gmail.com: Hello TomEE team, Would you please update us with TomEE 1.6.0 official release? For example, was the action mentionned by jean-Louis on OpenJPA done? When is planned something like an official beta or release candidate ? Thanks, Alex. On Wed, Oct 9, 2013 at 9:04 AM, Jean-Louis MONTEIRO jeano...@gmail.comwrote: First, push an official mail on OpenJPA mailling list asking for a 2.3.0 release. Waiting an answer within the usual 72 hours for example. If no answer or no way to get a release by October 20th or so (I don't care), then fork it internally as we did sometimes in the past and start releasing TomEE by end of November. That means more or less that we must freeze/finalize all on-going development by October the 15th I think. Thoughts? Jean-Louis 2013/10/8 Romain Manni-Bucau rmannibu...@gmail.com Technically yes, then the issue is we need somebody with all perms to release tomee (ping @David?). *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/10/8 Alex The Rocker alex.m3...@gmail.com @Romain, not sure to understand the details, but do you mean you may have a way to release TomEE+ 1.6.0 official release without waiting for the (unknown) OpenJPA 2.3.0 release? Thanks, Alex On Tue, Oct 8, 2013 at 4:55 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: I meant forking it for the release as usual, not using a snapshot which wouldn't be professional *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau*
Re: 1.6.0 release plans?
Hi I wouldnt expect it this month even if theorically possible Le 3 nov. 2013 23:19, Alex The Rocker alex.m3...@gmail.com a écrit : Hi, Is TomEE 1.6 release candidate something feasible this upcoming week (week 45) ? I can have large non-reg testing with our apps as soon as this release candidate is available... Thanks, Alex. On Wed, Oct 30, 2013 at 12:37 PM, Howard W. Smith, Jr. smithh032...@gmail.com wrote: understood, thanks. :) On Wed, Oct 30, 2013 at 7:34 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: this has been discussed on a lot of threads, we target 1.6 ATM then see to do a +1 version (2, 5 maybe 7, still under discussion) but this one will be obviously based on tomcat 8 + the whole apache EE 7 stack Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/10/30 Howard W. Smith, Jr. smithh032...@gmail.com: interesting response. well, tomcat 8 + myfaces 2.2 + some other components = tomee (javaee 7), right? tomcat 8 and myfaces 2.2 have already released. does tomee 1.7 (snapshot) = (possible) javaee 7 version/release? On Wed, Oct 30, 2013 at 1:46 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: When tomee will target javaee 7 Le 30 oct. 2013 05:26, Howard W. Smith, Jr. smithh032...@gmail.com a écrit : Mark, since you mentioned somewhat of a road map, maybe you, Romain, or one of the others can tell us when will MyFaces 2.2 be bundled with tomee(+) ? I would love to start using MyFaces 2.2 with tomee, but i don't want to use that until it is bundled in ZIP file. just a personal preference of mine. On Tue, Oct 29, 2013 at 4:16 PM, Mark Struberg strub...@yahoo.de wrote: yup, gonna start with cutting the actual release in a few hours. The next projects on the list are xbean and OpenWebBeans. LieGrue, strub - Original Message - From: Romain Manni-Bucau rmannibu...@gmail.com To: users@tomee.apache.org users@tomee.apache.org Cc: Sent: Tuesday, 29 October 2013, 17:14 Subject: Re: 1.6.0 release plans? Hi OpenJPA release work started, Jira are almost closed and the release should start soon Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/10/29 Alex The Rocker alex.m3...@gmail.com: Hello TomEE team, Would you please update us with TomEE 1.6.0 official release? For example, was the action mentionned by jean-Louis on OpenJPA done? When is planned something like an official beta or release candidate ? Thanks, Alex. On Wed, Oct 9, 2013 at 9:04 AM, Jean-Louis MONTEIRO jeano...@gmail.comwrote: First, push an official mail on OpenJPA mailling list asking for a 2.3.0 release. Waiting an answer within the usual 72 hours for example. If no answer or no way to get a release by October 20th or so (I don't care), then fork it internally as we did sometimes in the past and start releasing TomEE by end of November. That means more or less that we must freeze/finalize all on-going development by October the 15th I think. Thoughts? Jean-Louis 2013/10/8 Romain Manni-Bucau rmannibu...@gmail.com Technically yes, then the issue is we need somebody with all perms to release tomee (ping @David?). *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau * *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/10/8 Alex The Rocker alex.m3...@gmail.com @Romain, not sure to understand the details, but do you mean you may have a way to release TomEE+ 1.6.0 official release without waiting for the (unknown) OpenJPA 2.3.0 release? Thanks, Alex On Tue, Oct 8, 2013 at 4:55 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: I meant forking it for the release as usual, not using a snapshot which wouldn't be professional
Re: 1.6.0 release plans?
Started threads on XBean and OpenWebBeans about getting releases up. Branched in hopes we might get some progress. Updating the conversation on the dev@tomee list. On Sun, Nov 3, 2013 at 2:28 PM, Romain Manni-Bucau rmannibu...@gmail.comwrote: Hi I wouldnt expect it this month even if theorically possible Le 3 nov. 2013 23:19, Alex The Rocker alex.m3...@gmail.com a écrit : Hi, Is TomEE 1.6 release candidate something feasible this upcoming week (week 45) ? I can have large non-reg testing with our apps as soon as this release candidate is available... Thanks, Alex. On Wed, Oct 30, 2013 at 12:37 PM, Howard W. Smith, Jr. smithh032...@gmail.com wrote: understood, thanks. :) On Wed, Oct 30, 2013 at 7:34 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: this has been discussed on a lot of threads, we target 1.6 ATM then see to do a +1 version (2, 5 maybe 7, still under discussion) but this one will be obviously based on tomcat 8 + the whole apache EE 7 stack Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/10/30 Howard W. Smith, Jr. smithh032...@gmail.com: interesting response. well, tomcat 8 + myfaces 2.2 + some other components = tomee (javaee 7), right? tomcat 8 and myfaces 2.2 have already released. does tomee 1.7 (snapshot) = (possible) javaee 7 version/release? On Wed, Oct 30, 2013 at 1:46 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: When tomee will target javaee 7 Le 30 oct. 2013 05:26, Howard W. Smith, Jr. smithh032...@gmail.com a écrit : Mark, since you mentioned somewhat of a road map, maybe you, Romain, or one of the others can tell us when will MyFaces 2.2 be bundled with tomee(+) ? I would love to start using MyFaces 2.2 with tomee, but i don't want to use that until it is bundled in ZIP file. just a personal preference of mine. On Tue, Oct 29, 2013 at 4:16 PM, Mark Struberg strub...@yahoo.de wrote: yup, gonna start with cutting the actual release in a few hours. The next projects on the list are xbean and OpenWebBeans. LieGrue, strub - Original Message - From: Romain Manni-Bucau rmannibu...@gmail.com To: users@tomee.apache.org users@tomee.apache.org Cc: Sent: Tuesday, 29 October 2013, 17:14 Subject: Re: 1.6.0 release plans? Hi OpenJPA release work started, Jira are almost closed and the release should start soon Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/10/29 Alex The Rocker alex.m3...@gmail.com: Hello TomEE team, Would you please update us with TomEE 1.6.0 official release? For example, was the action mentionned by jean-Louis on OpenJPA done? When is planned something like an official beta or release candidate ? Thanks, Alex. On Wed, Oct 9, 2013 at 9:04 AM, Jean-Louis MONTEIRO jeano...@gmail.comwrote: First, push an official mail on OpenJPA mailling list asking for a 2.3.0 release. Waiting an answer within the usual 72 hours for example. If no answer or no way to get a release by October 20th or so (I don't care), then fork it internally as we did sometimes in the past and start releasing TomEE by end of November. That means more or less that we must freeze/finalize all on-going development by October the 15th I think. Thoughts? Jean-Louis 2013/10/8 Romain Manni-Bucau rmannibu...@gmail.com Technically yes, then the issue is we need somebody with all perms to release tomee (ping @David?). *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau * *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/10/8 Alex The Rocker alex.m3...@gmail.com @Romain, not sure to understand the details, but do you mean you may have a way to release
