Today, when deploying Oracle Summit Demo to a standalone Weblogic, ORA-01005 exceptions are reported, and running in Integrated Weblogic is always normal.
The main exception Log is as follows:
#### <Apr 29,201 3 3:16:40 pm cst> <Notice> <Diagnostics> <ol5.shawn.com> <AdminServer> <[STANDBY] ExecuteThread: '5' for queue: 'weblogic. kernel. default (self-tuning) '> <WLS Kernel> <11d1def534ea1be0:-294091cd: 13e54680b95: -8000-00000000000008d4> <1367219800002> <BEA-320068> <Watch 'uncheckedexception 'with severity 'notice' on server 'adminserver' has triggered at Apr 29,201 3 3:16:39 cst pm. notification details:
WatchRuleType: Log
WatchRule: (SEVERITY = 'error') AND (MSGID = 'wl-000000') OR (MSGID = 'wl-000000') OR (MSGID = 'wl-000000 ') OR (MSGID = 'bea-000000') OR (MSGID = 'bea-000000') OR (MSGID = 'bea-000000 '))
WatchData: DATE = Apr 29,201 3 3:16:39 pm cst server = AdminServer MESSAGE = [ServletContext @ 29859202 [app: SummitADF_application1 module: SummitADF-ViewController-context-root path: /SummitADF-ViewController-context-root spec-version: 2.5] Servlet failed with Exception
Oracle. jbo. noDefException: JBO-29114 ADFContext is not setup to process messages for this exception. use the exception stack trace and error code to investigate the root cause of this exception. root cause error code is JBO-25058. error message parameters are {0 = Attribute, 1 = Id, 2 = Id}
At oracle. jbo. uicli. binding. JUCtrlValueBinding. getAttributeDef (JUCtrlValueBinding. java: 552)
......
......
Caused By: oracle. jbo. DMLException: JBO-29114 ADFContext is not setup to process messages for this exception. use the exception stack trace and error code to investigate the root cause of this exception. root cause error code is JBO-26061.
At oracle. jbo. server. ConnectionPool. createConnection (ConnectionPool. java: 207)
......
......
Caused By: java. SQL. SQLException: ORA-01005: null password given; logon denied
At oracle. jdbc. driver. T4CTTIoer. processError (T4CTTIoer. java: 462)
......
......
I don't understand why the password is blank. Fortunately, Gu Ge has the following solutions:
Add the following parameter to JAVA_PROPERTIES in FMW_HOME/user_projects/domains/yourdomain/bin/setDomainEnv. sh:
-Djps. app. credential. overwrite. allowed = true
Result:
JAVA_PROPERTIES = "-Dplatform. home =$ {WL_HOME}-Dwls. home =$ {WLS_HOME}-Dweblogic. home =$ {WLS_HOME}-Djps. app. credential. overwrite. allowed = true"
Restart Weblogic and then access the application. Everything works...