[JBoss JIRA] (DROOLS-3238) Using -DgenerateModel=YES try to compile using Drools compiler test classes
by Matteo Mortari (Jira)
Matteo Mortari created DROOLS-3238:
--------------------------------------
Summary: Using -DgenerateModel=YES try to compile using Drools compiler test classes
Key: DROOLS-3238
URL: https://issues.jboss.org/browse/DROOLS-3238
Project: Drools
Issue Type: Bug
Components: tools
Reporter: Matteo Mortari
Assignee: Luca Molteni
Attachments: image-2018-11-05-11-45-49-430.png, test-generateModel-kjararchetype.zip
With the attachment zip file and use -DgenerateModel=YES flag.
Error will be reported as:
!image-2018-11-05-11-45-49-430.png!
It looks like generate exec model mojo is trying to compile classes and resources which belong to the test scope.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3237) Using -DgenerateModel=YES skips resources compilation check
by Matteo Mortari (Jira)
Matteo Mortari created DROOLS-3237:
--------------------------------------
Summary: Using -DgenerateModel=YES skips resources compilation check
Key: DROOLS-3237
URL: https://issues.jboss.org/browse/DROOLS-3237
Project: Drools
Issue Type: Bug
Components: tools
Reporter: Matteo Mortari
Assignee: Luca Molteni
Usually the standard kie-maven-plugin mojo compiles any Drools resource at compile time in order to check for errors.
Using -DgenerateModel=YES instead generate the exec model, but skips resource compilation.
To replicate:
introduce a Drools resource which does NOT compile in the KJAR. Without the flag, it fail maven compilation. With the flag, maven compilation succeeds.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11278) Management Console Replace Deployment file chooser doesn't select file
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFLY-11278?page=com.atlassian.jira.plugin... ]
Jeff Mesnil updated WFLY-11278:
-------------------------------
Component/s: Web Console
(was: Management)
> Management Console Replace Deployment file chooser doesn't select file
> ----------------------------------------------------------------------
>
> Key: WFLY-11278
> URL: https://issues.jboss.org/browse/WFLY-11278
> Project: WildFly
> Issue Type: Bug
> Components: Web Console
> Affects Versions: 14.0.0.Final
> Environment: Server on Solaris 11.3
> User on Windows 10 Chrome 69.0.3497.92 (Official Build) (64-bit)
> Reporter: Ian Roskam
> Assignee: Jeff Mesnil
> Priority: Major
>
> When clicking "Choose a file or drag it here" in the Replace Deployment dialog the OS file chooser appears. The selected file does not get set in the Replace Deployment dialog. Dragging the file into the dialog does work.
> To reproduce:
> Deployments tab
> Choose to Replace a deployment
> Click "Choose a file or drag it here" link in the Replace Deployment dialog.
> Select war to deploy in OS file chooser.
> Press OK.
> Expected result:
> File is set in dialog so replacement can proceed.
> Actual result:
> File is +not+ set in dialog and replacement cannot proceed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11278) Management Console Replace Deployment file chooser doesn't select file
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFLY-11278?page=com.atlassian.jira.plugin... ]
Jeff Mesnil reassigned WFLY-11278:
----------------------------------
Assignee: Harald Pehl (was: Jeff Mesnil)
> Management Console Replace Deployment file chooser doesn't select file
> ----------------------------------------------------------------------
>
> Key: WFLY-11278
> URL: https://issues.jboss.org/browse/WFLY-11278
> Project: WildFly
> Issue Type: Bug
> Components: Web Console
> Affects Versions: 14.0.0.Final
> Environment: Server on Solaris 11.3
> User on Windows 10 Chrome 69.0.3497.92 (Official Build) (64-bit)
> Reporter: Ian Roskam
> Assignee: Harald Pehl
> Priority: Major
>
> When clicking "Choose a file or drag it here" in the Replace Deployment dialog the OS file chooser appears. The selected file does not get set in the Replace Deployment dialog. Dragging the file into the dialog does work.
> To reproduce:
> Deployments tab
> Choose to Replace a deployment
> Click "Choose a file or drag it here" link in the Replace Deployment dialog.
> Select war to deploy in OS file chooser.
> Press OK.
> Expected result:
> File is set in dialog so replacement can proceed.
> Actual result:
> File is +not+ set in dialog and replacement cannot proceed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-10654) In WFLY 13 when you deploy a simple Jar file , WFLY 13 treats the jar as the EJB and starts the "ejb" cache container.
by Chao Wang (Jira)
[ https://issues.jboss.org/browse/WFLY-10654?page=com.atlassian.jira.plugin... ]
Chao Wang reassigned WFLY-10654:
--------------------------------
Assignee: Paul Ferraro
> In WFLY 13 when you deploy a simple Jar file , WFLY 13 treats the jar as the EJB and starts the "ejb" cache container.
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-10654
> URL: https://issues.jboss.org/browse/WFLY-10654
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB
> Affects Versions: 13.0.0.Final
> Reporter: Chao Wang
> Assignee: Paul Ferraro
> Priority: Major
>
> Deployment(from management console) of a simple Jar file in EAP 7.1.x causes the ejb cache container to start , which should not be the case .
> From EAP 7.1.x onwards @clustered annotation has been depricated and EJB application is required to start clustering , but in contradiction to this even if we deploy ant jar file (let's say ojdbc6.jar ) the container treats it as an EJB application and starts the EJB cache container as seen in the logs below :
> ~~~~
> 1,640 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000078: Starting JGroups channel ejb
> 22:14:21,640 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000078: Starting JGroups channel ejb
> 22:14:21,640 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000078: Starting JGroups channel ejb
> 22:14:21,640 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000078: Starting JGroups channel ejb
> 22:14:21,673 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000094: Received new cluster view for channel ejb: [plohia|0] (1) [plohia]
> 22:14:21,673 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000094: Received new cluster view for channel ejb: [plohia|0] (1) [plohia]
> 22:14:21,676 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000079: Channel ejb local address is plohia, physical addresses are [192.168.122.1:55200]
> 22:14:21,678 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000079: Channel ejb local address is plohia, physical addresses are [192.168.122.1:55200]
> ~~~~
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11282) ignore-dependency in jboss-web.xml does not work
by Jiri Ondrusek (Jira)
[ https://issues.jboss.org/browse/WFLY-11282?page=com.atlassian.jira.plugin... ]
Jiri Ondrusek moved JBEAP-15767 to WFLY-11282:
----------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-11282 (was: JBEAP-15767)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Affects Version/s: 15.0.0.Alpha1
(was: 7.1.0.GA)
> ignore-dependency in jboss-web.xml does not work
> ------------------------------------------------
>
> Key: WFLY-11282
> URL: https://issues.jboss.org/browse/WFLY-11282
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 15.0.0.Alpha1
> Environment: JBoss EAP 7.1.0
> Java 8u192
> CentOS 7.5 x64
> Reporter: Jiri Ondrusek
> Assignee: Jiri Ondrusek
> Priority: Major
> Labels: deploy, deployment, resource-ref
>
> 1. Use of *ignore-dependency* in the *resource-ref* in *jboss-web.xml* doesn't work, the resource reference remains mandatory.
> Have the following in *web.xml*
> {code:xml}<resource-ref>
> <res-ref-name>wm/WM1</res-ref-name>
> <res-type>commonj.work.WorkManager</res-type>
> <res-auth>Container</res-auth>
> <res-sharing-scope>Shareable</res-sharing-scope>
> </resource-ref>
> <resource-ref>
> <res-ref-name>tm/TM1</res-ref-name>
> <res-type>commonj.timers.TimerManager</res-type>
> <res-auth>Container</res-auth>
> <res-sharing-scope>Unshareable</res-sharing-scope>
> </resource-ref>{code}
> In order to let the ear/war deploy at JBoss EAP (where the CommonJ API isn't available), add a *jboss-web.xml* setting these resource references to be ignored by adding *<ignore-dependency/>*
> {code:xml}<?xml version="1.0" encoding="UTF-8"?>
> <jboss-web xmlns="http://www.jboss.com/xml/ns/javaee"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-web_7_2.xsd"
> version="7.2">
> <context-root>mod</context-root>
> <resource-ref>
> <res-ref-name>wm/WM1</res-ref-name>
> <jndi-name>DummyWorkManager</jndi-name>
> <ignore-dependency/>
> </resource-ref>
> <resource-ref>
> <res-ref-name>tm/TM1</res-ref-name>
> <jndi-name>DummyTimerManager</jndi-name>
> <ignore-dependency/>
> </resource-ref>
> </jboss-web>{code}
> However the deploy will fail (as if the jboss-web.xml wouldn't be there at all):
> {noformat}ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.subunit."APP.ear"."mod.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."APP.ear"."mod.war".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of subdeployment "mod.war" of deployment "APP.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0027: Could not load commonj.work.WorkManager referenced in env-entry
> at org.jboss.as.ee.component.deployers.ResourceReferenceProcessor.getResourceRefEntries(ResourceReferenceProcessor.java:153)
> at org.jboss.as.ee.component.deployers.ResourceReferenceProcessor.processDescriptorEntries(ResourceReferenceProcessor.java:74)
> at org.jboss.as.ee.component.deployers.AbstractDeploymentDescriptorBindingsProcessor.deploy(AbstractDeploymentDescriptorBindingsProcessor.java:95)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
> ... 5 more
> Caused by: java.lang.ClassNotFoundException: commonj.work.WorkManager from [Module "deployment.APP.ear.mod.war" from Service Module Loader]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:198)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:412)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:400)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
> at org.jboss.as.ee.component.deployers.ResourceReferenceProcessor.getResourceRefEntries(ResourceReferenceProcessor.java:151)
> ... 8 more{noformat}
> \\
> 2. Overriding *resource-ref* from *web.xml* in *jboss-web*.xml doesn't work properly.
> I can partially work around the above ClassNotFoundException by adding a dummy res-type like
> {code:xml}<res-type>javax.resource.Referenceable</res-type>{code}
> to both resource references in jboss-web.xml, however this seems to override only the 1st entry as the ClassNotFoundException will change to
> {noformat}java.lang.ClassNotFoundException: commonj.timers.TimerManager{noformat}
> and I don't seem to be able to get rid of this one in any way, save for removing the 2nd resource reference (timer manager) from web.xml and jboss.xml completely.
> Then the deploy will fail with
> {noformat}ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "APP.ear")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.module.app-name.mod-name.env.DummyWorkManager"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.app-name.mod-name.env.wm.WM1 is missing [jboss.naming.context.java.module.app-name.mod-name.env.DummyWorkManager]"]
> }{noformat}
> which only confirms that the ignore-dependency doesn't work.
> Notes:
> - The fact that the CommonJ API can't be used at JBoss EAP isn't a problem. The ear is built to be usable for multiple app servers. The CommonJ WorkManager and TimerManager resources are used only at those app servers where available. We just need the ear to successfully deploy at JBoss EAP. We can take care of the rest.
> - It's likely that providing a modified web.xml via deployment overlay would make things work (not tested but I'm pretty confident about that), but we want to avoid that, we'd like to have the ear deploy straight away (and it should be possible with the use of ignore-dependency)
> - ignore-dependency did work at JBoss AS 6.0, see https://developer.jboss.org/thread/160804
> - Slightly more extensive description of both issues is available here: https://stackoverflow.com/questions/52967897/jboss-eap-7-1-how-to-ignore-...
> - Since there are actually 2 issues being reported here (but they seem to be connected), this JIRA issue can be split into 2 if required
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3236) Unable to open KJAR project in eclipse due to "Missing parameter for pluginExecutionFilter"
by Matteo Mortari (Jira)
Matteo Mortari created DROOLS-3236:
--------------------------------------
Summary: Unable to open KJAR project in eclipse due to "Missing parameter for pluginExecutionFilter"
Key: DROOLS-3236
URL: https://issues.jboss.org/browse/DROOLS-3236
Project: Drools
Issue Type: Bug
Components: tools
Affects Versions: 7.13.0.Final, 7.12.0.Final, 7.11.0.Final, 7.10.0.Final
Environment: Eclipse photon, Eclipse 2018 09, no special plugin
m2eclipse configured to do-not-manage/ignore any unknown plugin goal (easiest choice)
Reporter: Matteo Mortari
Assignee: Mario Fusco
Attachments: image-2018-11-05-10-28-50-255.png
Since 7.10.0.Final the following error occurs when opening a KJAR project in Eclipse:
!image-2018-11-05-10-28-50-255.png!
Errors occurred during the build.
Errors running builder 'Maven Project Builder' on project '...'.
Missing parameter for pluginExecutionFilter. groupId, artifactId, versionRange and goals must be specificed, but found: groupId = 'org.kie'
artifactId = 'kie-maven-plugin'
versionRange = '7.10.0.Final'
goals = '[]'
Please notice kie-maven-plugin 7.9.0.Final and earlier do NOT exhibit this issue.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (ELY-1708) java.lang.NoSuchFieldError: state on oracle jdk 1.8.0_191
by Martin Choma (Jira)
Martin Choma created ELY-1708:
---------------------------------
Summary: java.lang.NoSuchFieldError: state on oracle jdk 1.8.0_191
Key: ELY-1708
URL: https://issues.jboss.org/browse/ELY-1708
Project: WildFly Elytron
Issue Type: Bug
Components: SSL
Affects Versions: 1.7.0.CR3
Reporter: Martin Choma
- on oracle java version "1.8.0_181" it was ok on oracle java version "1.8.0_191" it fails
- I have checked oracle jdk 1.8.0_191 release notes and this seems relevant to this issue https://bugs.java.com/view_bug.do?bug_id=JDK-8074462
- I have seen so far only in FIPS TS (BC and PKCS11)
- I dont see on openjdk
- I dont see on oracle jdk 11
- I have reported to oracle but get no link to issue tracker back. They just told me "We will contact you if needed" :)
- similar problem https://youtrack.jetbrains.com/issue/JT-49978
{noformat}
21:19:11 java.lang.NoSuchFieldError: state
21:19:11 at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:198)
21:19:11 at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1037)
21:19:11 at sun.security.ssl.Handshaker.process_record(Handshaker.java:965)
21:19:11 at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1064)
21:19:11 at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367)
21:19:11 at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1395)
21:19:11 at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1379)
21:19:11 at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:394)
21:19:11 at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:353)
{noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (ELY-1663) BC FIPS, Management Interface, ELY04001: No algorithm found matching TLS/SSL protocol selection criteria
by Martin Choma (Jira)
[ https://issues.jboss.org/browse/ELY-1663?page=com.atlassian.jira.plugin.s... ]
Martin Choma commented on ELY-1663:
-----------------------------------
Raising priotity to triage properly seems BC upper case "TLSV1.2" in TLSV1.2 is making troubles again. In this case intermittently.
> BC FIPS, Management Interface, ELY04001: No algorithm found matching TLS/SSL protocol selection criteria
> --------------------------------------------------------------------------------------------------------
>
> Key: ELY-1663
> URL: https://issues.jboss.org/browse/ELY-1663
> Project: WildFly Elytron
> Issue Type: Bug
> Components: SSL
> Affects Versions: 1.6.0.Final
> Reporter: Martin Choma
> Priority: Blocker
>
> Rarely 1:30 it happens there occures error accessing http management interface secured with TLS with BC FIPS
> {code}
> Operation {"operation" => "add","address" => [("subsystem" => "elytron"),("server-ssl-context" => "test-server-ssl-context")],"key-manager" => "key-manager-name_test-server-ssl-context","cipher-suite-filter" => "TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA,TLS_DHE_DSS_WITH_AES_128_CBC_SHA,TLS_DHE_DSS_WITH_AES_128_CBC_SHA256,TLS_DHE_DSS_WITH_AES_256_CBC_SHA,TLS_DHE_DSS_WITH_AES_256_CBC_SHA256,TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_3DES_EDE_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA256","trust-manager" => "trust-manager-name_test-server-ssl-context","protocols" => ["TLSv1.2"],"need-client-auth" => true} failed: {"outcome" => "failed","failure-description" => {"WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.test-server-ssl-context" => "java.security.NoSuchAlgorithmException: ELY04001: No algorithm found matching TLS/SSL protocol selection criteria
> Caused by: java.security.NoSuchAlgorithmException: ELY04001: No algorithm found matching TLS/SSL protocol selection criteria"}},"rolled-back" => true}
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service org.wildfly.security.ssl-context.test-server-ssl-context: org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.test-server-ssl-context: java.security.NoSuchAlgorithmException: ELY04001: No algorithm found matching TLS/SSL protocol selection criteria
> at org.wildfly.extension.elytron.SSLDefinitions$6.lambda$getValueSupplier$1(SSLDefinitions.java:982)
> at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.security.NoSuchAlgorithmException: ELY04001: No algorithm found matching TLS/SSL protocol selection criteria
> at org.wildfly.security.ssl.SSLUtils.lambda$createSslContextFactory$1(SSLUtils.java:130)
> at org.wildfly.security.ssl.SSLContextBuilder.lambda$build$0(SSLContextBuilder.java:340)
> at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:53)
> at org.wildfly.extension.elytron.SSLDefinitions$6.lambda$getValueSupplier$1(SSLDefinitions.java:980)
> ... 9 more
> {code}
> Some facts
> * It happens only on management interface BC FIPS TLS tests
> * It does not occur on Undertow secured with BC FIPS
> * Previously there was issue with similar error but that happened everywhere https://issues.jboss.org/browse/ELY-1618
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months