Wednesday 15 June 2016

blogger
[WLS 12.2.1.0.0] Managed servers going to FORCE_SHUTTING_DOWN state when resumed from ADMIN state.

Hello Viewer,

I have noticed one of the weird behavior in wls 12.2.1.0.0 version , where in when we start the server and in case any of the datasource do not come up because of associated database issue(database down or any other related issue). In that case server will stuck to Admin state which is normal behavior but when we will try to resume it from console it will again go to shutdown state.

Workaround: 

Reduce the initial connection capacity for datasource to ZERO.

Thanks a lot for your patience!!!

Regards
-Ashish


Friday 10 June 2016

blogger

Failed to initialize the application "SB_JMS_Proxy_N7de264e1.N2efb99d.2.1553951a327.N7ffe" due to error weblogic.management.DeploymentException: Exception occured while downloading files

Hello Viewer,

Today i faced one issue while bringing up the OSB servers.Servers were not coming up. After reaching to Admin state it again went to force shutting down mode.

After seeing the logs i got the below error:

 <Error> <Deployer> <BEA-149205> <Failed to initialize the application "SB_JMS_Proxy_N7de264e1.N2efb99d.2.1553951a327.N7ffe" due to error weblogic.management.DeploymentException: Exception occured while downloading files
weblogic.management.DeploymentException: Exception occured while downloading files
        at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:50)
        at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:59)
        at w
        Truncated. see log file for complete stacktrace
Caused By: java.io.IOException: [DeploymentService:290066]Error occurred while downloading files from Administration Server for deployment request "0". Underlying error is: "null"


Solution: Login to Admin console and goto deployments, search the ear for which you are facing the error, it should be in failed state.
It will not allow you to untarget this ear.just delete it from deployments and try to restart the server. This time servers should come up.

Thanks a lot for your patience!!!

Regards
-Ashish




Wednesday 1 June 2016

blogger

com.bea.console.exceptions.DeploymentConfigurationInitIncompleteException


Hello Viewer,

I opened the weblogic admin console and clicked on SAP Adapter  under deployments.it showed me the below error:

com.bea.console.exceptions.DeploymentConfigurationInitIncompleteException

Reason: This error came because disk space was full.you can check it by running the below command. "df -kh"

Solution: Clear the disk space and restart the Admin server and Managed server.

Note: Admin server restart is must to resolve this error.

Thanks a lot for your patience!!!

Regards
-Ashish