[JBoss JIRA] (WFLY-10712) Expose Metrics so that it can be consumed by OpenShift Console
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-10712?page=com.atlassian.jira.plugin... ]
Jeff Mesnil updated WFLY-10712:
-------------------------------
Description:
Expose Metric so that it can be consumed by OpenShift Console
This should be implemented in manner that is consistent with WildFly Swarm i.e. MicroProfile specifications where applicable.
This requirement can be delivered as Technology Preview for WF 15.
was:
Expose Metric so that it can be consumed by OpenShift Console
This should be implemented in manner that is consistent with WildFly Swarm i.e. MicroProfile specifications where applicable.
This requirement can be delivered as Technology Preview for WF 14.
> Expose Metrics so that it can be consumed by OpenShift Console
> --------------------------------------------------------------
>
> Key: WFLY-10712
> URL: https://issues.jboss.org/browse/WFLY-10712
> Project: WildFly
> Issue Type: Feature Request
> Reporter: Bilge Ozpeynirci
> Assignee: Jeff Mesnil
> Labels: OS_Observability
>
> Expose Metric so that it can be consumed by OpenShift Console
> This should be implemented in manner that is consistent with WildFly Swarm i.e. MicroProfile specifications where applicable.
> This requirement can be delivered as Technology Preview for WF 15.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 7 months
[JBoss JIRA] (DROOLS-3063) Renaming Packages with Guided Rules fails - Rules not moved to correct package
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3063?page=com.atlassian.jira.plugi... ]
Jozef Marko moved AF-783 to DROOLS-3063:
----------------------------------------
Project: Drools (was: AppFormer)
Key: DROOLS-3063 (was: AF-783)
Component/s: Guided Rule Editor
(was: VFS)
Fix Version/s: (was: Backlog)
> Renaming Packages with Guided Rules fails - Rules not moved to correct package
> ------------------------------------------------------------------------------
>
> Key: DROOLS-3063
> URL: https://issues.jboss.org/browse/DROOLS-3063
> Project: Drools
> Issue Type: Bug
> Components: Guided Rule Editor
> Reporter: Dominik Sandjaja
> Assignee: Michael Anstis
> Labels: drools-tools
>
> Renaming a package in the Drools Workbench renames the package but the guided rules (with DSLs) within that package still have the old package declaration in the created source code. Since there is no way to change the package declaration in the rules manually, I consider this a bug.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 7 months
[JBoss JIRA] (WFLY-10531) Wildfly leaks ActiveMQ connections
by Tjomme Schilstra (JIRA)
[ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin... ]
Tjomme Schilstra commented on WFLY-10531:
-----------------------------------------
I can confirm the issue. Perhaps best to revert WFLY-9501.
> Wildfly leaks ActiveMQ connections
> ----------------------------------
>
> Key: WFLY-10531
> URL: https://issues.jboss.org/browse/WFLY-10531
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 13.0.0.Final
> Environment: openjdk 8 / openjdk 9, Linux
> Reporter: Marcel Šebek
> Assignee: Jeff Mesnil
> Attachments: WFLY-10531-ear-1.0.ear, WFLY10531.zip
>
>
> After upgrading our application from wildfly 12 to 13, the app started to crash after a while (hours, days, depending on circumstances). It crashes on
> IJ000453: Unable to get managed connection for java:/JmsXA
> and other errors (it simply cannot perform all the jobs it contains). I found that when shutting down the server which has been running for a while, I can see a bunch of these messages in the log:
> WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (ServerService Thread Pool -- 117) [:::] IJ000615: Destroying active connection in pool: ActiveMQConnectionDefinition (org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection@2f37f69)
> Bascially, the longer the server was running, more of these messages are shown. I cannot find a way how to reproduce the issue. When the server runs for short time but with some load, no connection is leaked (or just one, rarely). On the other side, it leaks connections even without any particularly high load (just a few requests and @Schedule jobs) when running for longer time.
> It may also be a bug in our application, which just happen to have more serious impact with the new wildfly version.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 7 months