[JBoss JIRA] (WFWIP-145) Allow to define 'All except ABC subsystem' in exposed-subsystems attribute
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFWIP-145?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil resolved WFWIP-145.
-------------------------------
Resolution: Won't Do
We have a limited set of subsystems (and only a subset exposes metrics) so that it remains manageable to explicitly sets them.
> Allow to define 'All except ABC subsystem' in exposed-subsystems attribute
> --------------------------------------------------------------------------
>
> Key: WFWIP-145
> URL: https://issues.jboss.org/browse/WFWIP-145
> Project: WildFly WIP
> Issue Type: Enhancement
> Components: MP Metrics
> Reporter: Rostislav Svoboda
> Assignee: Jeff Mesnil
> Priority: Major
>
> Allow to define 'All except ABC subsystem' in exposed-subsystems attribute without explicitly defining all the valid subsystems.
> Use-case: I want to expose available subsystems, but without jgroups
> Example v1: {{exposed-subsystems=\["!jgroups"\]}}
> Example v2: {{exposed-subsystems=\["!jgroups,!jca"\]}}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFCORE-4199) jconsole can't connect to jboss CLI process
by Jean-Francois Denise (Jira)
[ https://issues.jboss.org/browse/WFCORE-4199?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise commented on WFCORE-4199:
----------------------------------------------
[~thofman], sincere thanks for your proposal to solve it!
> jconsole can't connect to jboss CLI process
> -------------------------------------------
>
> Key: WFCORE-4199
> URL: https://issues.jboss.org/browse/WFCORE-4199
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 7.0.0.Alpha4
> Reporter: Jean-Francois Denise
> Assignee: Jean-Francois Denise
> Priority: Critical
>
> Due to JBTHR-61 that is masked by a JDK bug (JDK-8213735), as soon as CLI is connected to a server, jconsole can't connect to CLI. There is an invalid ObjectName registered in the MBeanServer that breaks at deserialization time.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFCORE-4199) jconsole can't connect to jboss CLI process
by Tomas Hofman (Jira)
[ https://issues.jboss.org/browse/WFCORE-4199?page=com.atlassian.jira.plugi... ]
Tomas Hofman commented on WFCORE-4199:
--------------------------------------
Sorry, I got distracted by JBTHR-61 having fix version 2.3.2, which is already used in my Wildfly, and I could still hit the issue. Checking the commit, the correct fix version will be 2.3.3, so yeah, all is good :).
> jconsole can't connect to jboss CLI process
> -------------------------------------------
>
> Key: WFCORE-4199
> URL: https://issues.jboss.org/browse/WFCORE-4199
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 7.0.0.Alpha4
> Reporter: Jean-Francois Denise
> Assignee: Jean-Francois Denise
> Priority: Critical
>
> Due to JBTHR-61 that is masked by a JDK bug (JDK-8213735), as soon as CLI is connected to a server, jconsole can't connect to CLI. There is an invalid ObjectName registered in the MBeanServer that breaks at deserialization time.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFCORE-4199) jconsole can't connect to jboss CLI process
by Jean-Francois Denise (Jira)
[ https://issues.jboss.org/browse/WFCORE-4199?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise commented on WFCORE-4199:
----------------------------------------------
[~thofman], I already did the analysis, I logged JDK-8213735 that hides the problem when threads register CLI remoting threads (JBTHR-61). The bug in threads has been fixed, so I think we are all set. Just need to upgrade to latest threads. makes sense?
> jconsole can't connect to jboss CLI process
> -------------------------------------------
>
> Key: WFCORE-4199
> URL: https://issues.jboss.org/browse/WFCORE-4199
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 7.0.0.Alpha4
> Reporter: Jean-Francois Denise
> Assignee: Jean-Francois Denise
> Priority: Critical
>
> Due to JBTHR-61 that is masked by a JDK bug (JDK-8213735), as soon as CLI is connected to a server, jconsole can't connect to CLI. There is an invalid ObjectName registered in the MBeanServer that breaks at deserialization time.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFCORE-4199) jconsole can't connect to jboss CLI process
by Tomas Hofman (Jira)
[ https://issues.jboss.org/browse/WFCORE-4199?page=com.atlassian.jira.plugi... ]
Tomas Hofman edited comment on WFCORE-4199 at 11/21/18 10:47 AM:
-----------------------------------------------------------------
{code}
Nov 21, 2018 4:19:55 PM ClientNotifForwarder NotifFetcher.fetchOneNotif
WARNING: Failed to deserialize a notification: java.rmi.UnmarshalException: error unmarshalling return; nested exception is:
java.io.InvalidObjectException: javax.management.MalformedObjectNameException: Invalid character '"' in value part of property
{code}
Parsed string is "jboss.threads:name=Remoting "cli-client",type=thread-pool".
was (Author: thofman):
{code}
Nov 21, 2018 4:19:55 PM ClientNotifForwarder NotifFetcher.fetchOneNotif
WARNING: Failed to deserialize a notification: java.rmi.UnmarshalException: error unmarshalling return; nested exception is:
java.io.InvalidObjectException: javax.management.MalformedObjectNameException: Invalid character '"' in value part of property
{code}
> jconsole can't connect to jboss CLI process
> -------------------------------------------
>
> Key: WFCORE-4199
> URL: https://issues.jboss.org/browse/WFCORE-4199
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 7.0.0.Alpha4
> Reporter: Jean-Francois Denise
> Assignee: Jean-Francois Denise
> Priority: Critical
>
> Due to JBTHR-61 that is masked by a JDK bug (JDK-8213735), as soon as CLI is connected to a server, jconsole can't connect to CLI. There is an invalid ObjectName registered in the MBeanServer that breaks at deserialization time.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11392) Exception after sending SIGTERM to server
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFLY-11392?page=com.atlassian.jira.plugin... ]
Radoslav Husar updated WFLY-11392:
----------------------------------
Priority: Optional (was: Major)
> Exception after sending SIGTERM to server
> -----------------------------------------
>
> Key: WFLY-11392
> URL: https://issues.jboss.org/browse/WFLY-11392
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 15.0.0.Beta1
> Environment: MacOS
> Reporter: Jan Kašík
> Assignee: Radoslav Husar
> Priority: Optional
>
> When sending SIGTERM to started server (ctrl+c), a warning with exception appears in log. So far, this issue seems specific to Mac OS. Excerpt of log:
> {noformat}
> 14:25:18,036 INFO [org.jboss.as.server] (Thread-1) WFLYSRV0236: Suspending server with no timeout.
> 14:25:18,038 INFO [org.jboss.as.ejb3] (Thread-1) WFLYEJB0493: EJB subsystem suspension complete
> 14:25:18,040 INFO [org.jboss.as.server] (Thread-1) WFLYSRV0220: Server shutdown has been requested via an OS signal
> 14:25:18,050 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
> 14:25:18,053 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 78) MODCLUSTER000002: Initiating mod_cluster shutdown
> 14:25:18,053 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0019: Host default-host stopping
> 14:25:18,053 INFO [org.jboss.as.mail.extension] (MSC service thread 1-7) WFLYMAIL0002: Unbound mail session [java:jboss/mail/Default]
> 14:25:18,056 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0008: Undertow AJP listener ajp suspending
> 14:25:18,056 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0008: Undertow HTTPS listener https suspending
> 14:25:18,058 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0008: Undertow HTTP listener default suspending
> 14:25:18,058 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0019: Stopped Driver service with driver-name = h2
> 14:25:18,059 WARN [org.jboss.modcluster] (ServerService Thread Pool -- 78) MODCLUSTER000033: Failed to interrupt socket reception.: java.io.IOException: Can't assign requested address
> at java.base/java.net.PlainDatagramSocketImpl.send(Native Method)
> at java.base/java.net.DatagramSocket.send(DatagramSocket.java:695)
> at org.jboss.mod_cluster.core@1.4.0.Final-redhat-1//org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.interruptDatagramReader(AdvertiseListenerImpl.java:197)
> at org.jboss.mod_cluster.core@1.4.0.Final-redhat-1//org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.stop(AdvertiseListenerImpl.java:212)
> at org.jboss.mod_cluster.core@1.4.0.Final-redhat-1//org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.destroy(AdvertiseListenerImpl.java:224)
> at org.jboss.mod_cluster.core@1.4.0.Final-redhat-1//org.jboss.modcluster.ModClusterService.shutdown(ModClusterService.java:198)
> at org.wildfly.extension.mod_cluster@7.2.0.GA-redhat-00001//org.wildfly.extension.mod_cluster.ContainerEventHandlerServiceConfigurator.accept(ContainerEventHandlerServiceConfigurator.java:83)
> at org.wildfly.extension.mod_cluster@7.2.0.GA-redhat-00001//org.wildfly.extension.mod_cluster.ContainerEventHandlerServiceConfigurator.accept(ContainerEventHandlerServiceConfigurator.java:50)
> at org.wildfly.clustering.service@7.2.0.GA-redhat-00001//org.wildfly.clustering.service.FunctionalService.stop(FunctionalService.java:77)
> at org.wildfly.clustering.service@7.2.0.GA-redhat-00001//org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$stop$1(AsyncServiceConfigurator.java:142)
> at org.jboss.threads@2.3.2.Final-redhat-1//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.2.Final-redhat-1//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads@2.3.2.Final-redhat-1//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads@2.3.2.Final-redhat-1//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.base/java.lang.Thread.run(Thread.java:834)
> at org.jboss.threads@2.3.2.Final-redhat-1//org.jboss.threads.JBossThread.run(JBossThread.java:485)
> 14:25:18,068 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0007: Undertow HTTPS listener https stopped, was bound to 127.0.0.1:8443
> 14:25:18,068 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow AJP listener ajp stopped, was bound to 127.0.0.1:8009
> 14:25:18,068 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080
> 14:25:18,070 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0004: Undertow 2.0.15.Final-redhat-00001 stopping
> 14:25:18,078 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0050: JBoss EAP 7.2.0.GA (WildFly Core 6.0.11.Final-redhat-00001) stopped in 34ms
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11392) Exception after sending SIGTERM to server
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFLY-11392?page=com.atlassian.jira.plugin... ]
Radoslav Husar commented on WFLY-11392:
---------------------------------------
This is a known issue, see https://issues.jboss.org/browse/MODCLUSTER-460
Maybe it would still make sense to put it on debug in 1.4.
> Exception after sending SIGTERM to server
> -----------------------------------------
>
> Key: WFLY-11392
> URL: https://issues.jboss.org/browse/WFLY-11392
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 15.0.0.Beta1
> Environment: MacOS
> Reporter: Jan Kašík
> Assignee: Radoslav Husar
> Priority: Major
>
> When sending SIGTERM to started server (ctrl+c), a warning with exception appears in log. So far, this issue seems specific to Mac OS. Excerpt of log:
> {noformat}
> 14:25:18,036 INFO [org.jboss.as.server] (Thread-1) WFLYSRV0236: Suspending server with no timeout.
> 14:25:18,038 INFO [org.jboss.as.ejb3] (Thread-1) WFLYEJB0493: EJB subsystem suspension complete
> 14:25:18,040 INFO [org.jboss.as.server] (Thread-1) WFLYSRV0220: Server shutdown has been requested via an OS signal
> 14:25:18,050 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
> 14:25:18,053 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 78) MODCLUSTER000002: Initiating mod_cluster shutdown
> 14:25:18,053 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0019: Host default-host stopping
> 14:25:18,053 INFO [org.jboss.as.mail.extension] (MSC service thread 1-7) WFLYMAIL0002: Unbound mail session [java:jboss/mail/Default]
> 14:25:18,056 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0008: Undertow AJP listener ajp suspending
> 14:25:18,056 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0008: Undertow HTTPS listener https suspending
> 14:25:18,058 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0008: Undertow HTTP listener default suspending
> 14:25:18,058 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0019: Stopped Driver service with driver-name = h2
> 14:25:18,059 WARN [org.jboss.modcluster] (ServerService Thread Pool -- 78) MODCLUSTER000033: Failed to interrupt socket reception.: java.io.IOException: Can't assign requested address
> at java.base/java.net.PlainDatagramSocketImpl.send(Native Method)
> at java.base/java.net.DatagramSocket.send(DatagramSocket.java:695)
> at org.jboss.mod_cluster.core@1.4.0.Final-redhat-1//org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.interruptDatagramReader(AdvertiseListenerImpl.java:197)
> at org.jboss.mod_cluster.core@1.4.0.Final-redhat-1//org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.stop(AdvertiseListenerImpl.java:212)
> at org.jboss.mod_cluster.core@1.4.0.Final-redhat-1//org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl.destroy(AdvertiseListenerImpl.java:224)
> at org.jboss.mod_cluster.core@1.4.0.Final-redhat-1//org.jboss.modcluster.ModClusterService.shutdown(ModClusterService.java:198)
> at org.wildfly.extension.mod_cluster@7.2.0.GA-redhat-00001//org.wildfly.extension.mod_cluster.ContainerEventHandlerServiceConfigurator.accept(ContainerEventHandlerServiceConfigurator.java:83)
> at org.wildfly.extension.mod_cluster@7.2.0.GA-redhat-00001//org.wildfly.extension.mod_cluster.ContainerEventHandlerServiceConfigurator.accept(ContainerEventHandlerServiceConfigurator.java:50)
> at org.wildfly.clustering.service@7.2.0.GA-redhat-00001//org.wildfly.clustering.service.FunctionalService.stop(FunctionalService.java:77)
> at org.wildfly.clustering.service@7.2.0.GA-redhat-00001//org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$stop$1(AsyncServiceConfigurator.java:142)
> at org.jboss.threads@2.3.2.Final-redhat-1//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.2.Final-redhat-1//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads@2.3.2.Final-redhat-1//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads@2.3.2.Final-redhat-1//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.base/java.lang.Thread.run(Thread.java:834)
> at org.jboss.threads@2.3.2.Final-redhat-1//org.jboss.threads.JBossThread.run(JBossThread.java:485)
> 14:25:18,068 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0007: Undertow HTTPS listener https stopped, was bound to 127.0.0.1:8443
> 14:25:18,068 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow AJP listener ajp stopped, was bound to 127.0.0.1:8009
> 14:25:18,068 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080
> 14:25:18,070 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0004: Undertow 2.0.15.Final-redhat-00001 stopping
> 14:25:18,078 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0050: JBoss EAP 7.2.0.GA (WildFly Core 6.0.11.Final-redhat-00001) stopped in 34ms
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFCORE-4199) jconsole can't connect to jboss CLI process
by Tomas Hofman (Jira)
[ https://issues.jboss.org/browse/WFCORE-4199?page=com.atlassian.jira.plugi... ]
Tomas Hofman commented on WFCORE-4199:
--------------------------------------
{code}
Nov 21, 2018 4:19:55 PM ClientNotifForwarder NotifFetcher.fetchOneNotif
WARNING: Failed to deserialize a notification: java.rmi.UnmarshalException: error unmarshalling return; nested exception is:
java.io.InvalidObjectException: javax.management.MalformedObjectNameException: Invalid character '"' in value part of property
{code}
> jconsole can't connect to jboss CLI process
> -------------------------------------------
>
> Key: WFCORE-4199
> URL: https://issues.jboss.org/browse/WFCORE-4199
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 7.0.0.Alpha4
> Reporter: Jean-Francois Denise
> Assignee: Jean-Francois Denise
> Priority: Critical
>
> Due to JBTHR-61 that is masked by a JDK bug (JDK-8213735), as soon as CLI is connected to a server, jconsole can't connect to CLI. There is an invalid ObjectName registered in the MBeanServer that breaks at deserialization time.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-3027) [DMN Designer] Differentiate zero and non zero custom data types
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3027?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3027:
--------------------------------
Description:
There is no visual information if no custom data type is defined. In the attached dialog we should differentiate between states when no custom da taype is declared and when some custom data types are declared. The same way we do it in list of spaces and list of projects.
h2. Manual acceptance test
- Create new model, empty state indicated, save and reopen (/)
- Create some data type, not empty state indicated, save and reopen (/)
- Remove the data type, empty state indicated, save and reopen (/)
- Firefox, Edge, Chrome (/)
was:
There is no visual information if no custom data type is defined. In the attached dialog we should differentiate between states when no custom da taype is declared and when some custom data types are declared. The same way we do it in list of spaces and list of projects.
h2. Manual acceptance test
- Create new model, empty state indicated, save and reopen
- Create some data type, not empty state indicated, save and reopen
- Remove the data type, empty state indicated, save and reopen
- Firefox, Edge, Chrome
> [DMN Designer] Differentiate zero and non zero custom data types
> ----------------------------------------------------------------
>
> Key: DROOLS-3027
> URL: https://issues.jboss.org/browse/DROOLS-3027
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.12.0.Final
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: UX, drools-tools
> Attachments: Screenshot from 2018-09-24 18-12-02.png
>
>
> There is no visual information if no custom data type is defined. In the attached dialog we should differentiate between states when no custom da taype is declared and when some custom data types are declared. The same way we do it in list of spaces and list of projects.
> h2. Manual acceptance test
> - Create new model, empty state indicated, save and reopen (/)
> - Create some data type, not empty state indicated, save and reopen (/)
> - Remove the data type, empty state indicated, save and reopen (/)
> - Firefox, Edge, Chrome (/)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months