[JBoss JIRA] (WFLY-5682) Can't define absolute path for object store location
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-5682?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-5682:
----------------------------------------
The description of AS7-2078 describes the intended behavior in cases like this where the 'relative-to' attribute has a default value. Basically if the 'path' attribute is an absolute path, then relative-to should be ignored.
The text description of object-store-relative-to is inconsistent with the AS7-2078 fix, as it still describes the old hack behavior of treating '' as meaning null.
https://github.com/wildfly/wildfly/compare/master...bstansberry:WFLY-5682 shows how to restore the standard behavior.
Using a value like '/tmp' for a relative-to attribute as is attempted in [1] in the description is invalid. The values of relative-to attributes are the logical names of path resources, not filesystem paths.
> 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)
8 years, 4 months
[JBoss JIRA] (ELY-383) Update ServerAuthenticationContext to carry an identity from start to end
by David Lloyd (JIRA)
David Lloyd created ELY-383:
-------------------------------
Summary: Update ServerAuthenticationContext to carry an identity from start to end
Key: ELY-383
URL: https://issues.jboss.org/browse/ELY-383
Project: WildFly Elytron
Issue Type: Task
Components: API / SPI
Reporter: David Lloyd
Assignee: David Lloyd
Fix For: 1.1.0.Beta3
Attachments: Blank Flowchart - ServerAuthenticationContext.png
The {{ServerAuthenticationContext}} should capture the identity in force for its domain when it is constructed. Any authorization attempt should always apply to the current identity - either the captured identity, or whatever the last successfully authorized identity was in the context.
The attached state diagram should accurately summarize how authorization identity flows through. Authentication identity is only available during the "NAME ASSIGNED" state; once authorization occurs, the authentication identity is no longer useful and is disposed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months
[JBoss JIRA] (JGRP-1977) More redundant initial join logic to avoid becoming a fake coordinator
by Osamu Nagano (JIRA)
[ https://issues.jboss.org/browse/JGRP-1977?page=com.atlassian.jira.plugin.... ]
Osamu Nagano commented on JGRP-1977:
------------------------------------
OK, so I can tune timing of {{MERGE}} to minimize the period of several coordinators. If you come to your mind with any good workaround at discovery level, it's really appreciated.
> More redundant initial join logic to avoid becoming a fake coordinator
> ----------------------------------------------------------------------
>
> Key: JGRP-1977
> URL: https://issues.jboss.org/browse/JGRP-1977
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Osamu Nagano
> Assignee: Bela Ban
> Fix For: 3.6.7
>
>
> If the very initial JGroups discovery packet is lost, it is never recovered by the current GMS join logic. The node will be a standalone coordinator then merges after several minutes.
> This can happen if a new node reside in another network segment and a switch between the segments requires some time to establish a new multicast route. Currently, there is no enough time between IGMP join (by {{MulticastSocket#joinGroup()}}) and the JGroups discovery packet and the later is lost in such a network environment. Because the number of nodes can be very large, configuring a static route in the switch is not reasonable.
> Specifically, in method {{org.jgroups.protocols.pbcast.ClientGmsImpl#joinInternal()}}, part of {{gms.getDownProtocol().down(Event.FIND_INITIAL_MBRS_EVT)}} is outside of the retry loop of GMS.max_join_attempts and GMS.join_timeout.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months
[JBoss JIRA] (ELY-382) Add SASL server factory which has the ability to set a SecurityIdentity during authentication tasks
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/ELY-382?page=com.atlassian.jira.plugin.sy... ]
David Lloyd resolved ELY-382.
-----------------------------
Resolution: Rejected
On second thought, I'm rejecting this and throwing away the implementation.
The reason is that the callback handler is the thing which needs to track identity. The {{ServerAuthenticationContext}} should be capturing the active {{SecurityIdentity}} on instantiation, and maintaining an identity throughout the authentication process.
I will create a new JIRA, and a state machine diagram to illustrate the expected behavior of the authentication context.
> Add SASL server factory which has the ability to set a SecurityIdentity during authentication tasks
> ---------------------------------------------------------------------------------------------------
>
> Key: ELY-382
> URL: https://issues.jboss.org/browse/ELY-382
> Project: WildFly Elytron
> Issue Type: Task
> Components: SASL
> Reporter: David Lloyd
> Assignee: David Lloyd
>
> Add SASL server factory which has the ability to set a SecurityIdentity during authentication tasks. This is necessary so that (for example) EXTERNAL can perform authorization checks.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months
[JBoss JIRA] (WFLY-5479) rest api mashall object to json default not ignore null fileds
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-5479?page=com.atlassian.jira.plugin.... ]
Stuart Douglas resolved WFLY-5479.
----------------------------------
Fix Version/s: (was: 10.0.0.CR5)
Resolution: Rejected
Current behavior is expected. RESTeasy uses Jackson 2 for serialization, please refer to the Jackson docs for how to change this behavior.
> rest api mashall object to json default not ignore null fileds
> --------------------------------------------------------------
>
> Key: WFLY-5479
> URL: https://issues.jboss.org/browse/WFLY-5479
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 10.0.0.Beta1, 10.0.0.Beta2, 10.0.0.CR1, 10.0.0.CR2
> Reporter: henry hu
> Labels: jboss
>
> mashall object to Json default not ignore null fileds,but mashall to xml is ok .
> "user": {
> "id": 26357,
> "gameId": null,
> "userIds": null,
> "userName": "testn008",
> "status": 1,
> "password": null,
> "payPassword": null,
> "qq": null,
> "email": null,
> "userType": 16,
> "level": 0,
> "subCompany": null,
> "majorShareholder": null,
> "sharehoder": null,
> "majorAgent": null,
> "agent": null,
> "nickName": "sdfs",
> "cellPhoneNumber": null,
> "createTime": "2015-05-08 20:32:37",
> "currency": "CNY",
> "registerIp": "127.0.0.1",
> "lastLoginIP": "127.0.0.1",
> "lastLoginTime": 1444146936000,
> "roles": [],
> "roleIds": [],
> "userCount": 0,
> "fromId": null,
> "fromUrl": null,
> "hasUpdatePwd": 1,
> "isSpread": 0,
> "spreadType": null,
> "parentUserName": null,
> "memberCnt": null,
> "serverTime": "2015-10-06 23:58:40"
> },
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months