JDeveloper : A fatal error has been detected by the Java Runtime Environment:

Hi,

I have faced below mentioned issue while debugging the application in JDeveloper 12.1.3.


#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000005a7763ea, pid=8676, tid=9608
#
# JRE version: Java(TM) SE Runtime Environment (7.0_51-b13) (build 1.7.0_51-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.51-b03 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# V  [jvm.dll+0x1163ea]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\kmatada\AppData\Roaming\JDeveloper\system12.1.3.0.41.140521.1008\DefaultDomain\hs_err_pid8676.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
#
Debugger connection to debuggee process has been lost.
[04:52:05 PM] [IntegratedWebLogicServer is shutting down.  All applications currently running will be terminated and undeployed.]
[Application termination requested.  Undeploying application RmsProcurement.]
Stopping Derby server...
[04:52:11 PM] [J2EE Deployment SPI:260010]Unable to connect to "t3://localhost:7101" as user, "weblogic". Error received: t3://localhost:7101: Destination 127.0.0.1, 7101 unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination
#### There was an error undeploying application RmsProcurement from IntegratedWebLogicServer.[04:52:11 PM] [J2EE Deployment SPI:260010]Unable to connect to "t3://localhost:7101" as user, "weblogic". Error received: t3://localhost:7101: Destination 127.0.0.1, 7101 unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination

[04:52:11 PM] [J2EE Deployment SPI:260010]Unable to connect to "t3://localhost:7101" as user, "weblogic". Error received: t3://localhost:7101: Destination 127.0.0.1, 7101 unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination
[04:52:11 PM] t3://localhost:7101: Destination 127.0.0.1, 7101 unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination
[04:52:11 PM] t3://localhost:7101: Destination 127.0.0.1, 7101 unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination
[04:52:11 PM] t3://localhost:7101: Destination 127.0.0.1, 7101 unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination
[04:52:11 PM] Destination 127.0.0.1, 7101 unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination
[Application RmsProcurement terminated]
[Terminating IntegratedWebLogicServer.]
Derby server stopped.




Solution: I could not get proper solution. I have just deleted my Jdev system folder and it started working. If any one know alternative solution or reason for this issue, please let me know. 

Caused by: java.lang.ClassNotFoundException: sqlj.runtime.ref.DefaultContext

Caused by: java.lang.ClassNotFoundException: sqlj.runtime.ref.DefaultContext

Solution: Just edit the startWeblogic.cmd file from JDev system folder and add the runtime12.jar

set CLASSPATH=%SAVE_CLASSPATH%;C:\Oracle\Middleware\jdeveloper\sqlj\lib\runtime12.jar;

Issue with ‘Set Source Order’ in VO wizard - ADF

Problem statement: 

I had VO with few Transient Attributes. These attribute values needs be populated based on calling DB package call. 

I already had Java wrapper class contains logic to call DB packages

So I  override my createInstanceFromResultSet method in VO Impl to populate transient attributes.

My page is search page, so created view criteria on VO to create standard query panel.

At later point, I wanted to re-order or shuffle attributes/fields in the standard query panel.

So I used ‘Set Source Order’ option to re-order the attributes.

Problem it created: attribute mis-match happened and one attribute showing another attribute value.

                                                                                       

Solution I did: Taken backup of VO impl custom method(other than setter and getter methods)and VO Row Impl and Client interface(VO-Java file),

          Go to VO wizard.

       From the Java section un- check for VO impl and VO Row Impl

      Select  ‘Query’  options from the left panel and click on ‘Update Mappings’ button

Once done, just restart the JDeveloper, and Generate VOImpl , VORow Impl  and Client interface java

Copy custom method you implemented in VOImpl from back up file and re-run. It works fine for me.

As per my observation, whenever you want to change VO query/ attribute order, it is better to do it in source mode instead of directly doing in wizard

Hope it helps!...