March 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4469) Remove mod_cluster subsystem transformers for version < 1.4.0

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4469?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-4469: --------------------------------- Description: Both of these 1.2.0 and 1.3.0 can go now, including tests. Old parsers stay in. (was: Both of these 1.2.0 and 1.3.0 can go now, including tests.) > Remove mod_cluster subsystem transformers for version < 1.4.0 > ------------------------------------------------------------- > > Key: WFLY-4469 > URL: https://issues.jboss.org/browse/WFLY-4469 > Project: WildFly > Issue Type: Sub-task > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Both of these 1.2.0 and 1.3.0 can go now, including tests. Old parsers stay in. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-751) Missing nullchecks in LeftTupleSetsImpl

by Mark Proctor (JIRA)

[ https://issues.jboss.org/browse/DROOLS-751?page=com.atlassian.jira.plugin... ] Mark Proctor commented on DROOLS-751: ------------------------------------- the issue is the list element is being iterated in one thread and added back into the set in another thread. We'll need to add a copy process in there :( > Missing nullchecks in LeftTupleSetsImpl > --------------------------------------- > > Key: DROOLS-751 > URL: https://issues.jboss.org/browse/DROOLS-751 > Project: Drools > Issue Type: Bug > Reporter: Tibor Zimányi > Assignee: Mark Proctor > > In class LeftTupleSetsImpl there are missing nullchecks in some methods that contains handling LeftTuple instances. I.e. in method removeInsert there is LeftTuple variable previous that is not nullchecked. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-29) An ear file with modules in subfolders can not deploy under AS 7.0

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-29?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-29: --------------------------------------------- Brad Maxwell <bmaxwell(a)redhat.com> changed the Status of [bug 1206635|https://bugzilla.redhat.com/show_bug.cgi?id=1206635] from NEW to POST > An ear file with modules in subfolders can not deploy under AS 7.0 > ------------------------------------------------------------------ > > Key: WFLY-29 > URL: https://issues.jboss.org/browse/WFLY-29 > Project: WildFly > Issue Type: Bug > Components: EE > Reporter: Adrian Zuo > Assignee: Stuart Douglas > Fix For: 8.1.0.CR2, 8.1.0.Final > > Attachments: migrate.ear, migrate.ear > > > I have an ear file names migrate.ear which contains one ejb jar (ejb.jar) and one war file (war.war), if I put the ejb jar to a ejb folder and war file to war folder, the ear can not be depoyed. > If I move the ejb jar and war file out, it can be deployed. > Below structuer can be deployed: > ejb.jar > lib/ > lib/util-1.0-SNAPSHOT.jar > lib/version.jar > META-INF/ > META-INF/application.xml > META-INF/MANIFEST.MF > war.war > > Below structure can not be deployed: > ejb/ > ejb/ejb.jar > lib/ > lib/util-1.0-SNAPSHOT.jar > lib/version.jar > META-INF/ > META-INF/application.xml > META-INF/MANIFEST.MF > war/ > war/war.war > Below is the error: > http://community.jboss.org/message/630869#630869 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-29) An ear file with modules in subfolders can not deploy under AS 7.0

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-29?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration updated WFLY-29: ---------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1206635 > An ear file with modules in subfolders can not deploy under AS 7.0 > ------------------------------------------------------------------ > > Key: WFLY-29 > URL: https://issues.jboss.org/browse/WFLY-29 > Project: WildFly > Issue Type: Bug > Components: EE > Reporter: Adrian Zuo > Assignee: Stuart Douglas > Fix For: 8.1.0.CR2, 8.1.0.Final > > Attachments: migrate.ear, migrate.ear > > > I have an ear file names migrate.ear which contains one ejb jar (ejb.jar) and one war file (war.war), if I put the ejb jar to a ejb folder and war file to war folder, the ear can not be depoyed. > If I move the ejb jar and war file out, it can be deployed. > Below structuer can be deployed: > ejb.jar > lib/ > lib/util-1.0-SNAPSHOT.jar > lib/version.jar > META-INF/ > META-INF/application.xml > META-INF/MANIFEST.MF > war.war > > Below structure can not be deployed: > ejb/ > ejb/ejb.jar > lib/ > lib/util-1.0-SNAPSHOT.jar > lib/version.jar > META-INF/ > META-INF/application.xml > META-INF/MANIFEST.MF > war/ > war/war.war > Below is the error: > http://community.jboss.org/message/630869#630869 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-601) Boot sometimes fails on restart when deployments are present in the deployments directory and the deployment scanner is in use

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-601?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet commented on WFCORE-601: ------------------------------------------ Ok found that war is coming from https://github.com/TechEmpower/FrameworkBenchmarks > Boot sometimes fails on restart when deployments are present in the deployments directory and the deployment scanner is in use > ------------------------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-601 > URL: https://issues.jboss.org/browse/WFCORE-601 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > I observed this today, looks to be some kind of race in the deployment scanner on boot > {code} > 21:52:08,618 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.1.Final > 21:52:10,370 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.4.Final > 21:52:10,440 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: WildFly Full 9.0.0.Alpha2-SNAPSHOT (WildFly Core 1.0.0.Alpha19) starting > 21:52:11,390 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 20) WFLYCTL0028: Attribute enabled is deprecated, and it might be removed in future version! > 21:52:11,409 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment mysql-ds.xml > 21:52:11,413 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment wildfly-ee7.war > 21:52:11,488 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 3) WFLYDR0001: Content added at location /Users/stuart/workspace/wildfly/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/data/content/48/032d14f289775249a004205c059588ab0f44d4/content > 21:52:11,504 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 3) WFLYDR0001: Content added at location /Users/stuart/workspace/wildfly/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/data/content/c6/7babde4791697ddc6509fbd43ba1ec25952d47/content > 21:52:11,506 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 3) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "wildfly-ee7.war")]) - failure description: "WFLYCTL0212: Duplicate resource [(\"deployment\" => \"wildfly-ee7.war\")]" > 21:52:11,509 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) "WFLYCTL0193: Failed executing subsystem deployment-scanner boot operations" > 21:52:11,512 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("parallel-subsystem-boot") failed - address: ([]) - failure description: "\"WFLYCTL0193: Failed executing subsystem deployment-scanner boot operations\"" > 21:52:11,514 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. > 21:52:11,514 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested. > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3928) JBossSecuritySubjectFactory throws NullPointerException during JBoss shutdown

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-3928?page=com.atlassian.jira.plugin.... ] Ivo Studensky commented on WFLY-3928: ------------------------------------- Has this issue been resolved by WFLY-3972? > JBossSecuritySubjectFactory throws NullPointerException during JBoss shutdown > ----------------------------------------------------------------------------- > > Key: WFLY-3928 > URL: https://issues.jboss.org/browse/WFLY-3928 > Project: WildFly > Issue Type: Bug > Components: Security > Environment: JBoss EAP 6.3 > Reporter: Tom Ross > Assignee: Darran Lofthouse > > During JBoss shutdown we can see the following exception: > {noformat} > 2014-09-22 16:23:51,193 ERROR [org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl] (Periodic Recovery) IJ000903: Error creating Subject for crash recovery: java:/xa-resource-adapter/XAQueueConnectionFactory (null): java.lang.NullPointerException > at org.jboss.security.plugins.JBossSecuritySubjectFactory.createSubject(JBossSecuritySubjectFactory.java:83) > at org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl$1.run(XAResourceRecoveryImpl.java:300) > at org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl$1.run(XAResourceRecoveryImpl.java:261) > at java.security.AccessController.doPrivileged(Native Method) > at org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl.getSubject(XAResourceRecoveryImpl.java:260) > at org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl.getXAResources(XAResourceRecoveryImpl.java:165) > at com.arjuna.ats.internal.jbossatx.jta.XAResourceRecoveryHelperWrapper.getXAResources(XAResourceRecoveryHelperWrapper.java:51) > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.resourceInitiatedRecoveryForRecoveryHelpers(XARecoveryModule.java:516) > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:182) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:743) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4469) Remove mod_cluster subsystem transformers for version < 1.4.0

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-4469: ------------------------------------ Summary: Remove mod_cluster subsystem transformers for version < 1.4.0 Key: WFLY-4469 URL: https://issues.jboss.org/browse/WFLY-4469 Project: WildFly Issue Type: Sub-task Components: Clustering Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 9.0.0.CR1 Both of these 1.2.0 and 1.3.0 can go now, including tests. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4469) Remove mod_cluster subsystem transformers for version < 1.4.0

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4469?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-4469: --------------------------------- Fix Version/s: (was: 9.0.0.CR1) > Remove mod_cluster subsystem transformers for version < 1.4.0 > ------------------------------------------------------------- > > Key: WFLY-4469 > URL: https://issues.jboss.org/browse/WFLY-4469 > Project: WildFly > Issue Type: Sub-task > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Both of these 1.2.0 and 1.3.0 can go now, including tests. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4275) Implicit EE component attached to a root implicit bean archive recognized as implicit bean

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-4275?page=com.atlassian.jira.plugin.... ] Martin Kouba updated WFLY-4275: ------------------------------- Fix Version/s: 9.0.0.CR1 > Implicit EE component attached to a root implicit bean archive recognized as implicit bean > ------------------------------------------------------------------------------------------ > > Key: WFLY-4275 > URL: https://issues.jboss.org/browse/WFLY-4275 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 9.0.0.Alpha1 > Reporter: Martin Kouba > Assignee: Martin Kouba > Fix For: 9.0.0.CR1 > > > This is no longer necessary (see also WELD-1612). Furhtermore, it's producing confusing results. For example, an {{ProcessBeanAttributes}} event is fired for {{com.sun.faces.config.ConfigureListener}}, {{org.jboss.weld.servlet.WeldInitialListener}} and other implicitly added EE components for a WAR deployment with {{bean-discovery-mode="annotated"}}. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4275) Implicit EE component attached to a root implicit bean archive recognized as implicit bean

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-4275?page=com.atlassian.jira.plugin.... ] Martin Kouba reopened WFLY-4275: -------------------------------- The intention of https://github.com/wildfly/wildfly/pull/7120 was to ignore implicit EE components (i.e. components added by extensions) but the fix also excludes EE components from WEB-INF/classes. This probably causes 2 failures in the JAX-RS TCK. > Implicit EE component attached to a root implicit bean archive recognized as implicit bean > ------------------------------------------------------------------------------------------ > > Key: WFLY-4275 > URL: https://issues.jboss.org/browse/WFLY-4275 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 9.0.0.Alpha1 > Reporter: Martin Kouba > Assignee: Martin Kouba > > This is no longer necessary (see also WELD-1612). Furhtermore, it's producing confusing results. For example, an {{ProcessBeanAttributes}} event is fired for {{com.sun.faces.config.ConfigureListener}}, {{org.jboss.weld.servlet.WeldInitialListener}} and other implicitly added EE components for a WAR deployment with {{bean-discovery-mode="annotated"}}. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

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 March 2015