[JBoss JIRA] (WFCORE-1752) The deployment-overlay command fails to redeploy affected deployments
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1752?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-1752:
------------------------------------------
I don't have a good answer, just wanted to comment on this:
"I am trying to keep the --deployments option to reference deployment names and do the conversion to the runtime name internally when needed (mainly when adding the deployment to the overlay). The deployment name seems to me what people are really using to reference deployment (If I am wrong just say it). "
The meaning of this CLI parameter needs to align with the meaning of what is stored in the server side model and persisted. If they have 2 wars foo-1.war and foo-2.war installed, both with runtime name foo.war, and they say --deployments=foo-1.war they are going to actually be affecting both deployments.
I think having the server side model use runtime-name was a mistake, but we are kind of stuck with it.
Can execution of redeploy-affected be moved to the server side? The server will have all the data (including deployments added/removed in the batch) by the time it needs to do any changes to the service container.
> The deployment-overlay command fails to redeploy affected deployments
> ---------------------------------------------------------------------
>
> Key: WFCORE-1752
> URL: https://issues.jboss.org/browse/WFCORE-1752
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 3.0.0.Alpha5
> Reporter: ehsavoie Hugonnet
> Assignee: Jean-Francois Denise
>
> The deployment-overlay command fails to redeploy affected deployments if the runtime-name isn't the same as the deployment name. Since affected deployment to be redeployed should be running the couple runtime-name + enabled == true should be used to define which deployments are affected instead of using the deployment name since the name used in overlay is the runtime-name
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (DROOLS-1404) Alpha node not shared with static function evaluation
by Matteo Mortari (JIRA)
Matteo Mortari created DROOLS-1404:
--------------------------------------
Summary: Alpha node not shared with static function evaluation
Key: DROOLS-1404
URL: https://issues.jboss.org/browse/DROOLS-1404
Project: Drools
Issue Type: Bug
Components: core engine
Reporter: Matteo Mortari
Assignee: Matteo Mortari
The following code when placed in Misc2Test exhibit the problem
{code:java}
public static class TestStaticUtils {
public static int return1() {
return 1;
}
}
@Test
public void testCheck2() {
String drl = "package c;\n" + // <<- keep this package name
"\n" +
"import " + TestObject.class.getCanonicalName() + "\n" +
"\n" +
"rule fileBrule1 when\n" +
" TestObject(value == 1)\n" +
"then\n" +
"end"
;
String drl2 = "package iTransiberian;\n" + // <<- keep this package name
"\n" +
"import " + TestObject.class.getCanonicalName() + "\n" +
"import " + TestStaticUtils.class.getCanonicalName() + "\n" +
"\n" +
"rule fileArule1 when\n" +
" $t : String()\n" +
" TestObject(value == TestStaticUtils.return1() )\n" +
"then\n" +
"end\n"+
"rule fileArule2 when\n" + // <<- keep this rule
" $t : String()\n" +
" TestObject(value == 0 )\n" +
"then\n" +
"end\n" +
""
;
KieSession kieSession = new KieHelper()
.addContent(drl2, ResourceType.DRL)
.addContent(drl, ResourceType.DRL)
.build().newKieSession();
ReteDumper.dumpRete(kieSession);
System.out.println(drl);
System.out.println(drl2);
kieSession.addEventListener(new DebugAgendaEventListener());
kieSession.insert("test");
kieSession.insert(new TestObject(1));
assertEquals(2, kieSession.fireAllRules() );
}
{code}
Conducting further analysis...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JGRP-2152) ASYM_ENCRYPT failure on Wildfly 10.1.0
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/JGRP-2152?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz edited comment on JGRP-2152 at 1/12/17 2:50 PM:
--------------------------------------------------------------------
I added an ASYM_ENCRYT layer to the server configuration for the clustering testsuite and turned on TRACE logging for the ASYM_ENCRYPT protocol. Here is the stack:
{noformat}
<stack name="tcp">
<transport type="TCP" socket-binding="jgroups-tcp"/>
<protocol type="MPING" socket-binding="jgroups-mping">
<property name="ip_ttl">0</property>
</protocol>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/>
<protocol type="FD"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="ASYM_ENCRYPT">
<property name="encrypt_entire_message">true</property>
<property name="asym_keylength">512</property>
<property name="asym_algorithm">RSA</property>
</protocol>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="MFC"/>
<protocol type="FRAG2"/>
</stack>
{noformat}
The clustering tests pass with the old config and fail with the new config. One such test, CdiFailoverTestCase, fails with the same error message as in this issue. In this test, two servers, node-0 and node-1, are started. Then node-1 is stopped and then restarted, followed by node-0 which is stopped and then restarted. Looking at the logs, encryption seems to be progressing normally until the time at which node-1 is restarted. Then messages start getting enqueued and the cipher is reported as being null.
I am attaching the file containing the test case output, which includes logs from both servers.
So this might be a JGroups issue.
was (Author: rachmato):
I added an ASYM_ENCRYT layer to the server configuration for the clustering testsuite and turned on TRACE logging for the ASYM_ENCRYPT protocol. Here is the stack:
{noformat}
<stack name="tcp">
<transport type="TCP" socket-binding="jgroups-tcp"/>
<protocol type="MPING" socket-binding="jgroups-mping">
<property name="ip_ttl">0</property>
</protocol>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/>
<protocol type="FD"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="ASYM_ENCRYPT">
<property name="encrypt_entire_message">true</property>
<property name="asym_keylength">512</property>
<property name="asym_algorithm">RSA</property>
</protocol>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="MFC"/>
<protocol type="FRAG2"/>
</stack>
{noformat}
The clustering tests pass with the old config and fail with the new config. One such test, CdiFailoverTestCase, fails with the same error message as in this issue. In this test, two servers, node-0 and node-1, are started. Then node-1 is stopped and then restarted, followed by node-0 which is stopped and then restarted. Looking at the logs, encryption seems to be progressing normally until the time at which node-1 is restarted. Then messages start getting enqueued and the cipher is reported as being null.
I am attaching the files containing the test case output, which includes logs from both servers.
So this might be a JGroups issue.
> ASYM_ENCRYPT failure on Wildfly 10.1.0
> --------------------------------------
>
> Key: JGRP-2152
> URL: https://issues.jboss.org/browse/JGRP-2152
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.10
> Reporter: Matt Wringe
> Assignee: Bela Ban
> Fix For: 4.0, 3.6.13
>
> Attachments: hawkular-metrics-1.log, hawkular-metrics-2.log, org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase-SYNC-tcp-output.txt, standalone.xml
>
>
> Using ASYM_ENCRYPT on Wildfly 10.1.0 seems to be broken.
> I am using the parameters for ASYM_ENCRYPT specified in http://www.jgroups.org/manual/index.html#Security
> Note: running with SYM_ENCRYPT doesn't cause any issues and it works fine with my setup. Its only ASYM_ENCRYPT which is currently failing.
> Note: running this on EAP fails in a similar manner.
> Eg:
> <protocol type="ASYM_ENCRYPT">
> <property name="encrypt_entire_message">true</property>
> <property name="sym_keylength">128</property>
> <property name="sym_algorithm">AES/ECB/PKCS5Padding</property>
> <property name="asym_keylength">512</property>
> <property name="asym_algorithm">RSA</property>
> </protocol>
> If I run a single instance, then I don't see any problems appear in the logs. Its when I start a second instance that I start to see errors about unrecognised ciphers and timeouts.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JGRP-2152) ASYM_ENCRYPT failure on Wildfly 10.1.0
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/JGRP-2152?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz edited comment on JGRP-2152 at 1/12/17 2:49 PM:
--------------------------------------------------------------------
I added an ASYM_ENCRYT layer to the server configuration for the clustering testsuite and turned on TRACE logging for the ASYM_ENCRYPT protocol. Here is the stack:
{noformat}
<stack name="tcp">
<transport type="TCP" socket-binding="jgroups-tcp"/>
<protocol type="MPING" socket-binding="jgroups-mping">
<property name="ip_ttl">0</property>
</protocol>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/>
<protocol type="FD"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="ASYM_ENCRYPT">
<property name="encrypt_entire_message">true</property>
<property name="asym_keylength">512</property>
<property name="asym_algorithm">RSA</property>
</protocol>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="MFC"/>
<protocol type="FRAG2"/>
</stack>
{noformat}
The clustering tests pass with the old config and fail with the new config. One such test, CdiFailoverTestCase, fails with the same error message as in this issue. In this test, two servers, node-0 and node-1, are started. Then node-1 is stopped and then restarted, followed by node-0 which is stopped and then restarted. Looking at the logs, encryption seems to be progressing normally until the time at which node-1 is restarted. Then messages start getting enqueued and the cipher is reported as being null.
I am attaching the files containing the test case output, which includes logs from both servers.
So this might be a JGroups issue.
was (Author: rachmato):
I added an ASYM_ENCRYT layer to the server configuration for the clustering testsuite and turned on TRACE logging for the ASYM_ENCRYPT protocol. Here is the stack:
{noformat}
<stack name="tcp">
<transport type="TCP" socket-binding="jgroups-tcp"/>
<protocol type="MPING" socket-binding="jgroups-mping">
<property name="ip_ttl">0</property>
</protocol>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/>
<protocol type="FD"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="ASYM_ENCRYPT">
<property name="encrypt_entire_message">true</property>
<property name="asym_keylength">512</property>
<property name="asym_algorithm">RSA</property>
</protocol>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="MFC"/>
<protocol type="FRAG2"/>
</stack>
{noformat}
The clustering tests pass with the old config and fail with the new config. One such test, CdiFailoverTestCase, fails with the same error message as in this issue. In this test, two servers, node-0 and node-1, are started. Then node-1 is stopped and then restarted, followed by node-0 which is stolled and then retsrated. Looking at the logs, encryption seems to be progressing normally until the time at which node-1 is restarted. Then messages start getting enqueued and the cipher is reported as being null.
I am attaching the files containing the test case output, which includes logs from both servers.
So this might be a JGroups issue.
> ASYM_ENCRYPT failure on Wildfly 10.1.0
> --------------------------------------
>
> Key: JGRP-2152
> URL: https://issues.jboss.org/browse/JGRP-2152
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.10
> Reporter: Matt Wringe
> Assignee: Bela Ban
> Fix For: 4.0, 3.6.13
>
> Attachments: hawkular-metrics-1.log, hawkular-metrics-2.log, org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase-SYNC-tcp-output.txt, standalone.xml
>
>
> Using ASYM_ENCRYPT on Wildfly 10.1.0 seems to be broken.
> I am using the parameters for ASYM_ENCRYPT specified in http://www.jgroups.org/manual/index.html#Security
> Note: running with SYM_ENCRYPT doesn't cause any issues and it works fine with my setup. Its only ASYM_ENCRYPT which is currently failing.
> Note: running this on EAP fails in a similar manner.
> Eg:
> <protocol type="ASYM_ENCRYPT">
> <property name="encrypt_entire_message">true</property>
> <property name="sym_keylength">128</property>
> <property name="sym_algorithm">AES/ECB/PKCS5Padding</property>
> <property name="asym_keylength">512</property>
> <property name="asym_algorithm">RSA</property>
> </protocol>
> If I run a single instance, then I don't see any problems appear in the logs. Its when I start a second instance that I start to see errors about unrecognised ciphers and timeouts.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JGRP-2152) ASYM_ENCRYPT failure on Wildfly 10.1.0
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/JGRP-2152?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz updated JGRP-2152:
--------------------------------------
Attachment: org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase-SYNC-tcp-output.txt
> ASYM_ENCRYPT failure on Wildfly 10.1.0
> --------------------------------------
>
> Key: JGRP-2152
> URL: https://issues.jboss.org/browse/JGRP-2152
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.10
> Reporter: Matt Wringe
> Assignee: Bela Ban
> Fix For: 4.0, 3.6.13
>
> Attachments: hawkular-metrics-1.log, hawkular-metrics-2.log, org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase-SYNC-tcp-output.txt, standalone.xml
>
>
> Using ASYM_ENCRYPT on Wildfly 10.1.0 seems to be broken.
> I am using the parameters for ASYM_ENCRYPT specified in http://www.jgroups.org/manual/index.html#Security
> Note: running with SYM_ENCRYPT doesn't cause any issues and it works fine with my setup. Its only ASYM_ENCRYPT which is currently failing.
> Note: running this on EAP fails in a similar manner.
> Eg:
> <protocol type="ASYM_ENCRYPT">
> <property name="encrypt_entire_message">true</property>
> <property name="sym_keylength">128</property>
> <property name="sym_algorithm">AES/ECB/PKCS5Padding</property>
> <property name="asym_keylength">512</property>
> <property name="asym_algorithm">RSA</property>
> </protocol>
> If I run a single instance, then I don't see any problems appear in the logs. Its when I start a second instance that I start to see errors about unrecognised ciphers and timeouts.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JGRP-2152) ASYM_ENCRYPT failure on Wildfly 10.1.0
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/JGRP-2152?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz edited comment on JGRP-2152 at 1/12/17 2:48 PM:
--------------------------------------------------------------------
I added an ASYM_ENCRYT layer to the server configuration for the clustering testsuite and turned on TRACE logging for the ASYM_ENCRYPT protocol. Here is the stack:
{noformat}
<stack name="tcp">
<transport type="TCP" socket-binding="jgroups-tcp"/>
<protocol type="MPING" socket-binding="jgroups-mping">
<property name="ip_ttl">0</property>
</protocol>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/>
<protocol type="FD"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="ASYM_ENCRYPT">
<property name="encrypt_entire_message">true</property>
<property name="asym_keylength">512</property>
<property name="asym_algorithm">RSA</property>
</protocol>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="MFC"/>
<protocol type="FRAG2"/>
</stack>
{noformat}
The clustering tests pass with the old config and fail with the new config. One such test, CdiFailoverTestCase, fails with the same error message as in this issue. In this test, two servers, node-0 and node-1, are started. Then node-1 is stopped and then restarted, followed by node-0 which is stolled and then retsrated. Looking at the logs, encryption seems to be progressing normally until the time at which node-1 is restarted. Then messages start getting enqueued and the cipher is reported as being null.
I am attaching the files containing the test case output, which includes logs from both servers.
So this might be a JGroups issue.
was (Author: rachmato):
I added an ASYM_ENCRYT layer to the server configuration for the clustering testsuite and turned on TRACE logging for the ASYM_ENCRYPT protocol. Here is the stack:
{noformat}
<stack name="tcp">
<transport type="TCP" socket-binding="jgroups-tcp"/>
<protocol type="MPING" socket-binding="jgroups-mping">
<property name="ip_ttl">0</property>
</protocol>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/>
<protocol type="FD"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="ASYM_ENCRYPT">
<property name="encrypt_entire_message">true</property>
<property name="asym_keylength">512</property>
<property name="asym_algorithm">RSA</property>
</protocol>
<protocol type="pbcast.NAKACK2"/>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="MFC"/>
<protocol type="FRAG2"/>
</stack>
{noformat}
The clustering tests pass with the old config and fail with the new config. One such test, CdiFailoverTestCase, fails with the same error message as in this issue. In this test, two servers, node-0 and node-1, are started. Then node-1 is stopped and then restarted, followed by node-0 which is stolled and then retsrated. Looking at the logs, encryption seems to be progressing normally until the time at which node-1 is restarted. Then messages start getting enqueued and the cipher is reported as being null.
I am attaching the files containing the server logs.
So this might be a JGroups issue.
> ASYM_ENCRYPT failure on Wildfly 10.1.0
> --------------------------------------
>
> Key: JGRP-2152
> URL: https://issues.jboss.org/browse/JGRP-2152
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.10
> Reporter: Matt Wringe
> Assignee: Bela Ban
> Fix For: 4.0, 3.6.13
>
> Attachments: hawkular-metrics-1.log, hawkular-metrics-2.log, org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase-SYNC-tcp-output.txt, standalone.xml
>
>
> Using ASYM_ENCRYPT on Wildfly 10.1.0 seems to be broken.
> I am using the parameters for ASYM_ENCRYPT specified in http://www.jgroups.org/manual/index.html#Security
> Note: running with SYM_ENCRYPT doesn't cause any issues and it works fine with my setup. Its only ASYM_ENCRYPT which is currently failing.
> Note: running this on EAP fails in a similar manner.
> Eg:
> <protocol type="ASYM_ENCRYPT">
> <property name="encrypt_entire_message">true</property>
> <property name="sym_keylength">128</property>
> <property name="sym_algorithm">AES/ECB/PKCS5Padding</property>
> <property name="asym_keylength">512</property>
> <property name="asym_algorithm">RSA</property>
> </protocol>
> If I run a single instance, then I don't see any problems appear in the logs. Its when I start a second instance that I start to see errors about unrecognised ciphers and timeouts.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months