[JBoss JIRA] (WFLY-13256) Upgrade bouncycastle to 1.65.0
by Ashley Abdel-Sayed (Jira)
[ https://issues.redhat.com/browse/WFLY-13256?page=com.atlassian.jira.plugi... ]
Ashley Abdel-Sayed commented on WFLY-13256:
-------------------------------------------
[~jim.ma] Fixing the method order will fix the {{WSTrustTestCase}} when run alone, but when I run all the tests in the {{wildfly/testsuite/integration/ws}} folder with {{mvn clean install}} I still get the same failure for all 4 tests ({{WSBearerElytronSecurityPropagationTestCase.testBearer}}, {{WSBearerSecurityPropagationTestCase.testBearer}}, {{WSTrustTestCase.testBearer}} and {{WSTrustTestCase.testHolderOfKey}}).
> Upgrade bouncycastle to 1.65.0
> ------------------------------
>
> Key: WFLY-13256
> URL: https://issues.redhat.com/browse/WFLY-13256
> Project: WildFly
> Issue Type: Component Upgrade
> Components: Build System, Server
> Reporter: Bartosz Spyrko-Smietanko
> Assignee: Brian Stansberry
> Priority: Blocker
> Labels: downstream_dependency
> Fix For: 20.0.0.Beta1
>
> Attachments: handshake-error.log, handshake-success.log
>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFWIP-316) Different behaviour of ADMIN_PASSWORD and securing management interface
by Jeff Mesnil (Jira)
[ https://issues.redhat.com/browse/WFWIP-316?page=com.atlassian.jira.plugin... ]
Jeff Mesnil commented on WFWIP-316:
-----------------------------------
I've changed the priority to Critical as this issue is not specific to EAP XP1 but illustrates a difference of behaviour between legacy security and Elytron that is already present in EAP 7.3.0.
> Different behaviour of ADMIN_PASSWORD and securing management interface
> -----------------------------------------------------------------------
>
> Key: WFWIP-316
> URL: https://issues.redhat.com/browse/WFWIP-316
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Critical
> Labels: EAP-XP1
>
> With XP image started to fail test where {{ADMIN_PASSWORD}} env var is empty. Because test is expecting management interface to be unsecured in that case. But this does not happen and management interface is secured with SASL authentication factory. Test is using CLI so it is SASL which is used for accessing management interface.
> Seems in other images CD, 7.3.0.GA (with legacy security in place) when {{ADMIN_PASSWORD}} was empty management interface was left unsecured.
> Seems to me we should be consistent between legacy security and Elytron approach of securing OpenShift images.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFWIP-316) Different behaviour of ADMIN_PASSWORD and securing management interface
by Jeff Mesnil (Jira)
[ https://issues.redhat.com/browse/WFWIP-316?page=com.atlassian.jira.plugin... ]
Jeff Mesnil updated WFWIP-316:
------------------------------
Priority: Critical (was: Blocker)
> Different behaviour of ADMIN_PASSWORD and securing management interface
> -----------------------------------------------------------------------
>
> Key: WFWIP-316
> URL: https://issues.redhat.com/browse/WFWIP-316
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Critical
> Labels: EAP-XP1
>
> With XP image started to fail test where {{ADMIN_PASSWORD}} env var is empty. Because test is expecting management interface to be unsecured in that case. But this does not happen and management interface is secured with SASL authentication factory. Test is using CLI so it is SASL which is used for accessing management interface.
> Seems in other images CD, 7.3.0.GA (with legacy security in place) when {{ADMIN_PASSWORD}} was empty management interface was left unsecured.
> Seems to me we should be consistent between legacy security and Elytron approach of securing OpenShift images.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (JBPORTAL-2500) Changing JBoss Fuse version to 6.3
by Karina Hasler (Jira)
Karina Hasler created JBPORTAL-2500:
---------------------------------------
Summary: Changing JBoss Fuse version to 6.3
Key: JBPORTAL-2500
URL: https://issues.redhat.com/browse/JBPORTAL-2500
Project: JBoss Portal
Issue Type: Task
Reporter: Karina Hasler
Hi,
We are currently using Fuse 6.1 and we have to upgrade to 6.3. Also, we will be using a 3 node cluster configuration. What all do we require? Can we have a call to discuss it in detail this week?
Thanks,
Yashika
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5321) Randomly failing test org.kie.hacep.LocalStorageKieSessionTest.fireUntilHaltTest on timeout
by Marek Novotny (Jira)
[ https://issues.redhat.com/browse/DROOLS-5321?page=com.atlassian.jira.plug... ]
Marek Novotny commented on DROOLS-5321:
---------------------------------------
here it is https://rhba-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/KIE/job/master/j... but this is just the last one I saw, there were multiple times several occurences in the same test class on unrelated PR changes
> Randomly failing test org.kie.hacep.LocalStorageKieSessionTest.fireUntilHaltTest on timeout
> -------------------------------------------------------------------------------------------
>
> Key: DROOLS-5321
> URL: https://issues.redhat.com/browse/DROOLS-5321
> Project: Drools
> Issue Type: Task
> Reporter: Marek Novotny
> Assignee: Massimiliano Dessi
> Priority: Major
>
> {noformat}
> Error Message
> test timed out after 10000 milliseconds
> Stacktrace
> org.junit.runners.model.TestTimedOutException: test timed out after 10000 milliseconds
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at java.util.concurrent.CompletableFuture$Signaller.block(CompletableFuture.java:1693)
> at java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3323)
> at java.util.concurrent.CompletableFuture.waitingGet(CompletableFuture.java:1729)
> at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895)
> at org.kie.hacep.LocalStorageKieSessionTest.fireUntilHaltTest(LocalStorageKieSessionTest.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
> at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.lang.Thread.run(Thread.java:748)
> Standard Output
> 17:37:38.475 [main] WARN o.d.c.k.b.impl.ClasspathKieProject getPomPropertiesFromFileSystem - Unable to find pom.properties in /home/jenkins/workspace/KIE/master/upstream-downstream/droolsjbpm-build-bootstrap.downstream/kiegroup_droolsjbpm-integration/drools-ha/ha-core-infra/target/test-classes
> 17:37:39.088 [Thread-9] WARN org.kie.hacep.util.PrinterUtil process - DroolsConsumerHandler.process Remote command on process:Fact count of 9d177e58-24e5-4b1f-800c-0d0516856f4a from entry-point DEFAULT state:LEADER
> 17:37:39.089 [Thread-9] WARN org.kie.hacep.util.PrinterUtil process - DroolsConsumerHandler.process sideEffects:[]
> 17:37:39.089 [Thread-9] WARN org.kie.hacep.util.PrinterUtil process - DroolsConsumerHandler.process new ControlMessage sent to control topic:ControlMessage{offset=0, sideEffects=[], id='9d177e58-24e5-4b1f-800c-0d0516856f4a', timestamp=0}
> 17:37:39.089 [Thread-9] WARN org.kie.hacep.util.PrinterUtil process - sideEffectOnLeader:[]
> 17:37:39.091 [Thread-10] WARN org.kie.hacep.util.PrinterUtil process - DroolsConsumerHandler.process Remote command on process:Fire until halt of 2a5a4fd4-991d-41ac-99b0-ed7030d8533d state:LEADER
> 17:37:39.091 [Thread-9] WARN org.kie.hacep.util.PrinterUtil process - DroolsConsumerHandler.process Remote command on process:Insert of RemoteFactHandleImpl{id='0597e023-e5d6-4fdb-9396-04705d3b3353', object=StockTickEvent{company='RHT', price=9.0', timestamp=1589233059090}} into entry-point DEFAULT state:LEADER
> 17:37:39.091 [Thread-10] WARN org.kie.hacep.util.PrinterUtil process - DroolsConsumerHandler.process sideEffects:[]
> 17:37:39.091 [Thread-10] WARN org.kie.hacep.util.PrinterUtil process - DroolsConsumerHandler.process new ControlMessage sent to control topic:ControlMessage{offset=0, sideEffects=[], id='2a5a4fd4-991d-41ac-99b0-ed7030d8533d', timestamp=0}
> 17:37:39.091 [Thread-10] WARN org.kie.hacep.util.PrinterUtil process - sideEffectOnLeader:[]
> 17:37:39.091 [Thread-10] WARN org.kie.hacep.util.PrinterUtil process - DroolsConsumerHandler.process Remote command on process:GetObjectCommand{ remoteFactHandle=RemoteFactHandleImpl{id='0597e023-e5d6-4fdb-9396-04705d3b3353', object=StockTickEvent{company='RHT', price=9.0', timestamp=1589233059090}}} state:LEADER
> 17:37:39.098 [Thread-9] WARN org.kie.hacep.util.PrinterUtil process - DroolsConsumerHandler.process sideEffects:[]
> 17:37:39.098 [Thread-9] WARN org.kie.hacep.util.PrinterUtil process - DroolsConsumerHandler.process new ControlMessage sent to control topic:ControlMessage{offset=0, sideEffects=[], id='1a40df01-43a3-4c25-966f-69c5f4233453', timestamp=0}
> 17:37:39.098 [Thread-9] WARN org.kie.hacep.util.PrinterUtil process - sideEffectOnLeader:[]
> 17:37:42.600 [pool-12-thread-1] WARN o.k.h.c.i.e.LeaderElectionImpl lookupNewLeaderInfo - Pod[rhba-jenkins.rhev-ci-vms.eng.rdu2.redhat.com] Unable to retrieve the current ConfigMap default-leaders from Kubernetes
> 17:37:42.939 [pool-15-thread-1] WARN o.k.h.c.i.e.LeaderElectionImpl lookupNewLeaderInfo - Pod[rhba-jenkins.rhev-ci-vms.eng.rdu2.redhat.com] Unable to retrieve the current ConfigMap default-leaders from Kubernetes
> 17:37:48.299 [pool-15-thread-1] WARN o.k.h.c.i.e.LeaderElectionImpl lookupNewLeaderInfo - Pod[rhba-jenkins.rhev-ci-vms.eng.rdu2.redhat.com] Unable to retrieve the current ConfigMap default-leaders from Kubernetes
> 17:37:48.332 [pool-12-thread-1] WARN o.k.h.c.i.e.LeaderElectionImpl lookupNewLeaderInfo - Pod[rhba-jenkins.rhev-ci-vms.eng.rdu2.redhat.com] Unable to retrieve the current ConfigMap default-leaders from Kubernetes
> Standard Error
> Exception in thread "Thread-10" java.lang.IllegalStateException
> at org.kie.hacep.consumer.DroolsConsumerHandler.processCommand(DroolsConsumerHandler.java:182)
> at org.kie.hacep.consumer.DroolsConsumerHandler.process(DroolsConsumerHandler.java:130)
> at org.kie.hacep.core.infra.consumer.LocalConsumer.poll(LocalConsumer.java:50)
> at org.kie.hacep.core.infra.consumer.ConsumerThread.run(ConsumerThread.java:27)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5309) ServiceResponse is not properly serialized when ExecutionResultImpl
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-5309?page=com.atlassian.jira.plug... ]
Mario Fusco updated DROOLS-5309:
--------------------------------
Sprint: (was: 2020 Week 19-21 (from May 4))
> ServiceResponse is not properly serialized when ExecutionResultImpl
> -------------------------------------------------------------------
>
> Key: DROOLS-5309
> URL: https://issues.redhat.com/browse/DROOLS-5309
> Project: Drools
> Issue Type: Bug
> Components: kie server
> Affects Versions: 7.29.0.Final, 7.33.0.Final
> Reporter: Steve Davidson
> Assignee: Mario Fusco
> Priority: Major
> Labels: drools, kie
> Attachments: KieIssueDemo.tbz
>
>
> When a Drools Batch command has been processed, the conversion of the Kie ServiceResponse to JSON wraps the ServiceResponse. The resulting message looks like:
> {code:json}
> {
> "org.kie.server.api.model.ServiceResponse" : {
> "type" : "SUCCESS",
> "msg" : "Container Kie Demo: kie-server successfully called.",
> "result" : {
> "ExecutionResultImpl" : {
> "results" : [ ],
> "facts" : [ ]
> }
> }
> }
> }
> {code}
> A good response doesn't wrap the ServiceResponse:
> {code:json}
> {
> "type" : "SUCCESS",
> "msg" : "List of created containers",
> "result" : {
> "kie-containers" : {
> "kie-container" : [ {
> "container-id" : "Kie Demo: kie-server",
> "release-id" : {
> "group-id" : "com.j2eeguys.demo",
> "artifact-id" : "KieIssueDemo",
> "version" : "0.1.0-SNAPSHOT"
> },
> "resolved-release-id" : {
> "group-id" : "com.j2eeguys.demo",
> "artifact-id" : "KieIssueDemo",
> "version" : "0.1.0-SNAPSHOT"
> },
> "status" : "STARTED",
> "scanner" : {
> "status" : "DISPOSED",
> "poll-interval" : null
> },
> "config-items" : [ ],
> "messages" : [ {
> "severity" : "INFO",
> "timestamp" : {
> "java.util.Date" : 1588885337926
> },
> "content" : [ "Container Kie Demo: kie-server successfully created with module com.j2eeguys.demo:KieIssueDemo:0.1.0-SNAPSHOT." ]
> } ],
> "container-alias" : null
> } ]
> }
> }
> }
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFWIP-316) Different behaviour of ADMIN_PASSWORD and securing management interface
by Jeff Mesnil (Jira)
[ https://issues.redhat.com/browse/WFWIP-316?page=com.atlassian.jira.plugin... ]
Jeff Mesnil commented on WFWIP-316:
-----------------------------------
[~mchoma] I'm not sure that this issue is blocker.
As I understand it, the issue is related to the use of Elytron vs legacy security. If the application is configured with Elytron (instead of legacy security) on EAP 7.3.1, the test would fail, is that right?
I would agree with Jean-Francois that the test fixture could be updated in that case and remove --no-local-auth.
> Different behaviour of ADMIN_PASSWORD and securing management interface
> -----------------------------------------------------------------------
>
> Key: WFWIP-316
> URL: https://issues.redhat.com/browse/WFWIP-316
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Blocker
> Labels: EAP-XP1
>
> With XP image started to fail test where {{ADMIN_PASSWORD}} env var is empty. Because test is expecting management interface to be unsecured in that case. But this does not happen and management interface is secured with SASL authentication factory. Test is using CLI so it is SASL which is used for accessing management interface.
> Seems in other images CD, 7.3.0.GA (with legacy security in place) when {{ADMIN_PASSWORD}} was empty management interface was left unsecured.
> Seems to me we should be consistent between legacy security and Elytron approach of securing OpenShift images.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5324) Refactor "if" driven compilation for dmn/pmml
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-5324?page=com.atlassian.jira.plug... ]
Mario Fusco updated DROOLS-5324:
--------------------------------
Sprint: 2020 Week 22-24 (from May 25)
> Refactor "if" driven compilation for dmn/pmml
> ---------------------------------------------
>
> Key: DROOLS-5324
> URL: https://issues.redhat.com/browse/DROOLS-5324
> Project: Drools
> Issue Type: Task
> Reporter: Gabriele Cardosi
> Assignee: Mario Fusco
> Priority: Major
>
> Inside
> {code:java}
> CanonicalKieModule.createKieBase( KieBaseModelImpl, KieProject, ResultsImpl, KieBaseConfiguration)
> {code}
> there is a call to
> {code:java}
> CanonicalKieModule.hasNonModelResources( KieBaseModelImpl, KieProject )
> {code}
> This method returns `true` if there are some dmn and/or pmml files in the project.
> If such boolean is `true` a new KnowledgePackagesBuildResult is created.
> The main issues with this approach are:
> 1) managing of dmn/pmml resources is completely hidden inside this boolean method and hard to find in debug
> 2) it is possible that the new KnowledgePackagesBuildResult build will fire a compilation also of "drl" or other resources that are "compiled" anyway even without this flag
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5324) Refactor "if" driven compilation for dmn/pmml
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-5324?page=com.atlassian.jira.plug... ]
Mario Fusco commented on DROOLS-5324:
-------------------------------------
Reference https://github.com/kiegroup/drools/blob/master/drools-model/drools-model-...
> Refactor "if" driven compilation for dmn/pmml
> ---------------------------------------------
>
> Key: DROOLS-5324
> URL: https://issues.redhat.com/browse/DROOLS-5324
> Project: Drools
> Issue Type: Task
> Reporter: Gabriele Cardosi
> Assignee: Mario Fusco
> Priority: Major
>
> Inside
> {code:java}
> CanonicalKieModule.createKieBase( KieBaseModelImpl, KieProject, ResultsImpl, KieBaseConfiguration)
> {code}
> there is a call to
> {code:java}
> CanonicalKieModule.hasNonModelResources( KieBaseModelImpl, KieProject )
> {code}
> This method returns `true` if there are some dmn and/or pmml files in the project.
> If such boolean is `true` a new KnowledgePackagesBuildResult is created.
> The main issues with this approach are:
> 1) managing of dmn/pmml resources is completely hidden inside this boolean method and hard to find in debug
> 2) it is possible that the new KnowledgePackagesBuildResult build will fire a compilation also of "drl" or other resources that are "compiled" anyway even without this flag
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months