[JBoss JIRA] (WFLY-8977) Mdb Delivery-group is not working
by Flavia Rainone (JIRA)
Flavia Rainone created WFLY-8977:
------------------------------------
Summary: Mdb Delivery-group is not working
Key: WFLY-8977
URL: https://issues.jboss.org/browse/WFLY-8977
Project: WildFly
Issue Type: Bug
Components: EJB
Reporter: Flavia Rainone
Assignee: Flavia Rainone
Delivery-group feature is broken.
Disabling an active delivery-group does not affect delivery of messages in the server.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFLY-8975) Can't restart domain master host with slave attached
by Matthew Casperson (JIRA)
Matthew Casperson created WFLY-8975:
---------------------------------------
Summary: Can't restart domain master host with slave attached
Key: WFLY-8975
URL: https://issues.jboss.org/browse/WFLY-8975
Project: WildFly
Issue Type: Bug
Affects Versions: 11.0.0.Alpha1
Reporter: Matthew Casperson
Assignee: Jason Greene
With a domain controller started on a host called master and no slaves attached, I can restart the host master with the command
*./jboss-cli.ps1 -c --command="/host=master:shutdown(restart=true)"*
over and over with no issues.
Once a domain slave is attached, I often will not be able to restart the host master with the same command. It will shutdown, but not restart. The host master does seem to occasionally restart as expected, but not always.
The output from the domain controller is this:
{code:java}
Registered remote slave host "desktop-p010d77", JBoss WildFly Full 11.0.0.Alpha1 (WildFly 3.0.0.Beta11)
[Host Controller] 14:14:19,294 INFO [org.jboss.as.host.controller] (management-handler-thread - 1) WFLYHC0180: Shutting
down in response to management operation 'shutdown'
14:14:19,300 INFO [org.jboss.as.process] (Thread-15) WFLYPC0017: Shutting down process controller
14:14:19,301 INFO [org.jboss.as.process.Host Controller.status] (Thread-15) WFLYPC0019: Stopping process 'Host Controll
er'
[Host Controller] 14:14:19,317 INFO [org.jboss.as.host.controller] (Host Controller Service Threads - 40) WFLYHC0024: S
topping server server-one
[Host Controller] 14:14:19,320 INFO [org.jboss.as.host.controller] (Host Controller Service Threads - 40) WFLYHC0024: S
topping server server-two
14:14:19,320 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 4) WFLYPC0019: Stopping
process 'Server:server-one'
14:14:19,321 INFO [org.jboss.as.process.Server:server-two.status] (ProcessController-threads - 4) WFLYPC0019: Stopping
process 'Server:server-two'
[Server:server-one] 14:14:19,322 INFO [org.jboss.as.server] (main) WFLYSRV0240: ProcessController has signalled to shut
down; shutting down
[Server:server-two] 14:14:19,324 INFO [org.jboss.as.server] (main) WFLYSRV0240: ProcessController has signalled to shut
down; shutting down
[Server:server-one] 14:14:19,343 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0
010: Unbound data source [java:jboss/datasources/ExampleDS]
[Server:server-one] 14:14:19,351 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-5) WFLYMSGAMQ000
6: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
[Server:server-one] 14:14:19,354 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0019: Host defaul
t-host stopping
[Server:server-one] 14:14:19,357 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0011: Unbound
JCA ConnectionFactory [java:/JmsXA]
[Server:server-two] 14:14:19,362 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0
010: Unbound data source [java:jboss/datasources/ExampleDS]
[Server:server-one] 14:14:19,358 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0008: Undertow HT
TPS listener https suspending
[Server:server-one] 14:14:19,360 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0007: Undertow HT
TPS listener https stopped, was bound to 127.0.0.1:8443
[Server:server-two] 14:14:19,367 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-3) WFLYMSGAMQ000
6: Unbound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
[Server:server-one] 14:14:19,364 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 67) WFLY
MSGAMQ0006: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
[Server:server-two] 14:14:19,370 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-8) WFLYJCA0011: Unbound
JCA ConnectionFactory [java:/JmsXA]
[Server:server-two] 14:14:19,371 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0008: Undertow HT
TPS listener https suspending
[Server:server-two] 14:14:19,372 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0007: Undertow HT
TPS listener https stopped, was bound to 127.0.0.1:8593
[Server:server-two] 14:14:19,374 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 35) WFLY
MSGAMQ0006: Unbound messaging object to jndi name java:/ConnectionFactory
[Server:server-one] 14:14:19,392 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0019: Sto
pped Driver service with driver-name = h2
[Server:server-two] 14:14:19,407 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0019: Host defaul
t-host stopping
[Server:server-two] 14:14:19,414 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0019: Sto
pped Driver service with driver-name = h2
[Server:server-one] 14:14:19,426 INFO [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 74) AMQ151003: res
ource adaptor stopped
[Server:server-two] 14:14:19,437 INFO [org.apache.activemq.artemis.ra] (ServerService Thread Pool -- 73) AMQ151003: res
ource adaptor stopped
[Server:server-one] 14:14:19,475 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 74) AMQ22
1002: Apache ActiveMQ Artemis Message Broker version 1.5.3.jbossorg-003 [3d9fbbfb-5620-11e7-9672-9cb6d0de7033] stopped,
uptime 3 minutes
[Server:server-one] 14:14:19,475 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0008: Undertow HT
TP listener default suspending
[Server:server-one] 14:14:19,476 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0007: Undertow HT
TP listener default stopped, was bound to 127.0.0.1:8080
[Server:server-one] 14:14:19,478 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0004: Undertow 1.
4.11.Final stopping
[Host Controller] 14:14:19,488 INFO [org.jboss.as.host.controller] (management task-3) WFLYHC0027: Unregistering server
server-one
[Server:server-two] 14:14:19,491 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 73) AMQ22
1002: Apache ActiveMQ Artemis Message Broker version 1.5.3.jbossorg-003 [3da40166-5620-11e7-9b85-9cb6d0de7033] stopped,
uptime 3 minutes
[Server:server-two] 14:14:19,493 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0008: Undertow HT
TP listener default suspending
[Server:server-two] 14:14:19,495 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow HT
TP listener default stopped, was bound to 127.0.0.1:8230
[Server:server-two] 14:14:19,498 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0004: Undertow 1.
4.11.Final stopping
[Host Controller] 14:14:19,507 INFO [org.jboss.as.host.controller] (management task-5) WFLYHC0027: Unregistering server
server-two
[Server:server-one] 14:14:19,510 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0050: WildFly Full 11.0.0.Alpha1 (
WildFly Core 3.0.0.Beta11) stopped in 174ms
[Server:server-two] 14:14:19,518 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Full 11.0.0.Alpha1 (
WildFly Core 3.0.0.Beta11) stopped in 159ms
14:14:19,883 INFO [org.jboss.as.process.Server:server-one.status] (reaper for Server:server-one) WFLYPC0011: Process 'S
erver:server-one' finished with an exit status of 0
[Host Controller] 14:14:19,884 INFO [org.jboss.as.host.controller] (ProcessControllerConnection-thread - 2) WFLYHC0027:
Unregistering server server-one
14:14:19,903 INFO [org.jboss.as.process.Server:server-two.status] (reaper for Server:server-two) WFLYPC0011: Process 'S
erver:server-two' finished with an exit status of 0
[Host Controller] 14:14:19,904 INFO [org.jboss.as.host.controller] (ProcessControllerConnection-thread - 2) WFLYHC0027:
Unregistering server server-two
[Host Controller] 14:14:19,906 WARN [org.jboss.as.domain.controller] (MSC service thread 1-1) WFLYHC0030: Connection to
remote host "desktop-p010d77" closed unexpectedly
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFLY-8974) RBAC, There are missing access-constraint for attributes which referencing elytron capabilities.
by Stefan Guilhen (JIRA)
[ https://issues.jboss.org/browse/WFLY-8974?page=com.atlassian.jira.plugin.... ]
Stefan Guilhen updated WFLY-8974:
---------------------------------
Description:
According to RFE EAP7-548 there must be set access-constraint where are referenced elytron capabilities.
6 places were found where access-constraint missing.
{code}
/subsystem=undertow:read-resource-description(recursive=true)
{code}
There is http-invoker, attr http-authentication-factory with org.wildfly.security.http-authentication-factory capability.
{code}
/subsystem=datasources:read-resource-description(recursive=true)
{code}
There is xa-data-source, attr recovery-authentication-context with org.wildfly.security.authentication-context capability.
{code}
/subsystem=ejb3:read-resource-description(recursive=true)
{code}
There is identity, attr outflow-security-domains with org.wildfly.security.security-domain capability.
{code}
/core-service=management/management-interface=http-interface:read-resource-description(recursive=true)
{code}
There is sasl-authentication-factory with org.wildfly.security.sasl-authentication-factory capability.
{code}
/deployment=test:read-resource-description(recursive=true)
{code}
There is xa-data-source, attr recovery-authentication-context with org.wildfly.security.authentication-context capability
and there is same problem in subdeployment resource too.
> RBAC, There are missing access-constraint for attributes which referencing elytron capabilities.
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-8974
> URL: https://issues.jboss.org/browse/WFLY-8974
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Stefan Guilhen
> Assignee: Stefan Guilhen
> Priority: Critical
>
> According to RFE EAP7-548 there must be set access-constraint where are referenced elytron capabilities.
> 6 places were found where access-constraint missing.
> {code}
> /subsystem=undertow:read-resource-description(recursive=true)
> {code}
> There is http-invoker, attr http-authentication-factory with org.wildfly.security.http-authentication-factory capability.
> {code}
> /subsystem=datasources:read-resource-description(recursive=true)
> {code}
> There is xa-data-source, attr recovery-authentication-context with org.wildfly.security.authentication-context capability.
> {code}
> /subsystem=ejb3:read-resource-description(recursive=true)
> {code}
> There is identity, attr outflow-security-domains with org.wildfly.security.security-domain capability.
> {code}
> /core-service=management/management-interface=http-interface:read-resource-description(recursive=true)
> {code}
> There is sasl-authentication-factory with org.wildfly.security.sasl-authentication-factory capability.
> {code}
> /deployment=test:read-resource-description(recursive=true)
> {code}
> There is xa-data-source, attr recovery-authentication-context with org.wildfly.security.authentication-context capability
> and there is same problem in subdeployment resource too.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFLY-8973) RBAC, Security subsystem contains attributes with capabilities which don't set access-constraint.
by Stefan Guilhen (JIRA)
[ https://issues.jboss.org/browse/WFLY-8973?page=com.atlassian.jira.plugin.... ]
Stefan Guilhen updated WFLY-8973:
---------------------------------
Description:
Security subsystem contains attributes with capabilities which don't set access-constraint.
How to reproduce:
{code}
/subsystem=security:read-resource-description(recursive=true)
{code}
Resources elytron-realm, elytron-key-store, elytron-trust-store, elytron-key-manager and elytron-trust-manager all contain attributes that reference a JAAS security domain and that are missing the SECURITY_DOMAIN_REF constraint.
was:
Security subsystem contains attributes with capabilities which don't set access-constraint.
All of them have Elytron compatibility capability and I expect there some access constraint too.
How to reproduce:
{code}
/subsystem=security:read-resource-description(recursive=true)
{code}
Resources elytron-realm, elytron-key-store, elytron-trust-store, elytron-key-manager and elytron-trust-manager all contain attributes that reference a JAAS security domain and that are missing the SECURITY_DOMAIN_REF constraint.
> RBAC, Security subsystem contains attributes with capabilities which don't set access-constraint.
> -------------------------------------------------------------------------------------------------
>
> Key: WFLY-8973
> URL: https://issues.jboss.org/browse/WFLY-8973
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Stefan Guilhen
> Assignee: Stefan Guilhen
>
> Security subsystem contains attributes with capabilities which don't set access-constraint.
> How to reproduce:
> {code}
> /subsystem=security:read-resource-description(recursive=true)
> {code}
> Resources elytron-realm, elytron-key-store, elytron-trust-store, elytron-key-manager and elytron-trust-manager all contain attributes that reference a JAAS security domain and that are missing the SECURITY_DOMAIN_REF constraint.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFLY-8973) RBAC, Security subsystem contains attributes with capabilities which don't set access-constraint.
by Stefan Guilhen (JIRA)
[ https://issues.jboss.org/browse/WFLY-8973?page=com.atlassian.jira.plugin.... ]
Stefan Guilhen updated WFLY-8973:
---------------------------------
Priority: Critical (was: Major)
> RBAC, Security subsystem contains attributes with capabilities which don't set access-constraint.
> -------------------------------------------------------------------------------------------------
>
> Key: WFLY-8973
> URL: https://issues.jboss.org/browse/WFLY-8973
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Stefan Guilhen
> Assignee: Stefan Guilhen
> Priority: Critical
>
> Security subsystem contains attributes with capabilities which don't set access-constraint.
> How to reproduce:
> {code}
> /subsystem=security:read-resource-description(recursive=true)
> {code}
> Resources elytron-realm, elytron-key-store, elytron-trust-store, elytron-key-manager and elytron-trust-manager all contain attributes that reference a JAAS security domain and that are missing the SECURITY_DOMAIN_REF constraint.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFLY-8973) RBAC, Security subsystem contains attributes with capabilities which don't set access-constraint.
by Stefan Guilhen (JIRA)
[ https://issues.jboss.org/browse/WFLY-8973?page=com.atlassian.jira.plugin.... ]
Stefan Guilhen updated WFLY-8973:
---------------------------------
Description:
Security subsystem contains attributes with capabilities which don't set access-constraint.
All of them have Elytron compatibility capability and I expect there some access constraint too.
How to reproduce:
{code}
/subsystem=security:read-resource-description(recursive=true)
{code}
Resources elytron-realm, elytron-key-store, elytron-trust-store, elytron-key-manager and elytron-trust-manager all contain attributes that reference a JAAS security domain and that are missing the SECURITY_DOMAIN_REF constraint.
> RBAC, Security subsystem contains attributes with capabilities which don't set access-constraint.
> -------------------------------------------------------------------------------------------------
>
> Key: WFLY-8973
> URL: https://issues.jboss.org/browse/WFLY-8973
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management, Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Stefan Guilhen
> Assignee: Stefan Guilhen
>
> Security subsystem contains attributes with capabilities which don't set access-constraint.
> All of them have Elytron compatibility capability and I expect there some access constraint too.
> How to reproduce:
> {code}
> /subsystem=security:read-resource-description(recursive=true)
> {code}
> Resources elytron-realm, elytron-key-store, elytron-trust-store, elytron-key-manager and elytron-trust-manager all contain attributes that reference a JAAS security domain and that are missing the SECURITY_DOMAIN_REF constraint.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years