December 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-591) revertReloadRequired() throws a NPE is reloadRequired has not been called

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-591?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-591: ------------------------------------------------ Romain Pelisse <rpelisse(a)redhat.com> changed the Status of [bug 1294591|https://bugzilla.redhat.com/show_bug.cgi?id=1294591] from NEW to ASSIGNED > revertReloadRequired() throws a NPE is reloadRequired has not been called > ------------------------------------------------------------------------- > > Key: WFCORE-591 > URL: https://issues.jboss.org/browse/WFCORE-591 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha19 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 1.0.0.Beta1 > > > If an operation step handler calls org.jboss.as.controller.OperationContext#revertReloadRequired() when org.jboss.as.controller.OperationContext#reloadRequired() has not been called, it throws a NPE: > {noformat} > java.lang.NullPointerException > at org.jboss.as.controller.ControlledProcessState.revertReloadRequired(ControlledProcessState.java:181) > at org.jboss.as.controller.AbstractOperationContext.revertReloadRequired(AbstractOperationContext.java:1037) > at org.jboss.as.controller.test.RevertReloadRequiredTestCase$TestResourceAddHandler.rollbackRuntime(RevertReloadRequiredTestCase.java:98) > at org.jboss.as.controller.AbstractAddStepHandler$1$1.handleRollback(AbstractAddStepHandler.java:133) > at org.jboss.as.controller.AbstractOperationContext$RollbackDelegatingResultHandler.handleResult(AbstractOperationContext.java:1419) > at org.jboss.as.controller.AbstractOperationContext$Step.invokeResultHandler(AbstractOperationContext.java:1385) > at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1367) > at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1323) > at org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:1283) > at org.jboss.as.controller.AbstractOperationContext$Step.access$300(AbstractOperationContext.java:1172) > at org.jboss.as.controller.AbstractOperationContext.finishStep(AbstractOperationContext.java:929) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:877) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:601) > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:354) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:330) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1182) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:362) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:205) > {noformat} > The NPE is caused by this.activeStep.restartStamp field which is set only when reloadRequired() (or restartRequired()) is called. > My OSH may call reloadRequired() or not depending on some runtime state and I could add some logic to make sure I call > I can fix my handle to check that I call context.revertReloadRequired() only I had previously called reloadRequired () first. > However, in order to make the OperationContext more robust, I think that the revertReloadRequired() method should instead be a no-op if there is no reload required. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5652) Datasource spy attribute has no effect

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/WFLY-5652?page=com.atlassian.jira.plugin.... ] Jesper Pedersen reassigned WFLY-5652: ------------------------------------- Assignee: Lin Gao (was: Jesper Pedersen) > Datasource spy attribute has no effect > -------------------------------------- > > Key: WFLY-5652 > URL: https://issues.jboss.org/browse/WFLY-5652 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 10.0.0.CR2 > Reporter: Rich DiCroce > Assignee: Lin Gao > > The spy attribute of a datasource does not appear to have any effect. The datasources XSD says to set spy to true and enable the org.jboss.jdbc log category, but I did that and got no debug info in my log. From a quick search of the WildFly and IronJacamar codebases, it looks like no meaningful code ever checks the value of the spy attribute. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5917) numberOfLogicalViews not working

by Gabriel Vieira (JIRA)

[ https://issues.jboss.org/browse/WFLY-5917?page=com.atlassian.jira.plugin.... ] Gabriel Vieira updated WFLY-5917: --------------------------------- Description: Theres a bug in wildfly 9 Final Even if a set on web.xml {code:java} <context-param> <param-name>com.sun.faces.numberOfLogicalViews</param-name> <param-value>3</param-value> </context-param> {code} It keep storing 25 views. I tried @Named (CDI) and @ManagedBean and the problem persisted. My workaround was use @ViewScoped from Omnifaces was: Theres a bug in wildfly 9 Final Even if a set on web.xml {code:java} <context-param> <param-name>com.sun.faces.numberOfLogicalViews</param-name> <param-value>3</param-value> </context-param> {code} it keep storing 25 views. I tried @Named (CDI) and @ManagedBean and the problem persisted. My workaround was use @ViewScoped from Omnifaces > numberOfLogicalViews not working > -------------------------------- > > Key: WFLY-5917 > URL: https://issues.jboss.org/browse/WFLY-5917 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, JSF > Affects Versions: 9.0.2.Final > Reporter: Gabriel Vieira > Assignee: Stuart Douglas > Labels: cdi, jsf22, wildfly > > Theres a bug in wildfly 9 Final > Even if a set on web.xml > {code:java} > <context-param> > <param-name>com.sun.faces.numberOfLogicalViews</param-name> > <param-value>3</param-value> > </context-param> > {code} > It keep storing 25 views. > I tried @Named (CDI) and @ManagedBean and the problem persisted. > My workaround was use @ViewScoped from Omnifaces -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5917) numberOfLogicalViews not working

by Gabriel Vieira (JIRA)

[ https://issues.jboss.org/browse/WFLY-5917?page=com.atlassian.jira.plugin.... ] Gabriel Vieira updated WFLY-5917: --------------------------------- Description: Theres a bug in wildfly 9 Final Even if a set on web.xml {code:java} <context-param> <param-name>com.sun.faces.numberOfLogicalViews</param-name> <param-value>3</param-value> </context-param> {code} it keep storing 25 views. I tried @Named (CDI) and @ManagedBean and the problem persisted. My workaround was use @ViewScoped from Omnifaces was: Theres a bug in wildfly 9 Final Even if a set on web.xml {code:java} <context-param> <param-name>com.sun.faces.numberOfLogicalViews</param-name> <param-value>3</param-value> </context-param> {code} it keeps storing 25 views. I tried @Named (CDI) and @ManagedBean and the problem persisted. My workaround was use @ViewScoped from Omnifaces > numberOfLogicalViews not working > -------------------------------- > > Key: WFLY-5917 > URL: https://issues.jboss.org/browse/WFLY-5917 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, JSF > Affects Versions: 9.0.2.Final > Reporter: Gabriel Vieira > Assignee: Stuart Douglas > Labels: cdi, jsf22, wildfly > > Theres a bug in wildfly 9 Final > Even if a set on web.xml > {code:java} > <context-param> > <param-name>com.sun.faces.numberOfLogicalViews</param-name> > <param-value>3</param-value> > </context-param> > {code} > it keep storing 25 views. > I tried @Named (CDI) and @ManagedBean and the problem persisted. > My workaround was use @ViewScoped from Omnifaces -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5917) numberOfLogicalViews not working

by Gabriel Vieira (JIRA)

[ https://issues.jboss.org/browse/WFLY-5917?page=com.atlassian.jira.plugin.... ] Gabriel Vieira updated WFLY-5917: --------------------------------- Steps to Reproduce: 1-Create a WEB project 2-Create a @ViewScoped and log @PostConstruct and @PreDestroy. 3-Set com.sun.faces.numberOfLogicalViews to 3 (or any other number) on web.xml. 4-Create a page that call the View created (Step 2). 5-You will notice that it will store view ultil max 25 (LRU map). was: 1-Create a WEB project 2-Create a @ViewScoped and log @PostConstruct and @PreDestroy. 3-Set com.sun.faces.numberOfLogicalViews to 3 (or any other number). 4-Create a page that call the View created (Step 2). 5-You will notice that it will store view ultil max 25 (LRU map). > numberOfLogicalViews not working > -------------------------------- > > Key: WFLY-5917 > URL: https://issues.jboss.org/browse/WFLY-5917 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, JSF > Affects Versions: 9.0.2.Final > Reporter: Gabriel Vieira > Assignee: Stuart Douglas > Labels: cdi, jsf22, wildfly > > Theres a bug in wildfly 9 Final > Even if a set on web.xml > {code:java} > <context-param> > <param-name>com.sun.faces.numberOfLogicalViews</param-name> > <param-value>3</param-value> > </context-param> > {code} > it keeps storing 25 views. > I tried @Named (CDI) and @ManagedBean and the problem persisted. > My workaround was use @ViewScoped from Omnifaces -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5917) numberOfLogicalViews not working

by Gabriel Vieira (JIRA)

[ https://issues.jboss.org/browse/WFLY-5917?page=com.atlassian.jira.plugin.... ] Gabriel Vieira updated WFLY-5917: --------------------------------- Steps to Reproduce: 1-Create a WEB project 2-Create a @ViewScoped and log @PostConstruct and @PreDestroy. 3-Set com.sun.faces.numberOfLogicalViews to 3 (or any other number). 4-Create a page that call the View created (Step 2). 5-You will notice that it will store view ultil max 25 (LRU map). was: 1-Create a WEB project 2-Create a @ViewScoped and log @PostConstruct and @PreDestroy to log it. 3-Set com.sun.faces.numberOfLogicalViews to 3 (or any other number). 4-Create a page that call the View created (Step 2). 5-You will notice that it will store view ultil max 25 (LRU map). > numberOfLogicalViews not working > -------------------------------- > > Key: WFLY-5917 > URL: https://issues.jboss.org/browse/WFLY-5917 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, JSF > Affects Versions: 9.0.2.Final > Reporter: Gabriel Vieira > Assignee: Stuart Douglas > Labels: cdi, jsf22, wildfly > > Theres a bug in wildfly 9 Final > Even if a set on web.xml > {code:java} > <context-param> > <param-name>com.sun.faces.numberOfLogicalViews</param-name> > <param-value>3</param-value> > </context-param> > {code} > it keeps storing 25 views. > I tried @Named (CDI) and @ManagedBean and the problem persisted. > My workaround was use @ViewScoped from Omnifaces -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5917) numberOfLogicalViews not working

by Gabriel Vieira (JIRA)

Gabriel Vieira created WFLY-5917: ------------------------------------ Summary: numberOfLogicalViews not working Key: WFLY-5917 URL: https://issues.jboss.org/browse/WFLY-5917 Project: WildFly Issue Type: Bug Components: CDI / Weld, JSF Affects Versions: 9.0.2.Final Reporter: Gabriel Vieira Assignee: Stuart Douglas Theres a bug in wildfly 9 Final Even if a set on web.xml {code:java} <context-param> <param-name>com.sun.faces.numberOfLogicalViews</param-name> <param-value>3</param-value> </context-param> {code} it keeps storing 25 views. I tried @Named (CDI) and @ManagedBean and the problem persisted. My workaround was use @ViewScoped from Omnifaces -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5915) Upgrade Jackson from 2.5.4 to 2.6.3 as used in RESTEasy 3.0.14.Final

by Frank Langelage (JIRA)

[ https://issues.jboss.org/browse/WFLY-5915?page=com.atlassian.jira.plugin.... ] Frank Langelage commented on WFLY-5915: --------------------------------------- Duplicate of https://issues.jboss.org/browse/WFLY-5911. > Upgrade Jackson from 2.5.4 to 2.6.3 as used in RESTEasy 3.0.14.Final > -------------------------------------------------------------------- > > Key: WFLY-5915 > URL: https://issues.jboss.org/browse/WFLY-5915 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 10.0.0.CR5 > Reporter: Juergen Zimmermann > Assignee: Stuart Douglas > > RESTEasy 3.0.14.Final is upgraded to Jackson 2.6.3. However, WildFly is still providing the old Jackson release 2.5.4. > See https://github.com/resteasy/Resteasy/blob/master/jaxrs/pom.xml#L59 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5916) jackson-datatype-jsr310 and jackson-datatype-jdk8 are missing

by Juergen Zimmermann (JIRA)

Juergen Zimmermann created WFLY-5916: ---------------------------------------- Summary: jackson-datatype-jsr310 and jackson-datatype-jdk8 are missing Key: WFLY-5916 URL: https://issues.jboss.org/browse/WFLY-5916 Project: WildFly Issue Type: Bug Components: REST Affects Versions: 10.0.0.CR5 Reporter: Juergen Zimmermann Assignee: Stuart Douglas WildFly doesn't provide jackson-datatype-jsr310 and jackson-datatype-jdk8 for RESTEasy. jackson-datatype-jsr310 supports the new JDK 8 time API, and jackson-datatype-jdk8 supports the new JDK 8 Optional type. The GAVs are: com.fasterxml.jackson.datatype:jackson-datatype-jsr310:2.6.3 com.fasterxml.jackson.datatype:jackson-datatype-jdk8:2.6.3 The latest Jackson GA version is 2.6.4. Please see also https://issues.jboss.org/browse/WFLY-5915. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5915) Upgrade Jackson from 2.5.4 to 2.6.3 as used in RESTEasy 3.0.14.Final

by Juergen Zimmermann (JIRA)

Juergen Zimmermann created WFLY-5915: ---------------------------------------- Summary: Upgrade Jackson from 2.5.4 to 2.6.3 as used in RESTEasy 3.0.14.Final Key: WFLY-5915 URL: https://issues.jboss.org/browse/WFLY-5915 Project: WildFly Issue Type: Bug Components: REST Affects Versions: 10.0.0.CR5 Reporter: Juergen Zimmermann Assignee: Stuart Douglas RESTEasy 3.0.14.Final is upgraded to Jackson 2.6.3. However, WildFly is still providing the old Jackson release 2.5.4. See https://github.com/resteasy/Resteasy/blob/master/jaxrs/pom.xml#L59 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2015