[JBoss JIRA] (DROOLS-3253) [DMN Designer] Add support for DMN v1.2
by Jozef Marko (Jira)
Jozef Marko created DROOLS-3253:
-----------------------------------
Summary: [DMN Designer] Add support for DMN v1.2
Key: DROOLS-3253
URL: https://issues.jboss.org/browse/DROOLS-3253
Project: Drools
Issue Type: Epic
Components: DMN Editor
Affects Versions: 7.11.0.Final
Reporter: Jozef Marko
Assignee: Michael Anstis
The DMN Editor needs to support DMN v1.2
This requires enhancements to the marshalling and UI.
More specifically we need both to support DMN v1.1 and v1.2 models and restrict the operations that can be performed by the User in the editor when handling a v1.1 model (the editor needs to support v1.2 operations).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFWIP-141) Vendor metrics - subsystem - statistics-enabled to get valid data
by Rostislav Svoboda (Jira)
Rostislav Svoboda created WFWIP-141:
---------------------------------------
Summary: Vendor metrics - subsystem - statistics-enabled to get valid data
Key: WFWIP-141
URL: https://issues.jboss.org/browse/WFWIP-141
Project: WildFly WIP
Issue Type: Bug
Components: MP Metrics
Reporter: Rostislav Svoboda
Assignee: Jeff Mesnil
Vendor metrics - subsystem - statistics-enabled to get valid data
I was playing with vendor metrics and I received a lot of zeros.
{code}
curl http://localhost:10090/metrics/vendor 2>/dev/null | grep -v TYPE | grep -v HELP | sort
{code}
Note: I use {{-Djboss.socket.binding.port-offset=100}}
So I started to wonder why and it's because of statistics are not enabled.
When I enabled statistics for Undertow and hit the WF server main page I saw some changes in metrics.
{code}
subsystem=undertow/:write-attribute(name=statistics-enabled, value=true)
{code}
Later I realized this scenario is also mentioned in analysis, section WildFly Metrics with undefined value / statistic-enabled = false
https://github.com/wildfly/wildfly-proposals/blob/cc189b56720951875aa9610...
So this is mainly tracking + discussion point now.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (JBVFS-207) Provide way to retrieve VirtualFile instance from VirtualFileURLConnection
by Tomas Hofman (Jira)
[ https://issues.jboss.org/browse/JBVFS-207?page=com.atlassian.jira.plugin.... ]
Tomas Hofman updated JBVFS-207:
-------------------------------
Description:
It is not possible to obtain VirtualFile (and by extensions it's physicalFile) instance wrapped in VirtualFileURLConnection without using reflection.
Code snippet from Drools [1], where they try to get hold of {{VirtualFile#getPhysicalFile()}}:
{code}
private static Object findVirtualFile( URL url ) throws IOException {
URLConnection urlConnection = url.openConnection();
try {
if ( urlConnection.getClass().getName().equals( "org.jboss.vfs.protocol.VirtualFileURLConnection" ) ) {
Field f = urlConnection.getClass().getDeclaredField( "file" );
f.setAccessible( true );
return f.get( urlConnection );
}
} catch (NoSuchFieldException | IllegalAccessException e) {
// ignored
}
return urlConnection.getContent();
}
{code}
[1] https://github.com/kiegroup/drools/commit/2a36f67a29ed06d0f980a60ff1c81fa...
was:
It is not possible to obtain VirtualFile (and by extensions it's physicalFile) instance wrapped in VirtualFileURLConnection without using reflection.
Code snippet from Drools [1]:
{code}
private static Object findVirtualFile( URL url ) throws IOException {
URLConnection urlConnection = url.openConnection();
try {
if ( urlConnection.getClass().getName().equals( "org.jboss.vfs.protocol.VirtualFileURLConnection" ) ) {
Field f = urlConnection.getClass().getDeclaredField( "file" );
f.setAccessible( true );
return f.get( urlConnection );
}
} catch (NoSuchFieldException | IllegalAccessException e) {
// ignored
}
return urlConnection.getContent();
}
{code}
[1] https://github.com/kiegroup/drools/commit/2a36f67a29ed06d0f980a60ff1c81fa...
> Provide way to retrieve VirtualFile instance from VirtualFileURLConnection
> --------------------------------------------------------------------------
>
> Key: JBVFS-207
> URL: https://issues.jboss.org/browse/JBVFS-207
> Project: JBoss VFS
> Issue Type: Enhancement
> Reporter: Tomas Hofman
> Assignee: Tomas Hofman
> Priority: Major
>
> It is not possible to obtain VirtualFile (and by extensions it's physicalFile) instance wrapped in VirtualFileURLConnection without using reflection.
> Code snippet from Drools [1], where they try to get hold of {{VirtualFile#getPhysicalFile()}}:
> {code}
> private static Object findVirtualFile( URL url ) throws IOException {
> URLConnection urlConnection = url.openConnection();
> try {
> if ( urlConnection.getClass().getName().equals( "org.jboss.vfs.protocol.VirtualFileURLConnection" ) ) {
> Field f = urlConnection.getClass().getDeclaredField( "file" );
> f.setAccessible( true );
> return f.get( urlConnection );
> }
> } catch (NoSuchFieldException | IllegalAccessException e) {
> // ignored
> }
> return urlConnection.getContent();
> }
> {code}
> [1] https://github.com/kiegroup/drools/commit/2a36f67a29ed06d0f980a60ff1c81fa...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFWIP-140) microprofile-metrics-smallrye subsystem removal causes INFO log entry for each metric
by Rostislav Svoboda (Jira)
Rostislav Svoboda created WFWIP-140:
---------------------------------------
Summary: microprofile-metrics-smallrye subsystem removal causes INFO log entry for each metric
Key: WFWIP-140
URL: https://issues.jboss.org/browse/WFWIP-140
Project: WildFly WIP
Issue Type: Bug
Components: MP Metrics
Reporter: Rostislav Svoboda
Assignee: Jeff Mesnil
microprofile-metrics-smallrye subsystem removal causes INFO log entry for each metric
I think this should be decreased to DEBUG level.
{code}
12:09:38,411 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: classloader.currentLoadedClass.count]
12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: classloader.totalLoadedClass.count]
12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: classloader.totalUnloadedClass.count]
12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: cpu.availableProcessors]
12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: cpu.systemLoadAverage]
12:09:38,412 INFO [io.smallrye.metrics.MetricsRegistryImpl] (MSC service thread 1-8) Remove metric [name: gc.G1 Old Generation.count]
...
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFWIP-137) Integers are printed as floats with trailing .0
by Rostislav Svoboda (Jira)
[ https://issues.jboss.org/browse/WFWIP-137?page=com.atlassian.jira.plugin.... ]
Rostislav Svoboda updated WFWIP-137:
------------------------------------
Description:
Integers are printed as floats with trailing .0
{code}
base:classloader_current_loaded_class_count 11135.0
base:classloader_total_loaded_class_count 11171.0
base:classloader_total_unloaded_class_count 36.0
base:cpu_available_processors 8.0
base:gc_g1_old_generation_count 0.0
base:gc_g1_old_generation_time_seconds 0.0
base:gc_g1_young_generation_count 20.0
base:thread_count 50.0
base:thread_daemon_count 11.0
base:thread_max_count 121.0
{code}
Payara, OpenLiberty and Helidon report integers as integers.
was:
Integers are printed as floats with trailing .0
{code}
base:classloader_current_loaded_class_count 11135.0
base:classloader_total_loaded_class_count 11171.0
base:classloader_total_unloaded_class_count 36.0
base:cpu_available_processors 8.0
base:gc_g1_old_generation_count 0.0
base:gc_g1_old_generation_time_seconds 0.0
base:gc_g1_young_generation_count 20.0
base:thread_count 50.0
base:thread_daemon_count 11.0
base:thread_max_count 121.0
{code}
> Integers are printed as floats with trailing .0
> -----------------------------------------------
>
> Key: WFWIP-137
> URL: https://issues.jboss.org/browse/WFWIP-137
> Project: WildFly WIP
> Issue Type: Bug
> Components: MP Metrics
> Reporter: Rostislav Svoboda
> Assignee: Jeff Mesnil
> Priority: Major
>
> Integers are printed as floats with trailing .0
> {code}
> base:classloader_current_loaded_class_count 11135.0
> base:classloader_total_loaded_class_count 11171.0
> base:classloader_total_unloaded_class_count 36.0
> base:cpu_available_processors 8.0
> base:gc_g1_old_generation_count 0.0
> base:gc_g1_old_generation_time_seconds 0.0
> base:gc_g1_young_generation_count 20.0
> base:thread_count 50.0
> base:thread_daemon_count 11.0
> base:thread_max_count 121.0
> {code}
> Payara, OpenLiberty and Helidon report integers as integers.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFWIP-139) Payara reports non_heap memory, WF doesn't
by Rostislav Svoboda (Jira)
Rostislav Svoboda created WFWIP-139:
---------------------------------------
Summary: Payara reports non_heap memory, WF doesn't
Key: WFWIP-139
URL: https://issues.jboss.org/browse/WFWIP-139
Project: WildFly WIP
Issue Type: Bug
Components: MP Metrics
Reporter: Rostislav Svoboda
Assignee: Jeff Mesnil
Payara reports non_heap memory, WF doesn't
{code}
base:memory_committed_heap_bytes 5.0069504E8
base:memory_committed_non_heap_bytes 1.65412864E8
base:memory_max_heap_bytes 5.0069504E8
base:memory_max_non_heap_bytes -1.0
base:memory_used_heap_bytes 2.05958976E8
base:memory_used_non_heap_bytes 1.48845312E8
{code}
WF reports
{code}
base:memory_committed_heap_bytes 1.06954752E8
base:memory_max_heap_bytes 5.36870912E8
base:memory_used_heap_bytes 6.4805664E7
{code}
It's also true that Helidon and OpenLiberty do not report non-heap space.
Thorntail uses the same implementation as WF so it's irrelevant in this comparison.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months