[
https://issues.jboss.org/browse/AS7-3986?page=com.atlassian.jira.plugin.s...
]
Richard Achmatowicz edited comment on AS7-3986 at 3/4/12 4:00 PM:
------------------------------------------------------------------
This latter issue, not being able to write the default-cache-container attribute, is now
fixed
byhttps://issues.jboss.org/browse/AS7-3705.
The first issue shows two problems:
- the model contains a name attribute which is not writable; this should not be present as
the cache name is not stored in the model but embedded the resource address
- the model contains a mode attribute which cannot be changed for local caches
These should be resolved as follows:
The name attribute will be removed entirely and any processing which makes use of it will
consult the resource addrss.
The mode attribute is actually valid for all caches *except* local caches. It has the
values {SYNC, ASYNC} and these can be adjusted from the CLI. The error here is that it
shows up in the local cache model. I'll remove that today was well in the pull request
for this issue.
Thanks for pointing these issues out.
was (Author: rachmato):
This latter issue, not being able to write the default-cache-container attribute, is
now fixed
byhttps://issues.jboss.org/browse/AS7-3705.
The first issue shows two problems:
- the model contains a name attribute which is not writable; this should not be present as
the cache name is not stored in the model but embedded the resource address
- the model contains a mode attribute which cannot be changed for local caches
These should be resolved as follows:
The name attribute will be removed entirely and any processing which makes use of it will
consult the resource addrss.
The mode attribute is actually valid for all caches *except* local caches. It has the
values {SYNC, ASYNC} and these can be adjusted from the CLI. The error here is that it
shows up in the local cache model. I'll remove that today was well in the pull request
for this issue.
Attribute mode unknown for ISPN cache
-------------------------------------
Key: AS7-3986
URL:
https://issues.jboss.org/browse/AS7-3986
Project: Application Server 7
Issue Type: Bug
Components: Clustering, Domain Management
Affects Versions: 7.1.0.Final
Reporter: Heiko Rupp
Assignee: Richard Achmatowicz
Labels: rhq
Fix For: 7.1.1.Final
Domain-API says that the attribute 'mode' for a cache does not exist, while it
clearly is shown on a :read-resource operation.
snert:~/downloads/jboss-eap-6.0 hrupp$ bin/jboss-cli.sh --connect
[standalone@localhost:9999 /] cd
/subsystem=infinispan/cache-container=myContainer/local-cache=aCache
[standalone@localhost:9999 local-cache=aCache] :read-resource
read-resource read-resource-description
[standalone@localhost:9999 local-cache=aCache] :read-resource
{
"outcome" => "success",
"result" => {
"batching" => undefined,
"eviction" => undefined,
"expiration" => undefined,
"file-store" => undefined,
"indexing" => undefined,
"jdbc-store" => undefined,
"jndi-name" => undefined,
"locking" => undefined,
"mode" => "LOCAL",
"name" => "aCache",
"remote-store" => undefined,
"start" => undefined,
"store" => undefined,
"transaction" => undefined
}
}
[standalone@localhost:9999 local-cache=aCache] :write-attribute(name=mode,value=SYNC)
{
"outcome" => "failed",
"failure-description" => "JBAS014792: Unknown attribute
mode",
"rolled-back" => true
}
same applies for other listed attributes like jdbc-store.
--
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