January 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1574) ThreadPool rejection policy detecting stuck threads

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/JGRP-1574?page=com.atlassian.jira.plugin.... ] Radim Vansa updated JGRP-1574: ------------------------------ Affects Version/s: 3.2.6 > ThreadPool rejection policy detecting stuck threads > --------------------------------------------------- > > Key: JGRP-1574 > URL: https://issues.jboss.org/browse/JGRP-1574 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 3.2.6 > Reporter: Radim Vansa > Assignee: Radim Vansa > Priority: Minor > > Sometimes I find out my OOB threadpool size (which defaults to 200) in our tests too low, causing deadlock (this seems to be the case with the 64 node cluster - we've run out of OOB threads because all of them were stuck). > New rejection policy could usually silently discard the message, but in case that the thread pool does not finish anything (getCompletedTaskCount stays constant) for a period, it would throw a special exception denoting that there's possibly a deadlock (and that raising OOB threadpool could help). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-22) Drools index files are getting created out of control and consume all of the hard drive space

by Jyothi Alapati (JIRA)

[ https://issues.jboss.org/browse/DROOLS-22?page=com.atlassian.jira.plugin.... ] Jyothi Alapati updated DROOLS-22: --------------------------------- Description: Drools index files are getting created out of control and consume all of the hard drive space. It used to consume 20MB for index files, but in this case, it consumed 5GB of hard disk space and stopped working. Note: Deleting the old index files except the latest solved this problem, but we want this to be prevented, instead of deleting the index files manually. was: Drools index files are getting created out of control and consume all of the hard drive space. It used to consume 20MB for index files, but in this case, it consumed 5GB of hard disk space and stopped working. Note: Deleting the old index files except the latest solved this problem, but we want to this to be prevented, instead of deleting the index files manually. > Drools index files are getting created out of control and consume all of the hard drive space > --------------------------------------------------------------------------------------------- > > Key: DROOLS-22 > URL: https://issues.jboss.org/browse/DROOLS-22 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Jyothi Alapati > Assignee: Mark Proctor > Attachments: repository.xml, workspace.xml > > > Drools index files are getting created out of control and consume all of the hard drive space. It used to consume 20MB for index files, but in this case, it consumed 5GB of hard disk space and stopped working. > Note: Deleting the old index files except the latest solved this problem, but we want this to be prevented, instead of deleting the index files manually. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1574) ThreadPool rejection policy detecting stuck threads

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/JGRP-1574?page=com.atlassian.jira.plugin.... ] Radim Vansa updated JGRP-1574: ------------------------------ Description: Sometimes I find out my OOB threadpool size (which defaults to 200) in our tests too low, causing deadlock (this seems to be the case with the 64 node cluster - we've run out of OOB threads because all of them were stuck). New rejection policy could usually silently discard the message, but in case that the thread pool does not finish anything (getCompletedTaskCount stays constant) for a period, it would throw a special exception denoting that there's possibly a deadlock (and that raising OOB threadpool could help). > ThreadPool rejection policy detecting stuck threads > --------------------------------------------------- > > Key: JGRP-1574 > URL: https://issues.jboss.org/browse/JGRP-1574 > Project: JGroups > Issue Type: Feature Request > Reporter: Radim Vansa > Assignee: Radim Vansa > Priority: Minor > > Sometimes I find out my OOB threadpool size (which defaults to 200) in our tests too low, causing deadlock (this seems to be the case with the 64 node cluster - we've run out of OOB threads because all of them were stuck). > New rejection policy could usually silently discard the message, but in case that the thread pool does not finish anything (getCompletedTaskCount stays constant) for a period, it would throw a special exception denoting that there's possibly a deadlock (and that raising OOB threadpool could help). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-22) Drools index files are getting created out of control and consume all of the hard drive space

by Jyothi Alapati (JIRA)

[ https://issues.jboss.org/browse/DROOLS-22?page=com.atlassian.jira.plugin.... ] Jyothi Alapati updated DROOLS-22: --------------------------------- Attachment: repository.xml workspace.xml Attaching the repository.xml and workspace.xml > Drools index files are getting created out of control and consume all of the hard drive space > --------------------------------------------------------------------------------------------- > > Key: DROOLS-22 > URL: https://issues.jboss.org/browse/DROOLS-22 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Jyothi Alapati > Assignee: Mark Proctor > Attachments: repository.xml, workspace.xml > > > Drools index files are getting created out of control and consume all of the hard drive space. It used to consume 20MB for index files, but in this case, it consumed 5GB of hard disk space and stopped working. > Note: Deleting the old index files except the latest solved this problem, but we want to this to be prevented, instead of deleting the index files manually. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1574) ThreadPool rejection policy detecting stuck threads

by Radim Vansa (JIRA)

Radim Vansa created JGRP-1574: --------------------------------- Summary: ThreadPool rejection policy detecting stuck threads Key: JGRP-1574 URL: https://issues.jboss.org/browse/JGRP-1574 Project: JGroups Issue Type: Feature Request Reporter: Radim Vansa Assignee: Bela Ban -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1574) ThreadPool rejection policy detecting stuck threads

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/JGRP-1574?page=com.atlassian.jira.plugin.... ] Radim Vansa updated JGRP-1574: ------------------------------ Assignee: Radim Vansa (was: Bela Ban) > ThreadPool rejection policy detecting stuck threads > --------------------------------------------------- > > Key: JGRP-1574 > URL: https://issues.jboss.org/browse/JGRP-1574 > Project: JGroups > Issue Type: Feature Request > Reporter: Radim Vansa > Assignee: Radim Vansa > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1574) ThreadPool rejection policy detecting stuck threads

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/JGRP-1574?page=com.atlassian.jira.plugin.... ] Radim Vansa updated JGRP-1574: ------------------------------ Priority: Minor (was: Major) > ThreadPool rejection policy detecting stuck threads > --------------------------------------------------- > > Key: JGRP-1574 > URL: https://issues.jboss.org/browse/JGRP-1574 > Project: JGroups > Issue Type: Feature Request > Reporter: Radim Vansa > Assignee: Radim Vansa > Priority: Minor > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-22) Drools index files are getting created out of control and consume all of the hard drive space

by Jyothi Alapati (JIRA)

Jyothi Alapati created DROOLS-22: ------------------------------------ Summary: Drools index files are getting created out of control and consume all of the hard drive space Key: DROOLS-22 URL: https://issues.jboss.org/browse/DROOLS-22 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Jyothi Alapati Assignee: Mark Proctor Drools index files are getting created out of control and consume all of the hard drive space. It used to consume 20MB for index files, but in this case, it consumed 5GB of hard disk space and stopped working. Note: Deleting the old index files except the latest solved this problem, but we want to this to be prevented, instead of deleting the index files manually. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6415) Access Log directory - XML Parse issue

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6415?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6415: ---------------------------------- Component/s: Web > Access Log directory - XML Parse issue > -------------------------------------- > > Key: AS7-6415 > URL: https://issues.jboss.org/browse/AS7-6415 > Project: Application Server 7 > Issue Type: Bug > Components: Web > Environment: Jboss 7.1.1 win xp 32 bit > Reporter: narayana b > > step1) >  > <paths> > <path path="E:/jboss/jboss-as-7.1.1.Final/standalone" name="access-log-dir" /> > </paths> > step2) created a "access-log" dir under E:/jboss/jboss-as-7.1.1.Final/standalone > <virtual-server name="default-host" enable-welcome-root="true"> > <alias name="localhost"/> > <alias name="example.com"/> > <acesss-log pattern="Time Taken: %T %h %l %u %t %r %s %b" resolve-hosts="false" extended="false" prefix="access_log." rotate="true"> > <directory path ="access-log" relative-to="access-log-dir" /> > </acesss-log> > </virtual-server> > Parse Error > ----------- > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:155) [jboss-as-controller-7.1.1.Final.jar:7.1 > at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_17] > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[351,5] > Message: JBAS014789: Unexpected element '{urn:jboss:domain:web:1.1}acesss-log' encountered > at org.jboss.as.controller.parsing.ParseUtils.unexpectedElement(ParseUtils.java:85) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.web.WebSubsystemParser.parseHost(WebSubsystemParser.java:582) > at org.jboss.as.web.WebSubsystemParser.readElement(WebSubsystemParser.java:329) > at org.jboss.as.web.WebSubsystemParser.readElement(WebSubsystemParser.java:65) > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Fi......... > Please let me know is this fixed? ready to release?? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6408) Can't configure JGroups subsystem with CLI script in 7.2.0.Alpha1-SNAPSHOT

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/AS7-6408?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar commented on AS7-6408: ---------------------------------- I have found the issue and resolved it. However this approach of sending protocol list as part of add operation on stack is deprecated and only works because validation of operations is disabled in CLI. (check jboss-cli.xml) new approach is to call :add-protocol(type=<type>, socket-binding=<optional socket-binding>) operation for each protocol you are adding. problem with old way is that you can only list protocols but you cannot define to witch socket-binding they relate... old way will still work but if possible try to migrate your scripts to new model. > Can't configure JGroups subsystem with CLI script in 7.2.0.Alpha1-SNAPSHOT > --------------------------------------------------------------------------- > > Key: AS7-6408 > URL: https://issues.jboss.org/browse/AS7-6408 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering > Affects Versions: 7.2.0.Alpha1 > Environment: Git checkout of JBossAS 7.2.0.ALPHA1 from today (28/Jan/2013) > Reporter: Bernd Koecke > Assignee: Tomaz Cerar > Attachments: standalone-ha-jgroups.cli, standalone-jgroups-fragment.xml > > > When I try to configure extension and subsystem JGroups with a CLI script, the attribute "protocols" of the stack=tcp- or stack=udp-node contains the list of configured protocols twice. The result is that the list of protocols is doubled in the standalone.xml. But having a protocol twice in one stack results in an error at next server startup. I will attach the CLI script and the resulting XML fragment. > When I shutdown the server, remove the doubled second part of each protocol list, the server comes up and all is working fine. But I can't configure it only with a CLI script. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 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 2013