November 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-271) The description of the default scanner attribute "scan-enabled" is incorrect.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-271?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-271: ------------------------------------------------ Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1162982|https://bugzilla.redhat.com/show_bug.cgi?id=1162982] from POST to MODIFIED > The description of the default scanner attribute "scan-enabled" is incorrect. > ------------------------------------------------------------------------------- > > Key: WFCORE-271 > URL: https://issues.jboss.org/browse/WFCORE-271 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha13 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Minor > > Description of problem: The description of the 'scan-enabled' attribute states "Flag indicating that all scanning (including initial scanning at startup) should be disabled." The default value of this attribute is "true", therefore I believe the description is incorrect. > I propose that the description be changed to: "Flag indicating if all scanning (including initial scanning at startup) is enabled." -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2806) Add check to fail deployments that use CXFServlet but have not disabled the WS subsystem

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2806?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2806: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1166458|https://bugzilla.redhat.com/show_bug.cgi?id=1166458] from POST to MODIFIED > Add check to fail deployments that use CXFServlet but have not disabled the WS subsystem > ---------------------------------------------------------------------------------------- > > Key: WFLY-2806 > URL: https://issues.jboss.org/browse/WFLY-2806 > Project: WildFly > Issue Type: Feature Request > Components: Web Services > Reporter: Kyle Lape > Assignee: Alessio Soldano > Fix For: 9.0.0.Beta1 > > > If {{CXFServlet}} is defined in an app's {{web.xml}}, the webservices subsystem should always be disabled. (Of course the preference would be to stop using {{CXFServlet}} and follow the JAX-WS way to deploy web services.) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3931) Custom formatter property changes not written to, but overriden by logging.properties

by Anderson Parra de Paula (JIRA)

[ https://issues.jboss.org/browse/WFLY-3931?page=com.atlassian.jira.plugin.... ] Anderson Parra de Paula commented on WFLY-3931: ----------------------------------------------- Hello Vsevolod Golovanov. Please, could you attach your standalone.xml for that I will simulate this problem. Thank you! > Custom formatter property changes not written to, but overriden by logging.properties > ------------------------------------------------------------------------------------- > > Key: WFLY-3931 > URL: https://issues.jboss.org/browse/WFLY-3931 > Project: WildFly > Issue Type: Bug > Components: Logging > Affects Versions: 8.1.0.Final > Environment: Wildfly 8.1.0.Final > Reporter: Vsevolod Golovanov > Assignee: James Perkins > > When you first add custom formatter with properties to standalone.xml, on server start property values get correctly resolved and written to logging.properties. > If you change property values in standalone.xml of an existing custom formatter, that was flushed to logging.properties before, then on the next server start new values don't get written to logging.properties and formatter instance gets the old values from logging.properties. > For properties with static values that are defined in standalone.xml there is a workaround: change the custom formatter name each time you change a property value. > But with more dynamic properties, e.g. that rely on system properties, it's not so simple... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3935) cluster-ha-singleton fails to deploy when the server is started with the debug flag

by Anderson Parra de Paula (JIRA)

[ https://issues.jboss.org/browse/WFLY-3935?page=com.atlassian.jira.plugin.... ] Anderson Parra de Paula commented on WFLY-3935: ----------------------------------------------- I didn't have problems to run this application on current development version using debug mode. Please, take a look at log: 14:27:54,664 INFO [org.jboss.as.server] (XNIO-1 task-7) WFLYSRV0010: Deployed "wildfly-cluster-ha-singleton-service.jar" (runtime-name : "wildfly-cluster-ha-singleton-service.jar") 14:28:00,010 INFO [org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.SchedulerBean] (EJB default - 1) HASingletonTimer: Info=HASingleton timer @jb.node1 Fri Nov 21 14:27:54 GMT 2014 14:28:10,002 INFO [org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.SchedulerBean] (EJB default - 2) HASingletonTimer: Info=HASingleton timer @jb.node1 Fri Nov 21 14:27:54 GMT 2014 14:28:20,002 INFO [org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.SchedulerBean] (EJB default - 3) HASingletonTimer: Info=HASingleton timer @jb.node1 Fri Nov 21 14:27:54 GMT 2014 14:28:30,001 INFO [org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.SchedulerBean] (EJB default - 4) HASingletonTimer: Info=HASingleton timer @jb.node1 Fri Nov 21 14:27:54 GMT 2014 14:28:40,024 INFO [org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.SchedulerBean] (EJB default - 5) HASingletonTimer: Info=HASingleton timer @jb.node1 Fri Nov 21 14:27:54 GMT 2014 14:28:50,015 INFO [org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.SchedulerBean] (EJB default - 6) HASingletonTimer: Info=HASingleton timer @jb.node1 Fri Nov 21 14:27:54 GMT 2014 > cluster-ha-singleton fails to deploy when the server is started with the debug flag > ----------------------------------------------------------------------------------- > > Key: WFLY-3935 > URL: https://issues.jboss.org/browse/WFLY-3935 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.1.0.Final > Reporter: Euan Mapham > Assignee: Jason Greene > > When a clustered-ha-singleton is deployed to a wildfly server that was started using the --debug option, a org.jboss.msc.service.ServiceNotFoundException occurrs. > I am using the quickstart/cluster-ha-singleton found on github: > https://github.com/wildfly/quickstart/tree/master/cluster-ha-singleton > Wildfly version 8.1.0.Final > I start the server with this command: > ./bin/standalone.sh --debug -server-config=standalone-ha.xml -Djboss.node.name=jb.node1 > I then deploy the wildfly-cluster-ha-singleton-service.jar. > The exception that occurrs is: > 15:03:31,803 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."wildfly-cluster-ha-singleton-service.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."wildfly-cluster-ha-singleton-service.jar".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "wildfly-cluster-ha-singleton-service.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.1.0.Final.jar:8.1.0.Final] > 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:1142) [rt.jar:1.8.0_20] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_20] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_20] > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.clustering.singleton.builder.server.default not found > at org.jboss.as.server.deployment.service.ServiceActivatorProcessor.deploy(ServiceActivatorProcessor.java:72) [wildfly-server-8.1.0.Final.jar:8.1.0.Final] > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.1.0.Final.jar:8.1.0.Final] > ... 5 more > Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.clustering.singleton.builder.server.default not found > at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:668) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.DelegatingServiceRegistry.getRequiredService(DelegatingServiceRegistry.java:46) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.HATimerServiceActivator.install(HATimerServiceActivator.java:51) > at org.jboss.as.quickstarts.cluster.hasingleton.service.ejb.HATimerServiceActivator.activate(HATimerServiceActivator.java:44) > at org.jboss.as.server.deployment.service.ServiceActivatorProcessor.deploy(ServiceActivatorProcessor.java:70) [wildfly-server-8.1.0.Final.jar:8.1.0.Final] > ... 6 more > When I remove the "--debug" option from the command to start the server, everything works fine. > This means we cannot debug our applications if we use this feature. > Regards, > Euan -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4111) Unable to read web-application files using ServletContext.getResourceAsStream when security manager is used

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-4111?page=com.atlassian.jira.plugin.... ] David Lloyd updated WFLY-4111: ------------------------------ Assignee: Stuart Douglas (was: Stefan Guilhen) > Unable to read web-application files using ServletContext.getResourceAsStream when security manager is used > ----------------------------------------------------------------------------------------------------------- > > Key: WFLY-4111 > URL: https://issues.jboss.org/browse/WFLY-4111 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Josef Cacek > Assignee: Stuart Douglas > > Servlets should be able to read application files by using ServletContext.getResourceAsStream without specifying additional permissions. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4111) Unable to read web-application files using ServletContext.getResourceAsStream when security manager is used

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-4111?page=com.atlassian.jira.plugin.... ] David Lloyd updated WFLY-4111: ------------------------------ Component/s: Web (Undertow) (was: Security Manager) > Unable to read web-application files using ServletContext.getResourceAsStream when security manager is used > ----------------------------------------------------------------------------------------------------------- > > Key: WFLY-4111 > URL: https://issues.jboss.org/browse/WFLY-4111 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Josef Cacek > Assignee: Stefan Guilhen > > Servlets should be able to read application files by using ServletContext.getResourceAsStream without specifying additional permissions. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4111) Unable to read web-application files using ServletContext.getResourceAsStream when security manager is used

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-4111?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-4111: ----------------------------------- I think that (at least for JARs) we have automatically added read permission for the deployment to read its own content directory. Maybe that part is failing for servlets somehow. > Unable to read web-application files using ServletContext.getResourceAsStream when security manager is used > ----------------------------------------------------------------------------------------------------------- > > Key: WFLY-4111 > URL: https://issues.jboss.org/browse/WFLY-4111 > Project: WildFly > Issue Type: Bug > Components: Security Manager > Reporter: Josef Cacek > Assignee: Stefan Guilhen > > Servlets should be able to read application files by using ServletContext.getResourceAsStream without specifying additional permissions. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4111) Unable to read web-application files using ServletContext.getResourceAsStream when security manager is used

by Josef Cacek (JIRA)

Josef Cacek created WFLY-4111: --------------------------------- Summary: Unable to read web-application files using ServletContext.getResourceAsStream when security manager is used Key: WFLY-4111 URL: https://issues.jboss.org/browse/WFLY-4111 Project: WildFly Issue Type: Bug Components: Security Manager Reporter: Josef Cacek Assignee: Stefan Guilhen Servlets should be able to read application files by using ServletContext.getResourceAsStream without specifying additional permissions. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4110) EJBClientClusterConfigurationTestCase fails on JDK1.8 once -Dnode0 and -Dnode1 are used

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4110?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4110: ----------------------------------------------- Dominik Pospisil <dpospisi(a)redhat.com> changed the Status of [bug 1164231|https://bugzilla.redhat.com/show_bug.cgi?id=1164231] from ASSIGNED to POST > EJBClientClusterConfigurationTestCase fails on JDK1.8 once -Dnode0 and -Dnode1 are used > --------------------------------------------------------------------------------------- > > Key: WFLY-4110 > URL: https://issues.jboss.org/browse/WFLY-4110 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 9.0.0.Alpha1 > Reporter: Dominik Pospisil > Assignee: Dominik Pospisil > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4110) EJBClientClusterConfigurationTestCase fails on JDK1.8 once -Dnode0 and -Dnode1 are used

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4110?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-4110: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1164231 > EJBClientClusterConfigurationTestCase fails on JDK1.8 once -Dnode0 and -Dnode1 are used > --------------------------------------------------------------------------------------- > > Key: WFLY-4110 > URL: https://issues.jboss.org/browse/WFLY-4110 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 9.0.0.Alpha1 > Reporter: Dominik Pospisil > Assignee: Dominik Pospisil > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

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