DB Connection Usage

In doing some simulated load testing, it looks like for each
interactive user, Portal fires up (4) different DB connections,
one each for portal30, portal30_sso, portal30_public,
portal30_sso_public. For 100 users this is over 400 connections,
not exactly a scalable situation.
Anyone else seeing this behavior?
Also, anyone care to comment on experiences with multithreaded vs
dedicated server mode for portal? I'm currently running
dedicated.

MTS works fine with Portal.
We haven't certified it, but it does work and I have quite a few
high load customers using MTS and Portal 308 and 309.

Similar Messages

When i try to submit an application with Application Loader, the wizard is blocked on "Send API itunes connect usage, waiting for response". Any idea ?

When i try to submit an application with Application Loader, the wizard is blocked on "Send API itunes connect usage, waiting for response". Any idea ?

Thank you, Vincent! It's still down for me, but at least I know someone had the same issue. Hoping it's going to work over here soon
Best!

Registering Application Connection usage

Hi All,
I'm using Oracle 10 ojdbc library for creating cached connections, using OracleDataDource and OracleConnectionCacheManager class to handle pooling of connections. Our DB admin is currently having a hard time monitoring connections since there were alot of applications/instances connecting to the DB. So it was proposed that on creation of a connection it will call a callable statement registering itself (the connection) and the application using it.
My problem is, since the connection is created and pooled by the OracleDataSource how can I tell the OracleDataSource to do this upon creation of a connection. I checked the ConnectionListener and it only handles closeEvents. Or is there a better way of tracking/registering application per connection usage.
(BTW is was also propose that we assign seperate usernames for each applications but since the oracle license limited the number of users per DB it was later scraped since there were alot of applications and replicated instance running.)
Thanks.

(BTW is was also propose that we assign seperate
usernames for each applications but since the oracle
license limited the number of users per DB it was
later scraped since there were alot of applications
and replicated instance running.)I can't know what license you have, but named user licensing doesn't restrict how many accounts you can create. It restricts how many real people can benefit from the database. For example, a user group of 1000 people that uses an application that uses only a single name for logging in and accessing the database still needs to be licensed for 1000 users. On the other hand, a small group of 20 employees could have apps that actually require 200 user accounts -- and they would only need to be licensed for 20 users. There are minimum user requirements per cpu and such, and there have been many licensing models. I don't know what your license says, but what I described, I believe to be the most current for 'named user'.
Chris

Safari 3.2, Idle connection usage

I installed Safari 3.2 this evening on three of my systems. All of them run Tiger. After installing, I made sure to reboot one more time and run applejack, repairing permissions in the process. Safari was actually working quite well compared to the other stories I've been reading. A little while ago, all three seemed to start using bandwidth when idle while Safari was running. When I quit Safari, the bandwidth usage stopped. I opened up Safari again and made sure none of my settings had been switched on to check for any sort of updates and let Safari sit. Sure enough, the usage started up again. Now it seems to have resolved completely. Nothing terribly impressive showed up in netstat, except for an address that resolves to Google.
Is this just a one time thing Safari does on a new install/update? I specifically avoid using Firefox on a regular basis because of a similar random issue and I'd hate to find out that Safari is now connecting to something at random.

Firefox can connect to check for updates to the program, add-ons, search engines, or the anti-phishing list. You can disable any or all of these if you want.
As the latest version of Safari also has an anti-phishing list it's probably checking for updates to it, you can disable the option in Preferences > Security.

Servlet - database connection usage

Hi
I am writing a servlet based upon the multi thread model (default in many cases).In the servlet, I go to database 2 or 3 times per request and get data. I have broken down my main method into 4 methods. so method 1 calls method 2 with some params, method 2 calls method 3 etc.
I am using connection pooling. I am passing the connection object from method 1 to downstream methods. and release the connection only at the end.
My question is since this servlet can be accessed by multiple threads, is this a good practice of passing connection downstream since a servlet might try to access with a closed connection object. Should I just get connection objects from the pool and release them inside each method.
thanks

Hi
I am writing a servlet based upon the multi thread
model (default in many cases).In the servlet, I go to
database 2 or 3 times per request and get data. I have
broken down my main method into 4 methods. so method 1
calls method 2 with some params, method 2 calls method
3 etc.
I am using connection pooling. I am passing the
connection object from method 1 to downstream methods.
and release the connection only at the end.
My question is since this servlet can be accessed by
multiple threads, is this a good practice of passing
connection downstream since a servlet might try to
access with a closed connection object. Should I just
get connection objects from the pool and release them
inside each method.
thanksIf the Connection is a local variable for the service, doPost, doGet, etc... there isn't any problem with your aproach.
If it is, then your Connection is shared between all the threads that run concurrently (run througth the servlet).
Concerning your aproach (and the Connection beeing a local variable), there is no problem in passing it to the next method by parameter because it is the same thread running the code.
MSB

J2EE Spec for JMS Connection usage

I am trying to understand the rational behind the J2EE spec for using JMS that says that a connection within a container should have only one active session.
"... J2EE version 1.4 also requires that components in Web and EJB containers not create more than one active Session per connection."
This is in contrast to the original JMS doc:
"...A JMS client will normally create one Connection object to the JMS provider.
From this Connection, one or more Sessions will be created"
If anyone understands why the behavior should be different in using a Connection within a web container, pls elaborate.

J2EE1.4 requires a connection can have only one session. This has to do with the way JMS is built on JCA from 1.4.
Connection represents both connection and transactional context in JCA , however in JMS 'Session' represents a transactional context.
In J2EE 1.3 a connection can have multiple sessions.
Please look at following link for more details:
http://www-128.ibm.com/developerworks/blogs/dw_blog.jspa?roll=-4&blog=392

Connection usage

If we are using toplink api, is there any chance of connection leakage? Do we need to take any precautions with regards to managing database connection or other resources e.g. releasing uow etc while using toplink?

There should be no issues with 'connection leakage' and TopLink. If you are using the TopLink connection pooling you will want to ensure that either you are releasing the ClientSession (if you are using the Three Tier architecture) when it is no longer needed. Upon garbage collection the ClientSession will release the connection but clientSession.release() will release the Connection as well.
If you are using an external connection pool then there should be no issues at all.
--Gordon

RFC Destination Connection Pool requirement

Hi Experts,
I have a custom webdynpro java application to display number of work items pertaining to that particular user in a backend.
There are users who dont use this functionality as well. But the requirement is to place this application in home screen.
I have used both metadata and modeldata with hard coded user since we did not want error messages to appear for users who do not have backend access.
Application & Access Details
Application Location : Home Screen
Concurrent Users : 600 concurrent users maximum possible value
Connection Usage : Close connection immediately using disconnectIfAlive() method.
Now I need to configure JCO Pool Size , Max Connections, Wait Time for the RFC destination.
I have read a lot of post and documents but could not acheive clarity of thought on this.
Kindly let me know what values I should give in these fields for optimal performance and no connection issue for users.
Regards,
Porselvan

Hi Muthavudaiyan,
Hope you are doing good.
Basically from the JCo perspective, there are only 5 parameters that are involved here:
jco.destination.pool_capacity:
Maximum number of connections that are held open in the pool for reuse (default: 1)
jco.destination.peak_limit:
Maximum number of connections that can be obtained from a pool at peak usage times
jco.destination.max_get_client_time:
Maximum time to wait for a free connection if the peak limit is reached before exception is thrown
jco.destination.expiration_time:
Timeout period after which pooled idle connections can be closed (default: 600000ms = 10mins)
jco.destination.expiration_check_period:
Regular time interval for checking if pooled connections have expired and will be closed
The values are determined by the application in question. The ideal values have to told to you by the application developer; there are no two ways about this.
Thank you and have a nice day :).
Kind Regards,
Hemanth

Exchange Server 2010 usage monitoring

Dears
How we can monitor Exchange server 2010 usage like owa usage, mail sending, contact Adding and editing ...etc.
is exchange has tools to do that or i have to use system center if yes what version of system center is Enterprise or Standard?

Hi ,
Please check the below mentioned points
1.) For owa and rpc connections usage , you can make use of the mentioned script on below link.
http://mikepfeiffer.net/2011/04/determine-the-number-of-active-users-on-exchange-2010-client-access-servers-with-powershell/
2.)For tracing the total mails send and received by the individual users (i.e internal /external)you can make use of the below mentioned script
https://gallery.technet.microsoft.com/scriptcenter/bb94b422-eb9e-4c53-a454-f7da6ddfb5d6
3.For contact adding and editing.I mean to track administrator related activities on exchange recipients ,You can make use of Exchange admin audit logging to track such kind of activities.But that will not tell you the count of total contacts that are in
exchange and it exposes only the changes which is done by administrator on the recipients available in exchange.
http://www.msexchange.org/articles-tutorials/exchange-server-2010/compliance-policies-archiving/administrator-audit-logging-part1.html
Below is the link which will help you to get the Admin audit report via emails in HTML format.
http://mikepfeiffer.net/2010/08/administrator-audit-log-reports-in-html-format-exchange-2010-sp1/
Please feel free to reply me if anything is unclear
Thanks & Regards S.Nithyanandham

WLS 10.3.0.0 Solaris SPARC and DBMS Oracle 10gR2 connection pooling issue

Hi all,
we are currently testing Weblogic Server 10.3.0.0 in order to migrate our production system from WLS 8.1 to it.
While testing the new setup, we encountered some strange behaviour of the connection pooling within WLS.
We configured a XA-Connection pool to our DB (Oracle 10gR2) by using
a) the Oracle XA-thin-driver delivered within WLS 10.3.0.0
and alternatively
b) the Oracle 11.2.0.2 OCI-driver of the Oracle 11g database client.
We´ve got the same issue with both variants. We defined an initial capacity of 5 connections and a maximum capacity of 30 connections.
Our application is running flawlessly using the connection pool, but the amount of active sessions between the application server and the database server is increasing rapidly and the maximum capacity is exceeded. We are seeing up to multiple hundreds of sessions from the application server to our database server. Obviously the connections aren´t cleaned up.
We are using the following settings for the JDBC-Connection:
initial capacity = 5
max. capacity = 30
Capacity increment = 1
Statement cache type = LRU
Statement cache size = 10
Test connections on reserve = true
Test frequency = 120
Test table name = "sql select 1 from dual"
seconds to trust an idle pool connection = 10
shrink frequency = 0
connecttion creation retry frequency = 120
login delay = 0
incative connection timeout = 10
max. waiting for connection = 2147483647
connection reserve timeout= = -1
Ignare in-use connections = true
pinned-to-thread = false
remoce infected connections enabled = true
Does anyone have an idea how to track/solve this issue?
Kind regards
Marc

Hi Joe,
we´ve tested with the thin driver using an initial capacity of 5 and a maximum capacity of 15. During our tests (in a very short time period) the maximum capacity has not been exceeded. But we saw some exceptions in the managed server logfile which made us curious.
When these exceptions are occuring, a new connection to the database server is established. We are seeing for a short time a total count of 6 connections which is immediately decreasing to the initial capacity of 5. We will do some further testing over the next hours and monitor the connection usage.
The connection we are dealing with is the one called "ZDB2".
This is an excerpt of the logfile:
####<18.10.2010 19:45 Uhr MESZ> <Debug> <JDBCConn> <SERVER-NAME> <MANAGED SERVER NAME> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-02F7EA174F1D84653A69> <> <1287423940610> <BEA-000000> <java.lang.Exception: Pinned: autoCommit=true,enabled=true,isXA=true,isJTS=false,vendorID=0,connUsed=true,doInit=false,'null',destroyed=false,poolname=ZDB2,appname=null,moduleName=null,connectTime=177,dirtyIsolationLevel=false,initialIsolationLevel=2,infected=true,lastSuccessfulConnectionUse=1287423940605,secondsToTrustAnIdlePoolConnection=10,currentUser=java.lang.Exception
     at weblogic.jdbc.common.internal.ConnectionEnv.setup(ConnectionEnv.java:308)
     at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:314)
     at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:427)
     at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:316)
     at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:93)
     at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:61)
     at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1473)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1272)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:425)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:382)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:338)
     at org.hibernate.connection.DatasourceConnectionProvider.getConnection(DatasourceConnectionProvider.java:69)
     at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:423)
     at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:144)
     at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:139)
     at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1547)
     at org.hibernate.loader.Loader.doQuery(Loader.java:673)
     at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236)
     at org.hibernate.loader.Loader.doList(Loader.java:2220)
     at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2104)
     at org.hibernate.loader.Loader.list(Loader.java:2099)
     at org.hibernate.hql.classic.QueryTranslatorImpl.list(QueryTranslatorImpl.java:912)
     at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:172)
     at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1121)
     at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79)
     at org.hibernate.impl.AbstractQueryImpl.uniqueResult(AbstractQueryImpl.java:811)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderPersistenceGenerated.findByPrimaryKey(OrderPersistenceGenerated.java:45)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImplStandard.findOrderByPrimaryKey(OrderManagementServiceImplStandard.java:1356)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.findOrderByPrimaryKeyTx(OrderManagementServiceTransactionHandler.java:830)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceSessionBean.findOrderByPrimaryKey(OrderManagementServiceSessionBean.java:1276)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_ELOImpl.findOrderByPrimaryKey(OrderManagementEJB_yb2dzq_ELOImpl.java:19812)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceApplicationProxy.findOrderByPrimaryKey(OrderManagementServiceApplicationProxy.java:1289)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.findOrderByPrimaryKey(OrderManagementServiceTransactionHandler.java:823)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImplStandard.findOrderByPrimaryKey(OrderManagementServiceImplStandard.java:1341)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.findOrderByPrimaryKeyTx(OrderManagementServiceTransactionHandler.java:816)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceSessionBean.findOrderByPrimaryKey(OrderManagementServiceSessionBean.java:1255)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_ELOImpl.findOrderByPrimaryKey(OrderManagementEJB_yb2dzq_ELOImpl.java:7332)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceApplicationProxy.findOrderByPrimaryKey(OrderManagementServiceApplicationProxy.java:1266)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.findOrderByPrimaryKey(OrderManagementServiceTransactionHandler.java:809)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImpl.publishOrder(OrderManagementServiceImpl.java:1636)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImpl.savePublishedOrder(OrderManagementServiceImpl.java:1606)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.savePublishedOrderTx(OrderManagementServiceTransactionHandler.java:3467)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceSessionBean.savePublishedOrder(OrderManagementServiceSessionBean.java:5272)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl.savePublishedOrder(OrderManagementEJB_yb2dzq_EOImpl.java:3263)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.internalInvoke2(Unknown Source)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.internalInvoke1(Unknown Source)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
     at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
     at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
,currentThread=Thread[[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads],lastUser=null,currentError=null,currentErrorTimestamp=null,JDBC4Runtime=true,supportStatementPoolable=true,needRestoreClientInfo=false,defaultClientInfo={} is set to be refreshed
     at weblogic.jdbc.common.internal.ConnectionEnv.setRefreshNeeded(ConnectionEnv.java:518)
     at weblogic.jdbc.wrapper.Connection.getVendorConnection(Connection.java:292)
     at de.dpcom.persistence.hibernate.BinaryBlobType.nullSafeSet(BinaryBlobType.java:109)
     at org.hibernate.type.CustomType.nullSafeSet(CustomType.java:146)
     at org.hibernate.persister.entity.AbstractEntityPersister.dehydrate(AbstractEntityPersister.java:1997)
     at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2371)
     at org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:2307)
     at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2607)
     at org.hibernate.action.EntityUpdateAction.execute(EntityUpdateAction.java:92)
     at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:248)
     at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:232)
     at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:140)
     at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298)
     at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27)
     at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000)
     at APPNAME-ROOT-PATH.components.customermanagement.biz.CertificatePersistenceGenerated.updateCertificate(CertificatePersistenceGenerated.java:116)
     at APPNAME-ROOT-PATH.components.customermanagement.biz.CustomerManagementServiceImplStandard.updateCertificate(CustomerManagementServiceImplStandard.java:1282)
     at APPNAME-ROOT-PATH.components.customermanagement.biz.CustomerManagementServiceTransactionHandler.updateCertificateTx(CustomerManagementServiceTransactionHandler.java:711)
     at APPNAME-ROOT-PATH.components.customermanagement.biz.CustomerManagementServiceSessionBean.updateCertificate(CustomerManagementServiceSessionBean.java:1104)
     at APPNAME-ROOT-PATH.components.customermanagement.biz.CustomerManagementEJB_ap2i9a_ELOImpl.updateCertificate(CustomerManagementEJB_ap2i9a_ELOImpl.java:19199)
     at APPNAME-ROOT-PATH.components.customermanagement.biz.CustomerManagementServiceApplicationProxy.updateCertificate(CustomerManagementServiceApplicationProxy.java:1101)
     at APPNAME-ROOT-PATH.components.productionresultprocessing.biz.ProductionResultProcessingServiceImpl.publishCertificate(ProductionResultProcessingServiceImpl.java:1131)
     at APPNAME-ROOT-PATH.components.productionresultprocessing.biz.ProductionResultProcessingServiceTransactionHandler.publishCertificateTx(ProductionResultProcessingServiceTransactionHandler.java:298)
     at APPNAME-ROOT-PATH.components.productionresultprocessing.biz.ProductionResultProcessingServiceSessionBean.publishCertificate(ProductionResultProcessingServiceSessionBean.java:517)
     at APPNAME-ROOT-PATH.components.productionresultprocessing.biz.ProductionResultProcessingServiceSessionBean_yaua6q_ELOImpl.publishCertificate(ProductionResultProcessingServiceSessionBean_yaua6q_ELOImpl.java:1804)
     at APPNAME-ROOT-PATH.components.productionresultprocessing.biz.ProductionResultProcessingServiceApplicationProxy.publishCertificate(ProductionResultProcessingServiceApplicationProxy.java:471)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImpl.publishCertificate(OrderManagementServiceImpl.java:1825)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImpl.publishOrder(OrderManagementServiceImpl.java:1664)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImpl.savePublishedOrder(OrderManagementServiceImpl.java:1606)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.savePublishedOrderTx(OrderManagementServiceTransactionHandler.java:3467)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceSessionBean.savePublishedOrder(OrderManagementServiceSessionBean.java:5272)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl.savePublishedOrder(OrderManagementEJB_yb2dzq_EOImpl.java:3263)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.internalInvoke2(Unknown Source)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.internalInvoke1(Unknown Source)
     at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
     at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
     at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
####<18.10.2010 19:45 Uhr MESZ> <Info> <JDBC> <SERVER-NAME> <MANAGED SERVER NAME> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1287423940797> <BEA-001072> <Connection for XA pool "ZDB2" created.>
####<18.10.2010 19:45 Uhr MESZ> <Info> <JDBC> <SERVER-NAME> <MANAGED SERVER NAME> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1287423940808> <BEA-001132> <Initialized statement cache of size "10" for connection in pool "ZDB2".>
####<18.10.2010 19:45 Uhr MESZ> <Info> <Common> <SERVER-NAME> <MANAGED SERVER NAME> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1287423940808> <BEA-000628> <Created "1" resources for pool "ZDB2", out of which "1" are available and "0" are unavailable.>
Any suggestions?
Kind regards
Marc

Monitoring Connection Pools

Hello All,
Environment details: OBIEE - 10.1.3.4.1 on 10gAS , Solaris 10. Single Node
We are implementing OBIEE in our organization and every quarter we add more number of data sources, dashboards and users. Recently we have started observing slowness while logging in. After crosschecking we have observed that not having separate connection pools for session variables might be one of the issue.
Before defining any new connection pools, we would like to take a proper step to design our connection pools. But we are unable to locate proper resources for monitoring the connection pool usage at a give point of time. Ideally we would to automate a job which will collect statistics of all available connection pools, users at a decent level of detail. This can help us in identifying the pattern of usage and further help us in defining an optimal connection pool strategy.
Could someone please guide me to a proper resource ? Can UDML help me here ? Any tips?
Thanks a lot for your help.
~Ravi.M

As far as I know there isn't any way of checking the connection pool usage from the OBIEE layer. But your DBA should able to queries to monitor the OBIEE connection usage from the database side. As for your question about designing connections pools the documentation is very extensive on this subject, have you reviewed the relevant section in the server Administration Guide?
After crosschecking we have observed that not having separate connection pools for session variables might be one of the issue.This is specifically mentioned in the documentation, you should separate connections for your Init Blocks. Also you should try to consolidate Init Blocks to reduce the database call overhead. In addition to this I can mention that most login problems relate to Init Blocks taking long to run rather than connection pool issues. Make sure your Init Blocks return data quickly. Also if you have a lot of session init blocks you may want to set some depencies between them. Suppose you have 10 session init blocks. If two users login at the same time OBIEE will try to run all those queries at the same time, should the max connections be set that high (20). By setting some execution depencies in your Init Blocks you can control the execution to reduce the parallelism and make them to run a bit more serial reducing the connection pool usage.

Connect Audigy 2 Value to Recei

I am currently using the digital out from the card and connect to the coaxial input of the receiver. Everything works fine, except when I play DVD on the computer the receiver won't automatically detect the Dolby settings. Also, When I try to test the speakers using the software provided by the sound card, only the front two speakers will work, the other three speakers do not have the static sound coming out of them. Please give me some help on how to set up this correctly. Thanks

chenchr,
Make sure you have disable the soundcard decoder and your DVD playback software decoder(eg. WinDVD). To disable your soundcard decoder, go to the Creative Audio Console application, under decoder tab set it to SPDIF Passthrough. As for your DVD software, go to the audio setting and set it to something similar too.
Also, you can check out this sticky for digital connection usage and limits.
Jason

SQL0904N and SQL30081N while using DB2-Connect driver

Scenario:
Application program : Java on Unix
Database : DB2 on Mainframe
Database driver : IBM's DB2 connect
Usage : A number of connections are taken by the program and are used as long as the program is alive
(Life time of the program is variable. It can be as long as many days -- in a sense the program acts like a daemon process that runs as long it is not stopped).
Scenario:
-To one of the table using a load utility, such as BMC, data is loaded
-Database goes to copy-pending status
-Database is started by using the following command : "START DATABASE(database name) SPACENAM(table space name) ACCESS(FORCE)"
Doubts:
1. What happens to the connections that the program has opened to the database?
2. Does the database relinquish all the resources (like the sockets it would have opened for the communication with the driver) held by it during restarting?
(at least before restarting, it is evident that no query on the table in question is possible. A typical SQL0904N, which is non-availability of resources, is thrown)
3. Can the above scenario cause a SQL30081N, which is resetting of connection by peer i.e. database in this case?

Yes, there is a high probability for such things, you may want to consider using a connection pool instead of opening 2 connections once at the start of the program and using them all for days.
Have a look at the following link to get an idea on how to implement a simple connection pool.
http://developer.java.sun.com/developer/onlineTraining/Programming/JDCBook/conpool.html

QAAS Connection

Hi experts,
     I am working on xcelsius 2008 enterprise edition with sp3 and fp4. I have to clear about my doubts.
   I have created the QAAS connection for one of my dashboard. It shows data after generation to swf file in the desktop.
I have filters for the months (e g. 05.2011,06.2011, etc.,). If I select particular month i will get data for that month.
All are working fine with the connection.
My doubt is,
   The swf generated in the desktop showing the data through the qaas connection or it is downloading the entire data in the swf itself.
   is it getting data updated every time in desktop generated swf file? or it is showing the downloaded data?
I donot want to upload this file into infoview.
Regards,
Dharani

Hi Ameet,
   Thanks for your reply. "When you add a QaaWS connection to bring in the data for your swf you have the Refresh options (Connections -> Usage) that you can define for when you want your data to be refreshed."
IS THIS APPLICABLE FOR LOCALLY SAVED SWF FILE ?
   My question is not refereshing or not.
I want to conform that data show in local drive swf file is live(from qaas connection) or from xml source file i.e swf ?
Example,
    I created Qaas connections with variables based on month.
   if month 05.2011(May 2011) selected in the variable. it will show data in list view component for that month.
So, If I download this dashboard as swf file in local drive. The data shown in the swf is coming from the qaas connections or locally created swf file.
Regards,
Dharani
Edited by: dharani kumar on Jul 22, 2011 8:33 PM

What happends if I dont close the connection

Hi,
I would like to know what happends if I dont close the connection after processing. we wont get any compile time & run time error if you dont close the connection. But why we used to close the connetion. Any specific reason for this. Please let me know.
Regards,
Satish

What happens if you don't close a connection? It depends on how many connections you open and how long your program keeps running.
Let's start with the case of a standalone program that runs for a little while then exits.
While the program is running, the operating system maintains a network connection to the database server for each open database connection; there are system limits on the number of open network connections, although this is usually a very high number. Also, every open connection to a database uses resources of the database; many databases have limits on the number of connections they can have open at once. Some database products or configurations (Oracle in "dedicated" mode) will also start a seperate process on the server for each open connection; too many open connections and these processes start swapping out to disk, too many more and the server runs out of memory.
When the program exits, the operating system will close any open network connections; the database server will also recognize that the network connections are closed. If the database supports transactions and the connection was in a transactional mode and there were uncommitted transactions, then the uncommitted transactions will be rolled back. Ultimately, all the database resources get released (assuming there are no bugs in the database program).
Thus, a program that runs for a few minutes, commits all its transactions and exits without closing connections doesn't do major harm; the operating systems of both the client and the database server clean up the network connection and the database itself cleans up the database connection. It's all designed this way because programs sometimes crash; you can't have a system/database that breaks when that occurs... However, this cleanup is not always absolutely immediate on program exit; it usually takes a short time, seconds to minutes, for everything to clean up. Therefore, if the same programs is run over and over real fast, it becomes possible to exhaust a resource, such as memory or network connections. For a quick little test program that's run once and that's it, no problem...
Now for a long running prgram, such as a web application that will run for days or months...
As I've alluded to above, each database connection uses system resources, both on the client machine and on the database server. When a connection is maintained open, those resources are tied up; there's always a limit on the total number of connections that can be supported, although with the right software, hardware and database configurations that limit can be a huge number, tens of thousands. For other systems, it might be a low number, hundreds or less. Whatever it is, the program could potentially reach that limit and cause something to fail. If it doesn't reach that limit (or cause another program to push past the limit) then there's no problem (other than a potential performance impact).
Now within a Java program, the JDBC standard requires that when an open database connection object is garbage collected, the connection is first closed. Assuming your driver conforms to the standard in this regard, and assuming no resource limit gets exceeded, then a long running program could open and abandon connections and let the garbage collector close and clean up. However, garbage collection is unpredictable, and connections are often sufficiently long lived that they get moved out of the "Eden" memory space and into the space of long-lived objects. These objects are only garbage collected when a "full" garbage collection takes place; a "partial" collection only examines the "Eden" space. Thus, depending on the applications load and memory usage and connection usage pattern and garbage collection configuration, an abandonded connection might not be garbage collected for hours or even days, greately increasing the chances that you run out of resources.
In other words, not closing your connections in a long running program is a really really bad idea.

DB Connection Usage

Similar Messages

Maybe you are looking for