March 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1023) Add Missing Error Counts for Servlets

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-1023?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-1023: ----------------------------------- Component/s: Web (Undertow) I'm setting the component to "Web (Undertow)" in case this is applicable there. It's not a general Domain Management problem. > Add Missing Error Counts for Servlets > ------------------------------------- > > Key: WFLY-1023 > URL: https://issues.jboss.org/browse/WFLY-1023 > Project: WildFly > Issue Type: Enhancement > Components: Web (Undertow) > Environment: All applicable environments. > Reporter: Fernando Ribeiro > Assignee: Remy Maucherat > > Unlike in previous versions of AS, there aren't error counts for each servlet, but only a total in the connector. > These useful counts were used by many monitoring tools (e.g: RHQ/JON and dynaTrace), and should be available in AS 7 too. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1023) Add Missing Error Counts for Servlets

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-1023?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-1023: ----------------------------------- Component/s: (was: Domain Management) > Add Missing Error Counts for Servlets > ------------------------------------- > > Key: WFLY-1023 > URL: https://issues.jboss.org/browse/WFLY-1023 > Project: WildFly > Issue Type: Enhancement > Environment: All applicable environments. > Reporter: Fernando Ribeiro > Assignee: Remy Maucherat > > Unlike in previous versions of AS, there aren't error counts for each servlet, but only a total in the connector. > These useful counts were used by many monitoring tools (e.g: RHQ/JON and dynaTrace), and should be available in AS 7 too. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1134) Expose Http Session Manager trough management

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-1134?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-1134: ----------------------------------- Component/s: Web (Undertow) (was: Domain Management) > Expose Http Session Manager trough management > --------------------------------------------- > > Key: WFLY-1134 > URL: https://issues.jboss.org/browse/WFLY-1134 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Affects Versions: 8.0.0.Alpha1 > Reporter: Nicklas Karlsson > Assignee: Tomaz Cerar > > It would be handy to have access to a HTTP Session Manager so that you could e.g. see how many sessions are active, terminate selected sessions etc. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4299) transaction subsystem node-identifier can not resolve expression

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-4299?page=com.atlassian.jira.plugin.... ] Brian Stansberry resolved WFLY-4299. ------------------------------------ Fix Version/s: 9.0.0.Beta1 Resolution: Done Fixed with update of core to bring in WFCORE-499 fix. > transaction subsystem node-identifier can not resolve expression > ---------------------------------------------------------------- > > Key: WFLY-4299 > URL: https://issues.jboss.org/browse/WFLY-4299 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 9.0.0.Alpha1 > Reporter: Wolf-Dieter Fink > Assignee: Brian Stansberry > Priority: Critical > Labels: configuration, configuration_management, domain > Fix For: 9.0.0.Beta1 > > > If the transaction subsystem should use an expression as node-identifier this will not work in domain mode: > ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 36) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "transactions")]) - failure description: "WFLYCTL0211: Cannot resolve expression '${txNodeIdentifier}'" > This was possible in former builds with the same configuration. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-409) JPA should allow for a bean validator factory per persistence unit or per application deployment

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-409?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-409: ---------------------------------- Fix Version/s: (was: 8.0.0.Beta1) I'm clearing the Fix Version as 8.0.0.Beta1 is closed. > JPA should allow for a bean validator factory per persistence unit or per application deployment > ------------------------------------------------------------------------------------------------ > > Key: WFLY-409 > URL: https://issues.jboss.org/browse/WFLY-409 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Labels: open_to_community > > Currently, a new bean validator factory instance is associated with each deployed persistence unit. This jira calls for adding a new PU property that specifies that a 'per app bean validator factory' should be used for a persistence unit (via a persistence unit property). > This can be controlled by a new persistence unit property (see existing ones [here|https://docs.jboss.org/author/display/AS71/JPA+Reference+Guide#JPARe...]). > The new property can be something like "org.jboss.as.jpa.shareValidatorFactory" which defaults to false. > Look at org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.deployPersistenceUnit() to make this change. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3669) Deltaspike deployment fails on wildfly 8.1

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3669?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-3669: ----------------------------------- Fix Version/s: (was: 8.1.0.Final) > Deltaspike deployment fails on wildfly 8.1 > ------------------------------------------ > > Key: WFLY-3669 > URL: https://issues.jboss.org/browse/WFLY-3669 > Project: WildFly > Issue Type: Bug > Reporter: Paa Kojo Konduah Amos > Assignee: Jason Greene > > on addition of the Deltaspike-core dependency in my pom.xml....wildfly 8.1 fails at deployment time. > 01:45:08,481 INFO [org.apache.deltaspike.core.util.ProjectStageProducer] (MSC service thread 1-4) Computed the following DeltaSpike ProjectStage: Production > 01:45:12,813 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."jwi.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."jwi.war".WeldStartService: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [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_65] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65] > Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414: Bean name is ambiguous. Name dsWindowContext resolves to beans: > Producer Method [WindowContext] with qualifiers [@Default @Named @Any] declared as [[BackedAnnotatedMethod] @Produces @Named @Dependent public org.apache.deltaspike.core.impl.scope.window.WindowContextProducer.getWindowContext()], > Producer Method [WindowContext] with qualifiers [@Default @Named @Any] declared as [[BackedAnnotatedMethod] @Produces @Named @Dependent public org.apache.deltaspike.core.impl.scope.window.WindowContextProducer.getWindowContext()] > at org.jboss.weld.bootstrap.ConcurrentValidator$5.doWork(ConcurrentValidator.java:134) > at org.jboss.weld.bootstrap.ConcurrentValidator$5.doWork(ConcurrentValidator.java:130) > at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60) > at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_65] > ... 3 more > 01:45:12,824 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "jwi.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"jwi.war\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jwi.war\".WeldStartService: Failed to start service > Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414: Bean name is ambiguous. Name dsWindowContext resolves to beans: > Producer Method [WindowContext] with qualifiers [@Default @Named @Any] declared as [[BackedAnnotatedMethod] @Produces @Named @Dependent public org.apache.deltaspike.core.impl.scope.window.WindowContextProducer.getWindowContext()], > Producer Method [WindowContext] with qualifiers [@Default @Named @Any] declared as [[BackedAnnotatedMethod] @Produces @Named @Dependent public org.apache.deltaspike.core.impl.scope.window.WindowContextProducer.getWindowContext()]"}} > 01:45:12,919 INFO [org.jboss.as.server] (ServerService Thread Pool – 28) JBAS018559: Deployed "jwi.war" (runtime-name : "jwi.war") > 01:45:12,928 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report > JBAS014777: Services which failed to start: service jboss.deployment.unit."jwi.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."jwi.war".WeldStartService: Failed to start service -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4415) RemotingContext should be copied for async EJB calls

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4415?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-4415: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1201439 > RemotingContext should be copied for async EJB calls > ---------------------------------------------------- > > Key: WFLY-4415 > URL: https://issues.jboss.org/browse/WFLY-4415 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Stuart Douglas > Assignee: Stuart Douglas > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-166) Add a RemoveGlobalSecurityProvider action.

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-166: ------------------------------------ Summary: Add a RemoveGlobalSecurityProvider action. Key: ELY-166 URL: https://issues.jboss.org/browse/ELY-166 Project: WildFly Elytron Issue Type: Feature Request Components: Security Manager Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4423) ClassNotFoundException: org.jboss.naming.remote.client.InitialContextFactory

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4423?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-4423: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1201358 > ClassNotFoundException: org.jboss.naming.remote.client.InitialContextFactory > ---------------------------------------------------------------------------- > > Key: WFLY-4423 > URL: https://issues.jboss.org/browse/WFLY-4423 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 9.0.0.Alpha1 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 9.0.0.Beta1 > > > To reproduce this issue follow the steps: > - setup JMS bridge between two WildFly instances > - once JMS bridge is running, login into jboss-cli and stop the bridge > - restart the bridge fro jboss-cli > The following exception appears in the serve log file. > 10:12:59,414 INFO [org.hornetq.jms.server] (pool-9-thread-1) HQ121000: Failed to set up JMS bridge connections. Most probably the source or target servers are unavailable. Will retry after a pause of 60,000 ms > 10:13:59,416 WARN [org.hornetq.jms.server] (pool-9-thread-1) HQ122010: Failed to connect JMS Bridge: javax.naming.NamingException: JBAS011843: Failed instantiate InitialContextFactory org.jboss.naming.remote.client.InitialContextFactory from classloader ModuleClassLoader for Module "org.jboss.as.controller:main" from local module loader @543a2dec (finder: local module finder @379d0c27 (roots: /Volumes/RedHat/Work/JBoss/EAP/JBoss-6/current/home/modules,/Volumes/RedHat/Work/JBoss/EAP/JBoss-6/current/home/modules/system/layers/base)) [Root exception is java.lang.ClassNotFoundException: org.jboss.naming.remote.client.InitialContextFactory from [Module "org.jboss.as.controller:main" from local module loader @543a2dec (finder: local module finder @379d0c27 (roots: /Volumes/RedHat/Work/JBoss/EAP/JBoss-6/current/home/modules,/Volumes/RedHat/Work/JBoss/EAP/JBoss-6/current/home/modules/system/layers/base))]] > at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:126) > at org.jboss.as.naming.InitialContext.init(InitialContext.java:107) > at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:153) [rt.jar:1.7.0_75] > at org.jboss.as.naming.InitialContext.<init>(InitialContext.java:98) > at org.jboss.as.naming.InitialContextFactory.getInitialContext(InitialContextFactory.java:44) > at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684) [rt.jar:1.7.0_75] > at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307) [rt.jar:1.7.0_75] > at javax.naming.InitialContext.init(InitialContext.java:242) [rt.jar:1.7.0_75] > at javax.naming.InitialContext.<init>(InitialContext.java:216) [rt.jar:1.7.0_75] > at org.hornetq.jms.bridge.impl.JNDIFactorySupport.createObject(JNDIFactorySupport.java:55) > at org.hornetq.jms.bridge.impl.JNDIDestinationFactory.createDestination(JNDIDestinationFactory.java:40) > at org.hornetq.jms.bridge.impl.JMSBridgeImpl.setupJMSObjects(JMSBridgeImpl.java:1236) > at org.hornetq.jms.bridge.impl.JMSBridgeImpl.setupJMSObjectsWithRetry(JMSBridgeImpl.java:1474) > at org.hornetq.jms.bridge.impl.JMSBridgeImpl.access$2200(JMSBridgeImpl.java:79) > at org.hornetq.jms.bridge.impl.JMSBridgeImpl$FailureHandler.run(JMSBridgeImpl.java:2082) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_75] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_75] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75] > Caused by: java.lang.ClassNotFoundException: org.jboss.naming.remote.client.InitialContextFactory from [Module "org.jboss.as.controller:main" from local module loader @543a2dec (finder: local module finder @379d0c27 (roots: /Volumes/RedHat/Work/JBoss/EAP/JBoss-6/current/home/modules,/Volumes/RedHat/Work/JBoss/EAP/JBoss-6/current/home/modules/system/layers/base))] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.5.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.5.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.5.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.5.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.5.Final-redhat-1] > at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_75] > at java.lang.Class.forName(Class.java:274) [rt.jar:1.7.0_75] > at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:121) > ... 17 more -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4423) ClassNotFoundException: org.jboss.naming.remote.client.InitialContextFactory

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-4423: --------------------------------- Summary: ClassNotFoundException: org.jboss.naming.remote.client.InitialContextFactory Key: WFLY-4423 URL: https://issues.jboss.org/browse/WFLY-4423 Project: WildFly Issue Type: Bug Components: JMS Affects Versions: 9.0.0.Alpha1 Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 9.0.0.Beta1 To reproduce this issue follow the steps: - setup JMS bridge between two WildFly instances - once JMS bridge is running, login into jboss-cli and stop the bridge - restart the bridge fro jboss-cli The following exception appears in the serve log file. 10:12:59,414 INFO [org.hornetq.jms.server] (pool-9-thread-1) HQ121000: Failed to set up JMS bridge connections. Most probably the source or target servers are unavailable. Will retry after a pause of 60,000 ms 10:13:59,416 WARN [org.hornetq.jms.server] (pool-9-thread-1) HQ122010: Failed to connect JMS Bridge: javax.naming.NamingException: JBAS011843: Failed instantiate InitialContextFactory org.jboss.naming.remote.client.InitialContextFactory from classloader ModuleClassLoader for Module "org.jboss.as.controller:main" from local module loader @543a2dec (finder: local module finder @379d0c27 (roots: /Volumes/RedHat/Work/JBoss/EAP/JBoss-6/current/home/modules,/Volumes/RedHat/Work/JBoss/EAP/JBoss-6/current/home/modules/system/layers/base)) [Root exception is java.lang.ClassNotFoundException: org.jboss.naming.remote.client.InitialContextFactory from [Module "org.jboss.as.controller:main" from local module loader @543a2dec (finder: local module finder @379d0c27 (roots: /Volumes/RedHat/Work/JBoss/EAP/JBoss-6/current/home/modules,/Volumes/RedHat/Work/JBoss/EAP/JBoss-6/current/home/modules/system/layers/base))]] at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:126) at org.jboss.as.naming.InitialContext.init(InitialContext.java:107) at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:153) [rt.jar:1.7.0_75] at org.jboss.as.naming.InitialContext.<init>(InitialContext.java:98) at org.jboss.as.naming.InitialContextFactory.getInitialContext(InitialContextFactory.java:44) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684) [rt.jar:1.7.0_75] at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307) [rt.jar:1.7.0_75] at javax.naming.InitialContext.init(InitialContext.java:242) [rt.jar:1.7.0_75] at javax.naming.InitialContext.<init>(InitialContext.java:216) [rt.jar:1.7.0_75] at org.hornetq.jms.bridge.impl.JNDIFactorySupport.createObject(JNDIFactorySupport.java:55) at org.hornetq.jms.bridge.impl.JNDIDestinationFactory.createDestination(JNDIDestinationFactory.java:40) at org.hornetq.jms.bridge.impl.JMSBridgeImpl.setupJMSObjects(JMSBridgeImpl.java:1236) at org.hornetq.jms.bridge.impl.JMSBridgeImpl.setupJMSObjectsWithRetry(JMSBridgeImpl.java:1474) at org.hornetq.jms.bridge.impl.JMSBridgeImpl.access$2200(JMSBridgeImpl.java:79) at org.hornetq.jms.bridge.impl.JMSBridgeImpl$FailureHandler.run(JMSBridgeImpl.java:2082) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_75] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_75] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75] Caused by: java.lang.ClassNotFoundException: org.jboss.naming.remote.client.InitialContextFactory from [Module "org.jboss.as.controller:main" from local module loader @543a2dec (finder: local module finder @379d0c27 (roots: /Volumes/RedHat/Work/JBoss/EAP/JBoss-6/current/home/modules,/Volumes/RedHat/Work/JBoss/EAP/JBoss-6/current/home/modules/system/layers/base))] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.5.Final-redhat-1] at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.5.Final-redhat-1] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.5.Final-redhat-1] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.5.Final-redhat-1] at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.5.Final-redhat-1] at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_75] at java.lang.Class.forName(Class.java:274) [rt.jar:1.7.0_75] at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:121) ... 17 more -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 8 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 March 2015