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

Similar Messages

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.

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

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

Remote Control and Remote View Problem

Hi,
I work at a High School running Netware 6.0 SP5 and Zen works 4.01 ir7.
Remote Control and Remote View works great but I noticed one problem.
We have a logo of the school that is forced down on to the desktop when a
user logs in through group policies. This logo works perfect for the
desktop wall paper and loads every time a user logs in.
When I Remote Control or Remote View a computer the users desktop wall
paper turns from the logo being forced down through group policies to the
desktop to a blue desktop wall paper.
I would prefer the desktop wall paper staying the schools logo when I
Remote Control or Remote View because if the desktop wall paper changes to
the blue color I mentioned above when I Remote Control or Remote View the
users computer, they will know that someone is taking over their computer
which sometimes we dont want them knowing.
We have Windows 98SE computer running Novell Client 3.4 and we have some
computers running Windows XP Professional SP1 and Windows XP Professional
SP2 both running Novell Client 4.91 SP2.
The Remote Control and Remote View problem of the desktop wall paper
changing on the users computer occurs on all operating systems mentioned
above.
Is there a solution to my above problem? When Remote Controlling and
Remote Viewing someone's computer I don't want the desktop wall paper to
change.
Thanks!

Bpilon,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Do a search of our knowledgebase at http://support.novell.com/search/kb_index.jsp
- Check all of the other support tools and options available at
http://support.novell.com.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://support.novell.com/forums)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://support.novell.com/forums/faq_general.html
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

*** 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.

Remote JDBC Problem with Oracle BPM Studio

Hi all, i am facing the Remote JDBC Problem with Oracle BPM Studio.
When i configure a Remote JDBC Connection for SQL in BPM Studio, it prompt me an error.
The SQL Connection is configured as following :
External Resource:
Name : MyDS
Type : SQL Database
Supported Types : Remote JDBC
Details:
Database Type : BPM's Oracle Driver Version:10, 11
J2EE : WLS
Lookup Name : MyAppDS
Configuration for "WLS"
Name : WLS
Type : J2EE Application Server
Supported Types : GENERIC_J2EE
Details:
Initial Context Factory : weblogic.jndi.WLInitialContextFactory
URL : t3://localhost:7001
But, when i try to connect to the Database by using this configuration, I will get an Exception.
An exception occurred while getting a resource from a connector.
Detail:The connector [[ MyDS : SQL : REMOTE_JDBC ]] caused an exception when getting a resource.
Caused by: An exception occurred while getting a resource from a connector.
Detail:The connector [[ WLS : J2EE : J2EE ]] caused an exception when getting a resource.
Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [[ Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory ]]
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
     at javax.naming.InitialContext.init(InitialContext.java:223)
     at javax.naming.InitialContext.<init>(InitialContext.java:197)
     at fuego.jndi.FaultTolerantContext.createContext(FaultTolerantContext.java:726)
     at fuego.jndi.FaultTolerantContext.<init>(FaultTolerantContext.java:79)
     at fuego.connector.impl.GenericJ2EEConnector.createInitialContext(GenericJ2EEConnector.java:177)
     at fuego.connector.impl.GenericJ2EEConnector.createStandaloneContext(GenericJ2EEConnector.java:98)
     at fuego.connector.impl.BaseJ2EEConnector.getResource(BaseJ2EEConnector.java:92)
     at fuego.connector.impl.BaseJ2EEConnector.getResource(BaseJ2EEConnector.java:76)
     at fuego.connector.J2EEHelper.getReadOnlyContext(J2EEHelper.java:86)
     ... 12 more
Edited by: user2262377 on Jun 22, 2009 4:01 PM

I guess the weblogic.jar is not included in the studio.
So, i added weblogic.jar (Weblogic 10.3) and wlclient.jar (Weblogic 10.3)
It is working in my simple java code. But, still not working in BPM Studio.
The error logs:
An exception occurred while getting a resource from a connector.
Detail:The connector [OFT_APP_DS:SQL:REMOTE_JDBC] caused an exception when getting a resource.
Caused by: java.lang.Object cannot be cast to java.io.Serializable
fuego.connector.ConnectorException: An exception occurred while getting a resource from a connector.
Detail:The connector [OFT_APP_DS:SQL:REMOTE_JDBC] caused an exception when getting a resource.
     at fuego.connector.ConnectorException.exceptionOnGetResource(ConnectorException.java:88)
     at fuego.connector.JDBCHelper.getReadOnlyConnection(JDBCHelper.java:93)
     at fuego.sqlintrospector.BrowserPanel.connect(BrowserPanel.java:395)
     at fuego.sqlintrospector.BrowserPanel.populateTree(BrowserPanel.java:200)
     at fuego.ui.wizards.ui.CheckTreeBrowser$1.construct(CheckTreeBrowser.java:63)
     at fuego.ui.SwingWorker$2.run(SwingWorker.java:39)
     at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.ClassCastException: java.lang.Object cannot be cast to java.io.Serializable
     at weblogic.iiop.IIOPOutputStream.writeAny(IIOPOutputStream.java:1588)
     at weblogic.iiop.IIOPOutputStream.writeObject(IIOPOutputStream.java:2231)
     at weblogic.utils.io.ObjectStreamClass.writeFields(ObjectStreamClass.java:413)
     at weblogic.corba.utils.ValueHandlerImpl.writeValueData(ValueHandlerImpl.java:235)
     at weblogic.corba.utils.ValueHandlerImpl.writeValueData(ValueHandlerImpl.java:225)
     at weblogic.corba.utils.ValueHandlerImpl.writeValue(ValueHandlerImpl.java:182)
     at weblogic.iiop.IIOPOutputStream.write_value(IIOPOutputStream.java:1963)
     at weblogic.iiop.IIOPOutputStream.write_value(IIOPOutputStream.java:2001)
     at weblogic.iiop.IIOPOutputStream.writeObject(IIOPOutputStream.java:2266)
     at weblogic.jdbc.common.internal.RmiDataSource_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
     at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
     at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

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.

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

OS X Lion and Apple remote control problem

After installing OS X Lion my apple remote control no longer works properly. The menu wont come up on the screen, but it plays music if you press the buttons, but you are riding blind, can anyone help on this one?

It's not a problem with the remote, the problem is that Lion no longer has FrontRow.

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.

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 - J2EE Deployment Problem

I'm not sure if I should be posting this here or in the J2EE forum but here is my problem. Whenever I try to deploy a web application to our J2EE server I get the following error.
Invoking Oracle9iAS admin tool...
D:\jdk1.3.1\jre\bin\javaw.exe -jar D:\jdev9i_902\j2ee\home\admin.jar ormi://some.remote.host:23791/ admin **** -deploy -file D:\jdev9i_902\jdev\mywork\JSPTest\HW\HW.ear -deploymentName HW
Communication error: Disconnected: Connection reset by peer: JVM_recv in socket input stream read
Exit status of Oracle9iAS admin tool (-deploy): 0
-If i try to deploy a war file I get this slightly different error.
D:\jdk1.3.1\jre\bin\javaw.exe -Xmx128m -jar D:\jdev9i_902\j2ee\home\admin.jar ormi://some.remote.host:23791/ admin **** -deploy -file D:\jdev9i_902\jdev\mywork\JSPTest\Project1\webapp1.ear -deploymentName webapp1
Communication error: Disconnected: Connection reset by peer: JVM_recv in socket input stream read
Exit status of Oracle9iAS admin tool (-deploy): 0
D:\jdk1.3.1\jre\bin\javaw.exe -jar D:\jdev9i_902\j2ee\home\admin.jar ormi://some.remote.host:23791/ admin **** -bindWebApp webapp1 webapp1 http-web-site /JSPTest-Project1-context-root
Error: com.evermind.server.rmi.OrionRemoteException: Disconnected: Connection reset by peer: JVM_recv in socket input stream read
Exit status of Oracle9iAS admin tool (-bindWebApp): 1
Here is what I do to run our J2EE server.
java -Xmx268435456 -jar $j2ee_home/orion.jar
Oracle9iAS (1.0.2.2.1) Containers for J2EE initialized
I'm running JDev 9.0.2.829
I have confirmed that the J2EE server is listening on port 23791 and I can browse to it on port 8888. Any help would be appreciated.
-Eric Dalquist

See Infrastructure Serrver is down and Re: Lov values filtered by the value selected in other LOV for related discussions.
Here is a cut-and-paste of the important part:
When JDeveloper deploys to a remote OC4J, JDeveloper must use client-side classes to communicate with the server-side administrative objects via RMI. Since communication over RMI uses object serialization to send object instances across the wire, if there is a difference in version in the client-side objects and the server-side objects, there are likely to be deploy-time problems. The incompatibility would be due to implementation decisions made by the OC4J development team.
By default, JDeveloper uses the client-side OC4J classes that ship with JDeveloper. However, if you need to deploy to a different version of OC4J than what ships with JDeveloper, you can tell JDeveloper to use a different set of client-side classes when defining an OC4J connection in the JDeveloper connection manager. On step 3 of the Connection Wizard, there is a field labeled "Local Directory Where admin.jar for Oracle9iAS is Installed". Point that to the OC4J 1.0.2.2 directory containing admin.jar, and you should then be able to deploy from JDev 9i (9.0.2) production to OC4J 1.0.2.2.
There are a few other less common causes for hanging at deploy-time. Let's say you've specified a target server URL of "ormi://myserver".
1) Try specifying the full host name instead of the abbreviated name -- works around problems with hostname resolution.
2) Try specifying the IP address of the target server instead of the hostname -- works around problems with DNS lookups.
3) Try specifying "http:ormi://myserver" as the URL instead -- works around problems with a proxy server that is between the JDeveloper machine and the server (by using HTTP tunnelling).
Hope that helps.

Jdeveloper debugger problem

Hi,
I have JDeveloper 9.0.3.1 and jdk1.4 and I am having problems while debugging. Does the Jdev debugger execute methods ?
ex:
public class TesteDebug
public TesteDebug()
System.out.println("Value: "+getValue());
public String getValue()
return "3";
public static void main(String[] args)
TesteDebug testeDebug = new TesteDebug();
when i put a breakpoint on line "System.out.pri..." and select just the method call "getValue()", nothing works: inspect, watch, ..... Any ideas ?
Thank you.
Albert

Hi,
I have JDeveloper 9.0.3.1 and jdk1.4 and I am having problems while debugging. Does the Jdev debugger execute methods ?
ex:
public class TesteDebug
public TesteDebug()
System.out.println("Value: "+getValue());
public String getValue()
return "3";
public static void main(String[] args)
TesteDebug testeDebug = new TesteDebug();
when i put a breakpoint on line "System.out.pri..." and select just the method call "getValue()", nothing works: inspect, watch, ..... Any ideas ?
Thank you.
Albert

Jdev remote debugger problem

Similar Messages

Maybe you are looking for