[JBoss JIRA] (WFCORE-2526) Domain mode passed unwanted sys props to spawned servers
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2526?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-2526:
-------------------------------------
Component/s: Domain Management
Fix Version/s: 3.0.0.Beta25
Priority: Critical (was: Major)
> Domain mode passed unwanted sys props to spawned servers
> --------------------------------------------------------
>
> Key: WFCORE-2526
> URL: https://issues.jboss.org/browse/WFCORE-2526
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: John Mazzitelli
> Priority: Critical
> Fix For: 3.0.0.Beta25
>
>
> This is related to WFCORE-350, except the solution to that only involves filtering out some but not all unwanted sys props.
> I would say the solution should involve any properties, not just jboss.server.xxx properties.
> In my case, I'm trying to inject a javaagent into the host controller but I do NOT want the javaagent in the spawned servers. Because my javaagent uses JBoss Logging (JUL) I'm forced to pass in "-Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager" and
> "-Djava.util.logging.manager=org.jboss.logmanager.LogManager" so the host controller can start up.
> But these gets passed to the spawned servers and causes them to fail to boot up (because while my -javaagent command line argument isn't passed to their JVM, the -D sys props are and those combination of sys props are deadly without a JUL-enabled javaagent).
> See: http://lists.jboss.org/pipermail/wildfly-dev/2017-March/005810.html
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-8900) Regression in DR19, Elytron unable to authenticate with kerberos using jboss-cli
by Martin Choma (JIRA)
Martin Choma created WFLY-8900:
----------------------------------
Summary: Regression in DR19, Elytron unable to authenticate with kerberos using jboss-cli
Key: WFLY-8900
URL: https://issues.jboss.org/browse/WFLY-8900
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Martin Choma
Assignee: Darran Lofthouse
Priority: Blocker
Trying to connect with jboss-cli to server using kerberos leads to error
{code}
14:41:22,654 TRACE [org.wildfly.security.sasl.gssapi.server] (management task-7) Client selected security layer AUTH, with maxBuffer of 65536
14:41:22,655 TRACE [org.jboss.remoting.remote.server] (management task-7) Server sending authentication rejected: javax.security.sasl.SaslException: ELY05123: [GSSAPI] No security layer selected but message length received
at org.wildfly.security.sasl.gssapi.GssapiServer.evaluateMessage(GssapiServer.java:245)
at org.wildfly.security.sasl.util.AbstractSaslParticipant.evaluateMessage(AbstractSaslParticipant.java:180)
at org.wildfly.security.sasl.gssapi.GssapiServer.evaluateResponse(GssapiServer.java:121)
at org.wildfly.security.sasl.util.AuthenticationCompleteCallbackSaslServerFactory$1.evaluateResponse(AuthenticationCompleteCallbackSaslServerFactory.java:58)
at org.wildfly.security.sasl.util.AuthenticationTimeoutSaslServerFactory$DelegatingTimeoutSaslServer.evaluateResponse(AuthenticationTimeoutSaslServerFactory.java:106)
at org.wildfly.security.sasl.util.SecurityIdentitySaslServerFactory$1.evaluateResponse(SecurityIdentitySaslServerFactory.java:57)
at org.xnio.sasl.SaslUtils.evaluateResponse(SaslUtils.java:245)
at org.xnio.sasl.SaslUtils.evaluateResponse(SaslUtils.java:217)
at org.jboss.remoting3.remote.ServerConnectionOpenListener$AuthStepRunnable.run(ServerConnectionOpenListener.java:470)
at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:902)
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)
{code}
Error message is little bit confusing as previous log message claims AUTH security layer is selected.
Looking into code does not reveal meaning to me neither.
{code:java|title=GssapiServer.java}
log.tracef("Client selected security layer %s, with maxBuffer of %d", selectedQop, maxBuffer);
if (relaxComplianceChecks == false && selectedQop == QOP.AUTH && maxBuffer != 0) {
throw log.mechNoSecurityLayerButLengthReceived(getMechanismName()).toSaslException();
}
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-8889) Cannot find symbol class HttpServlet30Dispatcher
by Panagiotis Sotiropoulos (JIRA)
[ https://issues.jboss.org/browse/WFLY-8889?page=com.atlassian.jira.plugin.... ]
Panagiotis Sotiropoulos updated WFLY-8889:
------------------------------------------
Git Pull Request: https://github.com/wildfly/wildfly/pull/10143
> Cannot find symbol class HttpServlet30Dispatcher
> ------------------------------------------------
>
> Key: WFLY-8889
> URL: https://issues.jboss.org/browse/WFLY-8889
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 11.0.0.Alpha1
> Reporter: Panagiotis Sotiropoulos
> Assignee: Panagiotis Sotiropoulos
>
> When downloading and building wildfly I get the following error :
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.6.0:compile (default-compile) on project wildfly-jaxrs: Compilation failure: Compilation failure:
> [ERROR] ~/wildfly/jaxrs/src/main/java/org/jboss/as/jaxrs/deployment/JaxrsIntegrationProcessor.java:[56,49] cannot find symbol
> [ERROR] symbol: class HttpServlet30Dispatcher
> [ERROR] location: package org.jboss.resteasy.plugins.server.servlet
> [ERROR] ~/wildfly/jaxrs/src/main/java/org/jboss/as/jaxrs/deployment/JaxrsScanningProcessor.java:[60,49] cannot find symbol
> [ERROR] symbol: class HttpServlet30Dispatcher
> [ERROR] location: package org.jboss.resteasy.plugins.server.servlet
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (DROOLS-1582) Split kie-ci
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1582?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-1582:
-----------------------------------
Sprint: BxMS70-Iteration2, Sprint 3, 2017 Week 22-23 - remove (was: BxMS70-Iteration2, 2017 Week 24-25, 2017 Week 22-23 - remove)
> Split kie-ci
> ------------
>
> Key: DROOLS-1582
> URL: https://issues.jboss.org/browse/DROOLS-1582
> Project: Drools
> Issue Type: Task
> Components: core engine
> Reporter: Mario Fusco
> Assignee: Mario Fusco
>
> The maven integration features currently implemented by kie-ci are useful also for other projects like AppFormer. It is then required to split it in 2 modules, one only dependant on maven/aether and providing general maven integration facilities and the second dependant on both the first and drools and implementing drools incremental compilation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (DROOLS-1582) Split kie-ci
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1582?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-1582:
-----------------------------------
Sprint: BxMS70-Iteration2, Sprint 3, 2017 Week 24-25, 2017 Week 22-23 - remove (was: BxMS70-Iteration2, Sprint 3, 2017 Week 22-23 - remove)
> Split kie-ci
> ------------
>
> Key: DROOLS-1582
> URL: https://issues.jboss.org/browse/DROOLS-1582
> Project: Drools
> Issue Type: Task
> Components: core engine
> Reporter: Mario Fusco
> Assignee: Mario Fusco
>
> The maven integration features currently implemented by kie-ci are useful also for other projects like AppFormer. It is then required to split it in 2 modules, one only dependant on maven/aether and providing general maven integration facilities and the second dependant on both the first and drools and implementing drools incremental compilation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (DROOLS-1582) Split kie-ci
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1582?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-1582:
-----------------------------------
Sprint: BxMS70-Iteration2, Sprint 3, 2017 Week 22-23, 2017 Week 22-23 - remove (was: BxMS70-Iteration2, Sprint 3, 2017 Week 24-25, 2017 Week 22-23 - remove)
> Split kie-ci
> ------------
>
> Key: DROOLS-1582
> URL: https://issues.jboss.org/browse/DROOLS-1582
> Project: Drools
> Issue Type: Task
> Components: core engine
> Reporter: Mario Fusco
> Assignee: Mario Fusco
>
> The maven integration features currently implemented by kie-ci are useful also for other projects like AppFormer. It is then required to split it in 2 modules, one only dependant on maven/aether and providing general maven integration facilities and the second dependant on both the first and drools and implementing drools incremental compilation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (DROOLS-1582) Split kie-ci
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1582?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-1582:
-----------------------------------
Sprint: BxMS70-Iteration2, 2017 Week 24-25, 2017 Week 22-23 - remove (was: BxMS70-Iteration2, 2017 Week 22-23 - remove)
> Split kie-ci
> ------------
>
> Key: DROOLS-1582
> URL: https://issues.jboss.org/browse/DROOLS-1582
> Project: Drools
> Issue Type: Task
> Components: core engine
> Reporter: Mario Fusco
> Assignee: Mario Fusco
>
> The maven integration features currently implemented by kie-ci are useful also for other projects like AppFormer. It is then required to split it in 2 modules, one only dependant on maven/aether and providing general maven integration facilities and the second dependant on both the first and drools and implementing drools incremental compilation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (DROOLS-1582) Split kie-ci
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1582?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-1582:
-----------------------------------
Sprint: 2017 Week 22-23 - remove (was: 2017 Week 22-23)
> Split kie-ci
> ------------
>
> Key: DROOLS-1582
> URL: https://issues.jboss.org/browse/DROOLS-1582
> Project: Drools
> Issue Type: Task
> Components: core engine
> Reporter: Mario Fusco
> Assignee: Mario Fusco
>
> The maven integration features currently implemented by kie-ci are useful also for other projects like AppFormer. It is then required to split it in 2 modules, one only dependant on maven/aether and providing general maven integration facilities and the second dependant on both the first and drools and implementing drools incremental compilation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month