JCo Pool Configuration

hi all,
We have a new implementation of ERP2005 with EP7 of NW2004s and we will be primarily using ESS/MSS applications. The total number of users will be around 8000
can anyone help me with the JCo Pool Configuration. How much should I set the pool size and Maximum Connections
The default is set as follows
<b>maximun Pool Size: 5 
Maximum Connections: 10</b>
For JCo Application Data we are using SSO and for Meta data we are using a generic service user id with USER ID/ Pwd authetication with the needed authorizations at the back end.Is this a good practice?
Thanks in advance
regards
Madhu

Hello,
we have the same problem ERP2005 / EP7 SP9 and ESS/MSS by 8.000 user max but concurrent we think only 500 user using the ESS/MSS services.
If I read your answer, then I think that the application JCO pool can be lower as the Meta-Data Pool ??
I had try to set both (Application and Meta data) for the same value...
maybe wrong for 500 user / most 2 Browser sessions open and have 1/2 webdynpros per page (ESS)...
My urgent's problem reading all manuals about this topic are: is there any different between the  METADATA JCO pool parameter and the Application JCO pool parameter ? In some guides was the Meta-JCO's settings less then the application-JCO´s... ??
My assumption for app. 500 concurrent user are at the moment the following:
Maximal Pool Size :  6
Maximum Connections:  1000
Connection Timeout (msec.):  90
Maximum Waiting Time (msec.):  45
Can somebody please check this values ?
THX
Mario

Similar Messages

  • Thread pool configuration for write-behind cache store operation?

    Hi,
    Does Coherence have a thread pool configuration for the Coherence CacheStore operation?
    Or the CacheStore implementation needs to do that?
    We're using write-behind and want to use multiple threads to speed up the store operation (storeAll()...)
    Thanks in advance for your help.

    user621063 wrote:
    Hi,
    Does Coherence have a thread pool configuration for the Coherence CacheStore operation?
    Or the CacheStore implementation needs to do that?
    We're using write-behind and want to use multiple threads to speed up the store operation (storeAll()...)
    Thanks in advance for your help.Hi,
    read/write-through operations are carried out on the worker thread (so if you configured a thread-pool for the service the same thread-pool will be used for the cache-store operation).
    for write-behind/read-ahead operations, there is a single dedicated thread per cache above whatever thread-pool is configured, except for remove operations which are synchronous and still carried out on the worker thread (see above).
    All above is of course per storage node.
    Best regards,
    Robert

  • About the JCO's configuration...

    Dear,
    I have two questions:
    1) What the usage of "Extented Configuration Management (XCM)".
    2) What the usage of JCO configuration in Web Dynpro or SLD?
    Thanks.

    Hi Jie,
    1) Extended Configuration Management (XCM) Administration tool to configure Web applications after you  have installed the Web components.
    You can get more about this in
    http://help.sap.com/saphelp_crm60/helpdata/en/0f/f8a642a4f70c31e10000000a1550b0/content.htm
    2) SLD is used to store the connection properties of Java system and ABAP System.
    JCO Destinations acts as interface between web AS Java Technical system and Web AS ABAP Technical system.
    In an Webdynpro application we will use RFC's and BAPI's, if u want to communicate with ECC via webdynpro java application these SLD and JCO's  configurations are mandatory.
    See this document, how to configure it.
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c0c1d495-048e-2b10-babd-924a136f56b5
    Regards,
    Pradeep Kumar G

  • How to change the connection pool configuration on OC4J?

    Hi everybody,
    I am developing an application with JDeveloper which is running on an OC4J standalone server, we have 2 enviroments, the develop server and the server of the client, and the data base connection configurations are differents.
    The problem is that if we try to deploy the application (we have deploy on the develop server) on the client server and try to change the connection pool configuration the application cannot connect to the data base, we need to re-build the project with the client connection pool configuration.
    We tried to change the configuration on the enterprise manager of the OC4J, on "JDBC Resources" panel, and the test the connection is ok, but when try to access to the application we get an Exception. After that we try to do that changing the parameters from the datasources.xml file on the application, but the result is the same.
    How can we change the DataBase configuration without re-build the project?
    Thanks very much
    Tony

    Meaning you have created just the empty data-sources.xml and not configured any Connection Pool and DataSource in JDev?
    In Oracle AS 10.1.3 you have two ways to do this:
    1. Use JDev and configure the data-sources.xml (Context Menu -> Properties)
    2. In Oracle AS: Select application -> Administration -> Services -> JDBC Resources -> Create Pool and Create DataSource
    --olaf                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • ACE: Significance of mask in nat-pools configured for Source NAT

    Hi guys
    If I am using source nat in ACE (One IP address 10.10.10.200) used for all client address translations.
    What would be the difference between the nat-pools configured with different netmask.
    What is the recommended netmask for pat, 255.255.255.255 or Vlan interface's Mask (/24 in this case)
    and why?
    case1:
    interface vlan 7
    ip address 10.10.10.100 255.255.255.0
    nat-pool 1 10.10.10.200 10.10.10.200 netmask 255.255.255.0 pat
    service-policy input clientvips
    no shutdown
    case2:
    interface vlan 7
    ip address 10.10.10.100 255.255.255.0
    nat-pool 1 10.10.10.200 10.10.10.200 netmask 255.255.255.255 pat
    service-policy input clientvips
    no shutdown
    Thanks in Advance
    A.

    Gilles
    Thanks a lot. It makes more sense now.
    I posted another question for an ACE design validation. Could you please validate this
    I am planning to deploy ACE module in following manner:
    > ACE will be in one arm mode ( Only one vlan connected to the ACE).
    > Vips & Rservers (all serverfarms) will be in the same Vlan X.
    > Default gateway on the ACE & Real servers will be the upstream router
    > There will be Source NAT configured for all Serverfarms.
    ACE --- Vlan X -------Router--- internet
    .................|
    .................|-- Sfarm 1
    .................|
    .................|-- Sfarm 2
    .................|
    .................|-- Sfarm n
    I am pretty sure that it should work.
    Just wanted an expert opinion.
    Thanks

  • Need Extended Version of JCO Pool Viewer Tool for SSO Expiration Problem

    Hi, SDN Fellow.
    When we are running some of our Web Dynpro application, it ran into this error". Cannot create JCOClientConnection for Logical System XXXXX_WD_MODELDATA_DEST - Model class xxxxx. The SSO ticket needed for authentication to  XXXXX_WD_MODELDATA_DEST has expired. Close all applications and lofon anew!"
    We have researched on this error, and find that the optimal fix is to upgrade to SP12, then use the Assertion Ticket. But we are currently not ready to apply SP12 from SP11 yet.
    I have read about SAP Note 1130191 - JCO Pool Viewer Tool for SSO Expiration Problem.
    For workaround fix, we decided to try out Extended Version of JCO Pool Viewer Tool to clear the cache when this error occurs.
    The note did not mention where can I get the tool. I remembered I read a blog on this tool too, but could not recall the blog link. Can anyone guide me where can I get this tool?
    Thanks,
    Kent

    Hi Cui,
    Navigate to Content Admin-> Web Dynpro-> SAP.COM space in left navigation area.
    There you can find the EAR/WAR file for this tool, open it and click on run.
    Now it will show you list of threads which are faulty, you can remove the faulty thread from this list.
    So no server restart is needed in case of one thread failure.
    If you are not able to get this tool, I will mail it to your ID.
    regards
    Kedar Kulkarni
    Reward points for useful answers
    Edited by: Kedar Kulkarni on Jun 18, 2008 2:58 PM

  • Problem to JCO after configure ModelData

    Hello dear Experts.
    I have a DC Web dynpor java when i depploy my DC and tray to configure the ModelData at the end of the  asisstant of creating this when i press button finish i got the next error:
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       java.lang.NullPointerException
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
        at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:485)
        at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.updateJCOClientStatus(JCOConnectionsDetails.java:481)
        at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:700)
        at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:664)
        ... 39 more
    If i enter to the Portal content Studio in order to configure this JCO again i got the same exception We have to restart server
    to enter to the JCO maintenance of content portal studio.
    I am sstuck in this problem.
    Thanks for helping me.

    Hi,
    Please look at these links for that
    [Problem to JCO After Configure ModelData|http://www.qnasap.com/problem-to-jco-after-configure-modeldata/] and [Null pointer while maintaining JCO destination|Null pointer while maintaining JCO destination;
    Hope this is help full for you,
    Regards
    Vijay

  • Clean JCO pool

    Hi,
    How can I clean the Jco Pool from WebDynpro?
    Thanks,
    Aviad

    Hi ..
    <b>disconnect</b>
    Chk this link.
    When should we call disconnectIfAlive()
    you can use this also..
    MultiModel empModel = (MultiModel) DModelFactory.getModelInstance(MultiModel.class);
    empModel.disconnectIfAlive();
    hope this will help u..
    Urs GS

  • AM Pooling Configuration Parameters ??

    Hi ,
    I have one application module in my ADF Application. and 30 concurrent users are going to use my application.
    Any one can give me the exact parameters for AM Pooling configuration :
    Pooling and Scalability :-
    Initial Pool size : ??
    Max Pool size : ??
    Referenced Pool Size : ??
    Minimum Available size : ??
    Maximum available size : ??
    Thanks,
    Rajesh.
    Edited by: Rajesh Etraju on Dec 17, 2012 7:13 AM

    Hi,
    i had set everything as per the guidelines only ,like below..
    For 30 Concurrent users :
    Initital PoolSize : 33
    Maximum Poolsize : 100
    Referenced Pool Size : 10
    Minimum Available Size : 5
    Maximum Available Size: 20
    Idle InstanceTimeOut : 120(sec)
    Pool Pooling Interval : 60(sec)
    Still same problem with the above mentioned settings.
    Any more thoughts !!
    --Rajesh                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • JCO Pooling problem

    Dear members,
    We are experiencing some troubles with establishing a JCO Pool to an ECC backend. We want to call a BAPI to get employeenumber from uid. Our Java devver has implemented some code to set up JCO Pooling, but we are facing problems
    I have made a screen dump from VA, but I can not identify the point of failure:
    http://tweakers.net/ext/f/76d8bc3905102cbf05f5a3d77675a4a8/full.jpg
    Can anybody help me? Thanks a lot in advance!
    Best regards,
    Jan Laros

    I have to wait to download the default trace file, but i found some strange errors in another log file (dev_jrfc.trc in /usr/sap/<SID>/JC00/j2ee/cluster/server0). This error is from yesterday afternoon. When I now preview the created iView in which the JCO Pool is used, no error is raised. So I am not sure if this is related to my code.....
    [code]**** Error file opened at 20070910 162312 Central European Summer Time Rel 6.45.12 (2007-02-07) [700.102]
    Error> occured  >Mon Sep 10 16:23:12,491<
    RfcException:
        message: 'user' missing
        Return code: RFC_INVALID_PARAMETER(19)
        error group: 101
        key: RFC_ERROR_PROGRAM
            at com.sap.mw.rfc.api.RfcOptions.checkLogonData(RfcOptions.java:201)
            at com.sap.mw.rfc.api.RfcOptions.checkParameters(RfcOptions.java:498)
            at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:707)
            at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1008)
            at com.sap.mw.jco.JCO$Client.connect(JCO.java:3255)
            at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnection.connectWithJCO(SAPCFConnectorManagedConnection.java:394)
            at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnection.establishInitialConnection(SAPCFConnectorManagedConnection.java:203)
            at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnection.init(SAPCFConnectorManagedConnection.java:182)
            at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnectionFactory.createManagedConnection(SAPCFConnectorManagedConnectionFactory.java:129)
            at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:320)
            at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:188)
            at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorConnectionFactory.getConnectionEx(SAPCFConnectorConnectionFactory.java:155)
            at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:295)
            at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:256)
            at com.sapportals.portal.ivs.cg.ConnectorService.getConnection(ConnectorService.java:446)
            at com.sapportals.portal.ivs.cg.ConnectorService.getConnection(ConnectorService.java:84)
            at com.sap.portal.ivs.slcockpit.tests.TestConnectorConnection.isConnectionOK(TestConnectorConnection.java:257)
            at com.sap.portal.ivs.slcockpit.tests.TestConnectorConnection.startTest(TestConnectorConnection.java:209)
            at com.sap.portal.ivs.slcockpit.editor.panes.SLCockpitTestPane.setResults(SLCockpitTestPane.java:205)
            at com.sap.portal.ivs.slcockpit.editor.panes.SLCockpitTestPane.createUI(SLCockpitTestPane.java:165)
            at com.sap.portal.admin.editor.pane.EditorPaneProxy.createUI(EditorPaneProxy.java:130)
            at com.sap.portal.admin.editor.pane.OutPane.setupComponent(OutPane.java:122)
            at com.sap.portal.admin.editor.pane.EditorPaneWrapper.mySetupComponent(EditorPaneWrapper.java:143)
            at com.sapportals.admin.wizardframework.components.FlowContainer.setupComponent(FlowContainer.java:129)
            at com.sapportals.admin.wizardframework.core.TrivialPaneFactory.getComponent(TrivialPaneFactory.java:35)
            at com.sapportals.admin.wizardframework.core.WizardInstance.doWizard(WizardInstance.java:229)
            at com.sap.portal.admin.editor.Editor.doWizard(Editor.java:605)
            at com.sap.portal.admin.editor.Editor.run(Editor.java:150)
            at com.sap.portal.admin.editor.AbstractEditorComponent.doContent(AbstractEditorComponent.java:59)
            at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
            at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
            at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
            at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
            at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
            at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
            at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
            at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
            at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
            at java.security.AccessController.doPrivileged(AccessController.java:204)
            at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
            at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
            at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
            at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
            at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
            at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
            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(AccessController.java:180)
            at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Error> occured  >Mon Sep 10 16:23:12,621<
    RfcException:
        message: 'user' missing
        Return code: RFC_INVALID_PARAMETER(19)
        error group: 101
        key: RFC_ERROR_PROGRAM
            at com.sap.mw.rfc.api.RfcOptions.checkLogonData(RfcOptions.java:201)
            at com.sap.mw.rfc.api.RfcOptions.checkParameters(RfcOptions.java:498)
            at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:707)
            at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1008)
            at com.sap.mw.jco.JCO$Client.connect(JCO.java:3255)
            at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnection.connectWithJCO(SAPCFConnectorManagedConnection.java:428)
            at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnection.establishInitialConnection(SAPCFConnectorManagedConnection.java:203)
            at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnection.init(SAPCFConnectorManagedConnection.java:182)
            at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnectionFactory.createManagedConnection(SAPCFConnectorManagedConnectionFactory.java:129)
            at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:320)
            at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:188)
            at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorConnectionFactory.getConnectionEx(SAPCFConnectorConnectionFactory.java:155)
            at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:295)
            at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:256)
            at com.sapportals.portal.ivs.cg.ConnectorService.getConnection(ConnectorService.java:446)
            at com.sapportals.portal.ivs.cg.ConnectorService.getConnection(ConnectorService.java:84)
            at com.sap.portal.ivs.slcockpit.tests.TestConnectorConnection.isConnectionOK(TestConnectorConnection.java:257)
            at com.sap.portal.ivs.slcockpit.tests.TestConnectorConnection.startTest(TestConnectorConnection.java:209)
            at com.sap.portal.ivs.slcockpit.editor.panes.SLCockpitTestPane.setResults(SLCockpitTestPane.java:205)
            at com.sap.portal.ivs.slcockpit.editor.panes.SLCockpitTestPane.createUI(SLCockpitTestPane.java:165)
            at com.sap.portal.admin.editor.pane.EditorPaneProxy.createUI(EditorPaneProxy.java:130)
            at com.sap.portal.admin.editor.pane.OutPane.setupComponent(OutPane.java:122)
            at com.sap.portal.admin.editor.pane.EditorPaneWrapper.mySetupComponent(EditorPaneWrapper.java:143)
            at com.sapportals.admin.wizardframework.components.FlowContainer.setupComponent(FlowContainer.java:129)
            at com.sapportals.admin.wizardframework.core.TrivialPaneFactory.getComponent(TrivialPaneFactory.java:35)
            at com.sapportals.admin.wizardframework.core.WizardInstance.doWizard(WizardInstance.java:229)
            at com.sap.portal.admin.editor.Editor.doWizard(Editor.java:605)
            at com.sap.portal.admin.editor.Editor.run(Editor.java:150)
            at com.sap.portal.admin.editor.AbstractEditorComponent.doContent(AbstractEditorComponent.java:59)
            at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
            at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
            at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
            at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
            at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
            at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
            at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
            at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
            at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
            at java.security.AccessController.doPrivileged(AccessController.java:204)
            at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
            at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
            at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
            at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
            at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
            at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
            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(AccessController.java:180)
            at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)[/code]

  • JCO Pool Connection - how to determine max_connections?

    Hi
    I have just written a web application which utilises the JCo connector for EP5 and allows the user to communicate with R/3 for retrieving user information.  I am using the JCo Pooling technique to reuse JCO connections.  The question that I have is - how do I guesstimate what a good number would be for the maxConnections argument in the following line of code:
    JCO.addCientPool(poolName, maxConnections, client, uname, password, <i>etc</i>);
    The entire user population is about 5000 and not all of them will be using the web app at the same time.  What would be a good number of max connections to use - 100, 500??  I dont want the web app to fall over or for users to have to wait too long.  Any comments/suggesstions will be greatly appreciated. 
    Thanks
    Ankit

    Hi,
    does every user have an own R/3 account? In this case you are creating a different pool for every user, so there would'nt be a lot of reusing JCO Clients. So I guess a max number of 2-3 would be enough.
    If you are using the same R/3 account for all web users a max pool size of 100 seems reasonable for me.
    Hope that helps.

  • Buttons disabled while creating JCO- SLD configured in solman

    Hi All,
    I have configured SLD in solman.And I have made relevant entries in Visual Administrator also.
    When I try to create jco in my portal,all buttons are disabled.
    I had faced this problem when I had configured SLD in portal itself and that got resolved after I searched through the forum.
    But here I have no clue where i am going wrong.
    Regards
    Akshaya

    Hi,
    Check all these in VA.
    Go to Visual Composer
    1)Make new Connecion
    a)User name->
    b)Host ->
    c)Port->50004
    Goto cluster ->got to server->services->sld Data supplier.
    Set RFC Settings
    a)Gateway Host ->ip of ep
    b)GateWay service/port->sapgw00/3300
    CIM client generation settings
    Host->ip address of ep
    Port ->50000
    user->
    Set Http Settings
    Host->ip of ep
    port->50000
    user->j2ee_admin
    Do these steps  and check the CIM generation has displayed successfully or not.?
    It might helps you.

  • Which BC4J / JDBC pooling configurations are global for a JVM?

    There are several documents and postings saying that some of the BC4J / JDBC Pooling properties are unique for the JVM.
    So if i have 3 WAR files with 3 different settings in bc4j.xcfg (transaction factory, pooling settings) some of the settings are ignored after the first AM Pool is instanciated. This could be the reason for some "unreproducable" problems we have.
    So please provide us a list, which properties additional to the ones below are global per JVM and which are really used from the bc4j.xcfg.
    1. Getting the Connection object out of ApplicationModule says about the TransactionFactory
    Please not that this property is a static BC4J property. Meaning that the value of this property when the first ApplicationModule is created is the value which will be used. If you have multiple ApplicationPool(s) then it is necessary to define the property in all configurations, dynamically, or as a system property.
    2. http://www.oracle.com/technology/products/jdev/tips/muench/ampooling/index.html says about jbo.ampool.monitorsleepinterval
    Since there is only a single application monitor pool monitor per Java VM, the value that will effectively be used for the AM pool monitor polling interval will be the value found in the AM configuration read by the first AM pool that gets created. To make sure this value is set in a predictable way, it is best practice for all application modules to use the same Pool Polling Interval value.
    and
    3. Since the tuning parameters for all ADF database connection pools - regardless of <JDBCURL,Username> value - will be set based on the parameters found in the configuration for the first AM pool that is created. To insure the most predictable behavior, it is best practice to leave the values of the parameters in the Connnection Pooling section of the Pooling and Scalability tab at their default values - so that no entry for them is written into the bc4j.xcfg file - and to instead set the desired values for the database connection pooling tuning parameters as Java System Parameters in your J2EE container.
    Sounds like this means the parameters: jbo.initpoolsize, jbo.maxpoolsize, jbo.poolmonitorsleepinterval, jbo.poolmaxavailablesize, jbo.poolminavailablesize, jbo.poolmaxinactiveage ?
    4. And http://oracle-web.petersons.com/bc4jdoc/bc_aappmodpooling.htm tells There is one connection pool manager for each business logic tier's Java VM. Connections remain in the pool until the Java VM stops running.
    Thanks, Markus

    Just another funny observation regarding BC4J parameter settings in 9.0.5.2:
    Setting jbo.ampool.sessioncookiefactoryclass in the jboserver.properties is ignored. Setting in bc4j.xcfg works.
    rgds, Markus

  • Oracle JDBC Pool Configuration problems

    Hi all,
    I'm usin oracle 8.1.6 & thin driver (classes12.zip).
    I've set up correctly a pool in a wl 6.1 windows 2K machine.
    I've copied EXACTLY the configuration values in a wl 6.1 solaris 7 machine and
    doesn't works (it seems wl can't find the listener).
    My cuestions;
    -Why the wl console adds automatically the propertie dll=ocijdbc8 when i'm configuration
    the pool? I don´t want to use the OCI driver!
    -Can this be the problem?
    -Should I place classes12.zip first on the classpath than weblogic.jar?
    TIA.
    Pablo.

    Hi. The issue isn't the zip, it's probably the properties you supply for the pool.
    The oracle driver will try to use the type-2 native libraries if you specify
    a server in the properties.
    Joe
    Pablo wrote:
    Hi all,
    I'm usin oracle 8.1.6 & thin driver (classes12.zip).
    I've set up correctly a pool in a wl 6.1 windows 2K machine.
    I've copied EXACTLY the configuration values in a wl 6.1 solaris 7 machine and
    doesn't works (it seems wl can't find the listener).
    My cuestions;
    -Why the wl console adds automatically the propertie dll=ocijdbc8 when i'm configuration
    the pool? I don´t want to use the OCI driver!
    -Can this be the problem?
    -Should I place classes12.zip first on the classpath than weblogic.jar?
    TIA.
    Pablo.

  • Tomcat connection pooling configuration

    I have configured the datasource with connection pool as per
    http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html
    All the required jar fles are in $CATALINA_HOME/common/lib.
    When I run my app,I am getting the following error even though commons-pool.jar file is there which contains GenericObjectPool.class file
    java.lang.NoSuchMethodError: org.apache.commons.pool.impl.GenericObjectPool: method <init>()V not found
    at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:652)
    at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:403)
    Did anyone run into similar issue?
    Thanks

    I am running into this same issue at the moment.
    If you found the solution, it would be much appreciated if you could give me some insight into this problem.
    Thanks.

Maybe you are looking for

  • I have a yahoo search at the bottom of mozilla page and want it gone.

    My son installed a video game and didn't catch the yahoo search. The yahoo search is at the bottom of the page along with my weather info I have added on. This is not an extension or an add-on that I can just simply go into add-ons and uninstall it.

  • AP Discount on Vendor Payment

    Hi FI Gurus, Can you please help with the below.... When I run Payment program for Vendor (Transaction F110), system is taking/considering the discount amount even after the expiry of the cash discount period (as per vendor/invoice payment terms). Id

  • Z-Report Preparation

    Hi, I want to know basics in preparing the Z-Reports. I mean when you do confirmation where the data will be saved? the table name that appears in CO11N screen (by clicking F1-> Tech info) will remain same when we save? or will it change? any specifi

  • Safari behaving differently with site on .mac/external server

    Hello. I've started creating a little webpage of mine and I've noticed that when uploaded to .mac the top bar (for selecting pages within the site) works correctly, but when the site is uploaded to an external server the top bar goes bust. It is so u

  • Exception Handling of JboException with Struts  Jun 25, 2003 9:46 AM

    Hi, I am using BC4J with Struts. The struts <html:errors/> tag displays all the exception messages generated by ActionErrors and JboExceptions automatically. The problem i have is, I get a Jbo-26041 exception when i try to create a duplicate primary