[Red Hat JIRA] (WFLY-14364) Service org.wildfly.network.outbound-socket-binding might not get installed
by Ivan Straka (Jira)
[ https://issues.redhat.com/browse/WFLY-14364?page=com.atlassian.jira.plugi... ]
Ivan Straka updated WFLY-14364:
-------------------------------
Attachment: standalone-ha.xml
> Service org.wildfly.network.outbound-socket-binding might not get installed
> ---------------------------------------------------------------------------
>
> Key: WFLY-14364
> URL: https://issues.redhat.com/browse/WFLY-14364
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 23.0.0.Beta1
> Reporter: Ivan Straka
> Assignee: Brian Stansberry
> Priority: Major
> Attachments: standalone-ha.xml
>
>
> First of all, I am not sure about the component, feel free to change it.
> *Issue:*
> When remoute outbound socket binding is added:
> {code:java}
> /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=node-3:add(host=localhost, port=7900)
> {code}
> I can not change fixed-source-port attribute
> {code:java}
> [standalone@localhost:9990 /] /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=node-3:write-attribute(name=fixed-source-port, value=false)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0155: 'socket-binding-ref' may not be null",
> "rolled-back" => true
> }
> {code}
> next try:
> {code:java}
> [standalone@localhost:9990 /] /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=node-3:write-attribute(name=fixed-source-port, value=false)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.ServiceNotFoundException: service org.wildfly.network.outbound-socket-binding.node-3 not found",
> "rolled-back" => true
> }
> 16:31:33,000 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("write-attribute") failed - address: ([
> ("socket-binding-group" => "standard-sockets"),
> ("remote-destination-outbound-socket-binding" => "node-3")
> ]): org.jboss.msc.service.ServiceNotFoundException: service org.wildfly.network.outbound-socket-binding.node-3 not found
> at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:663)
> at org.jboss.as.controller.OperationContextImpl$OperationContextServiceRegistry.getRequiredService(OperationContextImpl.java:2285)
> at org.jboss.as.server.services.net.OutboundSocketBindingWriteHandler.applyUpdateToRuntime(OutboundSocketBindingWriteHandler.java:75)
> at org.jboss.as.controller.AbstractWriteAttributeHandler$1.execute(AbstractWriteAttributeHandler.java:110)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:1005)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:744)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:468)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1415)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:431)
> at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:248)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:304)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:248)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:328)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:285)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:513)
> {code}
>
> However if the destination is used like the mail-smtp:
> {code:java}
> <subsystem xmlns="urn:jboss:domain:mail:4.0">
> <mail-session name="default" jndi-name="java:jboss/mail/Default">
> <smtp-server outbound-socket-binding-ref="mail-smtp"/>
> </mail-session>
> </subsystem>
> {code}
> the attribute can be changed. See the attached xml - node-1 vs node-2.
>
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 5 months
[Red Hat JIRA] (WFLY-14364) Service org.wildfly.network.outbound-socket-binding might not get installed
by Ivan Straka (Jira)
[ https://issues.redhat.com/browse/WFLY-14364?page=com.atlassian.jira.plugi... ]
Ivan Straka updated WFLY-14364:
-------------------------------
Description:
First of all, I am not sure about the component, feel free to change it.
*Issue:*
When remoute outbound socket binding is added:
{code:java}
/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=node-3:add(host=localhost, port=7900)
{code}
I can not change fixed-source-port attribute
{code:java}
[standalone@localhost:9990 /] /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=node-3:write-attribute(name=fixed-source-port, value=false)
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0155: 'socket-binding-ref' may not be null",
"rolled-back" => true
}
{code}
next try:
{code:java}
[standalone@localhost:9990 /] /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=node-3:write-attribute(name=fixed-source-port, value=false)
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.ServiceNotFoundException: service org.wildfly.network.outbound-socket-binding.node-3 not found",
"rolled-back" => true
}
16:31:33,000 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("write-attribute") failed - address: ([
("socket-binding-group" => "standard-sockets"),
("remote-destination-outbound-socket-binding" => "node-3")
]): org.jboss.msc.service.ServiceNotFoundException: service org.wildfly.network.outbound-socket-binding.node-3 not found
at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:663)
at org.jboss.as.controller.OperationContextImpl$OperationContextServiceRegistry.getRequiredService(OperationContextImpl.java:2285)
at org.jboss.as.server.services.net.OutboundSocketBindingWriteHandler.applyUpdateToRuntime(OutboundSocketBindingWriteHandler.java:75)
at org.jboss.as.controller.AbstractWriteAttributeHandler$1.execute(AbstractWriteAttributeHandler.java:110)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:1005)
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:744)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:468)
at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1415)
at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:431)
at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:248)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:304)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270)
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:248)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:328)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:285)
at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254)
at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158)
at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:513)
{code}
However if the destination is used like the mail-smtp:
{code:java}
<subsystem xmlns="urn:jboss:domain:mail:4.0">
<mail-session name="default" jndi-name="java:jboss/mail/Default">
<smtp-server outbound-socket-binding-ref="mail-smtp"/>
</mail-session>
</subsystem>
{code}
the attribute can be changed. See the attached xml - node-1 vs node-2.
was:
First of all, I am not sure about component, feel free to change it.
*Issue:*
When remoute outbound socket binding is added:
{code:java}
/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=node-3:add(host=localhost, port=7900)
{code}
I can not change fixed-source-port attribute
{code:java}
[standalone@localhost:9990 /] /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=node-3:write-attribute(name=fixed-source-port, value=false)
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0155: 'socket-binding-ref' may not be null",
"rolled-back" => true
}
{code}
next try:
{code:java}
[standalone@localhost:9990 /] /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=node-3:write-attribute(name=fixed-source-port, value=false)
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.ServiceNotFoundException: service org.wildfly.network.outbound-socket-binding.node-3 not found",
"rolled-back" => true
}
16:31:33,000 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("write-attribute") failed - address: ([
("socket-binding-group" => "standard-sockets"),
("remote-destination-outbound-socket-binding" => "node-3")
]): org.jboss.msc.service.ServiceNotFoundException: service org.wildfly.network.outbound-socket-binding.node-3 not found
at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:663)
at org.jboss.as.controller.OperationContextImpl$OperationContextServiceRegistry.getRequiredService(OperationContextImpl.java:2285)
at org.jboss.as.server.services.net.OutboundSocketBindingWriteHandler.applyUpdateToRuntime(OutboundSocketBindingWriteHandler.java:75)
at org.jboss.as.controller.AbstractWriteAttributeHandler$1.execute(AbstractWriteAttributeHandler.java:110)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:1005)
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:744)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:468)
at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1415)
at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:431)
at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:248)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:304)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270)
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:248)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:328)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:285)
at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254)
at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158)
at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:513)
{code}
However if the destination is used like the mail-smtp:
{code:java}
<subsystem xmlns="urn:jboss:domain:mail:4.0">
<mail-session name="default" jndi-name="java:jboss/mail/Default">
<smtp-server outbound-socket-binding-ref="mail-smtp"/>
</mail-session>
</subsystem>
{code}
the attribute can be changed. See the attached xml - node-1 vs node-2.
> Service org.wildfly.network.outbound-socket-binding might not get installed
> ---------------------------------------------------------------------------
>
> Key: WFLY-14364
> URL: https://issues.redhat.com/browse/WFLY-14364
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 23.0.0.Beta1
> Reporter: Ivan Straka
> Assignee: Brian Stansberry
> Priority: Major
>
> First of all, I am not sure about the component, feel free to change it.
> *Issue:*
> When remoute outbound socket binding is added:
> {code:java}
> /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=node-3:add(host=localhost, port=7900)
> {code}
> I can not change fixed-source-port attribute
> {code:java}
> [standalone@localhost:9990 /] /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=node-3:write-attribute(name=fixed-source-port, value=false)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0155: 'socket-binding-ref' may not be null",
> "rolled-back" => true
> }
> {code}
> next try:
> {code:java}
> [standalone@localhost:9990 /] /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=node-3:write-attribute(name=fixed-source-port, value=false)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.ServiceNotFoundException: service org.wildfly.network.outbound-socket-binding.node-3 not found",
> "rolled-back" => true
> }
> 16:31:33,000 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("write-attribute") failed - address: ([
> ("socket-binding-group" => "standard-sockets"),
> ("remote-destination-outbound-socket-binding" => "node-3")
> ]): org.jboss.msc.service.ServiceNotFoundException: service org.wildfly.network.outbound-socket-binding.node-3 not found
> at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:663)
> at org.jboss.as.controller.OperationContextImpl$OperationContextServiceRegistry.getRequiredService(OperationContextImpl.java:2285)
> at org.jboss.as.server.services.net.OutboundSocketBindingWriteHandler.applyUpdateToRuntime(OutboundSocketBindingWriteHandler.java:75)
> at org.jboss.as.controller.AbstractWriteAttributeHandler$1.execute(AbstractWriteAttributeHandler.java:110)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:1005)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:744)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:468)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1415)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:431)
> at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:248)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:304)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:248)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:328)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:285)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:513)
> {code}
>
> However if the destination is used like the mail-smtp:
> {code:java}
> <subsystem xmlns="urn:jboss:domain:mail:4.0">
> <mail-session name="default" jndi-name="java:jboss/mail/Default">
> <smtp-server outbound-socket-binding-ref="mail-smtp"/>
> </mail-session>
> </subsystem>
> {code}
> the attribute can be changed. See the attached xml - node-1 vs node-2.
>
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 5 months
[Red Hat JIRA] (WFLY-14364) Service org.wildfly.network.outbound-socket-binding might not get installed
by Ivan Straka (Jira)
Ivan Straka created WFLY-14364:
----------------------------------
Summary: Service org.wildfly.network.outbound-socket-binding might not get installed
Key: WFLY-14364
URL: https://issues.redhat.com/browse/WFLY-14364
Project: WildFly
Issue Type: Bug
Components: Server
Affects Versions: 23.0.0.Beta1
Reporter: Ivan Straka
Assignee: Brian Stansberry
First of all, I am not sure about component, feel free to change it.
*Issue:*
When remoute outbound socket binding is added:
{code:java}
/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=node-3:add(host=localhost, port=7900)
{code}
I can not change fixed-source-port attribute
{code:java}
[standalone@localhost:9990 /] /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=node-3:write-attribute(name=fixed-source-port, value=false)
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0155: 'socket-binding-ref' may not be null",
"rolled-back" => true
}
{code}
next try:
{code:java}
[standalone@localhost:9990 /] /socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=node-3:write-attribute(name=fixed-source-port, value=false)
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.ServiceNotFoundException: service org.wildfly.network.outbound-socket-binding.node-3 not found",
"rolled-back" => true
}
16:31:33,000 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("write-attribute") failed - address: ([
("socket-binding-group" => "standard-sockets"),
("remote-destination-outbound-socket-binding" => "node-3")
]): org.jboss.msc.service.ServiceNotFoundException: service org.wildfly.network.outbound-socket-binding.node-3 not found
at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:663)
at org.jboss.as.controller.OperationContextImpl$OperationContextServiceRegistry.getRequiredService(OperationContextImpl.java:2285)
at org.jboss.as.server.services.net.OutboundSocketBindingWriteHandler.applyUpdateToRuntime(OutboundSocketBindingWriteHandler.java:75)
at org.jboss.as.controller.AbstractWriteAttributeHandler$1.execute(AbstractWriteAttributeHandler.java:110)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:1005)
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:744)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:468)
at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1415)
at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:431)
at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:248)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:304)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270)
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:248)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:138)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:162)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:158)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:328)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:285)
at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254)
at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:158)
at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:513)
{code}
However if the destination is used like the mail-smtp:
{code:java}
<subsystem xmlns="urn:jboss:domain:mail:4.0">
<mail-session name="default" jndi-name="java:jboss/mail/Default">
<smtp-server outbound-socket-binding-ref="mail-smtp"/>
</mail-session>
</subsystem>
{code}
the attribute can be changed. See the attached xml - node-1 vs node-2.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 5 months
[Red Hat JIRA] (WFLY-14363) Split full galleon-feature-pack module
by Jean Francois Denise (Jira)
Jean Francois Denise created WFLY-14363:
-------------------------------------------
Summary: Split full galleon-feature-pack module
Key: WFLY-14363
URL: https://issues.redhat.com/browse/WFLY-14363
Project: WildFly
Issue Type: Task
Components: Build System
Reporter: Jean Francois Denise
Assignee: Jean Francois Denise
In order to allow for building ee FP from a separate repository, there is a need to split the ee-feature-pack/galleon-feature-pack into 2 modules. One to contain the content (configs, ...), one to build the FP.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 5 months
[Red Hat JIRA] (WFLY-14363) Split full galleon-feature-pack module
by Jean Francois Denise (Jira)
[ https://issues.redhat.com/browse/WFLY-14363?page=com.atlassian.jira.plugi... ]
Jean Francois Denise updated WFLY-14363:
----------------------------------------
Description:
In order to allow for building full FP from a separate repository, there is a need to split the galleon-feature-pack into 2 modules. One to contain the content (configs, ...), one to build the FP.
was:
In order to allow for building ee FP from a separate repository, there is a need to split the ee-feature-pack/galleon-feature-pack into 2 modules. One to contain the content (configs, ...), one to build the FP.
> Split full galleon-feature-pack module
> --------------------------------------
>
> Key: WFLY-14363
> URL: https://issues.redhat.com/browse/WFLY-14363
> Project: WildFly
> Issue Type: Task
> Components: Build System
> Reporter: Jean Francois Denise
> Assignee: Jean Francois Denise
> Priority: Major
>
> In order to allow for building full FP from a separate repository, there is a need to split the galleon-feature-pack into 2 modules. One to contain the content (configs, ...), one to build the FP.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 5 months
[Red Hat JIRA] (WFLY-14362) Split ee galleon-feature-pack module
by Jean Francois Denise (Jira)
Jean Francois Denise created WFLY-14362:
-------------------------------------------
Summary: Split ee galleon-feature-pack module
Key: WFLY-14362
URL: https://issues.redhat.com/browse/WFLY-14362
Project: WildFly
Issue Type: Task
Components: Build System
Reporter: Jean Francois Denise
Assignee: Jean Francois Denise
In order to allow for building ee FP from a separate repository, there is a need to split the ee-feature-pack/galleon-feature-pack into 2 modules. One to contain the content (configs, ...), one to build the FP.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 5 months
[Red Hat JIRA] (DROOLS-5968) Propagate value type inside MiningField
by Gabriele Cardosi (Jira)
Gabriele Cardosi created DROOLS-5968:
----------------------------------------
Summary: Propagate value type inside MiningField
Key: DROOLS-5968
URL: https://issues.redhat.com/browse/DROOLS-5968
Project: Drools
Issue Type: Task
Reporter: Gabriele Cardosi
Assignee: Gabriele Cardosi
org.kie.pmml.api.models.MiningField will be used for OpenAPI generation, but currently it lack a needed info, i.e. the value type.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 5 months