Load Balancing cockpit error

          We are testing clustering and load balancing using WLS 6SP1. We have found that
          the fail over works fine (i.e. we kill a server and the next call is invoked on
          another server). However, we find that all calls (modulo failover) always go to
          the same server. We expected to get round-robin for each home access. I've attached
          the config.xml and deployment descriptors. What am I missing here? Is there anything
          special I should be doing code wise?
          BTW: All calls are going to a stateless session bean.
          Regards,
          Andy
          [config.zip]
          

          Viresh Garg <[email protected]> wrote:
          >The attached config.zip seems to be corrupted. I can't download it.
          Wierd, I've just managed to download it. Anyway, I'll paste the
          contents into the text below.
          >
          >I am assuming that you are using a JAVA client. Could you describe your
          >test case to
          >test the load balancing between home methods of EJB ( what kind of EJB??)
          We have a stateless session bean. At each request we use JNDI to
          obtain a handle to a stateless session bean. We invoke an
          operation on it and then call remove on the stateless session
          bean. We run several of these clients (Java clients) and observe
          the system load and network traffic. We see that network traffic
          is almost minimal and system load on the "other" server is non-
          existent. We know that other server can satisfy calls to the
          stateless session bean because fail over (between calls) works
          correctly. I'm sure we are doing something daft, but I can't spot it.
          --------------------- config.xml ---------------------------
          <?xml version="1.0" encoding="UTF-8"?>
          <!--If your domain is active, please do not edit the config.xml file. Any changes
          made to that file while the domain is active will not have any effect on the domain's
          configuration and are likely to be lost. If your domain is inactive, you may edit
          this file with an XML editor. If you do so, please refer to the configuration
          documentation at http://edocs.bea.com/wls/docs60/adminguide/config_xml.html.
          In general, we recommend that changes to your configuration file be made through
          the Administration Console.-->
          <Domain Name="myDomain">
          <Security Name="petstore"
          PasswordPolicy="wl_default_password_policy" Realm="myRealm"/>
          <Application Name="wl_management_internal2" Path="C:\bea\wlserver6.0sp1\config\tmp">
          <WebAppComponent Name="wl_management_internal2"
          Targets="petstoreServer" URI="wl_management_internal2.war"/>
          </Application>
          <PasswordPolicy Name="wl_default_password_policy"/>
          <Server Cluster="PetStoreCluster" ClusterWeight="80"
          IIOPEnabled="false" JavaCompiler="C:\bea\jdk130/bin/javac"
          ListenAddress="194.152.80.29" ListenPort="7001" Machine="ROWAN"
          Name="petstoreServer" NativeIOEnabled="false"
          RootDirectory="C:\bea\wlserver6.0sp1" StdoutDebugEnabled="true"
          StdoutEnabled="true" StdoutSeverityLevel="64"
          ThreadPoolSize="15" TransactionLogFilePrefix="config/myDomain/logs/">
          <Log FileName="./config/myDomain/logs/weblogic.log" Name="petstoreServer"/>
          <ServerDebug DebugAbbreviation="false" DebugCluster="true"
          DebugClusterAnnouncements="true"
          DebugClusterFragments="true" DebugClusterHeartbeats="true"
          DebugConnection="true" DebugEJB="true" DebugEJBCache="true"
          DebugEJBCalls="false" DebugEJBDeployment="true"
          DebugEJBFreepool="true" DebugEJBLocking="true"
          DebugEJBPersistence="true" DebugEJBSecurity="true"
          DebugEventManager="true" DebugFailOver="true"
          DebugHttp="true" DebugJMSBackEnd="true" DebugJMSBoot="true"
          DebugJMSCommon="true" DebugJMSConfig="true"
          DebugJMSDurableSubscribers="true" DebugJMSFrontEnd="true"
          DebugJMSJDBCScavengeOnFlush="true" DebugJMSLocking="true"
          DebugJMSStore="true" DebugJMSXA="true" DebugJNDI="true"
          DebugJNDIFactories="true" DebugJNDIResolution="false"
          DebugLoadBalancing="true" DebugMessaging="true"
          DebugRC4="true" DebugRSA="true" DebugReplication="true"
          DebugReplicationDetails="true" DebugRouting="true"
          DebugSSL="true" DebugSecurityPasswordPolicy="true"
          DebugSecurityRealm="true" DebugTunnelingConnection="true"
          DebugTunnelingConnectionTimeout="true"
          DebugURLResolution="true" JDBCConn="true" JDBCSQL="true"
          JTA2PC="true" JTAAPI="true" JTAJDBC="true"
          JTAPropagate="true" JTARMI="true" JTARecovery="true"
          JTATLOG="true" JTAXA="true" ListenThreadDebug="true"
          LogDGCStatistics="true" MagicThreadDumpBackToSocket="false"
          MagicThreadDumpEnabled="false"
          MagicThreadDumpFile="debugMagicThreadDumpFile"
          MagicThreadDumpHost="localhost" Name="petstoreServer"/>
          <SSL CertificateCacheSize="3" Enabled="true" ListenPort="7002"
          Name="petstoreServer"
          ServerCertificateChainFileName="./config/myDomain/ca.pem"
          ServerCertificateFileName="./config/myDomain/democert.pem"
          ServerKeyFileName="./config/myDomain/demokey.pem" TrustedCAFileName="./config/myDomain/ca.pem"/>
          <WebServer DefaultWebApp="tour"
          LogFileName="./config/myDomain/logs/access.log"
          LoggingEnabled="true" Name="petstoreServer"/>
          <KernelDebug Name="petstoreServer"/>
          </Server>
          <Application Name="wl_management_internal1" Path="C:\bea\wlserver6.0sp1\config\tmp">
          <WebAppComponent Name="wl_management_internal1"
          Targets="petstoreServer" URI="wl_management_internal1.war"/>
          </Application>
          <Application Deployed="true" Name="tour" Path="C:\bea\wlserver6.0sp1\config\myDomain\applications">
          <WebAppComponent Name="tour" Targets="petstoreServer" URI="tour.war"/>
          </Application>
          <FileRealm Name="myFileRealm"/>
          <Security Name="myDomain"
          PasswordPolicy="wl_default_password_policy" Realm="wl_default_realm"/>
          <Application Deployed="true" Name="monitorApp1_1" Path="C:\bea\wlserver6.0sp1\config\myDomain\applications\monitorApp1_1.ear">
          <EJBComponent Name="monitorBeans1_1" Targets="PetStoreCluster" URI="monitorBeans1_1.jar"/>
          <WebAppComponent Name="monitorClient1_1"
          Targets="PetStoreCluster" URI="monitorClient1_1.war"/>
          </Application>
          <ApplicationManager Name="petstore"/>
          <FileRealm Name="wl_default_file_realm"/>
          <JDBCConnectionPool CapacityIncrement="1"
          DriverName="com.inet.tds.TdsDriver" InitialCapacity="1"
          JDBCXADebugLevel="0" LoginDelaySeconds="0" MaxCapacity="10"
          Name="monitorSimplePool"
          Properties="sql7=true;user=sa;port=1433;password=;url=jdbc:inetdae7:194.152.80.29;host=194.152.80.29;database=poc3a"
          RefreshMinutes="0" ShrinkPeriodMinutes="15"
          ShrinkingEnabled="true" SupportsLocalTransaction="false"
          Targets="PetStoreCluster" TestConnectionsOnRelease="false"
          TestConnectionsOnReserve="false" URL="jdbc:inetdae7:194.152.80.29"/>
          <Machine Name="ROWAN"/>
          <Log FileName="./config/myDomain/logs/wl-domain.log" Name="petstore"/>
          <Server AcceptBacklog="50" AdministrationPort="0"
          Cluster="PetStoreCluster" ClusterWeight="100"
          CompleteHTTPMessageTimeout="480"
          CompleteIIOPMessageTimeout="480" CompleteT3MessageTimeout="480"
          ConsoleInputEnabled="false" DGCIdlePeriodsUntilTimeout="2"
          DefaultIIOPPassword="guest" DefaultIIOPUser="guest"
          DefaultProtocol="t3" DefaultSecureProtocol="t3s"
          EnabledForDomainLog="true" HelpPageURL="/docs/adminhelp/"
          HttpdEnabled="true" IIOPEnabled="false"
          IdlePeriodsUntilTimeout="4" InstrumentStackTraceEnabled="false"
          JDBCLoggingEnabled="false"
          JMSDefaultConnectionFactoriesEnabled="true"
          JavaCompiler="C:\bea\jdk130/bin/javac"
          ListenAddress="194.152.80.1" ListenPort="7001"
          ListenThreadStartDelaySecs="0"
          LogRemoteExceptionsEnabled="false" LoginTimeout="1000"
          LoginTimeoutMillis="5000" Machine="MOUSE"
          MaxHTTPMessageSize="10000000" MaxIIOPMessageSize="10000000"
          MaxT3MessageSize="10000000" Name="petstoreServerClone"
          NativeIOEnabled="false" NetworkClassLoadingEnabled="false"
          PeriodLength="60000" ResponseTimeout="0"
          ReverseDNSAllowed="false" RjvmIdleTimeout="0"
          RootDirectory="C:\bea\wlserver6.0sp1"
          SocketReaderTimeoutMaxMillis="1000"
          SocketReaderTimeoutMinMillis="100" StdoutDebugEnabled="true"
          StdoutEnabled="true" StdoutSeverityLevel="64"
          ThreadPoolPercentSocketReaders="33" ThreadPoolSize="15"
          TransactionLogFilePrefix="config/myDomain/logs/"
          TunnelingClientPingSecs="45" TunnelingClientTimeoutSecs="40"
          TunnelingEnabled="false" WorkspaceShowUserKeysOnly="false"
          ZACEnabled="true" ZACPublishRoot="exports">
          <WebServer ClusteringEnabled="false" DefaultWebApp="tour"
          HttpsKeepAliveSecs="60" KeepAliveEnabled="true"
          KeepAliveSecs="30" LogFileBufferKBytes="8"
          LogFileFlushSecs="60" LogFileFormat="common"
          LogFileName="./config/myDomain/logs/access.log"
          LogRotationPeriodMins="2147483647" LogRotationType="size"
          LoggingEnabled="true" MaxLogFileSizeKBytes="0"
          MaxPostSize="-1" MaxPostTimeSecs="-1"
          Name="petstoreServerClone" PostTimeoutSecs="0" WAPEnabled="false"/>
          <SSL CertificateCacheSize="3" ClientCertificateEnforced="false"
          Enabled="true" ExportKeyLifespan="500" HandlerEnabled="true"
          KeyEncrypted="false" ListenPort="8002"
          LoginTimeoutMillis="25000" MDAcceleration="Java"
          Name="petstoreServerClone" PeerValidationEnforced="0"
          RC4Acceleration="Native/Java" RSAAcceleration="Native/Java"
          ServerCertificateChainFileName="./config/myDomain/ca.pem"
          ServerCertificateFileName="./config/myDomain/democert.pem"
          ServerKeyFileName="./config/myDomain/demokey.pem"
          TrustedCAFileName="./config/myDomain/ca.pem" UseJava="true"/>
          <Log FileCount="7" FileMinSize="500"
          FileName="./config/myDomain/logs/weblogic_clone.log"
          FileTimeSpan="24" Name="petstoreServerClone"
          NumberOfFilesLimited="false" RotationType="none"/>
          <KernelDebug Name="petstoreServerClone"/>
          <ServerDebug DebugAbbreviation="false" DebugCluster="true"
          DebugClusterAnnouncements="true"
          DebugClusterFragments="true" DebugClusterHeartbeats="true"
          DebugConnection="true" DebugEJB="true" DebugEJBCache="true"
          DebugEJBCalls="false" DebugEJBDeployment="true"
          DebugEJBFreepool="true" DebugEJBLocking="true"
          DebugEJBPersistence="true" DebugEJBSecurity="true"
          DebugEventManager="true" DebugFailOver="true"
          DebugHttp="true" DebugJMSBackEnd="true" DebugJMSBoot="true"
          DebugJMSCommon="true" DebugJMSConfig="true"
          DebugJMSDurableSubscribers="true" DebugJMSFrontEnd="true"
          DebugJMSJDBCScavengeOnFlush="true" DebugJMSLocking="true"
          DebugJMSStore="true" DebugJMSXA="true" DebugJNDI="true"
          DebugJNDIFactories="true" DebugJNDIResolution="false"
          DebugLoadBalancing="true" DebugMessaging="true"
          DebugRC4="true" DebugRSA="true" DebugReplication="true"
          DebugReplicationDetails="true" DebugRouting="true"
          DebugSSL="true" DebugSecurityPasswordPolicy="true"
          DebugSecurityRealm="true" DebugTunnelingConnection="true"
          DebugTunnelingConnectionTimeout="true"
          DebugURLResolution="true" JDBCConn="true" JDBCSQL="true"
          JTA2PC="true" JTAAPI="true" JTAJDBC="true"
          JTAPropagate="true" JTARMI="true" JTARecovery="true"
          JTATLOG="true" JTAXA="true" ListenThreadDebug="true"
          LogDGCStatistics="false" MagicThreadDumpBackToSocket="false"
          MagicThreadDumpEnabled="false"
          MagicThreadDumpFile="debugMagicThreadDumpFile"
          MagicThreadDumpHost="localhost" Name="petstoreServerClone"/>
          </Server>
          <Log FileName="myDomain.log" Name="myDomain"/>
          <JTA Name="myDomain"/>
          <Machine Name="MOUSE"/>
          <ApplicationManager Name="myDomain"/>
          <Realm FileRealm="myFileRealm" Name="myRealm"/>
          <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
          <Cluster ClusterAddress="194.152.80.1,194.152.80.29:7001"
          DefaultLoadAlgorithm="round-robin"
          MulticastAddress="224.10.10.1" Name="PetStoreCluster" ServiceAgeThresholdSeconds="180"/>
          <Application Name="console" Path="C:\bea\wlserver6.0sp1\config\examples\applications">
          <WebAppComponent Name="console" Targets="petstoreServer" URI="console.war"/>
          </Application>
          <JDBCDataSource JNDIName="monitorSimplePool"
          Name="monitorSimpleDB_1" PoolName="monitorSimplePool" Targets="PetStoreCluster"/>
          </Domain>
          ---------------------- ejb-jar.xml -------------------------
          <?xml version="1.0"?>
          <!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans
          1.1//EN' 'http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd'>
          <ejb-jar>
          <enterprise-beans>
          <entity>
          <ejb-name>ContractCMP</ejb-name>
          <home>com.liffe.monitor.contractonly.server.cmp.ContractCMPHome</home>
          <remote>com.liffe.monitor.contractonly.server.Contract</remote>
          <ejb-class>com.liffe.monitor.contractonly.server.cmp.ContractCMPBean</ejb-class>
          <persistence-type>Container</persistence-type>
          <prim-key-class>com.liffe.monitor.general.ContractPK</prim-key-class>
          <reentrant>False</reentrant>
          <cmp-field>
          <field-name>contractCode</field-name>
          </cmp-field>
          <cmp-field>
          <field-name>tradeVolume</field-name>
          </cmp-field>
          <cmp-field>
          <field-name>suspended</field-name>
          </cmp-field>
          </entity>
          <entity>
          <ejb-name>ContractBMP</ejb-name>
          <home>com.liffe.monitor.contractonly.server.bmp.ContractBMPHome</home>
          <remote>com.liffe.monitor.contractonly.server.Contract</remote>
          <ejb-class>com.liffe.monitor.contractonly.server.bmp.ContractBMPBean</ejb-class>
          <persistence-type>Bean</persistence-type>
          <prim-key-class>com.liffe.monitor.general.ContractPK</prim-key-class>
          <reentrant>False</reentrant>
          </entity>
          <session>
          <ejb-name>ContractMonitor</ejb-name>
          <home>com.liffe.monitor.contractonly.server.ContractMonitorHome</home>
          <remote>com.liffe.monitor.contractonly.server.ContractMonitor</remote>
          <ejb-class>com.liffe.monitor.contractonly.server.ContractMonitorBean</ejb-class>
          <session-type>Stateful</session-type>
          <transaction-type>Container</transaction-type>
          <ejb-ref>
          <ejb-ref-name>ejb/ContractCMPHome</ejb-ref-name>
          <ejb-ref-type>Entity</ejb-ref-type>
          <home>com.liffe.monitor.contractonly.server.cmp.ContractCMPHome</home>
          <remote>com.liffe.monitor.contractonly.server.Contract</remote>
          </ejb-ref>
          <ejb-ref>
          <ejb-ref-name>ejb/ContractBMPHome</ejb-ref-name>
          <ejb-ref-type>Entity</ejb-ref-type>
          <home>com.liffe.monitor.contractonly.server.bmp.ContractBMPHome</home>
          <remote>com.liffe.monitor.contractonly.server.Contract</remote>
          </ejb-ref>
          </session>
          <session>
          <ejb-name>InjectorTarget</ejb-name>
          <home>com.liffe.monitor.injector.server.InjectorTargetHome</home>
          <remote>com.liffe.monitor.injector.server.InjectorTarget</remote>
          <ejb-class>com.liffe.monitor.injector.server.InjectorTargetBean</ejb-class>
          <session-type>Stateless</session-type>
          <transaction-type>Container</transaction-type>
          <ejb-ref>
          <ejb-ref-name>ejb/ContractCMPHome</ejb-ref-name>
          <ejb-ref-type>Entity</ejb-ref-type>
          <home>com.liffe.monitor.contractonly.server.cmp.ContractCMPHome</home>
          <remote>com.liffe.monitor.contractonly.server.Contract</remote>
          </ejb-ref>
          <ejb-ref>
          <ejb-ref-name>ejb/ContractBMPHome</ejb-ref-name>
          <ejb-ref-type>Entity</ejb-ref-type>
          <home>com.liffe.monitor.contractonly.server.bmp.ContractBMPHome</home>
          <remote>com.liffe.monitor.contractonly.server.Contract</remote>
          </ejb-ref>
          </session>
          </enterprise-beans>
          <assembly-descriptor>
          <method-permission>
          <role-name>everyone</role-name>
          <method>
          <ejb-name>InjectorTarget</ejb-name>
          <method-name>*</method-name>
          </method>
          </method-permission>
          <container-transaction>
          <method>
          <ejb-name>ContractCMP</ejb-name>
          <method-intf>Remote</method-intf>
          <method-name>*</method-name>
          </method>
          <trans-attribute>Required</trans-attribute>
          </container-transaction>
          <container-transaction>
          <method>
          <ejb-name>ContractMonitor</ejb-name>
          <method-intf>Remote</method-intf>
          <method-name>*</method-name>
          </method>
          <trans-attribute>Required</trans-attribute>
          </container-transaction>
          <container-transaction>
          <method>
          <ejb-name>InjectorTarget</ejb-name>
          <method-name>*</method-name>
          </method>
          <trans-attribute>Required</trans-attribute>
          </container-transaction>
          </assembly-descriptor>
          </ejb-jar>
          ------------------- weblogic-ejb-jar.xml -----------------
          <?xml version="1.0"?>
          <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 5.1.0 EJB//EN'
          'http://www.bea.com/servers/wls510/dtd/weblogic-ejb-jar.dtd'>
          <weblogic-ejb-jar>
          <weblogic-enterprise-bean>
          <ejb-name>ContractCMP</ejb-name>
          <caching-descriptor>
          <max-beans-in-cache>1000</max-beans-in-cache>
          </caching-descriptor>
          <persistence-descriptor>
          <persistence-type>
          <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
          <type-version>5.1.0</type-version>
          <type-storage>META-INF/weblogic-cmp-rdbms-jar-contractonly-cmp.xml</type-storage>
          </persistence-type>
          <persistence-use>
          <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
          <type-version>5.1.0</type-version>
          </persistence-use>
          </persistence-descriptor>
          <clustering-descriptor>
          <home-is-clusterable>true</home-is-clusterable>
          <home-load-algorithm>random</home-load-algorithm>
          </clustering-descriptor>
          <transaction-descriptor>
          <trans-timeout-seconds>15</trans-timeout-seconds>
          </transaction-descriptor>
          <jndi-name>com.liffe.monitor.contractonly.server.cmp.ContractCMPHome</jndi-name>
          <transaction-isolation>
          <isolation-level>TRANSACTION_READ_COMMITTED</isolation-level>
          <method>
          <ejb-name>ContractCMP</ejb-name>
          <method-intf>Remote</method-intf>
          <method-name>*</method-name>
          </method>
          </transaction-isolation>
          </weblogic-enterprise-bean>
          <weblogic-enterprise-bean>
          <ejb-name>ContractBMP</ejb-name>
          <caching-descriptor>
          <max-beans-in-cache>1000</max-beans-in-cache>
          </caching-descriptor>
          <clustering-descriptor>
          <home-is-clusterable>true</home-is-clusterable>
          <home-load-algorithm>random</home-load-algorithm>
          </clustering-descriptor>
          <transaction-descriptor>
          <trans-timeout-seconds>15</trans-timeout-seconds>
          </transaction-descriptor>
          <jndi-name>com.liffe.monitor.contractonly.server.bmp.ContractBMPHome</jndi-name>
          <transaction-isolation>
          <isolation-level>TRANSACTION_READ_COMMITTED</isolation-level>
          <method>
          <ejb-name>ContractBMP</ejb-name>
          <method-intf>Remote</method-intf>
          <method-name>*</method-name>
          </method>
          </transaction-isolation>
          </weblogic-enterprise-bean>
          <weblogic-enterprise-bean>
          <ejb-name>ContractMonitor</ejb-name>
          <caching-descriptor>
          <max-beans-in-cache>100</max-beans-in-cache>
          </caching-descriptor>
          <clustering-descriptor>
          <home-is-clusterable>true</home-is-clusterable>
          <home-load-algorithm>round-robin</home-load-algorithm>
          </clustering-descriptor>
          <reference-descriptor>
          <ejb-reference-description>
          <ejb-ref-name>ejb/ContractCMPHome</ejb-ref-name>
          <jndi-name>com.liffe.monitor.contractonly.server.cmp.ContractCMPHome</jndi-name>
          </ejb-reference-description>
          <ejb-reference-description>
          <ejb-ref-name>ejb/ContractBMPHome</ejb-ref-name>
          <jndi-name>com.liffe.monitor.contractonly.server.bmp.ContractBMPHome</jndi-name>
          </ejb-reference-description>
          </reference-descriptor>
          <jndi-name>com.liffe.monitor.contractonly.server.ContractMonitorHome</jndi-name>
          </weblogic-enterprise-bean>
          <weblogic-enterprise-bean>
          <ejb-name>InjectorTarget</ejb-name>
          <caching-descriptor>
          <max-beans-in-free-pool>50</max-beans-in-free-pool>
          </caching-descriptor>
          <clustering-descriptor>
          <home-is-clusterable>true</home-is-clusterable>
          <home-load-algorithm>round-robin</home-load-algorithm>
          </clustering-descriptor>
          <reference-descriptor>
          <ejb-reference-description>
          <ejb-ref-name>ejb/ContractCMPHome</ejb-ref-name>
          <jndi-name>com.liffe.monitor.contractonly.server.cmp.ContractCMPHome</jndi-name>
          </ejb-reference-description>
          <ejb-reference-description>
          <ejb-ref-name>ejb/ContractBMPHome</ejb-ref-name>
          <jndi-name>com.liffe.monitor.contractonly.server.bmp.ContractBMPHome</jndi-name>
          </ejb-reference-description>
          </reference-descriptor>
          <jndi-name>ejb/InjectorTargetHome</jndi-name>
          </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
          ---------------------- weblogic-cmp-.... ---------------------
          <!DOCTYPE weblogic-rdbms-bean PUBLIC
          '-//BEA Systems, Inc.//DTD WebLogic 5.1.0 EJB RDBMS Persistence//EN'
          'http://www.bea.com/servers/wls510/dtd/weblogic-rdbms-persistence.dtd'>
          <weblogic-rdbms-bean>
          <pool-name>monitorSimplePool</pool-name>
          <table-name>Contract</table-name>
          <attribute-map>
          <object-link>
          <bean-field>contractCode</bean-field>
          <dbms-column>contractCode</dbms-column>
          </object-link>
          <object-link>
          <bean-field>tradeVolume</bean-field>
          <dbms-column>tradeVolume</dbms-column>
          </object-link>
          <object-link>
          <bean-field>suspended</bean-field>
          <dbms-column>suspended</dbms-column>
          </object-link>
          </attribute-map>
          <finder-list>
          <finder>
          <method-name>findByGTVolume</method-name>
          <method-params>
          <method-param>int</method-param>
          </method-params>
          <finder-query><![CDATA[(> tradeVolume $0)]]></finder-query>
          </finder>
          <finder>
          <method-name>findAllContracts</method-name>
          <finder-query><![CDATA[(isNotNull contractCode)]]></finder-query>
          </finder>
          </finder-list>
          <options>
          <use-quoted-names>false</use-quoted-names>
          </options>
          </weblogic-rdbms-bean>
          

Similar Messages

  • Load Balance Manager Error

    Got the error below:
    Unable to create load balance manager object!
    Please verify that the user name, password, and dom,ain name are correct.
    Error = Cannot create ActiveX component.
    Source = Microsoft.VisualBasic
    xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    Can anyone help please? Thanks!

    What version of FDM are you using?

  • Load Balancing Server Error

    Hi Expert's
              I am working on Netweaver BI integrated with EP. while creating JCo destinations for both  model and meta data, we have an option of selecting load balancing server and application server. the connection with application server is working fine but when come's to load balancing server it is asking for system group.
             Added to this we are working on single server. Pls let us know is system group is necessary? also let us know where to create system group?
    Regards
    Subbaraju

    Hi Ashok,
               As I already mentioned we are working on BI 7.0  We are facing problem while Configuring JCo destinations In JCo we have maintained Meta and Model Data using load balancing server and application server Now when using Tr.RSPLAN and selecting START MODELER it is routing into local host. But after logging, It is routing to standard SAP host (host=pwdfm101) instead of our local host .
    Note: Routing means opening the web Dynpro page.
    I hope this makes things clear.
    Regards
    Subbaraju

  • Error while selecting Load Balancing in JCO creation

    While creating JCO i am facing this error.It is working fine with Single server connection,but when i chose Load balancing i error comes out.Please tell me the solution.
    I have read couples of forum mentioned you need to start both Portal and ECC.
    For you information my Portal and Java are both on diffrrent Box.
    com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM  TYPE=B MSHOST=olameccpdvr GROUP=PUBLIC R3NAME=DVR MSSERV=sapmsDVR PCS=1 LOCATION    CPIC (TCP/IP) on local host with Unicode ERROR       service 'sapmsDVR' unknown TIME        Thu Feb 24 12:19:54 201 RELEASE     701 COMPONENT   NI (network interface) VERSION     38 RC          -3 MODULE      nixxhsl.cpp LINE        776 DETAIL      NiHsLGetServNo: service name cached as unknown COUNTER     5

    Is your backend system configured correctly in your SLD ?
    Go to transaction SMMS on your backend system that your are connecting to. Click on Goto=>Parameters=>Display. Look for "server port" value.
    This should give you the TCP/IP port for your message server. It could be 3600 or 3601 (36NN - where NN is the instance number).
    In your services file, if you made the entry at the end of the file, press Enter (Return) after your entry.
    Try restarting your server after making the above changes.
    - Shanti

  • 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.

  • Load Balancing Error

    Scenario breakdown :
    I have two app servers on hand version 6 (App1) and (App2) and a singular web server - IWS 4.1(Web1).
    Solution thus far :
    I have chosen to use App2 as the Sync Primary and App1 as the Backup. Created a new cluster "mohrelxcluster" in kregedit and created two entries at location Clusters\mohrelxcluster\SyncServers to include both servers at port 10818(kxs). I have futher setup round robin polling under CCS0\LoadDb. I set the following values under CCS0\LoadDb\ServerWeights:
    - ipaddressApp1:10818=50
    - ipaddressApp2:10818=50
    Finally, created the needed entry under CCS0\ClusterName:
    -mohrelxcluster=0
    Upon doing so, I started both servers according to order of precedence App2 first then App1.
    Log Findings :
    As anticipated, according to the kxs log files on both machines shows the broadcasting and processing of information between Sync Primary and Backup. (indicated by the sending to and receiving from <ipaddressinhex:10818>).
    In the iasdsync log file on App2(Sync Primary) - App2 has be recognized as Primary and App1 as backup.
    Problem :
    Upon starting up the ksvradmin interface, the following error is trigged : An error occured while reading in load balancing values server app1. Upon clicking on app1's icon and clicking on the cluster tab, the "mohrelxcluster" cannot be seen.
    Many thanks for reviewing. Here's hoping some one can help
    Regards
    Sathya

    HI
    Are you sharing single LDAP for these two application servers. If not, you have to create those cluster entries in two regitries (Kregedit). (both syncserver entries and clustername=0 entries)
    If you are sharing single LDAP, the entries under SyncServers can be created once but you need to create ,
    <clustername>=0 entry under CCSO\ClusterName in two registries.
    Hope this helps.
    -Srinivas

  • Error while configuring logon load balancing

    Hi,
    I am trring to configure logon load balancing in cluster environment.
    I had created the logon group using T-Code SMLG and assigned the message server to logon group.
    I am using SAP GUI 720.
    In the front end system, i had added the host file entry as well as added u201Csapma<SID>  3600/tcpu201D as my CI instance number is 00.
    I had created u201Csapmsg.iniu201D and put the entries as below based on sapnote 38119
    Message Server
    System ID 1>=<Name or IP address of message server 1>
    Ex: <SID>=x.x.x.x
         <SID>=x.x.x.x
    Message Server Description
    <System ID 1>=<Description of message server 1>
    Ex: <SID>=CI
    But while selecting u201CGroup/Server Selectionu201D I am getting error   u201CError: partner x.x.x.x:sapms<SID> not reached u201C.
    On the logon pad I had given the following information:
    Description: PRD
    System ID: <SID>
    Message Server: IP address of CI package
    I am not able to find the exact reason of the error and how to proceed to resolve the error.
    Regards
    Dusmanta

    > In the front end system, i had added the host file entry as well as added u201Csapma<SID>  3600/tcpu201D as my CI instance number is 00.
    > But while selecting u201CGroup/Server Selectionu201D I am getting error   u201CError: partner x.x.x.x:sapms<SID> not reached u201C.
    > On the logon pad I had given the following information:
    > Description: PRD
    > System ID: <SID>
    Did you enter sapma<SID> or sapms<SID> to the services file on the Windows machine?
    Markus

  • Error while load balancing two servers

    i have two Solaris servers running 9iAS R2 OC4j.
    current patch level is 9.0.2.3
    i'm trying to load balance the instances according
    to the instructions in this document:
    Oracle9i Application Server: mod_oc4j Technical Overview
    all i should need to do is run the command:
    dcmctl addOPMNLink <IP>:<PORT>
    but when i do this i get this error:
    ADMN-906026
    i could not find any info on this error with searches of:
    Google, Google Groups, Oracle MetaLink, Oracle OTN.
    ideas? suggestions? anything?
    thanks,
    .rich

    i just tried running a "dcmctl getError", and got this:
    ADMN-906026
    This Oracle9iAS instance is currently using a database repository to store configuration information. The OPMN link functionality is not supported when a database repository is being used. An Oracle9iAS cluster should be created to associate Oracle9iAS instances when using a repository.
    the two OC4J instances in question are associated with an Infrastructure instance on their respective servers. do i need to de-couple the OC4J instances? or create a "cluster of one" instance?
    .rich

  • Enable External Load Balancing error

    Hello,
    I'm trying to create a DirectAccess farm with 2 external Load balancers (Step 3.1.1 http://technet.microsoft.com/en-us/library/jj134166.aspx)
    The first server is configured (Behind a Edge with 2 NICs) and working but when trying to enable External Load Balancing, I immediately receive this error when applying the settings:
    Initializing operations before applying configuration
     Backing up GPOs...
    Updating cluster settings
     Retrieving server GPO details...
     Opening the server GPO...
     Error: The configuration data for this product is corrupt. Contact your support personnel.
    Finishing operations after applying configuration
     Information: Attempting to roll back the configuration...
    The DirectAccess dashboard shows that all services are fine, the DC is available and no errors are logged in the Event Viewer.
    I can't find any explanation about a possible corrupted configuration.

    Ok... Found the problem... You can't mix Internet IP and LAN IP to create the VIP...

  • Webdispatcher SSL load balance server mismatch errors

    We are setting up a webdispatcher to access an Enterprise Portal with multiple instances.  Currently it is working but we are having to overide host mismatches.  in webdispacther log we see
    [Thr 4856] Mon Mar 07 11:38:02 2011
    [Thr 4856] MatchTargetName("aaa.mycompany.com", "CN=bbb.mycompany.com, OU=xxx, O=ooo, L=ccc, SP=sss, C=US") FAILS
    [Thr 4856] SSL NI-sock: local=##.21.13.137:50746 peer=##.21.13.131:51001
    [Thr 4856] <<- ERROR: SapSSLSessionStart(sssl_hdl=0000000008565100)==SSSLERR_SERVER_CERT_MISMATCH
    The Portal instances are on
    aaa.mycompany.com
    bbb.mycompany.com
    Currently have a CA approved certificate for each server installed in the portal.  Dispatcher on aaa uses aaa cert, dispatcher on bbb uses bbb cert.
    Message server is on aaa, but it will load balance and place you on either instance.
    have following related parameters
    wdisp/ssl_encrypt = 2
    wdisp/ssl_auth = 2
    wdisp/ssl_cred = C:\usr\sap\XXX\W00\sec\XXX.pse
    wdisp/ssl_certhost = aaa.mycompany.com
    wdisp/ssl_ignore_host_mismatch = TRUE
    C:\usr\sap\XXX\W00\sec\XXX.pse has ssl cert of both aaa and bbb servers.
    All seems to be working, as users are load balancing.  They are not getting certificate mismatches in their browser anymore.  We are getting the SSSLERR_SERVER_CERT_MISMATCH errors, but the messages do not seem to cause an issue since we have wdisp/ssl_ignore_host_mismatch set.
    Can we eliminate those mismatch errors instead of masking the problem with wdisp/ssl_ignore_host_mismatch?
    Should each portal instance have their own ssl cert, or is there a way to use one cert such as the aaa.mycompany.com cert on each portal instance?  It seems like that might eliminate the mismatch errors.  However, what happens when you go directly to the bbb.mycompany.com portal instance? there is a certificate error if you specify aaa's and you go to bbb.  I was wondering if the wdisp/ssl_auth and wdisp/ssl_certhost are valid in the portal system so that each server uses the aaa server and certificate.  I could not tell if this parameter is valid for java-only portal systems.
    Thanks for your help.
    Edited by: Fett Patrick on Mar 7, 2011 8:35 PM

    Thank you Martin for your prompt reply.  Can you clarify please, can we use the wdisp/ssl_certhost parameter in the instance profiles of the portal instances?  I wasn't sure if that is only valid for webdispatchers or can also be used in abap/java systems?
    We orginally had the aaa server certificate listed for each dispatcher in the portal under ssl provider runtime server identity.  That caused a browser "certificate error" when accessing the bbb server.  So we then installed an ssl certificate for bbb for its dispatcher.  We could then go to either server with no browser "certificate mismatch" error.
    Then when we added the webdispatcher, we started getting the server mismatch errors at the webdispatcher level.  If the wdisp/ssl_certhost can be used in the portal profiles, then that would hopefully resolve direct access or via web dispatcher aceess mismatches.  I.E. only the aaa ssl certificate would be used and parameters would be set at both the webdispatcher and portal profiles
    Thanks, Pat.

  • Errors when scheduling scenarios for agents using load balancing

    Hi,
    I have set up my ODI environment and have successfully manged to:
    * run scenarios manually in development repository
    * schedule scenarios and run on execution repository with one agent.
    However when I try to set up a second agent to load balance the scenarios I get the following error below.
    It seems to be a load balancing problem because I can run the scenario's successfully in every other case.
    I am running an oracle RAC database. (2 servers, one oracle instance on each). I have set up one ODI agent on each server and I am trying to load balance between these 2 agents.
    In topology I have set up 1 logical agent. Physical agent 1 is linked to itself and also to Physical Agent 2 under the load balancing tab.
    For my scenario's I have 2 master scenarios (which are the ones scheduled) that call a number of other scenarios in the correct order.
    Could anyone assist me please?
    Thanks,
    Matthew
    Error:
    ====
    java.lang.NullPointerException
         at com.sunopsis.dwg.cmd.DwgCommandScenario.treatCommand(Unknown Source)
         at com.sunopsis.dwg.cmd.DwgCommandBase.execute(Unknown Source)
         at com.sunopsis.dwg.cmd.e.i(Unknown Source)
         at com.sunopsis.dwg.cmd.g.E(Unknown Source)
         at com.sunopsis.dwg.dbobj.SnpScen.a(Unknown Source)
         at com.sunopsis.dwg.dbobj.SnpScen.localExecuteSync(Unknown Source)
         at com.sunopsis.dwg.tools.StartScen.actionExecute(Unknown Source)
         at com.sunopsis.dwg.function.SnpsFunctionBaseRepositoryConnected.execute(Unknown Source)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execIntegratedFunction(Unknown Source)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(Unknown Source)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSqlS.treatTaskTrt(Unknown Source)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(Unknown Source)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(Unknown Source)
         at com.sunopsis.dwg.dbobj.SnpSession.treatSession(Unknown Source)
         at com.sunopsis.dwg.cmd.DwgCommandScenario.treatCommand(Unknown Source)
         at com.sunopsis.dwg.cmd.DwgCommandBase.execute(Unknown Source)
         at com.sunopsis.dwg.cmd.e.i(Unknown Source)
         at com.sunopsis.dwg.cmd.g.y(Unknown Source)
         at com.sunopsis.dwg.cmd.e.run(Unknown Source)
         at java.lang.Thread.run(Unknown Source)

    Hi,
    I'm wondering whether there may be a design flaw in the way our scenario's have been created / are executed.
    Currently we have x number of scenarios executed by a x master scenario.
    There are also y number of scenarios executed by a y master scenario.
    These master scenarios are the ones scheduled against the agent and they call the "sub-scenarios".
    We experience the above error when one of the "sub-scenarios" of a master scenario is executed on a different agent to where the master scenario is executed.
    Any help greatly appreciated.
    Thanks,
    Matt

  • The load balancer is not provisioned error when attempting to deploy a SP 2013 App

    Hello:
    I am in VS 2013 with SP 2013 colocated on same Win 2008 R2 server.  I opened a SP 2013 App and directly hit F5 and got this error:
    Error occurred in deployment step 'Install app for SharePoint': The load balancer is not provisioned. Verify the load balancer was provisioned successfully before retrieving endpoint addresses.  When creating the project, the first screen asks for a
    site to deploy to, and I just took the default, which was http://<servername> for the colocated server.
     I googled this and could not find a solution.  Would anyone have any direction?
    thank you
    Harvey
    Regards, Harvey

    Hi Harvey Flaisher,
    Based on the error message, this seems to be a service application not working issue.
    Please check the ULS log or Event log to check in which service application the error occurs, like BCS, secure store service, app management service, then re-provision the service application using PowerShell command, or re-create the service application
    from UI to check the result.
    Thanks,
    Qiao Wei
    TechNet Community Support

  • Load Balancing Error Message

    We have two ASA 5550's, ver. 8.0.4. We just recently set them up for Load Balancing. Every time the user logins to Cisco VPN client (5.0.03.0560), we got two email notifications for the below message. We got the error messages every time every user logins to the Cisco VPN client
    163>%ASA-3-713128: Connection attempt to VCPIP redirected to VCA peer 192.168.110.18 via load balancing
    163>%ASA-3-713902: Group = office, IP = XX.XXX.XXX.XXX, Removing peer from peer table failed, no match!
    The user was able to access the internal resources. The two ASA's have the exact configurations. Do you have any suggestions how to fix the problem?
    Thanks.
    Debra

    Error Message - %PIX|ASA-3-713128: Connection attempt to VCPIP redirected to VCA peer IP_address via load balancing
    Explanation - This message appears when a connection attempt has been made to the VCPIP and has been redirected to a less loaded peer using load balancing.
    Recommended Action - None required.
    Error Message - %PIX|ASA-3-713902 descriptive_event_string
    Explanation - This system log message could have several possible text strings describing an error. This may be the result of a configuration error either on the headend or remote access client.
    Recommended Action - It might be necessary to troubleshoot the configuration to determine the cause of the error. Check the ISAKMP and crypto map configuration on both peers.

  • Logon Load Balancing error

    Hi
    I am trying to setup Logon Load Balancing for our ERP system, I have setup the logon groups in TX SMLG, the landscape consists of DB server app1 and app2, I have created a logon group for app1 and logon group for app2, I have then created a new system entry in the SAP Logon Pad under Group/Server Selection, here I have a problem in that when I enter the message server I get a message saying Error: hostname <message server> unknown, however when I enter the ip address for the message server I get the list of logon groups appear, however, I have entered the sapmsS02 3600/tcp setting within the services file, I have also added the ipaddress and the hostname of the message server into the hosts file, but I still cannot get the hostname to work within the message server.  When I test the logon I get the error message Logon Balancing Error 88: Cannot connect to message server (rc=9), I have searched the net and most people just suggest entering the details into the services file and host file, also a sap note which suggests issues within the registry for Microsft MSN which I have checked and still have the same issue.
    Does anyone have anymore ideas as to what this could be or what to try next?
    Thanks for your help
    Jay

    Dear Jay,
    It is not the service that can not be resolved, that is translated into an IP address, but the hostname. It depends on your system and the way in which it does hostname resolution, whether the hosts file will be used at all. So please check with the keyword 'hostname resolution' on how to set this up on your landscape.
    Best Regards,
    Tim

  • DirectAccess Load Balancing Error

    Hi 
    Just seeing if anyone has come across the following error when trying to enable Network Load Balancing in DA 2012.
    Error is The length of the prefix used to assign IPv6 addresses to DirectAccess clients connecting over IP-HTTPS should be 59 bits.
    Any help would be good
    Thanks

    Hi,
    By default, DirectAccess accept a /64 prefix for the IP-HTTPS range on a single server.
    This is the IPv6 range for your clients.
    When moving to NLB, you must use a /59 range because each DirectAccess server in the Cluster will receive a /64 range based on the range you defined in the console.
    Let's say you implement a 2001::1000:/59, server1 will use 2001::1000:/64 for the clients, server2 will use 2001::1001:/64, etc...
    Gerald
    Edit: Carriage Returns problem on the forum when posting from my smartphone, will correct that later :-)

Maybe you are looking for