JCo Server Load Balancing

We have created a JCo Server interface using RFC modules in SAP to communicate with an external web based system.  The SAP system calls the external application via tRFC and qRFC as needed from the business transaction.  We have achieved high throughput by clustering our external web application server, putting a load balancer in front of that web application, and finally creating multiple JCo Server instances within own JVMs (currently 6 instances with 5 servers each).  The JCo Server is registered to the central gateway of the SAP system using gwhost, gwserv, and progid.  With this setup we have successfully performed up to 50,000 transactions an hour.
My understanding is that the SAP gateway will act as a load balancer on the SAP side.  Is this right or should we consider to install a hardware load balancer "in front" of the SAP gateway and try to map this to the message server instead?  Or concern is that our JCo Server process will "flood" the central gateway and take all resources away form the SAP system.  Unfortunately the JCo Server class doesn't allow to connect to any other resource on the SAP system then the central gateway.
Any suggestions or real live examples are appreciated.
Stefan

Hi Stefan
We are doing a similar project wherein we are calling a middleware server based on the JCO.Server from SAP.
You did say that you have achieved a throughput of 50000 transactions and we are interested in knowing how ?.
Could you briefly tell use how you achieved it. In our case we have one instance of the JCO.Server working on the JVM.
Here is what we did .
We tried to start two instances of the middle ware server on the same JVM on the same BOX and register it with the gateway . This dint work .
We were successfull in starting two instances of the middleware server from two different JVM on two different boxes and registering it at the gateway under the same id.
This we know will work as the gateway will use its load balancing to distribute load between the two instances.
But we are interested in knowing how we can start more then one server instance on a given JVM.
Our questions are
It we have threading in our middleware server, we believe it will not help as if the SAP gateway server has opened an connection with one instance of the middleware server. It is not possible for it to open another one...till the first one is complete. Hence threading within the middleware server is redundant.
Your thoughts and comments are appreciated.

Similar Messages

  • Error in creation of JCO with Load balancing server

    Hi,
    We are using a ABAP user base for our WEBAS server 6.40 (with ABAP+JAVA). i have created a Public group in concerned ECC 5.0 system. I have already configured SLD, and then i maintain data supplier bridge in SLD and run RZ70 in ECC 5.0 system to load system information.. i can see details in SLD ..
    now i am trying to create JCO connections .. here i am unable to create JCO with load balancing option..  i get
    com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM  TYPE=B MSHOST=<servername> GROUP=PUBLIC R3NAME=SID MSSERV=sapms<SID> PCS=1 ERROR       service 'sapms<SID>' unknown TIME        Fri Jun 16 12:41:20 2006 RELEASE     640 COMPONENT   NI (network interface) VERSION     37 RC          -3 MODULE      ninti.c LINE        505 DETAIL      NiPGetServByName2: service 'sapms<SID>' not found SYSTEM CALL getservbyname_r COUNTER     1
    i am able to create single server JCO, but it fails in load balancing.. is there anything i have  missed out in settings...
    Thanks and regards,
    Sudhir

    Thanks, Bogdan Rokosa
    I have the same problem,and solved it following the steps provided by Bogdan Rokosa  :
    you must insert an entry for your R3 system
    (like: sapms<SID> 3600/tcp)
    in services file
    (C:\WINDOWS\system32\drivers\etc\services) on Java WAS.
    I test the Jco successful without restart J2EE Engine.

  • Using ACE for proxy server load balancing

    Hello groups,
    I wanted to know your experiences of using ACE for proxy server load balancing.
    I want to load balance to a pool of proxy servers. Note: load-balancing should be based on the HTTP URL (i can't use source or dest. ip address) so that
    a certain domain always gets "cached/forwarded" to the same proxy server. I don't really want to put matching
    criteria in the configuration (such as /a* to S1, /b* to S2, /c* to S3,etc..), but have this hash calculated automatically.
    Can the ACE compute its own hash based on the number of "online" proxy servers ? ie. when 4 servers are online, distribute domains between 1,2,3,4 evenly.
    Should server 4 fail, recalculate hash so that the load of S4 gets distributed across the other 3 evenly. Also load-balancing domains of S1 ,S2 and S3 should not change if S4 fails.....
    regards,
    Geert

    This is done with the following predictor command:
    Scimitar1/Admin# conf t
    Enter configuration commands, one per line.  End with CNTL/Z.
    Scimitar1/Admin(config)# serverfarm Proxy
    Scimitar1/Admin(config-sfarm-host)# predictor hash ?
      address         Configure 'hash address' Predictor algorithms
      content         Configure 'hash http content' Predictor algorithms
      cookie          Configure 'hash cookie' Predictor algorithms
      header          Configure 'hash header' Predictor algorithm
      layer4-payload  Configure 'hash layer4-payload' Predictor algorithms
      url             Configure 'hash url' Predictor algorithm
    Scimitar1/Admin(config-sfarm-host)# predictor hash url
    It does hash the url and the result takes into account the number of active proxies dynamically.
    This command has been designed for this kind of scenario that you describe.
    Gilles.

  • App.server load balancing for SAP System with 1 PS

    Hi,
    In SAP CPS 7.0 (Build M26.12) I have a SAP system with Central Instance + 10 App.servers, but all instances are managed by 1 ProcessServer.
    After activating the "App.server load balancing" setting in SAP system definition the application servers are becoming visible in CPS with their load factors (number of BGD wp's on app.servers) and load numbers (number of active jobs on app.servers).
    This is so far fine, but the additional functionality is not working as I would expect, I have issues with 2 functionalities:
    1. Based on documentation after activating also the XAL connection the CPS should submit the job on app.server with best performance based on XAL monitoring data filling the TARGET_SERVER parameter.
    This functionality is not working for me at all
    2. A useful functionality after activating the "App.server load balancing" setting is that the ProcessServer is going to "Overloaded" status when all BGD wp's of SAP system are occupied, thus restricting submitting new jobs during overload situation. But I had an issue also with this functionality, after SAP system recovery from overload situation, the CPS still remained in Overload status (so no new jobs were submitted).
    As a workaround I had increased the treshold values for loads on all app.servers for this SAP system, what was fine for several days, but after a while I believe this was a reason of unexpected performance issues in CPS, therefore I have deactivated the 'App.server load balancing" setting at all for this ProcessServer.
    I would appreciate your feedbacks with this functionality.
    Thanks and Regards,
    Ernest Liczki

    Hi Preetish,
    This connect string option is to loadbalance RFC connections. These are balanced upon login, once you are connected to a particular application server (AS) you stay on that server until you reconnect.
    Since CPS uses multiple RFC connections, this will result in the connections being distributed over the available AS resources which is fine as long as they are generally evenly loaded. If you have certain AS hosts that are continuosly more loaded than the rest, then you probably don't want the CPS RFC connections to end up on these servers.
    The original question is about loadbalancing of batch jobs over the available AS resources, and this is done independent of the RFC connection load balancing. Even if all CPS RFC connections are pinned to the DB/CI host, you can still loadbalance jobs over the available SAP AS hosts, either by using SAPs builtin balancing, or the CPS algorithm by activating the checkbox as indicated in the first entry in this thread.
    Finally, to reply to Ernest's question: I believe there are some fixes on the app load balancing in the latest release, M26.17 should be available on the SWDC now.
    Regards,
    Anton.
    Edited by: Anton Goselink on May 29, 2009 9:06 PM

  • Dev6 Server Load Balancing

    Hi
    I try to install Load Balancing with Dev6/Patch2 and OAS4.0.7.1
    on 4 Machines with WinNT Server 4 SP 5. I tried to do it as
    described in the documentation. But I did not succeed. It seems
    to be that the Doc is not complete or wrong. Could somebody give
    an example how to set up the LB Servers and Clients as NT
    Services ?
    Thank's in advance
    Charly
    null

    Hi Steven,
    No LACP and SLB are different.
    LACP is the Link Aggregation Control Protocol, which is the protocol used within the IEEE 802.3ad (now 802.1AX) Link Aggregation mechanism to control the bundling and unbundling of the physical links into an aggregate link.
    Server Load Balancing is a feature in IOS to load balance traffic destined to a virtual IP across a group of real IP. From Configuring Server Load Balancing:
    The SLB feature is a Cisco IOS-based solution that provides IP server load balancing. Using the IOS SLB feature, the network administrator defines a virtual server that represents a group of real servers in a cluster of network servers known as a server farm.
    Server Load Balancing is effectively what the Cisco Application Control Engine (ACE) etc., does but in IOS.
    Regards

  • Server Load balancing issues

    the servers are loadbalancing between the switches '3'
    and '2' and the link between the two switches is blocked.
    This link was forwarding before and thus any traffic going to the server was
    send to the Servers correctly no matter on which switch they are active.
    However after addition of another link in between the switches 'root'
    and '1', the path cost to the root has decreased and thus the link
    between the '2' and '3' is Blocking and the other link between
    the '2' and '1' is Forwarding as it should be ideally. But
    this would be creating an issue because the trafic coming from outside i.e.
    through switch '1' to the server will be correctly send to the
    server if the server NIC is active on the '3' because the Virtual MAC
    addresses are binded accordinlgy. In case the server falls onto the other
    NIC which is on the '2' the traffic won't be able to pass because the
    MAC address is not binded on the trunk connecting the switches '1'
    and '2'. This binding cannot be done because the same MAC address is
    being learned on the another trunk on the '1' which is connecting
    to 'root'. So if we bind the same Virtual MAC on two trunks on the same
    switch ('1') then this will cause MAC Address Flapping on the
    switch and hence canot be done.
    In another case,we can able to bind virtuak MAC on two trunks on the same
    switch('1') and it's working fine.
    The servers are load balancing in round robin fashion. each server has 2 NICs and work in Active-Passive mode. The servers load balance each other when all their active links are connected to '3' switch but when two of the active NICs of two servers are connected to '3' and the rest of the two active NICs from the other two servers are connected to '2' switch then only the forst 2 servers load balance and the other 2 servers do not load balance.
    Please help.
    Thanks in advance.

    In my experience, server load balancing is one of the most difficult things to get going properly in a switched LAN environment. Switched LANs are designed so that one MAC address can only be bound to one switch port. Therefore, if you have two NICs with the same MAC address (real or virtual), then you will get flapping somewhere.
    I have seen various ways that the manufacturers try to get around this limitation of switched LANs. For example, one technique I have seen, practiced by ISA Server, is to use a multicast MAC address for the service so that frames go to both exit ports. But that does not always work well unless you tweak the network to acommodate it.
    What sort of servers are they, and what system is used for the load balancing?
    Kevin Dorrell
    Luxembourg

  • WLC Radius Server Load Balance

    Hi,
    Can someone provide me detailed description on how WLC Radius Server Load balance works.
    Becuase, I encounted a problem of User Authenticated with the 1st Radius Server, but Accounting Records are actually on 2nd Server .
    Any response will be very appreciated
    -Angela

    Hi Angela,
    I pasted below the part of config guide explaining the different modes. In summary :
    -Fallback off means : when 1st radius server shows dead , WLC moves to the second. And will only change again when the 2nd is dead too.
    -Passive means : whent 1st radius is dead, WLC moves to the second. If there is a new authentication coming in, it will try the 1st radius server again
    -Active means : WLC constantly sends radius probes to detect when primary is back up.
    config radius fallback-test mode {off | passive | active}
    where
    •off disables RADIUS server fallback.
    •passive causes the controller to revert to a server with a lower priority from the available backup servers without using extraneous probe messages. The controller simply ignores all inactive servers for a time period and retries later when a RADIUS message needs to be sent.
    •active causes the controller to revert to a server with a lower priority from the available backup servers by using RADIUS probe messages to proactively determine whether a server that has been marked inactive is back online. The controller simply ignores all inactive servers for all active RADIUS requests. Once the primary server receives a response from the recovered ACS server, the active fallback RADIUS server no longer sends probe messages to the server requesting the active probe authentication.

  • CSM(content switching module) supports the 2 tier server load balance ?

    hi everyone,
    Does any know the CSM support 2 tier server load balance ?
    this means that CSM perform the server load balance for servers and the same servers require another time Server load balance. In the other word,
    the CSM supports server port and client port for server load balance ?
    thanks
    fred.

    Hi, this seems to describe a typical case of multi-tier design where the CSM needs to handle 2 types of connections:
    1. clients->CSM->serverfarm1
    2. serverfarm1->CSM->serverfarm2
    We usually refer to the second type of connections as server-to-server load balanced traffic.
    There is no problem in handling that scenario with the CSM and you have a few options.
    In particular, each virtual server on the CSM can be configured to only accept incoming connections from a specific VLAN, so you can use that as an additional security measure or to distinguish connections based on which VLAN they come in from.
    If you want to, you could even configure the CSM with 2 virtual servers with the same exact virtual IP and L4 port, but listening on 2 separate VLANs (the client-side VLAN and serverfarm1 VLAN) and use a different server farm based on that.
    One important thing to keep in mind when handling server-to-server load balanced connections: if serverfarm1 and serverfarm2 are on the same VLAN, you have to configure "client NAT" for the server-to-server connections, to force the return traffic back to the CSM.

  • Please provide vShield Manager Server Load Balance values

    Hi All:
         I couldn't find values about the server load balance of vShield Manager.
    Please provide these value:
    1. Throughput      Mbps
    2. Web port 80 server load balance connections:
    3. SSL port 443 server load balance connections:
    Thanks
    BR.
                            Vincent

    Hi Vincent,
    Can you please eloborate your question ?

  • Server load balancing for application access using multiple servers

    1.what are the methods supported by cisco switches for load balancing
    2. I want to achive users to access 1 particular ip from different locations but phsically few servers which handle the application and data

    well some servers allow you to install routing protocols on them. you could OSPF some links together.
    or you could NLB if it is a microsoft server. this uses a heartbeat network, a virtual mac and an IP address bound to the vmac.
    you could use NIC teaming. broadcom nics on dell servers allow you to configure them for loadbalancing, failover and a few other options.
    or if the servers are mirrored using MSCS or something similar (i.e configured the same but independant) you could just load balance using DNS.
    hope this helps. jsut some ideas quickly off the top of my head

  • Email send issue using "Mail Server Load balancer"  (Cisco ACE 20)

    Please let me know if someone have experienced this kind of issue or any suggestions.
    The send email action was working file in MII with smtp mail server on port 25. Recently basis did a change in mail server ip address and they installed a new Load Balancer . The Load balancer is between SMTP and MII. After this change MII does not send email (unknown source error). now MII send email action has ip address or qualified path of Load balancer in MII send email configuration instead of direct ip address of SMTP server. Below is the error message in Net Weaver logs.
    MII still sends email if direct ip address of email server  provided but not through email Load balancer .
    Any suggestions ?
    Could not authenticate mail account (Unknown Source)
    [EXCEPTION]
    javax.mail.AuthenticationFailedException
    at javax.mail.Service.connect(Service.java:319)
    at javax.mail.Service.connect(Service.java:169)
    at javax.mail.Service.connect(Service.java:118)
    at com.sap.xmii.storage.connections.MailConnection.sendMail(MailConnection.java:202)
    at com.sap.xmii.bls.executables.actions.mail.MailActions.send(MailActions.java:223)
    at sun.reflect.GeneratedMethodAccessor1412.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:592)
    at com.sap.xmii.bls.engine.ReflectiveAction.doExecute(ReflectiveAction.java:747)
    at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
    at com.sap.xmii.bls.engine.BaseAction.execute(BaseAction.java:76)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runAction(ProductionRunner.java:147)
    at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:50)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
    at com.sap.xmii.bls.executables.controls.Switch.doExecute(Switch.java:131)
    at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
    at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:122)
    at com.sap.xmii.bls.executables.controls.Repeater.doExecute(Repeater.java:113)
    at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
    at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
    at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:64)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
    at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:59)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
    at com.sap.xmii.bls.executables.sequences.RootNode.execute(RootNode.java:39)
    at com.sap.xmii.bls.engine.TransactionInstance.execute(TransactionInstance.java:1001)
    at com.sap.xmii.bls.engine.TransactionInstance.run(TransactionInstance.java:680)
    at com.sap.xmii.bls.executables.actions.logic.LogicActions.transaction(LogicActions.java:310)
    at sun.reflect.GeneratedMethodAccessor387.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:592)
    at com.sap.xmii.bls.engine.ReflectiveAction.doExecute(ReflectiveAction.java:747)
    at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
    at com.sap.xmii.bls.engine.BaseAction.execute(BaseAction.java:76)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runAction(ProductionRunner.java:147)
    at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:50)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
    at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:59)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
    at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
    at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
    at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
    at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:64)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
    at com.sap.xmii.bls.executables.sequences.RootNode.execute(RootNode.java:39)
    at com.sap.xmii.bls.engine.TransactionInstance.execute(TransactionInstance.java:1001)
    at com.sap.xmii.bls.engine.TransactionInstance.run(TransactionInstance.java:680)
    at com.sap.xmii.bls.executables.actions.logic.LogicActions.transaction(LogicActions.java:310)
    at sun.reflect.GeneratedMethodAccessor387.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:592)
    at com.sap.xmii.bls.engine.ReflectiveAction.doExecute(ReflectiveAction.java:747)
    at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
    at com.sap.xmii.bls.engine.BaseAction.execute(BaseAction.java:76)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runAction(ProductionRunner.java:147)
    at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:50)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
    at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
    at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
    at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:122)
    at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
    at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
    at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:122)
    at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
    at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
    at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
    at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:64)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
    at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
    at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
    at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
    at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:64)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
    at com.sap.xmii.bls.executables.sequences.RootNode.execute(RootNode.java:39)
    at com.sap.xmii.bls.engine.TransactionInstance.execute(TransactionInstance.java:1001)
    at com.sap.xmii.bls.engine.TransactionInstance.run(TransactionInstance.java:680)
    at com.sap.xmii.bls.executables.actions.logic.LogicActions.transaction(LogicActions.java:310)
    at sun.reflect.GeneratedMethodAccessor387.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:592)
    at com.sap.xmii.bls.engine.ReflectiveAction.doExecute(ReflectiveAction.java:747)
    at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
    at com.sap.xmii.bls.engine.BaseAction.execute(BaseAction.java:76)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runAction(ProductionRunner.java:147)
    at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:50)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
    at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:59)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
    at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
    at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
    at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:122)
    at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
    at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
    at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
    at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:64)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
    at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
    at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
    at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:122)
    at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:158)
    at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
    at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
    at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:64)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
    at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:59)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
    at com.sap.xmii.bls.executables.sequences.RootNode.execute(RootNode.java:39)
    at com.sap.xmii.bls.engine.TransactionInstance.execute(TransactionInstance.java:1001)
    at com.sap.xmii.bls.engine.TransactionInstance.run(TransactionInstance.java:680)
    at com.sap.xmii.bls.executables.actions.logic.LogicActions.transaction(LogicActions.java:310)
    at sun.reflect.GeneratedMethodAccessor387.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:592)
    at com.sap.xmii.bls.engine.ReflectiveAction.doExecute(ReflectiveAction.java:747)
    at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
    at com.sap.xmii.bls.engine.BaseAction.execute(BaseAction.java:76)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runAction(ProductionRunner.java:147)
    at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:50)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
    at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:59)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
    at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:59)
    at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
    at com.sap.xmii.bls.executables.sequences.RootNode.execute(RootNode.java:39)
    at com.sap.xmii.bls.engine.TransactionInstance.execute(TransactionInstance.java:1001)
    at com.sap.xmii.bls.engine.TransactionInstance.run(TransactionInstance.java:680)
    at com.sap.xmii.Illuminator.connectors.Xacute.XacuteRequestHandler.processQueryRequest(XacuteRequestHandler.java:342)
    at com.sap.xmii.Illuminator.connectors.Xacute.XacuteRequestHandler.QueryRequest(XacuteRequestHandler.java:135)
    at com.sap.xmii.Illuminator.connectors.Xacute.XacuteConnector.doProcessRequest(XacuteConnector.java:86)
    at com.sap.xmii.Illuminator.connectors.AbstractConnector.processRequest(AbstractConnector.java:83)
    at com.sap.xmii.Illuminator.server.QueryEngine.run(QueryEngine.java:41)
    at com.sap.xmii.Illuminator.services.handlers.IlluminatorService.processRequest(IlluminatorService.java:68)
    at com.sap.xmii.Illuminator.services.ServiceManager.run(ServiceManager.java:68)
    at com.sap.xmii.servlet.Illuminator.service(Illuminator.java:68)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    at com.sap.xmii.servlet.ServletRunner.run(ServletRunner.java:80)
    at com.sap.xmii.servlet.ServletRunner.run(ServletRunner.java:44)
    at com.sap.xmii.Illuminator.gui.irpt.ReportParser.processServletRequest(ReportParser.java:610)
    at com.sap.xmii.Illuminator.gui.irpt.ReportParser.parseServletTag(ReportParser.java:276)
    at com.sap.xmii.Illuminator.gui.irpt.ReportParser.parseFile(ReportParser.java:154)
    at com.sap.xmii.Illuminator.gui.irpt.ReportParser.parse(ReportParser.java:119)
    at com.sap.xmii.servlet.ReportServlet.service(ReportServlet.java:90)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:162)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81)
    at com.sap.xmii.system.SecurityFilter.doFilter(SecurityFilter.java:96)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
    at com.sap.xmii.system.SecurityFilter.doFilter(SecurityFilter.java:96)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
    at com.sap.xsrf.filter.XSRFProtectorFilter.doFilter(XSRFProtectorFilter.java:62)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:468)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:399)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:388)
    at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:84)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:244)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
    at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
    at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327)
    Date:
    2014-03-25
    Time:
    14:04:06:176
    Category:
    com.sap.xmii.storage.connections.MailConnection
    Location:
    com.sap.xmii.storage.connections.MailConnection
    Application:
    sap.com/xapps~xmii~ear
    Thread:
    Thread[HTTP Worker [@629095796],5,Dedicated_Application_Thread]
    Data Source:
    j2ee\cluster\server0\log\defaultTrace_00.trc
    Arguments:
    DSR Transaction:

    Have a look at this thread please: 
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/f11f3079-b04a-4a8e-b89e-d56eb0532c42/the-mail-could-not-be-sent-to-the-recipients-because-of-the-mail-server-failure-sending-mail-using?forum=sqldatabaseengine
    Saeid Hasani [sqldevelop]

  • Web Proxy Server Load Balancing

    I deployed Sun Jave Web Proxy Server 4.0 as a Reverse Proxy. I would also like to use it as a load balancer. As per the instructions, I configured the obj.conf file as shown below
    Route fn="set-origin-server" server="https://xx.xx.xx.xx" server="https:yy.yy.yy.yy" sticky-cookie="JSESSIONID" sticky-param="jsessionid" route-hdr="Proxy-jroute" route-cookie="JROUTE" rewrite-host="true" rewrite-location="true" rewrite-content-location="true"
    But, it is not doing load balancing. It always sends to the first server (xx.xx.xx.xx). I guess that is because I used mapping as follows:
    NameTrans fn="reverse-map" from="https:xx.xx.xx.xx" to="https://server.net" rewrite-location="true" rewrite-content-location="true"
    NameTrans fn="redirect" from="http://server" url="https://xx.xx.xx.xx"
    NameTrans fn="map" from="https://server" to="https://xx.xx.xx.xx" rewrite-host="true" name="pa-server-farm1" NameTrans fn="map" from="/" to="https://xx.xx.xx.xx" rewrite-host="true" name="pa-server-farm1"PathCheck fn="url-check"ObjectType fn="block-ip"
    ObjectType fn="cache-enable" cache-auth="1" cache-https="1" query-maxlen="0" min-size="0" Service fn="proxy-retrieve"
    I don't understand how routing and mapping work togother. Any help in this regard is appreciated.

    Motor,
    the following is from the Web Proxy Sever Administration guide. Please, check the last paragraph for the explanation. Any how, the problem is simple. I am using the Proxy Server as the Reverse proxy. And at the same time, I would like to use two origin servers (for load balancing) instead of one. How do I make both load balancing and reverse proxy functions work together?
    Thanks
    To Create Regular or Reverse Mapping
    Access the Server Manager, and click the URLs tab.
    Click the Create Mapping link.
    The Create Mapping page is displayed.
    In the page that appears, provide the source prefix and source destination for the regular mapping,
    for example,
    Source prefix: http://proxy.site.com
    Source destination: http://http.site.com/
    Click OK.
    Return to the page and create the reverse mapping, for example,
    Reverse mapping:
    Source prefix: http://http.site.com/
    Source destination: http://proxy.site.com/
    To make the change, click OK.
    Once you click the OK button, the proxy server adds one or more additional mappings. To see the mappings, click the lView/Edit Mappings link. Additional mappings would be in the following format:
    from: /
    to: http://http.site.com/
    These additional automatic mappings are for users who connect to the reverse proxy as a normal server. The first mapping is to catch users connecting to the reverse proxy as a regular proxy. The �/� mapping is added only if the user doesn't change the contents of the Map Source Prefix text box provided automatically by the Administration GUI. Depending on the setup, usually the second mapping is the only one required, but the extra mapping does not cause problems in the proxy.

  • Report server Load balancing

    short description of the setup:
    2 hosts running report services say reportsvc_1, reportsvc_2 in the sanme subnet.
    reports are called using run_report_object from within oracle forms.
    Is there any mechanism that these two hosts can share the load, load balanced. I know run_report_object requires report service name in order to run.
    what other mechanism can be used to load balance report requests initiated from oracle forms.
    Thanx

    You will need a virtual server between the app server and report server. Something like this:
    App server
    ....|
    ....|
    ....^ - virtual IP server
    .|.....|
    R1..R2 - report servers
    The virtual IP server accepts the call from the app server and rotates which 'back end' report server per call. It is a crude, round-robin solution, but it works relatively well. You have to hope that every-other report isn't rough on the server.

  • Server Load Balance in one network using CSM Cat6509

    I have 2 Web Servers with real IP address 10.1.12.61 and 10.1.12.62 (subnet mask 255.255.255.0). The virtual IP address configured on CSM is 10.1.12.100
    I also have 2 Application Servers with real IP address 10.1.12.81 and 10.1.12.82 (subnet mask 255.255.255.0). The virtual IP address is 10.1.12.120.
    Users will access Web server using the virtual IP address (10.1.12.100) so that the traffic will be load balanced.
    But there is also requirement that those Web Servers access Application Servers using IP address 10.1.12.120 so that the traffic will be load balanced as well.
    Is this requirement feasible?
    Can CSM load balance between servers in one network address?

    Budiman,
    I am building the same situatiuon here. But the most simple part seems not to be working. I have two webservers in the same subnet as my VIP.
    The clients can be everywhere in every subnet.
    This is what happens:
    btpebgw70#sh mod contentSwitchingModule 9 conns
    prot vlan source destination state
    In TCP 401 192.6.53.42:1901 151.183.58.196:80 ESTAB
    Out TCP 401 151.183.58.196:80 192.6.53.42:1901 ESTAB
    ok this is good but:
    btpebgw70#sh mod contentSwitchingModule 9 reals detail
    151.183.58.201, ORBIS, state = OPERATIONAL
    conns = 0, maxconns = 4294967295, minconns = 0
    weight = 8, weight(admin) = 8, metric = 0, remainder = 0
    total conns established = 58, total conn failures = 58
    the failures have the same value as the established. Can you send me your config part of the csm because I am getting tired of this. Please email to [email protected]
    Thanks in advance!

  • 7.10 installation server, load balancing and multiple installation servers

    Hi
    In the 7.10 GUI installation server, there is no Load balancing option anamore, also there seems to be no option to easily clone the installation server from within the nwsapsetupadmin.exe program.
    If having MANY users at one location, and needing more than one installation server to accomodate the frontend installations, do you need to do this "manually" now ? grouping users and and the logon script directing different user groups to different sapgui installation servers ?
    what about creating multiple installation servers easily, is it possible to simply copy the installation server directory (c:\sapinst f.ex.) to another file server, share the directory and configure the DS and IS services (if needed) ??
    will configured packages and "on end install" scripts and such be copied too to the new installation server ?
    I need to easily create installation servers in 15 countries, this is the reason for my question...

    Hi Kim Sonny,
    hope you're doing fine
    Regarding your question:
    The "Load Balancing" was more a fail-over service and wasn't intended to use for several locations like in your case.
    So the easiest way to do this is to setup one installation server and copy the files to the other servers. On the new Installation servers you only have to setup the service again and that's it.
    Cheers,
    Martin

Maybe you are looking for