Remote debug listening socket failure

I am getting the following error when starting Weblogic with remote debugging enabled:
Error [4] in accept() call!
err:: Interrupted system call
Socket transport failed to init.
dt_socket transport error; accept failed, rc = -1
My java startup parameters include:
-Xdebug -Xnoagent -Xms64m -Xmx64m -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,address=3998
,suspend=n
I am using JDK1.2.2 and am running with the JDK opposed to JRE which I understand
is required when trying to remote debug with 1.2. I have $JPDA/lib/sparc in my
LD_LIBRARY_PATH and jpda.jar in my classpath.
Can anyone help please?

Problem resolved, thanks.
"Moby" <[email protected]> wrote:
>
I am getting the following error when starting Weblogic with remote debugging
enabled:
Error [4] in accept() call!
err:: Interrupted system call
Socket transport failed to init.
dt_socket transport error; accept failed, rc = -1
My java startup parameters include:
-Xdebug -Xnoagent -Xms64m -Xmx64m -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,address=3998
,suspend=n
I am using JDK1.2.2 and am running with the JDK opposed to JRE which
I understand
is required when trying to remote debug with 1.2. I have $JPDA/lib/sparc
in my
LD_LIBRARY_PATH and jpda.jar in my classpath.
Can anyone help please?

Similar Messages

Remote Debug Listener crashes

Hi,
I try to remote debug via SQL-Developer and create a remote debug listener in my first sqldeveloper.
Then I use a second sqldeveloper and run the following statements as script everything works fine. My first sqldeveloper stops at the breakpoint and I can debug
set serveroutput on;
execute DBMS_DEBUG_JDWP.CONNECT_TCP('myIp',4010);
declare
begin
do_something(2); -- in this function is a breakpoint set
end;
execute DBMS_DEBUG_JDWP.disconnect(' myIp ',4010);
When I try to run the script e.g. in sqlplus I get following stacktrace in my first sqldeveloper console and the listener is closed
java.lang.StringIndexOutOfBoundsException: String index out of range: -2
at java.lang.String.substring(String.java:1911)
at com.sun.tools.jdi.JNITypeParser.nextTypeName(JNITypeParser.java:204)
at com.sun.tools.jdi.JNITypeParser.typeNameList(JNITypeParser.java:140)
at com.sun.tools.jdi.JNITypeParser.typeName(JNITypeParser.java:85)
at com.sun.tools.jdi.TypeImpl.name(TypeImpl.java:44)
at com.sun.tools.jdi.ReferenceTypeImpl.compareTo(ReferenceTypeImpl.java:150)
at com.sun.tools.jdi.ReferenceTypeImpl.compareTo(ReferenceTypeImpl.java:33)
at java.util.TreeMap.put(TreeMap.java:560)
at java.util.TreeSet.add(TreeSet.java:255)
at com.sun.tools.jdi.VirtualMachineImpl.addReferenceType(VirtualMachineImpl.java:785)
at com.sun.tools.jdi.VirtualMachineImpl.referenceType(VirtualMachineImpl.java:901)
at com.sun.tools.jdi.VirtualMachineImpl.retrieveAllClasses1_4(VirtualMachineImpl.java:979)
at com.sun.tools.jdi.VirtualMachineImpl.retrieveAllClasses(VirtualMachineImpl.java:995)
at com.sun.tools.jdi.VirtualMachineImpl.allClasses(VirtualMachineImpl.java:284)
at oracle.jdevimpl.debugger.jdi.DebugJDI.<init>(DebugJDI.java:420)
at oracle.jdevimpl.debugger.jdi.DebugJDIConnectorListen.run(DebugJDIConnectorListen.java:133)
at java.lang.Thread.run(Thread.java:724)
Does anyone have an idea what I'm doing wrong, or what's maybe misconfigured?
System Configuration
Client:
     Windows 7
     SqlDeveloper Version 4.0.0.12 Build MAIN-12.27 - running with jdk1.7.0_25
Database Server:
     Oracle 11.2.0.3.0

Hi
Has someone find an answer to this?
Debugger attempting to connect to remote process at localhost 4000.
...............................Debugger unable to connect to remote process.This is the same message you get when you try to run a debug session under JDeveloper, but with OJVM, not JPDA.
If this is a bug and will be fixed, can the SQL Developer team please make a post?

Not able to start remote debug listener

HI,
I'm using SQL Developer 1.1.0.23.64 and have read this article explaining remote pl/sql debugging.
http://sueharper.blogspot.com/2006/07/remote-debugging-with-sql-developer_13.html
When i try to start the debugger listener in SQL Developer (right click the database connection and choosing "remote debug") it seems like that the SQL Developer tries to connect to a listener instead of start listening. This is what console displays:
Debugger attempting to connect to remote process at LocalHost 4000...............Debugger unable to connect to remote process.
I thought that it should start listening instead of trying to connect to some other listener. What do I do wrong?
When I'm using remote debugging from JDeveloper every thing is fine!
Regards
Jacob

Hi
Has someone find an answer to this?
Debugger attempting to connect to remote process at localhost 4000.
...............................Debugger unable to connect to remote process.This is the same message you get when you try to run a debug session under JDeveloper, but with OJVM, not JPDA.
If this is a bug and will be fixed, can the SQL Developer team please make a post?

How to start listener in sql developer for remote debug

how to start listener in sql developer for remote debug ? Since the new version 1.1.0.23 is different with the old version for remote debug, I don't know how to start the listener on the new version for remote debug.
even follow the user guide below and not work . Experts on sql developer please help me with this.
Remote Debugging
To debug a procedure or function for a connection where the database is on a different host than the one on which you are
running SQL Developer, you can perform remote debugging.
Remote debugging involves many of the steps as for local debugging; however, do the
following before you start the remote debugging: Use an Oracle client such as SQL*Plus to issue the debugger connection command. Whatever
client you use, make sure that the session which issues the debugger connection commands is the same session which executes your PL/SQL
program containing the breakpoints.
For example, if the name of the remote system is remote1, use the following SQL*Plus command to open a
TCP/IP connection to that system and the port for the JDWP session:
EXEC DBMS_DEBUG_JDWP.CONNECT_TCP('remote1', '4000'); The first parameter
is the IP address or host name of the remote system, and the second parameter is the port number on that remote system on which the debugger
is listening.
Right-click the connection for the remote database, select Remote Debug, and complete the information in the Debugger - Attach
to JPDA dialog box. Then, follow the steps that you would for local debugging (for example, see Debugging a PL/SQL Procedure).
Debugger - Attach to JPDA This dialog box is displayed when you right-click a database connection name and select Remote Debug.
Use this
dialog box if you are using the Sun Microsystem's Java Platform Debugger Architecture (JPDA) and you would like the debugger to listen so
that a debuggee can attach to the debugger.
For more information about remote debugging, see Remote Debugging.
Host: Name or IP address of
the remote host on which SQL Developer should listen for the database to connect.
Port: Listening port number on the remote host. You can
choose any valid port number that is not in use by another process.
Timeout: The number of seconds that SQL Developer will wait for the
remote database to make a debugging connection. Don't Show Dialog Box Before Connecting: If this option is checked, this dialog box will not
be displayed before future connections for remote debugging

You're not the only one:
Not able to start remote debug listener
Re: remote debug question at version 1.1.0.23 64

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

How can I enable remote debug in weblogic to use with Rational RSA IDE?

How can I enable the remote debugging technique so that I can work with my IDE.
I use RSA by IBM as the IDE
What should be the changes in the setdomainenv or startweblogic?
I use 10.3
Please help.. ur help is appreciable...

Hi,
I did not make any console adjustments for debugging on my WebLogic 10.3.2.0 - however I am running in development mode on an "adminServer" (an option during the install)
In the console there is a debug setup page - that seems to have no effect for me (I can always debug) - so either it is a combination of development mode and/or the startWeblogic script from the Eclipse plugin.
However, these debug settings are likely for debugging into the server - you only want to debug your own app code right?
On the console page goto
http://localhost:7001/console/console.portal?_nfpb=true&_pageLabel=ServerDebugPage
servers | AdminServer | configuration-debug | expand weblogic
I see...
"Use this page to define debug settings for this server.
Debug settings for this Server
EnableDisableClear Showing 1 to 2 of 2 Previous Next
Debug Scopes and Attributes State
default Disabled
weblogic Disabled
EnableDisableClear Showing 1 to 2 of 2 Previous Next
Try expanding the whole tree and selecting the root to enable everything.
You will see the following
10-Dec-2009 11:53:46 o'clock AM EST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute DebugAbbreviation on weblogic.management.configuration.ServerDebugMBeanImpl@47a32e1b([base_domain]/Servers[AdminServer]/ServerDebug[AdminServer]) has been changed. This may require redeploying or rebooting configured entities>
<10-Dec-2009 11:53:46 o'clock AM EST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server AdminServer. This server must be rebooted in order to consume this change.>
<10-Dec-2009 11:53:46 o'clock AM EST> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=ServerDebugPage.>
When I debug WebLogic 10.3.2.0 from Eclipse 3.5 EE - I see the following in my server startup log which includes the "-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453" you mentioned.
Starting WLS with line:
c:\opt\wls10320\JROCKI~1.5-3\bin\java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms512m -Xmx512m -Dweblogic.Name=AdminServer -Djava.security.policy=C:\opt\wls10320\WLSERV~1.3\server\lib\weblogic.policy -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=C:\opt\wls10320\WLSERV~1.3 -Dwls.home=C:\opt\wls10320\WLSERV~1.3\server -Dweblogic.home=C:\opt\wls10320\WLSERV~1.3\server -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=c:\opt\wls10320\patch_wls1032\profiles\default\sysext_manifest_classpath weblogic.Server
Listening for transport dt_socket at address: 8453
The server process listening on debug portl 8453 ooks like this
Oracle WebLogic Server 11gR1 PatchSet 1 at localhost [Oracle WebLogic Launch Configuration]
     BEA JRockit(R)[localhost:8453]
          Thread [Main Thread] (Running)
          Daemon Thread [Timer-0] (Running)
          Daemon Thread [Timer-1] (Running)
          Daemon Thread [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] (Running)
          Daemon Thread [weblogic.time.TimeEventGenerator] (Running)
          Daemon Thread [JMAPI event thread] (Running)
          Daemon Thread [weblogic.timers.TimerThread] (Running)
          Daemon Thread [[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] (Running)
          Daemon Thread [Thread-7] (Running)
          Daemon Thread [ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'] (Running)
          Daemon Thread [ExecuteThread: '1' for queue: 'weblogic.socket.Muxer'] (Running)
I hit a breakpoint and see
Daemon Thread [[ACTIVE] ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)'] (Suspended (breakpoint at line 56 in ApplicationService))
     ApplicationService_5ptwty_Impl(ApplicationService).insertObjects(List<Cell>) line: 56
     NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]
     NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39
     DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25
     Method.invoke(Object, Object...) line: 597
     AopUtils.invokeJoinpointUsingReflection(Object, Method, Object[]) line: 310
     ReflectiveMethodInvocation.invokeJoinpoint() line: 182
     ReflectiveMethodInvocation.proceed() line: 149
     DelegatingIntroductionInterceptor.doProceed(MethodInvocation) line: 131
     DelegatingIntroductionInterceptor.invoke(MethodInvocation) line: 119
     ReflectiveMethodInvocation.proceed() line: 171
     MethodInvocationVisitorImpl.visit() line: 37
     EnvironmentInterceptorCallbackImpl.callback(MethodInvocationVisitor) line: 55
     EnvironmentInterceptor.invoke(MethodInvocation) line: 50
     ReflectiveMethodInvocation.proceed() line: 171
     ExposeInvocationInterceptor.invoke(MethodInvocation) line: 89
     ReflectiveMethodInvocation.proceed() line: 171
     DelegatingIntroductionInterceptor.doProceed(MethodInvocation) line: 131
     DelegatingIntroductionInterceptor.invoke(MethodInvocation) line: 119
     ReflectiveMethodInvocation.proceed() line: 171
     JdkDynamicAopProxy.invoke(Object, Method, Object[]) line: 204
     $Proxy68.insertObjects(List) line: not available
     ApplicationService_5ptwty_ApplicationServiceLocalImpl.insertObjects(List<Cell>) line: 306
     FrontController.generateGlider(PrintWriter) line: 240
thank you
/michael
http://www.eclipselink.org

How do I connect the debugger for remotely debugging PL/SQL?

Hi everyone,
Remotely debugging PL/SQL from JDeveloper and SQL Developer is something I have tried unsuccessfully to do.
The steps I took were to right-click my connection, select Remote Debug... and specify "4000" for the Port and "n.n.n.n" for the Local address which seems to correctly start the listener. (I used ipconfig to double-check the address.) Then, I run the anonymous block you see below.
begin
dbms_debug_jdwp.connect_tcp( 'n.n.n.n', 4000 );
end;
But, I always get the following error:
Error starting at line 18 in command:
begin
dbms_debug_jdwp.connect_tcp( 'n.n.n.n', 4000 );
end;
Error report:
ORA-30683: failure establishing connection to debugger
ORA-12535: TNS:operation timed out
ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
ORA-06512: at line 2
30683. 00000 - "failure establishing connection to debugger"
*Cause:    An error was indicated when trying to establish a connection
           to a debugger. Usually a TNS error will display along with
           this message to further explain the problem, although this
           TNS error will likely be hidden if you choose to trap the error.
*Action:   Correct the indicated parameter value and try again.
Additionally, my firewall in Windows 7 is disabled, and I work remotely from home via VPN.
The instructions are thatI followed: Sue's Blog... again...: Remote Debugging with SQL Developer.
Any help would be greatly appreciated. Thanks!
James

I found the answer.
Object classes are missing.
The right insert code is down but I have a new question.
-How can I assign Resource acces to user in PL/SQL?
Right insert code:
declare
vn_retval pls_integer;
emp_session dbms_ldap.session;
emp_dn varchar2(256);
emp_array dbms_ldap.mod_array;
emp_vals dbms_ldap.string_collection ;
vv_ldap_host varchar2(256);
vv_ldap_port varchar2(256);
vv_ldap_user varchar2(256);
vv_ldap_passwd varchar2(256);
vv_ldap_base varchar2(256);
begin
vn_retval := -1;
vv_ldap_host := 'XXXXXXX';
vv_ldap_port := '389');
vv_ldap_user := 'LDAP_USER';
vv_ldap_passwd:= 'LDAP_PASSWD';
vv_ldap_base := 'LDAP_BASE';
dbms_ldap.use_exception := true;
-- Initialize ldap library and get session handle.
emp_session := dbms_ldap.init(vv_ldap_host, vv_ldap_port);
-- Bind to the directory
vn_retval := dbms_ldap.simple_bind_s(emp_session, vv_ldap_user, vv_ldap_passwd);
-- Process New Entry in the database
-- Create and setup attribute array for the New entry
emp_array := dbms_ldap.create_mod_array(4);
emp_vals(1) := 'NAME';
dbms_ldap.populate_mod_array(emp_array, dbms_ldap.mod_add, 'cn', emp_vals);
emp_vals(1) := 'NAME';
dbms_ldap.populate_mod_array(emp_array, dbms_ldap.mod_add, 'sn', emp_vals);
emp_vals(1) := 'top';
emp_vals(2) := 'person';
emp_vals(3) := 'organizationalPerson';
emp_vals(4) := 'orcluserv2';
emp_vals(5) := 'orcluser';
emp_vals(6) := 'inetOrgPerson';
dbms_ldap.populate_mod_array(emp_array, dbms_ldap.mod_add, 'objectclass', emp_vals);
emp_vals.delete;
emp_vals(1) := 'NAME' || '1';
dbms_ldap.populate_mod_array(emp_array, dbms_ldap.mod_add, 'userpassword', emp_vals);
-- DN for Entry to be Added under 'ldap_base'
emp_dn := 'cn=' || 'NAME' || ', ' || vv_ldap_base ;
-- Add new Entry to ldap directory
vn_retval := dbms_ldap.add_s(emp_session, emp_dn, emp_array);
-- Free attribute array (emp_array)
dbms_ldap.free_mod_array(emp_array);
-- Unbind from ldap directory
vn_retval := dbms_ldap.unbind_s(emp_session);
end;

Remote debug on Eclipse

Hi,all
I'm using eclipse 3.1.1 to debug a servlet deployed on sjsas7 2004Q2, the os is windows. The only connect type on eclipse is Standard(Socket Attach), so I set the debug options in sjsas is:-Xdebug -Dnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,address=1234,suspend=n,
When I use debug in eclipse, it connect to sjsas successfully.
But there's and appservd.exe application error, if I set a breakpoint in eclipse and the sjsas restarts.
I appreciate anyone tell me how to solve this problem or how can I use shared memoy type in eclipse remote debug?
Thanks alot

Hi,
I am also facing this problem in debug mode in Eclipse 3.1.1 .
We are trying to run a huge JNI call to an exe which makes use of
win32 and mfc dlls . please help . is it possible to make jni calls from java program in eclipse . am not getting any exceptions but the .exe file is not running . any help would be great ...
email : [email protected]
FATAL ERROR in native method: No transports initialized
Invalid listen port number: localhost:2429
Transport dt_socket failed to initialize, rc = -1.

Weblogic 8.1 Remote Debugging Setup

I am requesting help on a problem I am encountering using remote debugging with eclipse and Weblogic 8.1.2. I have successfully used remote debugging in the past with other application servers, but I have been unsuccessful with Weblogic 8.1.
I have set the remote debugging options both on the weblogic start script as well as configured eclipse to connect to the port that was defined in the startup script (See Below). When I start the remote debugger within eclipse and it seems to connect properly. Once I set a break point or remove a break point, weblogic generates a "Transport error, error code = -1" and stops the debugger with in Eclipse.
At this point I am at a loss of what is causing this error. I would appreciate any help on this issue.
Operating System: WindowsXP Pro
Weblogic Version: 8.1.2
Eclipse 3.2
JDK 1.4.2
JAVA_OPTS: =-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=7777,server=y,suspend=n
Thanks!
Rafael Salazar

Address 7001 does't seem to be good idea for debuging, it is weblogic default address.
try 3999.
"Arsel" <[email protected]> wrote:
>
Hi There,
I started weblogic server 8.1 with the follwing option -Xdebug -Xnoagent
-Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=7001
Weblogic started successfully but when I tried to attached the java process
from
my IDE I got the error 'Target server failed to handshake' and in the
weblogic
console I got the following error.
<22-Aug-2003 10:09:52 o'clock AM EDT> <Error> <HTTP> <BEA-101083> <Connection
failure.
java.io.IOException: A complete message could not be read on socket:
'weblogic.servlet.internal.MuxableSocketHTTP@1871db
1 - idle timeout: '60000' ms, socket timeout: '5000' ms', in the configured
timeout
period of '60' secs
at weblogic.socket.SocketMuxer$TimeoutTrigger.trigger(SocketMuxer.java:734)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:49)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
Does weblogic 8.1 support JPDA? Any suggesstion is higly appreciated.
Thanks.
Arsel

Remote Debugging Weblogic 92 application using Eclipse 3.4

Hi,
1. I have the below debug options in the startweblogic script.
set JAVA_OPTIONS=-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,address=javadebug,suspend=n
2. I have configured remote debugging in Eclipse. Connection type - Standard Socket (attach), host =localhost, port 7001. 7001 is the listen port that I have specified in config.xml.
3. When I run weblogic, I see the message listening for transport dt_socket address. Since address=javadebug, each time the dt_socket address is different.
4. In Eclipse IDE, the debug prespective indicates the server has started. But when I click on the debug buttin in the Debug configuration dialog, I get the error below
Failed to connect to remote VM. Connection timed out.
org.eclipse.jdi.TimeoutException
Note: Another thread in this forum mentions using the same port that is specified in the java_options but that did not work either. Any ideas what might be wrong?
Thanks.
RS.

I think that value of "javadebug" is only used for shared memory transport, not socket transport. You have to choose a port that isn't being used by anything else. The value 8453 is a typical default value for this. Specify that instead of "javadebug", and use 8453 in your connection from Eclipse.

How do I disable remote debugging in JDeveloper??

I am having a problem disabling the remote debugging feature inside JDeveloper 9i. I currently have a workspace in which I has set up a remotely debuggable project and another "normal" project which contains the client application that accesses my remote application. When I start the remote application, I am able to attach the remote debugger inside JDeveloper and it works just fine. However, when I attempt to debug my local project, it starts with the following JVM parameters :
java -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,address=1552
and fails to start since it cannot attach to a remote process. I have double-checked the project settings and the remote debugging checkbox is NOT select for the local project. I have even resorted to restarting JDeveloper, but that failed to resolve the problem.
Does anybody have any suggestions as to how to fix this problem?

Hi David,
Some things concern me about the java command you show in your post:
1. On Windows, JDeveloper should be starting javaw, not java. In your post, you show a java command. Is it really java or is it javaw?
2. JDeveloper should be specifying which JVM to use. In your post, you show a java command where there is no JVM specified (there is no -ojvm or -hotspot). Check your project settings - on the Libraries panel, what J2SE (JDK) are you using? on the Runner panel, what Virtual Machine is selected?
Other than that, the command you show in your post (the command that JDev launches when you try to debug your local project) contains (mostly) the correct command options for local debugging with a JVM which supports JPDA debugging (for example, classic or hotspot).
Let me explain the command options:
java -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,address=1552-Xdebug Enables debugging.
-Xnoagent Disables old debugging agent (also called sun.tools.debug).
-Djava.compiler=NONE Disables the JIT compiler.
-Xrunjdwp Loads the JPDA JDWP library.
:transport=dt_socket Use sockets for communicating with the debugger.
,server=y Listen for a debugger to attach.
,address=1552 Use port 1552.
JDev will use the above command options when you do local debugging with a JVM other than OJVM. (Note that -Xnoagent and -Djava.compiler=NONE are not required for HotSpot, but are accepted and ignored.)
The command that you show is not trying to connect to anything.
When JDev does remote debugging, it does not start the java process at all.
I think there is some other reason why your program does not start up. What other messages are displayed in the Log Window? Do you see messages like "Debugger attempting to connect to local process." or "Debugger connected to local process." or "Debugger unable to connect to local process."?
-Liz

Cannot remote debug from JDev 10.1.3 on AS 10.1.2 running hotspot

Hi,
I've set up an embedded OC4J instance in an application server as described in the help topic, "Remote Debugging in OC4J" (with a few changes, such as the fact that I added startup options using the OC4J instance Admin page of EM, rather than at the command line (since the instance is embedded in a full AS). I followed the directions specifically for HotSpot, because that's the JVM the instance was set up to use, and I can't change it (I know OJVM enables lots more features, but that's the situation I'm in).
I've also configured my project for remote debugging, ensuring the host name and port matches, and trying both "Attach to JDPA" and "Attach to OJVM" (these being the only two options, except for starting a listener, which I don't think will help with a web application).
When I try to debug, though, I get:
Debugger unable to connect to remote process.
Should I be doing something differently?
Thanks much,
Avrom

I had the delete key quit working after accidentally pressing a key sequent that included the delete key. I don't know what keys were involved, but the delete key from that point on did nothing.
I am running JDeveloper 10.1.3.0.4 on Window XP.
To resolve the problem, I set the keyboard Accelerators back to 'Default' in JDeveloper.
I selected... Tools->Preferences->Accelerators
then click on 'Load preset' then I chose 'Default'
You may need to select something other than default for your platform, but that did the trick for me.

Advantages of using Oracle JVM over JPDA for Remote Debugging?

What are the "additional features" that the documentation hints at when using the Oracle JVM for remote debugging vs. the JPDA protocoL? Can a member of the JDEV briefly address this? What exactly am I losing when using JPDA?

I am not getting anywhere with 'NCOMPing' the stuff. Attempts to NCOMP keeps erroring out . The first of the errors is
'Error while determining classes contained in jsch-1.29_minimalClassListAndTCD
mper.java
Exception oracle.aurora.sqljdecl.ParseException: Encountered "-" at line 14
column 18.
Was expecting one of:
"extends" ...
"implements" ...
The following operations failed
jsch-0.1.29_minimalClassListAndTCDumper.java: creation
exiting : Failures occurred during processing
Kuassi, I have looked at a few of your posts where you make mention of a file titled 'Settings_os.properties'. I see no such file in my Oracle installation. What am I missing here ?

WD Java Remote Debug problem: Release Process from debugging

Hi Community,
when I used to debug Web Dynpro Java from the SAP Developer Studio (eclipse) to a remote host (Portal AS NW Java), it works fine for the first run. After disconnecting the remote debug session (server0), I changed the coding and try to debug again with the effect that the old coding is still used from the server process (server0) even though the parameter "Create and Deploy archive" is set (enabled) in the debug configuration. Furthermore the funktionality of "Relase process from debugging" option in the J2EE Engine dosn't react / work.
I think that the debug session is still running and the Developer Studio is not able to send any "Kill" statement to the server process for ending this session.
I tried following:
A. Rebuild Project and Deploy the archive on the "normal" way
B. Reopen the Developer Studio itself
C. Start the Project in debugmode again and chose the option "Terminate All"
...all without any success.
The only way is to restart the whole server process server0 again with the same trouble after the first debug.
Did any of you have a clue or experience to clear or kill the debugsession from the process so that next debugsessions can be started, please reply.
Thanks
Used Basic Manuell
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/849170e3-0601-0010-d59e-ddfce735fac5

So, I'm having the same issue, but it's like I'm chasing down a port. The first time I got these error messages
Connecting to the database DEV.
Executing PL/SQL: ALTER SESSION SET PLSQL_DEBUG=TRUE
Executing PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP( '555.12.18.288', '5950' )
ORA-30683: failure establishing connection to debugger
ORA-12535: TNS:operation timed out
ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
ORA-06512: at line 1
Process exited.
Disconnecting from the database DEV.Our network staff found a bunch of other denials in the firewall logs
/5185
/5200
/5236
/5815
/5950 Now that they've those allowed, I tried to start debug again, and this time I got
Connecting to the database DEV.
Executing PL/SQL: ALTER SESSION SET PLSQL_DEBUG=TRUE
Executing PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP('555.12.18.288', '6266' )
ORA-30683: failure establishing connection to debugger
ORA-12535: TNS:operation timed out
ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
ORA-06512: at line 1
Process exited.
Disconnecting from the database DEV.What gives? Do I just keep trying until I get all of the ports allowed?
Thanks,
---=Chuck

How to use Remote Debugging in JDeveloper 3.1 ?

I am trying to use the Remote Debugging option with EJBs in JDeveloper 3.1 with Oracle8i 8.1.6.
I checking all steps the online walkthrough for Remote Debugging EJB in 8i and it didn't work.
I'm using Oracle8i EJB/CORBA debug option in project properties, but it does not stop in my EJB's break points.
I tried deploying the EJB again ( with break points) and again it didn't work.
The error message I got in the trace file is:
Errors in file D:\Oracle\admin\SCT\udump\sctS000.TRC:
ORA-29516: Aurora assertion failure: Java thread deadlock detected
Could someone please tell me how to use it?
null

Which platform is the database running on ??
Other things you should check -
when debugging the EJB, JDev
3.1 looks through your IIOP connections to find the one to use.
Make sure that the IIOP connection that JDev is using for the debugging matches the IIOP connection that the EJB client application is using.
raghu
null

Remote debug listening socket failure

Similar Messages

Maybe you are looking for