How to run remote debug in eclipse with weblogic

-
I came across so many question and answers posted by peoples regarding to initiate a remote debug session from eclipse to application which is running in xyz port of weblogic server.so thought of coming up with what i have done,which is pretty straight forward.(i have tried this successfully in Weblogic9.1)

The very first golden rule is,while configuring the remote debug session make sure you are not specifying the same port number where your weblogic server is running,it has to be a free port(use this link to find the appropriate ports -> List of Ports).

The configuration  for remote debug is specified in the startup scripts of weblogic server,either in the 'startWeblogic.cmd' or 'setDomainEnv.cmd' or any other executable file associated with startup of the server.

I am modifying the script 'setDomainEnv.cmd'.Below are the two things you need to do to achieve this.

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.

debug java options




In the address property specify the debug port which i have given 8000.

Save the file and restart your weblogic server.
At the startup of weblogic server you can see this message
'Listening for transport dt_socket at address: 8000'
you are done with Weblogic.

Now go to your Eclipse IDE,Select WIndow-Show View-Debug.Debug Configurations-Remote Java-Application,right click,New.Name - can be any name,Project will be set default if you have already opened a file in Eclipse,otherwise choose from available projects configured in workspace, Hostname is the Server you want debug remotely, and the port is 8000,start debugging .

you can also check how we can run a  remote debug while both your admin and managed servers are running ->
Remote Debug with Managed Servers Running

Comments

Post a Comment

Popular posts from this blog

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

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