[JBoss JIRA] (WFLY-2789) Remote client transaction timeout values are overwrote by hardcoded values
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2789?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated WFLY-2789:
------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1056585, https://bugzilla.redhat.com/show_bug.cgi?id=1093128, https://bugzilla.redhat.com/show_bug.cgi?id=1093752, https://bugzilla.redhat.com/show_bug.cgi?id=1093753, https://bugzilla.redhat.com/show_bug.cgi?id=1159058 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1056585, https://bugzilla.redhat.com/show_bug.cgi?id=1093128, https://bugzilla.redhat.com/show_bug.cgi?id=1093752, https://bugzilla.redhat.com/show_bug.cgi?id=1093753)
> Remote client transaction timeout values are overwrote by hardcoded values
> --------------------------------------------------------------------------
>
> Key: WFLY-2789
> URL: https://issues.jboss.org/browse/WFLY-2789
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Johnathon Lee
> Assignee: David Lloyd
> Fix For: 8.1.0.Final, 9.0.0.Alpha1
>
>
> The EJB3 interceptor is not using client values for timeouts, this is a problem for users trying to use EJB for transaction propagation.
> Refer to the code in https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jbo...:
> private void createOrResumeXidTransaction(final XidTransactionID xidTransactionID) throws Exception {
> final TransactionManager transactionManager = this.ejbRemoteTransactionsRepository.getTransactionManager();
> final Transaction alreadyCreatedTx = this.ejbRemoteTransactionsRepository.getImportedTransaction(xidTransactionID);
> if (alreadyCreatedTx != null) {
> // resume the already created tx
> transactionManager.resume(alreadyCreatedTx);
> } else {
> // begin a new tx and add it to the tx repository
> // TODO: Fix the tx timeout (which currently is passed as 300 seconds)
> final Transaction newSubOrdinateTx = this.ejbRemoteTransactionsRepository.importTransaction(xidTransactionID, 300);
> // associate this tx with the thread
> transactionManager.resume(newSubOrdinateTx);
> }
> }
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 6 months
[JBoss JIRA] (WFLY-4036) update EclipseLink/OpenJPA test case to filter out javax.persistence classes
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-4036?page=com.atlassian.jira.plugin.... ]
Scott Marlow updated WFLY-4036:
-------------------------------
Attachment: module.xml
module.xml
attached are example module.xml from static module (wildfly/modules/system/layers/base/*) folders.
> update EclipseLink/OpenJPA test case to filter out javax.persistence classes
> ----------------------------------------------------------------------------
>
> Key: WFLY-4036
> URL: https://issues.jboss.org/browse/WFLY-4036
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Reporter: Scott Marlow
> Assignee: Scott Marlow
> Fix For: 9.0.0.Beta1
>
> Attachments: module.xml, module.xml
>
>
> WildFly-core upgrade is improving the case when two deployments have bi-directional dependencies (a depends on b and b depends on a). Part of this is ensuring that application level classes are used over classes from dependencies.
> This introduces an issue for application that include api jars or other jars that previlously used to be overriden by dependency level classes.
> This jira is about fixing this for two of our unit tests that willl have this problem (an EclipseLink + OpenJPA test).
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 6 months
[JBoss JIRA] (WFLY-4036) update EclipseLink/OpenJPA test case to filter out javax.persistence classes
by Scott Marlow (JIRA)
Scott Marlow created WFLY-4036:
----------------------------------
Summary: update EclipseLink/OpenJPA test case to filter out javax.persistence classes
Key: WFLY-4036
URL: https://issues.jboss.org/browse/WFLY-4036
Project: WildFly
Issue Type: Feature Request
Components: JPA / Hibernate
Reporter: Scott Marlow
Assignee: Scott Marlow
Fix For: 9.0.0.Beta1
WildFly-core upgrade is improving the case when two deployments have bi-directional dependencies (a depends on b and b depends on a). Part of this is ensuring that application level classes are used over classes from dependencies.
This introduces an issue for application that include api jars or other jars that previlously used to be overriden by dependency level classes.
This jira is about fixing this for two of our unit tests that willl have this problem (an EclipseLink + OpenJPA test).
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 6 months
[JBoss JIRA] (WFCORE-207) write- and undefine-attribute operations are registered as runtime-only
by Emanuel Muckenhuber (JIRA)
Emanuel Muckenhuber created WFCORE-207:
------------------------------------------
Summary: write- and undefine-attribute operations are registered as runtime-only
Key: WFCORE-207
URL: https://issues.jboss.org/browse/WFCORE-207
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 1.0.0.Alpha10
Reporter: Emanuel Muckenhuber
Assignee: Emanuel Muckenhuber
Fix For: 1.0.0.Alpha11
The write-attribute and undefine-attribute operation are registered as runtime-only, which is not correct and was probably done unintentionally.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 6 months