March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1499) When concurrently get prototype ksession bean, it could be repeated

by 国伟朱 (JIRA)

国伟朱 created DROOLS-1499: ---------------------------- Summary: When concurrently get prototype ksession bean, it could be repeated Key: DROOLS-1499 URL: https://issues.jboss.org/browse/DROOLS-1499 Project: Drools Issue Type: Bug Components: integration Affects Versions: 6.5.0.Final Reporter: 国伟朱 Assignee: Mario Fusco when currently get ksession bean , there could be repeated ksessions. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-149) Initializing the SyslogHandler should not do a permissions check when setting the output stream

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-149?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-149: --------------------------------- Git Pull Request: https://github.com/jboss-logging/jboss-logmanager/pull/107, https://github.com/jboss-logging/jboss-logmanager/pull/108, https://github.com/jboss-logging/jboss-logmanager/pull/109 (was: https://github.com/jboss-logging/jboss-logmanager/pull/107, https://github.com/jboss-logging/jboss-logmanager/pull/108) > Initializing the SyslogHandler should not do a permissions check when setting the output stream > ----------------------------------------------------------------------------------------------- > > Key: LOGMGR-149 > URL: https://issues.jboss.org/browse/LOGMGR-149 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Perkins > Fix For: 1.5.8.Final, 2.0.7.Final, 2.1.0.Beta1 > > > The {{org.jboss.logmanager.handlers.SyslogHandler}} attempts to lazily connect to the syslog server. If running under a security manager and the user (deployment in WildFly's case) doesn't have {{control}} logging permissions, the write will fail. The failure is also swallowed which means there is no indication as to what the error is. Logs will just not appear on the syslog server. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-149) Initializing the SyslogHandler should not do a permissions check when setting the output stream

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-149?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-149: --------------------------------- Fix Version/s: 1.5.8.Final 2.0.7.Final 2.1.0.Beta1 > Initializing the SyslogHandler should not do a permissions check when setting the output stream > ----------------------------------------------------------------------------------------------- > > Key: LOGMGR-149 > URL: https://issues.jboss.org/browse/LOGMGR-149 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Perkins > Fix For: 1.5.8.Final, 2.0.7.Final, 2.1.0.Beta1 > > > The {{org.jboss.logmanager.handlers.SyslogHandler}} attempts to lazily connect to the syslog server. If running under a security manager and the user (deployment in WildFly's case) doesn't have {{control}} logging permissions, the write will fail. The failure is also swallowed which means there is no indication as to what the error is. Logs will just not appear on the syslog server. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-149) Initializing the SyslogHandler should not do a permissions check when setting the output stream

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-149?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-149: --------------------------------- Git Pull Request: https://github.com/jboss-logging/jboss-logmanager/pull/107, https://github.com/jboss-logging/jboss-logmanager/pull/108 (was: https://github.com/jboss-logging/jboss-logmanager/pull/107) > Initializing the SyslogHandler should not do a permissions check when setting the output stream > ----------------------------------------------------------------------------------------------- > > Key: LOGMGR-149 > URL: https://issues.jboss.org/browse/LOGMGR-149 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Perkins > > The {{org.jboss.logmanager.handlers.SyslogHandler}} attempts to lazily connect to the syslog server. If running under a security manager and the user (deployment in WildFly's case) doesn't have {{control}} logging permissions, the write will fail. The failure is also swallowed which means there is no indication as to what the error is. Logs will just not appear on the syslog server. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2532) Some logging tests fail with security manager in WF core

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2532?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-2532: --------------------------------------- In the pull request I added a work around for LOGMGR-149. This is a permissions error in the {{org.jboss.logmanager.handlers.SyslogHandler}}. > Some logging tests fail with security manager in WF core > -------------------------------------------------------- > > Key: WFCORE-2532 > URL: https://issues.jboss.org/browse/WFCORE-2532 > Project: WildFly Core > Issue Type: Bug > Components: Logging, Test Suite > Reporter: Jan Tymel > Assignee: James Perkins > > * *org.jboss.as.test.integration.logging.operations.CustomFormattersTestCase* > * *org.jboss.as.test.integration.logging.operations.CustomHandlerOperationsTestCase* > * *org.jboss.as.test.integration.logging.operations.CustomHandlerTestCase* > * *org.jboss.as.test.integration.logging.operations.Log4jCustomHandlerTestCase* > * *org.jboss.as.test.integration.logging.perdeploy.JBossLog4jXmlTestCase* > * *org.jboss.as.test.integration.logging.perdeploy.JBossLoggingPropertiesTestCase* > * *org.jboss.as.test.integration.logging.perdeploy.Log4jPropertiesTestCase* > * *org.jboss.as.test.integration.logging.perdeploy.Log4jXmlTestCase* > * *org.jboss.as.test.integration.logging.perdeploy.LoggingPropertiesTestCase* > * *org.jboss.as.test.integration.logging.profiles.LoggingProfilesTestCase* > * *org.jboss.as.test.integration.logging.profiles.NonExistingProfileTestCase* > * *org.jboss.as.test.integration.logging.syslog.SyslogHandlerTestCase* > {{cd testsuite/standalone/}} > {{mvn test -Dtest=org.jboss.as.test.integration.logging.**.* -Dsecurity.manager}} > {code} > org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper$ServerDeploymentException: java.lang.Exception: { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"logging1.jar\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"logging1.jar\".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment \"logging1.jar\" > Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission \"(\"java.util.PropertyPermission\" \"jboss.bind.address\" \"read\")\" in code source \"(vfs:/content/logging1.jar <no signer certificates>)\" of \"ModuleClassLoader for Module \"deployment.logging1.jar\" from Service Module Loader\")"}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"logging1.jar\".INSTALL"] > } > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134) > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123) > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85) > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42) > at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:55) > at org.jboss.as.test.integration.logging.AbstractLoggingTestCase.deploy(AbstractLoggingTestCase.java:168) > at org.jboss.as.test.integration.logging.profiles.LoggingProfilesTestCase.deploy(LoggingProfilesTestCase.java:314) > at org.jboss.as.test.integration.logging.profiles.LoggingProfilesTestCase.deploy(LoggingProfilesTestCase.java:304) > at org.jboss.as.test.integration.logging.profiles.LoggingProfilesTestCase.testProfiles(LoggingProfilesTestCase.java:201 > {code} > * *org.jboss.as.test.manualmode.logging.Log4jAppenderTestCase* > * *org.jboss.as.test.manualmode.logging.LoggingPreferencesTestCase* > * *org.jboss.as.test.manualmode.logging.PerDeployLoggingTestCase* > * *org.jboss.as.test.manualmode.logging.ReconnectSyslogServerTestCase* > * *org.jboss.as.test.manualmode.logging.SizeAppenderRestartTestCase* > * *org.jboss.as.test.manualmode.logging.SyslogIsNotAvailableDuringServerBootTestCase* > {{cd testsuite/manualmode/}} > {{mvn test -Dtest=org.jboss.as.test.manualmode.logging.* -Dsecurity.manager}} > {code} > org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper$ServerDeploymentException: java.lang.Exception: { > "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"logging-test.jar\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"logging-test.jar\".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment \"logging-test.jar\" > Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission \"(\"java.util.PropertyPermission\" \"jboss.bind.address\" \"read\")\" in code source \"(vfs:/content/logging-test.jar <no signer certificates>)\" of \"ModuleClassLoader for Module \"deployment.logging-test.jar\" from Service Module Loader\")"}, > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"logging-test.jar\".INSTALL"] > } > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134) > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123) > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85) > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42) > at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:55) > at org.wildfly.core.testrunner.ServerController.deploy(ServerController.java:92) > at org.jboss.as.test.manualmode.logging.AbstractLoggingTestCase.deploy(AbstractLoggingTestCase.java:197) > at org.jboss.as.test.manualmode.logging.Log4jAppenderTestCase.startContainer(Log4jAppenderTestCase.java:93) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8456) Protocols added to a fork of some channel won't show in JMX MBeans

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8456?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-8456: --------------------------------- Affects Version/s: 11.0.0.Alpha1 > Protocols added to a fork of some channel won't show in JMX MBeans > ------------------------------------------------------------------ > > Key: WFLY-8456 > URL: https://issues.jboss.org/browse/WFLY-8456 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Optional > > When defining a fork of some channel and adding a protocol to the protocol stack of that fork channel, the newly added protocol won't show up in JMX MBeans. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8456) Protocols added to a fork of some channel won't show in JMX MBeans

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8456?page=com.atlassian.jira.plugin.... ] Radoslav Husar moved JBEAP-9925 to WFLY-8456: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8456 (was: JBEAP-9925) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Clustering (was: Clustering) Affects Version/s: (was: 7.1.0.DR13) > Protocols added to a fork of some channel won't show in JMX MBeans > ------------------------------------------------------------------ > > Key: WFLY-8456 > URL: https://issues.jboss.org/browse/WFLY-8456 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Optional > > When defining a fork of some channel and adding a protocol to the protocol stack of that fork channel, the newly added protocol won't show up in JMX MBeans. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-149) Initializing the SyslogHandler should not do a permissions check when setting the output stream

by James Perkins (JIRA)

James Perkins created LOGMGR-149: ------------------------------------ Summary: Initializing the SyslogHandler should not do a permissions check when setting the output stream Key: LOGMGR-149 URL: https://issues.jboss.org/browse/LOGMGR-149 Project: JBoss Log Manager Issue Type: Bug Reporter: James Perkins The {{org.jboss.logmanager.handlers.SyslogHandler}} attempts to lazily connect to the syslog server. If running under a security manager and the user (deployment in WildFly's case) doesn't have {{control}} logging permissions, the write will fail. The failure is also swallowed which means there is no indication as to what the error is. Logs will just not appear on the syslog server. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2585) Servers in domain don't start if management interfaces are bound to all IPv4 addresses

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2585?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2585: ------------------------------------- Fix Version/s: 3.0.0.Beta12 > Servers in domain don't start if management interfaces are bound to all IPv4 addresses > -------------------------------------------------------------------------------------- > > Key: WFCORE-2585 > URL: https://issues.jboss.org/browse/WFCORE-2585 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.0.Beta11 > Reporter: Pavel Jelinek > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 3.0.0.Beta12 > > Attachments: host-controller.log, server-one.log > > > This is regression compared to EAP 7.0.0. > See attached logs server-one.log , host-controller.log > {code} > ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 2) MSC000001: Failed to start service jboss.server-boot-operations: org.jboss.msc.service.StartException in service jboss.server-boot-operations: java.net.ConnectException: WFLYPRT0053: Could not connect to remote://0.0.0.0:9999. The connection failed > at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:72) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote://0.0.0.0:9999. The connection failed > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:121) > at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259) > at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) > at org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:128) > at org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:110) > at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:68) > ... 4 more > Caused by: javax.security.sasl.SaslException: Authentication failed: none of the mechanisms presented by the server (JBOSS-LOCAL-USER, DIGEST-MD5) are supported > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:426) > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:241) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) > at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:567) > at ...asynchronous invocation...(Unknown Source) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:465) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:427) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:415) > at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:177) > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:113) > ... 9 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2585) Servers in domain don't start if management interfaces are bound to all IPv4 addresses

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2585?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-2585: ------------------------------------------ I scheduled this for Beta12 just so it's always on the current release issue list, but it's a Blocker for CR1 not Beta12. > Servers in domain don't start if management interfaces are bound to all IPv4 addresses > -------------------------------------------------------------------------------------- > > Key: WFCORE-2585 > URL: https://issues.jboss.org/browse/WFCORE-2585 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.0.Beta11 > Reporter: Pavel Jelinek > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 3.0.0.Beta12 > > Attachments: host-controller.log, server-one.log > > > This is regression compared to EAP 7.0.0. > See attached logs server-one.log , host-controller.log > {code} > ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 2) MSC000001: Failed to start service jboss.server-boot-operations: org.jboss.msc.service.StartException in service jboss.server-boot-operations: java.net.ConnectException: WFLYPRT0053: Could not connect to remote://0.0.0.0:9999. The connection failed > at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:72) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote://0.0.0.0:9999. The connection failed > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:121) > at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259) > at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) > at org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:128) > at org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:110) > at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:68) > ... 4 more > Caused by: javax.security.sasl.SaslException: Authentication failed: none of the mechanisms presented by the server (JBOSS-LOCAL-USER, DIGEST-MD5) are supported > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:426) > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:241) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) > at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:567) > at ...asynchronous invocation...(Unknown Source) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:465) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:427) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:415) > at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:177) > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:113) > ... 9 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
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 March 2017