October 2014 - jboss-jira - Jboss List Archives

[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: ------------------------------------------------ Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1147715|https://bugzilla.redhat.com/show_bug.cgi?id=1147715] from MODIFIED to ON_QA > 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)

11 years, 9 months

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: ------------------------------------------------ Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1125421|https://bugzilla.redhat.com/show_bug.cgi?id=1125421] from MODIFIED to ON_QA > 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)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1212) Pool could keep connections open after shutdown

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1212?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1212: ------------------------------------------------ Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1147412|https://bugzilla.redhat.com/show_bug.cgi?id=1147412] from MODIFIED to ON_QA > Pool could keep connections open after shutdown > ----------------------------------------------- > > Key: JBJCA-1212 > URL: https://issues.jboss.org/browse/JBJCA-1212 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.27.Final, 1.1.7.Final, 1.2.0.Beta4 > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 1.0.28.Final, 1.1.8.Final, 1.2.0.CR1 > > > Let MCP check pool status before scheduling prefill -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-134) Make sure CLIWrapper doesn't use default encoding

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-134?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-134: ------------------------------------------------ Paul Gier <pgier(a)redhat.com> changed the Status of [bug 980923|https://bugzilla.redhat.com/show_bug.cgi?id=980923] from MODIFIED to ON_QA > Make sure CLIWrapper doesn't use default encoding > ------------------------------------------------- > > Key: WFCORE-134 > URL: https://issues.jboss.org/browse/WFCORE-134 > Project: WildFly Core > Issue Type: Bug > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Minor > Fix For: 1.0.0.Alpha9 > > > CLIWrapper is using the default encoding which might lead to issue with non US locales. > Also take advantage of this fix to remove some hard coded strings from tests. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1332) Integrate the compressed message support that was introduced in EJB client library

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1332?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1332: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1149020|https://bugzilla.redhat.com/show_bug.cgi?id=1149020] from MODIFIED to ON_QA > Integrate the compressed message support that was introduced in EJB client library > ---------------------------------------------------------------------------------- > > Key: WFLY-1332 > URL: https://issues.jboss.org/browse/WFLY-1332 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: jaikiran pai > Assignee: jaikiran pai > Fix For: 8.0.0.Alpha2 > > > https://issues.jboss.org/browse/EJBCLIENT-76 introduced a feature where the message stream that contains the EJB protocol message can be compressed. This involves a new message header which the server needs to support for the compression to be functional. This JIRA tracks the server side additions to support this feature. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-138) Upgrade log4j-jboss-logmanager from 1.1.0.Final to 1.1.1.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-138?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-138: ------------------------------------------------ Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1148632|https://bugzilla.redhat.com/show_bug.cgi?id=1148632] from MODIFIED to ON_QA > Upgrade log4j-jboss-logmanager from 1.1.0.Final to 1.1.1.Final > -------------------------------------------------------------- > > Key: WFCORE-138 > URL: https://issues.jboss.org/browse/WFCORE-138 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 1.0.0.Alpha9 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

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: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1139626|https://bugzilla.redhat.com/show_bug.cgi?id=1139626] from MODIFIED to ON_QA > 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)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-628) DecisionTable incorrectly parsed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-628?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated DROOLS-628: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1150308 > DecisionTable incorrectly parsed > --------------------------------- > > Key: DROOLS-628 > URL: https://issues.jboss.org/browse/DROOLS-628 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.2.0.CR1 > > > 5.2.0.CR1 creates incorrect drl from decision table. With 5.1.0.M1 the drl for the same decision table is correct. > Wrong DRL from 5.2.0.CR1: > rule "ProcessState" > salience 65522 > ruleflow-group "CompleteSubOrder" > activation-group "ProcessState" > when > $m:ModifiedMarker(processState==null, state ==null) > $s:SubOrder > then > $m.setIsModified(true); > $s.setProcessState(ProcessState.CREATED); > end > Correct DRL with 5.1.0.M1: > rule "ProcessState" > salience 65522 > ruleflow-group "CompleteSubOrder" > activation-group "ProcessState" > when > $m:ModifiedMarker() > $s:SubOrder(processState==null, state ==null) > then > $m.setIsModified(true); > $s.setProcessState(ProcessState.CREATED); > end > The difference is that the constraints are put to $m instead of putting them to $s. > The behaviour in 5.2.0.CR1 is the same for all decision tables in my project and prevents me from upgrading to newer drools versions. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3889) JMX monitoring is extremely memory inefficient

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3889?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3889: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1150304 > JMX monitoring is extremely memory inefficient > ---------------------------------------------- > > Key: WFLY-3889 > URL: https://issues.jboss.org/browse/WFLY-3889 > Project: WildFly > Issue Type: Bug > Components: Domain Management, JMX > Affects Versions: JBoss AS7 7.1.1.Final, 9.0.0.Alpha1 > Reporter: Koen Janssens > Assignee: Brian Stansberry > > When reading any JMX attribute(s), I have noticed a noticeable impact on the performance of our system. After attaching a profiler, I see that getting a single attribute of a JMX bean (either using remoting or using jconsole) is generating thousands of objects, that have to cleaned up by the GC. For instance, 6000 instances of the ModelNode class are created. > A clone is made of the complete management model before executing any JMX operation. This happens in the OperationContextImpl.readResourceFromRoot class. > More background on associated forum thread -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3894) Can't login JAAS secured management interfaces with --admin-only

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3894?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3894: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1146240|https://bugzilla.redhat.com/show_bug.cgi?id=1146240] from NEW to CLOSED > Can't login JAAS secured management interfaces with --admin-only > ---------------------------------------------------------------- > > Key: WFLY-3894 > URL: https://issues.jboss.org/browse/WFLY-3894 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 9.0.0.Alpha1 > Reporter: Chris Dolphy > Assignee: Darran Lofthouse > Attachments: standalone.xml > > > After configuring JAAS security for management realm, when I start JBoss with `bin/standalone.sh --admin-only', I can't login to the management web console. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 9 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