October 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4035) Upgrade HornetQ to 2.4.5

by Clebert Suconic (JIRA)

[ https://issues.jboss.org/browse/WFLY-4035?page=com.atlassian.jira.plugin.... ] Clebert Suconic commented on WFLY-4035: --------------------------------------- I've sent it to master .. do I need to send it any other branches? > Upgrade HornetQ to 2.4.5 > ------------------------ > > Key: WFLY-4035 > URL: https://issues.jboss.org/browse/WFLY-4035 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Reporter: Clebert Suconic > Assignee: Clebert Suconic > Fix For: 8.2.0.CR1, 9.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[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)

11 years, 6 months

1
0
0 / 0

[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)

11 years, 6 months

1
0
0 / 0

[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)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4030) wildfly-javaee7-webapp-blank-archetype using old namespaces for beans.xml and faces-config.xml

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/WFLY-4030?page=com.atlassian.jira.plugin.... ] Rafael Benevides edited comment on WFLY-4030 at 10/30/14 11:27 AM: ------------------------------------------------------------------- [~sebastian.laskawiec] After WFLY-4031 is fixed, Just do a mvn clean install for archetypes and it will synch the archetypes with fixed quickstarts. This is possible because I used QSTools at Archetypes: https://github.com/wildfly/wildfly-archetypes/blob/master/wildfly-javaee7... Thanks was (Author: rafabene): [~sebastian.laskawiec] After WFLY-4031 is fixed, Just do a mvn clean install for archetypes and it will synch the archetypes with fixed quickstarts. This is possible because I used QSTools at Archetypes to make this possible: https://github.com/wildfly/wildfly-archetypes/blob/master/wildfly-javaee7... Thanks > wildfly-javaee7-webapp-blank-archetype using old namespaces for beans.xml and faces-config.xml > ---------------------------------------------------------------------------------------------- > > Key: WFLY-4030 > URL: https://issues.jboss.org/browse/WFLY-4030 > Project: WildFly > Issue Type: Bug > Reporter: Arun Gupta > Assignee: Sebastian Łaskawiec > Priority: Minor > Labels: archetypes, maven, wildfly > > mvn archetype:generate -DgroupId=test -DartifactId=test -DarchetypeGroupId=org.wildfly.archetype -DarchetypeArtifactId=wildfly-javaee7-webapp-blank-archetype -DarchetypeVersion=8.1.0.Final > The app has the following files: > ./src/main/webapp/WEB-INF/beans.xml > ./src/main/webapp/WEB-INF/faces-config.xml > beans.xml and faces-config.xml are using java.sun.com-style namespaces instead of xmlns.jcp.org-style namespaces. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[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)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4035) Upgrade HornetQ to 2.4.5

by Clebert Suconic (JIRA)

Clebert Suconic created WFLY-4035: ------------------------------------- Summary: Upgrade HornetQ to 2.4.5 Key: WFLY-4035 URL: https://issues.jboss.org/browse/WFLY-4035 Project: WildFly Issue Type: Feature Request Components: JMS Reporter: Clebert Suconic Assignee: Clebert Suconic Fix For: 8.2.0.CR1, 9.0.0.Beta1 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4030) wildfly-javaee7-webapp-blank-archetype using old namespaces for beans.xml and faces-config.xml

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/WFLY-4030?page=com.atlassian.jira.plugin.... ] Rafael Benevides commented on WFLY-4030: ---------------------------------------- [~sebastian.laskawiec] After WFLY-4031 is fixed, Just do a mvn clean install for archetypes and it will synch the archetypes with fixed quickstarts. This is possible because I used QSTools at Archetypes to make this possible: https://github.com/wildfly/wildfly-archetypes/blob/master/wildfly-javaee7... Thanks > wildfly-javaee7-webapp-blank-archetype using old namespaces for beans.xml and faces-config.xml > ---------------------------------------------------------------------------------------------- > > Key: WFLY-4030 > URL: https://issues.jboss.org/browse/WFLY-4030 > Project: WildFly > Issue Type: Bug > Reporter: Arun Gupta > Assignee: Sebastian Łaskawiec > Priority: Minor > Labels: archetypes, maven, wildfly > > mvn archetype:generate -DgroupId=test -DartifactId=test -DarchetypeGroupId=org.wildfly.archetype -DarchetypeArtifactId=wildfly-javaee7-webapp-blank-archetype -DarchetypeVersion=8.1.0.Final > The app has the following files: > ./src/main/webapp/WEB-INF/beans.xml > ./src/main/webapp/WEB-INF/faces-config.xml > beans.xml and faces-config.xml are using java.sun.com-style namespaces instead of xmlns.jcp.org-style namespaces. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3548) JTA synchronization for a distributed transaction called with incorrect TCCL

by Tomasz Adamski (JIRA)

[ https://issues.jboss.org/browse/WFLY-3548?page=com.atlassian.jira.plugin.... ] Tomasz Adamski reassigned WFLY-3548: ------------------------------------ Assignee: Tomasz Adamski (was: Amos Feng) > JTA synchronization for a distributed transaction called with incorrect TCCL > ---------------------------------------------------------------------------- > > Key: WFLY-3548 > URL: https://issues.jboss.org/browse/WFLY-3548 > Project: WildFly > Issue Type: Bug > Components: Transactions > Affects Versions: 8.1.0.Final > Reporter: Martin Kouba > Assignee: Tomasz Adamski > > It seems the RequestProcessor which is processing JTA synchronizations > does not have the right TCCL set. > As a result, during synchronization invocation: > * {{NameNotFoundException}} is thrown for a JNDI lookup of "java:comp/UserTransaction" > * if we try to acccess {{org.jboss.weld.Container}} by means of {{org.jboss.as.weld.services.ModuleGroupSingletonProvider.TCCLSingleton}}, we get ISE: "Singleton not set....This means that you are trying to access a weld deployment with a Thread Context ClassLoader that is not associated with the deployment." -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBASMP-73) Duplicate deployment error if both 'reload' and 'deploy' goals are bound to the same maven phase

by Martin Basovnik (JIRA)

[ https://issues.jboss.org/browse/JBASMP-73?page=com.atlassian.jira.plugin.... ] Martin Basovnik updated JBASMP-73: ---------------------------------- Summary: Duplicate deployment error if both 'reload' and 'deploy' goals are bound to the same maven phase (was: Duplicate deployment error if both reload and deploy goals are bind to the same maven phase) > Duplicate deployment error if both 'reload' and 'deploy' goals are bound to the same maven phase > ------------------------------------------------------------------------------------------------ > > Key: JBASMP-73 > URL: https://issues.jboss.org/browse/JBASMP-73 > Project: JBoss AS Maven Plugins > Issue Type: Bug > Components: deploy > Reporter: Martin Basovnik > Assignee: James Perkins > Attachments: jbasmp-deploy-reproducer.zip > > > If I try to deploy a deployment just after the server reloading it sometimes fails: > {code} > 10:20:32,921 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014612: Operation ("add") failed - address: ([("deployment" => "jbasmp-deploy-reproducer-0.0.1-SNAPSHOT.jar")]) - failure description: "JBAS014803: Duplicate resource [(\"deployment\" => \"jbasmp-deploy-reproducer-0.0.1-SNAPSHOT.jar\")]" > {code} > https://github.com/jbossas/jboss-as-maven-plugin/blob/7.6.Final/src/main/... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2014