[JBoss JIRA] (WFCORE-2521) TLS between domain and host controllers does not work
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2521?page=com.atlassian.jira.plugi... ]
Darran Lofthouse moved JBEAP-9506 to WFCORE-2521:
-------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-2521 (was: JBEAP-9506)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Domain Management
Security
(was: Domain Management)
(was: Security)
Affects Version/s: (was: 7.1.0.DR10)
> TLS between domain and host controllers does not work
> -----------------------------------------------------
>
> Key: WFCORE-2521
> URL: https://issues.jboss.org/browse/WFCORE-2521
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Blocker
> Labels: domain-management, domain-mode, eap71_alpha, regression, ssl
> Fix For: 3.0.0.Beta8
>
>
> This is regression against EAP 7.0 . Customers relying on this feature won't be able to migrate to EAP 7.1.
> Working configuration of TLS between domain and host controller from EAP 7.0 (legacy) does not work on EAP 7.1 anymore.
> In server log there is this error:
> {code:title=server.log}
> [Host Controller] Caused by: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
> [Host Controller] at org.jboss.remoting3.remote.ClientConnectionOpenListener$StartTls.handleEvent(ClientConnectionOpenListener.java:527)
> [Host Controller] at org.jboss.remoting3.remote.ClientConnectionOpenListener$StartTls.handleEvent(ClientConnectionOpenListener.java:477)
> [Host Controller] at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> [Host Controller] at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
> [Host Controller] at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> [Host Controller] at org.xnio.nio.WorkerThread.run(WorkerThread.java:567)
> [Host Controller] at ...asynchronous invocation...(Unknown Source)
> [Host Controller] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:466)
> [Host Controller] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:437)
> [Host Controller] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:430)
> [Host Controller] at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:163)
> [Host Controller] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:119)
> [Host Controller] ... 9 more
> {code}
> See attached server.log for context log.
> Tests in wildfly-core covering this scenario are currently ignored:
> * SSLMasterSlaveOneWayTestCase is ignored by WFCORE-1978
> * SSLMasterSlaveTwoWayTestCase is ignored by WFCORE-2068
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2521) TLS between domain and host controllers does not work
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2521?page=com.atlassian.jira.plugi... ]
Darran Lofthouse updated WFCORE-2521:
-------------------------------------
Fix Version/s: 3.0.0.Beta8
> TLS between domain and host controllers does not work
> -----------------------------------------------------
>
> Key: WFCORE-2521
> URL: https://issues.jboss.org/browse/WFCORE-2521
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Blocker
> Labels: domain-management, domain-mode, eap71_alpha, regression, ssl
> Fix For: 3.0.0.Beta8
>
>
> This is regression against EAP 7.0 . Customers relying on this feature won't be able to migrate to EAP 7.1.
> Working configuration of TLS between domain and host controller from EAP 7.0 (legacy) does not work on EAP 7.1 anymore.
> In server log there is this error:
> {code:title=server.log}
> [Host Controller] Caused by: java.io.IOException: Client starting STARTTLS but channel doesn't support SSL
> [Host Controller] at org.jboss.remoting3.remote.ClientConnectionOpenListener$StartTls.handleEvent(ClientConnectionOpenListener.java:527)
> [Host Controller] at org.jboss.remoting3.remote.ClientConnectionOpenListener$StartTls.handleEvent(ClientConnectionOpenListener.java:477)
> [Host Controller] at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> [Host Controller] at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
> [Host Controller] at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> [Host Controller] at org.xnio.nio.WorkerThread.run(WorkerThread.java:567)
> [Host Controller] at ...asynchronous invocation...(Unknown Source)
> [Host Controller] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:466)
> [Host Controller] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:437)
> [Host Controller] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:430)
> [Host Controller] at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:163)
> [Host Controller] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:119)
> [Host Controller] ... 9 more
> {code}
> See attached server.log for context log.
> Tests in wildfly-core covering this scenario are currently ignored:
> * SSLMasterSlaveOneWayTestCase is ignored by WFCORE-1978
> * SSLMasterSlaveTwoWayTestCase is ignored by WFCORE-2068
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2520) expressions in quotes and brackets aren't resolved
by Alexey Loubyansky (JIRA)
Alexey Loubyansky created WFCORE-2520:
-----------------------------------------
Summary: expressions in quotes and brackets aren't resolved
Key: WFCORE-2520
URL: https://issues.jboss.org/browse/WFCORE-2520
Project: WildFly Core
Issue Type: Bug
Components: CLI
Affects Versions: 3.0.0.Beta7
Reporter: Alexey Loubyansky
Assignee: Alexey Loubyansky
Expressions (system properties, variables and command substitutions) aren't resolved and replaced during parsing of argument and parameter values in case the value is:
* quoted;
* a value of an attribute of a complex type;
* list item;
* in parenthesis.
E.g. op:add(param="$var")
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (DROOLS-1474) Activation.getObjectsDeep() should include "exists" elements too
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1474?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet commented on DROOLS-1474:
------------------------------------------
PR with reproducer (failing unit test) send: https://github.com/droolsjbpm/drools/pull/1140
> Activation.getObjectsDeep() should include "exists" elements too
> ----------------------------------------------------------------
>
> Key: DROOLS-1474
> URL: https://issues.jboss.org/browse/DROOLS-1474
> Project: Drools
> Issue Type: Enhancement
> Components: core engine
> Affects Versions: 7.0.0.Beta6
> Reporter: Geoffrey De Smet
> Assignee: Mario Fusco
>
> _Give them a finger and they'll want a hand. Give them a hand and they'll want an arm._ (dutch proverb)
> The Activation.getObjectDeeps() method introduced for DROOLS-1470 that also includes the accumulates elements, should also include the exists elements. For example:
> {code}
> when
> $c : Computer(id = "c1")
> exists Process(computer == $c)
> then ...
> {code}
> with this data
> {code}
> Computer c1;
> Computer c2;
> Computer c3;
> Process pA = new Process(c1);
> Process pB = new Process(c2);
> Process pC = new Process(c1);
> Process pD = new Process(c3);
> {code}
> gives this result
> {code}
> activation.getObjectsDeep() // includes c1, pA and pC.
> {code}
> The goal is to identify all objects that matched when this rule got fired. In a negative score rule, all those objects are to blame and by focusing to change any of those, it's more likely to improve the overall solution.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month