When we deploy web applications on the weblogic server, there are some common errors seen on the admin console while activating changes. These errors are usually not resolved even after restart of the server. Few of the issues are as below:
1) <Error> <Console> <BEA-240003> <Console encountered the following error weblogic.management.DeploymentException: [Deployer:149189]Attempt to operate ‘distribute’ on null BasicDeploymentMBean for deployment portalTramitsServeisEAR. Operation can not be performed until server is restarted.
– This may be resolved by running statd() and lockd() processes on every NFS client that accesses a remote NFS volume.
– If different servers (sharing the same domain root) are started with different user Ids of same group, set the correct “umask” for the server process so that the file created by one server can be opened for read/write by the other server without security exceptions. Eg: “umask 002”.
Workaround for this issue:
1. Click on Lock and Edit.
2. Go to deployments.
3. Click to install the web-app.
4. After installing (any staging mode), click on Activate changes. At this time, you will see the error as mentioned above.
5. Now click on Activate Changes again.
6. Click on Lock and Edit.
7. Click on Undo All Changes.
8. Click on Lock and Edit and install the app again.
9. This time it succeeds.
2) javax.xml.transform.TransformerFactoryConfigurationError: Provider org.apache.xalan.processor.TransformerFactoryImpl not found
at javax.xml.transform.TransformerFactory.newInstance(TransformerFactory.java:108)
at weblogic.management.provider.internal.ConfigReader.convert(ConfigReader.java:100)
at weblogic.management.provider.internal.ConfigReader.<init>(ConfigReader.java:71)
at weblogic.management.provider.internal.ConfigReader.<init>(ConfigReader.java:65)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.handleConfigTreeLoad(RuntimeAccessDeploymentReceiverService.java:961)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.updateDeploymentContext(RuntimeAccessDeploymentReceiverService.java:581)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doUpdateDeploymentContextCallback(DeploymentReceiverCallbackDeliverer.java:133)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.updateDeploymentContext(DeploymentReceiverCallbackDeliverer.java:27)
– When the application is already deployed on the server, any change made through the console throws this error. Suppose the application is deployed on the managed servers, when the servers are running and the application is active, the changes cannot be activated. The workaround for this is to shutdown the managed servers and make any changes. But this is not acceptable in the production environment.
Solution :
1- Undeploy the application. Shutdown the servers.
2- Add xercesImpl.jar, xalan.jar, serializer.jar, xml-apis.jar and xsltc.jar libraries in classpath.
3- In the application, place the file xalan.jar, xercesImpl.jar and xml-apis.jar in the war file i.e web-inf/lib directory, then set prefer-web-inf-classes to true in weblogic.xml as:
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
4- Set the following start-up flags in the JAVA_OPTIONS:
-Djavax.xml.parsers.SAXParserFactory=weblogic.xml.jaxp.RegistrySAXParserFactory
-Djavax.xml.parsers.DocumentBuilderFactory=weblogic.xml.jaxp.RegistryDocumentBuilderFactory
-Djavax.xml.transform.TransformerFactory=weblogic.xml.jaxp.RegistrySAXTransformerFactory
– Restart the servers, deploy the application again, and check if the issue still persists.
<BEA-290071> <Deployment service servlet failed on parsing the request or uploading the file>
Use the following java option
-Dweblogic.deploy.UploadLargeFile=true
Unable to access the selected application.
Exception in AppMerge flows’ progression
Exception in AppMerge flows’ progression
VALIDATION PROBLEMS WERE FOUND problem: cvc-complex-type.2.4a:
You need to update your web.xml namespace declaration.
http://docs.oracle.com/cd/E21764_01/web.1111/e13712/web_xml.htm#i1039990
You get the following exception when jsp size is huge.
too large for try statement
Use the following JVM Option
-Dweblogic.jsp.noOptimization
Getting following error at the time of deployment.
Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Logger
Apply Patch 16038283 and excluding classes which are not used as beans by editing the beans.xml file.
If the issue is still not resolve please get in touch with Oracle Support.
Add the following JVM option on the server on which you are doing the deployment and restart.
-Xverify:none
Stack overflow error while invoking jspx page WLS 10.3.6
java.lang.StackOverflowError exception occurs .
The related Java Stack is :
java.lang.StackOverflowError
at weblogic.servlet.internal.ServletResponseImpl.addHeader(ServletResponseImpl.java:556)
at javax.servlet.http.HttpServletResponseWrapper.addHeader(HttpServletResponseWrapper.java:168)
You need to modify the web.xml as below.
javax.faces.FACELETS_VIEW_MAPPINGS*.jspx
Exception in thread “AWT-EventQueue-0” sun.awt.X11.XException: Cannot write XdndAware property
at sun.awt.X11.XDnDDropTargetProtocol.registerDropTarget(XDnDDropTargetProtocol.java:79)
This is due to a JDK bug, add the following jvm option in config.sh
-DsuppressSwingDropSupport=true
java.lang.NullPointerException at com.bea.console.actions.jms.message.JMSMessageDetailAction.execute(JMSMessageD etailAction.java:143)
This issue has been addressed in defect 9889164.
weblogic.servlet.jsp.CompilationException: Failed to compile JSP /index.jsp
The type new Comparator(){} must implement the inherited abstract method Comparator.thenComparing(Function, Comparator)
Issue is present on WLS 12.1.3 and JDK 8.
You will need to download the patch for bug Bug 18729264.
org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 219 in XML document from file [] is invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 219; columnNumber: 9; cvc-complex-type.2.3: Element ‘beans’ cannot have character [children], because the type’s content type is element-only.
First thanks you share this knowlege for us.
Until now i have not found the issue during Deploying on our WebLogic system. i think it is diffiult to happen this ,if it happend ,it is also difficult to solve. i do not know how to recur the issue in my own WebLogic, when i meet the errors ,i hope this article will help me or help us . i will offen view this website, its really a good web .support u.
Hi Folin,
Thanks for the comments. Its great that you are not facing any deployment issues till now.. If there are any, let us know about it. And thanks for the support 🙂
hi,
very recently when we are deploying the war file it was not going into active state. it would come into start running state and after an hour or so it would go into prepared state.
the error would come as :
#### <>
#### <>
#### <> <Stack trace for message 149004
java.lang.IllegalStateException: WLDF Module not in PREPARED state during activate() callback. State was 3
at weblogic.diagnostics.module.WLDFModule.activate(WLDFModule.java:281)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:411)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:74)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:66)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
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:140)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:143)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:820)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1227)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:436)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
java.lang.IllegalStateException: WLDF Module not in PREPARED state during activate() callback. State was 3
at weblogic.diagnostics.module.WLDFModule.activate(WLDFModule.java:281)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:411)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:74)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:66)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
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:140)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:143)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:820)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1227)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:436)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
#### <> <Stack trace for message 149004
java.lang.Exception: [DeploymentService:290036]Deployment for request id '1290720649868' is deferred since target 'DOCMS1' is disconnected.
please share your findings with this issue.
regards
chandra.
Hi Chandra,
The stack trace says that the managed server is on which you are trying to deploy your application is disconnected. Can you tell me the state of your managed server in the console? How are you deploying your application.. (console or command-line)?
Check if you can restart the managed server and try the deployment again. Otherwise check the connectivity of the managed server with the admin server while start up in both the servers logs. If it gives an issue of JMX connectivity, the health would not be ok.
Regards,
Divya
Hi Divya,
1)I am able to see the message as context path is already in use while deploying the appplication frequently .I cleared the cache and deleted the application from console and deployed it freshely.Eventhough i am getting the same and after restarting the servers only i am able to able to deploy the application successfully.
2)secondthing while deploying the application, suddenly all of the applications which are present previosuly are not appearing in console.After server restart only i am able to see those applications.why this happening ?is server restart only the solution for the problem.sorry i donot have log trace for this.
Thanks In advance,
Rajewari.K
Hi Rajewari,
1– How are you deploying your applications? Is it through the admin console or command-line/wlst? If possible, collect the log file/stack trace next time you see the error. Application versioning might also cause the issue.
2– I am not sure why the deployed applications do not appear on the console. Is it that you are using some scripts to deploy/undeploy the apps?
Regards,
Divya
Hi,
Can you tell me the recommended way for stage mode deployment in production. We tried to deploy an appln in production which is targetted to 2 clusters (3 managed servers each) it appears some managed servers stage directory gets updated some not.
Regards,
Saranya
Hi Saranya,
There is a bug with the similar issue. Can you tell me which weblogic version are you using? Also, try and clear the tmp and cache directory and check if the issue still persists.
Regards,
Divya
Hi,
Hoping you can shed some light. I’ve an ear file that I can deploy on a 10.3.3 WL Server on my machine. It works fine, without problem. I have to deploy that same ear file to a remote 10.3.3 WL managed server and am running into the first issue you describe. I’ve changed the managed server deployment configuration to “no stage” hoping that would help. (no luck) The only difference between the problem WL environment and my local one is that the remote one is running in production mode and is a managed server. My local WL env is in development mode and is not a managed server.
I’ve tried the workaround steps as you describe with no luck, although the exact sequence seems to be a little off. (ie. The ear file is listed in the deployments so I’ve just been trying to “start” it. Also after #5, #6 isn’t an option. The only thing I can do is “release configuration”)
any ideas would be great,
thank you
Lynn
Hi Lynn,
Are you using NFS mounts by any chance? Can you try to turn on NFS locking and check if the server behavior improves?
Regards,
Divya
Unfortunately the filesystem used by the AdminServer and my managed server are on the local disk, not on NFS mounts. The entire environment I’m using (there are other applications deployed and other managed servers) is running on a slice of the bigger physical machine, but I don’t know if this would create any problems. Is there anything else you can think of that I should investigate?
Can you explain what you mean by this?
If different servers (sharing the same domain root) are started with different user Ids of same group, set the correct “umask” for the server process so that the file created by one server can be opened for read/write by the other server without security exceptions. Eg: “umask 002″.
Is that a workaround/solution that I need to try?
Hi Divya,
Thanks for the nice article. As always, you guys do a wonderful job of updating this website.
Could you please elaborate on the 2nd issue. What changes are you taking about when you say “When the application is already deployed on the server, any change made through the console throws this error. Suppose the application is deployed on the managed servers, when the servers are running and the application is active, the changes cannot be activated. The workaround for this is to shutdown the managed servers and make any changes. But this is not acceptable in the production environment.”
Thanks!!!
Hi Shawn,
First of all, wonders team thanks you for your continuous support. 🙂
Regarding your query about activating changes, take a few examples like changing the port number of the servers, creating a resource (datasources, JMS queues, topics etc), once you have done these on the console, you need to click on activate changes for these changes to take effect. Once you click, the error is thrown. I hope this answers your question.
Best Regards,
Divya
Hi Divaya,
Which env is easy to deploy the app windows/unix. Which env easily trace the issue. could you please resopond me my comments.
Regrads,
Srini
Hi Srini,
There is no such thing that deploying applications in windows is easier than unix is easier, or vice versa..
It just depends on which environment are you comfortable working in. I have worked in both windows and unix, both are similar for me.
If you have a particular scenario in mind or any experience to share, you are most welcome 🙂
Regards,
Divya
what are the frequent issues we wil get while deploying app in windows env.
Hi Lyn,
In your production machine could you try deploying the ear from Admin console and incase target to managed server (remote) ….
If still the error persists could you share your log file to us??
Hi ,
I get this below error when I try to deploy paym-bpm-utility-ear-1.0.ear . I have deployed paym-bpm-utility-ear-1.0.1.ear already .
This Exception occurred at Tue Jan 25 15:41:27 GMT 2011.
weblogic.application.ModuleException: Context path ‘/orange-shared-lib-paym-bpm-utility-1.0’ is already in use by the module: /orange-shared-lib-paym-bpm-utility-1.0 application: paym-bpm-utility-ear-1.0.1.
We have one library file deployed , which applications( ear’s ) deployed will reference this library . Is there any way that i can deploy both ear file paym-bpm-utility-ear-1.0.ear and paym-bpm-utility-ear-1.0.1.ear with referencing the lib file .
Thanks
Murali .T
Kindly post your question to our forum
https://weblogic-wonders.com/weblogic/forum/#/
Hi divya,
my name is lokesh iam fresher in weblogic looking for a job.will u plz send me the materials of weblogic to my mail i,e.,loke.gopalavari@gmail.com
Thanking you in advance.
Hi Lokesh,
The administrator will forward you the documents of basics of weblogic server on your email id to begin with.
Best Regards,
Divya
I am facing a problem during ear deployment. There are multiple ears in the application and some of the ears are getting deployed on first request. Where could the problem possibly lie?
Hi Kedar,
Are you sure these are EARs that are getting deployed on the first request? They can be jsp pages getting deployed.
Please verify and let me know. How are you monitoring this? If there is any stack trace, please share.
Best Regards,
Divya
hi,
Very recently when we are going to stop weblogic server we are getting below error.
<An exception [javax.xml.transform.TransformerFactoryConfigurationError: Provider org.apache.xalan.processor.TransformerFactoryImpl not found] was thrown while rendering the content at [null].
com.bea.portlet.adapter.scopedcontent.ActionLookupFailedException: javax.xml.transform.TransformerFactoryConfigurationError: Provider org.apache.xalan.processor.TransformerFactoryImpl not found
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:697)
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.renderInternal(ScopedContentCommonSupport.java:266)
at com.bea.portlet.adapter.scopedcontent.StrutsStubImpl.render(StrutsStubImpl.java:107)
at com.bea.netuix.servlets.controls.content.NetuiContent.preRender(NetuiContent.java:292)
at com.bea.netuix.nf.ControlLifecycle$6.visit(ControlLifecycle.java:428)
Truncated. see log file for complete stacktrace
javax.xml.transform.TransformerFactoryConfigurationError: Provider org.apache.xalan.processor.TransformerFactoryImpl not found
at javax.xml.transform.TransformerFactory.newInstance(TransformerFactory.java:108)
at weblogic.management.provider.internal.ConfigReader.convert(ConfigReader.java:100)
at weblogic.management.provider.internal.ConfigReader.(ConfigReader.java:71)
at weblogic.management.provider.internal.ConfigReader.(ConfigReader.java:65)
at weblogic.management.provider.internal.EditAccessImpl.loadBeanTree(EditAccessImpl.java:1862)
Truncated. see log file for complete stacktrace
>
<There was an error while running a lifecycle stage :: Lifecycle: UIControl.render :: for the control :: null ::.
com.bea.netuix.nf.UIControlException: com.bea.portlet.adapter.scopedcontent.ActionLookupFailedException: javax.xml.transform.TransformerFactoryConfigurationError: Provider org.apache.xalan.processor.TransformerFactoryImpl not found
<There was an error while running a lifecycle stage :: Lifecycle: UIControl.render :: for the control :: null ::.
com.bea.netuix.nf.UIControlException: com.bea.portlet.adapter.scopedcontent.ActionLookupFailedException: javax.xml.transform.TransformerFactoryConfigurationError: Provider org.apache.xalan.processor.TransformerFactoryImpl not found
at com.bea.netuix.servlets.controls.content.NetuiContent.checkPreRenderExceptions(NetuiContent.java:404)
at com.bea.netuix.servlets.controls.content.NetuiContent.beginRender(NetuiContent.java:343)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:485)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
Truncated. see log file for complete stacktrace
com.bea.portlet.adapter.scopedcontent.ActionLookupFailedException: javax.xml.transform.TransformerFactoryConfigurationError: Provider org.apache.xalan.processor.TransformerFactoryImpl not found
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:697)
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:697)
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.renderInternal(ScopedContentCommonSupport.java:266)
at com.bea.portlet.adapter.scopedcontent.StrutsStubImpl.render(StrutsStubImpl.java:107)
at com.bea.netuix.servlets.controls.content.NetuiContent.preRender(NetuiContent.java:292)
at com.bea.netuix.nf.ControlLifecycle$6.visit(ControlLifecycle.java:428)
Truncated. see log file for complete stacktrace
javax.xml.transform.TransformerFactoryConfigurationError: Provider org.apache.xalan.processor.TransformerFactoryImpl not found
at javax.xml.transform.TransformerFactory.newInstance(TransformerFactory.java:108)
at weblogic.management.provider.internal.ConfigReader.convert(ConfigReader.java:100)
at weblogic.management.provider.internal.ConfigReader.(ConfigReader.java:71)
at weblogic.management.provider.internal.ConfigReader.(ConfigReader.java:65)
at weblogic.management.provider.internal.EditAccessImpl.loadBeanTree(EditAccessImpl.java:1862)
Truncated. see log file for complete stacktrace
Please share finding with this error.
Hi Vivek,
Could you help us with JDK and WLS version you are using:
Also, could you check if you are using:
xmlParserAPIs.jar
If yes disable to delete in the application packaging.
Hi,
I am facing this issue when i am trying to deploy an ear file to the weblogic server. Please help me asap.
[HTTP:101216]Servlet: “WebServiceServlet” failed to preload on startup in Web application: “IPVPNInventoryService”. weblogic.webservice.dd.verify.VerifyException: ERROR: The java component class: com.aricent.granite.webservices.IPVPNInventoryServiceImpl from the component named: IPVPNInventoryService could not be loaded. at weblogic.webservice.dd.verify.JavaComponentChecker.verify(JavaComponentChecker.java:45) at weblogic.webservice.dd.verify.DDVerifierImpl.verifyComponents(DDVerifierImpl.java:70) at weblogic.webservice.dd.verify.DDVerifierImpl.verifyWebService(DDVerifierImpl.java:105) at weblogic.webservice.dd.verify.DDVerifierImpl.verify(DDVerifierImpl.java:124) at weblogic.webservice.server.WebServiceContext.(WebServiceContext.java:72) at weblogic.webservice.server.servlet.ServletSecurityHelper$1.run(ServletSecurityHelper.java:130) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147) at weblogic.webservice.server.servlet.ServletSecurityHelper.createWebServiceContext(ServletSecurityHelper.java:124) at weblogic.webservice.server.servlet.WebServiceServlet.initLocal(WebServiceServlet.java:119) at weblogic.webservice.server.servlet.WebServiceServlet.init(WebServiceServlet.java:97) at javax.servlet.GenericServlet.init(GenericServlet.java:256) at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:274) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64) at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58) at weblogic.servlet.internal.StubLifecycleHelper.(StubLifecycleHelper.java:48) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:504) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1716) at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1693) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1613) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2764) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:889) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:333) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104) at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:131) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:815) at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1222) at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:433) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67) at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Hi Wondeers Team
when i did a new deployment the application through some errors plz suggest
#### <> <[ServletContext@16542562[app:residuals module:residuals path:/residuals spec-version:null]] Root cause of ServletException.
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.fox.residuals.web.action.LongOperation$ExecuteThread.run(LongOperation.java:115)
Caused By: java.lang.NoSuchMethodError: org.apache.commons.beanutils.PropertyUtils.isWriteable(Ljava/lang/Object;Ljava/lang/String;)Z
at com.fox.residuals.util.ResidualsBeanUtils.copyProperties(ResidualsBeanUtils.java:39)
at com.fox.residuals.service.cast.impl.CastCalculationManagerImpl.updatePayInfoWithCalculatedPayInfo(CastCalculationManagerImpl.java:533)
at com.fox.residuals.service.cast.impl.CastCalculationManagerImpl.calculatePayInfo(CastCalculationManagerImpl.java:502)
at com.fox.residuals.service.cast.impl.CastCalculationManagerImpl.performCalculationsFor(CastCalculationManagerImpl.java:404)
at com.fox.residuals.web.action.castovrpmtinfo.EmployeePayInfoAction.edit(EmployeePayInfoAction.java:43)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.fox.residuals.web.action.LongOperation$ExecuteThread.run(LongOperation.java:115)
==========================================================
#### <> <[ServletContext@16542562[app:residuals module:residuals path:/residuals spec-version:null]] Servlet failed with Exception
java.lang.RuntimeException: java.net.SocketException: Broken pipe
at com.opensymphony.sitemesh.webapp.decorator.BaseWebAppDecorator.render(BaseWebAppDecorator.java:37)
at com.opensymphony.sitemesh.webapp.SiteMeshFilter.doFilter(SiteMeshFilter.java:84)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.fox.residuals.web.filter.ObserveFilter.doFilter(ObserveFilter.java:31)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.fox.residuals.web.filter.LoginFilter.doFilter(LoginFilter.java:145)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Thanks
Suresh,
Did you find a solution for this? please let me know..
these are very useful article
thanks reddy!
hi, please let me know , how to recover my domain, if my config.xml file is corrupted and no backup is taken and there is no remote machine also, one of the interviewer asked me this question. plz help me out
You need to figure out what part is corrupted?
If the password’s are deleted then its difficult to recover.
Otherwise it should not be that difficult.
Hi Everyone,
I have ANT script which calls wlst script to deploy the application.
Even though the wlst script is being called, it fails to deploy.
I did restart the complete domain , but still get the same error.
Is there any place I can upload my script as definitely my script has
some problem.
run-wlst-script:
[wlst] Executing the command line :
[wlst] /u01/app/oracle/product/fmw3/jrmc/jre/bin/java -Ddebug=true –
DfailOnError=true -DexecuteScriptBeforeFile=true –
DfileName=deploy_jee.py -classpath /apps/gct/bhcrr/wlstbuild/ant/lib/
ant-launcher.jar:/apps/gct/bhcrr/wlstbuild/ant/lib/ant-antlr.jar:/apps/
gct/bhcrr/wlstbuild/ant/lib/ant-apache-bcel.jar:/apps/gct/bhcrr/
wlstbuild/ant/lib/ant-apache-bsf.jar:/apps/gct/bhcrr/wlstbuild/ant/lib/
ant-apache-log4j.jar:/apps/gct/bhcrr/wlstbuild/ant/lib/ant-apache-
oro.jar:/apps/gct/bhcrr/wlstbuild/ant/lib/ant-apache-regexp.jar:/apps/
gct/bhcrr/wlstbuild/ant/lib/ant-apache-resolver.jar:/apps/gct/bhcrr/
wlstbuild/ant/lib/ant-apache-xalan2.jar:/apps/gct/bhcrr/wlstbuild/ant/
lib/ant-commons-logging.jar:/apps/gct/bhcrr/wlstbuild/ant/lib/ant-
commons-net.jar:/apps/gct/bhcrr/wlstbuild/ant/lib/ant-jai.jar:/apps/
gct/bhcrr/wlstbuild/ant/lib/ant-javamail.jar:/apps/gct/bhcrr/wlstbuild/
ant/lib/ant-jdepend.jar:/apps/gct/bhcrr/wlstbuild/ant/lib/ant-jmf.jar:/
apps/gct/bhcrr/wlstbuild/ant/lib/ant-jsch.jar:/apps/gct/bhcrr/
wlstbuild/ant/lib/ant-junit.jar:/apps/gct/bhcrr/wlstbuild/ant/lib/
ant.jar:/apps/gct/bhcrr/wlstbuild/ant/lib/ant-junit4.jar:/apps/gct/
bhcrr/wlstbuild/ant/lib/ant-netrexx.jar:/apps/gct/bhcrr/wlstbuild/ant/
lib/ant-swing.jar:/apps/gct/bhcrr/wlstbuild/ant/lib/ant-testutil.jar:/
u01/app/oracle/product/fmw3/jrmc/lib/tools.jar:/u01/app/oracle/product/
fmw3/wlserver_10.3/server/lib/weblogic.jar
weblogic.management.scripting.WLSTInterpreterInvoker
[wlst] sys.argv is [‘deploy_jee.py’]
[wlst] Loading Python files
[wlst] Connecting to t3://DBPM3HOST1VHN1.trcw.us.aexp.com:7026 with
userid deepshri …
[wlst] Successfully connected to Admin Server ‘AdminServer’ that
belongs to domain ‘gct_domain’.
[wlst]
[wlst] Warning: An insecure protocol was used to connect to the
[wlst] server. To ensure on-the-wire security, the SSL port or
[wlst] Admin port should be used instead.
[wlst]
[wlst] Location changed to edit tree. This is a writable tree with
[wlst] DomainMBean as the root. To make changes you will need to start
[wlst] an edit session via startEdit().
[wlst]
[wlst] For more help, use help(edit)
[wlst]
[wlst] Starting an edit session …
[wlst] Started edit session, please be sure to save and activate your
[wlst] changes once you are done.
[wlst] Deploying Application ‘BHC_Application_application1′ …
[wlst] Deploying application from /apps/gct/bhcrr/wlstbuild/src/test/
ADF/BHCApp/deploy/BHC_Application_application1.ear to targets
SOA_Cluster,AdminServer (upload=false) …
[wlst]
[wlst] You have an edit session in progress, hence WLST will not
[wlst] block for your deployment to complete.
[wlst] Started the Deployment of Application. Please refer to the
returned WLSTProgress object or variable LAST to track the status.
[wlst]
[wlst] *** WARNING ***
[wlst] Preparing to activate changes.
[wlst] *** WARNING ***
[wlst]
[wlst] Press the ‘Enter’ key to activate changes:
[wlst] Starting an edit session …
[wlst] Started edit session, please be sure to save and activate your
[wlst] changes once you are done.
[wlst] Saving all your changes …
[wlst] Saved all your changes successfully.
[wlst] Activating all your changes, this may take a while …
[wlst] The edit lock associated with this edit session is released
[wlst] once the activation is completed.
[wlst] weblogic.management.DeploymentException: [Deployer:
149189]Attempt to operate ‘deploy’ on null BasicDeploymentMBean for
deployment BHC_Application_application1. Operation can not be
performed until server is restarted.
[wlst] at
weblogic.deploy.internal.targetserver.DeploymentManager.assertDeploymentMBeanIsNonNull(DeploymentManager.java:
1319)
[wlst] at
weblogic.deploy.internal.targetserver.DeploymentManager.findDeploymentMBean(DeploymentManager.java:
1360)
[wlst] at
weblogic.deploy.internal.targetserver.DeploymentManager.createOperation(DeploymentManager.java:
1050)
[wlst] at
weblogic.deploy.internal.targetserver.DeploymentManager.createOperations(DeploymentManager.java:
1406)
[wlst] at
weblogic.deploy.internal.targetserver.DeploymentManager.handleUpdateDeploymentContext(DeploymentManager.java:
162)
[wlst] at
weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.updateDeploymentContext(DeploymentServiceDispatcher.java:
156)
[wlst] at
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doUpdateDeploymentContextCallback(DeploymentReceiverCallbackDeliverer.java:
147)
[wlst] at
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.updateDeploymentContext(DeploymentReceiverCallbackDeliverer.java:
29)
[wlst] at
weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.callDeploymentReceivers(ReceivedPrepare.java:
203)
[wlst] at
weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.handlePrepare(ReceivedPrepare.java:
114)
[wlst] at
weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.receivedPrepare(ReceivedPrepare.java:
52)
[wlst] at
weblogic.deploy.service.internal.targetserver.TargetRequestImpl.run(TargetRequestImpl.java:
211)
[wlst] at
weblogic.deploy.service.internal.transport.CommonMessageReceiver
$1.run(CommonMessageReceiver.java:458)
[wlst] at weblogic.work.SelfTuningWorkManagerImpl
$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
[wlst] at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
[wlst] at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
[wlst] Unexpected error: main.WLSTException
[wlst] This Exception occurred at Wed Mar 07 06:04:28 MST 2012.
[wlst] Edit session is cancelled successfully
[wlst] Disconnected from weblogic server: AdminServer
[wlst] Exception in thread “Main Thread”
java.lang.IllegalStateException: Traceback (innermost last):
[wlst] File “deploy_jee.py”, line 207, in ?
[wlst] File “deploy_jee.py”, line 92, in endTransaction
[wlst] File “”, line 376, in activate
[wlst] File “”, line 1848, in raiseWLSTException
[wlst] WLSTException: Error occured while performing activate : Error
while Activating changes. : [Deployer:149189]Attempt to operate
‘deploy’ on null BasicDeploymentMBean for deployment
BHC_Application_application1. Operation can not be performed until
server is restarted.
[wlst] Use dumpStack() to view the full stacktrace
[wlst]
[wlst] at
weblogic.management.scripting.WLSTInterpreterInvoker.printError(WLSTInterpreterInvoker.java:
110)
[wlst] at
weblogic.management.scripting.WLSTInterpreterInvoker.executePyScript(WLSTInterpreterInvoker.java:
103)
[wlst] at
weblogic.management.scripting.WLSTInterpreterInvoker.main(WLSTInterpreterInvoker.java:
27)
[wlst] Disconnecting from WebLogic Server
[wlst] Traceback (innermost last):
[wlst] File “deploy_jee.py”, line 207, in ?
[wlst] File “deploy_jee.py”, line 92, in endTransaction
[wlst] File “”, line 376, in activate
[wlst] File “”, line 1848, in raiseWLSTException
[wlst] WLSTException: Error occured while performing activate : Error
while Activating changes. : [Deployer:149189]Attempt to operate
‘deploy’ on null BasicDeploymentMBean for deployment
BHC_Application_application1. Operation can not be performed until
server is restarted.
[wlst] Use dumpStack() to view the full stacktrace
[wlst]
[wlst]
Hi Deepashri,
I am facing the same issue. Did you find any solution for it. If so please let me know
Thank you
sam
Hi
Administrator i am new to web logic server pl provide basic documents of web logic sever
Hi,
I loved this website, very informative!!
Can you please post some issues related to connection pool.
What if we find the connection failed? How do we resolve it?
How do we understand there is connection leakage?
what is broken pipe exception?
Can you please provide me basic documents of web logic Server.
Your help is greatly appreciated.
Thanks!!
thanks Sushmita!!
Hi team,
I need some material son JVM.Please
I want to start my carrier on weblogic admin..this site is Root for me
very informative..:)
Hi I have a problem in my weblogic 10g which is running on cent os .
when I am trying to create a datasource to SQL Server which is running on windows 2008 server, weblogic able to connect to that SQL Server DB ,its saying connection is success ,but when I am clicking on “Activate changes” button it is throwing below error.
<Attempt to operate 'activate' on null BasicDeploymentMBean for deployment mbsfactords. Operation can not be performed until server is
<Console encountere actords. Operation can not be performed until server is restarted.
at weblogic.deploy.internal.targetserver.DeploymentManager.assertDeploym
at weblogic.deploy.internal.targetserver.DeploymentManager.findDeploymen
at weblogic.deploy.internal.targetserver.DeploymentManager.createOperati
at weblogic.deploy.internal.targetserver.DeploymentManager.createOperati
at weblogic.deploy.internal.targetserver.DeploymentManager.handleUpdateD
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.upd
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedP
at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedP
at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedP
at weblogic.deploy.service.internal.targetserver.TargetRequestImpl.run(T
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$1.ru
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
It looks like similar to what error you people posted above ,but as you know this is a datasource problem and when I am clicking on undo all changes , it is clearing the created datasource settings and ,when I am creating the datasource again , same story, connection successful, when I press activate changes button , it throws the above mentioned error.
Pls help me , this is annoying me from past 2 days.
Thanks a lot
Prasad
Sorry the error message was not pasted properly
<Attempt to operate 'activate' on null BasicDeploymentMBean for deployment mbsfactords. Operation can not be performed until server is
<Stack trace for message 149004
weblogic.management.DeploymentException: [Deployer:149189]Attempt to operate 'activate' on null BasicDeploymentMBean for deployment mbsfactords. Operation can not be performed until server is restar
at weblogic.deploy.internal.targetserver.DeploymentManager.assertDeploymentMBeanIsNonNull(DeploymentManager.java:1281)
at weblogic.deploy.internal.targetserver.DeploymentManager.findDeploymentMBean(DeploymentManager.java:1322)
at weblogic.deploy.internal.targetserver.DeploymentManager.createOperation(DeploymentManager.java:1022)
at weblogic.deploy.internal.targetserver.DeploymentManager.createOperations(DeploymentManager.java:1368)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleUpdateDeploymentContext(DeploymentManager.java:160)
Truncated. see log file for complete stacktrace
<Attempt to operate 'activate' on null BasicDeploymentMBean for deployment mbsfactords. Operation can not be performed until server is
<Stack trace for message 149004
weblogic.management.DeploymentException: [Deployer:149189]Attempt to operate 'activate' on null BasicDeploymentMBean for deployment mbsfactords. Operation can not be performed until server is restar
at weblogic.deploy.internal.targetserver.DeploymentManager.assertDeploymentMBeanIsNonNull(DeploymentManager.java:1281)
at weblogic.deploy.internal.targetserver.DeploymentManager.findDeploymentMBean(DeploymentManager.java:1322)
at weblogic.deploy.internal.targetserver.DeploymentManager.createOperation(DeploymentManager.java:1022)
at weblogic.deploy.internal.targetserver.DeploymentManager.createOperations(DeploymentManager.java:1368)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleUpdateDeploymentContext(DeploymentManager.java:160)
Truncated. see log file for complete stacktrace
Sorry the error message is not posted properly.
<Attempt to operate 'activate' on null BasicDeploymentMBean for deployment mbsfactords. Operation can not be performed until server is
<Stack trace for message 149004
weblogic.management.DeploymentException: [Deployer:149189]Attempt to operate 'activate' on null BasicDeploymentMBean for deployment mbsfactords. Operation can not be performed until server is restar
at weblogic.deploy.internal.targetserver.DeploymentManager.assertDeploymentMBeanIsNonNull(DeploymentManager.java:1281)
at weblogic.deploy.internal.targetserver.DeploymentManager.findDeploymentMBean(DeploymentManager.java:1322)
at weblogic.deploy.internal.targetserver.DeploymentManager.createOperation(DeploymentManager.java:1022)
at weblogic.deploy.internal.targetserver.DeploymentManager.createOperations(DeploymentManager.java:1368)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleUpdateDeploymentContext(DeploymentManager.java:160)
Truncated. see log file for complete stacktrace
Hi team,
I am facing below exception while deploying EAR in Weblogic
but same is working in jBoss.
Please provide some solution…
com.sun.jersey.api.container.ContainerException: Exception obtaining parameters
at com.sun.jersey.server.impl.inject.InjectableValuesProvider.getInjectableValues(InjectableValuesProvider.java:54)
at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$EntityParamInInvoker.getParams(AbstractResourceMethodDispatchProvider.java:138)
at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:166)
at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:70)
at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:279)
at com.sun.jersey.server.impl.uri.rules.ResourceObjectRule.accept(ResourceObjectRule.java:84)
at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:136)
at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:74)
at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1357)
at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1289)
at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1239)
at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1229)
at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:420)
at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:497)
at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:684)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:183)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3683)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.IllegalStateException: The @FormParam is utilized when the content type of the request entity is not application/x-www-form-urlencoded
at com.sun.jersey.server.impl.model.parameter.FormParamInjectableProvider$FormParamInjectable.getValue(FormParamInjectableProvider.java:81)
at com.sun.jersey.server.impl.inject.InjectableValuesProvider.getInjectableValues(InjectableValuesProvider.java:46)
… 28 more
Hi team,
I am facing below exception while deploying EAR in Weblogic
but same is working in jBoss.
Please provide some solution…
com.sun.jersey.api.container.ContainerException: Exception obtaining parameters
at com.sun.jersey.server.impl.inject.InjectableValuesProvider.getInjectableValues(InjectableValuesProvider.java:54)
at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$EntityParamInInvoker.getParams(AbstractResourceMethodDispatchProvider.java:138)
at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:166)
at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:70)
at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:279)
at com.sun.jersey.server.impl.uri.rules.ResourceObjectRule.accept(ResourceObjectRule.java:84)
at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:136)
at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:74)
at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1357)
at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1289)
at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1239)
at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1229)
at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:420)
at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:497)
at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:684)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:183)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3683)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.IllegalStateException: The @FormParam is utilized when the content type of the request entity is not application/x-www-form-urlencoded
at com.sun.jersey.server.impl.model.parameter.FormParamInjectableProvider$FormParamInjectable.getValue(FormParamInjectableProvider.java:81)
at com.sun.jersey.server.impl.inject.InjectableValuesProvider.getInjectableValues(InjectableValuesProvider.java:46)
… 28 more
its very useful site , especially for me this is always my refercence. thank for provide ur time for us
thanks 🙂
Failure occurred in the execution of deployment request with ID ‘1371725830851’ for task ‘5’. Error is: ‘weblogic.application.ModuleException: Context path ‘/deployinfo’ is already in use by the module: deployinfo application: CrmCommonApp’
change the context path of the application and deploy again.
How/Where can I change the context path of the application ?
in weblogic.xml for a war, in application.xml for an ear…
Hi All
Suddenly on of my deployed application is change the status from active to admin. Could u plz tell me the reason y it’s got changed?
Thanks in advance
Hi Dhani,
Did you see any exceptions in the server logs??
Thanks,
Faisal
The reason for server is admin mode is database not available for the server……..
Hi Faisal,
Thanks for you reply,
Actually it’s a datasource issue. whenever the db is down the status is changed to admin state. Now the issue is resolved.
Thanks,
JWALA
Hi All,
I am facing issue while starting the weblogic 10.0 server. getting the error as “The server cannot be started.
Either the server process could not be started or it terminated abruptly. Check the start script. ”
After getting this error, I have deleted my domain and created once again , deployed the .ear, created the data sources. Then server starts working properly. next day again i faced the same problem.
Can anyone of you please guide me infront of this.
Hi Gunjan,
How are you trying to start the server? Do you face the issue for admin server or managed server?
Please let us know.
An internal error occurred during: “Publishing to Oracle WebLogic Server 11gR1 (10.3.6) at localhost [audit_domain]…”.
Could not initialize class oracle.eclipse.tools.weblogic.facets.WlsGarFacet
this looks to be related to eclipse classpath setup…
Excellant – Perfectly worked – Thank you Sou much for the Post
thanks Sandeep!
Hi,
I am srao.I deployed my .ear file in to WL 11G.its working fine.if I deploy it in 12C WL its not showing list services.can you plz help me do i need to do any changes.am getting below error
ExecuteThread: ‘3’ for queue: ‘weblogic.kernel.Default (self-tuning)’::: ERROR org.apache.axis2.deployment.DeploymentEngine – – Message[-Could not create URL from ‘META-INF/FSLASNService.wsdl’ and ‘FSLASNService.xsd’]
org.apache.axis2.deployment.DeploymentException: Could not create URL from ‘META-INF/xxx.wsdl’ and ‘xxx.xsd’
Here in .aar i have META-INF inside that dir i have .WSDL file and .XSD files.both are having same name like xxx.aar,xxx.wsdl,xxx.xsd.
for workaround i changed .wsdl name like xxx1.wsdl.its deployed but list services not comming also getting below error.
Unable to generate WSDL 1.1 for this service
If you wish Axis2 to automatically generate the WSDL 1.1, then please +set useOriginalwsdl as false in your services.xml
Hi Sandhya,
Can you please mail the complete log files to weblogicwonders@weblogic-wonders.com?
Thanks,
Faisal
Thanks for your reply.I mailed you log files
Hi,
Did you find a solution for the Axis2 and Weblogic 12c error “Could not create URL from ‘META-INF/”. ?
Sincerely,
Audrius
Hi,
we are trying to launch the ui application but while launching it getting below error we are using JDK 1.6 and weblogic 10.3.5. would you please help us to fix this issue :
javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.Document
at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:129)
at weblogic.jsp.internal.jsp.JspTagLibraryFeature.parseTldFromWebXML(JspTagLibraryFeature.java:897)
at weblogic.jsp.internal.jsp.JspTagLibraryFeature.initFromWebXML(JspTagLibraryFeature.java:870)
at weblogic.jsp.internal.jsp.JspTagLibraryFeature.init(JspTagLibraryFeature.java:458)
at weblogic.jsp.internal.jsp.JspTagLibraryFeature.init(JspTagLibraryFeature.java:257)
at weblogic.jsp.internal.jsp.JspTagLibraryFeature.setCPL(JspTagLibraryFeature.java:48)
at weblogic.jsp.internal.CPL.getFeature(CPL.java:731)
at weblogic.jsp.internal.jsp.JspParser.getTagLibraryFeature(JspParser.java:4603)
at weblogic.jsp.internal.jsp.JspParser.getTagLibInfo(JspParser.java:3009)
at weblogic.jsp.internal.jsp.JspParser.jspParse(JspParser.java:693)
at weblogic.jsp.internal.jsp.JspParser._parse(JspParser.java:604)
at weblogic.jsp.internal.jsp.JspParser.parse(JspParser.java:597)
at weblogic.jsp.internal.jsp.JspAnalyzer.parseFile(JspAnalyzer.java:104)
at weblogic.jsp.internal.jsp.JspAnalyzer.parse(JspAnalyzer.java:92)
at weblogic.jsp.internal.ProxySourceFile.parse(ProxySourceFile.java:106)
at weblogic.jsp.internal.SourceFile.getAst(SourceFile.java:559)
at weblogic.jsp.internal.SourceFile.getAst(SourceFile.java:533)
at weblogic.jsp.internal.SourceFile.check(SourceFile.java:335)
at weblogic.jsp.internal.ProxySourceFile.codeGen(ProxySourceFile.java:224)
at weblogic.jsp.internal.SourceFile.codeGen(SourceFile.java:327)
at weblogic.jsp.internal.client.ClientUtilsImpl$CodeGenJob.run(ClientUtilsImpl.java:599)
at weblogic.jsp.internal.client.Job.performJob(Job.java:83)
at weblogic.jsp.internal.client.ThreadPool$WorkerThread.run(ThreadPool.java:217)
at weblogic.servlet.jsp.JavelinxJSPStub.reportCompilationErrorIfNeccessary(JavelinxJSPStub.java:226)
at weblogic.servlet.jsp.JavelinxJSPStub.compilePage(JavelinxJSPStub.java:162)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:256)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:216)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:243)
we kept xerces.jar in both lib folder of application as well as weblogic lib but did not get any success.
you can keep the jar in WEB-INF and user prefer-web-inf classes option to true in weblogic.xml
Enable -verbose:class to find out where its getting loaded from..
Thank you for your reply…But what you have suggested I am doing the same and still facing the same problem
would you please provide some more possible solution for same
what exception are you facing?
Amrita, email your log file to Divya.Dureja@gmail.com I will take a look.
hi one and all,
i got a question one of the the interview can u please suggest me?
if u deploy the application into the weblogic server cluster one of the server in the cluster the deployment is failed?what is the root cause ?how to fix the issue?
how to resolve the issue
check the logs.. generally due to resource unavailabilty – datasource, jms queues topics.. instead of targetting on the cluster its targeted to only one server
Hi,
i am deploying a JCA Resource adaptor in weblogic 10.3.3.while i deploying i getting the below error.
1] The ra.xml class ‘oracle.tip.adapter.api.OracleConnectionFactory’ was not found in the resource adapter archive/application.
[2] The ra.xml class ‘oracle.tip.adapter.brm.BRMConnectionFactory’ was not found in the resource adapter archive/application
Please suggest on the issue.
Thanks
Divya
Hi,
some times managed servers are going down suddenly.can u please tel me why it’s happening.
Hi Ramana,
Can you please paste the managed server logs here?
Thanks,
Faisal
Hello,
Can you please help me on below issue?
when i try to install and click on finish button i get below exception in console?
The deployment has not been installed.
java.lang.NoSuchMethodException: weblogic.management.configuration.AppDeploymentMBeanImpl.isCacheInAppDirectorySet()
can you please paste your web.xml here?
I should have the following schema definition
-Faisal
Hi,
I’m facing this issue in production. My application seems to be working fine even though I get below exceptions. But I don’t understand what needs to be done. Please find my server configuration: Oracle Linux 6, JDK 7, WL 10.3.6. Appreciate your immediate help.
Thanks in advance.
And am getting the below exception:
2015-06-12 14:14:38,236 ERROR [oracle.retail.stores.common.webservice.logging.SOAPLoggingHandler] Unable to log inbound SOAPMessage
com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: Error during saving a multipart message
at com.sun.xml.internal.messaging.saaj.soap.MessageImpl.saveChanges(MessageImpl.java:1204)
at com.sun.xml.internal.messaging.saaj.soap.MessageImpl.writeTo(MessageImpl.java:1296)
at oracle.retail.stores.common.webservice.logging.SOAPLoggingHandler.handleMessage(SOAPLoggingHandler.java:60)
at oracle.retail.stores.common.webservice.logging.SOAPLoggingHandler.handleMessage(SOAPLoggingHandler.java:34)
at com.sun.xml.ws.handler.HandlerProcessor.callHandleMessage(HandlerProcessor.java:284)
at com.sun.xml.ws.handler.HandlerProcessor.callHandlersRequest(HandlerProcessor.java:135)
at com.sun.xml.ws.handler.ServerSOAPHandlerTube.callHandlersOnRequest(ServerSOAPHandlerTube.java:140)
at com.sun.xml.ws.handler.HandlerTube.processRequest(HandlerTube.java:117)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:866)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:815)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:778)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:680)
at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:403)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:539)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:253)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:140)
at weblogic.wsee.jaxws.WLSServletAdapter.handle(WLSServletAdapter.java:171)
at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:708)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.wsee.util.ServerSecurityHelper.authenticatedInvoke(ServerSecurityHelper.java:103)
at weblogic.wsee.jaxws.HttpServletAdapter$3.run(HttpServletAdapter.java:311)
at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:336)
at weblogic.wsee.jaxws.JAXWSServlet.doRequest(JAXWSServlet.java:99)
at weblogic.servlet.http.AbstractAsyncServlet.service(AbstractAsyncServlet.java:99)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:184)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3732)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: javax.xml.transform.TransformerFactoryConfigurationError: Provider org.apache.xalan.processor.TransformerFactoryImpl not found
at javax.xml.transform.TransformerFactory.newInstance(TransformerFactory.java:107)
at com.sun.xml.internal.messaging.saaj.util.transform.EfficientStreamingTransformer.(EfficientStreamingTransformer.java:68)
at com.sun.xml.internal.messaging.saaj.util.transform.EfficientStreamingTransformer.newTransformer(EfficientStreamingTransformer.java:420)
at com.sun.xml.internal.messaging.saaj.soap.impl.EnvelopeImpl.output(EnvelopeImpl.java:257)
at com.sun.xml.internal.messaging.saaj.soap.impl.EnvelopeImpl.output(EnvelopeImpl.java:305)
at com.sun.xml.internal.messaging.saaj.soap.SOAPPartImpl.getContentAsStream(SOAPPartImpl.java:311)
at com.sun.xml.internal.messaging.saaj.soap.MessageImpl.getHeaderBytes(MessageImpl.java:1015)
at com.sun.xml.internal.messaging.saaj.soap.MessageImpl.saveChanges(MessageImpl.java:1166)
… 38 more
Caused by: java.lang.ClassNotFoundException: org/apache/xalan/processor/TransformerFactoryImpl
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:270)
at javax.xml.transform.FactoryFinder.getProviderClass(FactoryFinder.java:125)
at javax.xml.transform.FactoryFinder.newInstance(FactoryFinder.java:182)
at javax.xml.transform.FactoryFinder.find(FactoryFinder.java:250)
at javax.xml.transform.TransformerFactory.newInstance(TransformerFactory.java:101)
… 45 more
CAUSE:
javax.xml.transform.TransformerFactoryConfigurationError: Provider org.apache.xalan.processor.TransformerFactoryImpl not found
at javax.xml.transform.TransformerFactory.newInstance(TransformerFactory.java:107)
at com.sun.xml.internal.messaging.saaj.util.transform.EfficientStreamingTransformer.(EfficientStreamingTransformer.java:68)
at com.sun.xml.internal.messaging.saaj.util.transform.EfficientStreamingTransformer.newTransformer(EfficientStreamingTransformer.java:420)
at com.sun.xml.internal.messaging.saaj.soap.impl.EnvelopeImpl.output(EnvelopeImpl.java:257)
at com.sun.xml.internal.messaging.saaj.soap.impl.EnvelopeImpl.output(EnvelopeImpl.java:305)
at com.sun.xml.internal.messaging.saaj.soap.SOAPPartImpl.getContentAsStream(SOAPPartImpl.java:311)
at com.sun.xml.internal.messaging.saaj.soap.MessageImpl.getHeaderBytes(MessageImpl.java:1015)
at com.sun.xml.internal.messaging.saaj.soap.MessageImpl.saveChanges(MessageImpl.java:1166)
at com.sun.xml.internal.messaging.saaj.soap.MessageImpl.writeTo(MessageImpl.java:1296)
at oracle.retail.stores.common.webservice.logging.SOAPLoggingHandler.handleMessage(SOAPLoggingHandler.java:60)
at oracle.retail.stores.common.webservice.logging.SOAPLoggingHandler.handleMessage(SOAPLoggingHandler.java:34)
at com.sun.xml.ws.handler.HandlerProcessor.callHandleMessage(HandlerProcessor.java:284)
at com.sun.xml.ws.handler.HandlerProcessor.callHandlersRequest(HandlerProcessor.java:135)
at com.sun.xml.ws.handler.ServerSOAPHandlerTube.callHandlersOnRequest(ServerSOAPHandlerTube.java:140)
at com.sun.xml.ws.handler.HandlerTube.processRequest(HandlerTube.java:117)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:866)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:815)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:778)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:680)
at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:403)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:539)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:253)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:140)
at weblogic.wsee.jaxws.WLSServletAdapter.handle(WLSServletAdapter.java:171)
at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:708)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.wsee.util.ServerSecurityHelper.authenticatedInvoke(ServerSecurityHelper.java:103)
at weblogic.wsee.jaxws.HttpServletAdapter$3.run(HttpServletAdapter.java:311)
at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:336)
at weblogic.wsee.jaxws.JAXWSServlet.doRequest(JAXWSServlet.java:99)
at weblogic.servlet.http.AbstractAsyncServlet.service(AbstractAsyncServlet.java:99)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:184)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3732)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: java.lang.ClassNotFoundException: org/apache/xalan/processor/TransformerFactoryImpl
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:270)
at javax.xml.transform.FactoryFinder.getProviderClass(FactoryFinder.java:125)
at javax.xml.transform.FactoryFinder.newInstance(FactoryFinder.java:182)
at javax.xml.transform.FactoryFinder.find(FactoryFinder.java:250)
at javax.xml.transform.TransformerFactory.newInstance(TransformerFactory.java:101)
… 45 more
hi
how to solve the problem in web logic during installation p6 there shows p6 status failed what is the reason pease explain
Hi Syed,
Can you please elaborate?
Can you please share the installation logs?
Thanks,
Faisal
Hi,
Please give me a log snippet to understand the issue. Also the information about which step in the installation is it failing.
Thanks,
Divya
Hi ,
This is Gopi , Please share common issues which you are facing in weblogic in realtime.
so it helps me in interview.