Error making initial connections for pool

          I'm using WLS6.1 on NT, trying my personal implementation of a connector (non
          CCI pattern) with a particular EIS.
          i'm having this error... what depends from?:
          ####<25-ott-00 19.52.41 CEST> <Info> <Connector> <semarmw0780> <examplesServer>
          <main> <system> <> <190014> <Initializing connection pool for resource adapter
          BlackBoxNoTx.>
          ####<25-ott-00 19.52.42 CEST> <Info> <Connector> <semarmw0780> <examplesServer>
          <main> <system> <> <190010> <Unable to determine Resource Principal for Container
          Managed Security Context.>
          ####<25-ott-00 19.52.42 CEST> <Info> <Connector> <semarmw0780> <examplesServer>
          <main> <system> <> <190035> <There was/were 1 physical connection(s) created with
          the following Meta Data: Product name of EIS instance: DBMS:cloudscape Product
          version of EIS instance: 3.5.1 Maximum number of connections supported from different
          processes: 0 User name for connection: null>
          ####<25-ott-00 19.52.42 CEST> <Info> <Connector> <semarmw0780> <examplesServer>
          <main> <system> <> <190026> << BlackBoxNoTx > Connection Pool initialization has
          completed successfully.>
          ####<25-ott-00 19.52.42 CEST> <Info> <Connector> <semarmw0780> <examplesServer>
          <main> <system> <> <190014> <Initializing connection pool for resource adapter
          SMJConnector.>
          ####<25-ott-00 19.52.42 CEST> <Info> <Connector> <semarmw0780> <examplesServer>
          <main> <system> <> <190010> <Unable to determine Resource Principal for Container
          Managed Security Context.>
          ####<25-ott-00 19.52.47 CEST> <Info> <Connector> <semarmw0780> <examplesServer>
          <main> <system> <> <190010> <Unable to determine Resource Principal for Container
          Managed Security Context.>
          ####<25-ott-00 19.53.06 CEST> <Error> <Connector> <semarmw0780> <examplesServer>
          <main> <system> <> <190024> << SMJConnector > Error making initial connections
          for pool. Reason: examplescnnct.ConnectionImpl>
          ####<25-ott-00 19.53.06 CEST> <Warning> <Connector> <semarmw0780> <examplesServer>
          <main> <system> <> <190025> << SMJConnector > Connection Pool has been initialized
          with no connections.>
          ####<25-ott-00 19.53.06 CEST> <Info> <Connector> <semarmw0780> <examplesServer>
          <main> <system> <> <190026> << SMJConnector > Connection Pool initialization has
          completed successfully.>
          ####<25-ott-00 19.54.30 CEST> <Info> <Connector> <semarmw0780> <examplesServer>
          <Application Manager Thread> <> <> <190027> << SMJConnector > Shutting down connections.>
          ####<25-ott-00 19.54.30 CEST> <Info> <Connector> <semarmw0780> <examplesServer>
          <Application Manager Thread> <> <> <190028> << SMJConnector > Connections shutdown
          successfully.>

Have you configured your principal map? Connection pools are initially populated using the
          default ("*") principal from the map.
          http://edocs.bea.com/wls/docs61/jconnector/config.html#1237429
          HTH.
          FilAiello wrote:
          > I'm using WLS6.1 on NT, trying my personal implementation of a connector (non
          > CCI pattern) with a particular EIS.
          >
          > <examplesServer>
          > <main> <system> <> <190010> <Unable to determine Resource Principal for Container
          > Managed Security Context.>
          > ####<25-ott-00 19.52.42 CEST> <Info> <Connector> <semarmw0780> <examplesServer>
          Tom Mitchell
          [email protected]
          Very Current Beverly, MA Weather
          http://www.tom.org:8080

Similar Messages

Unable to get a connection for pool - ResourceUnavailableException

Hi
I have a BPEL process which starts a child instance of another asynchronous BPEL process for each message in an XML file. The child BPEL process makes a call to the Oracle Apps JCA Adapter to push the data into E-Business Suite.
All works perfectly except when the number of messages exceeds a certain limit (15 or so). The error received is as follows:
"Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'SyncPersonRecord' failed due to:
JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection.
ebsPeoplesoftEmployees:SyncPersonRecord [ SyncPersonRecord_ptt::SyncPersonRecord(InputParameters,OutputParameters) ] :
The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue:
javax.resource.spi.ApplicationServerInternalException:
Unable to get a connection for pool = 'eis/Apps/Apps',
weblogic.common.resourcepool.ResourceUnavailableException:
No resources currently available in pool eis/Apps/Apps to allocate to applications.
Either specify a time period to wait for resources to become available, or increase the size of the pool and retry.. Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections.
Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections. ".
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution."
Obviously what is happening is the connection pool maximum is reached (currently 15) and this is throwing the error.
What I need to do is to implement the suggestion of "specifying a time period to wait" and I was hoping someone could tell me how I do this?
I have tried setting the 'Connection Creation Retry Frequency' parameter to 30 seconds which made no difference and also have checked the documentation on "Configuring and Managing JDBC Data Sources for Oracle WebLogic Server".
Does anyone know if this is something that is implemented directly in the BPEL process/composite or in the connection source itself.
Many thanks

Open the jndi : eis/Apps/Apps in /console - config tab - increase the initial and max conn capacity and save it. Retry the scenario

Using Ant task wlserver/wlconfig: Received exception while creating connection for pool.

Hi,
I am using ant tasks wlserver and wlconfig to configure my weblogic server. while creating a connection pool as shown below
<target name="jdbcinfo">
<wlconfig password="weblogic"
username="weblogic"
url="${url}"
<query domain="mydomain" type="Server"
name="myserver" property="serverbean"
/>
<create type="JDBCConnectionPool"
name="jdbcpoolA"
property="jdbcPoolProp">
<set value="false"
attribute="ShrinkingEnabled"
<set value
attribute="
<set value="${serverbean}"
attribute="Targets"/>
The JDBCConnectionPool is created as long as I don't specified the attribute "Targets"
Once I add the target I get the following error
<JDBC> <BEA-001129> <Received exception while creating connection for pool "poolname" invalid arguments in call>
Please any help will be greatly appreciated.
Thanks

In your applicaion module configurations check if you are using 'JDBC URL' or 'JDBC DataSource'. You should use JDBC DataSource. Then make sure that your deployment descriptor (menu 'Application->Application Properties->Deployment) has the 'Auto Generate ...' checkbox set.
Timo

Error: Missing initial value for session parameter

Hi,
I'm facing a problem while running the ETL process for Complete 11.5.10 Execution Plan in DAC Client. Some tasks are getting failed beacuse of the following error:-
ERROR : TM_6292 : (5080|4064) Session task instance [SDE_ORA_Product_Category_Derive_Full]: VAR_27026 [Error: Missing initial value for session parameter:[$DBConnection_OLAP].].
ERROR : TM_6292 : (5080|4064) Session task instance [SDE_ORA_Product_Category_Derive_Full]: CMN_1761 [Timestamp Event: [Mon Nov 19 21:01:52 2007]].
ERROR : TM_6292 : (5080|4064) Session task instance [SDE_ORA_Product_Category_Derive_Full]: TM_6270 [Error: Variable parameter expansion error.].
ERROR : TM_6292 : (5080|4064) Session task instance [SDE_ORA_Product_Category_Derive_Full]: CMN_1761 [Timestamp Event: [Mon Nov 19 21:01:52 2007]].
ERROR : TM_6292 : (5080|4064) Session task instance [SDE_ORA_Product_Category_Derive_Full]: TM_6163 [Error initializing variables and parameters for the paritition.].
ERROR : TM_6292 : (5080|4064) Session task instance [SDE_ORA_Product_Category_Derive_Full]: CMN_1761 [Timestamp Event: [Mon Nov 19 21:01:52 2007]].
ERROR : TM_6292 : (5080|4064) Session task instance [SDE_ORA_Product_Category_Derive_Full]: TM_6226 [ERROR: Failed to initialize session [SDE_ORA_Product_Category_Derive_Full]].
ERROR : LM_36320 [Mon Nov 19 21:02:08 2007] : (2108|2632) Session task instance [SDE_ORA_Product_Category_Derive_Full]: Execution failed.
When i checked the parameter file i can see the value assigned to the $DBConnection_OLAP. The same tasks ran successfully when i ran the ETL process for Complete 11.5.10 for the first time. I did not change anything after that and also all these are came built-in with the installation of Oracle BI Applications.
Please anyone give me an idea what is causing the problem.
Thanks,

in DAC > Run History > Task Details, query
Name = SDE_ORA_Product_Category_Temporary
Open Status Description, look for string -lpf, the file after it is the actual parameter file DAC send to INFA server. E.g
-lpf D:\DACTOPUS\Informatica\parameters\SDE_ORAR12_Adaptor.SDE_ORA_Product_Category_Temporary.txt
Open the parameter file, most likely the [session_name] does not match with SDE_ORA_Product_Category_Derive_Full or some parameters are missing.

Error Making Socket Connection

So, I'm trying to figure this out, I get this error after my code has compiled(Metrowerks CodeWarrior),the little dos run window comes up and afterwards I get this message "Error making socket connection". Anyone ever seen this? I'm running Windows 2000, CodeWarrior 5.0. Any ideas? Thanks

I've seen it when ive had an error making the socket connection!
Of course it was easier to fix my problem because I could see the code
and didnt have to guess it.

How do I set miminum # of connections for pool with Oracle and Tomcat?

Hi,
I can't seem to find any attribute to initialize the number of connections for my connection pool. Here is my current context.xml file under my /App1 directory:
<Context path="/App1" docBase="App1"
debug="5" reloadable="true" crossContext="true">
<Resource name="App1ConnectionPool" auth="Container"
type="oracle.jdbc.pool.OracleDataSource"
driverClassName="oracle.jdbc.driver.OracleDriver"
factory="oracle.jdbc.pool.OracleDataSourceFactory"
url="jdbc:oracle:thin:@127.0.0.1:1521:oddjob"
user="app1" password="app1" />
</Context>
I've been googling and reading forums, but haven't found a way to establish the minimum number of connections. I've tried all sorts of parameters like InitialLimit, MinLimit, MinActive, etc, with no success.
Here is some sample code that I am testing:
package web;
import oracle.jdbc.pool.OracleDataSource;
import oracle.jdbc.OracleConnection;
import javax.naming.*;
import java.sql.SQLException;
import java.sql.ResultSet;
import java.sql.Statement;
import java.util.Properties;
public class ConnectionPool {
String message = "Not Connected";
public void init() {
OracleConnection conn = null;
ResultSet rst = null;
Statement stmt = null;
try {
Context initContext = new InitialContext();
Context envContext = (Context) initContext.lookup("java:/comp/env");
OracleDataSource ds = (OracleDataSource) envContext.lookup("App1ConnectionPool");
message = "Here.";
     String user = ds.getUser();
if (envContext == null)
throw new Exception("Error: No Context");
if (ds == null)
throw new Exception("Error: No DataSource");
if (ds != null) {
message = "Trying to connect...";
conn = (OracleConnection) ds.getConnection();
Properties prop = new Properties();
prop.put("PROXY_USER_NAME", "adavey/xxx");
if (conn != null) {
message = "Got Connection " + conn.toString() + ", ";
          conn.openProxySession(OracleConnection.PROXYTYPE_USER_NAME,prop);
stmt = conn.createStatement();
rst = stmt.executeQuery("SELECT username, server from v$session where username is not null");
while (rst.next()) {
message = "DS User: " + user + "; DB User: " + rst.getString(1) + "; Server: " + rst.getString(2);
rst.close();
rst = null;
stmt.close();
stmt = null;
conn.close(); // Return to connection pool
conn = null; // Make sure we don't close it twice
} catch (Exception e) {
e.printStackTrace();
} finally {
// Always make sure result sets and statements are closed,
// and the connection is returned to the pool
if (rst != null) {
try {
rst.close();
} catch (SQLException e) {
rst = null;
if (stmt != null) {
try {
stmt.close();
} catch (SQLException e) {
stmt = null;
if (conn != null) {
try {
conn.close();
} catch (SQLException e) {
conn = null;
public String getMessage() {
return message;
I'm using a utility to repeatedly call a JSP page that uses this class and displays the message variable. This utility allows me to specify the number of concurrent web requests and an overall number of requests to try. While that is running, I look at V$SESSION in Oracle and occassionaly, I will see a brief entry for app1 or adavey depending on the timing of my query and how far along the code has processed in this example. So it seems that I am only using one connection at a time and not a true connection pool.
Is it possible that I need to use the oci driver instead of the thin driver? I've looked at the javadoc for oci and the OCIConnectionPool has a setPoolConfig method to set initial, min and max connections. However, it appears that this can only be set via Java code and not as a parameter in my context.xml resource file. If I have to set it each time I get a database connection, it seems like it sort of defeats the purpose of having Tomcat maintain the connection pool for me and that I need to implement my own connection pool. I'm a newbie to this technology so I really don't want to go this route.
Any advice on setting up a proper connection pool that works with Tomcat and Oracle proxy sessions would be greatly appreciated.
Thanks,
Alan

Well I did some more experiments and I am able to at least create a connection pool within my example code:
package web;
import oracle.jdbc.pool.OracleDataSource;
import oracle.jdbc.OracleConnection;
import javax.naming.*;
import java.sql.SQLException;
import java.sql.ResultSet;
import java.sql.Statement;
import java.util.Properties;
public class ConnectionPool {
String message = "Not Connected";
public void init() {
OracleConnection conn = null;
ResultSet rst = null;
Statement stmt = null;
try {
Context initContext = new InitialContext();
Context envContext = (Context) initContext.lookup("java:/comp/env");
OracleDataSource ds = (OracleDataSource) envContext.lookup("App1ConnectionPool");
message = "Here.";
     String user = ds.getUser();
if (envContext == null)
throw new Exception("Error: No Context");
if (ds == null)
throw new Exception("Error: No DataSource");
if (ds != null) {
message = "Trying to connect...";
boolean cache_enabled = ds.getConnectionCachingEnabled();
if (!cache_enabled){
ds.setConnectionCachingEnabled(true);
Properties cacheProps = new Properties();
cacheProps.put("InitialLimit","5");
     cacheProps.put("MinLimit","5");
cacheProps.put("MaxLimit","10");
ds.setConnectionCacheProperties(cacheProps);
          conn = (OracleConnection) ds.getConnection();
Properties prop = new Properties();
prop.put("PROXY_USER_NAME", "adavey/xyz");
if (conn != null) {
message = "Got Connection " + conn.toString() + ", ";
          conn.openProxySession(OracleConnection.PROXYTYPE_USER_NAME,prop);
stmt = conn.createStatement();
//rst = stmt.executeQuery("SELECT 'Success obtaining connection' FROM DUAL");
rst = stmt.executeQuery("SELECT user, SYS_CONTEXT ('USERENV', 'SESSION_USER') from dual");
while (rst.next()) {
message = "DS User: " + user + "; DB User: " + rst.getString(1) + "; sys_context: " + rst.getString(2);
message += "; Was cache enabled?: " + cache_enabled;
rst.close();
rst = null;
stmt.close();
stmt = null;
conn.close(OracleConnection.PROXY_SESSION); // Return to connection pool
conn = null; // Make sure we don't close it twice
} catch (Exception e) {
e.printStackTrace();
} finally {
// Always make sure result sets and statements are closed,
// and the connection is returned to the pool
if (rst != null) {
try {
rst.close();
} catch (SQLException e) {
rst = null;
if (stmt != null) {
try {
stmt.close();
} catch (SQLException e) {
stmt = null;
if (conn != null) {
try {
conn.close();
} catch (SQLException e) {
conn = null;
public String getMessage() {
return message;
In my context.xml file, I tried to specify the same Connection Cache Properties as attributes, but no luck:
<Context path="/App1" docBase="App1"
debug="5" reloadable="true" crossContext="true">
<Resource name="App1ConnectionPool" auth="Container"
type="oracle.jdbc.pool.OracleDataSource"
driverClassName="oracle.jdbc.OracleDriver"
factory="oracle.jdbc.pool.OracleDataSourceFactory"
url="jdbc:oracle:thin:@127.0.0.1:1521:oddjob"
user="app1" password="app1"
ConnectionCachingEnabled="1" MinLimit="5" MaxLimit="20"/>
</Context>
These attributes seemed to have no effect:
ConnectionCachingEnabled="1" ; also tried "true"
MinLimit="5"
MaxLimit="20"
So basically if I could find some way to get these attributes set within the context.xml file instead of my code, I would be a happy developer :-)
Oh well, it's almost Miller time here on the east coast. Maybe a few beers will help me find the solution I'm looking for.

Getting Error:closing a connection for you. Please help

Hello All,
I'm using jboss3.2.6. I used ejb2.1 (session bean and entity bean[BMP]). I did few data base transations in cmp and few in simple data source connection.
I'm getting below errors occasionally
'No managed connection exception
java.lang.OutOfMemoryError: Java heap space
[CachedConnectionManager] Closing a connection for you. Plea
se close them yourself: org.jboss.resource.adapter.jdbc.WrappedConnection@11ed0d
5
I've given below my dao connection code here,
package com.drtrack.util;
import java.sql.Connection;
import java.sql.SQLException;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.sql.DataSource;
public class DAOUtil {
private static DataSource _ds;
public Connection con;
public DAOUtil() throws SQLException {
try {
if (_ds == null)
assemble();
if(_ds != null && con == null) {
con = _ds.getConnection();
}catch(SQLException ex) {
ex.printStackTrace();
private void assemble() {
Context ic = null;
try {
ic = new InitialContext();
DrTrackUtil drutil = new DrTrackUtil();
_ds = (DataSource) ic.lookup("java:/" + drutil.getText("SOURCE_DIR"));
drutil = null;
}catch (Exception e) {
e.printStackTrace();
}finally {
try {
ic.close();
}catch(NamingException ne) {}
public void closeConnection() throws SQLException {
if(con != null)
con.close();
con = null;
}below is the code with get connection and doing transaction in it.
public static AccountMasterValueBean getAccountMasterByAcctId(String acctId) {
AccountMasterValueBean bean = null;
DAOUtil dao = null;
CallableStatement cst = null;
ResultSet rs = null;
try {
dao = new DAOUtil();
cst = dao.con.prepareCall(DrTrackConstants.MSSQL_USP_ACCOUNTMASTER_BY_ACCTID);
cst.setObject(1, acctId);
rs = cst.executeQuery();
if(rs != null && rs.next()) {
bean = new AccountMasterValueBean(
Integer.valueOf(rs.getString("accountkeyid")),
rs.getString("latitude"),
rs.getString("longitude"));
}catch(SQLException se) {
logger.info("SQL Error: " + se);
finally {
if(rs != null){
try {
rs.close();
}catch(SQLException se) {
logger.info("SQL Error: " + se);
finally {
rs = null;
if(cst != null) {
try{
cst.close();
}catch(SQLException se) {
logger.info("SQL Error: " + se);
finally {
cst = null;
if(dao != null) {
try {
dao.closeConnection();
}catch(SQLException se) {
logger.info("SQL Error: " + se);
finally {
dao = null;
return bean;
}I closed connections, resultsets and statements properly.
Why I'm getting these errors.? Where I'm doing wrong. ? Please help me. I have to fix them ASAP.
Thanks.

Hello All,
I'm using jboss3.2.6. I used ejb2.1 (session bean and entity bean[BMP]). I did few data base transations in cmp and few in simple data source connection.
I'm getting below errors occasionally
'No managed connection exception
java.lang.OutOfMemoryError: Java heap space
[CachedConnectionManager] Closing a connection for you. Plea
se close them yourself: org.jboss.resource.adapter.jdbc.WrappedConnection@11ed0d
5
I've given below my dao connection code here,
package com.drtrack.util;
import java.sql.Connection;
import java.sql.SQLException;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.sql.DataSource;
public class DAOUtil {
private static DataSource _ds;
public Connection con;
public DAOUtil() throws SQLException {
try {
if (_ds == null)
assemble();
if(_ds != null && con == null) {
con = _ds.getConnection();
}catch(SQLException ex) {
ex.printStackTrace();
private void assemble() {
Context ic = null;
try {
ic = new InitialContext();
DrTrackUtil drutil = new DrTrackUtil();
_ds = (DataSource) ic.lookup("java:/" + drutil.getText("SOURCE_DIR"));
drutil = null;
}catch (Exception e) {
e.printStackTrace();
}finally {
try {
ic.close();
}catch(NamingException ne) {}
public void closeConnection() throws SQLException {
if(con != null)
con.close();
con = null;
}below is the code with get connection and doing transaction in it.
public static AccountMasterValueBean getAccountMasterByAcctId(String acctId) {
AccountMasterValueBean bean = null;
DAOUtil dao = null;
CallableStatement cst = null;
ResultSet rs = null;
try {
dao = new DAOUtil();
cst = dao.con.prepareCall(DrTrackConstants.MSSQL_USP_ACCOUNTMASTER_BY_ACCTID);
cst.setObject(1, acctId);
rs = cst.executeQuery();
if(rs != null && rs.next()) {
bean = new AccountMasterValueBean(
Integer.valueOf(rs.getString("accountkeyid")),
rs.getString("latitude"),
rs.getString("longitude"));
}catch(SQLException se) {
logger.info("SQL Error: " + se);
finally {
if(rs != null){
try {
rs.close();
}catch(SQLException se) {
logger.info("SQL Error: " + se);
finally {
rs = null;
if(cst != null) {
try{
cst.close();
}catch(SQLException se) {
logger.info("SQL Error: " + se);
finally {
cst = null;
if(dao != null) {
try {
dao.closeConnection();
}catch(SQLException se) {
logger.info("SQL Error: " + se);
finally {
dao = null;
return bean;
}I closed connections, resultsets and statements properly.
Why I'm getting these errors.? Where I'm doing wrong. ? Please help me. I have to fix them ASAP.
Thanks.

Error while creating connection for Application server in Jdeveloper

Hi,
I am trying to create a new connection for my weblogic server from JDeveloper
I am using weblogic 6.1
The error is :javax.naming.AuthenticationException [Root exception is java.lang.SecurityException : attemting to add an object which is not an instance 0f java.security.Principal to a subject's Principal set
I am currectly passing my userID and password. but still it is giving the above exception.
Please advise me.
With thanks
Murthy

HI
In JDeveloper 10.1.3.1.0,
1. Click on the tab for the Connections navigator.
2. Right click on Application Server and select New Application Server Connection.
3. Enter a descriptive name for the new connection, and select the appropriate connection type from the drop down list. Click Next.
4. Specify oc4jadmin for User Name, then enter the oc4jadmin password. Click Next.
5. Select Single Instance for Connect To, then provide the host name where BPEL is installed, the OPMN port number, and the OC4J instance name (the default for 10.1.3.1 is oc4j_soa). Click Next.
6. Click Test Connection. If you have been successful, you should see "Success!"
7. Now, right click on Integration Server and select New Integration Server Connection.
8. Specify a connection name and click Next.
9. In the drop down list by Application Server, select the Application Server Connection you just created. Again, specify the host name where BPEL is installed and the port number. This port number will be the same that you specified for the Integration Server Connection to the home OC4J container. Click Next.
10. Test the connection. You should see something like:
Application Server: OK
BPEL Process Manager Server: OK
ESB Server: OK
11. Now, return to the Applications navigator, and try to redeploy your process using the Integration Server Connection just created. (It is possible that you will have to close JDeveloper and then reopen it for this to work.)
Cheers
Anirudh Pucha

Error while initializing UME for standalone scenario

What this error indicates. Where I can find this class. which jar file is required. Please help me. It's very urgent.
An error occurred while initializing UME for standalone scenario.
java.lang.reflect.InvocationTargetException: java.lang.NoClassDefFoundError: com/sap/util/cache/exception/CacheException
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Unknown Source)
        at com.sap.security.core.InternalUMFactory.class$(InternalUMFactory.java:80)
        at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:275)
        at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:563)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.sap.security.api.UMFactory.initialize(UMFactory.java:489)
        at TroubleShootUtility.main(TroubleShootUtility.java:101)
com.sap.security.api.UMRuntimeException: An error occurred while initializing UME for standalone scenario.
        at com.sap.security.api.UMFactory.initialize(UMFactory.java:501)
        at TroubleShootUtility.main(TroubleShootUtility.java:101)
Nested Exception:
java.lang.reflect.InvocationTargetException: java.lang.NoClassDefFoundError: com/sap/util/cache/exception/CacheException
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Unknown Source)
        at com.sap.security.core.InternalUMFactory.class$(InternalUMFactory.java:80)
        at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:275)
        at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:563)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.sap.security.api.UMFactory.initialize(UMFactory.java:489)
        at TroubleShootUtility.main(TroubleShootUtility.java:101)
Thanks.

Hi,
We are using ABAP and data is getting stored in MS SQL Server Database.
Thanks.

How to set min & max connections for MSSQLconnection pool

Hi,
I want to set minconnection, maxconnection, idletimeout initial limit for the pool
I have got a MSSQL database connection using following java code.
// MSSQL DbConnection Code
import java.sql.*;
public class MsSqlDataSource
public static void main(String arr[])
Connection con = null;
ResultSet rs = null;
try{
com.microsoft.sqlserver.jdbc.SQLServerDataSource ds = new com.microsoft.sqlserver.jdbc.SQLServerDataSource();
ds.setServerName("10.50.50.51");
ds.setPortNumber(1711);
ds.setDatabaseName("test");
ds.setUser("starhome");
ds.setPassword("starhome");
con = ds.getConnection();
}catch(Exception e){}
}In oracle i have passed min and max number of connection properties through setConnectionCacheProperties method.
//Connection Pooling using Oracle Data Source:
m_connSource = new OracleDataSource();
m_connSource.setDriverType("thin");
m_connSource.setServerName(m_host);
m_connSource.setNetworkProtocol("tcp");
m_connSource.setDatabaseName(m_db);
m_connSource.setPortNumber(m_port);
m_connSource.setUser(m_user);
m_connSource.setPassword(m_password);
// Enable caching. m_connSource.setConnectionCachingEnabled(true);
java.util.Properties prop = new java.util.Properties();
prop.setProperty("MinLimit", m_minConnections);
prop.setProperty("MaxLimit", m_maxConnections);
prop.setProperty("InitialLimit", m_initialConnections);
prop.setProperty("InactivityTimeout", m_inactivityTimeout);
prop.setProperty("AbandonedConnectionTimeout", m_abandonedTimeout);
prop.setProperty("ConnectionWaitTimeout", m_connWaitTimeout);
m_connSource.setConnectionCacheProperties(prop);I dont know how to pass min and max number of connection properties for SQLServerDataSource. Is there any method available to pass min and max number of connection properties for SQLServerDataSource.
Iam using Tomcat. I found one way to set min and max connections for pool by doing changes in context.xml and web.xml using below url http://tomcat.apache.org/tomcat-4.1-doc/jndi-datasource-examples-howto.html
I dont want to touch tomcat configuration files. I need to set connection pooling properties which is independent of application server.
Please anybody give solution for this?
Thanks,
Prisha

Hi,
you need to define your database under the DB Admin tab. In the Schema objects node you'll find Sequence Implementations, and there you can definde min max values as well as caching and increments.
Gerald

ISA B2B logon Error: No valid private connection for internet user

Hello ,
i used isauseradm to create a user zzweb with all authorizations for B2B..
now when i try to log to
http://host:port/b2b/b2b/init.do with the user zzweb
i have a runtime error with the logs :
EXCEPTION]
#1#com.sap.isa.businessobject.BORuntimeException: Error getting private connection for internet user:com.sap.isa.core.eai.BackendException: Error: No valid private connection for internet userzzweb
     at com.sap.isa.businessobject.BusinessObjectHelper.splitException(BusinessObjectHelper.java:78)
     at com.sap.isa.user.businessobject.UserBase.login(UserBase.java:313)
     at com.sap.isa.businessobject.User.login(User.java:143)
     at com.sap.isa.user.action.UserActions.performLogin(UserActions.java:295)
     at com.sap.isa.user.action.UserActions.performLogin(UserActions.java:368)
     at com.sap.isa.user.action.UserBaseAction.performLogin(UserBaseAction.java:126)
     at com.sap.isa.user.action.LoginBaseAction.ecomPerform(LoginBaseAction.java:77)
     at com.sap.isa.isacore.action.EComBaseAction.doPerform(EComBaseAction.java:353)
     at com.sap.isa.core.BaseAction.execute(BaseAction.java:211)
     at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
     at com.sap.isa.core.RequestProcessor.processActionPerform(RequestProcessor.java:674)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
     at com.sap.isa.core.RequestProcessor.process(RequestProcessor.java:391)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
     at com.sap.isa.core.ActionServlet.process(ActionServlet.java:243)
     at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
     at com.tealeaf.capture.LiteFilter.doFilter(Unknown Source)
     at com.sap.isa.isacore.TealeafFilter.doFilter(TealeafFilter.java:61)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:373)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
what does this error means..?
i also realised that zzweb was not created in CRM backen? should it be created ?
many thnx for help ..
Message was edited by: Blackman

Its a late response... but if someone gets the same issue here is the solution.
When you register try uppercase password . That should take care of that issue.
The problem is with function module CRM_ISA_IUSER_SWITCH , Note 946536.
Although the note says 5.0 the problem exists with ISA 4.0 too

Weblogic datasource - Created "1" resources for pool "DataSource", out of which "1" are available and "0" are unavailable.

I am performing some transactions with java application deployed on weblogic. I faced some issue of getting the transaction response with some delay. I found these below mention messages logged into the managed server logs.
Following is my datasource settings
Initial Capacity: 2
Maximum Capacity: 100
Capacity Increment: 20
Anyone have idea why these following errors coming.
####<Nov 26, 2013 2:25:41 PM PKT> <Info> <Common> <machine1> <managed_server> <[ACTIVE] ExecuteThread: '25' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <BEA1-1B6BE1217D118A188C49> <> <1385457941513> <BEA-000628> <Created "1" resources for pool "DataSource", out of which "1" are available and "0" are unavailable.>
####<Nov 26, 2013 2:25:42 PM PKT> <Info> <Common> <machine1> <managed_server> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <BEA1-1B6EE1217D118A188C49> <> <1385457942413> <BEA-000628> <Created "1" resources for pool "DataSource", out of which "1" are available and "0" are unavailable.>
####<Nov 26, 2013 2:25:43 PM PKT> <Info> <Common> <machine1> <managed_server> <[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <BEA1-1B71E1217D118A188C49> <> <1385457943792> <BEA-000628> <Created "1" resources for pool "DataSource", out of which "1" are available and "0" are unavailable.>
####<Nov 26, 2013 3:12:28 PM PKT> <Info> <JDBC> <machine1> <managed_server> <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1385460748433> <BEA-001128> <Connection for pool "DataSource" closed.>
####<Nov 26, 2013 3:12:28 PM PKT> <Info> <JDBC> <machine1> <managed_server> <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1385460748433> <BEA-001128> <Connection for pool "DataSource" closed.>
####<Nov 26, 2013 3:12:28 PM PKT> <Info> <JDBC> <machine1> <managed_server> <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1385460748433> <BEA-001128> <Connection for pool "DataSource" closed.>
####<Nov 26, 2013 3:12:28 PM PKT> <Info> <JDBC> <machine1> <managed_server> <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1385460748434> <BEA-001128> <Connection for pool "DataSource" closed.>

i know this,
The cause of the problem is: owing to the client's operations staff to modify the datasource ,and reployed
thinks

Wrapper connection for jboss exception

Hi
The url below says how to extract a Oracle type Connection from JBOSS Wrapper
"http://forums.oracle.com/forums/thread.jspa?messageID=1384788 "
No problem is getting the connection, but Do Not know hoe to close the same for the obtained
connection to be returned
Exception : "CAN'T CLOSE CONNECTION FOR POOL " is thrown ?
The code is as given below
* To get a connection
private WrappedConnection WCP = null;
public synchronized Connection getConnection() {
Connection conn = null;
OracleConnection connection;
try {
WCP = (WrappedConnection) ODS.getConnection();
connection = (OracleConnection) WCP.getUnderlyingConnection();
} catch (SQLException sqlex) {
System.out.println("<<<<<<<<<<< NO CONNECTION>>>>>>>>>>>>");
//sqlex.printStackTrace();
return conn;
* Return the Connection to Connectioon pool
public synchronized void freeConnection(Connection con) throws Exception {
System.out.println("RELEASING THE USED CONNECTION TO POOL");
try {
con.close();
}catch (Exception ex) {
System.out.println("CAN'T CLOSE CONNECTION FOR POOL ");
ex.printStackTrace();
Any help would be appreciated
SPEC
JBOSS 4.2.1
ORACLE DB : 10G DB
jar : ojdbc14.jar
j2sdk 1.4 for development
j2sdk1.6 for jboss runtime
with regards
Karthik
Edited by: user6161490 on Nov 25, 2008 8:40 PM

Well, it would be good if you showed us what exception was printed out when
you failed to close 'con'... Also, your getConnection() seems to return an unset
variable, not what you unwrapped.... And if you put the WCP variable in the
method, it won't have to be synchronized...
Edited by: [email protected] on Nov 26, 2008 8:22 AM

Fatal error while filling connection pool

I was not getting a connection to an Oracle database and I was getting the following error in cms.log: "FATAL Connector - Unable to create connection pool for T_Orbis_Oracle: Fatal error while filling connection pool for jdbc:oracle:thin:@MESDB:1521:ASPENB21" where T_Orbis_Oracle is the xMII link name and the database ASPENB21 is on server MESDB. I changed the database username in the link to SYSTEM and I then got a connection and a Created Connection pool message in the log. I then changed back to the username which originally was giving the error and it now also gave me a successful connection. I am now worried that there is an issue in the background which is gradually building up and will begin to fail again as previously. Can anyone explain what is causing this problem and suggest how I can correct it? Thanks, John.

John,
Check you have installed the JDBC driver ojdbc14.jar (works for both 9 and 10).
Also check the server package:
MII 11.x--->ServerPackage com.lighthammer.Illuminator.connectors.IDBC
MII 12.x--->com.sap.xmii.Illuminator.connectors.IDBC
Carefull when you set up the string because some oracle databases have servicenames instead of SID, and the url was different if you use them instead of the SID.
For services names the url is jdbc:oracle:thin@host:port:SID
Also check your Network firewall between MII and DB and ports too.
Oracle9i installs with a number of default accounts.You must unlock all other accounts before using them. Oracle recommends changing all user passwords immediately after installation.
-Suresh
Edited by: Suresh Hiremath on Jul 29, 2009 8:20 AM

Exception occurred. Internal error: Cannot obtain XAConnection Creation of XAConnection for pool....

Weblogic Server 6.1 SP2 is running fine. But unable to get XAConnections! I am getting following error
java.sql.SQLException: Internal error: Cannot obtain XAConnection Creation of XAConnection for pool ibesXaConnection Pool failed after waitSecs:300
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1063)
at weblogic.jdbc.jta.Connection.getXAConn(Connection.java:148)
at weblogic.jdbc.jta.Connection.prepareStatement(Connection.java:236)
at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:76)
-GoutamG

Hi Gautam!
Please make sure your refresh minutes is turned off in config.xml. You should put very large value like 999999 for RefreshMinutes parameter for
defination of connectionpool in config.xml instead of 0.
Thanks,
Mitesh
Goutam wrote:
Weblogic Server 6.1 SP2 is running fine. But unable to get XAConnections! I am getting following error
java.sql.SQLException: Internal error: Cannot obtain XAConnection Creation of XAConnection for pool ibesXaConnection Pool failed after waitSecs:300
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1063)
at weblogic.jdbc.jta.Connection.getXAConn(Connection.java:148)
at weblogic.jdbc.jta.Connection.prepareStatement(Connection.java:236)
at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:76)
-GoutamG

Error making initial connections for pool

Similar Messages

Maybe you are looking for