由于需要从一个远程机器取数据。处理后保存到本地数据库处理。用 wildfly datasource 会报:

[com.arjuna.ats.arjuna] (default task-6) ARJUNA012140: Adding multiple last resources is disallowed. Trying to add LastResourceRecord(XAOnePhaseResource(LocalXAResourceImpl@7f19c56d[connectionListener=1......

这主要是jpa里面的的事物,只允许一个datasource连接。

采用xa-datasource即可。


另一种方案是在主控程序中禁止事务。将数据库的操作写在其他类中,使用事务。即只有要修改的操作才需要事务。

更一步,可以在远程取数据的类中,也是不需要事务的。这样就可以inject 需要使用事务的类。

主控类:

package com.italktv.iof.service;

import java.util.List;
import java.util.logging.Logger; import javax.annotation.Resource;
import javax.ejb.Schedule;
import javax.ejb.Stateless;
import javax.ejb.Timer;
import javax.ejb.TimerService;
import javax.ejb.TransactionAttribute;
import javax.ejb.TransactionManagement;
import javax.inject.Inject; import com.italktv.iof.entity.AccountInfoSync; @Stateless
@TransactionManagement(javax.ejb.TransactionManagementType.CONTAINER)
@TransactionAttribute(javax.ejb.TransactionAttributeType.NEVER)
public class SyncTableTimer { @Inject
private Logger logger; @Resource
private TimerService timerService; @Inject
IOFDbUtil iof; @Inject
private MySqlUtil mysql; // @Schedule(hour = "6", minute = "0", second = "0", persistent = false ,info = "6点执行 ")
@Schedule(hour = "*", minute = "*/1", second = "0", persistent = false, info = " ")
public void automaticCustomer() {
logger.info("=== job " + " started ====");
doTask();
logger.info("=== job end ====");
} private void cancelTimers() {
for (Timer timer : timerService.getTimers()) {
// timer.cancel();
}
} private void doTask() {
List<AccountInfoSync> list;
list = iof.getList();
while (list.size() > 0) {
logger.info(" list.size=" + list.size());
mysql.saveList(list);
list = iof.getList();
}
}
}

连接数据源1:

@Stateless
public class MySqlUtil { @Inject
private Logger logger; @PersistenceContext(unitName = "primary")
protected EntityManager em; public void saveList(List<AccountInfoSync> list) {
String dataSql = "select * " + "from profile where id=1";
Query nativeQuery = em.createNativeQuery(dataSql, MacProfile.class); MacProfile i;
try {
i = (MacProfile) nativeQuery.getSingleResult();
//
} catch (NoResultException e) {
i = new MacProfile();
} } }

连接数据源2,select操作

@Stateless
@TransactionManagement(javax.ejb.TransactionManagementType.CONTAINER)
@TransactionAttribute(javax.ejb.TransactionAttributeType.NEVER)
public class IOFDbUtil { @Inject
private Logger logger; @PersistenceContext(unitName = "theirDb")
private EntityManager theirDb; int FETCH_MAX_SIZE = 1;
int start = 0; @PostConstruct
void init() { } public List<AccountInfoSync> getList() { List<AccountInfoSync> list = null; while (true) {
String dataSql = "select * from dbtable "
+ "where id>" + start + " and id<=" + start + "+" + FETCH_MAX_SIZE;
Query nativeQuery = iof.createNativeQuery(dataSql, AccountInfoSync.class); list = (List<AccountInfoSync>) nativeQuery.getResultList();
start += FETCH_MAX_SIZE;
if (list.size() < 1 && start > maxid)
break; if (list.size() < 1) {
continue;
} for (AccountInfoSync iofsync : list) {
logger.info(iofsync.toString());
}
break;//找到就停止
}
return list;
} @Inject
MySqlUtil mm; private int getLastId() { mm.test();
return 0;
} }

  • 使用xa-datasource解决方案

standardalone.xml中:

 <subsystem xmlns="urn:jboss:domain:datasources:4.0">
<datasources>
<datasource jndi-name="java:jboss/datasources/ExampleDS" pool-name="ExampleDS" enabled="true" use-java-context="true">
<connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE</connection-url>
<driver>h2</driver>
<security>
<user-name>sa</user-name>
<password>sa</password>
</security>
</datasource>
<datasource jndi-name="java:jboss/datasources/MySqlDS" pool-name="MySqlDS" enabled="true" use-java-context="true">
<connection-url>jdbc:mysql://localhost:3306/statisticsystem</connection-url>
<driver>mysql</driver>
<security>
<user-name>jboss</user-name>
<password>jboss</password>
</security>
</datasource>
<datasource jndi-name="java:jboss/datasources/MySqlStatBank" pool-name="MySqlStatBank" enabled="true" use-java-context="true">
<connection-url>jdbc:mysql://211.100.75.204:5029/statistics</connection-url>
<driver>mysql</driver>
<security>
<user-name>root</user-name>
<password>@^#coopen</password>
</security>
</datasource>
<xa-datasource jndi-name="java:jboss/datasources/MySqlStatBank1" pool-name="MySqlStatBank1" enabled="true" use-java-context="true">
<xa-datasource-property name="ServerName">
211.100.75.204
</xa-datasource-property>
<xa-datasource-property name="PortNumber">
5029
</xa-datasource-property>
<xa-datasource-property name="DatabaseName">
statistics
</xa-datasource-property>
<driver>mysql</driver>
<xa-pool>
<min-pool-size>5</min-pool-size>
<initial-pool-size>5</initial-pool-size>
<max-pool-size>100</max-pool-size>
<prefill>true</prefill>
</xa-pool>
<security>
<user-name>root</user-name>
<password>@^#coopen</password>
</security>
</xa-datasource>
<drivers>
<driver name="h2" module="com.h2database.h2">
<xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
</driver>
<driver name="mysql" module="com.mysqldatabase.mysql">
<driver-class>com.mysql.jdbc.Driver</driver-class>
<xa-datasource-class>com.mysql.jdbc.jdbc2.optional.MysqlXADataSource</xa-datasource-class>
</driver>
</drivers>
</datasources>
</subsystem>

persistent.xml:

<?xml version="1.0" encoding="UTF-8"?>
<persistence xmlns="http://xmlns.jcp.org/xml/ns/persistence"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd"
version="2.1"> <persistence-unit name="statLog">
<jta-data-source>java:jboss/datasources/MySqlStatBank1</jta-data-source>
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<!-- <class>com.italktv.colnv.stat.entity.LogOfPlay</class> -->
<!-- <class>com.italktv.colnv.stat.entity.LogOfView</class> --> <properties>
<property name="hibernate.hbm2ddl.auto" value="create-drop" />
<!-- <property name= "hibernate.hbm2ddl.auto" value ="validate" /> create-drop -->
<property name="hibernate.jdbc.fetch_size" value="15" />
<property name="hibernate.jdbc.batch_size" value="10" />
<property name="hibernate.show_sql" value="true" />
<property name="hibernate.format_sql" value="true"></property> <!--
<property name="javax.persistence.schema-generation.database.action" value="drop-and-create"/>
<property name="javax.persistence.schema-generation-target" value="scripts"/>
<property name="javax.persistence.ddl-create-script-target" value="e:\createSeats.sql"/>
<property name="javax.persistence.ddl-drop-script-target" value="e:/dropSeats.sql"/>
-->
</properties> </persistence-unit> <persistence-unit name="primary" >
<class>com.italktv.colnv.stat.entity.Seat</class>
<class>com.italktv.colnv.stat.entity.SeatType</class>
<class>com.italktv.colnv.stat.entity.LogOfPlayDuration</class>
<class>com.italktv.colnv.stat.entity.ReportLiveHits</class> <properties>
<property name="hibernate.hbm2ddl.auto" value="update" />
<!-- <property name= "hibernate.hbm2ddl.auto" value ="validate" /> create-drop -->
<property name="hibernate.jdbc.fetch_size" value="15" />
<property name="hibernate.jdbc.batch_size" value="10" />
<property name="hibernate.show_sql" value="true" />
<property name="hibernate.format_sql" value="true"></property> <!--
<property name="javax.persistence.schema-generation.database.action" value="drop-and-create"/>
<property name="javax.persistence.schema-generation-target" value="scripts"/>
<property name="javax.persistence.ddl-create-script-target" value="e:\createSeats.sql"/>
<property name="javax.persistence.ddl-drop-script-target" value="e:/dropSeats.sql"/>
-->
</properties>
</persistence-unit> </persistence>

mysql driver的配置参考以前文档,在

 <driver name="mysql" module="com.mysqldatabase.mysql">

调用:
public class PlayDurationTask {

    @PersistenceContext(unitName = "statLog")
private EntityManager emStatLog; String query = "SELECT * FROM statistics.log_2016 ;";
List aa = emStatLog.createNativeQuery(query).getResultList();
//ddl语句用 createNativeUpdate
// 处理 for (int i = 0; i < aa.size(); i++) {
Object[] obj = (Object[]) aa.get(i);
// 使用obj[0],obj[1],obj[2]...取出属性 
... ...
}
} class two{

@PersistenceContext(unitName = "primary")
private EntityManager em ;
public void genLiveReport() {
em.createNativeQuery(LIVE_PLAY_USERS_BY_MAINID).executeUpdate();
logger.info(LIVE_PLAY_USERS_BY_MAINID);

}

 

参考:

Demystifying Datasource JTA and XA settings on JBoss-WildFly

One topic which is often misunderstood by middleware administrators is the configuration of JTA and XA attributesand their effect on transactions. Let's see more in practice.

Basically on a JBoss AS 6/WildFly configuration you can choose three different strategies as far as transactioons are concerned:

1) Setting jta = false and Non-XA datasource

1
<datasource jta="false"  . . . >

When setting this option you will be responsible for managing by yourself the transactions.  For example, the following code will work when using a Datasource with JTA=false:

1
2
3
4
5
6
7
8
9
10
11
12
@Resource(mappedName="java:jboss/datasources/ExampleDS"
private DataSource ds; 
. . . . . . . . . . .
Connection conn = ds.getConnection();
conn.setAutoCommit(false);
 
PreparedStatement stmt = conn.prepareStatement("INSERT into PROPERTY values (?,?)");
stmt.setString(1,key);
stmt.setString(2,value);
stmt.execute();
 
conn.commit();

Please note: the datasource with jta=false corresponds exactly to the older definition of local-tx-datasource you can find in JBoss AS 4/5

What if you are using JPA instead ?

So, when using plain JDBC you can handle by yourself transaction boundaries using commit/rollback. What about if you are using JPA with JTA=false? in short, the transaction-type for JPA will be RESOURCE_LOCAL. This would use basic JDBC-level transactions. In such scenario you are responsible for EntityManager (PersistenceContext/Cache) creating and tracking and you have to follow these rules:

  • You must use the EntityManagerFactory to get an EntityManager
  • The resulting EntityManager instance is a PersistenceContext/Cache An EntityManagerFactory can be injected via the @PersistenceUnit annotation only (not @PersistenceContext)
  • You are not allowed to use @PersistenceContext to refer to a unit of type RESOURCE_LOCAL
  • You must use the EntityTransaction API to begin/commit around every call to your EntityManger

Here is an example of using JPA with a RESOURCE_LOCAL transaction:

1
2
3
4
5
6
7
@PersistenceUnit(unitName="unit01")
private EntityManagerFactory emf;
     
EntityManager em = emf.createEntityManager();
em.getTransaction().begin();
em.persist(mag);
em.getTransaction().commit();

 2) Setting jta = true and Non-XA datasource

1
<datasource jta="true"  . . . >

This is the default. When JTA is true, the JCA connection pool manager knows to enlist the connection into the JTA transaction. This means that, if the Driver and the database support it, you can use JTA transaction for a single resource.

1
2
3
4
5
6
@PersistenceContext(unitName = "unit01")
private EntityManager entityManager;
 
public void addMovie(Movie movie) throws Exception {
        entityManager.persist(movie);
}

If you try to manage JDBC transactions by yourself when jta=true an exception will be raised:

1
2
3
12:11:17,145 SEVERE [com.sample.Bean] (http-/127.0.0.1:8080-1) null: java.sql.SQLException: You cannot set autocommit during a managed transaction!
    at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.setJdbcAutoCommit(BaseWrapperManagedConnection.java:961)
    at org.jboss.jca.adapters.jdbc.WrappedConnection.setAutoCommit(WrappedConnection.java:716)

 3) Using an XA datasource

An XA transaction, in the most general terms, is a "global transaction" that may span multiple resources. A non-XA transaction always involves just one resource.

1
<xa-datasource . . . .>

An XA transaction involves a coordinating transaction manager, with one or more databases (or other resources, like JMS) all involved in a single global transaction. Non-XA transactions have no transaction coordinator, and a single resource is doing all its transaction work itself.

The Transaction Manager coordinates all of this through a protocol called Two Phase Commit (2PC). This protocol also has to be supported by the individual resources.

In terms of datasources, an XA datasource is a data source that can participate in an XA global transaction. A non-XA datasource can't participate in a global transaction

wildfly jobss 同时连接多个数据源 datasource xa-datasource的更多相关文章

  1. wildfly jobss 同时连接多个数据源

    由于需要从一个远程机器取数据.处理后保存到本地数据库处理.用 wildfly datasource 会报: [com.arjuna.ats.arjuna] (default task-6) ARJUN ...

  2. Netbeans 中创建数据连接池和数据源步骤(及解决无法ping通问题)

    1.启动glassfish服务器, 在浏览器的地址栏中输入 http://localhost:4848 2.首先建立JDBC Connection Pools: 3.new 一个Connectio P ...

  3. jdbc基础 (五) 连接池与数据源 DBCP以及C3P0的使用

    一.连接池的概念和使用 在实际应用开发中,特别是在WEB应用系统中,如果JSP.Servlet或EJB使用JDBC直接访问数据库中的数据,每一次数据访问请求都必须经历建立数据库连接.打开数据库.存取数 ...

  4. 在Tomcat中配置连接池和数据源

    1.DataSource接口介绍 (1)DataSource 概述 JDBC1.0原来是用DriverManager类来产生一个对数据源的连接.JDBC2.0用一种替代的方法,使用DataSource ...

  5. spring boot 连接多个数据源

    在springboot中有需要连接多个数据源的情况. 首先配置文件application.properties中添加两个数据源连接字符串 mybatis.type-aliases-package=co ...

  6. Spring学习11-Spring使用proxool连接池 管理数据源

    Spring 一.Proxool连接池简介及其配置属性概述   Proxool是一种Java数据库连接池技术.是sourceforge下的一个开源项目,这个项目提供一个健壮.易用的连接池,最为关键的是 ...

  7. 连接池、数据源、JNDI三者间的关系及用法

    连接池:连接池是由容器(比如Tomcat)提供的,用来管理池中的连接对象.连接池自动分配连接对象并对闲置的连接进行回收.连接池中的连接对象是由数据源(DataSource)创建的.连接池(Connec ...

  8. Spring使用proxool连接池 管理数据源

    一.Proxool连接池简介及其配置属性概述 Proxool是一种Java数据库连接池技术.是sourceforge下的一个开源项目,这个项目提供一个健壮.易用的连接池,最为关键的是这个连接池提供监控 ...

  9. c3p0 连接池配置数据源

    <!-- 配置数据源 --> <bean id="dataSource" class="com.mchange.v2.c3p0.ComboPooledD ...

随机推荐

  1. 介绍HTTP协议的传输过程

    1.HTTP是面向事物的应用层协议,它使用TCP连接进行可靠传输,服务器默认监听在80端口 2.服务流程 从协议执行过程来说,当浏览器要访问www服务器时,首先要对服务器进行域名解析(DNS协议).一 ...

  2. Canary机制的绕过

    目标程序下载 提取码:8ypi 1.检查程序开启了哪些安全保护机制 Canary与NX开启了 Canary机制简介 64位的canary机制,会在函数头部添加: mov rax,QWORD PTR f ...

  3. js格式化时间

    转自:https://blog.csdn.net/u010964869/article/details/51095827 显示格式为:yyyy-mm-dd hh:mi:ss function form ...

  4. [北航矩阵理论A]课程笔记

    [北航矩阵理论A]课程笔记 一.特征值 特征根相关: 设任一方阵 \(A = (a_{ij})_{n\times n} \in C^{n\times n}\) 特征多项式 \(T(\lambda)=| ...

  5. 2017-2018-2 1723《程序设计与数据结构》实验四 & 实验五 & 课程总结 总结

    作业地址 实验四作业:https://edu.cnblogs.com/campus/besti/CS-IMIS-1723/homework/1943 提交情况如图: 实验五作业:https://edu ...

  6. CI框架--数据库Query_Builder中的方法

    下面是DB_Query_Builder.php中,各个方法的声明: 选择字段(select) public function select($select = '*', $escape = NULL) ...

  7. PAT 1016 部分A+B

    https://pintia.cn/problem-sets/994805260223102976/problems/994805306310115328 正整数A的“D~A~(为1位整数)部分”定义 ...

  8. Spring Framework: @RestController vs @Controller

    https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/web/bind/annota ...

  9. Bootstrap Validator使用特性,动态(Dynamic)添加的input的验证问题

    http://1000hz.github.io/bootstrap-validator/#validator-usage Validated fields By default, the valida ...

  10. Docker(十六)-Docker的daemon.json的作用

    docker安装后默认没有daemon.json这个配置文件,需要进行手动创建.配置文件的默认路径:/etc/docker/daemon.json 一般情况,配置文件 daemon.json中配置的项 ...