[
https://issues.jboss.org/browse/WFLY-5682?page=com.atlassian.jira.plugin....
]
Ondřej Chaloupka commented on WFLY-5682:
----------------------------------------
Hi Amos,
it took me a bit to look at the change. In general my the most aching point was not being
able to set absolute path for object store. This seems being fixed. But I have an one
more request here and one doubt.
The request is to change description of {{object-store-relative-to}}. If this PR fixes the
issue can you please emphasize the fact that {{relative-to}} can be set only to some
specific values? Then I think that sentence {{force the value of the "path"
attribute to be treated as an absolute path}} should be rather using object-store-path
attribute name like {{force the value of the "object-store-path" attribute to be
treated as an absolute path}}.
My doubt here is that in general I do not like the fixed behavior too much. It's only
my personal feeling and I can be truly wrong here. If it's ok from your point of view
I can verify the issue without more words. But meanwhile my points are
- why I can't set any path as value of {{object-store-relative-to}}? There is some
hard restriction to that?
- I can't use expressions like {{${system.property}}} even if {{expression-allowed}}
is {{true}}
- how can user know what values are correct for the {{object-store-relative-to}}
attribute. Even it will be documented there is no logical clue why it's so.
Can't define absolute path for object store location
----------------------------------------------------
Key: WFLY-5682
URL:
https://issues.jboss.org/browse/WFLY-5682
Project: WildFly
Issue Type: Bug
Components: Transactions
Affects Versions: 10.0.0.CR4
Reporter: Ondřej Chaloupka
Assignee: Amos Feng
Fix For: 10.0.0.CR5
As trying to set absolute path for location of transaction log store I've got to
suspicion that's not possible.
If I try to set `object-store-relative-to` to some absolute path or set
`object-store-relative-to` to empty string and then `object-store-path` to some absolute
path the server starts with exceptions [1][2].
[1]
{code}
ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start
service jboss.txn.ArjunaObjectStoreEnvironment: org.jboss.msc.service.StartException in
service jboss.txn.ArjunaObjectStoreEnvironment: Failed to start service
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)Caused by: java.lang.IllegalArgumentException:
WFLYCTL0256: Could not find a path called '/home/ochaloup/tmp/'
at
org.jboss.as.controller.services.path.PathManagerService.resolveRelativePathEntry(PathManagerService.java:87) at
org.jboss.as.txn.service.ArjunaObjectStoreEnvironmentService.start(ArjunaObjectStoreEnvironmentService.java:76)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
...
ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread)
WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" =>
"transactions")]) - failure description: {"WFLYCTL0080: Failed
services" => {"jboss.txn.ArjunaObjectStoreEnvironment" =>
"org.jboss.msc.service.StartException in service
jboss.txn.ArjunaObjectStoreEnvironment: Failed to start service
Caused by: java.lang.IllegalArgumentException: WFLYCTL0256: Could not find a path
called '/home/ochaloup/tmp/'"}}
INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status
reportWFLYCTL0186: Services which failed to start: service
jboss.txn.ArjunaObjectStoreEnvironment: org.jboss.msc.service.StartException in service
jboss.txn.ArjunaObjectStoreEnvironment: Failed to start service
{code}
[2]
{code}
ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during
boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085:
Failed to parse configuration
at
org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131)
at org.jboss.as.server.ServerService.boot(ServerService.java:356) at
org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299)
at java.lang.Thread.run(Thread.java:745)
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[348,13]
Message: "WFLYCTL0113: '' is an invalid value for parameter relative-to.
Values must have a minimum length of 1 characters"
at
org.jboss.as.controller.SimpleAttributeDefinition.parse(SimpleAttributeDefinition.java:161) at
org.jboss.as.controller.SimpleAttributeDefinition.parseAndSetParameter(SimpleAttributeDefinition.java:186)
at
org.jboss.as.txn.subsystem.TransactionSubsystem14Parser.parseObjectStoreEnvironmentElementAndEnrichOperation(TransactionSubsystem14Parser.java:205)
at
org.jboss.as.txn.subsystem.TransactionSubsystem30Parser.readElement(TransactionSubsystem30Parser.java:67) at
org.jboss.as.txn.subsystem.TransactionSubsystem14Parser.readElement(TransactionSubsystem14Parser.java:111)
at
org.jboss.as.txn.subsystem.TransactionSubsystem14Parser.readElement(TransactionSubsystem14Parser.java:54) at
org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
at
org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) at
org.jboss.as.server.parsing.StandaloneXml_4.parseServerProfile(StandaloneXml_4.java:547)
at
org.jboss.as.server.parsing.StandaloneXml_4.readServerElement(StandaloneXml_4.java:244) at
org.jboss.as.server.parsing.StandaloneXml_4.readElement(StandaloneXml_4.java:143)
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:69) at
org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:47) at
org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) at
org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123)
... 3 more
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)