Discoverer Plus/Viewer 11g Gives "Empty Input (Or Null Input) Is Not Allowed" Error

(Doc ID 1384779.1)

Last updated on NOVEMBER 28, 2015

Applies to:

Oracle Discoverer - Version 11.1.1.4.0 and later
Information in this document applies to any platform.
***Checked for relevance on 13-JUN-2014***
***Checked for relevance on 28-Nov-2015***

Symptoms

When attempting to display the Discoverer Plus/Viewer 11g connections page the following error is encountered:

Error
An error occurred while handling the event. See the application log for more details. null
- Empty input (or null input) is not allowed.




Upon WLS_DISCO managed server startup the following can be noticed:

[2011-12-09T12:17:06.438+02:00] [WLS_DISCO] [ERROR] [J2EE JMX-46030] [] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 706df932b887598d:-2c6df81a:134225302a0:-8000-0000000000000002,0] [APP: discoverer#11.1.1.2.0] failure to register MBean "com.oracle:name=DiscovererConfig,type=Xml,Application=discoverer,ApplicationVersion=11.1.1.2.0" during application initialization.[[
java.lang.IllegalArgumentException: String "$$Discoverer.webcache$$" is not valid boolean value.
  at com.sun.xml.bind.DatatypeConverterImpl._parseBoolean(DatatypeConverterImpl.java:317)
  at oracle.discoverer.config.Configuration_JaxbXducedAccessor_webcache.parse(TransducedAccessor_field_Boolean.java:59)
  at com.sun.xml.bind.v2.runtime.unmarshaller.StructureLoader.startElement(StructureLoader.java:202)
  ...


Some other variations might be encountered too, i.e.:

java.lang.IllegalArgumentException: String "$$Discoverer.useConnectionMgmt$$" is not valid boolean value.


A slightly different exception (DiscovererPreviewConfig instead of DiscovererConfig) can be observed upon WLS_DISCO managed server startup , however that is not causing the "Empty input (or null input) is not allowed." error to be displayed.

Changes

Allegedly the issue started to occur after applying Patch  9313565.
Though, this could not be demonstrated and all leads suggested that the patch didn't had any impact on the issue.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms