September 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3803) Missing -jandex.jar libs with build using feature-pack

by Alessio Soldano (JIRA)

Alessio Soldano created WFLY-3803: ------------------------------------- Summary: Missing -jandex.jar libs with build using feature-pack Key: WFLY-3803 URL: https://issues.jboss.org/browse/WFLY-3803 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Build System Reporter: Alessio Soldano Assignee: Tomaz Cerar Priority: Blocker Fix For: 9.0.0.Beta1 After the recent changes to have feature-packs, the build is not creating -jandex.jar libs anymore. We used to have two of them in the org.apache.cxf.impl module. Those are strictly required for WS-* functionalities. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3201) Channel end notification received, closing channel ... should be logged at debug

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3201?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3201: ----------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1069591|https://bugzilla.redhat.com/show_bug.cgi?id=1069591] from ON_QA to VERIFIED > Channel end notification received, closing channel ... should be logged at debug > -------------------------------------------------------------------------------- > > Key: WFLY-3201 > URL: https://issues.jboss.org/browse/WFLY-3201 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Naming > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Fix For: 8.1.0.Final > > > Remote naming is logging this at ERROR, though it seems normal and no adverse effects are apparent, we should log it at debug instead of error. > ERROR Channel end notification received, closing channel Channel ID b8e969d6 (outbound) of Remoting connection 4970f4db to ... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-854) Fallback to FORM authentication when an invalid kerberos token is used

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-854?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-854: -------------------------------------------------- FIlip Bogyai <fbogyai(a)redhat.com> changed the Status of [bug 1131229|https://bugzilla.redhat.com/show_bug.cgi?id=1131229] from ON_QA to VERIFIED > Fallback to FORM authentication when an invalid kerberos token is used > ---------------------------------------------------------------------- > > Key: SECURITY-854 > URL: https://issues.jboss.org/browse/SECURITY-854 > Project: PicketBox > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Negotiation > Reporter: Derek Horton > Assignee: Darran Lofthouse > Fix For: Negotiation_2_3_4_Final > > > Negotiation will not fallback to FORM authentication if the client has a kerberos token from a different KDC than what JBoss is configured to use. > This results in the user getting presented with a 401 error and no way to login. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

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

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/JBMETA-379?page=com.atlassian.jira.plugin... ] Jean-Frederic Clere updated JBMETA-379: --------------------------------------- Fix Version/s: 8.0.1.Final > 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 > Security Level: Public(Everyone can see) > 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, 2 months

1
0
0 / 0

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

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/JBMETA-379?page=com.atlassian.jira.plugin... ] Jean-Frederic Clere commented on JBMETA-379: -------------------------------------------- merged, > 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 > Security Level: Public(Everyone can see) > Components: web > Affects Versions: 8.0.0.Final > Reporter: Jay Kumar SenSharma > Assignee: Jean-Frederic Clere > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-944) Connection manager not available during shutdown

by Piotr Findeisen (JIRA)

[ https://issues.jboss.org/browse/WFLY-944?page=com.atlassian.jira.plugin.s... ] Piotr Findeisen edited comment on WFLY-944 at 9/2/14 2:25 AM: -------------------------------------------------------------- I'm deploying single WAR and using Spring's {{<jee:jndi-lookup/>}} to access the datasource as a Spring bean. During application udneployment, I get a lot of those: {code} Caused by: javax.resource.ResourceException: IJ000451: The connection manager is shutdown: java:jboss/datasources/MyDS at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:321) at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:368) at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:464) at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:139) ... 52 more {code} No matter whether I configure datasource in {{standalone.xml}} or as a separate {{my-ds.xml}} in {{deployments/}}. Is it possible to workaround this without using EJBs? If not, how can I add one EJB to my WAR without having JBoss scan all my classes. Normally, in my case it is Spring who handles {{@Resource}} annotation. was (Author: findepi): I'm deploying single WAR and using Spring's {{<jee:jndi-lookup/>}} to access the datasource as a Spring bean. During application udneployment, I get a lot of those: {code} Caused by: javax.resource.ResourceException: IJ000451: The connection manager is shutdown: java:jboss/datasources/MyDS at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:321) at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:368) at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:464) at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:139) ... 52 more {code} No matter whether I configure datasource in {{standalone.xml}} or as a separate {{my-ds.xml}} in {{deployments/}}. Is it possible to workaround this without using EJBs? If not, wow can I add one EJB to my WAR without having JBoss scan all my classes. Normally, in my case it is Spring who handles {{@Resource}} annotation. > Connection manager not available during shutdown > ------------------------------------------------ > > Key: WFLY-944 > URL: https://issues.jboss.org/browse/WFLY-944 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server > Reporter: Ori Kremer > Attachments: TestEAR.zip > > > The problem occurs when trying to access the database during the shutdown phase. > It looks like when our shutdown code tries to access the database - it is no longer available. > Our application is deployed as an EAR that has a SAR module to handle startup and shutdown. > We add our application specific startup and shutdown code in the corresponding MBean hooks. > In JBoss 7.0.2 and 7.1.1 we're encountering an error when the shutdown code is attempting to access the database and is failing due to the fact that the connection manager is closed: > 13:08:37,975 ERROR [org.jboss.as.service] JBAS017200: Failed to execute legacy service stop() method: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_01] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_01] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_01] > at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_01] > at org.jboss.as.service.AbstractService.invokeLifecycleMethod(AbstractService.java:52) [jboss-as-sar-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.service.StartStopService.stop(StartStopService.java:66) [jboss-as-sar-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1911) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1874) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_01] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_01] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_01] > Caused by: java.sql.SQLException: javax.resource.ResourceException: IJ000451: The connection manager is shutdown: java:/org.test.NonSecureDS > at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:137) > at org.test.StartupService.updateStatus(StartupService.java:37) > at org.test.StartupService.stop(StartupService.java:56) > ... 11 more > Caused by: javax.resource.ResourceException: IJ000451: The connection manager is shutdown: java:/org.test.NonSecureDS > at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:321) > at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:368) > at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:464) > at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:129) > ... 13 more -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3797) Need post-timeout for WildFly / Undertow

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-3797?page=com.atlassian.jira.plugin.... ] Stuart Douglas resolved WFLY-3797. ---------------------------------- Resolution: Done This desired effect can be achieved by setting the read-timeout option on the listener. > Need post-timeout for WildFly / Undertow > ---------------------------------------- > > Key: WFLY-3797 > URL: https://issues.jboss.org/browse/WFLY-3797 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.1.0.Final > Reporter: Lyle Wang > Assignee: Stuart Douglas > > Is that possible to provide post timeout to prevent DoS ? JBoss AS 7 or WildFly has no such feature/option, but weblogic provides this: > http://docs.oracle.com/cd/E17904_01/web.1111/e13701/web_server.htm#i1059782 > Currently only "max-post-size" is supported: > https://docs.jboss.org/author/display/WFLY8/Undertow+%28web%29+subsystem+... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3802) 'Create a datasource' shows up on front page on console even if subsystem is not installed

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-3802: ------------------------------------ Summary: 'Create a datasource' shows up on front page on console even if subsystem is not installed Key: WFLY-3802 URL: https://issues.jboss.org/browse/WFLY-3802 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Console Reporter: Stuart Douglas Assignee: Heiko Braun e.g. if you install the console in wildfly-core with no datasources subsystem present this will still show up. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFBUILD-5) Build tools should use jboss-logging to allow internationalization

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFBUILD-5?page=com.atlassian.jira.plugin.... ] Stuart Douglas reassigned WFBUILD-5: ------------------------------------ Assignee: Eduardo Martins (was: Stuart Douglas) > Build tools should use jboss-logging to allow internationalization > ------------------------------------------------------------------ > > Key: WFBUILD-5 > URL: https://issues.jboss.org/browse/WFBUILD-5 > Project: WildFly Build Tools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Stuart Douglas > Assignee: Eduardo Martins > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3455) JBAS014544: No EJB found with interface of type

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-3455?page=com.atlassian.jira.plugin.... ] Stuart Douglas closed WFLY-3455. -------------------------------- Resolution: Rejected EJB's are not resolved across applications. You need to specify the global JNDI name of the ejb, e.g. @EJB(lookup="java:global/myapp/mymodule/MyEjb") > JBAS014544: No EJB found with interface of type > ----------------------------------------------- > > Key: WFLY-3455 > URL: https://issues.jboss.org/browse/WFLY-3455 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Affects Versions: 8.1.0.Final > Environment: Ubuntu 14.04 LTS: Linux blackbox 3.13.0-27-generic #50-Ubuntu SMP Thu May 15 18:06:16 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux > Java: java version "1.7.0_60" > Java(TM) SE Runtime Environment (build 1.7.0_60-b19) > Java HotSpot(TM) 64-Bit Server VM (build 24.60-b09, mixed mode) > Reporter: Gregor Kovač > Assignee: Enrique González Martínez > Attachments: WildflyTest.zip > > > I have an EAR with an Stateless EJB that implements a Remote interface. > In another application (WAR) I access his EJB like this: @EJB(beanInterface=RemoteBean.class) RemoteBean bean; When I deploy EAR I can see the JNDI name of the EJB, but when I deploy WAR I get error: JBAS014544: No EJB found with interface of type ..... > I have attached an example application. > You can build it with Maven, deploy and see that error. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 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 September 2014