October 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6271) SFSB methods can still be invoked after a calling transaction has rollbacked

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-6271?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-6271: -------------------------------------- Is this still an issue? > SFSB methods can still be invoked after a calling transaction has rollbacked > ---------------------------------------------------------------------------- > > Key: WFLY-6271 > URL: https://issues.jboss.org/browse/WFLY-6271 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7390) Demote the ERROR message about unavailable HTTP/2 on IBM JDK

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7390?page=com.atlassian.jira.plugin.... ] Stuart Douglas moved JBEAP-6654 to WFLY-7390: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7390 (was: JBEAP-6654) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Web (Undertow) (was: Web (Undertow)) Affects Version/s: (was: 7.1.0.DR1) > Demote the ERROR message about unavailable HTTP/2 on IBM JDK > ------------------------------------------------------------ > > Key: WFLY-7390 > URL: https://issues.jboss.org/browse/WFLY-7390 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > After discussing this in the QE team, we believe that this error message > bq. 2016-07-21 05:33:00,363 ERROR [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0071: Jetty ALPN not found. HTTP2 and SPDY are not available. Please make sure Jetty ALPN is on the boot class path. > > should be demoted to WARN to not cause too much panic with every server start. > Also, maybe we could enhance it to contain some instructions how to explicitly disable HTTP/2 in order to get rid of this message completely? -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1352) Embedded logged leaving filehandles open after stop

by Daniel Soukhov (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1352?page=com.atlassian.jira.plugi... ] Daniel Soukhov resolved WFCORE-1352. ------------------------------------ Resolution: Done > Embedded logged leaving filehandles open after stop > --------------------------------------------------- > > Key: WFCORE-1352 > URL: https://issues.jboss.org/browse/WFCORE-1352 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Environment: Windows > Reporter: Ken Wills > Assignee: James Perkins > Priority: Minor > Fix For: 3.0.0.Alpha1, 2.2.0.CR1 > > > After stop-embedded-server or stop-embedded-host-controller commands, logs in standalone/logs/ or domain/logs/ are still held open. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1845) Logging subsystem scans the CWD on server boot

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1845?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-1845: ---------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/1870, https://github.com/wildfly/wildfly-core/pull/1880 (was: https://github.com/wildfly/wildfly-core/pull/1870) > Logging subsystem scans the CWD on server boot > ---------------------------------------------- > > Key: WFCORE-1845 > URL: https://issues.jboss.org/browse/WFCORE-1845 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Affects Versions: 2.0.10.Final > Environment: OSX El Capitan, Oracle JDK 1.8.0_92 && 101, swarm 2016.8.1, WF 10.0.0.Final, WF-CORE 2.0.10.Final > Reporter: Brent Douglas > Assignee: James Perkins > Fix For: 3.0.0.Alpha11 > > > When booting the server from a directory where the subtree is large the server hangs for a long time. JStack shows that the logging subsystem is scanning the CWD. > Booting the server from the root dir of a maven parent project containing 2 subprojects, a swarm project and a small NPM subproject added 33s to the server boot time compared to stepping into the swarm project and booting it. > Stacktrace while the server is booting: > {noformat} > Thread 25859: (state = IN_NATIVE) > - sun.nio.fs.UnixNativeDispatcher.lstat0(long, sun.nio.fs.UnixFileAttributes) @bci=0 (Compiled frame; information may be imprecise) > - sun.nio.fs.UnixNativeDispatcher.lstat(sun.nio.fs.UnixPath, sun.nio.fs.UnixFileAttributes) @bci=10, line=300 (Compiled frame) > - sun.nio.fs.UnixFileAttributes.get(sun.nio.fs.UnixPath, boolean) @bci=22, line=72 (Compiled frame) > - sun.nio.fs.UnixFileAttributeViews$Basic.readAttributes() @bci=15, line=52 (Compiled frame) > - sun.nio.fs.UnixFileSystemProvider.readAttributes(java.nio.file.Path, java.lang.Class, java.nio.file.LinkOption[]) @bci=57, line=144 (Compiled frame) > - java.nio.file.Files.readAttributes(java.nio.file.Path, java.lang.Class, java.nio.file.LinkOption[]) @bci=7, line=1737 (Compiled frame) > - java.nio.file.FileTreeWalker.getAttributes(java.nio.file.Path, boolean) @bci=56, line=219 (Compiled frame) > - java.nio.file.FileTreeWalker.visit(java.nio.file.Path, boolean, boolean) @bci=3, line=276 (Compiled frame) > - java.nio.file.FileTreeWalker.next() @bci=134, line=372 (Compiled frame) > - java.nio.file.Files.walkFileTree(java.nio.file.Path, java.util.Set, int, java.nio.file.FileVisitor) @bci=256, line=2706 (Compiled frame) > - java.nio.file.Files.walkFileTree(java.nio.file.Path, java.nio.file.FileVisitor) @bci=9, line=2742 (Interpreted frame) > - org.jboss.as.logging.LoggingResource.findFiles(java.lang.String, org.jboss.dmr.ModelNode, boolean) @bci=47, line=251 (Interpreted frame) > - org.jboss.as.logging.LoggingResource.getChildrenNames(java.lang.String) @bci=37, line=157 (Interpreted frame) > - org.jboss.as.logging.LoggingResource.getChildren(java.lang.String) @bci=11, line=171 (Interpreted frame) > - org.jboss.as.controller.registry.AbstractModelResource$DelegateResource.getChildren(java.lang.String) @bci=5, line=362 (Interpreted frame) > - org.jboss.as.controller.registry.Resource$Tools.readModel(org.jboss.as.controller.PathAddress, org.jboss.as.controller.registry.Resource, int, org.jboss.as.controller.registry.ResourceFilter) @bci=99, line=289 (Interpreted frame) > - org.jboss.as.controller.registry.Resource$Tools.readModel(org.jboss.as.controller.registry.Resource, int, org.jboss.as.controller.registry.ResourceFilter) @bci=19, line=276 (Interpreted frame) > - org.jboss.as.controller.registry.Resource$Tools.readModel(org.jboss.as.controller.registry.Resource, int) @bci=5, line=262 (Interpreted frame) > - org.jboss.as.controller.registry.Resource$Tools.readModel(org.jboss.as.controller.PathAddress, org.jboss.as.controller.registry.Resource, int, org.jboss.as.controller.registry.ResourceFilter) @bci=189, line=291 (Interpreted frame) > - org.jboss.as.controller.registry.Resource$Tools.readModel(org.jboss.as.controller.registry.Resource, int, org.jboss.as.controller.registry.ResourceFilter) @bci=19, line=276 (Interpreted frame) > - org.jboss.as.controller.registry.Resource$Tools.readModel(org.jboss.as.controller.registry.Resource, int) @bci=5, line=262 (Interpreted frame) > - org.jboss.as.controller.registry.Resource$Tools.readModel(org.jboss.as.controller.registry.Resource) @bci=2, line=250 (Interpreted frame) > - org.jboss.as.controller.ModelControllerImpl.writeModel(org.jboss.as.controller.ModelControllerImpl$ManagementModelImpl, java.util.Set) @bci=19, line=769 (Interpreted frame) > - org.jboss.as.controller.OperationContextImpl.createPersistenceResource() @bci=17, line=519 (Interpreted frame) > - org.jboss.as.controller.AbstractOperationContext.executeDoneStage(org.jboss.dmr.ModelNode) @bci=22, line=708 (Interpreted frame) > - org.jboss.as.controller.AbstractOperationContext.processStages() @bci=277, line=680 (Interpreted frame) > - org.jboss.as.controller.AbstractOperationContext.executeOperation() @bci=27, line=370 (Interpreted frame) > - org.jboss.as.controller.OperationContextImpl.executeOperation() @bci=20, line=1344 (Interpreted frame) > - org.jboss.as.controller.ModelControllerImpl.boot(java.util.List, org.jboss.as.controller.client.OperationMessageHandler, org.jboss.as.controller.ModelController$OperationTransactionControl, boolean, org.jboss.as.controller.extension.MutableRootResourceRegistrationProvider, boolean, boolean) @bci=410, line=485 (Interpreted frame) > - org.jboss.as.controller.AbstractControllerService.boot(java.util.List, boolean, boolean, org.jboss.as.controller.extension.MutableRootResourceRegistrationProvider) @bci=16, line=387 (Interpreted frame) > - org.jboss.as.controller.AbstractControllerService.boot(java.util.List, boolean) @bci=7, line=349 (Interpreted frame) > - org.jboss.as.server.ServerService.boot(java.util.List, boolean) @bci=22, line=392 (Interpreted frame) > - org.jboss.as.server.ServerService.boot(org.jboss.as.controller.BootContext) @bci=907, line=365 (Interpreted frame) > - org.jboss.as.controller.AbstractControllerService$1.run() @bci=12, line=299 (Interpreted frame) > - java.lang.Thread.run() @bci=11, line=745 (Interpreted frame) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1352) Embedded logged leaving filehandles open after stop

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1352?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-1352: ---------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/1435 (was: https://github.com/wildfly/wildfly-core/pull/1435, https://github.com/wildfly/wildfly-core/pull/1880) > Embedded logged leaving filehandles open after stop > --------------------------------------------------- > > Key: WFCORE-1352 > URL: https://issues.jboss.org/browse/WFCORE-1352 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Environment: Windows > Reporter: Ken Wills > Assignee: James Perkins > Priority: Minor > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > > After stop-embedded-server or stop-embedded-host-controller commands, logs in standalone/logs/ or domain/logs/ are still held open. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1352) Embedded logged leaving filehandles open after stop

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1352?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-1352: ---------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/1435, https://github.com/wildfly/wildfly-core/pull/1880 (was: https://github.com/wildfly/wildfly-core/pull/1435) > Embedded logged leaving filehandles open after stop > --------------------------------------------------- > > Key: WFCORE-1352 > URL: https://issues.jboss.org/browse/WFCORE-1352 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Environment: Windows > Reporter: Ken Wills > Assignee: James Perkins > Priority: Minor > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > > After stop-embedded-server or stop-embedded-host-controller commands, logs in standalone/logs/ or domain/logs/ are still held open. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1352) Embedded logged leaving filehandles open after stop

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1352?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1352: ------------------------------------------ If this isn't broken in WildFly Core 2.2.0.Final (used in WildFly 10.1) then please file a separate issue. > Embedded logged leaving filehandles open after stop > --------------------------------------------------- > > Key: WFCORE-1352 > URL: https://issues.jboss.org/browse/WFCORE-1352 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Environment: Windows > Reporter: Ken Wills > Assignee: James Perkins > Priority: Minor > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > > After stop-embedded-server or stop-embedded-host-controller commands, logs in standalone/logs/ or domain/logs/ are still held open. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-893) Second security vault warning is displayed even if only one vault definition is present in the server configuration

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/SECURITY-893?page=com.atlassian.jira.plug... ] Ivo Studensky resolved SECURITY-893. ------------------------------------ Resolution: Done > Second security vault warning is displayed even if only one vault definition is present in the server configuration > ------------------------------------------------------------------------------------------------------------------- > > Key: SECURITY-893 > URL: https://issues.jboss.org/browse/SECURITY-893 > Project: PicketBox > Issue Type: Bug > Components: JBossSX, Security-SPI > Affects Versions: PicketBox_4_1_0.Beta2 > Reporter: Ivo Studensky > Assignee: Peter Skopek > > The BZ's description: > I have only one vault configured in the standalone.xml but I see following warning message in the server log file after login attempt (bindCredentials login module option uses a vaulted password): > {noformat} > 09:10:58,854 WARN [org.jboss.security] (http-/127.0.0.1:8080-1) PBOX000378: Attempt to create the second Security Vault [org.picketbox.plugins.vault.PicketBoxSecurityVault] is invalid. Only one Security Vault is supported. Change your configuration, please. > {noformat} > This issue is related to the previous fix for bz1055577, \[1\]. The problem needs to be fixed on EAP side in time of Security Subsystem configuration processing. Fix will be provided by bz1181457 \[2\]. > \[1\] https://bugzilla.redhat.com/show_bug.cgi?id=1055577 > \[2\] https://bugzilla.redhat.com/show_bug.cgi?id=1181457 -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1352) Embedded logged leaving filehandles open after stop

by Daniel Soukhov (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1352?page=com.atlassian.jira.plugi... ] Daniel Soukhov reopened WFCORE-1352: ------------------------------------ This issue still persists in eap 7.1.0DR7. > Embedded logged leaving filehandles open after stop > --------------------------------------------------- > > Key: WFCORE-1352 > URL: https://issues.jboss.org/browse/WFCORE-1352 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Environment: Windows > Reporter: Ken Wills > Assignee: James Perkins > Priority: Minor > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > > After stop-embedded-server or stop-embedded-host-controller commands, logs in standalone/logs/ or domain/logs/ are still held open. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7384) Removal of messaging-activemq's server stops Infinispan services

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-7384?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on WFLY-7384: ------------------------------------ [~jmesnil] This is expected. Infinispan cache-containers are installed as PASSIVE, which means that they will automatically start after their underlying transport starts. If the channel used by the transport is the same as used by messaging, then starting messaging (which starts the default channel) will trigger these cache containers to automatically start. After messaging is removed, and no other services are started that depend on these cache containers (e.g. a distributed web app, EJB deployment, JPA deployment, etc), then these services will automatically stop. You can close this. > Removal of messaging-activemq's server stops Infinispan services > ---------------------------------------------------------------- > > Key: WFLY-7384 > URL: https://issues.jboss.org/browse/WFLY-7384 > Project: WildFly > Issue Type: Bug > Components: Clustering, JMS > Reporter: Jeff Mesnil > Assignee: Paul Ferraro > Attachments: WFLY-7384.diff > > > This issue occurs after I fixed the issue for WFLY-7333 which ensures that all services related to a messaging-activemq server are stopped when the server is removed. > When I run the command to remove the server: > /subsystem=messaging-activemq/server=default:remove > I see logs in the app server about Infinispan services being stopped: > {noformat} > 09:28:46,344 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000080: Disconnecting JGroups channel server > 09:28:46,344 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000080: Disconnecting JGroups channel ejb > 09:28:46,344 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000080: Disconnecting JGroups channel hibernate > 09:28:46,344 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000080: Disconnecting JGroups channel web > 09:28:46,347 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000082: Stopping the RpcDispatcher for channel server > 09:28:46,347 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000082: Stopping the RpcDispatcher for channel ejb > 09:28:46,347 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000082: Stopping the RpcDispatcher for channel web > 09:28:46,347 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000082: Stopping the RpcDispatcher for channel hibernate > 09:28:46,381 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221002: Apache ActiveMQ Artemis Message Broker version 1.4.0 [c96316a7-9b4d-11e6-ab8c-b8f6b112daf7] stopped, uptime 18.904 seconds > {noformat} > There should be no reason than stopping the messaging server should stop such Infinispan services. The messaging-activemq subsystem has *no* dependency to Infinispan resources. > However both messaging-activemq and infinispan resources depends on JGroups resources. > I did a diff of the services dump before and after removing the messaging-activemq server (see attached file). > The Infinispan services are stopped as a consequence of stopping the jboss.messaging-activemq.default service. Before removing the server, this service is in this state: > {noformat} > Service \"jboss.messaging-activemq.default\" (class org.wildfly.extension.messaging.activemq.ActiveMQServerService) mode ACTIVE state UP (parent: jboss.as.server-controller) (dependencies: org.wildfly.management.jmx, org.wildfly.clustering.jgroups.default-channel-factory, jboss.outbound-socket-binding.http, jboss.binding.http, jboss.http-upgrade-registry.default, jboss.path.manager, jboss.security.security-domain.other) > {noformat} > The only relation between this messaging server and the Infinispan resources is that they depend on the org.wildfly.clustering.jgroups.default-channel-factory service. Before removing the messaging server, this service is in the state: > {noformat} > Service \"org.wildfly.clustering.jgroups.default-channel-factory\" (class org.jboss.msc.service.ValueService) mode PASSIVE state UP (parent: jboss.as.server-controller) (dependencies: org.wildfly.clustering.jgroups.channel-factory.ee) > {noformat} > After removing the messaging server, this service is in the state: > {noformat} > > Service \"org.wildfly.clustering.jgroups.default-channel-factory\" (class org.jboss.msc.service.ValueService) mode PASSIVE state DOWN (WAITING) (parent: jboss.as.server-controller) (dependencies: org.wildfly.clustering.jgroups.channel-factory.ee) > {noformat} > I am not sure to understand why and when removing the jboss.messaging-activemq.default implies to remove the org.wildfly.clustering.jgroups.default-channel-factory service but there is no reason that removing any messaging-activemq resources should impact the state of Infinispan services -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

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 October 2016