Windows Service Enterprise Library Data Access Application Blocks Connection Pooling Issue

Hello,
We are developing a windows service using c# .net v 4.5.1 which communicates with SQL database (SQL 2008 R2 x64), communication with SQL server is done using Enterprise Library data access block v 6, The windows service does a file copy process in bulk &
updates the database about the status of file copy, it is observed that as soon as we start the service the number of connections get max out & we start receiving a "Timeout expired. The timeout period elapsed prior to obtaining a connection
from the pool. This may have occurred because all pooled connections were in use and max pool size was reached."
This issue is only observed when we run the code logic by deploying it as a windows service, When we run the exactly same code as a standalone exe (right click -> run as administrator) / non windows service, the connections on database are not exceeded
& we do not receive the above mentioned error.
The code block which makes calls to the database is under the c# "using" statement, hence connection pooling should be handled by default.
Could you please recommend any suggestions on areas which I might have missed on to investigate this issue.
Thanks in advance.

Hi
The issue got resolved after refresh the SCOM Data base access service account in SQL 2012.
Unable to launch the operations manager 2012 R2 console after extended the C drive of the SQl server ,getting error "The Data
Access service is either not
running or not yet initialized.
Got to your SQL server -->databases-operationsmanager--security-users--locate the daa service account and refresh.issue fixed and am able to luanch.

Similar Messages

Data Access Application Block

Is there any talk of doing a Oracle version of Data Access Application Block for .NET?
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/daab-rm.asp

Initial implementation here:
http://forums.oracle.com/forums/thread.jspa?threadID=267373
Hasn't been updated since I last posted to it though. I couldn't convince my boss to use ODP.Net so haven't looked at this any further.

Issue with Enterprise Library's Data Access Application

I do not know if I have the correct forum for this post. I hve put it in what I believe is the most likely best forum, but please move this if there is a more germane forum for it.
I have inherited a solution (C#) which uses the reference Microsoft.Practices.EnterpriseLibrary.Data. The reference was included with the codebase I inherited, there are no missing references.
When the library is called with:
Microsoft.Practices.EnterpriseLibrary.Data.ExecuteDataSet("configConfigurationKeysSelect", parameterValues);
It complains with the runtime error:
[InvalidOperationException: The stored procedure 'configConfigurationKeysSelect' doesn't exist.] (I have put the full trace below)
This is true, there IS no stored procedure  'configConfigurationKeysSelect' but there is a table named  'configConfigurationKeys.'
I assumed this stored procedure is built on the fly to select from that table? Must I do something regarding  Enterprise Library's Data Access Application so that this works on the system I am running it on? (I am simply accessing the references
included with the sourced for this, nothing else). I am looking for some guidance here, and thanks in advance.
Stack trace on error as:
[InvalidOperationException: The stored procedure 'configConfigurationKeysSelect' doesn't exist.]   System.Data.SqlClient.SqlCommand.DeriveParameters() +5344249
System.Data.SqlClient.SqlCommandBuilder.DeriveParameters(SqlCommand command) +115
Microsoft.Practices.EnterpriseLibrary.Data.Sql.SqlDatabase.DeriveParameters(DbCommand discoveryCommand) +72
Microsoft.Practices.EnterpriseLibrary.Data.Database.DiscoverParameters(DbCommand command) +251
Microsoft.Practices.EnterpriseLibrary.Data.ParameterCache.SetParameters(DbCommand command, Database database) +225
Microsoft.Practices.EnterpriseLibrary.Data.Database.AssignParameters(DbCommand command, Object[] parameterValues) +53
Microsoft.Practices.EnterpriseLibrary.Data.Database.GetStoredProcCommand(String storedProcedureName, Object[] parameterValues) +161
Microsoft.Practices.EnterpriseLibrary.Data.Database.ExecuteDataSet(String storedProcedureName, Object[] parameterValues) +70
Enterprise Library's Data Access Application

This is true, there IS no stored procedure  'configConfigurationKeysSelect' but there is a table named  'configConfigurationKeys.'
I assumed this stored procedure is built on the fly to select from that table? Must I do something regarding  Enterprise Library's Data Access Application so that this works on the system I am running it on? (I am simply accessing the references
included with the sourced for this, nothing else). I am looking for some guidance here, and thanks in advance.
Why do you assume that a stored procedure is create on the fly? Looking at the documentation for this component, I don't see a mention of such.
Dan Guzman, SQL Server MVP, http://www.dbdelta.com

Oracle Application server connection pool and database links

I am using Oracle application server 10g with connection pools, the db used by the application connects to another oracle db using a database link. My question is when the application starts it creates 10 connections, does it also create x amount of database links as well?

Hi,
Is there any way to use the connection pool or Datasource while connecting to database?If I am using a stateless sesssion bean and using a Data Access layer which just creates a database session to write the persistence toplink objects how I can make use of application server connection pool?Hi Vinod,
Yes, TopLink allows you to use the app server's connection pooling and transaction services. Chapter 2 of the Oracle9iAS TopLink Foundation Library Guide provides details as do the TopLink examples. The easiest way to set this up is by using the sessions.xml file. The sample XML below is from the file <toplink903>\examples\ias\examples\ejb\sessionbean\sessions.xml. Here we are adding the datasource defined in OC4J and specifying that we are using the OC4J transaction controller also.
<login>
<user-name>sa</user-name>
<password></password>
<datasource>java:comp/env/jdbc/ejbJTSDataSource</datasource>
<uses-external-transaction-controller>true</uses-external-transaction-controller>
<uses-external-connection-pool>true</uses-external-connection-pool>
</login>
<external-transaction-controller-class>oracle.toplink.jts.oracle9i.Oracle9iJTSExternalTransactionController</external-transaction-controller-class>
When using this approach you need to change your TopLink code slightly in the EJB methods:
a. Acquire the ACTIVE unit of work from the server
session (again, see the EmployeeSessionEJB code
example) with something like:
UnitOfWork uow = clientSession.getActiveUnitOfWork();
b. Calls to uow.commit() can be ommitted or commented out
because the EJB will handle this. Note that of course
the methods you create in the EJB that are using this
approach must have TX Required (default).
Hope this helps.
Pete

KIMYONG : Applications Database Connection Pool 관련 parameter 설명

Purpose
JVM 이 과도한 CPU / Memory를 사용하게 되어 Application Performance에 영향을 미칠때가 있으며 이럴경우 Connection Pool 관련하여 Parameter Tunning을 해야 할때가 있습니다. 이때 사용되는 Parameter들의 의미를 설명하고자 합니다.
The Applications Database Connection Pool is a pool of JDBC database connections that are shared among java applications. Applications obtain connections from the pool by using the getJDBCConnection(...) methods of AppsContext.
Essentially, each AppsContext has a single database connection associated with it at all times.
The AOL/J layer internally borrows and returns this connection to the pool as needed to maintain connection reference that is properly initialized for the current Java tier AOL security context and NLS state.
FND_MAX_JDBC_CONNECTIONS
============================
The maximum pool size is the maximum allowed sum of the number of available connections and thenumber of locked connections. If the pool reaches the maximum size and all connections are locked, new clients will not be able to borrow a connection until one of the current clients has returned one. The default setting for this parameter is essentially unlimited (about 2 billion).
FND_JDBC_BUFFER_MIN
======================
The buffer minimum is the minimum number of connections that the pool should try to maintain in the available list. When the buffer size falls below the buffer minimum, the pool maintenance thread will be notified to create new connections. When notified, the thread will immediately attempt to create the number of connections to fill the difference. New connections will not be created if the pool is already at its maximum size. When creating new connections the thread uses the attributes of the most recent client request that resulted in a new connection being created.
Setting this parameter to "0" will disable maintenance of the buffer minimum.
However, the buffer maximum will still be maintained.
Setting this parameter to a number greater than the maximum pool size(FND_MAX_JDBC_CONNECTIONS) will disable all buffer maintenance.
FND_JDBC_BUFFER_MAX
======================
The buffer maximum is the maximum number of connections that the pool should try to maintain in the available list. During heavy usage, the buffer may exceed this maximum. However, during periods of low usage, the maintenance thread will decrease the buffer size until the buffer maximum is reached.
If the value of this parameter is an integer, (for example "20") the buffer maximum is static. If the value is a percent (for example, "20%"), the buffer maximum is not constant but instead is calculated dynamically as a percent of total pool size. The buffer minimum is also taken into account when
determining a dynamic buffer maximum.
The exact expression used is:
maximum(t) = buffer minimum + ( (FND_JDBC_BUFFER_MAX/100) * size(t) )
where maximum(t) and size(t) are the buffer maximum and pool size at some time t.
The thread is configured to periodically check the buffer size. If the buffer size is greater than the maximum, the thread will remove either the number of available connections specified by FND_JDBC_BUFFER_DECAY_SIZE or the number of connections in excess of the buffer minimum, whichever is smaller. When connections are removed from the available list, the least recently used ones are removed first.
Setting this parameter to100%, or to a number equal to FND_MAXIMUM_JDBC_CONNECTIONS, or to a number less than or equal to FND_JDBC_BUFFER_MIN will effectively prevent the maintenance thread from ever removing any connections.
FND_JDBC_BUFFER_DECAY_INTERVAL
===================================
The buffer decay interval specifies how often the connection pool maintenance thread should check the buffer size. The thread will check the buffer size at most once every FND_JDBC_BUFFER_DECAY_INTERVAL seconds. The actual time between consecutive thread cycles will vary somewhat depending on the JVM load.
This parameter, along with FND_JDBC_BUFFER_DECAY_SIZE, allows the buffer decay rate to be tuned. For example, if the buffer decay size is 2 and the buffer decay interval is one minute, the buffer decay rate will never exceed two connections per minute. When connections are removed, the least recently used ones are removed first.
FND_JDBC_BUFFER_DECAY_SIZE
=============================
The buffer decay size specifies the maximum number of connections that should be removed during any single thread cycle during which the number of available connections is greater than the buffer size. This parameter, along with FND_JDBC_BUFFER_DECAY_INTERVAL, allows the buffer decay rate to be tuned.
FND_JDBC_MAX_WAIT_TIME
=========================
The maximum wait time specifies how much time a client should spend trying to get a connection. The borrow algorithm, used to borrow an object from the pool, contains check points at which the elapsed time is compared to the maximum wait time. If it exceeds the maximum wait time, then a null object will be returned to the client. The pre-configured value for the maximum wait time is
10 seconds.
FND_JDBC_SELECTION_POLICY
============================
The selection policy determines how a connection is selected from the list of available connections for a particular client. The connection pool is pre-configured to use a cost-based selection algorithm, which selects the connection that will require the smallest amount of initialization to match the
client's context.
FND_JDBC_USABLE_CHECK
===========================
The FND_JDBC_USABLE_CHECK parameter governs whether a pl/sql query is performed before giving a connection to a client. The pool checks whether a connection is usable before handing it to a client. This always involves checking that the connection is not null and is not closed. If FND_JDBC_USABLE_CHECK is set to true, then it also verifies that the connection can be used to perform a simple PL/SQL query. (This parameter may have to be set to "true" in order to clean up
connections to a database that has been restarted.)
FND_JDBC_CONTEXT_CHECK
==========================
The FND_JDBC_CONTEXT_CHECK parameter governs whether the AOL security context and NLS state is obtained from the database when the connection is returned to the pool. If FND_JDBC_CONTEXT_CHECK is "true", when the connection is returned to the pool, the AOL security context and NLS state will be obtained from the database. (This is implemented in the DBConnObj.isReusable() method). This check must be done when the connection is returned (rather than when it is borrowed) so that the selection matching algorithm has access to the actual
session context of the connections in the available list.
FND_JDBC_PLSQL_RESET
========================
The PL/SQL reset flag, set using the variable FND_JDBC_PLSQL_RESET, governs whether the PL/SQL state associated with a connection should be freed before the pool hands the connection to the client. By default this flag is false.
If the flag is set by true, by including the line "FND_JDBC_PLSQL_RESET=true" in the .dbc file, each connection to the database will have its PL/SQL state cleared before the pool returns the connection to the client.
This is how it works. After the pool selects a connection from the available list for a client, it initializes the connection. One of the things initialization does is to set a flag that is later used by SessionManager to determine if the apps initialization routine needs to be performed for the connection. When FND_JDBC_PLSQL_RESET has been set to "true", this flag will always be set to true. After the pool initializes the connection, it also checks whether the connection is usable. In this case, this check will include a call to DBMS_SESSION.RESET_PACKAGE, which frees the PL/SQL state. The table below summaries the affect of FND_JDBC_PLSQL_RESET and the other safety check parameters on borrowing a connection from the pool.
The FND_JDBC_PLSQL_RESET parameter has been added to only to address the case where production PL/SQL global bugs are known to exist. The performance of the pool is reduced by setting this flag to true.
Reference : Note 264599.1

Purpose
JVM 이 과도한 CPU / Memory를 사용하게 되어 Application Performance에 영향을 미칠때가 있으며 이럴경우 Connection Pool 관련하여 Parameter Tunning을 해야 할때가 있습니다. 이때 사용되는 Parameter들의 의미를 설명하고자 합니다.
The Applications Database Connection Pool is a pool of JDBC database connections that are shared among java applications. Applications obtain connections from the pool by using the getJDBCConnection(...) methods of AppsContext.
Essentially, each AppsContext has a single database connection associated with it at all times.
The AOL/J layer internally borrows and returns this connection to the pool as needed to maintain connection reference that is properly initialized for the current Java tier AOL security context and NLS state.
FND_MAX_JDBC_CONNECTIONS
============================
The maximum pool size is the maximum allowed sum of the number of available connections and thenumber of locked connections. If the pool reaches the maximum size and all connections are locked, new clients will not be able to borrow a connection until one of the current clients has returned one. The default setting for this parameter is essentially unlimited (about 2 billion).
FND_JDBC_BUFFER_MIN
======================
The buffer minimum is the minimum number of connections that the pool should try to maintain in the available list. When the buffer size falls below the buffer minimum, the pool maintenance thread will be notified to create new connections. When notified, the thread will immediately attempt to create the number of connections to fill the difference. New connections will not be created if the pool is already at its maximum size. When creating new connections the thread uses the attributes of the most recent client request that resulted in a new connection being created.
Setting this parameter to "0" will disable maintenance of the buffer minimum.
However, the buffer maximum will still be maintained.
Setting this parameter to a number greater than the maximum pool size(FND_MAX_JDBC_CONNECTIONS) will disable all buffer maintenance.
FND_JDBC_BUFFER_MAX
======================
The buffer maximum is the maximum number of connections that the pool should try to maintain in the available list. During heavy usage, the buffer may exceed this maximum. However, during periods of low usage, the maintenance thread will decrease the buffer size until the buffer maximum is reached.
If the value of this parameter is an integer, (for example "20") the buffer maximum is static. If the value is a percent (for example, "20%"), the buffer maximum is not constant but instead is calculated dynamically as a percent of total pool size. The buffer minimum is also taken into account when
determining a dynamic buffer maximum.
The exact expression used is:
maximum(t) = buffer minimum + ( (FND_JDBC_BUFFER_MAX/100) * size(t) )
where maximum(t) and size(t) are the buffer maximum and pool size at some time t.
The thread is configured to periodically check the buffer size. If the buffer size is greater than the maximum, the thread will remove either the number of available connections specified by FND_JDBC_BUFFER_DECAY_SIZE or the number of connections in excess of the buffer minimum, whichever is smaller. When connections are removed from the available list, the least recently used ones are removed first.
Setting this parameter to100%, or to a number equal to FND_MAXIMUM_JDBC_CONNECTIONS, or to a number less than or equal to FND_JDBC_BUFFER_MIN will effectively prevent the maintenance thread from ever removing any connections.
FND_JDBC_BUFFER_DECAY_INTERVAL
===================================
The buffer decay interval specifies how often the connection pool maintenance thread should check the buffer size. The thread will check the buffer size at most once every FND_JDBC_BUFFER_DECAY_INTERVAL seconds. The actual time between consecutive thread cycles will vary somewhat depending on the JVM load.
This parameter, along with FND_JDBC_BUFFER_DECAY_SIZE, allows the buffer decay rate to be tuned. For example, if the buffer decay size is 2 and the buffer decay interval is one minute, the buffer decay rate will never exceed two connections per minute. When connections are removed, the least recently used ones are removed first.
FND_JDBC_BUFFER_DECAY_SIZE
=============================
The buffer decay size specifies the maximum number of connections that should be removed during any single thread cycle during which the number of available connections is greater than the buffer size. This parameter, along with FND_JDBC_BUFFER_DECAY_INTERVAL, allows the buffer decay rate to be tuned.
FND_JDBC_MAX_WAIT_TIME
=========================
The maximum wait time specifies how much time a client should spend trying to get a connection. The borrow algorithm, used to borrow an object from the pool, contains check points at which the elapsed time is compared to the maximum wait time. If it exceeds the maximum wait time, then a null object will be returned to the client. The pre-configured value for the maximum wait time is
10 seconds.
FND_JDBC_SELECTION_POLICY
============================
The selection policy determines how a connection is selected from the list of available connections for a particular client. The connection pool is pre-configured to use a cost-based selection algorithm, which selects the connection that will require the smallest amount of initialization to match the
client's context.
FND_JDBC_USABLE_CHECK
===========================
The FND_JDBC_USABLE_CHECK parameter governs whether a pl/sql query is performed before giving a connection to a client. The pool checks whether a connection is usable before handing it to a client. This always involves checking that the connection is not null and is not closed. If FND_JDBC_USABLE_CHECK is set to true, then it also verifies that the connection can be used to perform a simple PL/SQL query. (This parameter may have to be set to "true" in order to clean up
connections to a database that has been restarted.)
FND_JDBC_CONTEXT_CHECK
==========================
The FND_JDBC_CONTEXT_CHECK parameter governs whether the AOL security context and NLS state is obtained from the database when the connection is returned to the pool. If FND_JDBC_CONTEXT_CHECK is "true", when the connection is returned to the pool, the AOL security context and NLS state will be obtained from the database. (This is implemented in the DBConnObj.isReusable() method). This check must be done when the connection is returned (rather than when it is borrowed) so that the selection matching algorithm has access to the actual
session context of the connections in the available list.
FND_JDBC_PLSQL_RESET
========================
The PL/SQL reset flag, set using the variable FND_JDBC_PLSQL_RESET, governs whether the PL/SQL state associated with a connection should be freed before the pool hands the connection to the client. By default this flag is false.
If the flag is set by true, by including the line "FND_JDBC_PLSQL_RESET=true" in the .dbc file, each connection to the database will have its PL/SQL state cleared before the pool returns the connection to the client.
This is how it works. After the pool selects a connection from the available list for a client, it initializes the connection. One of the things initialization does is to set a flag that is later used by SessionManager to determine if the apps initialization routine needs to be performed for the connection. When FND_JDBC_PLSQL_RESET has been set to "true", this flag will always be set to true. After the pool initializes the connection, it also checks whether the connection is usable. In this case, this check will include a call to DBMS_SESSION.RESET_PACKAGE, which frees the PL/SQL state. The table below summaries the affect of FND_JDBC_PLSQL_RESET and the other safety check parameters on borrowing a connection from the pool.
The FND_JDBC_PLSQL_RESET parameter has been added to only to address the case where production PL/SQL global bugs are known to exist. The performance of the pool is reduced by setting this flag to true.
Reference : Note 264599.1

Application wide connection pooling

Just a quick question about connection pooling. How would one go about using application-side connection pooling? For example, I have multiple users logged into my application, all wanting to access the same database (with different username/password credentials). Is this possible? And if so, could someone provide a (brief) code snippet?
Thanks in advance :)
Ben

Thank you for your replies. I understand everything that you have said, but I think that I will elaborate my question further just to make sure that I have everything the right way around in my head.
My application defines a class called Product. This class represents a particular database schema/product. Within the Product class is the member variable;
    private transient ConnectionPoolDataSource connectionPool = null;
When the product is constructed a platform-specific pooled datasource is created (either Oracle or MS SQL Server).
    com.microsoft.jdbcx.sqlserver.SQLServerDataSource ds = new com.microsoft.jdbcx.sqlserver.SQLServerDataSource();
or
    oracle.jdbc.pool.OracleConnectionPoolDataSource ds = new oracle.jdbc.pool.OracleConnectionPoolDataSource();
which is assigned to the aforementioned member variable.
I also have a class called UserSpace which represents a user's work area. Multiple users can access the same product concurrently, and this is why I want to use connection pooling.
A user will do a lot of work "in situ". What I mean by this is that the user will take some time to construct a SQL query, and while they do so their work area is updated with relevant information. When they have fully specified the query that they want to execute I want to be able to grab a connection from the relevant product's connection pool, execute the query, and then hand the connecton back (so that it can be used by someone else).
To me it seems that this should be possible. Indeed I note that there is a method in the ConnectionPoolDataSource class called "getPooledConnection(String username, String password)". This suggests to me that username and password details can be set after the pool is created and that different connections in the pool can have differing user/password details and hence different access priviledges.
Is this correct?
Ben

Excel Automation with Interop - Windows Service - Microsoft Excel cannot access the file

I have a windows console application, which automates Excel. In our scenario the application gets called from a Windows Service. If the console app is executed directly everything works fine. If the console app is executed through the Win Service, we get
the following error when trying to open the excel file:
Unhandled exception Occured : 'Microsoft Excel cannot access the file 'bla.xls'. There are several possible reasons:
The file name or path does not exist.
The file is being used by another program.
The workbook you are trying to save has the same name as a currently open workbook.'.'
The code snippet used to open the file:
xlApp = new Application();xlApp.Visible = false;xlApp.UserControl = false;xlApp.Application.ScreenUpdating = false;xlApp.DisplayAlerts = false;xlWorkbook = xlApp.Workbooks.Open( Filename: filePath, UpdateLinks: 2, IgnoreReadOnlyRecommended: true, Editable: false);
The console app and windows service are running on a Win Server 2008 64-bit OS with Excel 2013 32-bit installed. The service is running with a special user account, which has all the right permissions on accessed files and folders. The excel process is also
started with the same account (I cheched that one).
I already tried to do the following, but to no avail:
Run excel.exe /automation -> worked fine
Created the folders and also gave full control to the account under which the service is run (even gave full control to Everyone)
C:\Windows\SysWOW64\config\systemprofile\Desktop
C:\Windows\System32\config\systemprofile\Desktop
Configured DCOM
Excel Application -> Identity -> Specific user account
Excel Application -> Identity -> Interactive User
Excel Application -> Security -> Launch permissions -> Everyone full control
Several combinations of the above
So I really am stuck with this problem right now. Any input on this is appreciated.

I have a windows console application, which automates Excel. In our scenario the application gets called from a Windows Service. If the console app is executed directly everything works fine. If the console app is executed through the Win Service, we get
the following error when trying to open the excel file
Microsoft does not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, ASP.NET, DCOM, and NT Services), because Office
may exhibit unstable behavior and/or deadlock when Office is run in this environment.
If you are building a solution that runs in a server-side context, you should try to use components that have been made safe for unattended execution. Or, you should try to find alternatives that allow at least part of the code to run client-side.
If you use an Office application from a server-side solution, the application will lack many of the necessary capabilities to run successfully. Additionally, you will be taking risks with the stability of your overall solution.
You can read more about that in the
Considerations for server-side Automation of Office article.

Windows 7 Enterprise - Cannot Print - Access Denied

Hello Guys,
I have strange issues..i just created a new Windows 7 Image. Even if i'am connected with Local Admin or Domain users, i cannot print to any printers.
When i want to print a test page, i receive the following error message " Print Test page failed, would you like to open troubleshooter?
Access Denied".
I have this message for network printer or Local Printer.
When i want to print from Office, i receive the following message " Printer Setup Configuration error...".
There is nothing on C:\Windows\System32\Spool\Printers.
Help !
THanks,
Laurent

Hi LoLe,
"i just created a new Windows 7 Image"
First of all ,I would suggest you to install all the updates for the new machine.Please also run "sfc /scannow"to check the health of the system .
"When i want to print from Office, i receive the following message "
Have you tried to print from other programs for example the Internet Explorer ?
"Access denied "
We can try to enable the built-in administrator account to have a check .If there is a antivirus software installed ,please turn them off temporarily to have a check .Please also check the status of "Printer Spooler" serivce and ensure it is running.
To enable the built-in administrator account (This is used to troubleshoot ,it is recommended to keep it disabled):
net user administrator /active:yes
net user administrator /active:no
Here is a fixit tool may be useful .
Diagnose and fix printer and printing problems automatically
https://support.microsoft.com/en-us/mats/printing_problems/en-hk
Please also checked the Event Viewer for any useful information to troubleshoot this issue .
Event Viewer\Windows Logs\Application ,System
Best regards
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Connection pool issue with packaged application

we are using 9.2 mp1 for a Oarcle packaged application which is talking to Oracle RAC. In production one
of the RAC nodes went down and we see that the wbelogic connection pool is never able to reconnect
This is a packaged application Bharosa which internally uses hibernate and in turn relies on weblogic connection pool
See a few stuck threads in the logs indicating some prolem with the connection cleanup
<Dec 16, 2008 12:11:03 PM PST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "626" seconds working on the request "Http Request: /fahost/econnect/IntegratedAuthRemoteServlet.svl;JSPSESSIONID=82W2JLLJ8vCB25G3jyc6cYdXVXLYc1G1GwTt91plpCpB9MY6yQP3!468271380!-864027599!1229457609639", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
     weblogic.common.resourcepool.ResourcePoolImpl.releaseResource(ResourcePoolImpl.java:521)
     weblogic.jdbc.common.internal.ConnectionPool.release(ConnectionPool.java:669)
     weblogic.jdbc.common.internal.ConnectionPoolManager.release(ConnectionPoolManager.java:113)
     weblogic.jdbc.wrapper.PoolConnection.doClose(PoolConnection.java:192)
     weblogic.jdbc.wrapper.PoolConnection.close(PoolConnection.java:117)
     org.hibernate.connection.DatasourceConnectionProvider.closeConnection(DatasourceConnectionProvider.java:74)
     org.hibernate.jdbc.ConnectionManager.closeConnection(ConnectionManager.java:388)
     org.hibernate.jdbc.ConnectionManager.aggressiveRelease(ConnectionManager.java:343)
     org.hibernate.jdbc.ConnectionManager.afterTransaction(ConnectionManager.java:230)
     org.hibernate.jdbc.JDBCContext.afterTransactionCompletion(JDBCContext.java:201)
     org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:127)
     com.bharosa.common.hibernate.HiberDBMgr.commitTransaction(HiberDBMgr.java:293)
     com.bharosa.common.db.BharosaDBMgr.endSession(BharosaDBMgr.java:243)
     com.bharosa.common.hibernate.HiberBaseDAO.executeQuery(HiberBaseDAO.java:596)
     com.bharosa.common.hibernate.HiberBaseDAO.executeDBQuery(HiberBaseDAO.java:543)
     com.bharosa.common.hibernate.HiberDBMgr.executeDBQuery(HiberDBMgr.java:351)
     com.bharosa.vcrypt.dataaccess.impl.VCryptUserDataAccessImpl.getVCryptUserByLoginId(VCryptUserDataAccessImpl.java:520)
     com.bharosa.vcrypt.auth.impl.VCryptAuthImpl.getUserByLoginId(VCryptAuthImpl.java:274)
     com.bharosa.client.BharosaHelper.getUser(BharosaHelper.java:116)
     com.bharosa.client.BharosaHelper.createPersonalizedAuthentiPad(BharosaHelper.java:308)
     com.svb.ib.security.web.loginauthserver.IntegratedAuthDelegateSkeleton.getAuthpadHTML(IntegratedAuthDelegateSkeleton.java:672)
     com.svb.ib.security.web.loginauthserver.IntegratedAuthDelegateSkeleton.createAuthPad(IntegratedAuthDelegateSkeleton.java:113)
     com.svb.ib.security.web.loginauthserver.IntegratedAuthDelegateSkeleton.createAuthPad(IntegratedAuthDelegateSkeleton.java:103)
     com.svb.ib.security.web.loginauthserver.IntegratedAuthRemoteServlet.invokeService(IntegratedAuthRemoteServlet.java:60)
     com.svb.ib.security.web.loginauthserver.IntegratedAuthRemoteServlet.doPost(IntegratedAuthRemoteServlet.java:40)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:223)
     weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
     weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3245)
     weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2003)
     weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1909)
     weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359)
     weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
<Dec 16, 2008 12:11:03 PM PST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "616" seconds working on the request "weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl@ba063", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
     weblogic.common.resourcepool.ResourcePoolImpl.getCurrCapacity(ResourcePoolImpl.java:671)
     weblogic.common.resourcepool.ResourcePoolImpl$ResourcePoolMaintanenceTask.timerExpired(ResourcePoolImpl.java:1922)
     weblogic.timers.internal.TimerImpl.run(TimerImpl.java:265)
     weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
<Dec 16, 2008 12:11:03 PM PST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "635" seconds working on the request "Http Request: /fahost/econnect/IntegratedAuthRemoteServlet.svl;JSPSESSIONID=Q3C6JLLV1lwjqmTWLQ4m5M02BqBKmQzcyt66wY925kykg2pQyB1t!1872529297!468271380!1229457621681", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
     java.net.SocketInputStream.socketRead0(Native Method)
     java.net.SocketInputStream.read(SocketInputStream.java:129)
     oracle.net.ns.Packet.receive(Unknown Source)
     oracle.net.ns.DataPacket.receive(Unknown Source)
     oracle.net.ns.NetInputStream.getNextPacket(Unknown Source)
     oracle.net.ns.NetInputStream.read(Unknown Source)
     oracle.net.ns.NetInputStream.read(Unknown Source)
     oracle.net.ns.NetInputStream.read(Unknown Source)
     oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1099)
     oracle.jdbc.driver.T4CMAREngine.unmarshalSB1(T4CMAREngine.java:1070)
     oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:478)
     oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216)
     oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:955)
     oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:10622)
     weblogic.jdbc.wrapper.PreparedStatement.executeBatch(PreparedStatement.java:157)
     org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:58)
     org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:195)
     org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:230)
     org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:141)
     org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:296)
     org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27)
     org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1009)
     org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:356)
     org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106)
     com.bharosa.common.hibernate.HiberDBMgr.commitTransaction(HiberDBMgr.java:293)
     com.bharosa.common.db.BharosaDBMgr.endSession(BharosaDBMgr.java:243)
     com.bharosa.common.dataaccess.DataAccessMgr.endSession(DataAccessMgr.java:132)
     com.bharosa.vcrypt.tracker.impl.VCryptTrackerImpl.updateLog(VCryptTrackerImpl.java:1048)
     com.bharosa.vcrypt.tracker.impl.VCryptTrackerImpl.updateLog(VCryptTrackerImpl.java:622)
     com.bharosa.client.BharosaHelper.fingerPrintFlash(BharosaHelper.java:203)
     com.bharosa.client.BharosaHelper.fingerPrintBrowser(BharosaHelper.java:155)
     com.svb.ib.security.web.loginauthserver.IntegratedAuthDelegateSkeleton.runPreAuthRules(IntegratedAuthDelegateSkeleton.java:239)
     com.svb.ib.security.web.loginauthserver.IntegratedAuthDelegateSkeleton.runPreAuthRules(IntegratedAuthDelegateSkeleton.java:214)
     com.svb.ib.security.web.loginauthserver.IntegratedAuthRemoteServlet.invokeService(IntegratedAuthRemoteServlet.java:83)
     com.svb.ib.security.web.loginauthserver.IntegratedAuthRemoteServlet.doPost(IntegratedAuthRemoteServlet.java:40)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:223)
     weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
     weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3245)
     weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2003)
     weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1909)
     weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359)
     weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>

Hi. Something is seriously ill there. I would ask that you post a full thread dump
to see what's locking what. You may need an official support case...

Read data using 2 diff connection pool for same DB folder in physical layer

Hi All,
i am using two connection pool which have different dsn connection information (both are directed to different database name or database server)..
so if i view the data of any table, a prompt will come asking for the connection pool, so how do i automize it....?
how do i set the different connection pool for different tables?
please let me know if u need further informtaion to understand my problem..
thnx...

thnx Stijn..
yupe that i know...
actually i have total of around 300 tables in physical layer (in both the schemas..) , around 12 fact and 100 dimension tables in bmm and same in the presentation layer...
so i think u can guess how many joins and other stuff, i have made in my bmm layer..
if now i will start modifying all this it will take lot of time...
i am just wondering that there is no alternative for this...
as when i check my data from the physical layer then a prompt ask for the connection pool (i have already made two connection pool..) so there could be some alternative way to automize the default connection pool setting for the tables/schemas folders in case if more than one connection pool exits under the same database in the physical layer...
isn't it?
thnx again..

Hyperion Enterprise historic data access (tool)

we are moving from Hyperion Enterprise to SAP SEM.
As the historic data won't be moved we are looking for the best and easiest way to be able to access that data in the future.
Is there an option of not using Enterprise anymore? Reading the data with another tool where no infrastructure is needed?
Has anyone done something similar already?
Thanks
Jonas

for anyone interested:
talked to Oracle and they said other customers were running a virtual server till it was not used anymore.
so there is no other option than running the system as long as you need it or export everything to excel
Jonas

Using Enterprise library 2

Hi every one,
iam using .net2 enterprise library and oracle as my background db.
can any one guide me in using the data access application block for .net2.
i wrote a sample stored procedure which returns cursors as output parameter.
is there any way to handle it.
can any one provide me an example for this which will helpfull for me.
thanks

Microsoft's Petshop example application uses the Microsoft Database Access Application Block (DAAB) with Oracle 9i. This was the DAAB from before the Enterprise Library, when it was still separate.I am guessing they use the MS Oracle provider instead of ODP.
http://msdn2.microsoft.com/en-us/library/ms954623.aspx
I don't care for DAAB myself. It seems terribly inefficient. It's a late-bound architecture where they have to hit the DB first to get metadata before executing a query. It's true that they cache the metadata, but it's better in my mind if you know the types ahead of time. Their approach is fine for dynamic SQL in cases where you can't know the types ahead of time, but that's a rare situation. With most dynamic SQL you know the types of the columns you might access.
The Enterprise Library is also pretty heavy. It's hard to use only part of it. Once you start using it, you're stuck with a bunch of blocks, like caching, logging, configuration, etc.
Eric

Using both Enterprise library and Entity framework as DAL for same application

We have been using EF for large amount of data retrieval in our current application. We faced performance related issues with using EF with large data retrieval and manipulation.
We need to extend the same project with some additional functionality similar to what currently exists in the application and uses EF.
For the new functionality, we do not want to use EF and want to use enterprise library for Data access.
My question is if we use both entity framework for parts of the application data access mechanism and enterprise library for other parts of application data access, are there any known issues?
if there are any best practices to be followed please share .

We have been using EF for large dataset retrieval in our current application. We faced performance related issues with using EF for large data set's .
Dataset? What are you talking about? If you are using the salad bowl, the dataset with datatables, then here is the reason not to use them.
http://lauteikkehn.blogspot.com/2012/03/datatable-vs-list.html
My question is if we use both entity framework for parts of the application data access mechanism and enterprise library for other parts of application data access, are there any known issues?
What is Entlib going to buy you in performance? It's going to buy you nothing. You'll be better of going to the EF backdoor, use SQL command objects, inline T-SQL, sprocs, datareder and using custom objects or objects off of the virtual model returning a
single object or objects in a collction., if you are concerned about performance.
http://blogs.msdn.com/b/alexj/archive/2009/11/07/tip-41-how-to-execute-t-sql-directly-against-the-database.aspx
You'll probably be better of going to Entity SQL, using a datareader, collection and using custom objects or objects off of the model, if you are concerned about query performance.
https://msdn.microsoft.com/en-us/library/vstudio/bb738684(v=vs.100).aspx
https://msdn.microsoft.com/en-us/library/vstudio/bb387145(v=vs.100).aspx
https://msdn.microsoft.com/en-us/library/vstudio/bb399560(v=vs.100).aspx
My question is if we use both entity framework for parts of the application data access mechanism and enterprise library for other parts of application data access,
are there any known issues?
A nightmare, no consistency and complete Helter Skelter is what I see. Been there and seen it in action with different technologies doing the same thing in a solution.

"unable to connect to the data access service" installing report server

Trying to do a 2 server SCOM 2012 R2 install on Server 2012 w/SQL 2012. Management server and operations console on one, and SQL, web console, and reporting server on the other. When I get to the web console and reporting server install, and
the "Specify Management Server" screen, I input the 1st management server name and it gives me a red X with the message:
"Unable to connect to the Data Access service for this management server. Ensure the Data Access service is running and that the service, the management group, and setup are all the same version."
Here is the setup log error:
"Info: :Could not connect to Management Server: scom-app with exception: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or
too long."
I don't see the "Data Access" service in services on either server. I followed all of the setup prereqs in SCOM 2012 unleashed book, and also referenced this article for setup advice:
http://blogs.technet.com/b/kevinholman/archive/2013/01/16/opsmgr-2012-sp1-quickstart-deployment-guide.aspx
Everything seems to be working until I get to this point.
Thank you for any help you can provide,
Dan

Hi Tom,
1. Did the setup complete successfully on the MS and Console server?
>>>Yes, without issue
2. You do not see the service "System Center Data Access Service"
>>>I do indeed see it on the MS and Console server, it is set to Auto and running. (I also tried rebooting this server and retried, no help)
3. Is the Windows Firewall enabled?
>>>It has symantec endpoint protection. I disabled symantec completely on both servers and retried, no help.
Thx,
Dan

Data Access Service Designer

Hi,
does anybody know where I can find some informations regarding Data Access Services or the Data Access Service Designer?
Thanks
Lutz

Hi Lutz,
it is being quite long time since you created this thread. I came across it since I'm also interesting in Data Access Services.
It seems that Data Access Service Designer is web based tool running most likely on JAVA Stack of BW server.
I've found ABAP Class called CL_RSDAS_WDAPP which seems to serve as this web app starter.
URL which thsi class triggers should be like:
http(s)://host:port/webdynpro/dispatcher/sap.com/bidasui/DasDesigner?
Have you some more information on this topic?
BR
m./

Windows Service Enterprise Library Data Access Application Blocks Connection Pooling Issue

Similar Messages

Maybe you are looking for