December 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2696) management audit settings: syslog protocol is lowercase while uppercase is expected

by Tom Fonteyne (JIRA)

Tom Fonteyne created WFLY-2696: ---------------------------------- Summary: management audit settings: syslog protocol is lowercase while uppercase is expected Key: WFLY-2696 URL: https://issues.jboss.org/browse/WFLY-2696 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 8.0.0.CR1 Environment: - 8.0.0 CR1 + latest code in master - domain mode Reporter: Tom Fonteyne Assignee: Tom Fonteyne Add a syslog handler to the audit settings of the management service of the domain controller, then start an instance. It fails to start with: JBAS014612: Operation ("register-server") failed - address: ([]): java.lang.IllegalArgumentException: No enum const class org.jboss.as.controller.audit.SyslogAuditLogHandler$Transport.udp at java.lang.Enum.valueOf(Enum.java:214) -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1765) TP: enable loopback by default and discard own multicasts

by Bela Ban (JIRA)

Bela Ban created JGRP-1765: ------------------------------ Summary: TP: enable loopback by default and discard own multicasts Key: JGRP-1765 URL: https://issues.jboss.org/browse/JGRP-1765 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.5 Enable {{TP.looback}} by default (deprecate and ignore prop): all messages sent by self are passed right to a thread pool to send them up again. When a multicast message sent by self is received, it is currently passed to a thread pool, de-serialized and only then discarded if loopback=true. This means that we create an unneeded buffer for de-serializationand perform de-serialization. SOLUTION: discard the multicast from self immediately when receiving it, in {{TP.receive()}} -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1763) TimeService

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1763?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1763: -------------------------------- Investigate where else this could be used. E.g. {{UNICAST3$Entry.update()}} > TimeService > ----------- > > Key: JGRP-1763 > URL: https://issues.jboss.org/browse/JGRP-1763 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.5 > > > New service which provides wall clock time at a coarse (configurable) granularity. > Motivation: {{System.currentTimeMillis()}} or {{System.nanoTime()}} is sometimes called frequently, e.g. by {{TCPConnectionMap$TCPConnection.updateLastAccessed()}} or in FD/FD_ALL. This has a cost, especially when a lock is held (system calls while a lock is held cause preemption and the thread losing its time slice). > However, the 2 examples above don't need the exact time, but an approximation of it is OK. > GOALS: > * Provide a time service which returns the last cached value of {{System.timeCurrentMillis()}} > * This is a quick and efficient call > * {{TimeService}} registers a timer task which updates its internal cached value every N milliseconds (configurable), e.g. every 500 ms > BENEFIT: > For example, in TCPConnection, the timestamp is updated whenever we send or receive a message from the peer. The timestamp is used to expire and close a connection (if configured), and can be updated 100'000 times a second. If the time service provided the current time in ms every 500ms, then {{System.currentTimeMillis()}} would only be called 2 times during a second instead of 100'000 times ! -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1764) TCPConnectionMap$TCPConnection: update time stamp only if connection reaping is enabled

by Bela Ban (JIRA)

Bela Ban created JGRP-1764: ------------------------------ Summary: TCPConnectionMap$TCPConnection: update time stamp only if connection reaping is enabled Key: JGRP-1764 URL: https://issues.jboss.org/browse/JGRP-1764 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.5 In TCPConnectionMap, {{updateLastAccessed()}} is called whenever a message is sent or received. This doesn't need to be done if connection reaping is disabled. -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1763) TimeService

by Bela Ban (JIRA)

Bela Ban created JGRP-1763: ------------------------------ Summary: TimeService Key: JGRP-1763 URL: https://issues.jboss.org/browse/JGRP-1763 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.5 New service which provides wall clock time at a coarse (configurable) granularity. Motivation: {{System.currentTimeMillis()}} or {{System.nanoTime()}} is sometimes called frequently, e.g. by {{TCPConnectionMap$TCPConnection.updateLastAccessed()}} or in FD/FD_ALL. This has a cost, especially when a lock is held (system calls while a lock is held cause preemption and the thread losing its time slice). However, the 2 examples above don't need the exact time, but an approximation of it is OK. GOALS: * Provide a time service which returns the last cached value of {{System.timeCurrentMillis()}} * This is a quick and efficient call * {{TimeService}} registers a timer task which updates its internal cached value every N milliseconds (configurable), e.g. every 500 ms BENEFIT: For example, in TCPConnection, the timestamp is updated whenever we send or receive a message from the peer. The timestamp is used to expire and close a connection (if configured), and can be updated 100'000 times a second. If the time service provided the current time in ms every 500ms, then {{System.currentTimeMillis()}} would only be called 2 times during a second instead of 100'000 times ! -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2695) Creating named formater patterns for offline servers fail

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-2695?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-2695: -------------------------------- Workaround Description: Create the pattern before stopping the servers. Workaround: Workaround Exists > Creating named formater patterns for offline servers fail > --------------------------------------------------------- > > Key: WFLY-2695 > URL: https://issues.jboss.org/browse/WFLY-2695 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Logging > Affects Versions: 8.0.0.CR1 > Environment: any domain configuration > Reporter: Matthias Berndt > Assignee: James Perkins > > After adding and attaching a named formatter to an offline server starting the server fails due to an invalid logging configuration. > server-one fails with: > {{ > [Server:server-one] 00:08:00,214 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("add") failed - address: ([ > [Server:server-one] ("subsystem" => "logging"), > [Server:server-one] ("console-handler" => "CONSOLE") > [Server:server-one] ]): java.lang.IllegalArgumentException: Formatter "TESTPATTERN" is not found > }} > I assume logging.properties is written too late in LoggingOperations.java -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2693) list-active-jsf-impls is missing reply type

by Stan Silvert (JIRA)

[ https://issues.jboss.org/browse/WFLY-2693?page=com.atlassian.jira.plugin.... ] Stan Silvert commented on WFLY-2693: ------------------------------------ Thanks for the fix Philippe! > list-active-jsf-impls is missing reply type > ------------------------------------------- > > Key: WFLY-2693 > URL: https://issues.jboss.org/browse/WFLY-2693 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JSF > Reporter: Philippe Marschall > Assignee: Stan Silvert > > The DMR operation "list-active-jsf-impls" of the JSF subsystem is missing a reply type. Therefore the operation will show up as "Void" in VisualVM and no result will be displayed. -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2695) Creating named formater patterns for offline servers fail

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-2695?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-2695: -------------------------------- Steps to Reproduce: * extract wildfly-8.0.0.CR1 * run bin/domain * execute commands via CLI ** :stop-servers ** -/profile=full/subsystem=logging/console-handler=CONSOLE:remove- ** /profile=full/subsystem=logging/pattern-formatter=TESTPATTERN:add(pattern="%d%n") ** /profile=full/subsystem=logging/console-handler=CONSOLE:write-attribute(name=named-formatter, value=TESTPATTERN) ** /host=master/server-config=server-one:start was: * extract wildfly-8.0.0.CR1 * run bin/domain * execute commands via CLI ** :stop-servers ** /profile=full/subsystem=logging/console-handler=CONSOLE:remove ** /profile=full/subsystem=logging/pattern-formatter=TESTPATTERN:add(pattern="%d%n") ** /profile=full/subsystem=logging/console-handler=CONSOLE:write-attribute(name=named-formatter, value=TESTPATTERN) ** /host=master/server-config=server-one:start > Creating named formater patterns for offline servers fail > --------------------------------------------------------- > > Key: WFLY-2695 > URL: https://issues.jboss.org/browse/WFLY-2695 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Logging > Affects Versions: 8.0.0.CR1 > Environment: any domain configuration > Reporter: Matthias Berndt > Assignee: James Perkins > > After adding and attaching a named formatter to an offline server starting the server fails due to an invalid logging configuration. > server-one fails with: > {{ > [Server:server-one] 00:08:00,214 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("add") failed - address: ([ > [Server:server-one] ("subsystem" => "logging"), > [Server:server-one] ("console-handler" => "CONSOLE") > [Server:server-one] ]): java.lang.IllegalArgumentException: Formatter "TESTPATTERN" is not found > }} > I assume logging.properties is written too late in LoggingOperations.java -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2695) Creating named formater patterns for offline servers fail

by Matthias Berndt (JIRA)

Matthias Berndt created WFLY-2695: ------------------------------------- Summary: Creating named formater patterns for offline servers fail Key: WFLY-2695 URL: https://issues.jboss.org/browse/WFLY-2695 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Logging Affects Versions: 8.0.0.CR1 Environment: any domain configuration Reporter: Matthias Berndt Assignee: James Perkins After adding and attaching a named formatter to an offline server starting the server fails due to an invalid logging configuration. server-one fails with: {{ [Server:server-one] 00:08:00,214 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("add") failed - address: ([ [Server:server-one] ("subsystem" => "logging"), [Server:server-one] ("console-handler" => "CONSOLE") [Server:server-one] ]): java.lang.IllegalArgumentException: Formatter "TESTPATTERN" is not found }} I assume logging.properties is written too late in LoggingOperations.java -- 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

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2694) CLI example output for connecting to domain controller inaccurate

by Mark Little (JIRA)

Mark Little created WFLY-2694: --------------------------------- Summary: CLI example output for connecting to domain controller inaccurate Key: WFLY-2694 URL: https://issues.jboss.org/browse/WFLY-2694 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 8.0.0.CR1 Environment: Raspberry Pi Linux raspberrypi 3.2.27+ #250 PREEMPT Thu Oct 18 19:03:02 BST 2012 armv6l GNU/Linux Reporter: Mark Little Assignee: Tom Wells Priority: Minor According to https://docs.jboss.org/author/display/WFLY8/Management+Clients --- ./bin/jboss-cli.sh You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. [disconnected /] [disconnected /] connect Connected to domain controller at localhost:9999 ---- But no "Connected to domain controller" is output. No indication of success is given other than the next line of the CLI has the hostname (localhost) referenced. -- 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

10 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2013