[JBoss JIRA] (LOGTOOL-33) Validation of message types fails for out-of-order types
by Sanne Grinovero (Created) (JIRA)
Validation of message types fails for out-of-order types
--------------------------------------------------------
Key: LOGTOOL-33
URL: https://issues.jboss.org/browse/LOGTOOL-33
Project: Log Tool
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 1.0.0.CR2
Reporter: Sanne Grinovero
Assignee: David Lloyd
>From Infinispan:
{code}@LogMessage(level = WARN)
@Message(value = "Error committing cache view %2$d for cache %1$s", id = 169)
void cacheViewCommitFailure(@Cause Exception e, String cacheName, int committedViewId);
{code}
{code}
Log.java:797: Invalid format for 'Error committing cache view %2$d for cache %1$s' with parameters '[33, JBoss]'. java.util.Formatter Error: d != java.lang.String
{code}
I think the log message is correct, and the validator should not prevent this from being used.
I've a test case ready in a pull request I'm sending now.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (AS7-1738) CLI usability: unclear that the CLI is managing a domain not a host
by Radoslav Husar (JIRA)
CLI usability: unclear that the CLI is managing a domain not a host
-------------------------------------------------------------------
Key: AS7-1738
URL: https://issues.jboss.org/browse/AS7-1738
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.0.1.Final, 7.0.0.Final
Reporter: Radoslav Husar
Assignee: Alexey Loubyansky
Looks to me that the CLI is behaving differently if you are running in a domain mode or in a stadnalone mode managing just a host. However it is not really clear from the CLI help messages.
In the following log
* the console does not say its running in the domain mode
* claims that the --profile argument is optional even though its indeed required
* does not say that it is not the master domain controller and refuses all changes anyway
{code}
[domain@rhusar:9999 /] add-jms-queue --help
Synopsis: add-jms-queue [--profile=profile_name] --name=queue_name [--entries=entry(,entry)*] [--selector=selector_name] [--durable=(true|false)]
Description: creates a JMS queue
Arguments:
profile - is allowed and required only in the domain mode, specifies the profile
in which the JMS resource should be created.
name - the name of the queue.
entries - an optional comma-separated list of JNDI names the queue should be bound under.
If not present, the name will be used as the JNDI name.
selector - optional selector.
durable - optional, specifies whether the queue should be durable or not (the default is true).
[domain@rhusar:9999 /] add-jms-queue --profile=ha --name=rQ
Operation add for address [
("profile" => "ha"),
("subsystem" => "messaging"),
("jms-queue" => "rQ")
] can only handled by the master Domain Controller; this host is not the master Domain Controller
[domain@rhusar:9999 /] add-jms-queue --name=rQ
--profile argument value is missing.
[domain@rhusar:9999 /] quit
Closed connection to rhusar:9999
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] (AS7-2245) Help text needed for topics
by Kevin Barfield (Created) (JIRA)
Help text needed for topics
---------------------------
Key: AS7-2245
URL: https://issues.jboss.org/browse/AS7-2245
Project: Application Server 7
Issue Type: Bug
Components: Console
Reporter: Kevin Barfield
Assignee: Heiko Braun
There needs to be help text for each topic in the console - this help text should explain what the topic is, why it is important to the user, and maybe a link to the relevant docs section. This needs to be understandable by average people For example:
Datasource Configurations
Datasources are used to connect JBoss EAP to databases. This page allows admins to view existing datasources Admins can also create, modify, and delete datasources. Please see the datasource section of the documentation for more details about datasources <link>.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months