2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2014

jboss-jira@lists.jboss.org

1 participants
1474 discussions

Start a nNew thread

[JBoss JIRA] (WFLY-3959) Upgrade HAL to 2.4.3.Final

by Harald Pehl (JIRA)

Harald Pehl created WFLY-3959: --------------------------------- Summary: Upgrade HAL to 2.4.3.Final Key: WFLY-3959 URL: https://issues.jboss.org/browse/WFLY-3959 Project: WildFly Issue Type: Component Upgrade Components: Web Console Reporter: Harald Pehl Assignee: Harald Pehl Fix For: 9.0.0.Beta1 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-154) Patching does not process subdirectories

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-154?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-154: ------------------------------------------------ baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1134735|https://bugzilla.redhat.com/show_bug.cgi?id=1134735] from ASSIGNED to POST > Patching does not process subdirectories > ---------------------------------------- > > Key: WFCORE-154 > URL: https://issues.jboss.org/browse/WFCORE-154 > Project: WildFly Core > Issue Type: Bug > Components: Patching > Affects Versions: 1.0.0.Alpha9 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 1.0.0.Alpha10 > > > If patched resource is in subdirectory of moduleRoot, it is not included as part of patch, even though it is present in patch zip. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-154) Patching does not process subdirectories

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-154?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-154: ------------------------------------------------ baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1136365|https://bugzilla.redhat.com/show_bug.cgi?id=1136365] from ASSIGNED to POST > Patching does not process subdirectories > ---------------------------------------- > > Key: WFCORE-154 > URL: https://issues.jboss.org/browse/WFCORE-154 > Project: WildFly Core > Issue Type: Bug > Components: Patching > Affects Versions: 1.0.0.Alpha9 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 1.0.0.Alpha10 > > > If patched resource is in subdirectory of moduleRoot, it is not included as part of patch, even though it is present in patch zip. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JBMETA-379) Missing param-name in a web.xml causes NullPointerException during deployment

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBMETA-379?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBMETA-379: ------------------------------------------------ Pavel Jelinek <pjelinek(a)redhat.com> changed the Status of [bug 1125421|https://bugzilla.redhat.com/show_bug.cgi?id=1125421] from ON_QA to VERIFIED > Missing param-name in a web.xml causes NullPointerException during deployment > ------------------------------------------------------------------------------ > > Key: JBMETA-379 > URL: https://issues.jboss.org/browse/JBMETA-379 > Project: JBoss Metadata > Issue Type: Bug > Components: web > Affects Versions: 8.0.0.Final > Reporter: Jay Kumar SenSharma > Assignee: Jean-Frederic Clere > Fix For: 8.0.1.Final > > Attachments: ContextParamNullDemo.war > > > - While deploying a WAR, If the web.xml file is used which has context <param-value> defined, However it has missing <param-name> then it causes NullPointerException as following: > {code} > 00:12:09,583 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "ContextParamNullDemo.war" (runtime-name: "ContextParamNullDemo.war") > 00:12:09,591 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."ContextParamNullDemo.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."ContextParamNullDemo.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "ContextParamNullDemo.war" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163) [wildfly-server-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > Caused by: java.lang.NullPointerException > at org.jboss.as.jsf.deployment.JSFVersionProcessor.deploy(JSFVersionProcessor.java:91) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156) [wildfly-server-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT] > ... 5 more > 00:12:09,598 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "ContextParamNullDemo.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"ContextParamNullDemo.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"ContextParamNullDemo.war\".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment \"ContextParamNullDemo.war\" > Caused by: java.lang.NullPointerException"}} > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3832) Upgrade JBMETA to 8.0.1.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3832?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3832: ----------------------------------------------- Pavel Jelinek <pjelinek(a)redhat.com> changed the Status of [bug 1139626|https://bugzilla.redhat.com/show_bug.cgi?id=1139626] from ON_QA to VERIFIED > Upgrade JBMETA to 8.0.1.Final > ----------------------------- > > Key: WFLY-3832 > URL: https://issues.jboss.org/browse/WFLY-3832 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Bartosz Baranowski > Assignee: Jason Greene > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JBJCA-1213) XA_RBEND should be included in check

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1213?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1213: ------------------------------------------------ Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1147881|https://bugzilla.redhat.com/show_bug.cgi?id=1147881] from ASSIGNED to POST > XA_RBEND should be included in check > ------------------------------------ > > Key: JBJCA-1213 > URL: https://issues.jboss.org/browse/JBJCA-1213 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: 1.0.27.Final, 1.1.7.Final, 1.2.0.Beta4 > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.0.28.Final, 1.1.8.Final, 1.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JBJCA-1215) Only use XidWrapper if needed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1215?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1215: ------------------------------------------------ Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1147881|https://bugzilla.redhat.com/show_bug.cgi?id=1147881] from ASSIGNED to POST > Only use XidWrapper if needed > ----------------------------- > > Key: JBJCA-1215 > URL: https://issues.jboss.org/browse/JBJCA-1215 > Project: IronJacamar > Issue Type: Task > Components: Core > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.0.28.Final, 1.1.8.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2551) AS7.2 - JMX Datasource pool & jdbc statistics dissapear if you enable validation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2551?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-2551: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1150821 > AS7.2 - JMX Datasource pool & jdbc statistics dissapear if you enable validation > -------------------------------------------------------------------------------- > > Key: WFLY-2551 > URL: https://issues.jboss.org/browse/WFLY-2551 > Project: WildFly > Issue Type: Bug > Components: JCA, JMX > Reporter: Will Tatam > Assignee: Brian Stansberry > Fix For: 9.0.0.Alpha1 > > > If you just create a basic datasource under AS 7.2 the you can view the current statistics about the pool under > jboss.as:subsystem=datasources,data-source=mySQL,statistics=pool > However, if you add the following then sometimes the statistics=pool and statistics=jdbc entries disspaear > <validation><check-valid-connection-sql>select 1</check-valid-connection-sql></validation> -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3958) WildFly datasource shows disabled even after enabling

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3958?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3958: ------------------------------- Assignee: Harald Pehl (was: Jason Greene) Component/s: Web Console > WildFly datasource shows disabled even after enabling > ----------------------------------------------------- > > Key: WFLY-3958 > URL: https://issues.jboss.org/browse/WFLY-3958 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 8.1.0.Final > Reporter: Carlton Zachary > Assignee: Harald Pehl > > After creating a datasource via the domain console, it still shows disabled after clicking enable. At that moment, the server log shows "Bound" for the datasource. When checking the domain.xml, it shows "enabled=false". This should be "enabled=true". To change this, I have to do ":write-attribute(name=enabled. value=true" in the CLI. > Please correct this bug. > Thank you. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3958) WildFly datasource shows disabled even after enabling

by Carlton Zachary (JIRA)

[ https://issues.jboss.org/browse/WFLY-3958?page=com.atlassian.jira.plugin.... ] Carlton Zachary updated WFLY-3958: ---------------------------------- Description: After creating a datasource via the domain console, it still shows disabled after clicking enable. At that moment, the server log shows "Bound" for the datasource. When checking the domain.xml, it shows "enabled=false". This should be "enabled=true". To change this, I have to do ":write-attribute(name=enabled. value=true" in the CLI. Please correct this bug. Thank you. > WildFly datasource shows disabled even after enabling > ----------------------------------------------------- > > Key: WFLY-3958 > URL: https://issues.jboss.org/browse/WFLY-3958 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.1.0.Final > Reporter: Carlton Zachary > Assignee: Jason Greene > > After creating a datasource via the domain console, it still shows disabled after clicking enable. At that moment, the server log shows "Bound" for the datasource. When checking the domain.xml, it shows "enabled=false". This should be "enabled=true". To change this, I have to do ":write-attribute(name=enabled. value=true" in the CLI. > Please correct this bug. > Thank you. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

Jump to page: