[JBoss JIRA] (WFLY-1033) Enhance XTS AS7 configuration
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/WFLY-1033?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated WFLY-1033:
--------------------------------
Fix Version/s: (was: 11.0.0.Final)
> Enhance XTS AS7 configuration
> -----------------------------
>
> Key: WFLY-1033
> URL: https://issues.jboss.org/browse/WFLY-1033
> Project: WildFly
> Issue Type: Enhancement
> Components: XTS
> Reporter: Andrew Dinn
> Priority: Minor
>
> The current integration of XTS into AS7 as an AS7 extension allows optional configuration of the coordinator URL from the <xts/> element in the AS7 standalone configuration file. No other configuration options are currently supported.
> XTS ought to support more precise configuration. IN particular, it ought to be possible to enable or disable deployment of coordinator, participant or client services independently and also to choose whether to deploy WS-AT or WS-BA services or both. This requires selectively deploying only the required web service endpoints, selectively executing the required initialization routines and selectively loading the required high level service implementations and context factory implementations.
> The XTS implementation has already been factored so as to to support such discriminated bootstrapping. So this task only requires modifying the AS7 extension code to manage the relevant configuration information and install the relevant values into the XTS environment configuration beans before starting the XTS service.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 4 months
[JBoss JIRA] (WFLY-5574) org.wildfly.test.extension.rts InboundBridgeTestCase failing when transaction uses JTS
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/WFLY-5574?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated WFLY-5574:
--------------------------------
Fix Version/s: (was: 11.0.0.Final)
> org.wildfly.test.extension.rts InboundBridgeTestCase failing when transaction uses JTS
> --------------------------------------------------------------------------------------
>
> Key: WFLY-5574
> URL: https://issues.jboss.org/browse/WFLY-5574
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite, Transactions
> Affects Versions: 10.0.0.CR3
> Reporter: Ondra Chaloupka
> Assignee: Gytis Trikleris
> Priority: Minor
> Attachments: server.log
>
>
> There is failures in testcase org.wildfly.test.extension.rts.InboundBridgeTestCase when transaction uses JTS.
> Example of the failure
> {code}
> testCommit(org.wildfly.test.extension.rts.InboundBridgeTestCase) Time elapsed: 2.54 sec <<< FAILURE!
> java.lang.AssertionError: expected:<4> but was:<5>
> {code}
> The JBOSS_HOME distribution is change to transaction to be run with JTS: changing the {{docs/example/standalone-rts.xml}} to switch transactions parameter in iiop orb subsystem to {{full}} and adding {{jts}} element to transactions subsystem.
> When JBOSS_HOME is set then I've run the test in this way
> {{./integration-tests.sh clean install -Dts.noSmoke -Dts.rts -Djboss.dist=$JBOSS_HOME -Dtest=InboundBridgeTestCase}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 4 months
[JBoss JIRA] (WFLY-9271) Create CommandDispatcher-based BroadcastEndpoint
by Paul Ferraro (JIRA)
Paul Ferraro created WFLY-9271:
----------------------------------
Summary: Create CommandDispatcher-based BroadcastEndpoint
Key: WFLY-9271
URL: https://issues.jboss.org/browse/WFLY-9271
Project: WildFly
Issue Type: Task
Components: Clustering, JMS
Affects Versions: 11.0.0.CR1
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 12.0.0.Alpha1
A broadcast endpoint implementation based on the clustering API insulates the ActiveMQ Artemis integration from JGroups API changes (e.g. JGroups 3.6->4.0 migration) and facilitates the sharing of JGroups resources across the server.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 4 months