remote debug in eclipse with both Admin and Managed Servers running

-
For configuring Remote Debug in Managed Weblogic Server,the very first golden rule is,you should not specify any port number of  weblogic admin or  managed server which is running ,it has to be a free port(use this link to find the appropriate ports List of Ports).

How to create managed weblogic server and run multiple EAR's can be found in this link -> Run Multiple Ear in Managed Server Mode

How to run remote debug in Admin server can be found in the link
->Remote Debugging Weblogic Admin Server


The configuration  for remote debug is specified in the startup script 'setDomainEnv.cmd'.



First Approach

Here we need to  create three scripts corresponding to the orignial scritps,'startManagedWeblogic.cmd', 'startWeblogic.cmd' and 'setDomainEnv.cmd.


For Eg:

Create the scripts  startManagedATGProductionWeblogic.cmd,startWeblogicATGProduction.cmd,
setDomainEnvATGProduction.cmd by copying from the original script.Modify the call to each of this scripts as per the new naming convention.

Then for the degbug to work  in the setDomainEnvATGProduction.cmd file

1. Set the debgug flag as true in the first line of the script.(set
   debugFlag=true)

2. Add the line to append JAVA_OPTIONS variable,if the debug options is not already there.Now all recent weblogic versions comes with the debug option.

set JAVA_OPTIONS=-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8002,server=y,suspend=n %JAVA_OPTIONS%

In the address property you need to specify the debug port which i used as 8002 here.

Save the file and restart your managed weblogic server.
At the startup of managed weblogic server you can see this message
'Listening for transport dt_socket at address: 8002' you are done !!! . For Your Admin Server specify a port  eg:8004 in
setDomainEnv.cmd.Hope you know how to configure remote debug in eclipse.

Second Approach (Updated as per the new CIM settings)

Run CIM which will create instances for ATG Production,ATGPublishing and other Servers based on your Product Selection,you need a simple modification in the auto generated script generated by CIM for your Managed Servers. Copied the scripts generated by ATG10.2 CIM configurations below for your reference.The Bold part is the modification you need to do for remote debug to work.

C:\ATG\ATG10.2\home\servers\ATGProduction\startServerOnWeblogic.bat

setlocal
title ATGProduction

REM  -- Update USER_MEM_ARGS - added by CIM

set debugFlag=true

if "%DEBUG_PORT%"=="" (
    set DEBUG_PORT=8446
)

if "%JAVA_USE_64BIT%"=="true" (
  set USER_MEM_ARGS=-Xms512m -Xmx1024m -XX:NewSize=128m -XX:MaxNewSize=256m -XX:PermSize=256m -XX:MaxPermSize=512m
) else (
  set USER_MEM_ARGS=-Xms512m -Xmx1024m -XX:NewSize=128m -XX:MaxNewSize=256m -XX:PermSize=256m -XX:MaxPermSize=512m
)

REM  -- End USER_MEM_ARGS block - added by CIM
call "C:/Oracle/Middleware/user_projects/domains/base_domain//bin/startManagedWebLogic.cmd" ATGProduction t3://localhost:7001/ %*

endlocal

The script setDomainEnv.cmd will check whether the DEBUG_PORT is set,we are overriding this in the above script from our Managed Server and setting it to 8446.Similiarly if we call Admin Server Startup script it will default to port 8686.

setDomainEnv.cmd

if "%DEBUG_PORT%"=="" (
    set DEBUG_PORT=8686
)

This apporach will help to simultaneously run Admin and Managed Server with different EARS with Debugging enabled,This will be useful for Eg: We have a ATGProduction and ATGFullfillment Applications running in Admin and Managed or in multiple Managed Servers,We can run a live debug between applications,so that First Application create an Order and Second Applications start Processing the Order.

Comments

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

BCC site status inaccessible Agent Production in error state

-
Image
The Error Message showing in BCC T he 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
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