[JBoss JIRA] (WFLY-5574) org.wildfly.test.extension.rts InboundBridgeTestCase failing when transaction uses JTS
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-5574?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-5574:
-------------------------------
Fix Version/s: 11.0.0.CR2
(was: 11.0.0.CR1)
> 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
> Fix For: 11.0.0.CR2
>
> 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, 8 months
[JBoss JIRA] (WFLY-5551) Formalize ejb clustering modules into a proper subsystem
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-5551?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-5551:
-------------------------------
Fix Version/s: 11.0.0.CR2
(was: 11.0.0.CR1)
> Formalize ejb clustering modules into a proper subsystem
> --------------------------------------------------------
>
> Key: WFLY-5551
> URL: https://issues.jboss.org/browse/WFLY-5551
> Project: WildFly
> Issue Type: Enhancement
> Components: Clustering
> Affects Versions: 10.0.0.CR3
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 11.0.0.CR2
>
>
> Currently, the coupling between the ejb3 subsystem and the modules required for the distributed cache is very loose.
> Consequently, misconfiguration (e.g. a missing "ejb" cache-container) can prevent deployment from succeeding without an adequate explanation.
> The subsystem would define the requisite cache-container, exposed as a capability.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (WFLY-5550) Formalize web session clustering modules into a proper subsystem
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-5550?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-5550:
-------------------------------
Fix Version/s: 11.0.0.CR2
(was: 11.0.0.CR1)
> Formalize web session clustering modules into a proper subsystem
> ----------------------------------------------------------------
>
> Key: WFLY-5550
> URL: https://issues.jboss.org/browse/WFLY-5550
> Project: WildFly
> Issue Type: Enhancement
> Components: Clustering
> Affects Versions: 10.0.0.CR3
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 11.0.0.CR2
>
>
> Currently, the coupling between the undertow subsystem and the modules required for distributed web session manager and single sign-on manager support is very loose.
> Consequently, misconfiguration (e.g. a missing "web" cache-container) can prevent deployment from succeeding without an adequate explanation.
> The subsystem would define the requisite cache-container, exposed as a capability.
> This subsystem would exposes a number of profiles, containing the configuration traditionally specified in jboss-web.xml, as well as the cache configuration to use (specified by cache-container + cache name). jboss-web.xml would only need to reference a profile by name, or, if unspecified, use the default profile.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (WFLY-5497) Add <distributable/> to shared-session-config schema
by Jason Greene (JIRA)
[ https://issues.jboss.org/browse/WFLY-5497?page=com.atlassian.jira.plugin.... ]
Jason Greene updated WFLY-5497:
-------------------------------
Fix Version/s: 11.0.0.CR2
(was: 11.0.0.CR1)
> Add <distributable/> to shared-session-config schema
> ----------------------------------------------------
>
> Key: WFLY-5497
> URL: https://issues.jboss.org/browse/WFLY-5497
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering, Web (Undertow)
> Affects Versions: 10.0.0.CR2
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 11.0.0.CR2
>
>
> Currently, the shared-session-config does not indicate whether a distributable or non-distributable session manager should be used. Consequently, we assign the session manager implementation based on the availability of the module providing the distributed implementation. Since the default infinispan web session configuration attempts to passivate sessions on shutdown, users will see NotSerializableExceptions on shutdown if they use non-serializable session attributes - even if their web applications do not define themselves as being <distributable/>.
> To clarify this ambiguity, we should add a <distributable/> element (a la web.xml) to the shared-session-config schema to determine which session manager implementation to use.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months