Started Weblogic server.
Deployed application into server.
Accessed the application for some time.
Undeployed the application from server.
Again deployed the same application into server
After 5th step getting the below exception and results blank page when try to access the application (It is working fine once I restart the server).
Is there any solution for this ?
Thanks,Gopal.
Caused by: oracle.jbo.ConfigException: JBO-33001: STRINGMANAGER: Message file: 'oracle.jbo.common.CommonMessageBundle' not found. (Looking for '33001')
at oracle.jbo.client.Configuration.loadFromClassPath(Configuration.java:457)
at oracle.jbo.common.ampool.PoolMgr.loadConfiguration(PoolMgr.java:756)
at oracle.jbo.common.ampool.PoolMgr.findPool(PoolMgr.java:591)
at oracle.jbo.client.Configuration.createRootApplicationModule(Configuration.java:1508)
at oracle.jbo.client.Configuration.createRootApplicationModule(Configuration.java:1485)
at oracle.cloud.applications.common.util.AMUtil.getAM(AMUtil.java:76)
at oracle.cloud.applications.common.util.AMUtil.getMyAM(AMUtil.java:98)
at oracle.cloud.applications.common.util.Configuration.getConfig(Configuration.java:242)
at oracle.cloud.applications.myapp.model.Executor.run(Executor.java:47)
at oracle.cloud.applications.common.util.Configuration.getFrequency(Configuration.java:150)
Caused by: oracle.mds.exception.MDSRuntimeException: MDS-00168: MDS object oracle.mds.core.MDSInstance#2391563b is being used after it or its MDSInstance or PManager has been released.
at oracle.mds.core.MDSInstance.checkNotReleased(MDSInstance.java:1600)
at oracle.mds.core.MDSInstance.getPersistenceManager(MDSInstance.java:906)
at oracle.mds.core.MDSSession.getPersistenceManager(MDSSession.java:2792)
at oracle.mds.core.MDSSession.getBaseMO(MDSSession.java:3874)
at oracle.mds.core.MDSSession.getMetadataObject(MDSSession.java:1750)
at oracle.adf.share.jndi.MDSBackingStore.documentExists(MDSBackingStore.java:159)
at oracle.jbo.client.Configuration.loadFromClassPath(Configuration.java:443)
at oracle.jbo.common.ampool.PoolMgr.loadConfiguration(PoolMgr.java:756)
at oracle.jbo.common.ampool.PoolMgr.findPool(PoolMgr.java:591)
at oracle.jbo.client.Configuration.createRootApplicationModule(Configuration.java:1508)
at oracle.jbo.client.Configuration.createRootApplicationModule(Configuration.java:1485)
at oracle.cloud.applications.common.util.AMUtil.getAM(AMUtil.java:76)
at oracle.cloud.applications.common.util.AMUtil.getMyAM(AMUtil.java:98)
at oracle.cloud.applications.common.util.Configuration.getConfig(Configuration.java:242)
at oracle.cloud.applications.myapp.model.Executor.run(Executor.java:47)
at oracle.cloud.applications.common.util.Configuration.getFrequency(Configuration.java:150)
Follow the below link for answer.
MDS-00168: MDS object is used after PManager has been relesed
Related
My Web API runs OK most of the time in IIS v.10 on Windows Server 2016. However, an error occurs from time to time and I can't figure out the error source or cause. The corresponding Windows Logs/Application error log record is as follows
Application '/LM/W3SVC/1/ROOT/MyWebAPI' with physical root '....\MyWebAPI\' failed to load clr and managed application.
Managed server didn't initialize after 120000 ms.
Process Id: 4840.
File Version: 12.2.19169.6. Description: IIS ASP.NET Core Module V2 Request Handler. Commit: e7f262e33108e92fc8805b925cc04b07d254118b
The error results in HTTP Error 500.30 - ANCM In-Process Start Failure on the client side. After that, MyWebAPI stops working and I have to recycle MyWebAPI application pool manually.
Can anybody help, please?
ACM 500.30 means something wrong with the startup.
for more info -> https://learn.microsoft.com/en-us/aspnet/core/test/troubleshoot-azure-iis?view=aspnetcore-3.1#50030-in-process-startup-failure
If you are using 3rd party services like KeyVault etc then surround them with try-catch and log error in the logger.
you can use event viewer for debugging.
https://www.happycoder.gr/blog/aspnet-core-20-event-viewer-application-logging/
I got the same error when I published my .net core 3.1 project.
You can get this error if your server is win-x64 and you published to win-x86. If this is the case, you must change the target runtime to win-x64.
Without changing something my webapplication refuses to load today.
I am using JBoss 4.0 and am deploying a web application using Inteli J IDE.
Initially I had the application at http://localhost:8080/app
Yesterday everything was working fine.
Today I am trying to run the application and am recieving a blank page.
Below is a screenshot from the debugger:
Update
I noticed that when I deploy 1 out of the 2 war's, I can access some addresses.
I am starting to suspect there is a problem with a Servlet context listener for one of the two war's.
Update 2
I see in the logs the following message:
java.lang.NoClassDefFoundError: org/jboss/cache/aop/PojoCacheMBean
The problem was with the deployed war. It seems if the deployment fails, this error is thrown for that context.
The solution in the specific case was to make a completely new/fresh and clean InteliJ project, and redo everything from the start with a fresh checkout.
I'm trying to create a sample application in endeca. When i run the initailze_services.bat I'm getting the following error log.
[01.30.15 11:54:07] SEVERE: Caught an exception while checking provisioning.
Caused by com.endeca.soleng.eac.toolkit.exception.EacCommunicationException
com.endeca.soleng.eac.toolkit.application.Application setDefinition - Caught exception while defining application 'ATGen'.
Caused by com.endeca.eac.client.EACFault sun.reflect.NativeConstructorAccessorImpl newInstance0 - null
Failure to initialize EAC application.
I tried solving this issue by deleting the state folder in platform services and then running it again. But still the same issue persists. Any help appreciated.
EACCommunicationException can mean a few things:
The EAC Central Server isn't running (fixed by ensuring that you've successfully started all Endeca services (Platform Services and Tools and Frameworks)
EAC Central Server is running, but couldn't be reached (fixed by ensuring you have the correct port and hostname specified for eacHost and eacPort in config/scripts/AppConfig.xml, and that you have no firewall rules blocking communication with EAC Central Server)
I have MVC application that uses integrated app pool.
Under this MVC application, i have created a virtual directory that points to our file server location. This file server has some pdfs and custom images.
When we try to access the resources via virtual directory, I get the following error:
Server Error in '/' Application.
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: An error occurred loading a configuration file: Failed to start monitoring changes to '\\nas2\CardDeck\web.config'.
Source Error:
[No relevant source lines]
Source File: \\nas2\CardDeck\web.config Line: 0
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.17929
When I change the app pool to classic, i can access these resources just fine. What am i missing here?
Thanks
App pool was running under "NetworkService" identity.
I have changed it to a user account that has admin permissions on the box.
The thing that i still need to figure out is, why these were working under classic app pool and network service as the identity?
I have migrated an application from WL 8 to WL 10 and set up my managed servers. They indicate that they are running, but when I try to access the site it throws a 404. This is my first time deploying anything on 10 so I could be missing something. Any ideas? Please let me know what additional information could be helpful. edit: I had this working, added a db connection and now it fails.
Here is my error:
weblogic.management.DeploymentException: Exception occured while downloading files
at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:43)
at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:98)
at weblogic.deploy.internal.targetserver.BasicDeployment.prepareDataUpdate(BasicDeployment.java:670)
at weblogic.deploy.internal.targetserver.BasicDeployment.stageFilesForStatic(BasicDeployment.java:713)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:100)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
java.io.IOException: [DeploymentService:290066]Error occurred while downloading files from admin server for deployment request "0". Underlying error is: "[DeploymentService:290065]Deployment service servlet encountered an Exception while handling the deployment datatransfer message for request id "0" from server "TEST01". Exception is: "weblogic.management.configuration.JDBCSystemResourceMBeanImpl"."
at weblogic.deploy.service.datatransferhandlers.HttpDataTransferHandler.getDataAsStream(HttpDataTransferHandler.java:86)
at weblogic.deploy.service.datatransferhandlers.DataHandlerManager$RemoteDataTransferHandler.getDataAsStream(DataHandlerManager.java:153)
at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:39)
at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:98)
at weblogic.deploy.internal.targetserver.BasicDeployment.prepareDataUpdate(BasicDeployment.java:670)
at weblogic.deploy.internal.targetserver.BasicDeployment.stageFilesForStatic(BasicDeployment.java:713)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:100)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
You got a weblogic.management.DeploymentException and this means that something went wrong in some server even if everything seems OK from the console.
Underlying error is from weblogic.management.configuration.JDBCSystemResourceMBeanImpl so I would review datasource config is appropiate for every target in your environment. Also check that datasource targets are the same as web application targets and JDBC drivers are available at managed servers classpath as well.
Try to log to the WebLogic Admin console and see what is the status of your application.
You can use the 'Testing' tab of your deployment to see the URL that the application has been deployed to. This will assist you in the troubleshooting process.
If you don't see anything here to test there are a few possible reasons, including the following:
The application failed to deploy and/or is not 'Active'
You are using a cluster and no managed servers are running
You have managed servers running but they are not in a 'RUNNING' state