BCC site status inaccessible Agent Production in error state

-
The Error Message showing in BCC

BCC Site Inaccessible error message

The error logs is showing the below message

/atg/epub/DeploymentServer Failed to connect to agent
'Production'. This agent not allowed to be absent for 
a deployment. The server will continue attempts to 
intialize the connection. Set loggingDebug to true for 
continued exception and stacktrace logging.

Analysis

This happens when the target/Production instance is down for some 
reason or the RMI configuration which points to the
target/Production instance may not be correct one.

Fix

If this is happening  due to target/Production instance down 
then we can restart the target/Production Server,Other wise 
correct the RMI configuration from the BCC agent configuration page
and reinitialise.

Verify the RMI Port in Configuration.properties file.Usually this file will be located in the path C:\ATG\ATG10.2\home\servers\ATGProduction\localconfig\atg\dynamo\Configuration.properties,make sure the RMI port in the file matches with the port number specified in the URL while configuring the ProdAgent in BCC.

This will solve the issue.

See Tweak BCC Snapshot

Comments

  1. UnknownFebruary 16, 2014 at 3:27 AM

    I am having smiliar issue,corrected rmi port but still getting same error..

    In your solution u have asked to update rmi port and reinitialise..can you elaborate what needs to be reinitialised?

    Thanks In Advance

    ReplyDelete
  2. SebastianFebruary 19, 2014 at 9:44 AM

    Yes,Go to BCC Admin Console then select Agent then Configuration,Modify the value for rmi port,Go back to Overview then Configuration,You will see a button 'Make Changes Live',Click this button to reinitialise the deployment topology

    ReplyDelete

Post a Comment

Popular posts from this blog

Weblogic Issues during EAR Deployment Exception in AppMerge flows progression

-
Unable to access the selected application Exception in AppMerge flows progression Bean already exists "weblogic.j2ee.descriptor.ModuleBeanImpl@..../Modules[weblogic.descriptor.internal.Descriptor.Beankey@....] This issue can happen in many scenarios, may be you need to check your deployment descriptors based on Application Servers used, this generally happens due to issue in XML files related to deployment. I got this issue when i mistakenly added the modules twice in the Manifest file, the module 'Store.Storefront' is added more than once in  'ATG-Required'  of my Manifest.MF file,due to this i am seeing the module 'storedocroot.war' is added twice in my application.xml which is located in the  path ATGProd.ear\META-INF\application.xml.Due to this i am not able to deploy my EAR file. I have removed the duplicate entry and deployed the application and everything working fine. ....... <module>         <web>             <web-uri>atg_
Read more

DUseSunHttpHandler=true weblogic.net.http.SOAPHttpsURLConnection Weblogic/Java HttpHandler issues

-
Verify the issue is happening due to the error throwing  from the weblogic class  SOAPHttpsURLConnection,then you need to inform the Application Server which handler implementation you need to use.  add the following option to JAVA_OPTIONS in   setDomainEnv.sh/setDomainEnv.cmd  on Unix/Windows.   -DUseSunHttpHandler=true.  eg:  set JAVA_PROPERTIES=%JAVA_PROPERTIES% %WLP_JAVA_PROPERTIES%  set JAVA_OPTIONS=%JAVA_OPTIONS% %JAVA_PROPERTIES% -  DUseSunHttpHandler=true -Dwlw.iterativeDev=%iterativeDevFlag% -  Dwlw.testConsole=%testConsoleFlag% -Dwlw.logErrorsToConsole=%  logErrorsToConsoleFlag%  This setting tells WebLogic to use the Sun's https Handler   implementation rather than the WebLogic one.  So after this,it will use the  class HttpsURLConnection from the  javax package.   See Also   SSL Handshake error   java.lang.RuntimePermission modifyThread
Read more