0 Replies Latest reply on Jan 14, 2002 7:09 PM by 3004

    Problem bringing up WL Commerce Server

    3004

      Platform: Win 2000
      Installed the product(s) in the following order:
      1. WebLogic Server 6.1 (with SP2)
      2. Campaign Manager for WebLogic, WebLogic Commerce Server, WebLogic Personalization
      Server with Portal Framework (WLCS 3.5 with SP2).
      3. E-Business Control Center client tool

      Upon starting the WLCS, I get the following exception:

      ***************************************************************************
      The WebLogic Server did not start up properly.
      Exception raised:
      weblogic.management.configuration.ConfigurationException: value 0 for attribute
      CapacityIncrement of MBean "wlcsDomain:Name=docPool,Type=JDBCConnectionPool" is
      smaller than the minimum allowed: 1
      at weblogic.management.internal.xml.ConfigurationParser.parse(Configurat
      ionParser.java:120)
      at weblogic.management.internal.xml.XmlFileRepository.loadDomain(XmlFile
      Repository.java:261)
      at weblogic.management.internal.xml.XmlFileRepository.loadDomain(XmlFile
      Repository.java:223)
      at java.lang.reflect.Method.invoke(Native Method)
      at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
      eanImpl.java:636)
      at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
      .java:621)
      at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
      ionMBeanImpl.java:359)
      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
      55)
      at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
      23)
      at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
      at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
      at $Proxy1.loadDomain(Unknown Source)
      at weblogic.management.AdminServer.configureFromRepository(AdminServer.j
      ava:188)
      at weblogic.management.AdminServer.configure(AdminServer.java:173)
      at weblogic.management.Admin.initialize(Admin.java:239)
      at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
      at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
      at weblogic.Server.main(Server.java:35)
      Reason: Fatal initialization exception
      *************

      Please let me know what the reason for this is, and how to remedy.

      Regards
      P Kesh