[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 updated WFCORE-4674:
----------------------------------
Priority: Major (was: Blocker)
> 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: Major
> Labels: OpenShift, jdk11
>
> 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)
6 years, 5 months
[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 updated WFCORE-4674:
----------------------------------
Priority: Critical (was: Major)
> 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
>
> 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)
6 years, 5 months
[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 updated WFCORE-4674:
----------------------------------
Fix Version/s: (was: 11.0.0.Beta5)
> 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: Blocker
> Labels: OpenShift, jdk11
>
> 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)
6 years, 5 months
[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 updated WFCORE-4674:
----------------------------------
Priority: Blocker (was: Critical)
> 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: Blocker
> Labels: OpenShift, jdk11
> Fix For: 11.0.0.Beta5
>
>
> 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)
6 years, 5 months
[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 updated WFCORE-4674:
----------------------------------
Fix Version/s: 11.0.0.Beta5
> 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: Blocker
> Labels: OpenShift, jdk11
> Fix For: 11.0.0.Beta5
>
>
> 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)
6 years, 5 months
[JBoss JIRA] (DROOLS-3761) [DMN Designer] Data Types - Constraints - Enumeration constraint entry on edit mode - Fix buttons behavior
by Edson Tirelli (Jira)
[ https://issues.redhat.com/browse/DROOLS-3761?page=com.atlassian.jira.plug... ]
Edson Tirelli commented on DROOLS-3761:
---------------------------------------
[~jomarko] ok.
> [DMN Designer] Data Types - Constraints - Enumeration constraint entry on edit mode - Fix buttons behavior
> ----------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3761
> URL: https://issues.redhat.com/browse/DROOLS-3761
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.19.0.Final
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Priority: Minor
> Labels: drools-tools
> Attachments: constraint_unsaved.png, focus_lost.webm, lost_focus_data_types.webm
>
>
> The attached video shows the user interaction with enumeration constraint component. We can see if user fill valid values and clicks somewhere outside of the entry in edit mode, the values are lost. The only way how to save values is to click the *check* button. User should not lost filled in values if he clicks outside of input fields.
> Please compare the same behavior with data types list view component. It means [^focus_lost.webm] vs [^lost_focus_data_types.webm] .
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (JGRP-2423) NPE during unlock operation
by Max Shaposhnyk (Jira)
[ https://issues.redhat.com/browse/JGRP-2423?page=com.atlassian.jira.plugin... ]
Max Shaposhnyk updated JGRP-2423:
---------------------------------
Description:
The following NPE's are appearing in the che.openshift.io production server logs causing the multiple threads to blocking and break down some fuctionality.
ATM we're unable to clearly reproduce issue on local installations (it happens very rarely on local, but quite frequently on prod server)
{noformat}
java.lang.NullPointerException: null
at org.jgroups.util.Owner.compareTo(Owner.java:59)
at org.jgroups.protocols.Locking$ClientLock.compareTo(Locking.java:1142)
at org.jgroups.protocols.Locking$ClientLock.compareTo(Locking.java:942)
at java.util.concurrent.ConcurrentSkipListMap.cpr(ConcurrentSkipListMap.java:655)
at java.util.concurrent.ConcurrentSkipListMap.doPut(ConcurrentSkipListMap.java:835)
at java.util.concurrent.ConcurrentSkipListMap.putIfAbsent(ConcurrentSkipListMap.java:1979)
at java.util.concurrent.ConcurrentSkipListSet.add(ConcurrentSkipListSet.java:241)
at org.jgroups.protocols.Locking$ClientLockTable.addToPendingReleaseRequests(Locking.java:1323)
at org.jgroups.protocols.Locking$ClientLock._unlock(Locking.java:1070)
at org.jgroups.protocols.Locking$ClientLock.unlock(Locking.java:996)
at org.jgroups.protocols.Locking.down(Locking.java:176)
at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:928)
at org.jgroups.JChannel.down(JChannel.java:627)
at org.jgroups.blocks.locking.LockService$LockImpl.unlock(LockService.java:167)
at org.eclipse.che.multiuser.api.distributed.lock.JGroupsWorkspaceLockService$UnlockerImpl.unlock(JGroupsWorkspaceLockService.java:73)
at org.eclipse.che.commons.lang.concurrent.Unlocker.close(Unlocker.java:38)
at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.$closeResource(WorkspaceRuntimes.java:314)
{noformat}
additional links:
[1] https://github.com/eclipse/che/issues/15231
[2] https://issues.redhat.com/browse/JGRP-2299
[3] https://issues.redhat.com/browse/JGRP-2364
[4] https://github.com/eclipse/che/blob/master/assembly/assembly-wsmaster-war...
was:
The following NPE's are appearing in the che.openshift.io production server logs causing the multiple threads to blocking and break down some fuctionality.
ATM we're unable to clearly reproduce issue on local installations (it happens very rarely on local, but quite frequently on prod server)
{noformat}
java.lang.NullPointerException: null
at org.jgroups.util.Owner.compareTo(Owner.java:59)
at org.jgroups.protocols.Locking$ClientLock.compareTo(Locking.java:1142)
at org.jgroups.protocols.Locking$ClientLock.compareTo(Locking.java:942)
at java.util.concurrent.ConcurrentSkipListMap.cpr(ConcurrentSkipListMap.java:655)
at java.util.concurrent.ConcurrentSkipListMap.doPut(ConcurrentSkipListMap.java:835)
at java.util.concurrent.ConcurrentSkipListMap.putIfAbsent(ConcurrentSkipListMap.java:1979)
at java.util.concurrent.ConcurrentSkipListSet.add(ConcurrentSkipListSet.java:241)
at org.jgroups.protocols.Locking$ClientLockTable.addToPendingReleaseRequest
{noformat}
additional links:
[1] https://github.com/eclipse/che/issues/15231
[2] https://issues.redhat.com/browse/JGRP-2299
[3] https://issues.redhat.com/browse/JGRP-2364
[4] https://github.com/eclipse/che/blob/master/assembly/assembly-wsmaster-war...
> NPE during unlock operation
> ---------------------------
>
> Key: JGRP-2423
> URL: https://issues.redhat.com/browse/JGRP-2423
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.1.8
> Reporter: Max Shaposhnyk
> Assignee: Bela Ban
> Priority: Major
>
> The following NPE's are appearing in the che.openshift.io production server logs causing the multiple threads to blocking and break down some fuctionality.
> ATM we're unable to clearly reproduce issue on local installations (it happens very rarely on local, but quite frequently on prod server)
> {noformat}
> java.lang.NullPointerException: null
> at org.jgroups.util.Owner.compareTo(Owner.java:59)
> at org.jgroups.protocols.Locking$ClientLock.compareTo(Locking.java:1142)
> at org.jgroups.protocols.Locking$ClientLock.compareTo(Locking.java:942)
> at java.util.concurrent.ConcurrentSkipListMap.cpr(ConcurrentSkipListMap.java:655)
> at java.util.concurrent.ConcurrentSkipListMap.doPut(ConcurrentSkipListMap.java:835)
> at java.util.concurrent.ConcurrentSkipListMap.putIfAbsent(ConcurrentSkipListMap.java:1979)
> at java.util.concurrent.ConcurrentSkipListSet.add(ConcurrentSkipListSet.java:241)
> at org.jgroups.protocols.Locking$ClientLockTable.addToPendingReleaseRequests(Locking.java:1323)
> at org.jgroups.protocols.Locking$ClientLock._unlock(Locking.java:1070)
> at org.jgroups.protocols.Locking$ClientLock.unlock(Locking.java:996)
> at org.jgroups.protocols.Locking.down(Locking.java:176)
> at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:928)
> at org.jgroups.JChannel.down(JChannel.java:627)
> at org.jgroups.blocks.locking.LockService$LockImpl.unlock(LockService.java:167)
> at org.eclipse.che.multiuser.api.distributed.lock.JGroupsWorkspaceLockService$UnlockerImpl.unlock(JGroupsWorkspaceLockService.java:73)
> at org.eclipse.che.commons.lang.concurrent.Unlocker.close(Unlocker.java:38)
> at org.eclipse.che.api.workspace.server.WorkspaceRuntimes.$closeResource(WorkspaceRuntimes.java:314)
> {noformat}
> additional links:
> [1] https://github.com/eclipse/che/issues/15231
> [2] https://issues.redhat.com/browse/JGRP-2299
> [3] https://issues.redhat.com/browse/JGRP-2364
> [4] https://github.com/eclipse/che/blob/master/assembly/assembly-wsmaster-war...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (JGRP-2423) NPE during unlock operation
by Max Shaposhnyk (Jira)
[ https://issues.redhat.com/browse/JGRP-2423?page=com.atlassian.jira.plugin... ]
Max Shaposhnyk updated JGRP-2423:
---------------------------------
Description:
The following NPE's are appearing in the che.openshift.io production server logs causing the multiple threads to blocking and break down some fuctionality.
ATM we're unable to clearly reproduce issue on local installations (it happens very rarely on local, but quite frequently on prod server)
{noformat}
java.lang.NullPointerException: null
at org.jgroups.util.Owner.compareTo(Owner.java:59)
at org.jgroups.protocols.Locking$ClientLock.compareTo(Locking.java:1142)
at org.jgroups.protocols.Locking$ClientLock.compareTo(Locking.java:942)
at java.util.concurrent.ConcurrentSkipListMap.cpr(ConcurrentSkipListMap.java:655)
at java.util.concurrent.ConcurrentSkipListMap.doPut(ConcurrentSkipListMap.java:835)
at java.util.concurrent.ConcurrentSkipListMap.putIfAbsent(ConcurrentSkipListMap.java:1979)
at java.util.concurrent.ConcurrentSkipListSet.add(ConcurrentSkipListSet.java:241)
at org.jgroups.protocols.Locking$ClientLockTable.addToPendingReleaseRequest
{noformat}
additional links:
[1] https://github.com/eclipse/che/issues/15231
[2] https://issues.redhat.com/browse/JGRP-2299
[3] https://issues.redhat.com/browse/JGRP-2364
[4] https://github.com/eclipse/che/blob/master/assembly/assembly-wsmaster-war...
was:
The following NPE's are appearing in the che.openshift.io production server logs causing the multiple threads to blocking and break down some fuctionality.
ATM we're unable to clearly reproduce ussie on local installations (it happens very rarely on local, but quite frequently on prod server)
{noformat}
java.lang.NullPointerException: null
at org.jgroups.util.Owner.compareTo(Owner.java:59)
at org.jgroups.protocols.Locking$ClientLock.compareTo(Locking.java:1142)
at org.jgroups.protocols.Locking$ClientLock.compareTo(Locking.java:942)
at java.util.concurrent.ConcurrentSkipListMap.cpr(ConcurrentSkipListMap.java:655)
at java.util.concurrent.ConcurrentSkipListMap.doPut(ConcurrentSkipListMap.java:835)
at java.util.concurrent.ConcurrentSkipListMap.putIfAbsent(ConcurrentSkipListMap.java:1979)
at java.util.concurrent.ConcurrentSkipListSet.add(ConcurrentSkipListSet.java:241)
at org.jgroups.protocols.Locking$ClientLockTable.addToPendingReleaseRequest
{noformat}
additional links:
[1] https://github.com/eclipse/che/issues/15231
[2] https://issues.redhat.com/browse/JGRP-2299
[3] https://issues.redhat.com/browse/JGRP-2364
[4] https://github.com/eclipse/che/blob/master/assembly/assembly-wsmaster-war...
> NPE during unlock operation
> ---------------------------
>
> Key: JGRP-2423
> URL: https://issues.redhat.com/browse/JGRP-2423
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.1.8
> Reporter: Max Shaposhnyk
> Assignee: Bela Ban
> Priority: Major
>
> The following NPE's are appearing in the che.openshift.io production server logs causing the multiple threads to blocking and break down some fuctionality.
> ATM we're unable to clearly reproduce issue on local installations (it happens very rarely on local, but quite frequently on prod server)
> {noformat}
> java.lang.NullPointerException: null
> at org.jgroups.util.Owner.compareTo(Owner.java:59)
> at org.jgroups.protocols.Locking$ClientLock.compareTo(Locking.java:1142)
> at org.jgroups.protocols.Locking$ClientLock.compareTo(Locking.java:942)
> at java.util.concurrent.ConcurrentSkipListMap.cpr(ConcurrentSkipListMap.java:655)
> at java.util.concurrent.ConcurrentSkipListMap.doPut(ConcurrentSkipListMap.java:835)
> at java.util.concurrent.ConcurrentSkipListMap.putIfAbsent(ConcurrentSkipListMap.java:1979)
> at java.util.concurrent.ConcurrentSkipListSet.add(ConcurrentSkipListSet.java:241)
> at org.jgroups.protocols.Locking$ClientLockTable.addToPendingReleaseRequest
> {noformat}
> additional links:
> [1] https://github.com/eclipse/che/issues/15231
> [2] https://issues.redhat.com/browse/JGRP-2299
> [3] https://issues.redhat.com/browse/JGRP-2364
> [4] https://github.com/eclipse/che/blob/master/assembly/assembly-wsmaster-war...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months
[JBoss JIRA] (JGRP-2423) NPE during unlock operation
by Max Shaposhnyk (Jira)
[ https://issues.redhat.com/browse/JGRP-2423?page=com.atlassian.jira.plugin... ]
Max Shaposhnyk updated JGRP-2423:
---------------------------------
Description:
The following NPE's are appearing in the che.openshift.io production server logs causing the multiple threads to blocking and break down some fuctionality.
ATM we're unable to clearly reproduce ussie on local installations (it happens very rarely on local, but quite frequently on prod server)
{noformat}
java.lang.NullPointerException: null
at org.jgroups.util.Owner.compareTo(Owner.java:59)
at org.jgroups.protocols.Locking$ClientLock.compareTo(Locking.java:1142)
at org.jgroups.protocols.Locking$ClientLock.compareTo(Locking.java:942)
at java.util.concurrent.ConcurrentSkipListMap.cpr(ConcurrentSkipListMap.java:655)
at java.util.concurrent.ConcurrentSkipListMap.doPut(ConcurrentSkipListMap.java:835)
at java.util.concurrent.ConcurrentSkipListMap.putIfAbsent(ConcurrentSkipListMap.java:1979)
at java.util.concurrent.ConcurrentSkipListSet.add(ConcurrentSkipListSet.java:241)
at org.jgroups.protocols.Locking$ClientLockTable.addToPendingReleaseRequest
{noformat}
additional links:
[1] https://github.com/eclipse/che/issues/15231
[2] https://issues.redhat.com/browse/JGRP-2299
[3] https://issues.redhat.com/browse/JGRP-2364
[4] https://github.com/eclipse/che/blob/master/assembly/assembly-wsmaster-war...
was:
The following NPE's are apperaing in the che.openshift.io production server logs causing the multiple threads to blocking and break down some fuctionality.
{noformat}
java.lang.NullPointerException: null
at org.jgroups.util.Owner.compareTo(Owner.java:59)
at org.jgroups.protocols.Locking$ClientLock.compareTo(Locking.java:1142)
at org.jgroups.protocols.Locking$ClientLock.compareTo(Locking.java:942)
at java.util.concurrent.ConcurrentSkipListMap.cpr(ConcurrentSkipListMap.java:655)
at java.util.concurrent.ConcurrentSkipListMap.doPut(ConcurrentSkipListMap.java:835)
at java.util.concurrent.ConcurrentSkipListMap.putIfAbsent(ConcurrentSkipListMap.java:1979)
at java.util.concurrent.ConcurrentSkipListSet.add(ConcurrentSkipListSet.java:241)
at org.jgroups.protocols.Locking$ClientLockTable.addToPendingReleaseRequest
{noformat}
additional links:
[1] https://github.com/eclipse/che/issues/15231
[2] https://issues.redhat.com/browse/JGRP-2299
[3] https://issues.redhat.com/browse/JGRP-2364
[4] https://github.com/eclipse/che/blob/master/assembly/assembly-wsmaster-war...
> NPE during unlock operation
> ---------------------------
>
> Key: JGRP-2423
> URL: https://issues.redhat.com/browse/JGRP-2423
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.1.8
> Reporter: Max Shaposhnyk
> Assignee: Bela Ban
> Priority: Major
>
> The following NPE's are appearing in the che.openshift.io production server logs causing the multiple threads to blocking and break down some fuctionality.
> ATM we're unable to clearly reproduce ussie on local installations (it happens very rarely on local, but quite frequently on prod server)
> {noformat}
> java.lang.NullPointerException: null
> at org.jgroups.util.Owner.compareTo(Owner.java:59)
> at org.jgroups.protocols.Locking$ClientLock.compareTo(Locking.java:1142)
> at org.jgroups.protocols.Locking$ClientLock.compareTo(Locking.java:942)
> at java.util.concurrent.ConcurrentSkipListMap.cpr(ConcurrentSkipListMap.java:655)
> at java.util.concurrent.ConcurrentSkipListMap.doPut(ConcurrentSkipListMap.java:835)
> at java.util.concurrent.ConcurrentSkipListMap.putIfAbsent(ConcurrentSkipListMap.java:1979)
> at java.util.concurrent.ConcurrentSkipListSet.add(ConcurrentSkipListSet.java:241)
> at org.jgroups.protocols.Locking$ClientLockTable.addToPendingReleaseRequest
> {noformat}
> additional links:
> [1] https://github.com/eclipse/che/issues/15231
> [2] https://issues.redhat.com/browse/JGRP-2299
> [3] https://issues.redhat.com/browse/JGRP-2364
> [4] https://github.com/eclipse/che/blob/master/assembly/assembly-wsmaster-war...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months