[JBoss JIRA] (DROOLS-5671) [DMN Designer] Text annotation causes unexpected system error
by Lubomír Terifaj (Jira)
[ https://issues.redhat.com/browse/DROOLS-5671?page=com.atlassian.jira.plug... ]
Lubomír Terifaj updated DROOLS-5671:
------------------------------------
Description:
Creating Text annotation causes unexpected system error.
Error details:
{code:java}
Uncaught exception: Exception caught: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.controls.event.BuildCanvasShapeEvent, BeanReference=BuildCanvasShapeEvent [definition=org.kie.workbench.common.dmn.api.definition.model.TextAnnotation@85a8abd2, factory=org.kie.workbench.common.dmn.client.shape.factory.DMNShapeFactory@4941, clientX=674, clientY=350], FromClient=1 sent to [unavailable] Caused by: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.controls.event.BuildCanvasShapeEvent, BeanReference=BuildCanvasShapeEvent [definition=org.kie.workbench.common.dmn.api.definition.model.TextAnnotation@85a8abd2, factory=org.kie.workbench.common.dmn.client.shape.factory.DMNShapeFactory@4941, clientX=674, clientY=350], FromClient=1 sent to [unavailable] Caused by: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent, BeanReference=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent@4bb7, FromClient=1 sent to [unavailable] Caused by: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent, BeanReference=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent@4bb6, FromClient=1 sent to [unavailable] Caused by: (TypeError) : c is null
{code}
was:
Text annotation causes unexpected system error:
{code:java}
Uncaught exception: Exception caught: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.controls.event.BuildCanvasShapeEvent, BeanReference=BuildCanvasShapeEvent [definition=org.kie.workbench.common.dmn.api.definition.model.TextAnnotation@85a8abd2, factory=org.kie.workbench.common.dmn.client.shape.factory.DMNShapeFactory@4941, clientX=674, clientY=350], FromClient=1 sent to [unavailable] Caused by: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.controls.event.BuildCanvasShapeEvent, BeanReference=BuildCanvasShapeEvent [definition=org.kie.workbench.common.dmn.api.definition.model.TextAnnotation@85a8abd2, factory=org.kie.workbench.common.dmn.client.shape.factory.DMNShapeFactory@4941, clientX=674, clientY=350], FromClient=1 sent to [unavailable] Caused by: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent, BeanReference=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent@4bb7, FromClient=1 sent to [unavailable] Caused by: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent, BeanReference=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent@4bb6, FromClient=1 sent to [unavailable] Caused by: (TypeError) : c is null
{code}
> [DMN Designer] Text annotation causes unexpected system error
> -------------------------------------------------------------
>
> Key: DROOLS-5671
> URL: https://issues.redhat.com/browse/DROOLS-5671
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.44.0.Final
> Reporter: Lubomír Terifaj
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
>
> Creating Text annotation causes unexpected system error.
> Error details:
> {code:java}
> Uncaught exception: Exception caught: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.controls.event.BuildCanvasShapeEvent, BeanReference=BuildCanvasShapeEvent [definition=org.kie.workbench.common.dmn.api.definition.model.TextAnnotation@85a8abd2, factory=org.kie.workbench.common.dmn.client.shape.factory.DMNShapeFactory@4941, clientX=674, clientY=350], FromClient=1 sent to [unavailable] Caused by: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.controls.event.BuildCanvasShapeEvent, BeanReference=BuildCanvasShapeEvent [definition=org.kie.workbench.common.dmn.api.definition.model.TextAnnotation@85a8abd2, factory=org.kie.workbench.common.dmn.client.shape.factory.DMNShapeFactory@4941, clientX=674, clientY=350], FromClient=1 sent to [unavailable] Caused by: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent, BeanReference=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent@4bb7, FromClient=1 sent to [unavailable] Caused by: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent, BeanReference=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent@4bb6, FromClient=1 sent to [unavailable] Caused by: (TypeError) : c is null
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (DROOLS-5671) [DMN Designer] Text annotation causes unexpected system error
by Lubomír Terifaj (Jira)
[ https://issues.redhat.com/browse/DROOLS-5671?page=com.atlassian.jira.plug... ]
Lubomír Terifaj updated DROOLS-5671:
------------------------------------
Affects Version/s: 7.44.0.Final
> [DMN Designer] Text annotation causes unexpected system error
> -------------------------------------------------------------
>
> Key: DROOLS-5671
> URL: https://issues.redhat.com/browse/DROOLS-5671
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.44.0.Final
> Reporter: Lubomír Terifaj
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
>
> Text annotation causes unexpected system error:
> {code:java}
> Uncaught exception: Exception caught: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.controls.event.BuildCanvasShapeEvent, BeanReference=BuildCanvasShapeEvent [definition=org.kie.workbench.common.dmn.api.definition.model.TextAnnotation@85a8abd2, factory=org.kie.workbench.common.dmn.client.shape.factory.DMNShapeFactory@4941, clientX=674, clientY=350], FromClient=1 sent to [unavailable] Caused by: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.controls.event.BuildCanvasShapeEvent, BeanReference=BuildCanvasShapeEvent [definition=org.kie.workbench.common.dmn.api.definition.model.TextAnnotation@85a8abd2, factory=org.kie.workbench.common.dmn.client.shape.factory.DMNShapeFactory@4941, clientX=674, clientY=350], FromClient=1 sent to [unavailable] Caused by: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent, BeanReference=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent@4bb7, FromClient=1 sent to [unavailable] Caused by: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent, BeanReference=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent@4bb6, FromClient=1 sent to [unavailable] Caused by: (TypeError) : c is null
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (DROOLS-5671) [DMN Designer] Text annotation causes unexpected system error
by Lubomír Terifaj (Jira)
Lubomír Terifaj created DROOLS-5671:
---------------------------------------
Summary: [DMN Designer] Text annotation causes unexpected system error
Key: DROOLS-5671
URL: https://issues.redhat.com/browse/DROOLS-5671
Project: Drools
Issue Type: Bug
Components: DMN Editor
Reporter: Lubomír Terifaj
Assignee: Guilherme Gomes
Text annotation causes unexpected system error:
{code:java}
Uncaught exception: Exception caught: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.controls.event.BuildCanvasShapeEvent, BeanReference=BuildCanvasShapeEvent [definition=org.kie.workbench.common.dmn.api.definition.model.TextAnnotation@85a8abd2, factory=org.kie.workbench.common.dmn.client.shape.factory.DMNShapeFactory@4941, clientX=674, clientY=350], FromClient=1 sent to [unavailable] Caused by: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.controls.event.BuildCanvasShapeEvent, BeanReference=BuildCanvasShapeEvent [definition=org.kie.workbench.common.dmn.api.definition.model.TextAnnotation@85a8abd2, factory=org.kie.workbench.common.dmn.client.shape.factory.DMNShapeFactory@4941, clientX=674, clientY=350], FromClient=1 sent to [unavailable] Caused by: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent, BeanReference=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent@4bb7, FromClient=1 sent to [unavailable] Caused by: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent, BeanReference=org.kie.workbench.common.stunner.core.client.canvas.event.selection.CanvasSelectionEvent@4bb6, FromClient=1 sent to [unavailable] Caused by: (TypeError) : c is null
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (WFWIP-359) Server can get to state, where XP2 manager thinks both XP1 and XP2 streams are active
by Kabir Khan (Jira)
[ https://issues.redhat.com/browse/WFWIP-359?page=com.atlassian.jira.plugin... ]
Kabir Khan commented on WFWIP-359:
----------------------------------
I have added some better validation to the patch-apply command if they specify a patch that looks like an XP stream patch.
If the user is not on the XP 2.0 patch stream (i.e. the server does not have the patch stream set up OR they are on the 1.0 patch stream) you will get the following error:
{code:java}
java.lang.IllegalStateException: You are attempting to install a patch for the 'jboss-eap-xp-2.0' JBoss EAP XP Patch Stream. However this patch stream is not yet set up in the JBoss EAP server. Run the 'setup' command to enable the patch stream.
at org.jboss.eap.util.xp.patch.stream.manager.ManagerPatchApplyAction.doExecute(ManagerPatchApplyAction.java:29)
at org.jboss.eap.util.xp.patch.stream.manager.ManagerAction.execute(ManagerAction.java:40)
at org.jboss.eap.util.xp.patch.stream.manager.ManagerMain.main(ManagerMain.java:50)
{code}
If they try to install an old XP patch (i.e. 1.0) on a server with the XP 2.0 patch stream set up, they will get this error:
{code:java}
java.lang.IllegalStateException: The JBoss EAP XP patch stream in the patch 'jboss-eap-xp-1.0' does not match the currently enabled JBoss EAP XP patch stream [jboss-eap-xp-2.0]
at org.jboss.eap.util.xp.patch.stream.manager.ManagerPatchApplyAction.doExecute(ManagerPatchApplyAction.java:33)
at org.jboss.eap.util.xp.patch.stream.manager.ManagerAction.execute(ManagerAction.java:40)
at org.jboss.eap.util.xp.patch.stream.manager.ManagerMain.main(ManagerMain.java:50)
{code}
For base patch stream patches I am not doing any validation. Similarly, if it is neither a base nor an XP patch (unlikely but you never know) I am not doing any validation.
> Server can get to state, where XP2 manager thinks both XP1 and XP2 streams are active
> -------------------------------------------------------------------------------------
>
> Key: WFWIP-359
> URL: https://issues.redhat.com/browse/WFWIP-359
> Project: WildFly WIP
> Issue Type: Bug
> Reporter: Martin Svehla
> Assignee: Kabir Khan
> Priority: Major
>
> If I run setup first, manager activates XP2 stream. However, if I then use patch-apply to apply XP1 patch, manager lets this action to happen and then thinks both streams are active.
> {code}
> $ java -jar manager.jar status --jboss-home=jboss-eap-73
> Starting JBoss EAP XP manager (2.0.0.Final-redhat-20200911).
> The JBoss EAP XP patch stream is enabled. You may apply patches both from the JBoss EAP and the JBoss EAP XP patch streams. While enabled the following support policy applies:
> [snip]
> You are currently on JBoss EAP XP 2.
> Enabled patch streams and their cumulative patch ids:
> - Patch stream: 'JBoss EAP'; Cumulative patch id: 'base'
> - Patch stream: 'jboss-eap-xp-2.0'; Cumulative patch id: 'base'
> Available commands in this state are: [remove]
> {code}
> {code}
> $ java -jar manager.jar patch-apply --jboss-home=jboss-eap-7.3 --patch=jboss-eap-xp-1.0.2.GA-redhat-20200911-patch.zip
> {code}
> {code}
> $ java -jar manager.jar status --jboss-home=jboss-eap-7.3
> Starting JBoss EAP XP manager (2.0.0.Final-redhat-20200911).
> The JBoss EAP XP patch stream setup in the JBoss EAP server seems broken.
> Enabled patch streams and their cumulative patch ids:
> - Patch stream: 'JBoss EAP'; Cumulative patch id: 'base'
> - Patch stream: 'jboss-eap-xp-2.0'; Cumulative patch id: 'base'
> - Patch stream: 'jboss-eap-xp-1.0'; Cumulative patch id: 'jboss-eap-xp-1.0.2.CP'
> Available commands in this state are: [remove]
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (WFCORE-1031) PS1 scripts invocation ends with "cannot be loaded because running scripts is disabled on thi s system", affect MS Windows desktop series
by James Perkins (Jira)
[ https://issues.redhat.com/browse/WFCORE-1031?page=com.atlassian.jira.plug... ]
James Perkins closed WFCORE-1031.
---------------------------------
Resolution: Won't Fix
I'm closing this as won't fix as I don't think we want to override these security settings in the script itself.
You can run with the {{-ExecutionPolicy}} argument to override it from the command line. For example:
{code}
powershell -ExecutionPolicy Unrestricted -File bin\standalone.ps1
{code}
> PS1 scripts invocation ends with "cannot be loaded because running scripts is disabled on thi s system", affect MS Windows desktop series
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1031
> URL: https://issues.redhat.com/browse/WFCORE-1031
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Reporter: Rostislav Svoboda
> Priority: Major
>
> PS1 scripts invocation ends with "cannot be loaded because running scripts is disabled on thi s system".
> This was spotted on Windows 10 but it seems it affect more MS Windows desktop series (at leas 8.x too) - based on HiChat discussion.
> When I open PowerShel, enter the bin folder and run .\standalone.ps1 I get this:
> {code}
> .\standalone.ps1 : File E:\jboss-eap-7.0\bin\standalone.ps1 cannot be loaded because running scripts is disabled on this s system.
> For more information, see about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170.
> At line:1 char:1
> + .\standalone.ps1
> + ~~~~~~~~~~~~~~~~
> + CategoryInfo : SecurityError: (:) [], PSSecurityException
> + FullyQualifiedErrorId : UnauthorizedAccess
> {code}
> what "helped" is this:
> Set-ExecutionPolicy RemoteSigned
> but I had to run powershell as administrator because it's changing registry key ... so well, not straightforward usage of ps1 scripts ... Not everybody is able to run in admin mode.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (WFWIP-359) Server can get to state, where XP2 manager thinks both XP1 and XP2 streams are active
by Kabir Khan (Jira)
[ https://issues.redhat.com/browse/WFWIP-359?page=com.atlassian.jira.plugin... ]
Kabir Khan edited comment on WFWIP-359 at 9/24/20 10:45 AM:
------------------------------------------------------------
Enhanced status message:
{code:java}
$java -jar target/jboss-eap-xp-patch-stream-manager-2.0.0.Final-SNAPSHOT.jar status --jboss-home=../xp-patching/jboss-eap-7.3
Starting JBoss EAP XP manager (2.0.0.Final-SNAPSHOT).
The JBoss EAP XP patch stream setup in the JBoss EAP server seems broken.
You have more than one JBoss EAP XP patch stream set up in the JBoss EAP server. You may end up in this situation if you installed the latest XP patch stream and applied patches from an older JBoss EAP XP patch stream. To recover from this you need to run the 'remove' command, run 'setup' again and make sure you only install JBoss EAP XP patch stream patches from the current JBoss EAP XP patch stream.
Enabled patch streams and their cumulative patch ids:
- Patch stream: 'JBoss EAP'; Cumulative patch id: 'base'
- Patch stream: 'jboss-eap-xp-2.0'; Cumulative patch id: 'base'
- Patch stream: 'jboss-eap-xp-1.0'; Cumulative patch id: 'jboss-eap-xp-1.0.0.CP'
Available commands in this state are: [remove]
{code}
[~amehendal] This might be of interest to you. Essentially the issue is that we cannot stop the user from enabling the XP 2.0 patch stream and then applying XP 1.0 patches. Once they apply the XP 1.0 patch, that is also available as a patch stream which makes the installation broken.
I will try to change the XP manager to check the streams from the patch-apply command to avoid this there, but they may still get into this situation by applying patches from the CLI.
was (Author: kabirkhan):
Enhanced status message:
{code:java}
$java -jar target/jboss-eap-xp-patch-stream-manager-2.0.0.Final-SNAPSHOT.jar status --jboss-home=../xp-patching/jboss-eap-7.3
Starting JBoss EAP XP manager (2.0.0.Final-SNAPSHOT).
The JBoss EAP XP patch stream setup in the JBoss EAP server seems broken.
You have more than one JBoss EAP XP patch stream set up in the JBoss EAP server. You may end up in this situation if you installed the latest XP patch stream and applied patches from an older JBoss EAP XP patch stream. To recover from this you need to run the 'remove' command, run 'setup' again and make sure you only install JBoss EAP XP patch stream patches from the current JBoss EAP XP patch stream.
Enabled patch streams and their cumulative patch ids:
- Patch stream: 'JBoss EAP'; Cumulative patch id: 'base'
- Patch stream: 'jboss-eap-xp-2.0'; Cumulative patch id: 'base'
- Patch stream: 'jboss-eap-xp-1.0'; Cumulative patch id: 'jboss-eap-xp-1.0.0.CP'
Available commands in this state are: [remove]
{code}
> Server can get to state, where XP2 manager thinks both XP1 and XP2 streams are active
> -------------------------------------------------------------------------------------
>
> Key: WFWIP-359
> URL: https://issues.redhat.com/browse/WFWIP-359
> Project: WildFly WIP
> Issue Type: Bug
> Reporter: Martin Svehla
> Assignee: Kabir Khan
> Priority: Major
>
> If I run setup first, manager activates XP2 stream. However, if I then use patch-apply to apply XP1 patch, manager lets this action to happen and then thinks both streams are active.
> {code}
> $ java -jar manager.jar status --jboss-home=jboss-eap-73
> Starting JBoss EAP XP manager (2.0.0.Final-redhat-20200911).
> The JBoss EAP XP patch stream is enabled. You may apply patches both from the JBoss EAP and the JBoss EAP XP patch streams. While enabled the following support policy applies:
> [snip]
> You are currently on JBoss EAP XP 2.
> Enabled patch streams and their cumulative patch ids:
> - Patch stream: 'JBoss EAP'; Cumulative patch id: 'base'
> - Patch stream: 'jboss-eap-xp-2.0'; Cumulative patch id: 'base'
> Available commands in this state are: [remove]
> {code}
> {code}
> $ java -jar manager.jar patch-apply --jboss-home=jboss-eap-7.3 --patch=jboss-eap-xp-1.0.2.GA-redhat-20200911-patch.zip
> {code}
> {code}
> $ java -jar manager.jar status --jboss-home=jboss-eap-7.3
> Starting JBoss EAP XP manager (2.0.0.Final-redhat-20200911).
> The JBoss EAP XP patch stream setup in the JBoss EAP server seems broken.
> Enabled patch streams and their cumulative patch ids:
> - Patch stream: 'JBoss EAP'; Cumulative patch id: 'base'
> - Patch stream: 'jboss-eap-xp-2.0'; Cumulative patch id: 'base'
> - Patch stream: 'jboss-eap-xp-1.0'; Cumulative patch id: 'jboss-eap-xp-1.0.2.CP'
> Available commands in this state are: [remove]
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (WFCORE-4674) Custom handlers, formatters and filters cause the server to crash if the log manager is on the boot class path
by James Perkins (Jira)
[ https://issues.redhat.com/browse/WFCORE-4674?page=com.atlassian.jira.plug... ]
James Perkins commented on WFCORE-4674:
---------------------------------------
[~indrajit29] That won't work with WildFly 18. This will only work with WildFly 21. If you're attempting to back port it you'd need to use JBoss Modules 1.10.2.Final. You'd also need to update the scripts because the {{MODULE_OPTS}} in the {{standalone.conf}} is not honored in versions below WildFly 21.
That said are you using another agent? If not there is no need to set the {{jboss-modules.jar}} as an agent.
> Custom handlers, formatters and filters cause the server to crash if the log manager is on the boot class path
> --------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-4674
> URL: https://issues.redhat.com/browse/WFCORE-4674
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Critical
> Labels: OpenShift, jdk11
> Fix For: 13.0.0.Beta1
>
>
> If the log manager is on the boot class path with Java 11, {{-Xbootclasspath/a:jboss-logmanager.jar}}, and a custom handler, formatter or filter is used the server will fail to boot as the log manager can't see the types in jboss-modules. This seems due to the fact that the log manager is on the boot class path and jboss-modules is on the system class path.
> Example exception:
> {code}
> Failed to read or configure the org.jboss.logmanager.LogManager
> java.lang.IllegalArgumentException: Failed to load module "org.jboss.logmanager" for formatter "JSON"
> at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:65)
> at org.jboss.logmanager.config.FormatterConfigurationImpl.<init>(FormatterConfigurationImpl.java:30)
> at org.jboss.logmanager.config.LogContextConfigurationImpl.addFormatterConfiguration(LogContextConfigurationImpl.java:172)
> at org.jboss.logmanager.PropertyConfigurator.configureFormatter(PropertyConfigurator.java:631)
> at org.jboss.logmanager.PropertyConfigurator.configureHandler(PropertyConfigurator.java:701)
> at org.jboss.logmanager.PropertyConfigurator.configureLogger(PropertyConfigurator.java:583)
> at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:521)
> at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:97)
> at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:170)
> at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:132)
> at java.util.logging.LogManager$3.run(LogManager.java:399)
> at java.util.logging.LogManager$3.run(LogManager.java:396)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.util.logging.LogManager.readPrimordialConfiguration(LogManager.java:396)
> at java.util.logging.LogManager.access$800(LogManager.java:145)
> at java.util.logging.LogManager$2.run(LogManager.java:345)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.util.logging.LogManager.ensureLogManagerInitialized(LogManager.java:338)
> at java.util.logging.LogManager.getLogManager(LogManager.java:378)
> at org.jboss.modules.Main.main(Main.java:523)
> Caused by: java.lang.NoClassDefFoundError: org/jboss/modules/ModuleLoader
> at org.jboss.logmanager.config.AbstractPropertyConfiguration$ModuleFinder.getClassLoader(AbstractPropertyConfiguration.java:556)
> at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:63)
> ... 19 more
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years
[JBoss JIRA] (WFWIP-359) Server can get to state, where XP2 manager thinks both XP1 and XP2 streams are active
by Kabir Khan (Jira)
[ https://issues.redhat.com/browse/WFWIP-359?page=com.atlassian.jira.plugin... ]
Kabir Khan commented on WFWIP-359:
----------------------------------
Enhanced status message:
{code:java}
$java -jar target/jboss-eap-xp-patch-stream-manager-2.0.0.Final-SNAPSHOT.jar status --jboss-home=../xp-patching/jboss-eap-7.3
Starting JBoss EAP XP manager (2.0.0.Final-SNAPSHOT).
The JBoss EAP XP patch stream setup in the JBoss EAP server seems broken.
You have more than one JBoss EAP XP patch stream set up in the JBoss EAP server. You may end up in this situation if you installed the latest XP patch stream and applied patches from an older JBoss EAP XP patch stream. To recover from this you need to run the 'remove' command, run 'setup' again and make sure you only install JBoss EAP XP patch stream patches from the current JBoss EAP XP patch stream.
Enabled patch streams and their cumulative patch ids:
- Patch stream: 'JBoss EAP'; Cumulative patch id: 'base'
- Patch stream: 'jboss-eap-xp-2.0'; Cumulative patch id: 'base'
- Patch stream: 'jboss-eap-xp-1.0'; Cumulative patch id: 'jboss-eap-xp-1.0.0.CP'
Available commands in this state are: [remove]
{code}
> Server can get to state, where XP2 manager thinks both XP1 and XP2 streams are active
> -------------------------------------------------------------------------------------
>
> Key: WFWIP-359
> URL: https://issues.redhat.com/browse/WFWIP-359
> Project: WildFly WIP
> Issue Type: Bug
> Reporter: Martin Svehla
> Assignee: Kabir Khan
> Priority: Major
>
> If I run setup first, manager activates XP2 stream. However, if I then use patch-apply to apply XP1 patch, manager lets this action to happen and then thinks both streams are active.
> {code}
> $ java -jar manager.jar status --jboss-home=jboss-eap-73
> Starting JBoss EAP XP manager (2.0.0.Final-redhat-20200911).
> The JBoss EAP XP patch stream is enabled. You may apply patches both from the JBoss EAP and the JBoss EAP XP patch streams. While enabled the following support policy applies:
> [snip]
> You are currently on JBoss EAP XP 2.
> Enabled patch streams and their cumulative patch ids:
> - Patch stream: 'JBoss EAP'; Cumulative patch id: 'base'
> - Patch stream: 'jboss-eap-xp-2.0'; Cumulative patch id: 'base'
> Available commands in this state are: [remove]
> {code}
> {code}
> $ java -jar manager.jar patch-apply --jboss-home=jboss-eap-7.3 --patch=jboss-eap-xp-1.0.2.GA-redhat-20200911-patch.zip
> {code}
> {code}
> $ java -jar manager.jar status --jboss-home=jboss-eap-7.3
> Starting JBoss EAP XP manager (2.0.0.Final-redhat-20200911).
> The JBoss EAP XP patch stream setup in the JBoss EAP server seems broken.
> Enabled patch streams and their cumulative patch ids:
> - Patch stream: 'JBoss EAP'; Cumulative patch id: 'base'
> - Patch stream: 'jboss-eap-xp-2.0'; Cumulative patch id: 'base'
> - Patch stream: 'jboss-eap-xp-1.0'; Cumulative patch id: 'jboss-eap-xp-1.0.2.CP'
> Available commands in this state are: [remove]
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years