[JBoss JIRA] (DROOLS-4430) Unable to find class 'ksLoggers.newFileLogger'
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-4430?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-4430:
--------------------------------
Sprint: 2019 Week 35-37
> Unable to find class 'ksLoggers.newFileLogger'
> ----------------------------------------------
>
> Key: DROOLS-4430
> URL: https://issues.jboss.org/browse/DROOLS-4430
> Project: Drools
> Issue Type: Bug
> Environment: Windows 1 w/ JDK-12.02, Eclipse
> Reporter: Stephen Kaisler
> Assignee: Mario Fusco
> Priority: Major
> Attachments: MsgreClass NotFound Exception.docx, MsgreClass NotFound Exception.docx
>
>
> java.lang.ClassNotFoundException: Unable to find class 'ksLoggers.newFileLogger'
> at org.kie.soup.project.datamodel.commons.types.ClassTypeResolver.resolveType(ClassTypeResolver.java:268)
> at org.kie.soup.project.datamodel.commons.types.ClassTypeResolver.resolveType(ClassTypeResolver.java:153)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.processGlobals(KnowledgeBuilderImpl.java:1686)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.processOtherDeclarations(KnowledgeBuilderImpl.java:1668)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.buildOtherDeclarations(KnowledgeBuilderImpl.java:2511)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.buildPackagesWithoutRules(KnowledgeBuilderImpl.java:2458)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.buildPackages(KnowledgeBuilderImpl.java:2449)
> at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.build(CompositeKnowledgeBuilderImpl.java:108)
> at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.build(CompositeKnowledgeBuilderImpl.java:100)
> at org.drools.compiler.kie.builder.impl.AbstractKieProject.buildKnowledgePackages(AbstractKieProject.java:261)
> at org.drools.compiler.kie.builder.impl.AbstractKieModule.buildKnowledgePackages(AbstractKieModule.java:201)
> at org.drools.compiler.kie.builder.impl.AbstractKieModule.createKieBase(AbstractKieModule.java:215)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.createKieBase(KieContainerImpl.java:406)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:374)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBaseFromKieSessionModel(KieContainerImpl.java:575)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:551)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:458)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:441)
> at CAKnowledgeBase.CAKB.initializeRuleEngine(CAKB.java:269)
> at chemistryAdvisor.ChemistryAdvisor.main(ChemistryAdvisor.java:217)
> SOurce code:
> try
> {
> // define a KieModule
> //KieModuleModel CAproj = ks.newKieModuleModel();
>
> // get a container for the KieBases
> chemistryAdvisorSession = CAks.newKieClasspathContainer().newKieSession();
> if (debugKB)
> {
> System.out.println("\ninitialized KieContainer:\t" + CAContainer);
> }
> }
> catch (NoClassDefFoundError fe)
> {
> fe.printStackTrace();
> }
> where CAks is a KieSession.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-4454) NullPointerException at org.drools.core.phreak.SegmentUtilities.createChildSegments with a removed rule in updateToVersion
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-4454?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-4454:
--------------------------------
Sprint: 2019 Week 35-37
> NullPointerException at org.drools.core.phreak.SegmentUtilities.createChildSegments with a removed rule in updateToVersion
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-4454
> URL: https://issues.jboss.org/browse/DROOLS-4454
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.25.0.Final
> Reporter: Martin Weiler
> Assignee: Mario Fusco
> Priority: Major
> Labels: support
> Attachments: DROOLS-4454-reproducer.zip
>
>
> After an updateToVersion where a rule is removed from the KieBase,
> fireAllRules fails with the exception below.
> Note: This happens with versions 6.4.0.Final-redhat-6 and later
> (including latest master)
> The following commit seems to be causing the NPE:
> https://issues.jboss.org/browse/DROOLS-1147
> https://github.com/kiegroup/drools/commit/8897a8dcccce10a93803d7073ecf499...
> {noformat}
> java.lang.NullPointerException
> at org.drools.core.phreak.SegmentUtilities.createChildSegments(SegmentUtilities.java:305)
> at org.drools.core.reteoo.LeftInputAdapterNode.doInsertObject(LeftInputAdapterNode.java:185)
> at org.drools.core.reteoo.LeftInputAdapterNode.assertObject(LeftInputAdapterNode.java:169)
> at org.drools.core.reteoo.SingleObjectSinkAdapter.propagateAssertObject(SingleObjectSinkAdapter.java:63)
> at org.drools.core.reteoo.ObjectTypeNode.propagateAssert(ObjectTypeNode.java:304)
> at org.drools.core.phreak.PropagationEntry$Insert.execute(PropagationEntry.java:120)
> at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:82)
> at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:77)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.flushPropagations(StatefulKnowledgeSessionImpl.java:2044)
> at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1334)
> at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1288)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1333)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1324)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1305)
> at CreateChildSegmentNpeTest.fireAllRules(CreateChildSegmentNpeTest.java:91)
> at CreateChildSegmentNpeTest.reproducer(CreateChildSegmentNpeTest.java:126)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-4463) Drools and KIE are too chatty on INFO logging (= default for spring-boot).
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-4463?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-4463:
--------------------------------
Sprint: 2019 Week 35-37
> Drools and KIE are too chatty on INFO logging (= default for spring-boot).
> --------------------------------------------------------------------------
>
> Key: DROOLS-4463
> URL: https://issues.jboss.org/browse/DROOLS-4463
> Project: Drools
> Issue Type: Enhancement
> Components: core engine
> Reporter: Geoffrey De Smet
> Assignee: Mario Fusco
> Priority: Critical
> Attachments: Selection_115.png
>
>
> This makes us look like bloatware on spring-boot:
> !Selection_115.png|thumbnail!
> Can we make all these log messages DEBUG level?
> No user that looks at the logs cares that we're reading a kie.conf file or adding a kie service. Actually, let's make them TRACE :)
> Drools should have zero or one info message when creating a kie factory and kie session. Anything more is unacceptable.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-12427) Missing io.smallrye.health dependency on org.jboss.logging
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-12427?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-12427:
------------------------------------
Description:
I happened to notice this in a server log of a CI job:
{code}
16:03:53,351 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-000119: Not generating any bean definitions from io.smallrye.health.SmallRyeHealthReporter because of underlying class loading error: Type org.jboss.logging.Logger from [Module "io.smallrye.health" version 1.0.2 from local module loader @4909b8da (finder: local module finder @3a03464 (roots: C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\wildfly\modules,C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\wildfly\modules\system\layers\base,C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\modules))] not found. If this is unexpected, enable DEBUG logging to see the full error.
{code}
The io.smallrye:smallrye-health-2.0:1.0.2 pom shows a dependency on JBoss Logging but the module.xml for its module does not.
was:
I happened to notice this in a server log of a CI job:
{code}
16:03:53,351 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-000119: Not generating any bean definitions from io.smallrye.health.SmallRyeHealthReporter because of underlying class loading error: Type org.jboss.logging.Logger from [Module "io.smallrye.health" version 1.0.2 from local module loader @4909b8da (finder: local module finder @3a03464 (roots: C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\wildfly\modules,C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\wildfly\modules\system\layers\base,C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\modules))] not found. If this is unexpected, enable DEBUG logging to see the full error.
{code}
The io.smallrye:smallrye-health-2.0:1.0.2 pom shows a dependency on JBoss Logging but the module.xml for its module does not.
An examination of the other io.smallrye modules shows the same problem in pom vs module.xml difference for config as well.
> Missing io.smallrye.health dependency on org.jboss.logging
> ----------------------------------------------------------
>
> Key: WFLY-12427
> URL: https://issues.jboss.org/browse/WFLY-12427
> Project: WildFly
> Issue Type: Bug
> Components: MP Health
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Major
>
> I happened to notice this in a server log of a CI job:
> {code}
> 16:03:53,351 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-000119: Not generating any bean definitions from io.smallrye.health.SmallRyeHealthReporter because of underlying class loading error: Type org.jboss.logging.Logger from [Module "io.smallrye.health" version 1.0.2 from local module loader @4909b8da (finder: local module finder @3a03464 (roots: C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\wildfly\modules,C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\wildfly\modules\system\layers\base,C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\modules))] not found. If this is unexpected, enable DEBUG logging to see the full error.
> {code}
> The io.smallrye:smallrye-health-2.0:1.0.2 pom shows a dependency on JBoss Logging but the module.xml for its module does not.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-12427) Missing io.smallrye.health dependency on org.jboss.logging
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-12427?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-12427:
------------------------------------
Summary: Missing io.smallrye.health dependency on org.jboss.logging (was: Missing io.smallrye.health and config dependency on org.jboss.logging)
> Missing io.smallrye.health dependency on org.jboss.logging
> ----------------------------------------------------------
>
> Key: WFLY-12427
> URL: https://issues.jboss.org/browse/WFLY-12427
> Project: WildFly
> Issue Type: Bug
> Components: MP Health
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Major
>
> I happened to notice this in a server log of a CI job:
> {code}
> 16:03:53,351 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-000119: Not generating any bean definitions from io.smallrye.health.SmallRyeHealthReporter because of underlying class loading error: Type org.jboss.logging.Logger from [Module "io.smallrye.health" version 1.0.2 from local module loader @4909b8da (finder: local module finder @3a03464 (roots: C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\wildfly\modules,C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\wildfly\modules\system\layers\base,C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\modules))] not found. If this is unexpected, enable DEBUG logging to see the full error.
> {code}
> The io.smallrye:smallrye-health-2.0:1.0.2 pom shows a dependency on JBoss Logging but the module.xml for its module does not.
> An examination of the other io.smallrye modules shows the same problem in pom vs module.xml difference for config as well.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFCORE-4623) Intermittent failures in IdentityOperationsTestCase
by Brian Stansberry (Jira)
Brian Stansberry created WFCORE-4623:
----------------------------------------
Summary: Intermittent failures in IdentityOperationsTestCase
Key: WFCORE-4623
URL: https://issues.jboss.org/browse/WFCORE-4623
Project: WildFly Core
Issue Type: Bug
Components: Security
Reporter: Brian Stansberry
Assignee: Darran Lofthouse
IdentityOperationsTestCase fails intermittently, producing a set of 21 failures. When this happens the entire job seems to time out.
https://ci.wildfly.org/project.html?projectId=WildFlyCore_PullRequest&bui...
The problem seems to involve a server not being able to reach MSC stability during boot and then a lot of problems trying to roll back the boot op. The latter are kind of noise, i.e. the stack trace bit in the snippet below. The key thing is the failure to get MSC stability.
{code}
17:11:15,658 INFO (main) [org.wildfly.security] <Version.java:55> ELY00001: WildFly Elytron version 1.10.0.CR5
17:11:15,878 INFO (main) [org.jboss.msc] <ServiceContainerImpl.java:90> JBoss MSC version 1.4.8.Final
17:11:15,893 INFO (main) [org.jboss.threads] <Version.java:52> JBoss Threads version 2.3.3.Final
17:11:16,027 TRACE (main) [org.wildfly.security] <SecurityDomain.java:1056> Building security domain with defaultRealmName Empty.
17:11:16,037 TRACE (main) [org.wildfly.security] <SecurityDomain.java:708> Role mapping: principal [anonymous] -> decoded roles [] -> realm mapped roles [] -> domain mapped roles []
17:11:16,312 TRACE (MSC service thread 1-2) [org.wildfly.extension.elytron] <ProviderDefinitions.java:238> Loaded providers [WildFlyElytron version 1.0]
17:16:16,313 ERROR (Controller Boot Thread) [org.jboss.as.controller.management-operation] <OperationContextImpl.java:489> WFLYCTL0348: Timeout after [300] seconds waiting for service container stability. Operation will roll back. Step that first updated the service container was 'add' at address '[("path" => "jboss.server.data.dir")]'
17:16:21,322 ERROR (Controller Boot Thread) [org.jboss.as.controller.management-operation] <AbstractOperationContext.java:1525> WFLYCTL0190: Step handler org.jboss.as.controller.AbstractAddStepHandler$1@b0b65f for operation add at address [
("subsystem" => "elytron"),
("filesystem-realm" => "FileSystemRealm")
] failed handling operation rollback -- java.util.concurrent.TimeoutException: java.util.concurrent.TimeoutException
at org.jboss.as.controller.OperationContextImpl.waitForRemovals(OperationContextImpl.java:523)
at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1518)
at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1472)
at org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:1455)
at org.jboss.as.controller.AbstractOperationContext$Step.access$400(AbstractOperationContext.java:1319)
at org.jboss.as.controller.AbstractOperationContext.executeResultHandlerPhase(AbstractOperationContext.java:876)
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:726)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467)
at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1413)
at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:495)
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-12413) IllegalStateException when bad metrics scope requested
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-12413?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-12413:
-----------------------------------------
I filed issue https://github.com/smallrye/smallrye-metrics/pull/167 and submitted PRs https://github.com/smallrye/smallrye-metrics/pull/168 and https://github.com/smallrye/smallrye-metrics/pull/169 for the smallrye-metrics master and 2.1.x branches.
> IllegalStateException when bad metrics scope requested
> ------------------------------------------------------
>
> Key: WFLY-12413
> URL: https://issues.jboss.org/browse/WFLY-12413
> Project: WildFly
> Issue Type: Bug
> Components: MP Metrics
> Reporter: Jan Stourac
> Assignee: Jeff Mesnil
> Priority: Major
>
> With WildFly build from master branch (commit {{0e13252d9e7a6c82e6e170bac1a2faf727287c1d}}), I can see following exception in log:
> {code}
> 16:38:57,964 ERROR [io.undertow.request] (management I/O-1) UT005071: Undertow request failed HttpServerExchange{ GET /metrics/test}: java.lang.IllegalStateException: UT000002: The response has already been started
> at io.undertow.server.HttpServerExchange.setStatusCode(HttpServerExchange.java:1406)
> at org.wildfly.extension.microprofile.metrics.MetricsContextService$1.lambda$handleRequest$0(MetricsContextService.java:85)
> at io.smallrye.metrics.MetricsRequestHandler.handleRequest(MetricsRequestHandler.java:142)
> at io.smallrye.metrics.MetricsRequestHandler.handleRequest(MetricsRequestHandler.java:73)
> at org.wildfly.extension.microprofile.metrics.MetricsContextService$1.handleRequest(MetricsContextService.java:84)
> at org.jboss.as.domain.http.server.security.RealmReadinessHandler.handleRequest(RealmReadinessHandler.java:51)
> at org.jboss.as.domain.http.server.security.ServerErrorReadinessHandler.handleRequest(ServerErrorReadinessHandler.java:35)
> at io.undertow.server.handlers.PathHandler.handleRequest(PathHandler.java:91)
> at io.undertow.server.handlers.ChannelUpgradeHandler.handleRequest(ChannelUpgradeHandler.java:211)
> at io.undertow.server.handlers.cache.CacheHandler.handleRequest(CacheHandler.java:92)
> at io.undertow.server.handlers.error.SimpleErrorPageHandler.handleRequest(SimpleErrorPageHandler.java:78)
> at io.undertow.server.handlers.CanonicalPathHandler.handleRequest(CanonicalPathHandler.java:49)
> at org.jboss.as.domain.http.server.ManagementHttpRequestHandler.handleRequest(ManagementHttpRequestHandler.java:57)
> at org.jboss.as.domain.http.server.cors.CorsHttpHandler.handleRequest(CorsHttpHandler.java:75)
> at org.jboss.as.domain.http.server.ManagementHttpServer$UpgradeFixHandler.handleRequest(ManagementHttpServer.java:664)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:376)
> at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:255)
> at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:136)
> at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:162)
> at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:100)
> at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:57)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:291)
> at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:286)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.nio.QueuedNioTcpServer$1.run(QueuedNioTcpServer.java:132)
> at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:612)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:479)
> {code}
> This exception is caused by following request:
> {code}
> $ curl -v http://localhost:9990/metrics/test
> * Trying ::1:9990...
> * TCP_NODELAY set
> * connect to ::1 port 9990 failed: Connection refused
> * Trying 127.0.0.1:9990...
> * TCP_NODELAY set
> * Connected to localhost (127.0.0.1) port 9990 (#0)
> > GET /metrics/test HTTP/1.1
> > Host: localhost:9990
> > User-Agent: curl/7.65.3
> > Accept: */*
> >
> * Mark bundle as not supporting multiuse
> < HTTP/1.1 404 Not Found
> < Connection: keep-alive
> < Content-Length: 25
> < Date: Thu, 22 Aug 2019 14:57:20 GMT
> <
> * Connection #0 to host localhost left intact
> Bad scope requested: test
> The 404 Not Found HTTP response code is expected and also 'Bad scope request: test' in this case. Although, I think that mentioned IllegalStateException should be avoided. Also, this exception is not thrown in WildFly 17.0.1.
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-12427) Missing io.smallrye.health and config dependency on org.jboss.logging
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-12427?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-12427:
------------------------------------
Summary: Missing io.smallrye.health and config dependency on org.jboss.logging (was: Missing io.smallrye.health dependency on org.jboss.logging)
> Missing io.smallrye.health and config dependency on org.jboss.logging
> ---------------------------------------------------------------------
>
> Key: WFLY-12427
> URL: https://issues.jboss.org/browse/WFLY-12427
> Project: WildFly
> Issue Type: Bug
> Components: MP Health
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Major
>
> I happened to notice this in a server log of a CI job:
> {code}
> 16:03:53,351 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-000119: Not generating any bean definitions from io.smallrye.health.SmallRyeHealthReporter because of underlying class loading error: Type org.jboss.logging.Logger from [Module "io.smallrye.health" version 1.0.2 from local module loader @4909b8da (finder: local module finder @3a03464 (roots: C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\wildfly\modules,C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\wildfly\modules\system\layers\base,C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\modules))] not found. If this is unexpected, enable DEBUG logging to see the full error.
> {code}
> The io.smallrye:smallrye-health-2.0:1.0.2 pom shows a dependency on JBoss Logging but the module.xml for its module does not.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-12427) Missing io.smallrye.health and config dependency on org.jboss.logging
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-12427?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-12427:
------------------------------------
Description:
I happened to notice this in a server log of a CI job:
{code}
16:03:53,351 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-000119: Not generating any bean definitions from io.smallrye.health.SmallRyeHealthReporter because of underlying class loading error: Type org.jboss.logging.Logger from [Module "io.smallrye.health" version 1.0.2 from local module loader @4909b8da (finder: local module finder @3a03464 (roots: C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\wildfly\modules,C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\wildfly\modules\system\layers\base,C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\modules))] not found. If this is unexpected, enable DEBUG logging to see the full error.
{code}
The io.smallrye:smallrye-health-2.0:1.0.2 pom shows a dependency on JBoss Logging but the module.xml for its module does not.
An examination of the other io.smallrye modules shows the same problem in pom vs module.xml difference for config as well.
was:
I happened to notice this in a server log of a CI job:
{code}
16:03:53,351 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-000119: Not generating any bean definitions from io.smallrye.health.SmallRyeHealthReporter because of underlying class loading error: Type org.jboss.logging.Logger from [Module "io.smallrye.health" version 1.0.2 from local module loader @4909b8da (finder: local module finder @3a03464 (roots: C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\wildfly\modules,C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\wildfly\modules\system\layers\base,C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\modules))] not found. If this is unexpected, enable DEBUG logging to see the full error.
{code}
The io.smallrye:smallrye-health-2.0:1.0.2 pom shows a dependency on JBoss Logging but the module.xml for its module does not.
> Missing io.smallrye.health and config dependency on org.jboss.logging
> ---------------------------------------------------------------------
>
> Key: WFLY-12427
> URL: https://issues.jboss.org/browse/WFLY-12427
> Project: WildFly
> Issue Type: Bug
> Components: MP Health
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Major
>
> I happened to notice this in a server log of a CI job:
> {code}
> 16:03:53,351 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-000119: Not generating any bean definitions from io.smallrye.health.SmallRyeHealthReporter because of underlying class loading error: Type org.jboss.logging.Logger from [Module "io.smallrye.health" version 1.0.2 from local module loader @4909b8da (finder: local module finder @3a03464 (roots: C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\wildfly\modules,C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\wildfly\modules\system\layers\base,C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\modules))] not found. If this is unexpected, enable DEBUG logging to see the full error.
> {code}
> The io.smallrye:smallrye-health-2.0:1.0.2 pom shows a dependency on JBoss Logging but the module.xml for its module does not.
> An examination of the other io.smallrye modules shows the same problem in pom vs module.xml difference for config as well.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-12427) Missing io.smallrye.health dependency on org.jboss.logging
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-12427:
---------------------------------------
Summary: Missing io.smallrye.health dependency on org.jboss.logging
Key: WFLY-12427
URL: https://issues.jboss.org/browse/WFLY-12427
Project: WildFly
Issue Type: Bug
Components: MP Health
Reporter: Brian Stansberry
Assignee: Brian Stansberry
I happened to notice this in a server log of a CI job:
{code}
16:03:53,351 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-000119: Not generating any bean definitions from io.smallrye.health.SmallRyeHealthReporter because of underlying class loading error: Type org.jboss.logging.Logger from [Module "io.smallrye.health" version 1.0.2 from local module loader @4909b8da (finder: local module finder @3a03464 (roots: C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\wildfly\modules,C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\wildfly\modules\system\layers\base,C:\buildAgent\work\37b47ae8b9c60325\full\testsuite\integration\smoke\target\modules))] not found. If this is unexpected, enable DEBUG logging to see the full error.
{code}
The io.smallrye:smallrye-health-2.0:1.0.2 pom shows a dependency on JBoss Logging but the module.xml for its module does not.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months