Wednesday, March 28, 2012

WSDL excpetion in weblogic

Error message: WARNING: Input Action on WSDL operation PreparedOperation and @Action on its associated Web Method preparedOperation did not match and will cause problems in dispatching the request

or 

Error message : WARNING: Input Action on WSDL operation RegisterOperation and @Action on its associated Web Method registerOperation did not match and will cause problems in dispatching the requests
 

Weblogic version: 12c (12.1.1)

Solution : 1. change the domain from development mode to production mode.
                This could be done by opening the console and domain name --> configuration --> general
                click production mode enabled - save -activate changes - restart.
                2. Also a patch 13606167 is available.

Wednesday, March 21, 2012

Weblogic console showing old version after upgrade

After upgrading from 10.3.3 to 10.3.5, the console page is still showing old version.

config.xml & startup logs are showing the correct version.

under the middleware directory directory where the patch for upgrade installer is kept, i found two patch directories patch_wls1033 & patch_wls1035.
I deleted patch_wls1033 as my weblogic has now been upgraded to 10.3.5
The console is showing the correct version now.

Monday, March 19, 2012

Connection has been administratively disabled.

Seeing error message :
java.sql.SQLException: Connection has been administratively disabled.

intermittent issueand connection hangs for requests

Added the following parameter and problem solved
-Dweblogic.resourcepool.max_test_wait_secs=

Wednesday, March 14, 2012

domain creation stuck

Weblogic Domain creation stuck/froze at creating domain security information.......
Have taken a backup of config.sh (wlserver_10.3\common\bin)
added the variable -Djava.security.egd=file:/dev/./urandom in JVM_ARGS

it now looks like 
JVM_ARGS="-Djava.security.egd=file:/dev/./urandom -Dprod.props.file='${WL_HOME}/.product.properties' -Dpython.cachedir=/tmp/cachedir ${JVM_D64} ${MEM_ARGS} ${CONFIG_JVM_ARGS}"

rerunning config.sh solved the issue.