1 Reply Latest reply on Dec 30, 2015 3:57 AM by Steffen Kreis

    _spawner deployment not starting on newly deployed AppServer

    Steffen Kreis

      Hi,

       

      since we switched to 8.6.1, we have some kind of issues with our standard deployment sequence for installing a completely new AppServer.

       

      What we usually do is (this is for a Linux installation):

      • Install BSA AppServer
      • Run blappconf to specify DB connection
      • Adjust _template deployment
        • Adjust log4j
        • Copy valid bladelogic.keystore
      • Adjust installation
        • Fix TTL in java.security
        • Copy blappsrv_login.conf and blappsrv_krb5.conf
      • Jython
        • Install and configure Jython
      • Blasadmin
        • create host specific deployments via script


      Then we start the AppServer for the first time.


      What we noticed is that when we do not run blappconf, but specify the DB settings via blasadmin, the deployments fail to start.

      So we already changed that in our sequence as up to 8.3 we never ran blappconf, but specified the DB settings manually.


      Today, i am having the issue, that the CONSOLE and JOB instances we create are working fine, but the auto-generated _spawner deployment is failing to start.

      The spawner.log shows the following entries


       

      [29 Dec 2015 16:00:49,490] [main] [INFO] [::] [] JNI Configuration complete.

      [29 Dec 2015 16:00:49,494] [main] [ERROR] [::] [] Error installing to Configured: name=bladelogic.service.management.ClientSocketFactory state=Instantiated

      java.lang.IllegalArgumentException:

              at com.sun.beans.editors.BooleanEditor.setAsText(Unknown Source)

              at org.jboss.beans.metadata.plugins.StringValueMetaData.getValue(StringValueMetaData.java:98)

       

      and goes on and on with errors like this.

       

      I suspect this is something to do with the new stateless AppServer behavior of 8.6, as the above procedure worked fine in previous versions.

       

      I also noticed something weird with blasadmin:

       

      blasadmin -s _spawner show database all

      blasadmin now running against deployment: _spawner

      [Database]

      AutoBatchEnabled:

      ConnectionString:jdbc:oracle:thin:@DBHOST.OURDOMAIN.com:1521:ORACLESID

      DatabaseInstrumentationFilePath:

      DatabaseInstrumentationRolloverCount:

      DatabaseInstrumentationRolloverSize:

      DatabaseVersion:8.6.01

      DriverClass:oracle.jdbc.driver.OracleDriver

      FetchSize:

      IdleConnectionTestPeriod:

      MaxClientConnections:

      MaxGeneralConnections:

      MaxIdleTime:

      MaxJobExecutionConnections:

      MaxWaitTime:

      MinClientConnections:

      MinGeneralConnections:

      MinJobExecutionConnections:

      MinTimeToLog:

      NumUsageHistoryPeriod:

      Password:SUPERSECRETPASSWORD

      TransactionAttempts:

      UsageHistoryPeriod:

      UserId:BLADELOGIC

       

      On all other deployments all the properties above are filled with values, but not for this one.

      Any idea how this can be fixed ?

       

      Steffen