6 Replies Latest reply: May 17, 2011 6:45 AM by John Stegeman RSS

    JDeveloper & Debug : FATAL ERROR

    4172
      Hello,
      when i try to debug any project in JDeveloper, i got the following error:
      *****************
      FATAL ERROR in native method: No transports initialized
      Transport dt_socket failed to initialize, rc = 509.
      Process exited with exit code 1.
      Debugger unable to connect to local process.
      *****************

      I allready reinstall JDeveloper in JDK, but no luck. Please, help. Thank you.
        • 1. Re: JDeveloper & Debug : FATAL ERROR
          dvohra21
          No transports initialized
          Transport dt_socket failed to initialize


          Which application server is aset for remote debugging?

          In the application server is the debug mode set?
          -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=4999,server=y,suspend=n
          • 2. Re: JDeveloper & Debug : FATAL ERROR
            dvohra21
            For local embedded OC4J server please refer to
            http://helponline.oracle.com/jdeveloper/help/state/content/vtTopicId./navSetId.jdeveloper/vtTopicFile.jdeveloper%7Ctuning%7Crem_p_main_oc4j%7Ehtml/navId.4/
            • 3. Re: JDeveloper & Debug : FATAL ERROR
              4172
              Deepak,
              thank you for your help. One of Oracle guys from Slovenia allready help me. The problem was, that file "dt_socket.dll" (\jdk14\jre\bin' directory) must be in the system path. Thank you again.
              • 4. Re: JDeveloper & Debug : FATAL ERROR
                580521
                If you have jdk1.5\jre\bin on your path when you start JDeveloper on Windows, you will not be able to use the debugger with JDK1. (The default JDK with JDeveloper 10.1.2) with the HotSpot JVMs (hotspot, client, or server). Attempting to debug with JDK1.4 with a HotSpot JVM will cause the following error to appear in the log window:

                FATAL ERROR in native method: No transports initialized Transport dt_socket failed to initialize, rc = 509.

                The error is caused by the debuggee process looking for the dt_socket.dll and finding the JDK1.5 version of the dll from the jdk1.5\jre\bin directory on the path instead of the JDK1.4 version of the DLL The error will not occur when using the debugger with OJVM because OJVM does not use the dt_socket.dll.

                Try either of these workarounds to avoid this problem:

                Remove jdk1.5\jre\bin from the path before starting JDeveloper.

                Use OJVM when debugging. This is specified in the Project Properties dialog box, on the Runner panel.
                • 5. Re: JDeveloper & Debug : FATAL ERROR
                  akshay
                  hello,

                  i am also getting the erro while executing project on jdeveloper using ejb and jpa entities the error is as follows :

                  [EclipseLink/JPA Client] Adding Java options: -javaagent:C:\middleware\jdeveloper\..\modules\org.eclipse.persistence_1.0.0.0_2-1.jar
                  c:\middleware\jdk160_21\bin\javaw.exe -client -classpath C:\Users\eaurgta\Documents\JDeveloper\mywork\cab_ejb_jpa_app\.adf;C:\Users\eaurgta\Documents\JDeveloper\mywork\cab_ejb_jpa_app\cabejbmodel\classes;C:\middleware\modules\com.oracle.toplink_1.0.0.0_11-1-1-4-0.jar;C:\middleware\modules\org.eclipse.persistence_1.0.0.0_2-1.jar;C:\middleware\modules\com.bea.core.antlr.runtime_2.7.7.jar;C:\middleware\oracle_common\modules\oracle.toplink_11.1.1\javax.persistence_2.0_preview.jar;C:\middleware\oracle_common\modules\oracle.xdk_11.1.0\xmlparserv2.jar;C:\middleware\oracle_common\modules\oracle.xdk_11.1.0\xml.jar;C:\middleware\modules\javax.jsf_1.1.0.0_1-2.jar;C:\middleware\modules\javax.ejb_3.0.1.jar;C:\middleware\modules\javax.enterprise.deploy_1.2.jar;C:\middleware\modules\javax.interceptor_1.0.jar;C:\middleware\modules\javax.jms_1.1.1.jar;C:\middleware\modules\javax.jsp_1.2.0.0_2-1.jar;C:\middleware\modules\javax.jws_2.0.jar;C:\middleware\modules\javax.activation_1.1.0.0_1-1.jar;C:\middleware\modules\javax.mail_1.1.0.0_1-4-1.jar;C:\middleware\modules\javax.xml.soap_1.3.1.0.jar;C:\middleware\modules\javax.xml.rpc_1.2.1.jar;C:\middleware\modules\javax.xml.ws_2.1.1.jar;C:\middleware\modules\javax.management.j2ee_1.0.jar;C:\middleware\modules\javax.resource_1.5.1.jar;C:\middleware\modules\javax.servlet_1.0.0.0_2-5.jar;C:\middleware\modules\javax.transaction_1.0.0.0_1-1.jar;C:\middleware\modules\javax.xml.stream_1.1.1.0.jar;C:\middleware\modules\javax.security.jacc_1.0.0.0_1-1.jar;C:\middleware\modules\javax.xml.registry_1.0.0.0_1-0.jar;C:\middleware\modules\javax.persistence_1.0.0.0_1-0-2.jar;C:\middleware\wlserver_10.3\server\lib\weblogic.jar -Djavax.net.ssl.trustStore=C:\middleware\wlserver_10.3\server\lib\DemoTrust.jks -javaagent:C:\middleware\jdeveloper\..\modules\org.eclipse.persistence_1.0.0.0_2-1.jar oracle.cab_facadeClient
                  java.lang.reflect.InvocationTargetException
                       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                       at java.lang.reflect.Method.invoke(Method.java:597)
                       at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:323)
                       at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:338)
                  Caused by: java.lang.reflect.InvocationTargetException
                       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                       at java.lang.reflect.Method.invoke(Method.java:597)
                       at org.eclipse.persistence.internal.jpa.deployment.JavaSECMPInitializerAgent.initializeFromAgent(JavaSECMPInitializerAgent.java:45)
                       at org.eclipse.persistence.internal.jpa.deployment.JavaSECMPInitializerAgent.premain(JavaSECMPInitializerAgent.java:38)
                       ... 6 more
                  Caused by: javax.persistence.PersistenceException: Exception [EclipseLink-28018] (Eclipse Persistence Services - 2.1.2.v20101206-r8635): org.eclipse.persistence.exceptions.EntityManagerSetupException
                  Exception Description: Predeployment of PersistenceUnit [cabejbmodel] failed.
                  Internal Exception: Exception [EclipseLink-7161] (Eclipse Persistence Services - 2.1.2.v20101206-r8635): org.eclipse.persistence.exceptions.ValidationException
                  Exception Description: Entity class [class oracle.T76] has no primary key specified. It should define either an @Id, @EmbeddedId or an @IdClass. If you have defined PK using any of these annotations then make sure that you do not have mixed access-type (both fields and properties annotated) in your entity class hierarchy.
                       at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.predeploy(EntityManagerSetupImpl.java:1014)
                       at org.eclipse.persistence.internal.jpa.deployment.JPAInitializer.callPredeploy(JPAInitializer.java:88)
                       at org.eclipse.persistence.internal.jpa.deployment.JavaSECMPInitializer.initPersistenceUnits(JavaSECMPInitializer.java:256)
                       at org.eclipse.persistence.internal.jpa.deployment.JavaSECMPInitializer.initialize(JavaSECMPInitializer.java:216)
                       at org.eclipse.persistence.internal.jpa.deployment.JavaSECMPInitializer.initializeFromAgent(JavaSECMPInitializer.java:159)
                       ... 12 more
                  Caused by: Exception [EclipseLink-28018] (Eclipse Persistence Services - 2.1.2.v20101206-r8635): org.eclipse.persistence.exceptions.EntityManagerSetupException
                  Exception Description: Predeployment of PersistenceUnit [cabejbmodel] failed.
                  Internal Exception: Exception [EclipseLink-7161] (Eclipse Persistence Services - 2.1.2.v20101206-r8635): org.eclipse.persistence.exceptions.ValidationException
                  Exception Description: Entity class [class oracle.T76] has no primary key specified. It should define either an @Id, @EmbeddedId or an @IdClass. If you have defined PK using any of these annotations then make sure that you do not have mixed access-type (both fields and properties annotated) in your entity class hierarchy.
                       at org.eclipse.persistence.exceptions.EntityManagerSetupException.predeployFailed(EntityManagerSetupException.java:210)
                       ... 17 more
                  Caused by: Exception [EclipseLink-7161] (Eclipse Persistence Services - 2.1.2.v20101206-r8635): org.eclipse.persistence.exceptions.ValidationException
                  Exception Description: Entity class [class oracle.T76] has no primary key specified. It should define either an @Id, @EmbeddedId or an @IdClass. If you have defined PK using any of these annotations then make sure that you do not have mixed access-type (both fields and properties annotated) in your entity class hierarchy.
                       at org.eclipse.persistence.exceptions.ValidationException.noPrimaryKeyAnnotationsFound(ValidationException.java:1374)
                       at org.eclipse.persistence.internal.jpa.metadata.accessors.classes.EntityAccessor.validatePrimaryKey(EntityAccessor.java:1366)
                       at org.eclipse.persistence.internal.jpa.metadata.accessors.classes.EntityAccessor.processAccessors(EntityAccessor.java:885)
                       at org.eclipse.persistence.internal.jpa.metadata.accessors.classes.EntityAccessor.process(EntityAccessor.java:691)
                       at org.eclipse.persistence.internal.jpa.metadata.MetadataProject.processStage2(MetadataProject.java:1531)
                       at org.eclipse.persistence.internal.jpa.metadata.MetadataProcessor.processORMMetadata(MetadataProcessor.java:474)
                       at org.eclipse.persistence.internal.jpa.deployment.PersistenceUnitProcessor.processORMetadata(PersistenceUnitProcessor.java:441)
                       at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.predeploy(EntityManagerSetupImpl.java:968)
                       ... 16 more
                  FATAL ERROR in native method: processing of -javaagent failed
                  Exception in thread "main" Process exited with exit code 1.



                  thanks and regards
                  ankur
                  • 6. Re: JDeveloper & Debug : FATAL ERROR
                    John Stegeman
                    akshay,

                    Your issue has nothing whatsoever to do with the original post, which was about remote debugging.

                    If you were to thoroughly read your stack trace, you'd find the source of your problem:
                    Exception Description: Entity class [class oracle.T76] has no primary key specified. It should define either an @Id, @EmbeddedId or an @IdClass. If you have defined PK using any of these annotations then make sure that you do not have mixed access-type (both fields and properties annotated) in your entity class hierarchy.
                    John