[JBoss JIRA] (WFCORE-3522) Module dependency order for a deployment is wrong
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3522?page=com.atlassian.jira.plugi... ]
David Lloyd updated WFCORE-3522:
--------------------------------
Fix Version/s: (was: 4.0.0.Alpha10)
(was: 3.1.0.Final)
> Module dependency order for a deployment is wrong
> -------------------------------------------------
>
> Key: WFCORE-3522
> URL: https://issues.jboss.org/browse/WFCORE-3522
> Project: WildFly Core
> Issue Type: Bug
> Affects Versions: 3.0.8.Final
> Reporter: Ken Finnigan
> Assignee: David Lloyd
> Priority: Blocker
>
> Within WildFly Swarm we need the ability to override the `javax.ws.rs.client.ClientBuilder` service file for a deployment to provide custom handling for implementing Eclipse MicroProfile.
> With a service file present in the deployment, the existing RESTEasy service file is always found first because the deployment module is added as a dependency after other non local dependencies. See https://github.com/wildfly/wildfly-core/blob/master/server/src/main/java/...
> After discussing with [~dmlloyd] on IRC, he agreed this was a bug and a better solution was for the deployment's dependency to always be first if `isLocalLast()` is false, and instead remove any spec packages that might be present on the deployment path instead.
> He explained the purpose of this ordering was to prevent a user deploying `javax.servlet.api` and breaking things, but it appears this can be achieved by alternative methods.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10342) Unsecured EJB causes "Multiple security domains" exception
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-10342?page=com.atlassian.jira.plugin... ]
Jan Kalina commented on WFLY-10342:
-----------------------------------
I have draft of possible fix: https://github.com/hkalina/wildfly/commits/WFLY-10342
This would ensure the exception will not be thrown for unsecured beans. But it will also remove it for secured beans without SecurityDomain annotation - where should be default security domain used -> exception thrown.
Problem is, scanning for security annotations is done in EJBSecurityViewConfigurator AFTER this check is in EJBDefaultSecurityDomainProcessor done :/
> Unsecured EJB causes "Multiple security domains" exception
> ----------------------------------------------------------
>
> Key: WFLY-10342
> URL: https://issues.jboss.org/browse/WFLY-10342
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 12.0.0.Final
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Priority: Critical
>
> When trying to deploy deployment containing following two EJBs, secured and unsecured, deploying fails with "Multiple security domains not supported" exception:
> {code}
> 21:16:30,089 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."ejb-deployment-1.0-SNAPSHOT.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."ejb-deployment-1.0-SNAPSHOT.war".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment "ejb-deployment-1.0-SNAPSHOT.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:150)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEJB0490: Multiple security domains not supported
> at org.jboss.as.ejb3.deployment.processors.EJBDefaultSecurityDomainProcessor.deploy(EJBDefaultSecurityDomainProcessor.java:99)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:143)
> ... 8 more
> {code}
> This behavior was in JBEAP-9289 considered correct for situation when one EJB references one security domain and the second references second security domain.
> It seems unsecured EJB is considered to be using default security domain.
> *Workaround:* Need to set unsecured bean secured by adding:
> {code}
> @PermitAll
> @SecurityDomain("other2") // the same as for secured ejb
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10349) WeldBundledLibraryDeployment Test cases fail on IBM jdk
by Petr Kremensky (JIRA)
[ https://issues.jboss.org/browse/WFLY-10349?page=com.atlassian.jira.plugin... ]
Petr Kremensky commented on WFLY-10349:
---------------------------------------
[~manovotn] I'll check it out and let you know.
> WeldBundledLibraryDeployment Test cases fail on IBM jdk
> -------------------------------------------------------
>
> Key: WFLY-10349
> URL: https://issues.jboss.org/browse/WFLY-10349
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, Test Suite
> Environment: {noformat}
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: /usr/lib/maven
> Java version: 1.8.0_161, vendor: IBM Corporation
> Java home: /usr/lib/java/ibm-java-8.0-5.11/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.15.17-300.fc27.x86_64", arch: "amd64", family: "unix"
> $ git rev-parse --short HEAD
> 11e21f08d3
> {noformat}
> Reporter: Petr Kremensky
> Assignee: Martin Kouba
>
> WeldBundledLibraryDeploymentEarTestCase and WeldBundledLibraryDeploymentTestCase fails on IBM jdk.
> *reproduce*
> {noformat}
> git clone https://github.com/wildfly/wildfly.git ; cd wildfly
> mvn clean install -B -DskipTests
> cd testsuite/integration/basic
> mvn test -Dtest=WeldBundledLibraryDeploymentEarTestCase,WeldBundledLibraryDeploymentTestCase -DtestLogToFile=false
> ...
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR] WeldBundledLibraryDeploymentEarTestCase.org.jboss.as.test.integration.weld.multideployment.WeldBundledLibraryDeploymentEarTestCase » Deployment
> [ERROR] WeldBundledLibraryDeploymentTestCase.org.jboss.as.test.integration.weld.multideployment.WeldBundledLibraryDeploymentTestCase » Deployment
> [INFO]
> [ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0
> {noformat}
>
> *server log errors*
> {noformat}
> 11:56:22,104 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.extension-index: org.jboss.msc.service.StartException in service jboss.deployment.extension-index: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1728)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:811)
> Caused by: java.lang.NullPointerException
> at org.jboss.as.server.moduleservice.ExtensionIndexService.start(ExtensionIndexService.java:94)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
> ... 6 more
> 11:56:22,260 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "2b7495c2-60cb-4e65-8c99-4decc85ace30.ear")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"],
> "Services that may be the cause:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"]
> }}
> 11:56:22,261 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "2b7495c2-60cb-4e65-8c99-4decc85ace30.ear" was rolled back with the following failure message:
> {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"],
> "Services that may be the cause:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"]
> }}
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (SWSQE-200) B12 OpenShift Cluster is flaky
by Kevin Earls (JIRA)
[ https://issues.jboss.org/browse/SWSQE-200?page=com.atlassian.jira.plugin.... ]
Kevin Earls reassigned SWSQE-200:
---------------------------------
Assignee: Guilherme Baufaker Rêgo (was: Michael Foley)
> B12 OpenShift Cluster is flaky
> ------------------------------
>
> Key: SWSQE-200
> URL: https://issues.jboss.org/browse/SWSQE-200
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Kevin Earls
> Assignee: Guilherme Baufaker Rêgo
>
> I'm opening this mostly as a placeholder, and will update it as I get more information on the problems I've been experiencing. Since I've been using B12 I've been experiencing more frequent failures than on other clusters, including minishift on my laptop and the CNCF CI Jenkins. Here are a couple of instances:
> 1. Deploying ElasticSearch along with the Jaeger Production templates requires allocating 2G or memory, even though the default 512M works fine elsewhere. This can be seen in the Jaeger Standalone Performance tests job here: https://jenkins-jaeger-test.openshift3.jonqe.lab.eng.bos.redhat.com/job/J... . If you run the job without changing the ES_MEMORY parameter to 2Gi it will fail.
> 2. I have a set of smoke tests for Red Hat productized artifacts for the Jaeger Java client which are run using the Jaeger all-in-one template. It's fairly simple, but on B12 deployment of the Jaeger all-in-one images fails on every other build. I've made a copy of the job here: https://jenkins-jaeger-test.openshift3.jonqe.lab.eng.bos.redhat.com/job/F... and its history should be clear.
> So far I have not been able to get any useful information about why this is failing. In the OpenShift console it looks like Jaeger has started correctly. There are no errors in the logs, nor any to be found under monitoring. But if you click on the Jaeger link, you get the message "Application is not available . The application is currently not serving requests at this endpoint. It may not have been started or is still starting."
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10349) WeldBundledLibraryDeployment Test cases fail on IBM jdk
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/WFLY-10349?page=com.atlassian.jira.plugin... ]
Matej Novotny commented on WFLY-10349:
--------------------------------------
[~pkremens] do you happen to know when this broke (or what was the last time it was working)? I am not aware of any Weld-related change in this.
Maybe a new version of IBM JDK broke this?
> WeldBundledLibraryDeployment Test cases fail on IBM jdk
> -------------------------------------------------------
>
> Key: WFLY-10349
> URL: https://issues.jboss.org/browse/WFLY-10349
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, Test Suite
> Environment: {noformat}
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: /usr/lib/maven
> Java version: 1.8.0_161, vendor: IBM Corporation
> Java home: /usr/lib/java/ibm-java-8.0-5.11/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.15.17-300.fc27.x86_64", arch: "amd64", family: "unix"
> $ git rev-parse --short HEAD
> 11e21f08d3
> {noformat}
> Reporter: Petr Kremensky
> Assignee: Martin Kouba
>
> WeldBundledLibraryDeploymentEarTestCase and WeldBundledLibraryDeploymentTestCase fails on IBM jdk.
> *reproduce*
> {noformat}
> git clone https://github.com/wildfly/wildfly.git ; cd wildfly
> mvn clean install -B -DskipTests
> cd testsuite/integration/basic
> mvn test -Dtest=WeldBundledLibraryDeploymentEarTestCase,WeldBundledLibraryDeploymentTestCase -DtestLogToFile=false
> ...
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR] WeldBundledLibraryDeploymentEarTestCase.org.jboss.as.test.integration.weld.multideployment.WeldBundledLibraryDeploymentEarTestCase » Deployment
> [ERROR] WeldBundledLibraryDeploymentTestCase.org.jboss.as.test.integration.weld.multideployment.WeldBundledLibraryDeploymentTestCase » Deployment
> [INFO]
> [ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0
> {noformat}
>
> *server log errors*
> {noformat}
> 11:56:22,104 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.extension-index: org.jboss.msc.service.StartException in service jboss.deployment.extension-index: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1728)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:811)
> Caused by: java.lang.NullPointerException
> at org.jboss.as.server.moduleservice.ExtensionIndexService.start(ExtensionIndexService.java:94)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
> ... 6 more
> 11:56:22,260 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "2b7495c2-60cb-4e65-8c99-4decc85ace30.ear")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"],
> "Services that may be the cause:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"]
> }}
> 11:56:22,261 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "2b7495c2-60cb-4e65-8c99-4decc85ace30.ear" was rolled back with the following failure message:
> {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> "Services that were unable to start:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"],
> "Services that may be the cause:" => ["jboss.deployment.unit.\"2b7495c2-60cb-4e65-8c99-4decc85ace30.ear\".REGISTER"]
> }}
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2477) [GDT] Wizard hints not aligned with project ui
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2477?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2477:
--------------------------------
Attachment: Screenshot from 2018-05-09 13-24-52.png
Screenshot from 2018-05-09 13-24-45.png
> [GDT] Wizard hints not aligned with project ui
> ----------------------------------------------
>
> Key: DROOLS-2477
> URL: https://issues.jboss.org/browse/DROOLS-2477
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Affects Versions: 7.7.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Fix For: 7.8.0.Final
>
> Attachments: Screenshot from 2018-05-09 13-24-45.png, Screenshot from 2018-05-09 13-24-52.png
>
>
> The hint for Work Item Definition creation in GDT column wizard is obsolete. Project UI does not more contain items as Authoring and Project Authoring.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2477) [GDT] Wizard hints not aligned with project ui
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2477?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-2477:
-------------------------------------
Attached screenshots with latest UI state.
> [GDT] Wizard hints not aligned with project ui
> ----------------------------------------------
>
> Key: DROOLS-2477
> URL: https://issues.jboss.org/browse/DROOLS-2477
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Affects Versions: 7.7.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Fix For: 7.8.0.Final
>
> Attachments: Screenshot from 2018-05-09 13-24-45.png, Screenshot from 2018-05-09 13-24-52.png
>
>
> The hint for Work Item Definition creation in GDT column wizard is obsolete. Project UI does not more contain items as Authoring and Project Authoring.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2477) [GDT] Wizard hints not aligned with project ui
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2477?page=com.atlassian.jira.plugi... ]
Jozef Marko reopened DROOLS-2477:
---------------------------------
Currently hint contains:
Design → Projects → [select project] → *Create New Asset* → Work Item *Definition*
But should be:
Design → Projects → [select project] → *Add Asset* → Work Item *definition*
> [GDT] Wizard hints not aligned with project ui
> ----------------------------------------------
>
> Key: DROOLS-2477
> URL: https://issues.jboss.org/browse/DROOLS-2477
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Affects Versions: 7.7.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Fix For: 7.8.0.Final
>
>
> The hint for Work Item Definition creation in GDT column wizard is obsolete. Project UI does not more contain items as Authoring and Project Authoring.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3735) Axis jar not working in WildFly 11
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3735?page=com.atlassian.jira.plugi... ]
Darran Lofthouse commented on WFCORE-3735:
------------------------------------------
What I mean is there is insufficient information here to even suggest the presence of a bug or what that bug might be. The first step is going to be to discuss on the forums the problem that you are experiencing which may lead to a solution or may lead to the information required to create a bug report.
As the underlying error is a NoClassDefFoundError the first step is to review the structure of your deployment and related class loading configuration, it is possible on migrating from one major version to the next a change may be needed within the deployment.
> Axis jar not working in WildFly 11
> ----------------------------------
>
> Key: WFCORE-3735
> URL: https://issues.jboss.org/browse/WFCORE-3735
> Project: WildFly Core
> Issue Type: Bug
> Reporter: J Prasanna Venkatesan
>
> Hi,
> We have application which uses another application's webservice. It was working till WildFly 10.
> But in WildFly 11, it is not working. It is throwing
> 2018-04-10 15:02:47,494 ERROR [io.undertow.request] (default task-7) UT005023: Exception handling request to /authenticationManager/: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
> at deployment.authenticationManager.war//com.collabnet.ce.soap60.webservices.ClientSoapStubFactory.createSoapStub(ClientSoapStubFactory.java:107)
> at deployment.authenticationManager.war//com.collabnet.ce.soap60.webservices.ClientSoapStubFactory.getSoapStub(ClientSoapStubFactory.java:60)
> at deployment.authenticationManager.war//etc.TeamForgeImpl.setHostUrl(TeamForgeImpl.java:73)
> at deployment.authenticationManager.war//filters.CtfAuthFilterImpl.filter(CtfAuthFilterImpl.java:54)
> at deployment.authenticationManager.war//ninja.FilterChainImpl.next(FilterChainImpl.java:35)
> at deployment.authenticationManager.war//ninja.NinjaImpl.invoke(NinjaImpl.java:97)
> at deployment.authenticationManager.war//ninja.servlet.NinjaServletDispatcher.service(NinjaServletDispatcher.java:83)
> at deployment.authenticationManager.war//com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:263)
> at deployment.authenticationManager.war//com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:178)
> at deployment.authenticationManager.war//com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
> at deployment.authenticationManager.war//com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:62)
> at deployment.authenticationManager.war//filters.DemoServletFilter.doFilter(DemoServletFilter.java:43)
> at deployment.authenticationManager.war//com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)
> at deployment.authenticationManager.war//com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
> at deployment.authenticationManager.war//com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:118)
> at deployment.authenticationManager.war//com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:113)
> at io.undertow.servlet//io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61)
> at io.undertow.servlet//io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131)
> at io.undertow.servlet//io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:84)
> at io.undertow.servlet//io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
> at io.undertow.servlet//io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
> at org.wildfly.extension.undertow//org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
> at io.undertow.core//io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet//io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)
> at io.undertow.servlet//io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
> at io.undertow.core//io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.core//io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
> at io.undertow.servlet//io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
> at io.undertow.core//io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
> at io.undertow.servlet//io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
> at io.undertow.core//io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
> at io.undertow.core//io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
> at io.undertow.core//io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at org.wildfly.extension.undertow//org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
> at io.undertow.core//io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.core//io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet//io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292)
> at io.undertow.servlet//io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81)
> at io.undertow.servlet//io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138)
> at io.undertow.servlet//io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135)
> at io.undertow.servlet//io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
> at io.undertow.servlet//io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at org.wildfly.extension.undertow//org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
> at org.wildfly.extension.undertow//org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow//org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow//org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow//org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at io.undertow.servlet//io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
> at io.undertow.servlet//io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
> at io.undertow.servlet//io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
> at io.undertow.core//io.undertow.server.Connectors.executeRootHandler(Connectors.java:326)
> at io.undertow.core//io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:812)
> at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [java.base:]
> at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [java.base:]
> at java.base/java.lang.Thread.run(Unknown Source) [java.base:]
> Caused by: java.lang.reflect.InvocationTargetException
> at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [java.base:]
> at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) [java.base:]
> at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) [java.base:]
> at java.base/java.lang.reflect.Constructor.newInstance(Unknown Source) [java.base:]
> at deployment.authenticationManager.war//com.collabnet.ce.soap60.webservices.ClientSoapStubFactory.createSoapStub(ClientSoapStubFactory.java:97)
> ... 54 more
> Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.apache.axis.client.AxisClient
> at deployment.authenticationManager.war//org.apache.axis.client.Service.getAxisClient(Service.java:104)
> at deployment.authenticationManager.war//org.apache.axis.client.Service.<init>(Service.java:113)
> at deployment.authenticationManager.war//com.collabnet.ce.soap60.webservices.ClientSoapStub.<init>(ClientSoapStub.java:50)
> at deployment.authenticationManager.war//com.collabnet.ce.soap60.webservices.cemain.CollabNetSoapStub.<init>(CollabNetSoapStub.java:21)
> ... 59 more
> Please throw some light here.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months