February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3541) NullPointerException when evicting all entities

by Zbyněk Roubalík (JIRA)

Zbyněk Roubalík created AS7-3541: ------------------------------------ Summary: NullPointerException when evicting all entities Key: AS7-3541 URL: https://issues.jboss.org/browse/AS7-3541 Project: Application Server 7 Issue Type: Bug Components: Clustering, JPA / Hibernate Affects Versions: 7.1.0.CR1b Reporter: Zbyněk Roubalík Assignee: Scott Marlow Fix For: 7.1.1.Final Get NullPointerException when evicting entity cache (emf.getCache().evictAll()). Hibernate JIRA for this issue: https://hibernate.onjira.com/browse/HHH-7016 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

5
12
0 / 0

[JBoss JIRA] (AS7-3027) NPE when calling operations on inactive modcluster subsystem

by Jesse Jaggars (Created) (JIRA)

NPE when calling operations on inactive modcluster subsystem ------------------------------------------------------------ Key: AS7-3027 URL: https://issues.jboss.org/browse/AS7-3027 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.0.Beta1b Reporter: Jesse Jaggars Assignee: Paul Ferraro Despite not being able to 'see' the modcluster subsystem as illustrated below: [domain@localhost:9999 subsystem] pwd /host=master/server=server-one/subsystem [domain@localhost:9999 subsystem] ls cmp datasources ee ejb3 infinispan jacorb jaxrs jca jdr jmx jpa logging mail messaging naming osgi remoting resource-adapters sar security threads transactions web webservices weld I can still call methods on that subsystem. However when I do this, there is a NullPointerException thrown by the operation code. [domain@localhost:9999 /] /host=master/server=server-one/subsystem=modcluster/:read-proxies-configuration { "outcome" => "failed", "result" => undefined, "failure-description" => "JBAS014749: Operation handler failed: null", "rolled-back" => true } And the log/stacktrace is: [Server:server-one] 11:39:45,518 ERROR [org.jboss.as.controller.management-operation] (pool-1-thread-3) JBAS014612: Operation ("read-proxies-configuration") failed - address: ([("subsystem" => "modcluster")]): java.lang.NullPointerException [Server:server-one] at org.jboss.as.modcluster.ModClusterGetProxyConfiguration$1.execute(ModClusterGetProxyConfiguration.java:56) [jboss-as-modcluster-7.1.0.CR1-SNAPSHOT.jar:] [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:359) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:254) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:190) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] [Server:server-one] at org.jboss.as.modcluster.ModClusterGetProxyConfiguration.execute(ModClusterGetProxyConfiguration.java:75) [jboss-as-modcluster-7.1.0.CR1-SNAPSHOT.jar:] [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:359) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:254) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:190) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] [Server:server-one] at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:432) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:359) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:254) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] [Server:server-one] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:190) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] [Server:server-one] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:119) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] [Server:server-one] at org.jboss.as.controller.remote.TransactionalModelControllerOperationHandler$ExecuteRequestHandler.doExecute(TransactionalModelControllerOperationHandler.java:142) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] [Server:server-one] at org.jboss.as.controller.remote.TransactionalModelControllerOperationHandler$ExecuteRequestHandler$1.execute(TransactionalModelControllerOperationHandler.java:128) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] [Server:server-one] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$3$1.doExecute(AbstractMessageHandler.java:268) [Server:server-one] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:424) [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29] [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29] [Server:server-one] at java.lang.Thread.run(Thread.java:680) [:1.6.0_29] [Server:server-one] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

5
5
0 / 0

[JBoss JIRA] (AS7-3199) RESTEasy: Can't deploy WebApp if more than one subclass of javax.ws.rs.Application is present

by Bill Burke (JIRA)

[ https://issues.jboss.org/browse/AS7-3199?page=com.atlassian.jira.plugin.s... ] Bill Burke commented on AS7-3199: --------------------------------- The thing is, i'm not fixing it for 2.3.x. period. It breaks backward compatibility with 2.3.1 and earlier versions of resteasy. BTW, you are the only person who has ever complained about this. It has never been mentioned by users. > RESTEasy: Can't deploy WebApp if more than one subclass of javax.ws.rs.Application is present > --------------------------------------------------------------------------------------------- > > Key: AS7-3199 > URL: https://issues.jboss.org/browse/AS7-3199 > Project: Application Server 7 > Issue Type: Bug > Components: REST > Affects Versions: 7.1.0.CR1b > Reporter: Pavel Janousek > Assignee: Stuart Douglas > Priority: Critical > Labels: eap6_prd_req > Fix For: 7.1.1.Final > > Attachments: ExampleJAXRS.war > > > If I packed WAR WebApp with more that one subclass of javax.ws.rs.Application, deployment fails with "JBAS011232: Only one JAX-RS Application Class allowed." > This is not correct because it is against JAX-RS 1.1. specs where invalid situation (in section 2.3.2) is only when "It is a n error for > more than one application to be deployed +at the same effective servlet mapping+". > If you have any objections, please compare to reference JEE6 and JAX-RS implementation represented by the GlassFish Prelude 3.1.1 application server with already +fully JEE6 platform support+. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-3900) Cannot add a new PID in the

by Ed Roberts (JIRA)

Ed Roberts created AS7-3900: ------------------------------- Summary: Cannot add a new PID in the Key: AS7-3900 URL: https://issues.jboss.org/browse/AS7-3900 Project: Application Server 7 Issue Type: Bug Reporter: Ed Roberts -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
2
0 / 0

[JBoss JIRA] (AS7-3199) RESTEasy: Can't deploy WebApp if more than one subclass of javax.ws.rs.Application is present

by Pavel Janousek (JIRA)

[ https://issues.jboss.org/browse/AS7-3199?page=com.atlassian.jira.plugin.s... ] Pavel Janousek commented on AS7-3199: ------------------------------------- Could be (at least) generated error message something aka "unsupported case" and not pure confusing exception? Anyway - which backward compatibility case breaks this requirement? One Application sub-class will be supported faraway, when being deploy more App. sub-class behavior will be the same as in reference impl. (Jersey) - which customer's expectation will be broken? > RESTEasy: Can't deploy WebApp if more than one subclass of javax.ws.rs.Application is present > --------------------------------------------------------------------------------------------- > > Key: AS7-3199 > URL: https://issues.jboss.org/browse/AS7-3199 > Project: Application Server 7 > Issue Type: Bug > Components: REST > Affects Versions: 7.1.0.CR1b > Reporter: Pavel Janousek > Assignee: Stuart Douglas > Priority: Critical > Labels: eap6_prd_req > Fix For: 7.1.1.Final > > Attachments: ExampleJAXRS.war > > > If I packed WAR WebApp with more that one subclass of javax.ws.rs.Application, deployment fails with "JBAS011232: Only one JAX-RS Application Class allowed." > This is not correct because it is against JAX-RS 1.1. specs where invalid situation (in section 2.3.2) is only when "It is a n error for > more than one application to be deployed +at the same effective servlet mapping+". > If you have any objections, please compare to reference JEE6 and JAX-RS implementation represented by the GlassFish Prelude 3.1.1 application server with already +fully JEE6 platform support+. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-3199) RESTEasy: Can't deploy WebApp if more than one subclass of javax.ws.rs.Application is present

by Bill Burke (JIRA)

[ https://issues.jboss.org/browse/AS7-3199?page=com.atlassian.jira.plugin.s... ] Bill Burke commented on AS7-3199: --------------------------------- Defer this. It is not being fixed for 2.3.2 or EAP6 because it would break backward compatibility and change user's expectations of code. > RESTEasy: Can't deploy WebApp if more than one subclass of javax.ws.rs.Application is present > --------------------------------------------------------------------------------------------- > > Key: AS7-3199 > URL: https://issues.jboss.org/browse/AS7-3199 > Project: Application Server 7 > Issue Type: Bug > Components: REST > Affects Versions: 7.1.0.CR1b > Reporter: Pavel Janousek > Assignee: Stuart Douglas > Priority: Critical > Labels: eap6_prd_req > Fix For: 7.1.1.Final > > Attachments: ExampleJAXRS.war > > > If I packed WAR WebApp with more that one subclass of javax.ws.rs.Application, deployment fails with "JBAS011232: Only one JAX-RS Application Class allowed." > This is not correct because it is against JAX-RS 1.1. specs where invalid situation (in section 2.3.2) is only when "It is a n error for > more than one application to be deployed +at the same effective servlet mapping+". > If you have any objections, please compare to reference JEE6 and JAX-RS implementation represented by the GlassFish Prelude 3.1.1 application server with already +fully JEE6 platform support+. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-2710) Allow a way to override the settings.xml used by the integration-tests.sh and build.sh

by jaikiran pai (Created) (JIRA)

Allow a way to override the settings.xml used by the integration-tests.sh and build.sh -------------------------------------------------------------------------------------- Key: AS7-2710 URL: https://issues.jboss.org/browse/AS7-2710 Project: Application Server 7 Issue Type: Enhancement Components: Test Suite Environment: AS7 upstream Reporter: jaikiran pai Assignee: Andrew Rubinger Right now the integration-tests.sh hardcodes the settings.xml that gets used for the tests: {code} # the default arguments MVN_OPTIONS="-s ../tools/maven/conf/settings.xml" {code} Some users have custom settings in my local /home/myname/.m2/settings.xml (for example the path to the local maven repo might be customized). I'm one of them. There should be a way to override the settings.xml that gets used in these test runs. i.e. if a overridden param value is specified then use it else fallback to the default (like above). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
3
0 / 0

[JBoss JIRA] (AS7-2040) AS7 TS: Running sets of tests from the command line

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/AS7-2040?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka resolved AS7-2040. ------------------------------- Resolution: Done Implemented using {{-Dts.xxx}} and documented in https://docs.jboss.org/author/display/AS71/AS+7+Integration+Testsuite+Use... > AS7 TS: Running sets of tests from the command line > --------------------------------------------------- > > Key: AS7-2040 > URL: https://issues.jboss.org/browse/AS7-2040 > Project: Application Server 7 > Issue Type: Task > Components: Test Suite > Reporter: Ondrej Zizka > Assignee: Ondrej Zizka > > Work out a way, using profiles, to run: > * unit tests and all integration tests in one shot (needed by dev) > * run the integration tests separately (needed by QA) > Running combinations of integration tests was achieved with the > $AS7/testsuite/build.{sh,bat} scripts, but I wasn't expecting the > requirement to have to be able to do this from $AS7/build.{sh,bat} > entirely. > {code} > @Test (groups = {"JMS", "XA"}) > {code} > or the new style > {code} > @Category( Integration.class ) > {code} > See 3.5.1 of https://docspace.corp.redhat.com/docs/DOC-74146 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-3810) Specifying the HTTPS port for the HTTP Interface but not specifying the keystore results in a NPE

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3810: ------------------------------------- Summary: Specifying the HTTPS port for the HTTP Interface but not specifying the keystore results in a NPE Key: AS7-3810 URL: https://issues.jboss.org/browse/AS7-3810 Project: Application Server 7 Issue Type: Bug Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.1.Final If the HTTPS port is specified but no keystore defined a NPE is encountered. At the very least a meaningful error should be reported. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

2
2
0 / 0

[JBoss JIRA] (AS7-3769) Register the whoami operation for domain mode.

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3769: ------------------------------------- Summary: Register the whoami operation for domain mode. Key: AS7-3769 URL: https://issues.jboss.org/browse/AS7-3769 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

2
3
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 February 2012