Connection test failed with the following exception: weblogic.common.resourcepool.ResourceDisabledException: Pool mds-SpacesDS is Suspended, cannot allocate resources to applications..
You may observe datasources going into suspended state. When you try to test the datasource connection, it throws error as above (with the problem datasource name)
Try checking the DB parameters:
SQL> select name, value from v$parameter where name in ('processes', 'sessions', 'transactions');
If the parameters are set to low values, you may want to increase the value of these parameters & restart the database. Often the case may be Processes parameter may have maxed out & increasing it should resolve the issue of datasources going into suspended state.
SQL> alter system set processes = <value> scope = spfile;
System altered.
SQL> alter system set sessions = <value> scope = spfile;
System altered.
SQL> alter system set transactions = <value> scope = spfile;
System altered.
Restart the database
You may also want to increase Max Capacity of problem datasources.
Also consider increasing the timeout value under Domain -> JTA -> Configuration
Apply patch 19177895 to fix WEB SERVICE CALL MEMORY LEAK in Weblogic 12.1.2.0.0
Memory leak & OutofMemory Errors can be seen in Weblogic 12.1.2 after upgrading from Weblogic 12.1.1 when making remote client web service calls.
To fix this apply patch 19177895.
For more details, please refer to
Bug 19358570 : WEB SERVICE CALL MEMORY LEAK in Weblogic 12.1.2
Patch 19177895: WEBLOGIC.WSE.JAXWS.OWSM.WSDLDEFINITIONFEATURE USES 3.6GB OF MEMORY
Pre Install Instructions:
-------------------------
- Stop all Webogic Server instances (AdminServer and all Managed server(s))
Install Instructions:
---------------------
1. Unzip the patch zip file into the PATCH_TOP.
unzip -d PATCH_TOP p19177895_121200_Generic.zip
NOTE : p19177895_121200_Generic.zip cannot be in PATCH_TOP directory.
2. Set your current directory to the directory where the patch is located.
cd PATCH_TOP/19177895
3. Run OPatch to apply the patch.
Run following command:
- opatch apply -jdk $JAVA_HOME (in Windows %JAVA_HOME%)
4. Run OPatch to verify the patch application.
Run following command:
- opatch lsinventory -jdk $JAVA_HOME (in Windows %JAVA_HOME%)
Post Install Instructions:
--------------------------
- Start all servers (AdminServer and all Managed server(s))
Applying Patch 18040640 - SU Patch [T5F1]: Weblogic Server (WLS) PATCH SET UPDATE 10.3.6.0.8 on OBIEE client
Check existing WLS details by executing below command
cd $MW_HOME\utils\bsu
./bsu.cmd -view -status=applied -prod_dir=$MW_HOME\wlserver_10.3
ProductName: WebLogic Server
ProductVersion: 10.3 MP5
Components: WebLogic Server/Core Application Server,WebLogic Server/Administration Console,WebLogic Server/Configuration Wizard and
Upgrade Framework,WebLogic Server/Web 2.0 HTTP Pub-Sub Server,WebLogic Server/WebLogic SCA,WebLogic Server/WebLogic JDBC
Drivers,WebLogic Server/Third Party JDBC Drivers,WebLogic Server/WebLogic Server Clients,WebLogic Server/WebLogic Web
Server Plugins,WebLogic Server/UDDI and Xquery Support,WebLogic Server/Evaluation Database,WebLogic Server/Workshop Code
Completion Support
BEAHome: $MW_HOME
ProductHome: $MW_HOME\wlserver_10.3
PatchSystemDir: $MW_HOME\utils\bsu
PatchDir: $MW_HOME\patch_wls1035
Profile: Default
DownloadDir: $MW_HOME\utils\bsu\cache_dir
JavaHome: $MW_HOME\jdk160_24
JavaVersion: 1.6.0_24
JavaVendor: Sun
Step 1:
$Stage_Dir\p13529623_1036_Generic>$MW_HOME\jrockit_160_24_D1.1.2-4\bin\java.exe -jar wls1036_upgrade_generic.jar
Extracting 0%...................................................................
.................................100%
Step 2: Install 10.3.6.0.8 Patch 18040640
unzip $Stage_Dir\p18040640_1036_Generic.zip to $MW_HOME\utils\bsu\cache_dir
cd $MW_HOME\utils\bsu
$MW_HOME\utils\bsu\bsu.cmd -install -patch_download_dir=$MW_HOME\utils\bsu\cache_dir -patchlist=T5F1 -prod_dir=$MW_HOME\wlserver_10.3
Patch T5F1 install SUCCESS
Related Posts:
Applying Patch 20844228: WLS PATCH SET UPDATE 12.1.2.0.6
Applying Patch 20780171: SU Patch [EJUW]: WLS PATCH SET UPDATE 10.3.6.0.12
Applying Patch 20181997: SU Patch [YUIS]: WLS PATCH SET UPDATE 10.3.6.0.11
Applying Patch 19637463: SU Patch [12UV]: Oracle WebLogic Server (WLS) PATCH SET UPDATE 10.3.6.0.10
Applying Patch 19182814: SU Patch [FSR2]: Weblogic Server (WLS) PATCH SET UPDATE 10.3.6.0.9
Applying Weblogic patch 16810786 - MEMORY LEAK ON COM.CERTICOM.TLS.INTERFACEIMPL.CERTIFICATESUPPORT
Download p16810786_1036_Generic.zip in the server stage area.
$ ./bsu.sh -prod_dir=/<MW_HOME>/111/wlserver_10.3 -patch_download_dir=/<MW_HOME>/111/utils/bsu/cache_dir -patchlist=SK1V -verbose -install
Checking for conflicts..
No conflict(s) detected
Starting installation of Patch ID: SK1V
Installing /<MW_HOME>/111/utils/bsu/cache_dir/SK1V.jar
Extracting /<MW_HOME>/111/patch_wls1036/patch_jars/BUG16810786_1036.jar
Updating /<MW_HOME>/111/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar
Old manifest value: Class-Path=../../../patch_jars/BUG14331527_1036.jar ../../../patch_jars/com.bea.core.stax2_2.0.0.0_3-0-3.jar
New manifest value: Class-Path=../../../patch_jars/BUG16810786_1036.jar ../../../patch_jars/BUG14331527_1036.jar ../../../patch_jars/com.bea.core.stax2_2.0.0.0_3-0-3.jar
Result: Success
./bsu.sh -prod_dir=/<MW_HOME>/111/wlserver_10.3 -patch_download_dir=/<MW_HOME>/111/utils/bsu/cache_dir -status=applied -verbose -view
Checking for conflicts..
No conflict(s) detected
Starting installation of Patch ID: SK1V
Installing /<MW_HOME>/111/utils/bsu/cache_dir/SK1V.jar
Extracting /<MW_HOME>/111/patch_wls1036/patch_jars/BUG16810786_1036.jar
Updating /<MW_HOME>/111/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar
Old manifest value: Class-Path=../../../patch_jars/BUG14331527_1036.jar ../../../patch_jars/com.bea.core.stax2_2.0.0.0_3-0-3.jar
New manifest value: Class-Path=../../../patch_jars/BUG16810786_1036.jar ../../../patch_jars/BUG14331527_1036.jar ../../../patch_jars/com.bea.core.stax2_2.0.0.0_3-0-3.jar
Result: Success
$ ./bsu.sh -prod_dir=/<MW_HOME>/111/wlserver_10.3 -patch_download_dir=/<MW_HOME>/111/utils/bsu/cache_dir -status=applied -verbose -view
ProductName: WebLogic Server
ProductVersion: 10.3 MP6
Components: WebLogic Server/Core Application Server,WebLogic Server/Administration Console,WebLogic Server/Configuration Wizard and
Upgrade Framework,WebLogic Server/Web 2.0 HTTP Pub-Sub Server,WebLogic Server/WebLogic SCA,WebLogic Server/WebLogic JDBC
Drivers,WebLogic Server/Third Party JDBC Drivers,WebLogic Server/WebLogic Server Clients,WebLogic Server/WebLogic Web
S erver Plugins,WebLogic Server/UDDI and Xquery Support,WebLogic Server/Evaluation Database,WebLogic Server/Workshop Code
Completion Support
BEAHome: /<MW_HOME>/111
ProductHome: /<MW_HOME>/111/wlserver_10.3
PatchSystemDir: /<MW_HOME>/111/utils/bsu
PatchDir: /<MW_HOME>/111/patch_wls1036
Profile: Default
DownloadDir: /<MW_HOME>/111/utils/bsu/cache_dir
JavaVersion: 1.6.0_29
JavaVendor: Sun
Patch ID: MYFD
PatchContainer: MYFD.jar
Checksum: -133381619
Severity: optional
Category: General
CR/BUG: 14331527
Restart: true
Description: WLS PATCH SET UPDATE 10.3.6.0.2
.
Patch ID: SK1V
PatchContainer: SK1V.jar
Checksum: 58385918
Severity: optional
Category: Web App
CR/BUG: 16810786
Restart: true
Description: MEMORY LEAK ON COM.CERTICOM.TLS.INTERFACEIMPL.CERTIFICATESUPPORT
MEMORY LEAK ON COM.CERTICOM.TLS.INTERFACEIMPL.CERTIFICATESUPPORT
More on Fusion Middleware updates & issues http://confusionmiddleware.blogspot.com/
Caused by: weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 't3://hostname:port'
Trying to deploy custom code on weblogic server using ant but getting exception like below?
Caused by: weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 't3://hostname:port': User: custadmin , failed to be authenticated.. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.
Please check below points and apply configurations as required:
1) Ensure hostname, port and credentials are correct
2) Enable tunneling as required in weblogic console
- Login to weblogic console http://hostname:port/console
- Environmnets -> Server -> Select Sever
- Go to Protcols -> HTTP
- Check Enable Tunneling
- Apply changes
- No restart required
Strangely this 'authentication failed' exception did not disappear from build.log file after trying to deploy the code several times.
So tried another workaround. Created another admin user 'weblogic' in weblogic console with the same password as user custadmin and assigned it to administrators group.
Ran the deployment script again (after updating weblogic.username=weblogic in custom deployment config files) and there were no authentication failed exceptions seen.
Still wondering why authentication failed exception appeared for non weblogic user !!
Did you encounter such bizarre issue before? Do leave a comment if you faced similar issue and if you were able to resolve this.
