Set jbo.ampool.doampooling=false to Reproduce Problems Related to AM Passivation / Activation

Some users report intermittent errors like the following, occurring under heavy load in the Production environment:

JBO-27120: SQL error during query execution. Statement: <SQL Statement>
java.sql.SQLException: Missing IN or OUT parameter at index:: <index number>

JBO-27122: SQL error during statement preparation. Statement: <SQL Statement>

JBO-30003: The application pool (AppModuleLocal) failed to checkout an application module due to the following exception:
oracle.jbo.JboException: JBO-29000: Unexpected exception caught:
msg=JBO-25000: Unknown SQL type: null

These errors are difficult to diagnose as developers cannot reproduce in the Development or Test environments.

There is then a strong suspicion that the problem is related to the Application Module passivation / activation.

To be 100% sure this is the case, you can force it to occur in your Development environment by setting jbo.ampool.doampooling=false (or uncheck the "Enable Application Module Pooling" in your Configuration):


From the ADF Developer's Guide topic "28.3 Controlling the State Management Release Level" ("Note" under 28.3.1 Supported Release Levels):
 "Setting this property [jbo.ampool.doampooling] to false is useful to discover problems in your application logic that might occur when reactivation does occur due to unpredictable load on your system."

If the problem reproduces then, you'll be 100% sure the problem occurs at the reactivation of your Application Module.
Please contact Oracle Support Services then so that a Support Engineer can help you in fixing the problem.

We recommend you to test all your applications in your Development environment with this parameter jbo.ampool.doampooling=false to ensure they are activation-safe, as explained in "28.8 Testing to Ensure Your Application Module is Activation-Safe" of the ADF Developer's Guide.

Forewarned is forarmed...


Hi, I recently had an "Unknown SQL type" exception in my web application... I turned off AM Pooling and recreated this exception. I have parametrized ViewObject with 3 String parameters, jspx site with search form and read only table for search results. Table and search form are based od different iterators (search form iterator is always in findMode). On first search everything seems fine. But when I try to do second search I'm getting "Unknown SQL type: null" exception. It works properly only when all the parameters in the ViewObject are set. I tried to overload activateState and passivateState methods in VO but result is excactly the same. ActivateState method doesn't even run before exception is thrown... Of course with AM pooling turned on everything works fine :/ If You have any tips I'll be very greatfull. Thank You Part of stack trace: oracle.jbo.common.UnknownSQLTypeException: JBO-25000: Nieznany typ SQL: null at oracle.jbo.domain.NullValue.( at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance( at sun.reflect.DelegatingConstructorAccessorImpl.newInstance( at java.lang.reflect.Constructor.newInstance( at oracle.jbo.domain.TypeConvMapEntry.convert( at oracle.jbo.domain.TypeFactory.get( at oracle.jbo.domain.TypeFactory.getInstance( at oracle.jbo.server.AttributeDefImpl.getXMLContentValue( at oracle.jbo.server.ViewObjectImpl.activateParams( at oracle.jbo.server.ViewObjectImpl.doActivateSettings( at oracle.jbo.server.ViewObjectImpl.doActivateSettings( at oracle.jbo.server.ApplicationModuleImpl.activateVOs( at oracle.jbo.server.ApplicationModuleImpl.doActivateState( at oracle.jbo.server.ApplicationModuleImpl.doActivateAMState(

Posted by Kuba on December 04, 2006 at 01:31 AM CET #


this is a known issue (Bug 5191597) for which a patch exists. I also answered your OTN post

Either log a Service Request in Metalink or read instructions from Note 400316.1



Posted by Didier Laurent on December 04, 2006 at 02:38 AM CET #

Didier, Thank You for quick reply. You really helped me a lot! Regards, Kuba

Posted by Kuba on December 04, 2006 at 06:43 PM CET #

You're welcome. I'm happy I could help. Didier.

Posted by Didier Laurent on December 04, 2006 at 07:23 PM CET #

Didier, I saw that this bug is solved with JDeveloper Production Release ( Would using JDeveloper be enough, or do I have to upgrade/patch my application server as well? The application server version is Regards, Pat

Posted by Pat Lee on December 08, 2006 at 12:26 AM CET #

Hi Pat,

as a rule of thumb, I would always advise you to install the ADF Runtime libraries in your iAS after an upgrade of JDeveloper (other than a Service Update that just includes Design Time fixes).
See remark A in the "Application Servers Supported by JDeveloper"

For more information, see the following documents:
Hope this helps,


Posted by Didier Laurent on December 08, 2006 at 06:58 AM CET #

Hi Didier, Thanks for the reply. My concern was indeed how to update without JDeveloper and drive mapping. The stand-alone installer is sufficient for me. (I was not aware of it's existence). Note that the OTN howto deals with an upgrade from 9.0.5.x to 10g and is dating from August 2004. I think the article needs reviewing to match current technologies. Thanks again for the help. Regards, Pat

Posted by Pat Lee on December 10, 2006 at 07:17 PM CET #

Hi Pat, I'm not aware of changes in the ADF BC APIs, so I think the article is still valid. However, I agree it would be better to update it to the current releases. I'll forward your comment to the author. Thanks, Didier.

Posted by Didier Laurent on December 10, 2006 at 07:30 PM CET #

Hi Didier, I am using JDeveloper I developed an application and deployed to the Oracle Application Server 10g. When I access the application from the server sometimes I get the error: Missing IN or OUT parameter at index:: 1 I went through your blog in: As you asked I un-checked the check box for Enable Application Module Pooling in Application Module configuration. And the error was re-produced. Now according to your suggestion, should I contact Oracle Support Services to fix it or you have other suggestions/idea? Please advice Thanks Syed Jabbar University of Windsor Windsor, ON, Canada

Posted by Syed Jabbar on April 09, 2007 at 08:14 AM CEST #

Hi Syed, it seems you are hitting Bug 5524157 - INTERMITTENT "MISSING IN OR OUT PARAMETER AT INDEX:: 1" NAMED PARAM ADF/JSF Please check Note 413797.1 I wrote in Metalink a few months ago. It includes instructions on how to install a patch to fix the problem. If you have any further question, please log a SR so that we improve the Note. NB: Notes in Metalink include the following 2 questions: . Did this article help solve your problem? . Would you recommend this document to others? You can also provide feedback on a Note this way. Hope this helps, Didier.

Posted by Didier Laurent on April 09, 2007 at 07:24 PM CEST #

Hi i am having exactly same situation like Syed Jabbar. I searched in Metalink and didnt found any patch for, Is this Bug fixed in or what ? Thanks in advance !

Posted by MeJ on May 03, 2010 at 01:26 PM CEST #

Bug 5524157 was indeed fixed in JDev, what explains you cannot find a patch for that version.

Posted by Didier on May 04, 2010 at 09:32 AM CEST #

Post a Comment:
Comments are closed for this entry.

Didier Laurent - Sr Principal Support Engineer in the JDeveloper team


« June 2016