February 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-565) StaticDiscoveryResourceDefinition allows undefined values for its attributes

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-565?page=com.atlassian.jira.plugin... ] Alexey Loubyansky reassigned WFCORE-565: ---------------------------------------- Assignee: Alexey Loubyansky > StaticDiscoveryResourceDefinition allows undefined values for its attributes > ---------------------------------------------------------------------------- > > Key: WFCORE-565 > URL: https://issues.jboss.org/browse/WFCORE-565 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Alexey Loubyansky > > StaticDiscoveryResourceDefinition reuses the AttributeDefinitions from RemoteDomainControllerAddHandler, but those ADs allow undefined. That's appropriate for that OSH, but not for the StaticDiscoveryResourceDefinition ADs. > Also, the RemoteDomainControllerAddHandler AD's could use some clarification and validation as well, e.g. use setRequires(...) on the builder such that each of protocol, host, port requires the other two. So none are required, but if any is set all 3 must be. > The StaticDiscovery constructor should validate inputs with assert statements and javadoc its parameters, include whether null is allowed. (A null protocol or host will result in an IAE in discover(), so the current code does not support null.) > The DiscoveryOption interface should document whether the 3 "get" methods can return null. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-411) Syntax error when applying patch and exiting jboss-cli

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-411?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-411: ------------------------------------ Comment: was deleted (was: Cross post. :)) > Syntax error when applying patch and exiting jboss-cli > ------------------------------------------------------ > > Key: WFCORE-411 > URL: https://issues.jboss.org/browse/WFCORE-411 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Patching > Reporter: Arun Gupta > Assignee: Alexey Loubyansky > > [disconnected /] patch apply > ../wildfly-8.1.0.Final-update/wildfly-8.1.0.Final.patch > { > "outcome" : "success", > "result" : {} > } > [disconnected /] > [disconnected /] > [disconnected /] > [disconnected /] exit > logging.configuration already set in JAVA_OPTS > ./bin/jboss-cli.sh: line 81: syntax error near unexpected token `fi' > ./bin/jboss-cli.sh: line 81: `fi' -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-411) Syntax error when applying patch and exiting jboss-cli

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-411?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFCORE-411: ----------------------------------------- That's true if there's no script involved to run the package manager. And the authors of any such script can perhaps be really careful too. I don't mean to turn this into a package manager design thread though. :) > Syntax error when applying patch and exiting jboss-cli > ------------------------------------------------------ > > Key: WFCORE-411 > URL: https://issues.jboss.org/browse/WFCORE-411 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Patching > Reporter: Arun Gupta > Assignee: Alexey Loubyansky > > [disconnected /] patch apply > ../wildfly-8.1.0.Final-update/wildfly-8.1.0.Final.patch > { > "outcome" : "success", > "result" : {} > } > [disconnected /] > [disconnected /] > [disconnected /] > [disconnected /] exit > logging.configuration already set in JAVA_OPTS > ./bin/jboss-cli.sh: line 81: syntax error near unexpected token `fi' > ./bin/jboss-cli.sh: line 81: `fi' -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-411) Syntax error when applying patch and exiting jboss-cli

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-411?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFCORE-411: ----------------------------------------- Cross post. :) > Syntax error when applying patch and exiting jboss-cli > ------------------------------------------------------ > > Key: WFCORE-411 > URL: https://issues.jboss.org/browse/WFCORE-411 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Patching > Reporter: Arun Gupta > Assignee: Alexey Loubyansky > > [disconnected /] patch apply > ../wildfly-8.1.0.Final-update/wildfly-8.1.0.Final.patch > { > "outcome" : "success", > "result" : {} > } > [disconnected /] > [disconnected /] > [disconnected /] > [disconnected /] exit > logging.configuration already set in JAVA_OPTS > ./bin/jboss-cli.sh: line 81: syntax error near unexpected token `fi' > ./bin/jboss-cli.sh: line 81: `fi' -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-411) Syntax error when applying patch and exiting jboss-cli

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-411?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-411: ------------------------------------ Comment: was deleted (was: That's true if there's no script involved to run the package manager. And the authors of any such script can perhaps be really careful too. I don't mean to turn this into a package manager design thread though. :)) > Syntax error when applying patch and exiting jboss-cli > ------------------------------------------------------ > > Key: WFCORE-411 > URL: https://issues.jboss.org/browse/WFCORE-411 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Patching > Reporter: Arun Gupta > Assignee: Alexey Loubyansky > > [disconnected /] patch apply > ../wildfly-8.1.0.Final-update/wildfly-8.1.0.Final.patch > { > "outcome" : "success", > "result" : {} > } > [disconnected /] > [disconnected /] > [disconnected /] > [disconnected /] exit > logging.configuration already set in JAVA_OPTS > ./bin/jboss-cli.sh: line 81: syntax error near unexpected token `fi' > ./bin/jboss-cli.sh: line 81: `fi' -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-411) Syntax error when applying patch and exiting jboss-cli

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFCORE-411?page=com.atlassian.jira.plugin... ] David Lloyd commented on WFCORE-411: ------------------------------------ I guess that doesn't answer the problem, but I envisioned that the launchers for the patch tool would be single-line affairs. Though it wouldn't hurt to add a line to the top saying: {code} # Line numbers must be preserved {code} or some such. > Syntax error when applying patch and exiting jboss-cli > ------------------------------------------------------ > > Key: WFCORE-411 > URL: https://issues.jboss.org/browse/WFCORE-411 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Patching > Reporter: Arun Gupta > Assignee: Alexey Loubyansky > > [disconnected /] patch apply > ../wildfly-8.1.0.Final-update/wildfly-8.1.0.Final.patch > { > "outcome" : "success", > "result" : {} > } > [disconnected /] > [disconnected /] > [disconnected /] > [disconnected /] exit > logging.configuration already set in JAVA_OPTS > ./bin/jboss-cli.sh: line 81: syntax error near unexpected token `fi' > ./bin/jboss-cli.sh: line 81: `fi' -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-411) Syntax error when applying patch and exiting jboss-cli

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFCORE-411?page=com.atlassian.jira.plugin... ] David Lloyd commented on WFCORE-411: ------------------------------------ Separate package manager can cope by anticipating the situation and pre-initializing all classes it will need for the upgrade operation, so that if its JAR goes away, it can still finish the operation. > Syntax error when applying patch and exiting jboss-cli > ------------------------------------------------------ > > Key: WFCORE-411 > URL: https://issues.jboss.org/browse/WFCORE-411 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Patching > Reporter: Arun Gupta > Assignee: Alexey Loubyansky > > [disconnected /] patch apply > ../wildfly-8.1.0.Final-update/wildfly-8.1.0.Final.patch > { > "outcome" : "success", > "result" : {} > } > [disconnected /] > [disconnected /] > [disconnected /] > [disconnected /] exit > logging.configuration already set in JAVA_OPTS > ./bin/jboss-cli.sh: line 81: syntax error near unexpected token `fi' > ./bin/jboss-cli.sh: line 81: `fi' -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-411) Syntax error when applying patch and exiting jboss-cli

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-411?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFCORE-411: ----------------------------------------- Ouch. That implies the whole approach of using the CLI as the patching tool is problematic. And allowing the server to be running is problematic as well, as the same problem can happen with standalone.sh, domain.sh, etc. Using a separate package manager and not supporting the server continuing to run doesn't have that problem, although the question of how to update the package manager software itself still exists. > Syntax error when applying patch and exiting jboss-cli > ------------------------------------------------------ > > Key: WFCORE-411 > URL: https://issues.jboss.org/browse/WFCORE-411 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Patching > Reporter: Arun Gupta > Assignee: Alexey Loubyansky > > [disconnected /] patch apply > ../wildfly-8.1.0.Final-update/wildfly-8.1.0.Final.patch > { > "outcome" : "success", > "result" : {} > } > [disconnected /] > [disconnected /] > [disconnected /] > [disconnected /] exit > logging.configuration already set in JAVA_OPTS > ./bin/jboss-cli.sh: line 81: syntax error near unexpected token `fi' > ./bin/jboss-cli.sh: line 81: `fi' -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1916) ConcurrentModificationException in FD_ALL

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1916?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1916. ---------------------------- Resolution: Done Thanks Dan, fixed as suggested > ConcurrentModificationException in FD_ALL > ----------------------------------------- > > Key: JGRP-1916 > URL: https://issues.jboss.org/browse/JGRP-1916 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.2 > Reporter: Dan Berindei > Assignee: Bela Ban > Fix For: 3.6.3 > > > When DEBUG logging is enabled, FD_ALL logs the set of suspected members without proper synchronization. If another thread modifies the {{suspected_mbrs}} set at the same time, it can cause a {{ConcurrentModificationException}} and the {{SUSPECT}} event will be lost. > {noformat} > java.util.ConcurrentModificationException > at java.util.HashMap$HashIterator.nextEntry(HashMap.java:922) > at java.util.HashMap$KeyIterator.next(HashMap.java:956) > at java.util.AbstractCollection.toString(AbstractCollection.java:457) > at java.lang.String.valueOf(String.java:2847) > at java.lang.StringBuilder.append(StringBuilder.java:128) > at org.jgroups.protocols.FD_ALL.suspect(FD_ALL.java:368) > at org.jgroups.protocols.FD_ALL$TimeoutChecker.run(FD_ALL.java:444) > at org.jgroups.util.TimeScheduler3$Task.run(TimeScheduler3.java:287) > at org.jgroups.util.TimeScheduler3$RecurringTask.run(TimeScheduler3.java:321) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > {noformat} > I would also suggest adding a synchronized block in {{getSuspectedMembers()}}, {{init()}} and {{stop()}}. > FD_ALL2 seems to have the same problem. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4387) Unable to configure ajaxTimeout in wildfly 8.2_Final

by Manjunatha KB (JIRA)

[ https://issues.jboss.org/browse/WFLY-4387?page=com.atlassian.jira.plugin.... ] Manjunatha KB commented on WFLY-4387: ------------------------------------- Thanks for response stuart. One last query.. Is there any way to increase http connection timeout atlease... > Unable to configure ajaxTimeout in wildfly 8.2_Final > ---------------------------------------------------- > > Key: WFLY-4387 > URL: https://issues.jboss.org/browse/WFLY-4387 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.2.0.Final > Environment: OS : Windows 8.1 > WildFly: 8.2_Final > Reporter: Manjunatha KB > Assignee: Jason Greene > Labels: wildfly > > Hi. Am newbie to wildfly. Am facing an issue in getting ajax response as my DB is taking some quite time due to huge data. I guess wildfly is throwing internal server error after exactly 10 seconds of request time. So i need to know is there is any attribute which I need to set in standalone.xml to increase this timeout. Exactly as there is "ajaxTimeOut" in apache Tomcat. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 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 February 2015