[JBoss JIRA] (JGRP-2489) TcpConnection.Receiver#run should use logger to handle exception rather than rely on the UncaughtExceptionHandler
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2489?page=com.atlassian.jira.plugin... ]
Bela Ban commented on JGRP-2489:
--------------------------------
The PR is against master, do you want to submit another one against 4.x?
> TcpConnection.Receiver#run should use logger to handle exception rather than rely on the UncaughtExceptionHandler
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JGRP-2489
> URL: https://issues.redhat.com/browse/JGRP-2489
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.2.4
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Minor
> Fix For: 4.2.5
>
>
> An example of an exception being non-standardly thusly logged to stderr:
> {code}
> [0m[31m15:09:28,663 ERROR [stderr] (Connection.Receiver [10.128.3.125:7600 - 10.131.0.184:32825]-11,ee,hsc-1-2d7n4) Exception in thread "Connection.Receiver [10.128.3.125:7600 - 10.131.0.184:32825]-11,ee,hsc-1-2d7n4" java.lang.RuntimeException: failed handling message from 10.131.0.184:7600: java.io.IOException: Stream closed
> [0m[31m15:09:28,663 ERROR [stderr] (Connection.Receiver [10.128.3.125:7600 - 10.131.0.184:32825]-11,ee,hsc-1-2d7n4) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.blocks.cs.TcpConnection$Receiver.run(TcpConnection.java:309)
> [0m[31m15:09:28,663 ERROR [stderr] (Connection.Receiver [10.128.3.125:7600 - 10.131.0.184:32825]-11,ee,hsc-1-2d7n4) at org.jboss.as.clustering.common@7.4.0.CD20-redhat-00001//org.jboss.as.clustering.context.ContextReferenceExecutor.execute(ContextReferenceExecutor.java:49)
> [0m[31m15:09:28,663 ERROR [stderr] (Connection.Receiver [10.128.3.125:7600 - 10.131.0.184:32825]-11,ee,hsc-1-2d7n4) at org.jboss.as.clustering.common@7.4.0.CD20-redhat-00001//org.jboss.as.clustering.context.ContextualExecutor$1.run(ContextualExecutor.java:70)
> [0m[31m15:09:28,663 ERROR [stderr] (Connection.Receiver [10.128.3.125:7600 - 10.131.0.184:32825]-11,ee,hsc-1-2d7n4) at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (JGRP-2489) TcpConnection.Receiver#run should use logger to handle exception rather than rely on the UncaughtExceptionHandler
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2489?page=com.atlassian.jira.plugin... ]
Bela Ban updated JGRP-2489:
---------------------------
Fix Version/s: 5.0.0.Final
> TcpConnection.Receiver#run should use logger to handle exception rather than rely on the UncaughtExceptionHandler
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JGRP-2489
> URL: https://issues.redhat.com/browse/JGRP-2489
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.2.4
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Minor
> Fix For: 4.2.5, 5.0.0.Final
>
>
> An example of an exception being non-standardly thusly logged to stderr:
> {code}
> [0m[31m15:09:28,663 ERROR [stderr] (Connection.Receiver [10.128.3.125:7600 - 10.131.0.184:32825]-11,ee,hsc-1-2d7n4) Exception in thread "Connection.Receiver [10.128.3.125:7600 - 10.131.0.184:32825]-11,ee,hsc-1-2d7n4" java.lang.RuntimeException: failed handling message from 10.131.0.184:7600: java.io.IOException: Stream closed
> [0m[31m15:09:28,663 ERROR [stderr] (Connection.Receiver [10.128.3.125:7600 - 10.131.0.184:32825]-11,ee,hsc-1-2d7n4) at org.jgroups@4.2.4.Final-redhat-00001//org.jgroups.blocks.cs.TcpConnection$Receiver.run(TcpConnection.java:309)
> [0m[31m15:09:28,663 ERROR [stderr] (Connection.Receiver [10.128.3.125:7600 - 10.131.0.184:32825]-11,ee,hsc-1-2d7n4) at org.jboss.as.clustering.common@7.4.0.CD20-redhat-00001//org.jboss.as.clustering.context.ContextReferenceExecutor.execute(ContextReferenceExecutor.java:49)
> [0m[31m15:09:28,663 ERROR [stderr] (Connection.Receiver [10.128.3.125:7600 - 10.131.0.184:32825]-11,ee,hsc-1-2d7n4) at org.jboss.as.clustering.common@7.4.0.CD20-redhat-00001//org.jboss.as.clustering.context.ContextualExecutor$1.run(ContextualExecutor.java:70)
> [0m[31m15:09:28,663 ERROR [stderr] (Connection.Receiver [10.128.3.125:7600 - 10.131.0.184:32825]-11,ee,hsc-1-2d7n4) at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFCORE-5053) Prometheus JMX exporter jar, stops starting the wildfly server.
by Rakesh Kumar Shah (Jira)
[ https://issues.redhat.com/browse/WFCORE-5053?page=com.atlassian.jira.plug... ]
Rakesh Kumar Shah commented on WFCORE-5053:
-------------------------------------------
Alright James. Can you expedite the fix or workaround? We are actually blocked from monitoring JMX beans.
> Prometheus JMX exporter jar, stops starting the wildfly server.
> ----------------------------------------------------------------
>
> Key: WFCORE-5053
> URL: https://issues.redhat.com/browse/WFCORE-5053
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: Rakesh Kumar Shah
> Assignee: James Perkins
> Priority: Major
>
> Trying to integrate the Prometheus JMX exporter with wildfly. After spending lot of time and work around it, wildfly is not starting. It throws following exception.
> {code}
> java.lang.ClassNotFoundException: org.jboss.logmanager.LogManager
> at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583)
> at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> at java.logging/java.util.logging.LogManager$1.run(LogManager.java:239)
> at java.logging/java.util.logging.LogManager$1.run(LogManager.java:223)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at java.logging/java.util.logging.LogManager.<clinit>(LogManager.java:223)
> at java.logging/java.util.logging.Logger.demandLogger(Logger.java:648)
> at java.logging/java.util.logging.Logger.getLogger(Logger.java:717)
> at java.logging/java.util.logging.Logger.getLogger(Logger.java:701)
> at io.prometheus.jmx.shaded.io.prometheus.jmx.JmxCollector.<clinit>(JmxCollector.java:39)
> at io.prometheus.jmx.shaded.io.prometheus.jmx.JavaAgent.premain(JavaAgent.java:29)
> 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 java.instrument/sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:513)
> at java.instrument/sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:525)
> WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager
> Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logmanager/Level
> at java.base/java.lang.Class.forName0(Native Method)
> at java.base/java.lang.Class.forName(Class.java:398)
> at org.jboss.modules.Module.run(Module.java:340)
> at org.jboss.modules.Module.run(Module.java:320)
> at org.jboss.modules.Main.main(Main.java:617)
> Caused by: java.lang.ClassNotFoundException: org.jboss.logmanager.Level
> at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583)
> at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> at org.jboss.modules.JDKSpecific.getSystemClass(JDKSpecific.java:183)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:395)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFCORE-5054) Allows to load bootable JAR provider during boot
by Jean Francois Denise (Jira)
Jean Francois Denise created WFCORE-5054:
--------------------------------------------
Summary: Allows to load bootable JAR provider during boot
Key: WFCORE-5054
URL: https://issues.redhat.com/browse/WFCORE-5054
Project: WildFly Core
Issue Type: Enhancement
Reporter: Jean Francois Denise
Assignee: Jean Francois Denise
The bootable JAR boot should be able to load provider during boot. Such provider can be injected by the wildfly-jar-maven-plugin.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFLY-13433) Improve capability support in EJB3 subsystem
by Richard Achmatowicz (Jira)
[ https://issues.redhat.com/browse/WFLY-13433?page=com.atlassian.jira.plugi... ]
Richard Achmatowicz edited comment on WFLY-13433 at 7/15/20 4:20 PM:
---------------------------------------------------------------------
Added more resources, changed the branch: [https://github.com/rachmatowicz/wildfly/tree/WFLY-13433]
Resources now completed:
{noformat}
ApplicationSecurityDomainDefinition
CacheFactoryResourceDefinition
PassivationStoreResourceDefinition
EJB3RemoteResourceDefinition
EJB3SubsystemRootResourceDefintion
IdentityResourceDefinition
EJB3AsyncResourceDefinition
MDBDeliveryGroupResourceDefinition
{noformat}
PassivationStoreResoureDefinition integrates with Capability classes from org.wildfly.clustering.controller.
was (Author: rachmato):
Added more resources, changed the branch: [https://github.com/rachmatowicz/wildfly/tree/WFLY-13433]
Resources now completed:
{noformat}
ApplicationSecurityDomainDefinition
CacheFactoryResourceDefinition
PassivationStoreResourceDefinition
EJB3RemoteResourceDefinition
EJB3SubsystemRootResourceDefintion
IdentityResourceDefinition{noformat}
PassivationStoreResoureDefinition integrates with Capability classes from org.wildfly.clustering.controller.
> Improve capability support in EJB3 subsystem
> --------------------------------------------
>
> Key: WFLY-13433
> URL: https://issues.redhat.com/browse/WFLY-13433
> Project: WildFly
> Issue Type: Enhancement
> Components: EJB
> Affects Versions: 20.0.0.Beta1
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Priority: Major
>
> Survey all external subsystem dependencies and introduce capability based dependencies where required.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFLY-13433) Improve capability support in EJB3 subsystem
by Richard Achmatowicz (Jira)
[ https://issues.redhat.com/browse/WFLY-13433?page=com.atlassian.jira.plugi... ]
Richard Achmatowicz edited comment on WFLY-13433 at 7/15/20 4:20 PM:
---------------------------------------------------------------------
Added more resources, changed the branch: [https://github.com/rachmatowicz/wildfly/tree/WFLY-13433]
Resources now completed:
{noformat}
ApplicationSecurityDomainDefinition
CacheFactoryResourceDefinition
PassivationStoreResourceDefinition
EJB3RemoteResourceDefinition
EJB3SubsystemRootResourceDefintion
IdentityResourceDefinition
EJB3AsyncResourceDefinition
MDBDeliveryGroupResourceDefinition
{noformat}
PassivationStoreResoureDefinition integrates with Capability classes from org.wildfly.clustering.controller.
was (Author: rachmato):
Added more resources, changed the branch: [https://github.com/rachmatowicz/wildfly/tree/WFLY-13433]
Resources now completed:
{noformat}
ApplicationSecurityDomainDefinition
CacheFactoryResourceDefinition
PassivationStoreResourceDefinition
EJB3RemoteResourceDefinition
EJB3SubsystemRootResourceDefintion
IdentityResourceDefinition
EJB3AsyncResourceDefinition
MDBDeliveryGroupResourceDefinition
{noformat}
PassivationStoreResoureDefinition integrates with Capability classes from org.wildfly.clustering.controller.
> Improve capability support in EJB3 subsystem
> --------------------------------------------
>
> Key: WFLY-13433
> URL: https://issues.redhat.com/browse/WFLY-13433
> Project: WildFly
> Issue Type: Enhancement
> Components: EJB
> Affects Versions: 20.0.0.Beta1
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Priority: Major
>
> Survey all external subsystem dependencies and introduce capability based dependencies where required.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFLY-13433) Improve capability support in EJB3 subsystem
by Richard Achmatowicz (Jira)
[ https://issues.redhat.com/browse/WFLY-13433?page=com.atlassian.jira.plugi... ]
Richard Achmatowicz commented on WFLY-13433:
--------------------------------------------
Two more resources:
{noformat}
EJB3IIOPResourceDefinition
RemotingProfileResourceDefinition
{noformat}
>From my notes, these are all of the resources defined in the EJB3 subsystem.
There are two cases where I did not add/make use of capability references and left legacy service names in place:
* when an EJB3 subsystem makes use of an external dependency from subsystem EXT but subsystem EXT has not been converted to use capabilities (there are a number of these...transactions, IIOP, Service module loader, ... )
* when the service names referenced are associated with deployment-specific services internal to the EJB3 subsystem
This could benefit from a review as it's likely I have missed some things. I'll review myself in a day or two.
> Improve capability support in EJB3 subsystem
> --------------------------------------------
>
> Key: WFLY-13433
> URL: https://issues.redhat.com/browse/WFLY-13433
> Project: WildFly
> Issue Type: Enhancement
> Components: EJB
> Affects Versions: 20.0.0.Beta1
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Priority: Major
>
> Survey all external subsystem dependencies and introduce capability based dependencies where required.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (DROOLS-5494) Uploading Excel Spreadsheets using OpenJDK 11
by Ben-Johan van der Walt (Jira)
[ https://issues.redhat.com/browse/DROOLS-5494?page=com.atlassian.jira.plug... ]
Ben-Johan van der Walt commented on DROOLS-5494:
------------------------------------------------
Thanks Mario!
> Uploading Excel Spreadsheets using OpenJDK 11
> ---------------------------------------------
>
> Key: DROOLS-5494
> URL: https://issues.redhat.com/browse/DROOLS-5494
> Project: Drools
> Issue Type: Bug
> Components: decision tables
> Affects Versions: 7.33.0.Final
> Reporter: Ben-Johan van der Walt
> Assignee: Mario Fusco
> Priority: Major
> Fix For: 7.35.0.Final
>
>
> Using Drools version 7.33.0.Final as well as 7.33.0.Final-redhat-00002.
> When trying to upload an Excel Spreadsheet of type .xlsx I am getting a lot of error trying to upload the file. I am able to import the Excel file via the import Asset button, but not by using the "Add Asset" button and adding a new Spreadsheet asset and then uploading the Excel file.
> So I am using OpenJDK 11.0.7 and I think that is the reason for the errors.
> There are a lot of issues with the libraries from org.apache.poi version 3.17 (e.g. poi-3.17.jar, poi-ooxml-3.17.jar and poi-ooxml-schemas-3.17.jar) which are all part of the drools or decision-central war file. Using OpenJDK you have to use at least version 4.1.1 and update a few other dependancies like commons-compress-1.19.jar and xmlbeans-3.1.0.jar to get it to work.
>
> I do not have a specific excel spreadsheet, but any spreadsheet of type .xlsx will cause the error when trying to upload it.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (DROOLS-5494) Uploading Excel Spreadsheets using OpenJDK 11
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-5494?page=com.atlassian.jira.plug... ]
Mario Fusco resolved DROOLS-5494.
---------------------------------
Fix Version/s: 7.35.0.Final
Resolution: Done
Fixed by https://github.com/kiegroup/droolsjbpm-build-bootstrap/commit/ac340870647...
> Uploading Excel Spreadsheets using OpenJDK 11
> ---------------------------------------------
>
> Key: DROOLS-5494
> URL: https://issues.redhat.com/browse/DROOLS-5494
> Project: Drools
> Issue Type: Bug
> Components: decision tables
> Affects Versions: 7.33.0.Final
> Reporter: Ben-Johan van der Walt
> Assignee: Mario Fusco
> Priority: Major
> Fix For: 7.35.0.Final
>
>
> Using Drools version 7.33.0.Final as well as 7.33.0.Final-redhat-00002.
> When trying to upload an Excel Spreadsheet of type .xlsx I am getting a lot of error trying to upload the file. I am able to import the Excel file via the import Asset button, but not by using the "Add Asset" button and adding a new Spreadsheet asset and then uploading the Excel file.
> So I am using OpenJDK 11.0.7 and I think that is the reason for the errors.
> There are a lot of issues with the libraries from org.apache.poi version 3.17 (e.g. poi-3.17.jar, poi-ooxml-3.17.jar and poi-ooxml-schemas-3.17.jar) which are all part of the drools or decision-central war file. Using OpenJDK you have to use at least version 4.1.1 and update a few other dependancies like commons-compress-1.19.jar and xmlbeans-3.1.0.jar to get it to work.
>
> I do not have a specific excel spreadsheet, but any spreadsheet of type .xlsx will cause the error when trying to upload it.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months