[JBoss JIRA] (WFLY-8452) Management Interfaces stopping before server fully shutdown
by John Farrelly (JIRA)
John Farrelly created WFLY-8452:
-----------------------------------
Summary: Management Interfaces stopping before server fully shutdown
Key: WFLY-8452
URL: https://issues.jboss.org/browse/WFLY-8452
Project: WildFly
Issue Type: Bug
Components: CLI
Affects Versions: 10.1.0.Final
Reporter: John Farrelly
Assignee: Jason Greene
In our product, we use jboss-cli.sh to monitor if WildFly is running ({{jboss-cli.sh -c --controller=${JBOSS_HOST}:${JBOSS_MANAGEMENT_PORT} "read-attribute server-state"}}). We've been using this mechanism to determine if JBoss/WildFly is running since JBoss 7.1.1.Final.
What we are seeing in WildFly 10.1.0.Final is that WildFly shuts down the native interface before it has closed all other services. This means that some long-running business logic thread in WildFly can stop it from shutting down, but the native interface has already stopped, making it seem that WildFly has stopped.
I can see that other services (such as undertow) stay up until the long running business logic thread has completed. This is a regression from JBoss AS 7.1.1, where the management interfaces would not stop while long running business logic was still executing.
Here's the management section of my standalone.xml:
{code:xml}
<management>
<security-realms>
<security-realm name="ManagementRealm">
<authentication>
<properties path="mgmt-users.properties" relative-to="jboss.server.config.dir"/>
</authentication>
</security-realm>
<security-realm name="ApplicationRealm">
<authentication>
<properties path="application-users.properties" relative-to="jboss.server.config.dir"/>
</authentication>
</security-realm>
</security-realms>
<management-interfaces>
<native-interface security-realm="ManagementRealm">
<socket-binding native="management-native"/>
</native-interface>
<http-interface security-realm="ManagementRealm">
<socket-binding http="management-http"/>
</http-interface>
</management-interfaces>
</management>
{code}
We use {{jboss-cli.sh}} to issue the shutdown command:
{code}
jboss-cli.sh -c --controller=${JBOSS_HOST}:${JBOSS_MANAGEMENT_PORT} --command=":shutdown"
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-8451) org.wildfly.clustering.web.session.IdentifierExternalizerTestCase#toHex fails on JDK9 b162
by Radoslav Husar (JIRA)
Radoslav Husar created WFLY-8451:
------------------------------------
Summary: org.wildfly.clustering.web.session.IdentifierExternalizerTestCase#toHex fails on JDK9 b162
Key: WFLY-8451
URL: https://issues.jboss.org/browse/WFLY-8451
Project: WildFly
Issue Type: Bug
Components: Clustering
Reporter: Radoslav Husar
Assignee: Radoslav Husar
testHex(org.wildfly.clustering.web.session.IdentifierExternalizerTestCase) Time elapsed: 0.008 sec <<< ERROR!
java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:533)
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:186)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:476)
at org.wildfly.clustering.web.IdentifierExternalizer$3.writeObject(IdentifierExternalizer.java:74)
at org.wildfly.clustering.web.IdentifierExternalizer$3.writeObject(IdentifierExternalizer.java:71)
at org.wildfly.clustering.web.session.IdentifierExternalizerTestCase.test(IdentifierExternalizerTestCase.java:97)
at org.wildfly.clustering.web.session.IdentifierExternalizerTestCase.testHex(IdentifierExternalizerTestCase.java:61)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ELY-1032) Help output has limit for line length 160 chars and it leads to ugly line break in the middle of one option.
by Hynek Švábek (JIRA)
Hynek Švábek created ELY-1032:
---------------------------------
Summary: Help output has limit for line length 160 chars and it leads to ugly line break in the middle of one option.
Key: ELY-1032
URL: https://issues.jboss.org/browse/ELY-1032
Project: WildFly Elytron
Issue Type: Bug
Reporter: Hynek Švábek
Assignee: Darran Lofthouse
Help output has limit 160 chars for line length and it leads to ugly line break in the middle of one option.
Command
{code}
java -jar wildfly-elytron-tool.jar credential-store --help
{code}
has this output:
{code}
usage: java -jar wildfly-elytron-tool.jar credential-store -a <alias> | -e <alias> | -h | -r <alias> | -v [-c] [-f] [-i <arg>] [-l <loc>] [-p <pwd>] [-s
<arg>] [-t <type>] [-u <uri>] [-x <secret to store>]
{code}
I expect at least line break before "-s" option
{code}
usage: java -jar wildfly-elytron-tool.jar credential-store -a <alias> | -e <alias> | -h | -r <alias> | -v [-c] [-f] [-i <arg>] [-l <loc>] [-p <pwd>]
[-s <arg>] [-t <type>] [-u <uri>] [-x <secret to store>]
{code}
The best option would be some dynamic settings of line length
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-8450) Make org.wildfly.transaction.client module unsupported
by Ondra Chaloupka (JIRA)
Ondra Chaloupka created WFLY-8450:
-------------------------------------
Summary: Make org.wildfly.transaction.client module unsupported
Key: WFLY-8450
URL: https://issues.jboss.org/browse/WFLY-8450
Project: WildFly
Issue Type: Bug
Components: Transactions
Reporter: Ondra Chaloupka
Assignee: Tom Jenkinson
Priority: Blocker
Per e-mail discussion with David, the {{org.wildfly.transaction.client}} module currently doesn't contain anything meant to be used by application developers directly.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (HAWKULARQE-74) 2nd baselines
by viet nguyen (JIRA)
[ https://issues.jboss.org/browse/HAWKULARQE-74?page=com.atlassian.jira.plu... ]
viet nguyen edited comment on HAWKULARQE-74 at 3/27/17 1:33 AM:
----------------------------------------------------------------
I hit a hard limit at 240 pods on the node !239pods.png|thumbnail!
239 test pods + 1 HOSA pod.
Cluster info https://issues.jboss.org/browse/HAWKULARQE-73
{code}
[root@b20 ~]# free -g
total used free shared buff/cache available
Mem: 62 16 32 3 13 41
Swap: 0 0 0
{code}
- HOSA collection interval 30seconds
- Use [Hawkular Python client |https://github.com/vnugent/pyme]and iterate through each pod counting number of raw metrics captured in 30 minute-duration.
- Expecting 2 raw metrics / minute * 30 minute = 60 metrics / 30 minutes
Observations:
- Python client -> Metrics master endpoint on slow VPN connection causes exceptions in Metrics log [BZ 1435436|https://bugzilla.redhat.com/show_bug.cgi?id=1435436]
- Few pods have less than 60 metrics (see attachment). Need more investigation.
was (Author: vietn):
I hit a hard limit at 240 pods on the node !239pods.png|thumbnail!
239 test pods + 1 HOSA pod.
{code}
[root@b20 ~]# free -g
total used free shared buff/cache available
Mem: 62 16 32 3 13 41
Swap: 0 0 0
{code}
- HOSA collection interval 30seconds
- Use [Hawkular Python client |https://github.com/vnugent/pyme]and iterate through each pod counting number of raw metrics captured in 30 minute-duration.
- Expecting 2 raw metrics / minute * 30 minute = 60 metrics / 30 minutes
Observations:
- Python client -> Metrics master endpoint on slow VPN connection causes exceptions in Metrics log [BZ 1435436|https://bugzilla.redhat.com/show_bug.cgi?id=1435436]
- Few pods have less than 60 metrics. Need more investigation.
> 2nd baselines
> -------------
>
> Key: HAWKULARQE-74
> URL: https://issues.jboss.org/browse/HAWKULARQE-74
> Project: Hawkular QE
> Issue Type: Sub-task
> Reporter: viet nguyen
> Assignee: viet nguyen
> Attachments: 239pods.png, 30minutes-raw.txt.zip
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (HAWKULARQE-74) 2nd baselines
by viet nguyen (JIRA)
[ https://issues.jboss.org/browse/HAWKULARQE-74?page=com.atlassian.jira.plu... ]
viet nguyen edited comment on HAWKULARQE-74 at 3/27/17 1:28 AM:
----------------------------------------------------------------
I hit a hard limit at 240 pods on the node !239pods.png|thumbnail!
239 test pods + 1 HOSA pod.
{code}
[root@b20 ~]# free -g
total used free shared buff/cache available
Mem: 62 16 32 3 13 41
Swap: 0 0 0
{code}
- HOSA collection interval 30seconds
- Use [Hawkular Python client |https://github.com/vnugent/pyme]and iterate through each pod counting number of raw metrics captured in 30 minute-duration.
- Expecting 2 raw metrics / minute * 30 minute = 60 metrics / 30 minutes
Observations:
- Python client -> Metrics master endpoint on slow VPN connection causes exceptions in Metrics log [BZ 1435436|https://bugzilla.redhat.com/show_bug.cgi?id=1435436]
- Few pods have less than 60 metrics. Need more investigation.
was (Author: vietn):
I hit a hard limit at 240 pods on the node !239pods.png|thumbnail!
239 test pods + 1 HOSA pod.
{code}
[root@b20 ~]# free -g
total used free shared buff/cache available
Mem: 62 16 32 3 13 41
Swap: 0 0 0
{code}
- HOSA collection interval 30seconds
- Use [Hawkular Python client |https://github.com/vnugent/pyme]and iterate through each pod counting number of raw metrics captured in 30 minute-duration.
- 2 raw metrics / minute * 30 minute = 60 metrics
Observations:
- Python client -> Metrics master endpoint on slow VPN connection causes exceptions in Metrics log [BZ 1435436|https://bugzilla.redhat.com/show_bug.cgi?id=1435436]
> 2nd baselines
> -------------
>
> Key: HAWKULARQE-74
> URL: https://issues.jboss.org/browse/HAWKULARQE-74
> Project: Hawkular QE
> Issue Type: Sub-task
> Reporter: viet nguyen
> Assignee: viet nguyen
> Attachments: 239pods.png, 30minutes-raw.txt.zip
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month