[JBoss JIRA] (WFLY-9010) Transformers for connetors
by ehsavoie Hugonnet (JIRA)
ehsavoie Hugonnet created WFLY-9010:
---------------------------------------
Summary: Transformers for connetors
Key: WFLY-9010
URL: https://issues.jboss.org/browse/WFLY-9010
Project: WildFly
Issue Type: Sub-task
Components: Domain Management
Affects Versions: 11.0.0.Alpha1
Reporter: ehsavoie Hugonnet
Assignee: ehsavoie Hugonnet
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-2968) Servers in a domain won't boot if local auth is disabled on the host controller
by Ken Wills (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2968?page=com.atlassian.jira.plugi... ]
Ken Wills commented on WFCORE-2968:
-----------------------------------
[~darranl]
After debugging this back and forth between core and elytron, I seem to be getting stuck on the expectation of how the authKey should get passed in HostControllerConnection. Previously we'd used a PasswordCallback, and put the key in there, with the new configuration, we appear to get a CredentialCallback.
I've tried using this one, and getting the callback invoked, but the password always returns null (Elytron: ServerAuthenticationContext:931). This is how the CLI is passing it's auth, so I'm a bit stumped to how that works there.
Any clues would be appreciated at this point, I'm probably doing something silly.
Basic changes here: https://github.com/luck3y/wildfly-core/tree/WFCORE-2968
The changes basically add support for the CredentialCallback in HostConnection (similar to what is being done for ServerInventory), and disable local auth for server authentication with the authKey.
> Servers in a domain won't boot if local auth is disabled on the host controller
> -------------------------------------------------------------------------------
>
> Key: WFCORE-2968
> URL: https://issues.jboss.org/browse/WFCORE-2968
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Security
> Reporter: James Perkins
> Assignee: Ken Wills
> Priority: Blocker
> Fix For: 3.0.0.Beta28
>
>
> If local authentication has been disabled on the host controller servers cannot communicate with the host controller and fail to start.
> {code}
> [Server:server-one] 15:10:51,241 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 2) MSC000001: Failed to start service jboss.server-boot-operations: org.jboss.msc.service.StartException in service jboss.server-boot-operations: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. The connection failed
> [Server:server-one] at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:72)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [Server:server-one] at java.lang.Thread.run(Thread.java:748)
> [Server:server-one] at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> [Server:server-one] Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. The connection failed
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:126)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:128)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:110)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:68)
> [Server:server-one] ... 4 more
> [Server:server-one] Caused by: javax.security.sasl.SaslException: Authentication failed: none of the mechanisms presented by the server (DIGEST-MD5) are supported
> [Server:server-one] at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:438)
> [Server:server-one] at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:246)
> [Server:server-one] at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> [Server:server-one] at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
> [Server:server-one] at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> [Server:server-one] at org.xnio.nio.WorkerThread.run(WorkerThread.java:571)
> [Server:server-one] at ...asynchronous invocation...(Unknown Source)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:545)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:509)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:497)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:194)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:118)
> [Server:server-one] ... 9 more
> [Server:server-one]
> [Server:server-one] 15:10:51,241 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: java.util.concurrent.ExecutionException: Operation failed
> [Server:server-one] at org.jboss.as.server.ServerStartTask$2$1.load(ServerStartTask.java:188)
> [Server:server-one] at org.jboss.as.server.ServerService.boot(ServerService.java:387)
> [Server:server-one] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:370)
> [Server:server-one] at java.lang.Thread.run(Thread.java:748)
> [Server:server-one] Caused by: java.util.concurrent.ExecutionException: Operation failed
> [Server:server-one] at org.jboss.threads.AsyncFutureTask.operationFailed(AsyncFutureTask.java:74)
> [Server:server-one] at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:268)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$2.get(ServerBootOperationsService.java:113)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$2.get(ServerBootOperationsService.java:95)
> [Server:server-one] at org.jboss.as.server.ServerStartTask$2$1.load(ServerStartTask.java:185)
> [Server:server-one] ... 3 more
> [Server:server-one] Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. The connection failed
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:126)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:128)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:110)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:68)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [Server:server-one] at java.lang.Thread.run(Thread.java:748)
> [Server:server-one] at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> [Server:server-one] Caused by: javax.security.sasl.SaslException: Authentication failed: none of the mechanisms presented by the server (DIGEST-MD5) are supported
> [Server:server-one] at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:438)
> [Server:server-one] at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:246)
> [Server:server-one] at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> [Server:server-one] at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
> [Server:server-one] at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> [Server:server-one] at org.xnio.nio.WorkerThread.run(WorkerThread.java:571)
> [Server:server-one] at ...asynchronous invocation...(Unknown Source)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:545)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:509)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:497)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:194)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:118)
> [Server:server-one] ... 9 more
> [Server:server-one]
> [Server:server-one] 15:10:51,243 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> [Server:server-one] 15:10:51,254 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0050: WildFly Core 3.0.0.Beta27-SNAPSHOT "Kenny" stopped in 6ms
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-2968) Servers in a domain won't boot if local auth is disabled on the host controller
by Ken Wills (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2968?page=com.atlassian.jira.plugi... ]
Ken Wills reassigned WFCORE-2968:
---------------------------------
Assignee: Ken Wills (was: Jan Kalina)
> Servers in a domain won't boot if local auth is disabled on the host controller
> -------------------------------------------------------------------------------
>
> Key: WFCORE-2968
> URL: https://issues.jboss.org/browse/WFCORE-2968
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Security
> Reporter: James Perkins
> Assignee: Ken Wills
> Priority: Blocker
> Fix For: 3.0.0.Beta28
>
>
> If local authentication has been disabled on the host controller servers cannot communicate with the host controller and fail to start.
> {code}
> [Server:server-one] 15:10:51,241 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 2) MSC000001: Failed to start service jboss.server-boot-operations: org.jboss.msc.service.StartException in service jboss.server-boot-operations: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. The connection failed
> [Server:server-one] at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:72)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [Server:server-one] at java.lang.Thread.run(Thread.java:748)
> [Server:server-one] at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> [Server:server-one] Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. The connection failed
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:126)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:128)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:110)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:68)
> [Server:server-one] ... 4 more
> [Server:server-one] Caused by: javax.security.sasl.SaslException: Authentication failed: none of the mechanisms presented by the server (DIGEST-MD5) are supported
> [Server:server-one] at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:438)
> [Server:server-one] at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:246)
> [Server:server-one] at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> [Server:server-one] at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
> [Server:server-one] at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> [Server:server-one] at org.xnio.nio.WorkerThread.run(WorkerThread.java:571)
> [Server:server-one] at ...asynchronous invocation...(Unknown Source)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:545)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:509)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:497)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:194)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:118)
> [Server:server-one] ... 9 more
> [Server:server-one]
> [Server:server-one] 15:10:51,241 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: java.util.concurrent.ExecutionException: Operation failed
> [Server:server-one] at org.jboss.as.server.ServerStartTask$2$1.load(ServerStartTask.java:188)
> [Server:server-one] at org.jboss.as.server.ServerService.boot(ServerService.java:387)
> [Server:server-one] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:370)
> [Server:server-one] at java.lang.Thread.run(Thread.java:748)
> [Server:server-one] Caused by: java.util.concurrent.ExecutionException: Operation failed
> [Server:server-one] at org.jboss.threads.AsyncFutureTask.operationFailed(AsyncFutureTask.java:74)
> [Server:server-one] at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:268)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$2.get(ServerBootOperationsService.java:113)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$2.get(ServerBootOperationsService.java:95)
> [Server:server-one] at org.jboss.as.server.ServerStartTask$2$1.load(ServerStartTask.java:185)
> [Server:server-one] ... 3 more
> [Server:server-one] Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. The connection failed
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:126)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:128)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:110)
> [Server:server-one] at org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:68)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [Server:server-one] at java.lang.Thread.run(Thread.java:748)
> [Server:server-one] at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> [Server:server-one] Caused by: javax.security.sasl.SaslException: Authentication failed: none of the mechanisms presented by the server (DIGEST-MD5) are supported
> [Server:server-one] at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:438)
> [Server:server-one] at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:246)
> [Server:server-one] at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> [Server:server-one] at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
> [Server:server-one] at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> [Server:server-one] at org.xnio.nio.WorkerThread.run(WorkerThread.java:571)
> [Server:server-one] at ...asynchronous invocation...(Unknown Source)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:545)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:509)
> [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:497)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:194)
> [Server:server-one] at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:118)
> [Server:server-one] ... 9 more
> [Server:server-one]
> [Server:server-one] 15:10:51,243 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> [Server:server-one] 15:10:51,254 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0050: WildFly Core 3.0.0.Beta27-SNAPSHOT "Kenny" stopped in 6ms
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-2999) Logging subsystem bump & transformers for EAP7
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2999?page=com.atlassian.jira.plugi... ]
James Perkins reopened WFCORE-2999:
-----------------------------------
> Logging subsystem bump & transformers for EAP7
> ----------------------------------------------
>
> Key: WFCORE-2999
> URL: https://issues.jboss.org/browse/WFCORE-2999
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: Tomaz Cerar
> Assignee: James Perkins
> Priority: Critical
>
> Currently model version of logging subsystem is 3.0.0 same as in EAP 7.0.
> but model diff reports changes to the model.
> So it needs model bump to 4.0.0, as well as transformers.
> As a bonus point, it would be really good performance wise if we could move transformers registration to use non deprecated ExtensionTransformerRegistration API.
> model diff:
> {noformat}
> ====== Resource root address: ["subsystem" => "logging"] - Current version: 3.0.0; legacy version: 3.0.0 =======
> --- Problems for relative address to root ["file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["log-file" => "*"]:
> Different 'type' for attribute 'stream'. Current: STRING; legacy: LONG
> --- Problems for relative address to root ["logging-profile" => "*","file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["logging-profile" => "*","log-file" => "*"]:
> Different 'type' for attribute 'stream'. Current: STRING; legacy: LONG
> --- Problems for relative address to root ["logging-profile" => "*","periodic-rotating-file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["logging-profile" => "*","periodic-size-rotating-file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["periodic-rotating-file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["periodic-size-rotating-file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-2999) Logging subsystem bump EAP7
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2999?page=com.atlassian.jira.plugi... ]
James Perkins updated WFCORE-2999:
----------------------------------
Summary: Logging subsystem bump EAP7 (was: Logging subsystem bump & transformers for EAP7)
> Logging subsystem bump EAP7
> ---------------------------
>
> Key: WFCORE-2999
> URL: https://issues.jboss.org/browse/WFCORE-2999
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: Tomaz Cerar
> Assignee: James Perkins
> Priority: Critical
>
> Currently model version of logging subsystem is 3.0.0 same as in EAP 7.0.
> but model diff reports changes to the model.
> So it needs model bump to 4.0.0, as well as transformers.
> As a bonus point, it would be really good performance wise if we could move transformers registration to use non deprecated ExtensionTransformerRegistration API.
> model diff:
> {noformat}
> ====== Resource root address: ["subsystem" => "logging"] - Current version: 3.0.0; legacy version: 3.0.0 =======
> --- Problems for relative address to root ["file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["log-file" => "*"]:
> Different 'type' for attribute 'stream'. Current: STRING; legacy: LONG
> --- Problems for relative address to root ["logging-profile" => "*","file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["logging-profile" => "*","log-file" => "*"]:
> Different 'type' for attribute 'stream'. Current: STRING; legacy: LONG
> --- Problems for relative address to root ["logging-profile" => "*","periodic-rotating-file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["logging-profile" => "*","periodic-size-rotating-file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["periodic-rotating-file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["periodic-size-rotating-file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-2999) Logging subsystem bump EAP7
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2999?page=com.atlassian.jira.plugi... ]
James Perkins commented on WFCORE-2999:
---------------------------------------
No transformer will be needed, but a version bump is required.
> Logging subsystem bump EAP7
> ---------------------------
>
> Key: WFCORE-2999
> URL: https://issues.jboss.org/browse/WFCORE-2999
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: Tomaz Cerar
> Assignee: James Perkins
> Priority: Critical
>
> Currently model version of logging subsystem is 3.0.0 same as in EAP 7.0.
> but model diff reports changes to the model.
> So it needs model bump to 4.0.0, as well as transformers.
> As a bonus point, it would be really good performance wise if we could move transformers registration to use non deprecated ExtensionTransformerRegistration API.
> model diff:
> {noformat}
> ====== Resource root address: ["subsystem" => "logging"] - Current version: 3.0.0; legacy version: 3.0.0 =======
> --- Problems for relative address to root ["file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["log-file" => "*"]:
> Different 'type' for attribute 'stream'. Current: STRING; legacy: LONG
> --- Problems for relative address to root ["logging-profile" => "*","file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["logging-profile" => "*","log-file" => "*"]:
> Different 'type' for attribute 'stream'. Current: STRING; legacy: LONG
> --- Problems for relative address to root ["logging-profile" => "*","periodic-rotating-file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["logging-profile" => "*","periodic-size-rotating-file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["periodic-rotating-file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["periodic-size-rotating-file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-2999) Logging subsystem bump & transformers for EAP7
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2999?page=com.atlassian.jira.plugi... ]
James Perkins closed WFCORE-2999.
---------------------------------
Resolution: Rejected
The {{path-info}} is not available on the domain profile and therefore does not need a transformer. The type difference on the {{stream}} attribute was a bug and should have been a {{STRING}} from the beginning.
> Logging subsystem bump & transformers for EAP7
> ----------------------------------------------
>
> Key: WFCORE-2999
> URL: https://issues.jboss.org/browse/WFCORE-2999
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: Tomaz Cerar
> Assignee: James Perkins
> Priority: Critical
>
> Currently model version of logging subsystem is 3.0.0 same as in EAP 7.0.
> but model diff reports changes to the model.
> So it needs model bump to 4.0.0, as well as transformers.
> As a bonus point, it would be really good performance wise if we could move transformers registration to use non deprecated ExtensionTransformerRegistration API.
> model diff:
> {noformat}
> ====== Resource root address: ["subsystem" => "logging"] - Current version: 3.0.0; legacy version: 3.0.0 =======
> --- Problems for relative address to root ["file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["log-file" => "*"]:
> Different 'type' for attribute 'stream'. Current: STRING; legacy: LONG
> --- Problems for relative address to root ["logging-profile" => "*","file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["logging-profile" => "*","log-file" => "*"]:
> Different 'type' for attribute 'stream'. Current: STRING; legacy: LONG
> --- Problems for relative address to root ["logging-profile" => "*","periodic-rotating-file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["logging-profile" => "*","periodic-size-rotating-file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["periodic-rotating-file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> --- Problems for relative address to root ["periodic-size-rotating-file-handler" => "*"]:
> Missing operations in current: []; missing in legacy [path-info]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-3022) WildFly Servlet should provide license data
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3022?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-3022:
-------------------------------------
Description: The servlet-feature-pack should provide license data in the same manner the "full" feature-pack in does. (was: The core-feature-pack should provide license data in the same manner the "full" feature-pack in WildFly does.)
> WildFly Servlet should provide license data
> -------------------------------------------
>
> Key: WFCORE-3022
> URL: https://issues.jboss.org/browse/WFCORE-3022
> Project: WildFly Core
> Issue Type: Task
> Components: Server
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 11.0.0.Beta1
>
>
> The servlet-feature-pack should provide license data in the same manner the "full" feature-pack in does.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months