February 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-557) Remove usage of jboss-common-core in logging

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFCORE-557: ---------------------------------- Summary: Remove usage of jboss-common-core in logging Key: WFCORE-557 URL: https://issues.jboss.org/browse/WFCORE-557 Project: WildFly Core Issue Type: Sub-task Components: Logging Affects Versions: 1.0.0.Alpha18 Reporter: Tomaz Cerar Assignee: James Perkins Fix For: 1.0.0.Alpha19 we should avoid using jboss-common-core if possible -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-556) Remove usage of jboss-common-core in domain-managment

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFCORE-556: ---------------------------------- Summary: Remove usage of jboss-common-core in domain-managment Key: WFCORE-556 URL: https://issues.jboss.org/browse/WFCORE-556 Project: WildFly Core Issue Type: Sub-task Components: Domain Management Reporter: Tomaz Cerar Assignee: Brian Stansberry -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1912) LockService can fail under heavy load

by Chris Gentile (JIRA)

[ https://issues.jboss.org/browse/JGRP-1912?page=com.atlassian.jira.plugin.... ] Chris Gentile commented on JGRP-1912: ------------------------------------- I relocated the <CENTRAL_LOCK /> tag in my channel config and the problem goes away. For anyone else that stumbles upon this thread: The doc says: "The locking protocol has to be placed at or towards the top of the stack (close to the channel)." The stack is lowest-to-highest in channel config files, so "towards the top" is actually at the bottom of the file. Then it is the last protocol to get added to the stack and is on top. Bela, Perhaps in the documentation you could elaborate on what "close to the channel" actually means. Or perhaps an actual example might help. The jgroups jar files seem to include several config files already (i.e.: udp.xml). Perhaps you could include a locking.xml too? Thanks, Chris > LockService can fail under heavy load > ------------------------------------- > > Key: JGRP-1912 > URL: https://issues.jboss.org/browse/JGRP-1912 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.1 > Environment: both windows 8.1 and RHEL > java 1.7.0_75 > Reporter: Chris Gentile > Assignee: Bela Ban > Fix For: 3.6.3 > > Attachments: LockServiceTestClient.java, LockServiceTestClient.java, logFile, logFile2, runLockServiceTestClient.sh, udp.xml > > > Once in awhile, the LockService will get stuck acquiring a lock. > These seems to occur most often when two threads are simultaneously trying to acquire the same lock. (i.e.: exact same millisecond on a server with multiple processors). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4360) Remove jboss-common-core.jar

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4360?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-4360: --------------------------------- Assignee: Tomaz Cerar > Remove jboss-common-core.jar > ---------------------------- > > Key: WFLY-4360 > URL: https://issues.jboss.org/browse/WFLY-4360 > Project: WildFly > Issue Type: Task > Reporter: David Lloyd > Assignee: Tomaz Cerar > > Completely remove the JAR and its module from the application server. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4367) jboss-cli.xml should include timeout of 30 seconds

by Travis Rogers (JIRA)

[ https://issues.jboss.org/browse/WFLY-4367?page=com.atlassian.jira.plugin.... ] Travis Rogers updated WFLY-4367: -------------------------------- Attachment: loop-cli-cmd.sh Test script > jboss-cli.xml should include timeout of 30 seconds > --------------------------------------------------- > > Key: WFLY-4367 > URL: https://issues.jboss.org/browse/WFLY-4367 > Project: WildFly > Issue Type: Enhancement > Components: CLI > Affects Versions: 8.2.0.Final > Reporter: Travis Rogers > Assignee: Alexey Loubyansky > Attachments: loop-cli-cmd.sh > > > Description of problem: > CLI commands use a default timeout of 5 seconds. Testing has shown that connection timeouts will occur with a timeout value this low. Recommended value is 30 seconds. > The following default setting should be added to $JBOSS_HOME/bin/jboss-cli.xml: > <connection-timeout>30000</connection-timeout> > Version-Release number of selected component (if applicable): > How to reproduce: > Loop calling the CLI executing a command. > Example command: > jboss-cli.sh -c --command=":read-attribute(name=server-state)" > Actual results: > Connection timeout error will eventually be thrown. > Expected results: > No errors due to connection timeout. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-555) Minimize usage of jboss-common-* jars

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-555?page=com.atlassian.jira.plugin... ] Tomaz Cerar moved WFLY-2557 to WFCORE-555: ------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-555 (was: WFLY-2557) Affects Version/s: 1.0.0.Alpha18 (was: 8.2.0.Final) > Minimize usage of jboss-common-* jars > ------------------------------------- > > Key: WFCORE-555 > URL: https://issues.jboss.org/browse/WFCORE-555 > Project: WildFly Core > Issue Type: Task > Affects Versions: 1.0.0.Alpha18 > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > > Currenty we have domain-mgmt, host controller, testsuite etc > using common-core.jar just for using Base64 class... > There is Base64 impl in jboss-dmr -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4361) Remove usages of jboss-common-core from the EJB subsystem and libraries

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4361?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-4361: ------------------------------ Parent: WFLY-4360 Issue Type: Sub-task (was: Task) > Remove usages of jboss-common-core from the EJB subsystem and libraries > ----------------------------------------------------------------------- > > Key: WFLY-4361 > URL: https://issues.jboss.org/browse/WFLY-4361 > Project: WildFly > Issue Type: Sub-task > Components: EJB > Reporter: David Lloyd > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4367) jboss-cli.xml should include timeout of 30 seconds

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4367?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-4367: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1194359 > jboss-cli.xml should include timeout of 30 seconds > --------------------------------------------------- > > Key: WFLY-4367 > URL: https://issues.jboss.org/browse/WFLY-4367 > Project: WildFly > Issue Type: Enhancement > Components: CLI > Affects Versions: 8.2.0.Final > Reporter: Travis Rogers > Assignee: Alexey Loubyansky > > Description of problem: > CLI commands use a default timeout of 5 seconds. Testing has shown that connection timeouts will occur with a timeout value this low. Recommended value is 30 seconds. > The following default setting should be added to $JBOSS_HOME/bin/jboss-cli.xml: > <connection-timeout>30000</connection-timeout> > Version-Release number of selected component (if applicable): > How to reproduce: > Loop calling the CLI executing a command. > Example command: > jboss-cli.sh -c --command=":read-attribute(name=server-state)" > Actual results: > Connection timeout error will eventually be thrown. > Expected results: > No errors due to connection timeout. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2557) Minimize usage of jboss-common-* jars

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2557?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-2557: ------------------------------ Affects Version/s: 8.2.0.Final > Minimize usage of jboss-common-* jars > ------------------------------------- > > Key: WFLY-2557 > URL: https://issues.jboss.org/browse/WFLY-2557 > Project: WildFly > Issue Type: Task > Affects Versions: 8.2.0.Final > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > > Currenty we have domain-mgmt, host controller, testsuite etc > using common-core.jar just for using Base64 class... > There is Base64 impl in jboss-dmr -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4367) jboss-cli.xml should include timeout of 30 seconds

by Travis Rogers (JIRA)

[ https://issues.jboss.org/browse/WFLY-4367?page=com.atlassian.jira.plugin.... ] Travis Rogers updated WFLY-4367: -------------------------------- Issue Type: Enhancement (was: Bug) > jboss-cli.xml should include timeout of 30 seconds > --------------------------------------------------- > > Key: WFLY-4367 > URL: https://issues.jboss.org/browse/WFLY-4367 > Project: WildFly > Issue Type: Enhancement > Components: CLI > Affects Versions: 8.2.0.Final > Reporter: Travis Rogers > Assignee: Alexey Loubyansky > > Description of problem: > CLI commands use a default timeout of 5 seconds. Testing has shown that connection timeouts will occur with a timeout value this low. Recommended value is 30 seconds. > The following default setting should be added to $JBOSS_HOME/bin/jboss-cli.xml: > <connection-timeout>30000</connection-timeout> > Version-Release number of selected component (if applicable): > How to reproduce: > Loop calling the CLI executing a command. > Example command: > jboss-cli.sh -c --command=":read-attribute(name=server-state)" > Actual results: > Connection timeout error will eventually be thrown. > Expected results: > No errors due to connection timeout. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 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