March 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13256) Upgrade bouncycastle to 1.65.0

by Jim Ma (Jira)

[ https://issues.redhat.com/browse/WFLY-13256?page=com.atlassian.jira.plugi... ] Jim Ma commented on WFLY-13256: ------------------------------- [~aabdelsa] I upgraded BC to version 1.65b16 and get the same error "javax.net.ssl.SSLException: readHandshakeRecord" with https://ci.wildfly.org/viewLog.html?buildId=192989&tab=buildResultsDiv&bu.... It looks test WSTrustTestCase#testPicketLink breaks testBearer() and testHolderOfKey tests. I looked at the handshake log(please find from attachement) , there is no more findings. It seems there are setting in PicketLinkSTS server endpoint affects ssl setting for other endpoints. I still don't know why. But JDK8 doesn't share this problem. Is it possible some jdk13 bug ? > 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 > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13256) Upgrade bouncycastle to 1.65.0

by Jim Ma (Jira)

[ https://issues.redhat.com/browse/WFLY-13256?page=com.atlassian.jira.plugi... ] Jim Ma updated WFLY-13256: -------------------------- Attachment: bcmail-jdk15on-165b16.jar handshake-error.log handshake-success.log > 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 > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13256) Upgrade bouncycastle to 1.65.0

by Jim Ma (Jira)

[ https://issues.redhat.com/browse/WFLY-13256?page=com.atlassian.jira.plugi... ] Jim Ma updated WFLY-13256: -------------------------- Attachment: (was: bcmail-jdk15on-165b16.jar) > 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 > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5106) Local/Internal Maven Repos can not be accessed

by Enrique González Martínez (Jira)

[ https://issues.redhat.com/browse/DROOLS-5106?page=com.atlassian.jira.plug... ] Enrique González Martínez reassigned DROOLS-5106: ------------------------------------------------- Assignee: Luca Molteni (was: Enrique González Martínez) > Local/Internal Maven Repos can not be accessed > ---------------------------------------------- > > Key: DROOLS-5106 > URL: https://issues.redhat.com/browse/DROOLS-5106 > Project: Drools > Issue Type: Bug > Components: Artifact Repository > Affects Versions: 7.33.0.Final > Reporter: Steve Davidson > Assignee: Luca Molteni > Priority: Major > Labels: Drools, drools-compiler, maven > Attachments: settings.xml > > > Attempting to use an internal Nexus Repository, unable to load Drools KIE Modules using Maven. This works with 7.29.Final. Changing to 7.33.Final fails with the following stack trace; > {code:java} > WARNING: Environment variable M2_HOME is not set > Feb 24, 2020 5:12:30 PM org.kie.server.services.impl.KieServerImpl createContainer > SEVERE: Error creating container 'JUnit Test: kie-server' for module 'com.j2eeguys.demo:KieIssueDemo:0.1.0-SNAPSHOT' > java.lang.RuntimeException: Cannot find KieModule: com.j2eeguys.demo:KieIssueDemo:0.1.0-SNAPSHOT > at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:186) > at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:176) > at org.kie.server.services.impl.KieServerImpl.createContainer(KieServerImpl.java:281) > at org.kie.server.remote.rest.common.resource.KieServerRestImpl.createContainer(KieServerRestImpl.java:157) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:140) > at org.jboss.resteasy.core.ResourceMethodInvoker.internalInvokeOnTarget(ResourceMethodInvoker.java:509) > at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTargetAfterFilter(ResourceMethodInvoker.java:399) > at org.jboss.resteasy.core.ResourceMethodInvoker.lambda$invokeOnTarget$0(ResourceMethodInvoker.java:363) > at org.jboss.resteasy.core.interception.PreMatchContainerRequestContext.filter(PreMatchContainerRequestContext.java:358) > at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:365) > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:337) > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:310) > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:443) > at org.jboss.resteasy.core.SynchronousDispatcher.lambda$invoke$4(SynchronousDispatcher.java:233) > at org.jboss.resteasy.core.SynchronousDispatcher.lambda$preprocess$0(SynchronousDispatcher.java:139) > at org.jboss.resteasy.core.interception.PreMatchContainerRequestContext.filter(PreMatchContainerRequestContext.java:358) > at org.jboss.resteasy.core.SynchronousDispatcher.preprocess(SynchronousDispatcher.java:142) > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:219) > at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:227) > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at org.eclipse.jetty.servlet.ServletHolder$NotAsyncServlet.service(ServletHolder.java:1401) > at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:760) > at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617) > at org.eclipse.jetty.websocket.server.WebSocketUpgradeFilter.doFilter(WebSocketUpgradeFilter.java:226) > at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) > at org.kie.server.services.impl.security.web.CaptureHttpRequestFilter.doFilter(CaptureHttpRequestFilter.java:42) > at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1596) > at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:545) > at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:501) > at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) > at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235) > at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1592) > at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233) > at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1296) > at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188) > at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:485) > at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1562) > at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186) > at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1211) > at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:221) > at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:146) > at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) > at org.eclipse.jetty.server.Server.handle(Server.java:500) > at org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:386) > at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:562) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:378) > at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:270) > at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) > at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117) > at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336) > at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313) > at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171) > at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129) > at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:388) > at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:806) > at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:938) > at java.base/java.lang.Thread.run(Thread.java:834) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5196) Library Screen: Labels in Try Sample are truncated regardless of the actual size of the rectangle

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5196?page=com.atlassian.jira.plug... ] Michael Anstis updated DROOLS-5196: ----------------------------------- Summary: Library Screen: Labels in Try Sample are truncated regardless of the actual size of the rectangle (was: Labels in Try Sample are truncated regardless of the actual size of the rectangle) > Library Screen: Labels in Try Sample are truncated regardless of the actual size of the rectangle > ------------------------------------------------------------------------------------------------- > > Key: DROOLS-5196 > URL: https://issues.redhat.com/browse/DROOLS-5196 > Project: Drools > Issue Type: Quality Risk > Components: DMN Editor > Affects Versions: 7.35.0.Final > Reporter: Luca Molteni > Assignee: Paulo Rego > Priority: Major > Attachments: Screenshot 2020-03-25 17.25.00.png > > > See attached screenshot -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5196) Library Screen: Labels in Try Sample are truncated regardless of the actual size of the rectangle

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5196?page=com.atlassian.jira.plug... ] Michael Anstis updated DROOLS-5196: ----------------------------------- Component/s: tools (was: DMN Editor) > Library Screen: Labels in Try Sample are truncated regardless of the actual size of the rectangle > ------------------------------------------------------------------------------------------------- > > Key: DROOLS-5196 > URL: https://issues.redhat.com/browse/DROOLS-5196 > Project: Drools > Issue Type: Quality Risk > Components: tools > Affects Versions: 7.35.0.Final > Reporter: Luca Molteni > Assignee: Paulo Rego > Priority: Major > Attachments: Screenshot 2020-03-25 17.25.00.png > > > See attached screenshot -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5196) Library Screen: Labels in Try Sample are truncated regardless of the actual size of the rectangle

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5196?page=com.atlassian.jira.plug... ] Michael Anstis updated DROOLS-5196: ----------------------------------- Component/s: (was: tools) > Library Screen: Labels in Try Sample are truncated regardless of the actual size of the rectangle > ------------------------------------------------------------------------------------------------- > > Key: DROOLS-5196 > URL: https://issues.redhat.com/browse/DROOLS-5196 > Project: Drools > Issue Type: Quality Risk > Affects Versions: 7.35.0.Final > Reporter: Luca Molteni > Assignee: Paulo Rego > Priority: Major > Attachments: Screenshot 2020-03-25 17.25.00.png > > > See attached screenshot -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5196) Labels in Try Sample are truncated regardless of the actual size of the rectangle

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5196?page=com.atlassian.jira.plug... ] Michael Anstis commented on DROOLS-5196: ---------------------------------------- [~paulovmr] IDK who looks after Library these days. Can you please reassign accordingly if required. > Labels in Try Sample are truncated regardless of the actual size of the rectangle > --------------------------------------------------------------------------------- > > Key: DROOLS-5196 > URL: https://issues.redhat.com/browse/DROOLS-5196 > Project: Drools > Issue Type: Quality Risk > Components: DMN Editor > Affects Versions: 7.35.0.Final > Reporter: Luca Molteni > Assignee: Paulo Rego > Priority: Major > Attachments: Screenshot 2020-03-25 17.25.00.png > > > See attached screenshot -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5197) It’s possible to create multiple null values in an enumeration.

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5197?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-5197: -------------------------------------- Assignee: Guilherme Gomes (was: Mario Fusco) > It’s possible to create multiple null values in an enumeration. > --------------------------------------------------------------- > > Key: DROOLS-5197 > URL: https://issues.redhat.com/browse/DROOLS-5197 > Project: Drools > Issue Type: Quality Risk > Components: DMN Editor > Affects Versions: 7.35.0.Final > Reporter: Luca Molteni > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: nullinenumeration.mov > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5197) It’s possible to create multiple null values in an enumeration.

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5197?page=com.atlassian.jira.plug... ] Michael Anstis updated DROOLS-5197: ----------------------------------- Tester: Jozef Marko > It’s possible to create multiple null values in an enumeration. > --------------------------------------------------------------- > > Key: DROOLS-5197 > URL: https://issues.redhat.com/browse/DROOLS-5197 > Project: Drools > Issue Type: Quality Risk > Components: DMN Editor > Affects Versions: 7.35.0.Final > Reporter: Luca Molteni > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: nullinenumeration.mov > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2020