[JBoss JIRA] (WFLY-12608) Integration tests for OCSP followup
by Jan Stourac (Jira)
Jan Stourac created WFLY-12608:
----------------------------------
Summary: Integration tests for OCSP followup
Key: WFLY-12608
URL: https://issues.jboss.org/browse/WFLY-12608
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Jan Stourac
Assignee: Darran Lofthouse
Followup integration tests for OCSP feature into WildFly testsuite to comply with the feature test-plan.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (WFWIP-213) Can't resolve artifact for module when executing CLI modification
by Jean Francois Denise (Jira)
[ https://issues.jboss.org/browse/WFWIP-213?page=com.atlassian.jira.plugin.... ]
Jean Francois Denise resolved WFWIP-213.
----------------------------------------
Resolution: Done
The settings.xml are now properly set before user execution hooks.
> Can't resolve artifact for module when executing CLI modification
> -----------------------------------------------------------------
>
> Key: WFWIP-213
> URL: https://issues.jboss.org/browse/WFWIP-213
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Jan Blizňák
> Assignee: Jean Francois Denise
> Priority: Blocker
>
> Using image {{docker-registry.upshift.redhat.com/kwills/eap-cd-openshift-rhel8:18.0-EAP7-1216}} when we workaround the issues WFWIP-208 & WFWIP-212 the CLI modification still won't process successfully because of the exception:
> {code:java}
> I0926 13:20:23.465008 1 sti.go:697] Exception in thread "main" org.jboss.modules.ModuleLoadException: Error loading module from /opt/eap/modules/system/layers/base/org/apache/xerces/main/module.xml
> I0926 13:20:23.465037 1 sti.go:697] at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:339)
> I0926 13:20:23.465047 1 sti.go:697] at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:295)
> I0926 13:20:23.465052 1 sti.go:697] at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:256)
> I0926 13:20:23.465060 1 sti.go:697] at org.jboss.modules.LocalModuleFinder.parseModuleXmlFile(LocalModuleFinder.java:250)
> I0926 13:20:23.465067 1 sti.go:697] at org.jboss.modules.LocalModuleFinder.lambda$findModule$1(LocalModuleFinder.java:195)
> I0926 13:20:23.465075 1 sti.go:697] at java.base/java.security.AccessController.doPrivileged(Native Method)
> I0926 13:20:23.465082 1 sti.go:697] at org.jboss.modules.LocalModuleFinder.findModule(LocalModuleFinder.java:195)
> I0926 13:20:23.465089 1 sti.go:697] at org.jboss.modules.ModuleLoader.findModule0(ModuleLoader.java:696)
> I0926 13:20:23.465096 1 sti.go:697] at org.jboss.modules.ModuleLoader.findModule(ModuleLoader.java:689)
> I0926 13:20:23.465103 1 sti.go:697] at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:499)
> I0926 13:20:23.465110 1 sti.go:697] at org.jboss.modules.DelegatingModuleLoader.preloadModule(DelegatingModuleLoader.java:57)
> I0926 13:20:23.465117 1 sti.go:697] at org.jboss.modules.Module.addPaths(Module.java:1252)
> I0926 13:20:23.465125 1 sti.go:697] at org.jboss.modules.Module.link(Module.java:1622)
> I0926 13:20:23.465132 1 sti.go:697] at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650)
> I0926 13:20:23.465141 1 sti.go:697] at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:299)
> I0926 13:20:23.465147 1 sti.go:697] at org.jboss.modules.Main.main(Main.java:437)
> I0926 13:20:23.465153 1 sti.go:697] Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to resolve artifact 'xerces:xercesImpl:2.12.0.SP02' (position: END_TAG seen ...esources>\n <artifact name="xerces:xercesImpl:2.12.0.SP02"/>... @26:57)
> I0926 13:20:23.465159 1 sti.go:697] at org.jboss.modules.xml.ModuleXmlParser.parseArtifact(ModuleXmlParser.java:1063)
> I0926 13:20:23.465177 1 sti.go:697] at org.jboss.modules.xml.ModuleXmlParser.parseResources(ModuleXmlParser.java:950)
> I0926 13:20:23.465206 1 sti.go:697] at org.jboss.modules.xml.ModuleXmlParser.parseModuleContents(ModuleXmlParser.java:710)
> I0926 13:20:23.465211 1 sti.go:697] at org.jboss.modules.xml.ModuleXmlParser.parseDocument(ModuleXmlParser.java:471)
> I0926 13:20:23.465217 1 sti.go:697] at org.jboss.modules.xml.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:337)
> I0926 13:20:23.465224 1 sti.go:697] ... 15 more
> {code}
> Because jboss-modules will try to resolve artifact from ~/.m2/settings.xml and galleon integration replaces this file before this error, there must be something wrong.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (WFLY-12601) Eliminate StabilityMonitor usages in clustering subsystem
by Richard Opalka (Jira)
[ https://issues.jboss.org/browse/WFLY-12601?page=com.atlassian.jira.plugin... ]
Richard Opalka commented on WFLY-12601:
---------------------------------------
CountDownLifecycle listener needs to remove listener
once target event is achieved - see my review comment.
Otherwise changes to ServiceLifecycle looks good to me [~pferraro]
> Eliminate StabilityMonitor usages in clustering subsystem
> ---------------------------------------------------------
>
> Key: WFLY-12601
> URL: https://issues.jboss.org/browse/WFLY-12601
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Reporter: Richard Opalka
> Assignee: Paul Ferraro
> Priority: Major
> Fix For: 19.0.0.Beta1
>
> Attachments: ServiceSupplier.png
>
>
> Clustering needs to eliminate usages of StabilityMonitor because SM is not reliable.
> It is possible that SM will prematurely inform about achieved stability even if it is not true.
> The reason is SM is not propagated up the dependencies chain and thus it may report
> about achieved stability even in case dependencies chain didn't finish its processing yet
> and 'real' stability wasn't achieved yet.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (DROOLS-4575) Test Scenario: unsaved changes warning appears even if file has not been changed
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4575?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4575:
--------------------------------
Description:
If user opens a scesim file and then close it, no confirmation message should be opened
h2. Manual Acceptance Test
- Opening and closing without changes
- Open, change data in cell, close
- Open, add column, remove column, change column binding, close
- Open, Change settings on the settings panel (e.g. ruleflow group, kie session), close
was:If user opens a scesim file and then close it, no confirmation message should be opened
> Test Scenario: unsaved changes warning appears even if file has not been changed
> --------------------------------------------------------------------------------
>
> Key: DROOLS-4575
> URL: https://issues.jboss.org/browse/DROOLS-4575
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Daniele Zonca
> Priority: Major
> Labels: CustomerFocus
>
> If user opens a scesim file and then close it, no confirmation message should be opened
> h2. Manual Acceptance Test
> - Opening and closing without changes
> - Open, change data in cell, close
> - Open, add column, remove column, change column binding, close
> - Open, Change settings on the settings panel (e.g. ruleflow group, kie session), close
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months