Remote debugger

Hi, I am looking for a remote debugger for a Java application. Does anyone have any advice ? Thanks.

Hi Meggie,
try to use JBuilder 4 (or even higher) because this IDE has everything you need. You can even debug EJBs remotely with it.
Gabe

Similar Messages

*** FREE REMOTE DEBUGGER UTILITY ***

I just created this "remote debugger" last week because I wanted to get runtime output from my servlets without having to resort to finding the server logs...scanning them...etc. It can also be used to log info locally. Here is the code for the screen logger:
package com.mycode.remotedebugger.applet;import javax.swing.*;import java.awt.*;import java.awt.event.*;import java.net.*;import java.io.*;public class CRemoteDebugger extends JApplet implements Runnable{ boolean isStandalone = false; static ServerSocket m_socket = null; JScrollPane jScrollPane1 = new JScrollPane(); static Thread runner = null; static Socket connection = null; BorderLayout borderLayout1 = new BorderLayout(); JTextArea jTextArea1 = new JTextArea(); /** * Constructs a new instance. */ /** * getParameter * @param key * @param def * @return java.lang.String */ public String getParameter(String key, String def) { if (isStandalone) { return System.getProperty(key, def); } if (getParameter(key) != null) { return getParameter(key); } return def; } public CRemoteDebugger() { } /** * Initializes the state of this instance. */ /** * init */ public void init() { try { jbInit(); } catch (Exception e) { e.printStackTrace(); } } public boolean isConnected() { return m_socket != null; } private void jbInit() throws Exception { this.setSize(new Dimension(400, 400)); this.getContentPane().add(jScrollPane1, BorderLayout.CENTER); jScrollPane1.getViewport().add(jTextArea1, null); runner = new Thread(this); runner.start(); } public void run() { try { m_socket = new ServerSocket(6666); while(true) { InetAddress ia = InetAddress.getLocalHost(); connection = m_socket.accept(); InputStream is = connection.getInputStream(); BufferedReader br = new BufferedReader(new InputStreamReader(is)); String strLine = br.readLine(); while(strLine != null) { jTextArea1.append(strLine + "\n"); jTextArea1.setCaretPosition(jTextArea1.getDocument().getLength()); strLine = br.readLine(); } } } catch(Exception e) { } } /** * start */ public void start() { setLookAndFeel(); } /** * stop */ public void stop() { } /** * destroy */ public void destroy() { if(m_socket != null) { try { m_socket.close(); } catch (IOException ioe) { } m_socket = null; } if(runner != null) runner = null; if(connection != null) { try { connection.close(); } catch(IOException ioe) { } connection = null; } } /** * getAppletInfo * @return java.lang.String */ public String getAppletInfo() { return "Applet Information"; } /** * getParameterInfo * @return java.lang.String[][] */ public String[][] getParameterInfo() { return null; } /** * main * @param args */ public static void main(String[] args) { CRemoteDebugger applet = new CRemoteDebugger(); applet.isStandalone = true; JFrame frame = new JFrame(); frame.setTitle("Remote Debugging"); frame.getContentPane().add(applet, BorderLayout.CENTER); applet.init(); applet.start(); frame.setSize(400, 420); Dimension d = Toolkit.getDefaultToolkit().getScreenSize(); frame.setLocation((d.width - frame.getSize().width) / 2, (d.height - frame.getSize().height) / 2); frame.setVisible(true); frame.addWindowListener(new WindowAdapter() { public void windowClosing(WindowEvent e) { if(m_socket != null) { try { m_socket.close(); } catch (IOException ioe) { } m_socket = null; } if(runner != null) runner = null; if(connection != null) { try { connection.close(); } catch(IOException ioe) { } connection = null; } System.exit(0); } }); } void setLookAndFeel(){ try { UIManager.setLookAndFeel(UIManager.getSystemLookAndFeelClassName()); } catch(Exception e) { e.printStackTrace(); } }}
I compiled this and put it into a jar file for easy running via a shortcut on my desktop.
Here is the static function you would put either in your application/applet or perhaps in some utility class that you import:
package com.mycode.common.utilities;import java.awt.*;import java.awt.event.*;import java.net.*;import java.io.*;public class RemoteDebugMessage{ static Socket m_socket = null; static PrintWriter serverOutput = null; /** * Constructor */ public static void Print(String strClient, int nPort, String strMessage) { try { m_socket = new Socket(strClient,nPort); if(m_socket != null) { OutputStream os = m_socket.getOutputStream(); if(os != null) { serverOutput = new PrintWriter(new BufferedOutputStream(m_socket.getOutputStream()),true); if(serverOutput != null) { serverOutput.println(strMessage); } } } } catch(IOException ioe) { } try { m_socket.close(); m_socket = null; serverOutput = null; } catch(IOException ioe) { } }}
The "server" side listens on port 6666 (you can always change to whatever port you like and recompile) Then, in your code where you wish to watch messages in realtime, you call the static function above:
RemoteDebugMessage.Print("MachineName",6666,"This is my message!");
Where "MachineName" is the name of your pc.

Thank god for the scrollbars. :)
Maybe you should repost and add proper newlines.

If VS 2008 'Remote Debugger' is added to an existing VS 2008 install, should VS 2010 first be uninstalled?

I found that Visual Studio 2008 Remote Debugger was not included when Visual Studio 2008 was installed. I also have Visual Studio 2010 installed. Should Visual Studio 2010 be uninstalled prior to installing Visual Studio 2008
Remote Debugger?
Thanks

Hi Bontrager,
Based on your issue, I know that since the different Visual Studio versions exist as separate applications. So if you want to install the Visual Studio 2008 Remote Debugger, you will not need to uninstall Visual Studio 2010. Visual Studio 2010 will
not affect you install the Visual Studio 2008 Remote Debugger.
Hope it help you!
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

How to kill remote debugger listener...?

Hi,
Is there a way to kill the remote debugger listener, without closing the sql-developer (1.5.5)...?
Because it hangs sometimes and I have to establish a new port and a new port ...
Thanks, Juergen

You can't.
I complained about this too a couple of years ago, management acknowledged the issue, but still no sign of wanting to enhance the behaviour.
Only solution I know is restart sqldev.
Best add this as feature request at the SQL Developer Exchange, so other users can vote to add weight for possible future implementation.
Regards,
K.

Multiple remote debugger connections from JDev

Hello,
I'm running JDev Studio Edition Version 11.1.2.3.0
I need to debug an application running on a 2 node WLS Cluster. I have the two servers running in debug mode listening on different hosts/ports.
In JDev I click the debug button twice and open a connection to each server in turn, however I suspect that the last connection made may be the only one that's active?
Can somebody please clarify whether it's possible to open multiple remote debugger connections in JDev?
Many thanks.

Hello,
I'm running JDev Studio Edition Version 11.1.2.3.0
I need to debug an application running on a 2 node WLS Cluster. I have the two servers running in debug mode listening on different hosts/ports.
In JDev I click the debug button twice and open a connection to each server in turn, however I suspect that the last connection made may be the only one that's active?
Can somebody please clarify whether it's possible to open multiple remote debugger connections in JDev?
Many thanks.

Visual Studio cannot remote debug Azure cloud service: There was a failure to launch the remote debugger

I am trying to invoke remote debugger on an Azure worker role cloud service, following the example of
http://msdn.microsoft.com/en-us/library/azure/ff683670.aspx
But on attaching the remote debugger for the cloud service instance
Microsoft Visual Studio
There was a failure to launch the remote debugger.
OK
According to somebody else's extra coverage on the topic, there are extra ports 4016/4017 that need to be taken care of (but do they have to be exposed externally)?
http://developers.de/blogs/damir_dobric/archive/2014/02/04/behind-windows-azure-remote-debugger.aspx
So servicedefinition.csdef gets
    <Endpoints>
      <InputEndpoint name="Endpoint1" protocol="http" port="80" />
      <InputEndpoint name="RemoteDebugger" protocol="tcp" port="4016" localPort="4016" />
      <InputEndpoint name="RemoteDebugger2" protocol="tcp" port="4017" localPort="4017" />
      <InstanceInputEndpoint name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector" protocol="tcp" localPort="30398">
        <AllocatePublicPortFrom>
          <FixedPortRange min="30400" max="30424" />
        </AllocatePublicPortFrom>
      </InstanceInputEndpoint>
      <InstanceInputEndpoint name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Forwarder" protocol="tcp" localPort="31398">
        <AllocatePublicPortFrom>
          <FixedPortRange min="31400" max="31424" />
        </AllocatePublicPortFrom>
      </InstanceInputEndpoint>
    </Endpoints>
Serviceconfiguration.cscfg gets
      <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector.Enabled" value="true" />
      <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector.Version" value="2.3" />
      <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.ClientThumbprint" value="THUMBNAIL" />
      <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.ServerThumbprint" value="THUMBNAIL" />
    </ConfigurationSettings>
    <Certificates>
      <Certificate name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.TransportValidation" thumbprint="THUMBNAIL" thumbprintAlgorithm="sha1"
/>
    </Certificates>
But all these are to no avail; the same error still pops for Visual Studio 2013 Update 4; Azure SDK 2.3
Anybody regularly perform remote debugging for Azure cloud services?
The melody of logic will always play out the truth. ~ Narumi Ayumu, Spiral

And, how do I control that in Visual Studio?
All I get is the Attach Debugger... context menu option in the Azure cloud service nodes in Server Explorer. That is where it is failing. There are no customisable options.
Because of that, the Attach to Process dialog box is unable to retrieve the list of processes (to debug) in the remote worker role instance server.
I tested a blank-template worker role project and published to a new cloud project, and this simplistic copy had no problems with the Remote debugger.
Now the question is, what is it about this real-world project/cloud service that is different from blank sample? From what I compare between what I think are the relevant settings, there are none.
ServiceDefinition.csdef
<Imports>
<Import moduleName="Diagnostics" />
<Import moduleName="RemoteAccess" />
<Import moduleName="RemoteForwarder" />
<Import moduleName="RemoteDebuggerConnector" />
</Imports>
<Contents>
<Content destination=".\">
<SourceDirectory path="D:\Projects\experiments\workerrole1\workerrole1\rcf\Debug\RemoteDebuggerContent\" />
</Content>
</Contents>
<Endpoints>
<InstanceInputEndpoint name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector" protocol="tcp" localPort="30398">
<AllocatePublicPortFrom>
<FixedPortRange min="30400" max="30424" />
</AllocatePublicPortFrom>
</InstanceInputEndpoint>
<InstanceInputEndpoint name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Forwarder" protocol="tcp" localPort="31398">
<AllocatePublicPortFrom>
<FixedPortRange min="31400" max="31424" />
</AllocatePublicPortFrom>
</InstanceInputEndpoint>
</Endpoints>
ServiceConfiguration.cscfg
<ConfigurationSettings>
<Setting name="Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString" value="DefaultEndpointsProtocol=https;AccountName=storage;AccountKey=" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.Enabled" value="true" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.AccountUsername" value="" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.AccountEncryptedPassword" value="" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.AccountExpiration" value="2015-12-31T23:59:59.0000000+08:00" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteForwarder.Enabled" value="true" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector.Enabled" value="true" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector.Version" value="2.4" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.ClientThumbprint" value="" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.ServerThumbprint" value="" />
</ConfigurationSettings>
<Certificates>
<Certificate name="Microsoft.WindowsAzure.Plugins.RemoteAccess.PasswordEncryption" thumbprint="" thumbprintAlgorithm="sha1" />
<Certificate name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.TransportValidation" thumbprint="" thumbprintAlgorithm="sha1" />
</Certificates>
The melody of logic will always play out the truth. ~ Narumi Ayumu, Spiral

When I started my Mac the screen was white with the Apple logo and power motion icon running. I attempted to turn off Mac then a message stating "Debugger called: Button SCI . Also "Waiting for remote debugger connection." What is my next step?

When I started my Mac the screen was white with the Apple logo and power motion icon running. I attempted to turn off Mac then a message stating "Debugger called: <Button SCI>. Also "Waiting for remote debugger connection." What is my next step?

Hi , and a warm welcome to the forums!
Could be many things, we should start with this...
"Try Disk Utility
1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu at top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
*Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
3. Click the First Aid tab.
4. Select your Mac OS X volume.
5. Click Repair Disk, (not Repair Permissions). Disk Utility checks and repairs the disk."
http://docs.info.apple.com/article.html?artnum=106214
Then try a Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
(Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.)
If perchance you can't find your install Disc, at least try it from the Safe Boot part onward.
If 10.7.0 or later...
Bootup holding CMD+r, or the Option/alt key to boot from the Restore partition & use Disk Utility from there to Repair the Disk, then Repair Permissions.
And sorry to report that OSX is more Widows like than ever, but….
If that doesn't help Reinstall the OS.

Remote debugger gives error about not supporting this version

I have LabWindows/CVI 8.0.1 (356) on a Windows 7 machine and I'm trying to remotely debug a product on a Windows XP machine. The product is a DLL called by TestStand sequences. TestStand is version 2.0.1f1. When trying to connect, I receive the following error message ( see attachment ) after the debugger machine sees TestStand was launched on the debugee machine. What does this mean? Thanks.
-G-
Attachments:
Error_Msg.docx ‏30 KB

Hi Grasshopper,
This problem is possibly occurring because your LabWindows/CVI Run-Time Engine is newer than your version of LabWindows/CVI Development System. Please refer to the following forum thread which mentions a similar problem with remote debugging: http://forums.ni.com/t5/LabWindows-CVI/Remote-Debug-problem-with-CVI-Runtime-Versions/m-p/2067462 .
To correct this problem, you must make the version of your Run-Time Engine (RTE) the same as or earlier than the version of your Development System. You can either do this by upgrading LabWindows/CVI to a newer version, or by uninstalling the RTE on your debugger/debugee, and then installing the RTE corresponding to your Development System on both machines.
Please let me know after completing this step whether you encounter any further errors.
Warm Regards,
Daniel D.
National Instruments
Automated Test Software R&D

[2514] Remote debugger asks for source file.

I've been testing the fixed remote debug facility in the new release.
It is now possible to connect to a remote session and start debugging, but as soon as I hit a breakpoint a dialog pops up saying that it is unable to find the source file for the package being debugged. It offers various options, including two 'Look for file in connection ....'
and browsing for the source file.
If I do a local debug first, this does not happen.

We have a bug logged for "unable to find the source". You need to accept the dialog and select the connection you want to do the debugging on. For the other issue, we have multiple databases, with connections for users with the same name in each and have not run into the issue described. Please can you provide more detail.
Sue

Flash Remote Debugger Help

Yesterday, my Flash CS3 AS2 remote debugging stopped working
after I installed a number of Adobe updates and on Mac OS X (Intel)
update. Before I installed the updates, I was able to debug any SWF
loaded in my browser window with the CS3 debug interface and output
window. After I rebooted, all of my browsers stopped sending my the
prompt to connect to a local host or enter an IP. Also, "debug" is
no longer an option in the drop down menu when I right click on the
swf in the browser window. Flash remote debugging is marked
properly in the FLA publish settings and a new SWD is being
published every time I test. But the player doesn't attempt to
connect at all! I don't know if the loss of this functionality is
related to the updates but it does seem that way.
Any help, please?!
Thanks,
Steven

Problem solved. After the update, I needed to get the newest
version of the Adobe Debug Player for Intel Macs.
see what players you have here:
http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_15507&sliceId=1
get the player specific to your OS here:
http://www.adobe.com/shockwave/download/alternates/#fp

10.1.3 - Remote Debugger not connecting to remote OC4J

I have been using a previous version of JDeveloper and connecting to a remote OC4J instance without any problems. However, 10.1.3 does not seem to be able to connect. I select the Remote Debugging/Profiling option from Project Properties-Run/Debug
The debug string that I am using in starting the JVM is
-Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=2102,suspend=n
Anyone any ideas?

This has been answered by post 'Remote debugging Tomcat 4.1', posted by 388431 on March 31.

Flash player connecting to remote debugger

hello,
i have linux computer with fdb running there,
can i run flashplayerdebugger.exe connecting to that remote linux host from command line? maybe some configuration variables in mms.cfg?
thank you.

Go with dismiss all.
Sincerely,
Michael
El 12/05/2009, a las 10:34, Foxchx <[email protected]> escribió:
>
I am not sure i am getting that?!
>
is it like with php when you don't hide the basic warning that are
not really errors and warning codes show?
>
Should i continue or dismiss, i always get confused when i get those
2 choices, continue and dismiss?!
>

Found x-platform remote debugger that works with WLSv4.5.1!!

[att1.html]

Hi!
I have problem to get the co-client debug project to run. Do you have
the same problem?
-----Original Message-----
From: Terry Potter [mailto:[email protected]]
Posted At: måndag, augusti 07, 2000 23:18
Posted To: tools
Conversation: Debugger that works with WebLogic 5.1?
Subject: Re: Debugger that works with WebLogic 5.1?
I use the deistributed debugging that comes with Visual Cafe by Webgain
v4.0. It works fine.
"Jim Piersol" <[email protected]> wrote in message
news:3989ccec$[email protected]..
Get a real debugger. Try BugSeeker from http://www.karmira.com
Jim Piersol
Senior Software Engineer
Sun Certified Java Programmer
Strata Group, Inc.
[email protected]
"Greg Kim" <[email protected]> wrote in message
news:8ibuit$35e$[email protected]..

Is anyone having problem with remote debugg in version jdev9i_902

Remote debugging used to work for me with "jdev9i_rc2" but no longer working with "jdev9i_902". I am tring to debug an app running on Weblogic 6.1 on Win2K.
Can anyone verify that Remote debugging is working for him/her (preferably Weblogic 6.1 and Win2k?
Thanks.

I use Jdev 9.0.2 to remote debug Oracle 9iAS 1.0.2.2.1. it works for me if I use OJVM on both client and server. The OS is Windows 2000.

Jdev remote debugger problem

When we debug a Java Stored proc with JDev (3.2.2 against 8.1.7), if you hit Program Reset instead of letting the proc run through completion, JDev leaves a hung session sitting out there in the DB that can only be killed by restarting the instance. This also seems to lock the object so that deployment of any dependant Java SP's after this time cannot be deployed without an instance restart. This is very frustrating when you have 10 developers working on an app at the same time. Has this bug been addressed yet?
Thanks in advance.

Mistake: misnamed the bean in problem statement.
I meant to say the 'DeptBean' (not hrApp EJB) did not compile, using sample code from instructions.
Surely someone can help.
Robert

Remote debugger

Similar Messages

Maybe you are looking for