January 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4262) Memory of expired session not released

by Wojciech Ozga (JIRA)

[ https://issues.jboss.org/browse/WFLY-4262?page=com.atlassian.jira.plugin.... ] Wojciech Ozga updated WFLY-4262: -------------------------------- Attachment: Expired session still available.png > Memory of expired session not released > -------------------------------------- > > Key: WFLY-4262 > URL: https://issues.jboss.org/browse/WFLY-4262 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.2.0.Final > Environment: Running on Windows 7 > Wildfly 8.2 > Primefaces 5.1 > Reporter: Wojciech Ozga > Assignee: Jason Greene > Attachments: Expired session still available.png, JVM memory usage.png > > > Expecting Wildfly to remove expired user session data after 20 minutes. But the data is never removed, neither by container, neither by GC, neither when new requests reach the server. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4262) Memory of expired session not released

by Wojciech Ozga (JIRA)

Wojciech Ozga created WFLY-4262: ----------------------------------- Summary: Memory of expired session not released Key: WFLY-4262 URL: https://issues.jboss.org/browse/WFLY-4262 Project: WildFly Issue Type: Bug Affects Versions: 8.2.0.Final Environment: Running on Windows 7 Wildfly 8.2 Primefaces 5.1 Reporter: Wojciech Ozga Assignee: Jason Greene Expecting Wildfly to remove expired user session data after 20 minutes. But the data is never removed, neither by container, neither by GC, neither when new requests reach the server. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1876) MERGE3 : Strange number and content of subgroups

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1876?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1876: -------------------------------- Karim: what's the root cause ? Can you submit a PR for fixing this issue ? > MERGE3 : Strange number and content of subgroups > ------------------------------------------------ > > Key: JGRP-1876 > URL: https://issues.jboss.org/browse/JGRP-1876 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4.2 > Reporter: Karim AMMOUS > Assignee: Bela Ban > Fix For: 3.5.1, 3.6, 3.6.2 > > Attachments: 4Subgroups.zip, ChannelCreator.java, DkeJgrpAddress.java, MergeTest4.java, MergeViewWith210Subgroups.log, SplitMergeTest.java, views.txt > > > Using JGroups 3.4.2, a split occurred and a merge was processed successfully but number of subgroups is wrong (210 instead of 2). > The final mergeView is correct and contains 210 members. > Here is an extract of subviews: > {code} > INFO | Incoming-18,cluster,term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F] | [MyMembershipListener.java:126] | (middleware) | MergeView view ID = [serv-ZM2BU35940-58033:vt-14:192.168.55.55:1:CL(GROUP01)[F]|172] > 210 subgroups > [.... > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [term-ETJ104215245-11092:host:192.168.56.72:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU38960-6907:asb:192.168.55.52:1:CL(GROUP01)[F]] > [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]|171] (1) [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU47533-55240:vt-14:192.168.55.57:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU35943-49435:asb:192.168.55.51:1:CL(GROUP01)[F]] > ....] > {code} > II wasn't able to reproduce that with a simple program. But I observed that merge was preceded by an ifdown/ifup on host 192.168.56.6. That member lost all others members, but it still present in their view. > Example: > {code} > {A, B, C} => {A, B, C} and {C} => {A, B, C} > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1876) MERGE3 : Strange number and content of subgroups

by Karim AMMOUS (JIRA)

[ https://issues.jboss.org/browse/JGRP-1876?page=com.atlassian.jira.plugin.... ] Karim AMMOUS updated JGRP-1876: ------------------------------- Attachment: ChannelCreator.java Sample program to reproduced Radim's issue > MERGE3 : Strange number and content of subgroups > ------------------------------------------------ > > Key: JGRP-1876 > URL: https://issues.jboss.org/browse/JGRP-1876 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4.2 > Reporter: Karim AMMOUS > Assignee: Bela Ban > Fix For: 3.5.1, 3.6, 3.6.2 > > Attachments: 4Subgroups.zip, ChannelCreator.java, DkeJgrpAddress.java, MergeTest4.java, MergeViewWith210Subgroups.log, SplitMergeTest.java, views.txt > > > Using JGroups 3.4.2, a split occurred and a merge was processed successfully but number of subgroups is wrong (210 instead of 2). > The final mergeView is correct and contains 210 members. > Here is an extract of subviews: > {code} > INFO | Incoming-18,cluster,term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F] | [MyMembershipListener.java:126] | (middleware) | MergeView view ID = [serv-ZM2BU35940-58033:vt-14:192.168.55.55:1:CL(GROUP01)[F]|172] > 210 subgroups > [.... > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [term-ETJ104215245-11092:host:192.168.56.72:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU38960-6907:asb:192.168.55.52:1:CL(GROUP01)[F]] > [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]|171] (1) [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU47533-55240:vt-14:192.168.55.57:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU35943-49435:asb:192.168.55.51:1:CL(GROUP01)[F]] > ....] > {code} > II wasn't able to reproduce that with a simple program. But I observed that merge was preceded by an ifdown/ifup on host 192.168.56.6. That member lost all others members, but it still present in their view. > Example: > {code} > {A, B, C} => {A, B, C} and {C} => {A, B, C} > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1876) MERGE3 : Strange number and content of subgroups

by Karim AMMOUS (JIRA)

[ https://issues.jboss.org/browse/JGRP-1876?page=com.atlassian.jira.plugin.... ] Karim AMMOUS commented on JGRP-1876: ------------------------------------ Hi Bela and Radim, I reproduced the issue encountered by Radim, which is different form the current one. Please find enclosed a test program. Just launch three instances and wait few minutes. Each merge, the number of subgroups increments by two. In fact, old subgroups are not deleted. Adding clear instruction (subviews.clear()) at the begin of Merger.MergeTask.start() method fixes the problem. Otherwise, my issue (JGRP-1876) still exists in spite of the patch. I think that I got the root cause, but it is not easy to reproduce it with a standalone program. > MERGE3 : Strange number and content of subgroups > ------------------------------------------------ > > Key: JGRP-1876 > URL: https://issues.jboss.org/browse/JGRP-1876 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4.2 > Reporter: Karim AMMOUS > Assignee: Bela Ban > Fix For: 3.5.1, 3.6, 3.6.2 > > Attachments: 4Subgroups.zip, DkeJgrpAddress.java, MergeTest4.java, MergeViewWith210Subgroups.log, SplitMergeTest.java, views.txt > > > Using JGroups 3.4.2, a split occurred and a merge was processed successfully but number of subgroups is wrong (210 instead of 2). > The final mergeView is correct and contains 210 members. > Here is an extract of subviews: > {code} > INFO | Incoming-18,cluster,term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F] | [MyMembershipListener.java:126] | (middleware) | MergeView view ID = [serv-ZM2BU35940-58033:vt-14:192.168.55.55:1:CL(GROUP01)[F]|172] > 210 subgroups > [.... > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [term-ETJ104215245-11092:host:192.168.56.72:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU38960-6907:asb:192.168.55.52:1:CL(GROUP01)[F]] > [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]|171] (1) [term-ETJ101697729-31726:host:192.168.56.6:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU47533-55240:vt-14:192.168.55.57:1:CL(GROUP01)[F]] > [term-ETJ100691812-36873:host:192.168.56.16:1:CL(GROUP01)[F]|170] (1) [serv-ZM2BU35943-49435:asb:192.168.55.51:1:CL(GROUP01)[F]] > ....] > {code} > II wasn't able to reproduce that with a simple program. But I observed that merge was preceded by an ifdown/ifup on host 192.168.56.6. That member lost all others members, but it still present in their view. > Example: > {code} > {A, B, C} => {A, B, C} and {C} => {A, B, C} > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4261) JDR not logging stacktraces from skipped commands

by Brad Maxwell (JIRA)

Brad Maxwell created WFLY-4261: ---------------------------------- Summary: JDR not logging stacktraces from skipped commands Key: WFLY-4261 URL: https://issues.jboss.org/browse/WFLY-4261 Project: WildFly Issue Type: Bug Components: JDR Reporter: Brad Maxwell Assignee: Brad Maxwell JDR not logging stacktraces from skipped commands Bug where skipped commands are logged to sos_logs/skips.log is writing the stack to a StringWriter but not adding it to the skips.log correctly. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1197) Port the legacy jmx-console to AS7

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/WFLY-1197?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec closed WFLY-1197. ------------------------------------- Resolution: Done > Port the legacy jmx-console to AS7 > ---------------------------------- > > Key: WFLY-1197 > URL: https://issues.jboss.org/browse/WFLY-1197 > Project: WildFly > Issue Type: Feature Request > Components: JMX > Reporter: Dimitris Andreadis > Assignee: Sebastian Łaskawiec > Labels: JMX, as7, jmx-console, management_security,, management_sso > Attachments: jmx-console.war, jmx-console.war > > > I've seen a few people asking for a port of the old jmx-console to AS7, for monitoring purposes, until equivalent functionality is available through the new GWT-based console. > I've ported the old console in this branch: > https://github.com/dandreadis/jboss-as/commits/jmx-console > It only includes a new top-level directory 'jmx-console'. The directory is not build by default, and when you build it manually it does not alter the server configuration in any way, you need to manually copy the resulting target/jboss-as-jmx-console-VERSION.war to the server deployment directory (and rename it to jmx-console.war) > If there is interest, it could be included in the AS7 distro in some top level 'legacy' directory so it is not deployed by default? > The resulting .war is attached on this JIRA, in case someone wants to use it. It work just as well on AS 7.0.2 and the latest AS 7.1.x development branch. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1197) Port the legacy jmx-console to AS7

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/WFLY-1197?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on WFLY-1197: ------------------------------------------- The implementation might be found here: https://github.com/wildfly-extras/jmx-console > Port the legacy jmx-console to AS7 > ---------------------------------- > > Key: WFLY-1197 > URL: https://issues.jboss.org/browse/WFLY-1197 > Project: WildFly > Issue Type: Feature Request > Components: JMX > Reporter: Dimitris Andreadis > Assignee: Sebastian Łaskawiec > Labels: JMX, as7, jmx-console, management_security,, management_sso > Attachments: jmx-console.war, jmx-console.war > > > I've seen a few people asking for a port of the old jmx-console to AS7, for monitoring purposes, until equivalent functionality is available through the new GWT-based console. > I've ported the old console in this branch: > https://github.com/dandreadis/jboss-as/commits/jmx-console > It only includes a new top-level directory 'jmx-console'. The directory is not build by default, and when you build it manually it does not alter the server configuration in any way, you need to manually copy the resulting target/jboss-as-jmx-console-VERSION.war to the server deployment directory (and rename it to jmx-console.war) > If there is interest, it could be included in the AS7 distro in some top level 'legacy' directory so it is not deployed by default? > The resulting .war is attached on this JIRA, in case someone wants to use it. It work just as well on AS 7.0.2 and the latest AS 7.1.x development branch. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1197) Port the legacy jmx-console to AS7

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/WFLY-1197?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec reassigned WFLY-1197: ----------------------------------------- Assignee: Sebastian Łaskawiec (was: Darran Lofthouse) > Port the legacy jmx-console to AS7 > ---------------------------------- > > Key: WFLY-1197 > URL: https://issues.jboss.org/browse/WFLY-1197 > Project: WildFly > Issue Type: Feature Request > Components: JMX > Reporter: Dimitris Andreadis > Assignee: Sebastian Łaskawiec > Labels: JMX, as7, jmx-console, management_security,, management_sso > Attachments: jmx-console.war, jmx-console.war > > > I've seen a few people asking for a port of the old jmx-console to AS7, for monitoring purposes, until equivalent functionality is available through the new GWT-based console. > I've ported the old console in this branch: > https://github.com/dandreadis/jboss-as/commits/jmx-console > It only includes a new top-level directory 'jmx-console'. The directory is not build by default, and when you build it manually it does not alter the server configuration in any way, you need to manually copy the resulting target/jboss-as-jmx-console-VERSION.war to the server deployment directory (and rename it to jmx-console.war) > If there is interest, it could be included in the AS7 distro in some top level 'legacy' directory so it is not deployed by default? > The resulting .war is attached on this JIRA, in case someone wants to use it. It work just as well on AS 7.0.2 and the latest AS 7.1.x development branch. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4260) Schema validation errors against jboss-service_7_0.xsd

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/WFLY-4260?page=com.atlassian.jira.plugin.... ] Sande Gilda commented on WFLY-4260: ----------------------------------- Created related bug: https://bugzilla.redhat.com/show_bug.cgi?id=1183165 > Schema validation errors against jboss-service_7_0.xsd > ------------------------------------------------------- > > Key: WFLY-4260 > URL: https://issues.jboss.org/browse/WFLY-4260 > Project: WildFly > Issue Type: Bug > Reporter: Sande Gilda > Assignee: Jason Greene > > When you import a quickstart containing a jboss-service.xml file, you get the following XML: > cvc-complex-type.2.3: Element 'attribute' cannot have character [children], because the type's content type is element-only. > The quickstart source is located here: > https://github.com/jboss-developer/jboss-eap-quickstarts/tree/6.4.x-devel... > I searched the https://github.com/jbossas/jboss-eap/ source code for other jboss-service.xml examples, and found a few with syntax similar to what the quickstarts use: > * sar/src/test/resources/test/serviceXmlDeployment.jar/META-INF/jboss-service.xml > * testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/sar/injection/jboss-service.xml > * testsuite/integration/smoke/src/test/java/org/jboss/as/test/smoke/sar/jboss-service.xml > * arquillian/container-managed/src/test/resources/sar-example.sar/META-INF/jboss-service.xml > * arquillian/container-remote/src/test/resources/sar-example.sar/META-INF/jboss-service.xml > There seems to be an error in the schema: > http://www.jboss.org/schema/jbossas/jboss-service_7_0.xsd > The quickstart bug is located here: https://bugzilla.redhat.com/show_bug.cgi?id=1178782 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2015