[JBoss JIRA] (WFCORE-2499) Elytron, using wrong provider-http-server-mechanism-factory does not generates any log messages
by Martin Choma (JIRA)
Martin Choma created WFCORE-2499:
------------------------------------
Summary: Elytron, using wrong provider-http-server-mechanism-factory does not generates any log messages
Key: WFCORE-2499
URL: https://issues.jboss.org/browse/WFCORE-2499
Project: WildFly Core
Issue Type: Bug
Components: Security
Reporter: Martin Choma
Assignee: Darran Lofthouse
When I secure management interface with wrongly configured http-authentication-factory and try to authenticate I get no error except of warning during boot
{code}
11:41:16,140 WARN [org.jboss.as.remoting] (MSC service thread 1-2) ****** All authentication is ANONYMOUS for org.jboss.as.remoting.RemotingHttpUpgradeService
{code}
But user is not able to know what is going wrong.
When I do similar for deployment there is at least error during boot:
{code}
14:30:59,608 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 63) MSC000001: Failed to start service jboss.undertow.deployment.default-server.default-host./secured-webapp: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./secured-webapp: java.lang.RuntimeException: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory.
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:84)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
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)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
Caused by: java.lang.RuntimeException: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory.
at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:241)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:99)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:81)
... 6 more
Caused by: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory.
at org.wildfly.extension.undertow.ApplicationSecurityDomainDefinition$ApplicationSecurityDomainService.initialSecurityHandler(ApplicationSecurityDomainDefinition.java:463)
at org.wildfly.extension.undertow.ApplicationSecurityDomainDefinition$ApplicationSecurityDomainService.lambda$applyElytronSecurity$2(ApplicationSecurityDomainDefinition.java:425)
at io.undertow.servlet.core.DeploymentManagerImpl.setupSecurityHandlers(DeploymentManagerImpl.java:415)
at io.undertow.servlet.core.DeploymentManagerImpl.access$600(DeploymentManagerImpl.java:119)
at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:211)
at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:174)
at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1704)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1704)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1704)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1704)
at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:239)
... 8 more
14:30:59,613 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "secured-webapp.war")]) - failure description: {
"WFLYCTL0080: Failed services" => {"jboss.undertow.deployment.default-server.default-host./secured-webapp" => "org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./secured-webapp: java.lang.RuntimeException: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory.
Caused by: java.lang.RuntimeException: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory.
Caused by: java.lang.IllegalStateException: WFLYUT0084: There are no mechanisms available from the HttpAuthenticationFactory."},
"WFLYCTL0412: Required services that are not installed:" => ["jboss.undertow.deployment.default-server.default-host./secured-webapp"]
}
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (DROOLS-1469) Using ExternalSpreadsheetCompiler in osgi throws java.lang.ClassNotFoundException
by Manjunath S Paramesan (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1469?page=com.atlassian.jira.plugi... ]
Manjunath S Paramesan commented on DROOLS-1469:
-----------------------------------------------
Hi,
I have added a reproducer.
The bundle with the compiler https://github.com/manjunath-sp/drools-template-issue-reproducer/tree/mas...
The PAX exam to reproduce the issue https://github.com/manjunath-sp/drools-template-issue-reproducer/tree/mas...
The issue seems to occur when rules are compiled in the init-method of the bundle, whereas when invoked as service the compilation works.
Thanks,
Manjunath
> Using ExternalSpreadsheetCompiler in osgi throws java.lang.ClassNotFoundException
> ---------------------------------------------------------------------------------
>
> Key: DROOLS-1469
> URL: https://issues.jboss.org/browse/DROOLS-1469
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Reporter: Mario Fusco
> Assignee: Mario Fusco
>
> Trying to compile a rule template using ExternalSpreadsheetCompiler, the rule compilation works correctly in stand alone eclipse project, but when done inside an OSGI bundle the following exception is throw at runtime:
> {code}
> java.lang.ClassNotFoundException: Unable to find class 'org.drools.template.parser.DefaultGenerator'
> at org.drools.core.base.ClassTypeResolver.resolveType(ClassTypeResolver.java:241)
> at org.drools.core.base.ClassTypeResolver.resolveType(ClassTypeResolver.java:130)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.processGlobals(KnowledgeBuilderImpl.java:1640)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.processOtherDeclarations(KnowledgeBuilderImpl.java:1613)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.mergePackage(KnowledgeBuilderImpl.java:1605)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.addPackage(KnowledgeBuilderImpl.java:980)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.addPackageFromDrl(KnowledgeBuilderImpl.java:365)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.addPackageFromDrl(KnowledgeBuilderImpl.java:341)
> at org.drools.template.parser.DefaultTemplateRuleBase.readKnowledgeBase(DefaultTemplateRuleBase.java:133)
> at org.drools.template.parser.DefaultTemplateRuleBase.<init>(DefaultTemplateRuleBase.java:56)
> at org.drools.template.parser.TemplateDataListener.<init>(TemplateDataListener.java:74)
> at org.drools.decisiontable.ExternalSpreadsheetCompiler.compile(ExternalSpreadsheetCompiler.java:99)
> at org.drools.decisiontable.ExternalSpreadsheetCompiler.compile(ExternalSpreadsheetCompiler.java:85)
> at com.mlnms.common.fmwk.drools.impl.DroolsBundleTracker.compileRules(DroolsBundleTracker.java:204)
> at com.mlnms.common.fmwk.drools.impl.DroolsBundleTracker.addNewRulesFromContexts(DroolsBundleTracker.java:183)
> at com.mlnms.common.fmwk.drools.impl.DroolsBundleTracker.addingBundle(DroolsBundleTracker.java:119)
> at com.mlnms.common.fmwk.drools.impl.DroolsBundleTracker.addingBundle(DroolsBundleTracker.java:67)
> at org.osgi.util.tracker.BundleTracker$Tracked.customizerAdding(BundleTracker.java:467)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8306) Soap attachments are being truncated when moving from jboss 7 to wildfly9/10
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-8306?page=com.atlassian.jira.plugin.... ]
Stuart Douglas commented on WFLY-8306:
--------------------------------------
You are going to need to provide more details, ideally some kind of reproducer. In particular:
- How big is the zip, is it larger that the default max-entity-size of 10mb?
- Fixed length or chunked?
> Soap attachments are being truncated when moving from jboss 7 to wildfly9/10
> ----------------------------------------------------------------------------
>
> Key: WFLY-8306
> URL: https://issues.jboss.org/browse/WFLY-8306
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.1.0.Final
> Environment: Windows
> Reporter: Einat Peretz
> Assignee: Stuart Douglas
> Priority: Blocker
>
> Client access wildfly 9 or 10 web service (soap using Axis2) using https with zip attachment and the zip is received truncated on the server.
> The same deployed application with same client worked fine on Jboss 7.3.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months