Tech Tip : CA Single Sign-On : How to remove the "javax.xml.bind.JAXBException: Unable to locate jaxb.properties for package com.sun.research.ws.wadl" warning from the logs when deploying FWS in WebLogic

Document created by Albert_Fernandez Employee on Mar 29, 2018
Version 1Show Document
  • View in full screen mode

Question:

We are seeing the following error messages when we are deploying FWS on WebLogic Managed servers, but the deployment is successful and we are able to access to the affwebservices/assertionretriever resource:

 

<Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING><Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>com.sun.jersey.server.impl.application.WebApplicationImpl _initiateINFO: Initiating Jersey application, version 'Jersey: 1.17 01/17/2013 03:31 PM'com.sun.jersey.server.impl.application.DeferredResourceConfig$ApplicationHolder <init>INFO: Instantiated the Application class org.odata4j.jersey.producer.resources.ODataApplicationcom.sun.jersey.server.impl.wadl.WadlApplicationContextImpl <init>WARNING: Unable to locate jaxb.properties for package com.sun.research.ws.wadljavax.xml.bind.JAXBException: Unable to locate jaxb.properties for package com.sun.research.ws.wadl        at javax.xml.bind.ContextFinder.searchcontextPath(ContextFinder.java:205)        at javax.xml.bind.ContextFinder.find(ContextFinder.java:149)        at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:281)        at com.sun.jersey.server.impl.wadl.WadlApplicationContextImpl.<init>(WadlApplicationContextImpl.java:95)        at com.sun.jersey.server.impl.wadl.WadlFactory.init(WadlFactory.java:96)        at com.sun.jersey.server.impl.application.RootResourceUriRules.initWadl(RootResourceUriRules.java:169)        at com.sun.jersey.server.impl.application.RootResourceUriRules.<init>(RootResourceUriRules.java:106)        at com.sun.jersey.server.impl.application.WebApplicationImpl._initiate(WebApplicationImpl.java:1331)        at com.sun.jersey.server.impl.application.WebApplicationImpl.access$700(WebApplicationImpl.java:168)        at com.sun.jersey.server.impl.application.WebApplicationImpl$13.f(WebApplicationImpl.java:774)        at com.sun.jersey.server.impl.application.WebApplicationImpl$13.f(WebApplicationImpl.java:770)        at com.sun.jersey.spi.inject.Errors.processWithErrors(Errors.java:193)        at com.sun.jersey.server.impl.application.WebApplicationImpl.initiate(WebApplicationImpl.java:770)        at com.sun.jersey.server.impl.application.WebApplicationImpl.initiate(WebApplicationImpl.java:765)        at com.sun.jersey.spi.container.servlet.ServletContainer.initiate(ServletContainer.java:489)        at com.sun.jersey.spi.container.servlet.ServletContainer$InternalWebComponent.initiate(ServletContainer.java:319)        at com.sun.jersey.spi.container.servlet.WebComponent.load(WebComponent.java:605)        at com.sun.jersey.spi.container.servlet.WebComponent.init(WebComponent.java:210)        at com.sun.jersey.spi.container.servlet.ServletContainer.init(ServletContainer.java:374)        at com.sun.jersey.spi.container.servlet.ServletContainer.init(ServletContainer.java:557)        at javax.servlet.GenericServlet.init(GenericServlet.java:241)        at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)        at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)        at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)        at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)        at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)        at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1981)        at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1955)        at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1874)        at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3154)        at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1518)        at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:484)        at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)        at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)        at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)        at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)        at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)        at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)        at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)        at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:671)        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)        at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)        at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:44)        at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)        at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)        at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)        at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)        at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)        at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)        at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)        at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)        at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)        at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)        at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)        at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

We would like to get rid of these errors in the log to make it error free, even if FWS is working properly. How we can do it? Is this something we must worry about?

 

Environment:

Web Agent Option Pack R12.52 SP1 CR02Oracle WebLogic 10.3.6

Answer:

This error message can be ignored as per the following note in documentation:
https://docops.ca.com/ca-single-sign-on/12-52-sp1/en/release-notes/known-issues-in-release-12-52-sp1/known-issues-in-federation-12-52-sp1#KnownIssuesinFederation12.52SP1-ErrorsWhileDeployingaffwebservicesonWebLogic
This is a 3rd party warning message that does not affect functionality.

 

However, to remove this messages from the logs, you can create a jar file with a jaxb.properties file inside (creating it using the same com/sun/research/ws/wadl path seen in the warning message) and put it in the folder where the current CLASSPATH is set.

Add the following as content for the jaxb.properties file:

javax.xml.bind.context.factory=com.sun.xml.bind.ContextFactory

 

KD : KB000014908 

Attachments

    Outcomes