分类
外汇短线交易策略

使用 XA 交易時的指導方針和限制

when to use xa-datasource

consulting different documentation and searching the internet I'm unsure when to use xa-datasources/transactions.

For example the book "Jboss in Action" states:

If you're clustering your application servers or wanting to use distributed transactions among multiple application servers, then you should use . Note that both and handle distributed transactions involving multiple data 使用 XA 交易時的指導方針和限制 sources. The difference is that handles them only within a single running application server, whereas 使用 XA 交易時的指導方針和限制 handles them among many running application servers.

So in short "Use xa-datasource when bulding a jboss cluster".

Before reading the book I thought, that I have to use xa-datasources in cases where one transaction spans multiple datasources. For example a method consuming a JMS 使用 XA 交易時的指導方針和限制 message and manipulating a JPA Entity. Regardless of wheter I use a cluster or 使用 XA 交易時的指導方針和限制 not.

I would really appreciate any help.

  • 118301 Views
  • Tags: none (add) jboss
1. Re: when to use xa-datasource

I've just been reading JBoss in Action as 使用 XA 交易時的指導方針和限制 well and was also stumped by what they said.

Like yourself I thought XA 使用 XA 交易時的指導方針和限制 was only required for multiple data sources (or other branches in the transaction e.g 使用 XA 交易時的指導方針和限制 JMS).

Fellow colleagues of mine insist this is what it means.

So I can't confirm 100%, but I'm sure (and so are my colleagues) the book is wrong

2. Re: when to use xa-datasource

thanks for your answer. I already thought I am the only fool not understanding this book passage.

I will try to 使用 XA 交易時的指導方針和限制 使用 XA 交易時的指導方針和限制 confirm our opinion and ask the authors of JBoss in Action.

If I get any answer I will post it here.

3. Re: when to use xa-datasource

At 使用 XA 交易時的指導方針和限制 使用 XA 交易時的指導方針和限制 the time that I wrote this text I checked this with the JBoss engineers 使用 XA 交易時的指導方針和限制 and that is what they stated - the XA data source is required only when 使用 XA 交易時的指導方針和限制 multiple JBoss AS instances are involved, or when you have JBoss AS and some external 使用 XA 交易時的指導方針和限制 service all managed by a transaction manager. Two-phase commit within a single JBoss AS instance is handled by the local data source.

  • Actions
4. Re: when to use xa-datasource

thanks for your reply and btw for writing this book. It's really very usefull for my daily work.

Regarding my question I am still not totally convinced. I don't want to be annoying, but perhaps you mixed two aspects of transactions in JBoss when writing the book or discussing with the jboss engineers. I did a lot of research to get the whole picture and right now I guess 使用 XA 交易時的指導方針和限制 the following:

local-tx-datasource vs. xa-datasource

There are local-tx-datasources and xa-datasources. local-tx-datasources can be used if there aren't any transactions spanning multiple transactional resources. As soon as you use two or more transactional resources in the same transaction e.g. a transactional session bean method manipulating JPA entities and producing JMS messages, you must use xa-datasources for the transactional resources.

JBossTS JTA for local-only transactions vs. JBossTS JTS for distributed transactions

If you use xa-datasources you need a transaction manager to coordinate the resources (with 2PC). This http://community.jboss.org/wiki/JBossTransactionsVersionGuide wiki page and this http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.1/html/Administration_And_Configuration_Guide/transaction.html#id2524403 guide state, that there are two different implementations or modules for this transaction manager. The JBossTS JTA module for local-only transactions and the JBossTS JTS module for distributed transactions. Both are capable to handle multiple XA resources but JBoss JTS can handle distributed transactions spanning multiple VMs and JBossTS JTA can only handle transactions in a single VM. In case of jboss clusters I'm not sure if every cluster configuration needs JBoss JTS. I would 使用 XA 交易時的指導方針和限制 guess that in a homogenous cluster JBoss JTA is sufficient because a transaction startet 使用 XA 交易時的指導方針和限制 by a transaction manager on a certain cluster node does not leave this node and 使用 XA 交易時的指導方針和限制 thus stays in a single VM.

As I said this is only my current guess about I think transactions within JBoss AS are working. Can anybody confirm or deny this?

when to use xa-datasource

consulting different documentation and searching the internet I'm unsure 使用 XA 交易時的指導方針和限制 when to use xa-datasources/transactions.

For example the book "Jboss in Action" states:

If you're 使用 XA 交易時的指導方針和限制 clustering your application servers or wanting to use distributed transactions among multiple application servers, then you should use . Note that both and handle distributed transactions involving multiple data sources. The 使用 XA 交易時的指導方針和限制 difference is that handles them only within a single running application server, whereas handles 使用 XA 交易時的指導方針和限制 them among many running application servers.

So in short "Use xa-datasource when bulding a 使用 XA 交易時的指導方針和限制 使用 XA 交易時的指導方針和限制 jboss cluster".

Before reading the book I thought, that I have to use xa-datasources in cases where one transaction spans multiple datasources. For example a method consuming a JMS message and manipulating a JPA Entity. Regardless of wheter I use a cluster or not.使用 XA 交易時的指導方針和限制 使用 XA 交易時的指導方針和限制 使用 XA 交易時的指導方針和限制 使用 XA 交易時的指導方針和限制

I would really appreciate any help.

  • 118301 Views
  • Tags: none (add) jboss
1. Re: when to use xa-datasource

I've just been reading JBoss in Action as well and was also stumped by what they said.

Like yourself I thought XA was 使用 XA 交易時的指導方針和限制 only required for multiple data sources (or other branches in the transaction e.g JMS).

Fellow colleagues of mine insist this is what it means.

So I can't confirm 100%, but I'm sure (and so are my colleagues) the book is wrong

2. Re: when to use xa-datasource

thanks for your answer. I already thought I am the only fool not understanding this book passage.

I will try to confirm our opinion and ask the authors of JBoss in Action.

If I get any answer 使用 XA 交易時的指導方針和限制 I will post it here.

3. Re: when to use xa-datasource

At 使用 XA 交易時的指導方針和限制 使用 XA 交易時的指導方針和限制 the time that I wrote this text I checked this with the JBoss engineers and that is what they stated - the XA data source is required only when multiple JBoss AS instances are involved, or when you have JBoss AS and some external service all managed by a transaction manager. Two-phase commit within a single JBoss AS instance is handled by the local data source.

  • Actions
4. Re: when to use xa-datasource

thanks for your reply and btw for writing this book. It's really very usefull for my daily work.

Regarding my question I am still not totally convinced. I don't want to be annoying, but perhaps you mixed two aspects of transactions in JBoss when writing the book or discussing with the jboss engineers. I did a lot of research to get the whole picture and right now I guess the following:

local-tx-datasource vs. xa-datasource

There are local-tx-datasources and xa-datasources. local-tx-datasources can be used if there aren't any transactions spanning multiple transactional resources. As soon as you use two or more transactional resources in the same transaction e.g. a transactional session bean method manipulating 使用 XA 交易時的指導方針和限制 使用 XA 交易時的指導方針和限制 JPA entities and producing JMS messages, you must use xa-datasources for the transactional resources.

JBossTS JTA for local-only transactions vs. JBossTS JTS for distributed transactions

If you use xa-datasources you need a transaction manager to coordinate the resources (with 2PC). This http://community.jboss.org/wiki/JBossTransactionsVersionGuide wiki page and this http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.1/html/Administration_And_Configuration_Guide/transaction.html#id2524403 guide state, that 使用 XA 交易時的指導方針和限制 使用 XA 交易時的指導方針和限制 there are two different implementations or modules for this transaction manager. The JBossTS JTA module 使用 XA 交易時的指導方針和限制 for local-only transactions and the JBossTS JTS module for distributed transactions. Both are capable to handle multiple XA resources but JBoss JTS can handle distributed transactions spanning multiple VMs and JBossTS JTA can only handle transactions in a single VM. In case of jboss clusters I'm not sure if every cluster configuration needs JBoss JTS. I would guess that in a homogenous cluster JBoss JTA is sufficient because a transaction startet by 使用 XA 交易時的指導方針和限制 a transaction manager on a certain cluster node does not leave this node and thus stays in a single VM.

As I said this is only my current guess 使用 XA 交易時的指導方針和限制 使用 XA 交易時的指導方針和限制 about I think transactions within JBoss AS are working. Can anybody confirm or deny this?使用 XA 交易時的指導方針和限制

使用 XA 交易時的指導方針和限制

加入QQ群:457200227(SAP S4 HANA技术交流) 一起学习S4 HANA .

我们最近遇到了" Xacute Connector",可用于调用交易(与转轮服务相同)。 但是这里的区别在于,我们可以利用SSO功能,而无需使用Xacute查询。 由于各种原因,我们想避免使用Xacute查询,其中之一是32个输入参数的限制。

我们决定为此目的使用Xacute Connector,但是,在不了解此服务的可靠性的情况下,我们仍然有些犹豫。 有人使用过吗? 该服务的可靠性如何?它将在生产过程中处理重载(非常高的使用量)吗?

点击此处---> EasySAP.com 一起学习S4 HANA .

加入QQ群:457200227(SAP S4 HANA技术交流) 一起学习S4 HANA .

我们最近遇到了" Xacute Connector",可用于调用交易(与转轮服务相同)。 但是这里的区别在于,我们可以利用SSO功能,而无需使用Xacute查询。 由于各种原因,我们想避免使用Xacute查询,其中之一是32个输入参数的限制。

我们决定为此目的使用Xacute Connector,但是,在不了解此服务的可靠性的情况下,我们仍然有些犹豫。 有人使用过吗? 该服务的可靠性如何?它将在生产过程中处理重载(非常高的使用量)吗?

使用 XA 交易時的指導方針和限制

农业无人机

农业无人机

农业无人车

农业无人车

农机自驾仪

农机自驾仪

遥感无人机

遥感无人机

农业物联网

农业物联网

智慧农业系统

智慧农业系统

3WWDZ-35A型农业无人机使用说明-V3.0

3WWDZ-20B型农业无人机使用说明-V3.0

3WWDZ-15.2A型农业无人机使用说明-V3.0

极飞睿图®2使用说明-V1.1

极飞®睿喷2 V50版使用说明-V1.0

极飞️®睿喷2 P100版使用说明-V1.0

极飞®睿播2 V50版使用说明-V1.2

极飞®睿播2 P100版(60L)使用说明-V1.1

极飞®睿播2 P100版(50L)使用说明-V1.2

极飞®睿播2 P80版使用说明-V1.1

极飞®V50 2022款农业无人飞机使用说明-V1.1

极飞®GC9000移动超充站使用说明-V1.0

极飞®CM27000充电管理器使用说明-V1.1

极飞®CM13300充电管理器使用说明-V1.1

极飞®B13960S 智能电池使用说明-V1.2

极飞®ACS3单手遥控器使用说明-V1.0

P100 2022款农业无人机使用说明-V1.1

V40 2021款智能播撒系统快速入门指南-V2.0

P40 2021款智能播撒系统快速入门指南-V2.0

农用北斗差分定位终端使用说明-V1.1

P80 2021款智能播撒系统快速入门指南-V2.0

禁飞区飞行解禁申请书模板

P30 2020 款入门指南-V1.1

P30 2019 款入门指南-V1.4

P20 2020 款入门指南-V1.1

P20 2019款入门指南-V1.3

XP 2020款入门指南-V1.1

P30 2019快速入门指南V1.2

P20 2019快速入门指南V1.1

P30 2019模块拆装及保养手册V1.0

极飞无人机操作安全须知V1.1

无人驾驶航空器经营许可证申请指引V1.1

民用无人驾驶航空器实名制登记指引V1.1

P20 2017 款植保无人机升级安装指引 V1.1

天目XCOPE™免责声明和警告

P30 产品及配件说明清单 V1

P20 2018 款植保无人机产品及配件说明清单 V1

P20 2017款快速安装说明手册V1.1

P20 2017 款植保无人机升级拆解指引-V1

P20 2017 款(升级版)快速安装说明手册 -V1.2

P10 2018 款植保无人机产品及配件说明清单 V1

极飞A2智能手持终端联网说明V1

XP 2020款农业无人机宣传视频

XP 2020款农业无人机渲染图

P 系列 2019 使用 XA 交易時的指導方針和限制 款植保无人机系统渲染图

P30 2018款植保无人机渲染图

P20 2018款植保无人机渲染图

P10 2018款植保无人机渲染图

P30 2018款植保无人机官方宣传视频

农业无人机

农业无人车

农机自驾仪

遥感无人机

农业物联网

智慧农业系统

    3WWDZ-35A型农业无人机使用说明-V3.0 2022-04-18

极飞农服为您提供地块测绘和管理、农业无人机作业和管理、作业记录查询等一站式作业功能。全新的 U1 设计,简易的交互操作,直观的信息展示,让您可以快速掌握高效作业的方式,获得出色的作业效果。极飞农服,专注农业效率与服务。

极飞农业 app 使用 XA 交易時的指導方針和限制 是一款提供农业自主航线作业及农业地理测绘的移动终端应用软件,可一站式实现农业地块管理、多维度植保作业、作业记录以及植保设备管理功能。极飞农业 app 灵活易用,智能高效,结合极飞 P 系列无人机,帮助用户显著提高农业生产效率。

极飞稻草人是极飞科技专为农业物联网设备开发的智能交互终端,连接着土地、作物、农民与消费者,既可帮助农业生产者远程管理设备,实时查看全生长周期的作物情况、气象与土壤数据,实现生产环节可追溯,也可通过数据共享帮助消费者进行农产品安全追溯,建立消费信任,提供食品安全保证。 支持的极飞农业物联网设备包括:IFC16 农田智能相机、IFC16S 农田智能相机、IWS7 农田气象站、IWS3 农田气象站、ISM50 土壤监测仪等。

农机自驾仪APP 是极飞科技针对极飞 XAPC 自动驾驶仪开发的应用软件,能够实现自动驾驶作业,农田地块管理、农事作业记录以及农机农具管理功能。农机自驾仪APP 操作简单,配合自动驾驶仪控制传统农机,精准执行既定规划的路线作业,使传统农机实现智能化,进一步提高农业生产效率。