TROUBLESHOOTING: weblogic.descriptor.BeanAlreadyExistsException

Example Error
weblogic.descriptor.BeanAlreadyExistsException: Bean already exists: "weblogic.j2ee.descriptor.wl.LibraryRefBeanImpl@c76e5f19(/LibraryRefs[[CompoundKey: adf.oracle.domain]])


Solution
Dimitris Stasinopoulos posted on his blog regarding this error. Quick tips based on his post:

• Source of your problem is weblogic-application.xml. Check to see if you have duplicated or other unrelated entries and remove them. 

More details on his post.

TROUBLESHOOTING: The domain edit lock is owned by another session in non-exclusive mode (WLS deployer)

Error

[Deployer:149163]The domain edit lock is owned by another session in non-exclusive mode - this deployment operation requires exclusive access to the edit lock and hence cannot proceed. If you are using "Automatically Aquire Lock and Activate Changes" in the console, then the lock will expire shortly so retry this operation.

Solution

Actually what Deployer is trying to tell you is that it tried to deployed but another user has Lock and Edit the domain . More regarding Lock and Edit in this related post.

In other not to fail but exist gracefully leaving you deployment to be applied when the Lock is released, then use nonexclusivelock option.

Using this option you ll get the following message, if another user has avquire the lock and the script will not fail:
[wldeploy] Operation is pending and will be activated or cancelled when the ongoing edit session is activated or cancelled.


In case if you use a wldeploy ant task, here is an example script

<project name="deploy" default="deploy">
<property file="deploy.properties" />

<!-- Setting TaskDefinition -->
<taskdef name="wldeploy" classname="weblogic.ant.taskdefs.management.WLDeploy">
    <classpath>
        <pathelement location="${wldeploy.home}/weblogic.jar"/>
    </classpath>
</taskdef>
<!-- Deploying Applications  -->
<target name="deploy">
<wldeploy action="deploy"
          name="${deploy.name}"
          source="${deploy.source.path}/${deploy.source.ear}"
          verbose="true"
          adminurl="${connection.protocol}://${wls.hostname}:${wls.port}" 
          targets="${deploy.target}"
          upload="true"
          user="${wls.username}"
          password="${wls.password}"
          usenonexclusivelock="true" />
</target>
</project> 

Dig more:

• http://vbandaru.wordpress.com/2010/11/17/wldeployexclusive-access-to-the-edit-lock/

TROUBLESHOOTING: Bad Request' for url: '.../bea_wls_deployment_internal/DeploymentService (upon WLS deployment)

Error

weblogic.deploy.api.internal.utils.DeployerHelperException: The source '/tmp/ApplicationGreeceDEV.ear' for the application 'ApplicationGreeceDEV#2.0'
could not be loaded to the server 'http://127.0.0.1:7007/bea_wls_deployment_internal/DeploymentService'.
Response: '400: Bad Request' for url: 'http://127.0.0.1:7007/bea_wls_deployment_internal/DeploymentService'

Solution
I know it seems silly but do not waste time. Just restart server.

TROUBLESHOOTING: Changing the source location is not allowed for a previously attempted deployment. Try deploying without specifying the source. (WLS Error upon deployment)

Error

[Deployer:149007]New source location, '/u01/app/oracle/product/Middleware_1034/user_projects/domains/dev/servers/AdminServer/upload/ApplicationGreeceDEV/2.0/app/ApplicationGreeceDEV.ear',
 cannot be deployed to configured application, 'ApplicationGreeceDEV [Version=2.0]'. 

The application source is at
 '/u01/app/oracle/product/Middleware_1034/user_projects/domains/dev/servers/AdminServer/upload/ApplicationGreeceDEV.ear'.
 Changing the source location is not allowed for a previously attempted deployment. Try deploying without specifying the source.

Possible solution

(or  Solution that worked in my case)

-Undeploy the application.

-Go to Admin server's upload folder

eg. upload in my case

cd /u01/app/oracle/product/Middleware_1034/user_projects/domains/dev/servers/AdminServer/upload

-Remove any relate archives or directories
eg. ApplicationGreeceDEV.ear or ApplicationGreeceDEV directory
from upload folder

TROUBLESHOOTING: Compilation error - XML-20108: (Fatal Error) Start of root element expected. in rdf files.

If during compilation you get

Project: E:\JDeveloper\mywork\DEVELOPMENT\App\App\Model.jpr
    E:\JDeveloper\mywork\DEVELOPMENT\App\src\model\lovqueries\mdssys
           \mdx\MyLov.xml.rdf
        Error(1,1): file:/E:\JDeveloper\mywork\DEVELOPMENT\App\src\model
           \lovqueries\mdssys\mdx\MyLov.xml.rdf<Line 1, Column 1>: 
           XML-20108: (Fatal Error) Start of root element expected.

Then JDeveloper just created an empty rdf file.

Solution

Open rdf
add

<?xml version="1.0" encoding="UTF-8" ?>
<test>
</test>

Save


You might want to check: Utility to remove once and for all the *.rdf file error.



Src: http://forums.oracle.com/forums/thread.jspa?threadID=1134014&tstart=44

TROUBLESHOOTING: JDeveloper closes unexpectedly with no error message

Problem
Sometime JDeveloper might start acting funny and in worst case might crashes or closes unexpectedly.

The good thing is that all JDeveloper's setting are stored under its system directory. More regarding this directory in Change JDeveloper's system directory (system11.1.1.x.x.xx.xx).

Solution
Close JDeveloper  (if you are running it)

Go where the system dir is located, typically under

C:\Documents and Settings\username\Application Data\JDeveloper\

and remove it

Start JDeveloper. JDeveloper will recreate a fresh system dir automatically.

Warning! 

All you JDeveloper Preferences, SVN settings, embedded WLS configuration will be lost!!

TROUBLESHOOTING: "java.lang.ClassNotFoundException: javax.faces.context.FacesContextFactory" while deploying ADF Application

Last update: 4/7/2011

The error log is

[11:59:10 AM] Deploying Application...
<22 ???? 2011 11:59:20 pµ EEST> <Error> <Deployer> <BEA-149265> 
       <Failure occurred in the execution of deployment request with 
       ID '1308733152059' for task '0'. Error is: 
       'java.lang.ClassNotFoundException: javax.faces.context.
       FacesContextFactory'
java.lang.ClassNotFoundException: javax.faces.context.FacesContextFactory
 at weblogic.utils.classloaders.GenericClassLoader.findLocalClass
       (GenericClassLoader.java:297)
 at weblogic.utils.classloaders.GenericClassLoader.findClass
       (GenericClassLoader.java:270)
 at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass
       (ChangeAwareClassLoader.java:64)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
 Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: javax.faces.context.
       FacesContextFactory
 at weblogic.utils.classloaders.GenericClassLoader.findLocalClass
       (GenericClassLoader.java:297)
 at weblogic.utils.classloaders.GenericClassLoader.findClass
       (GenericClassLoader.java:270)
 at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass
       (ChangeAwareClassLoader.java:64)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
 Truncated. see log file for complete stacktrace
>

Solution:
In the Model project JDeveloper has created files related to ViewController (Web Content/WEB_INF folder with faces-config.xml, trinidad-config.xml  and web.xml). If you use a SubVersioning System, it is easy to check because they ll newly created and not added to SVN.
 

Remove this files/folders.

Maybe you might need to remove the contents of drs folder, too.
That is the folder that JDeveloper delpoys the application in order to run it in the embedded WLS.
It is located under %JDEV_SYSTEM_ROOT%/\o.j2ee
eg
C:\Documents and Settings\user\Application Data\JDeveloper\system11.1.1.4.37.59.23\o.j2ee\drs  

Decompiling ADF classes

Download Java Decompiler.

Extract zip and run included .exe

Open file and select a ADF lib eg. adfm.jar located in my case under C:\Oracle\Middleware\oracle_common\modules\oracle.adf.model_11.1.1




As you can see all packages are there.

Select the class you to see eg. oracle.jbo.server.ViewObjectImpl

Thanx Nick for the tip!

Utility to remove once and for all the *.rdf file error

Problem
As it is referred in OTN's post: RDF file xml error (quoting below)

I am trying to run the AM and somehow I am getting the following compilation error in file: \src\cs\model\view\mdssys\mdx\VO.xml.rdf

Error(1,1): : XML-20108: (Fatal Error) Start of root element expected.
I don't see anything in that file and i have now idea how that file is being used or got generated....
any help is really appreciated.....

Solution
The solution  is actually described in my other post TROUBLESHOOTING: Compilation error - XML-20108: (Fatal Error) Start of root element expected. in rdf files. More details below.
The solution to permanently remove the rdf problem once and for all (because if you just delete the files, they ll reappear) is to (quoting Amir Khanof):
open the file RDF( already you see it on the log) put these line (see below) on it and push save

<?xml version="1.0" encoding="UTF-8" ?>
<test>
</test>

Utility
RDF Cleaner is a tiny utility developed to perform the above for you. It search filesystem and for every rdf file it finds, add the above xml code in order not to complain again.

You can download it here.

Extract zip

Right Click Edit *.bat file

Set MY_APPLICATION_PATH with the path of you application

Save

Run bat file.

Also below is an ant target to run the util:

<?xml version="1.0" encoding="windows-1252" ?>
<project default="clean_RDF">
  <target name="clean_RDF">
    <fail unless="env.MY_APPLICATION_PATH" 
      message="Environment variable MY_APPLICATION_PATH 
       (with the project's path) is needed to run!"/>
    <fail unless="env.JDEV_UTILS_ROOT" 
      message="Environment variable JDEV_UTILS_ROOT 
       (pointing to the rdf cleaner jar) is needed to run!"/>
    <java jar="${env.JDEV_UTILS_ROOT}/RDFCleaner.1.0.jar" fork="true">
      <arg line="${env.MY_APPLICATION_PATH}"/>
    </java>
  </target>
</project>

Special thanx to Evgenia Maniati for offering this utility.

TROUBLESHOOTING: oracle.security.jps.JpsRuntimeException: Cannot read from policy store.

If during development you get

<12 Apr 2011 10:49:36 μμ EEST>

          \logs\DefaultServer.log is opened. All server side log events will be written to this file.>
 

oracle.security.jps.JpsRuntimeException: Cannot read from policy store.
            at oracle.security.jps.internal.policystore.xml.XmlPolicyStore.buildFromFile(XmlPolicyStore.java:425)
            at oracle.security.jps.internal.policystore.xml.XmlPolicyStore.(XmlPolicyStore.java:224)
        ...
Caused by: oracle.security.jps.JpsRuntimeException: javax.xml.stream.XMLStreamException: End Document reached 

                                    prematurely.
            at oracle.security.jps.internal.core.datastore.xml.XmlDataStoreParser.getDataStoreEntryStax

                 (XmlDataStoreParser.java:166)
        ...
            ... 28 more
...
weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to 

               exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the 

                debug flag -Djava.security.debug=jpspolicy to get more information. Error message: 

                oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider
          at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy

                                    (CommonSecurityServiceManagerDelegateImpl.java:1398)
        ...
Caused By: oracle.security.jps.JpsRuntimeException: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting 

                default policy Provider
           at oracle.security.jps.internal.policystore.PolicyDelegationController.(PolicyDelegationController.java:291)
...       
Caused By: java.security.PrivilegedActionException: oracle.security.jps.JpsException: [PolicyUtil] Unable to obtain default 

               JPS Context!
            at java.security.AccessController.doPrivileged(Native Method)
...
Caused By: oracle.security.jps.JpsRuntimeException: Cannot read from policy store.
            at oracle.security.jps.internal.policystore.xml.XmlPolicyStore.buildFromFile(XmlPolicyStore.java:425)
...

Solution
Try to remove jazn-data.xml and system-jazn-data.xml from the DefaultDomain.
For example under my DefaultDomain I have all these:

Although jazn-data is part of your application, it is copied to the domain because there is where the security is stored.

Note: I have changed my default path of JDeveloper's system folder. The default is C:\Documents and Settings\username\Application Data\JDeveloper\system11.1.1.4.37.59.23

TROUBLESHOOTING: Could not find saved view state for token ...

Chris Muir has an excellent post which resolves this kind of error. Reposting some of his material here:

Reason

The PS_TXN table  and PS_TXN_SEQ sequence are used by ADF to serialize user session state to the database. Without these database objects your application can't scale effectively to multiple users, you'll see some bizarre and wonderful behaviour as ADF chokes on not having the ability to serialize to the database objects. However it's not an ADF problem, the manuals clearly state that you need to grant specific privileges to the database user or create the database objects beforehand.

Resolution
Make sure that your database user has all 3 priviledges

• CREATE TABLE,  
• CREATE INDEX and  
• CREATE SEQUENCE

Supplying another database connection/schema  for "state management": 
Check BC State management (Activation/Passsivation) best practise
Some log entries to help identify it.

Under JDev 11g build 5188 you'll see the following WLS log entries:
First it'll throw errors that it can't retrieve user session state:

SEVERE: Could not find saved view state for token -505abe38
11/08/2009 14:29:29 org.apache.myfaces.trinidadinternal.application.StateManagerImpl restoreView
SEVERE: Could not find saved view state for token -505abe38
11/08/2009 14:29:29 org.apache.myfaces.trinidadinternal.application.StateManagerImpl restoreView
SEVERE: Could not find saved view state for token -505abe38
11/08/2009 14:29:29 org.apache.myfaces.trinidadinternal.application.StateManagerImpl restoreView

At a later point in the logs you'll see exceptions thrown, but they're not very meaningful:

WARNING: ADFc: Error while opening JDBC connection.
oracle.jbo.DMLException: JBO-26061: Error while opening JDBC connection.
 at oracle.jbo.server.ConnectionPool.createConnection(ConnectionPool.java:253)
 at oracle.jbo.server.ConnectionPool.instantiateResource(ConnectionPool.java:168)
 at oracle.jbo.pool.ResourcePool.createResource(ResourcePool.java:546)
 at oracle.jbo.pool.ResourcePool.useResource(ResourcePool.java:327)

Further in the logs you may see the following TNS Listener issue (though this may just be particular to my Oracle XE setup):

Caused by: java.sql.SQLException: Listener refused the connection with the following error:
ORA-12519, TNS:no appropriate service handler found
The Connection descriptor used by the client was:
localhost:1521:xe
 at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
 at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:116)
 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:177)

And you may see NullPointerExceptions dependent on what ADF was attempting to do with the database connection at the time:

Caused by: java.lang.NullPointerException
 at oracle.adf.model.binding.DCIteratorBinding.initSourceRSI(DCIteratorBinding.java:1735)
 at oracle.adf.model.binding.DCIteratorBinding.callInitSourceRSI(DCIteratorBinding.java:1625)
 ... 75 more

Under JDev 11gR1 build 5407 gives you a more meaningful error message:

Again, first you'll see errors that it can't retrieve user session state:

SEVERE: Could not find saved view state for token -ce0efchp5
11/08/2009 2:35:31 PM org.apache.myfaces.trinidadinternal.application.StateManagerImpl restoreView
SEVERE: Could not find saved view state for token -ce0efchp7
11/08/2009 2:35:31 PM org.apache.myfaces.trinidadinternal.application.StateManagerImpl restoreView
SEVERE: Could not find saved view state for token -ce0efchp7
11/08/2009 2:35:31 PM org.apache.myfaces.trinidadinternal.application.StateManagerImpl restoreView

But then you'll see a much more meaningful message that ADF can't create the required objects:

oracle.jbo.PCollException: JBO-28006: Could not create persistence table PS_TXN_seq
 at oracle.jbo.PCollException.throwException(PCollException.java:36)
 at oracle.jbo.pcoll.OraclePersistManager.createTable(OraclePersistManager.java:908)
 at oracle.jbo.pcoll.OraclePersistManager.queryNextCollectionId(OraclePersistManager.java:1444)

And further down:

Caused by: java.sql.SQLSyntaxErrorException: ORA-01031: insufficient privileges
 at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:91)
 at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:206)
 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)

Special thanx to Chris Muir for his excellent post.

Dig more:

• http://chrismuir.sys-con.com/node/1067419/mobile
• http://download.oracle.com/docs/cd/E12839_01/web.1111/b31974/bcstatemgmt.htm#ADFFD1307

TROUBLESHOOTING: JDeveloper will not start

Problem/Symptoms
JDeveloper refused to start. It loaded up to ~600MB of memory and then it freezed. See image below:

Also IE was refusing to load the Home page.

Investigation
Checking the files accessed by JDeveloper, indicated the probable cause:

Resolution
So after removing the files below

• C:\Documents and Settings\spiros\Local Settings\History\History.IE5\index.dat
  
• C:\Documents and Settings\spiros\Local Settings\Temp\hsperfdata_spiros\3736
• C:\Documents and Settings\spiros\Local Settings\Temporary Internet Files\Content.IE5\index.dat

and Restarting Windows, JDeveloper managed to start.
 
Tip:
Moreover, one of the most useful tips when you have problem with JDeveloper (not starting or performance degradation, crashes etc) is to remove JDeveloper's system directory. 
The default location is

C:\Documents and Settings\username\Application Data\JDeveloper\

under that directory is a directory named

system11.1.1.4.37.59.23

(for JDeveloper 11.1.1.4.0)
Close JDeveloper and remove it. Upon starting again, JDeveloper will recreate a new fresh one.
WARNING: All your JDeveloper settings (SVN settings, Preferences etc) will be lost!!!!

Debug ADF Rich Faces

For debugging Rich Faces using Firebug check
"Advanced Javascript debugging with FireBug and analyzing your page with View Source Chart"


The following sections in the Developer's Guide may help you in understanding how the javascripts are generated, and also set up some options for debugging (org.apache.myfaces.trinidad.DEBUG_JAVASCRIPT f.ex.):

1.2.1.2 JavaScript Library Partitioning
http://download.oracle.com/docs/cd/E15523_01/web.1111/b31973/gs_intro.htm#BABJGCAI

A.9 Using JavaScript Library Partitioning
http://download.oracle.com/docs/cd/E15523_01/web.1111/b31973/ap_config.htm#BABCJIDJ

and other documents like:

"Oracle Application Development Framework Performance Tuning" in the "Oracle Fusion Middleware Performance and Tuning Guide"
http://download.oracle.com/docs/cd/E16764_01/core.1111/e10108/adf.htm#CIHHGADG

TROUBLESHOOTING: "Because of inactivity, your session has timed out and is no longer active..."

Last updated: 7/4/2011

Problem
The following error might occur will navigating to your app.

Solution
One of the reason might be that org.apache.myfaces.trinidad.CLIENT_STATE_MAX_TOKENS value is not great enough.

Add the following param in your web.xml and setting according to yourneeds:

Memory consuption
What about memory consuption? See my related pos: Memory consumption of org.apache.myfaces.trinidad.CLIENT_STATE_MAX_TOKENS

Theory
For some theory behind CLIENT_STATE_MAX_TOKENS check my related post "What is org.apache.myfaces.trinidad.CLIENT_STATE_MAX_TOKENS?"





Dig more:

• http://forums.oracle.com/forums/thread.jspa?threadID=550783
• http://myfaces.apache.org/trinidad/devguide/configuration.html
• http://download.oracle.com/docs/cd/E12839_01/web.1111/b31973/ap_config.htm
• What is org.apache.myfaces.trinidad.CLIENT_STATE_MAX_TOKENS?

Using Diagnostic Messages for troubleshooting

You can enable Diagnostic messages when running your application (on WLS (WebLogic Server) or BC Tester).

Enable diagnostic messages post will tell you how to configure the BC and/or Weblogic Server to print these messages.

To find the available diagnostic message you can enable, take a look at oracle.jbo.common.logging.Diagnostic.properties file.
This file's  purpose is  for DEBUG build of Business Components for Java. This is the file used to determine the way that Diagnostic  calls in the code are handled: all of its the properties  can be overridden by specifying then as -D switches to the java VM.


The available properties are:

jbo.debugoutput=console

Values: console|silent|classname|file

Which implementation of IDiagnostic to use: console|silent|classname classname is the fully qualified name of a user-defined class that implements the IDiagnostic interface

Also a 4th options is available. You can set it to be jbo.debugoutput=file.

In this case the diagnostic messages will be written to file. The location of the file is the system/user temp 
directory and will be printed (so as for you to be sure the -D switches are applied ) when you run your 
application (either from the BC Tester (when testing BC) or when running app on Weblogic).

eg.

Target URL -- http://127.0.0.1:7101/MyWebapps-context-root/faces/main

Diagnostics: (Properties (re)loaded) Routing diagnostics to File: C:\DOCUME~1\spiros\LOCALS~1\Temp\bc4j5308862451677235376.log

jbo.logging.show.function=false

Values:true|false

Setting to true will output the name of the class and method displaying the log.

Eg. <3>[11] (10) RowSetHelper.getListeners Getting listeners ready...

In the above example:

•  <3>  - the message is issues at trace level 3
•  [11] - this is trace line number 11
•  (10) - 10 ms have elapsed since the last trace message
•  RowSetHelper - class from which the trace message was issued
•  getListeners - function from which the trace message was issued
•  Getting Listeners ready ... - test of the trace message

jbo.logging.show.linecount=true

Values:true|false

Show a linecount as each diagnostic line is output (true|false)

jbo.logging.trace.threshold=3

Logging cutoff threshold: any trace messages with a level  higher than this threshold will be suppressed (to understand it better log4j has the reverse priority).

For a release build, system Diagnostic messages are at level 3
dditionally, in a Debug build, DebugDiagnostic messages are at level 6

jbo.debug.prefix=DBG

Prefix string to display on DebugDiagnostic lines.Debug build only

jbo.logging.show.timing=false

Show elapsed time info every call (true|false)

jbo.logging.show.level=false
Show level of trace statement

Dig more:

• http://radio-weblogs.com/0118231/stories/2003/01/17/howToGetMoreDetailsErrorInformation.html
• http://radio-weblogs.com/0118231/2004/11/25.html
• http://download.oracle.com/docs/cd/A97336_01/buslog.102/bc4j/developing_bc_projects/obcUseMessages.htm
• http://technology.amis.nl/blog/435/bc4j-adf-business-components-logging-and-debugging-great-blog-from-sandra

Enable Diagnostic Messages on your ADF Application

Last Upate: 1/4/2011

 

In order to troubleshoot the problem of your Fusion Web Application, you can enable the diagnostic messages on the WLS (WebLogic Server) that you application is running.

Enable Diagnostic messages in BC
To enable diagnostic message in BC check Turn on Diagnostic to Debug Oracle ADF BC Applications

Reposting:

1. Select the project (e.g., "Model").
2. Do right mouse click and select "Project Properties"
3. On the property dialog, select "Run/Debug/Profile".
4. Edit your Run Configuration (e.g., "Default")
5. On the right pane, you should see "Java Options" input text field. Add the following Java system parameter: -Djbo.debugoutput=console

Enable Diagnostic messages in View
You can enable both on the embedded or standalone WLS.

• The embedded WLS is the one that is running when you run your application from JDeveloper (during development)

• A standalone WLS is when you run wls from the start script (usually in production systems). You can run the embedded as a standalone too.

(cmd for windows , sh for Unix)

In the following examples will be enabling only 2 diagnostic options:

• -Djbo.debugoutput=file  
• -Djbo.logging.show.function=true

You can find more on diagnostic messages related post.

Enabling diagnostic messages in embedded WLS 
You can enable diagnostic messages

• Open your ViewController Project Properties
•  run/debug/profile
• Edit
• In "Java Options" add the parameters for enabling dagnostic messages. e.g. -Djbo.debugoutput=file  -Djbo.logging.show.function=true

Moreover, you can perform this steps to a Model problem in case you want to have diagnotic messages when running Bussiness Components Tester.

Enabling diagnostic messages in standalone WLS
In the following example will be using the WLS that is shipped with JDeveloper as a standalone in a Windows machine.  
Go to WLS bin directory. In our case  %JDEV_SYSTEM_DIR%\DefaultDomain\bin\ 
eg
C:\JDeveloper\mywork\system11.1.1.3.37.56.60\DefaultDomain\bin\ 
(Note: Check related post to find out the JDEV_SYSTEM_DIR from log of the running WLS.)

Open file setDomainEnv.cmd On the top of the file after the comments enter the following line set DIAGNOSTIC_OPTIONS=-Djbo.debugoutput=file -Djbo.logging.show.function=true Then modify the following line set JAVA_PROPERTIES=-Dplatform.home=%WL_HOME% -Dwls.home=%WLS_HOME% -Dweblogic.home=%WLS_HOME% (in the same line.)
to set JAVA_PROPERTIES=-Dplatform.home=%WL_HOME% -Dwls.home=%WLS_HOME% -Dweblogic.home=%WLS_HOME% %DIAGNOSTIC_OPTIONS% (in the same line.)



The is also an alternative way. You do not need to set -D params but edit the Diagnostic.properties file. Just take a look on the following quoted text:

Business Component diagnostics can be controlled by setting various jbo.xxx system properties. By default, the system property definitions reside in the file Diagnostic.properties in the .\oracle\jbo\common path on theCLASSPATH.
A default version of this file is supplied in the .\lib\jbomt.zip library. You can permanently change the default settings by extracting this file from the .zip archive, changing the values of the properties in the file, and making it available earlier in your project's library path. The file must appear before the library named "JBO Runtime" in the appropriate .\oracle\jbo\common subdirectory.
(I ll try to find time to give a more detailed and ready to  use example)


dig more:

• http://adfhowto.blogspot.com/2011/01/using-diagnostic-messages-for.html
• http://download.oracle.com/docs/cd/A97336_01/buslog.102/bc4j/developing_bc_projects/obcUseMessages.htm
• http://adfjsf.blogspot.com/2009/06/turning-on-diagnostic-debugging-in.html
• http://radio-weblogs.com/0118231/stories/2003/01/17/howToGetMoreDetailsErrorInformation.html
• http://xmlandmore.blogspot.com/2009/06/turn-on-diagnostic-to-debug-oracle-adf.html
• http://xmlandmore.blogspot.com/2009/06/turn-on-diagnostic-to-debug-oracle-adf.htmls

What ADF Error Messages mean (eg. JBO-xxxxx or ADFC-xxxxx etc. )

Last Update: 17/1/2011

Errors, that you can see in the log files of your app, source from middleware (ADF part) or DB. In the reference below a Source/Caution and an Action is provided to help resolve the problem

On the top I created a page "SEARCH ADF ERROR MESSAGES", that can help in locating the problem. It searches all the Error Message types referenced below.

Fusion Middleware Error Messages

In the link below are all the error message regarding the Fusion Middleware

Oracle® Fusion Middleware Error Messages Reference 11g Release 1 (11.1.1)

where you ll find also 

• JBO Error Messages Error Message regarding JBO-xxxxx errors 
• ADFC Error Messages regarding ADF Controller ADFC-xxxxx errors

JBO Error Messages

It is a subpart of Fusion Middleware Error Messages.

So, check the link above (JBO Error Messages)

Check also Business Components for Java Error Messages. There are some errors not mentioned in the above link

ORA Error reference

Regarding Oracle DB error messages check:

Oracle® Database Error Messages 11g Release 1 (11.1)

Note:

If you need an older version google for "Oracle<the BD version you want> Database Error Messages"

Also here you can find a search utility too.

BEA Error reference

This are the error produced from Weblogic (BEA was the company created Weblogic before Oracle buy BEA)
Oracle Fusion Middleware Oracle WebLogic Server Message Catalog 11g Release 1 (10.3.4)

dig more:

• http://wiki.oracle.com/page/Understanding+ADF+Error+Codes
• http://psoug.org/oraerror.htm/ 

TROUBLESHOOTING: LOV in af:query automatically returns value if it has only 1 row

Problem
You have an af:query with an View Criteria attribute that has a LOV.
If this LOV has only 1 row then it will return automatically the value of that row to the View Criteria attr.
This is regardless of  the VC attr being required or not.
So even if you go and erase the value, when you select the next field, the LOV will populate it automatically.

Solution
There is no any. This is default ADF behavior (?!?)
If user want to clear the VC attr of the af:query must click Reset.

Src:
http://adfbugs.blogspot.com/2010/05/single-row-lov-in-query-criteria-bug.html

TROUBLESHOOTING: af:query does not search when in query field, String is used

This is an ADF newbie tip.

Problem
Let's say you got a af:query with one query field (of type String) and a result table (typical scenario).
You can search using Number but you cannot search (it brings everything) using String.
No error occurs.

Solution
The bind var of the query field is of type Number, which is the wrong type. Change it to String.

TROUBLESHOOTING: "Low Memory Warning" of JDeveloper or How to tweak memory settings.

Last updated on: 14/12/2010

Here are the 2 well known tips to make JDeveloper use more mem, and workaround the "Low Memory Warning".


The files to modify
The following 2 files  must be modified

• C:\Oracle\Middleware\jdeveloper\ide\bin\ide.conf
• C:\Oracle\Middleware\jdeveloper\jdev\bin\jdev.conf

here I have used the default installation folder that is proposed by JDev. If you have another just search the 2 files in hte installaiton folder.

The mods
For ide.conf
Tweak the following lines

AddVMOption  -Xmx940M
AddVMOption  -Xms128M


For jdev.conf
Tweak
AddVMOption  -XX:MaxPermSize=356M

these are the setting I use and my jdeveloper.exe limits up to around 1200MB

Remember the limit of the mem that can me allocated to a java process in Windows is around 1.5Gigs.
These so if (Xmx + XX:MaxPermSize) around 1.5 gigs JDeveloper will not start and through a related jvm.dll error.

Note:
This is a common and old practice to increase memory of JDeveloper (back to the first days of 11g release when the mem leaks where creting pools of memory). These days are in to the past and the tool now behaves  almost ideally.

Note2 :
Also if you machine is really old, decreasing history of JDeveloper might help a lot.