BSM configure database wizard exception: file creation failed

Hello,

I have reinstalled SONIC BUS on BSM platform and was about to reconfigure database wizard.

Unfortunately it throw an exception in the final step just in the step of creating a responsefile.

The error is the following:

com.mercury.infra.configserver.exception.ConfigServerException: file creation failed

Any idea to solve this problem please.

I have searched in BSM_HOME\log for the recent logs that should be written while trying the configure database wizard and on the log files jmsutils.log has the following error:

2015-12-07 14:07:47,186 [SM_NotificationManager] (CheckBus.java:80) ERROR - java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: SBA-bsmapp1; nested exception is: 
	java.net.ConnectException: Connection refused: connect]

 

I can't get the error cause

 

Regards,

Elmassimo

 

Parents
  • Hi Elmassimo,

    from what you shared it's impossible to say if this is a file creation error with the responsefile or something different.
    From the second error you quoted
    2015-12-07 14:07:47,186 [SM_NotificationManager] (CheckBus.java:80) ERROR - java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: SBA-bsmapp1; nested exception is:
     java.net.ConnectException: Connection refused: connect]

    it looks like BSM fails to invoke the bean 
     Foundations:service=BusConfigTool

    Is the host "SBA-bsmapp1" the correct BSM server name?
    Did you clear / clean all required tables after you re-installed Sonic?
    Did you set Sonic config to unconfigured?

    i can see in the code
    ..
    private boolean isJNDIConfigBeanReady() {
    ..
                Object isReady = MBeanUtils.execOperation("Foundations:service=BusConfigTool", url, "isReady", null, null);
                result = Boolean.valueOf(isReady.toString());
            } catch (InstanceNotFoundException e){
                log.debug("BusConfigTool not found while initialization", e);
            } catch (Exception e) {
               log.error(e);   <--- line 80
            }
    so we obviously have a problem invoking the mehtod, as the host cannot be reached,

    You can enable debug logging in
     <HPBSM>\conf\core\Tools\log4j\<process_name>\jmsutils.properties
    change
     log4j.category.com.mercury.infra.bus.JMSUtils=${level}, jmsutils.appender
    to
     log4j.category.com.mercury.infra.bus.JMSUtils=DEBUG, jmsutils.appender
    and save the file
    while <process_name> would be the folder you found the jmsutils.log file in, for example configserver
    ->  <HPBSM>\conf\core\Tools\log4j\configserver\jmsutils.properties 

    Then start the wizard again and see if you can find a more useful error message in the logs.What is the BSM version and the server deployment?

    Greetings
    Siggi

Reply
  • Hi Elmassimo,

    from what you shared it's impossible to say if this is a file creation error with the responsefile or something different.
    From the second error you quoted
    2015-12-07 14:07:47,186 [SM_NotificationManager] (CheckBus.java:80) ERROR - java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: SBA-bsmapp1; nested exception is:
     java.net.ConnectException: Connection refused: connect]

    it looks like BSM fails to invoke the bean 
     Foundations:service=BusConfigTool

    Is the host "SBA-bsmapp1" the correct BSM server name?
    Did you clear / clean all required tables after you re-installed Sonic?
    Did you set Sonic config to unconfigured?

    i can see in the code
    ..
    private boolean isJNDIConfigBeanReady() {
    ..
                Object isReady = MBeanUtils.execOperation("Foundations:service=BusConfigTool", url, "isReady", null, null);
                result = Boolean.valueOf(isReady.toString());
            } catch (InstanceNotFoundException e){
                log.debug("BusConfigTool not found while initialization", e);
            } catch (Exception e) {
               log.error(e);   <--- line 80
            }
    so we obviously have a problem invoking the mehtod, as the host cannot be reached,

    You can enable debug logging in
     <HPBSM>\conf\core\Tools\log4j\<process_name>\jmsutils.properties
    change
     log4j.category.com.mercury.infra.bus.JMSUtils=${level}, jmsutils.appender
    to
     log4j.category.com.mercury.infra.bus.JMSUtils=DEBUG, jmsutils.appender
    and save the file
    while <process_name> would be the folder you found the jmsutils.log file in, for example configserver
    ->  <HPBSM>\conf\core\Tools\log4j\configserver\jmsutils.properties 

    Then start the wizard again and see if you can find a more useful error message in the logs.What is the BSM version and the server deployment?

    Greetings
    Siggi

Children
  • Hello Siggi,

    Let me summarize informations:

    - BSM 9.23 on windows 2008 R2 (1GW , 1 DPS , remote SQL server database)

    - Hostname SBA-bsmapp1 is resolved in DNS and is the right server

    - Sonic re-install procedure followed

     

    stop BAC (GW first, then on the DPS)
    - under HPBAC\Sonic directory leave only bin, installation and input directories delete all others
    - execute HPBAC\Sonic\bin\install.bat
    - In HPBAC\conf\bus\jms.configuration.status.properties make sure that the entries below are set as shown
    
       domain.manager.status=nonconfigured
       message.broker.status=nonconfigured
    - next execute "Connect to Database" wizard
    - start BAC (DPS first, then GW

     

     

    The same error is appearing when executing database config wizard

    Topaz_all.log shows the following error: NullPointerException

     

    2015-12-10 01:03:44,827 [main] (DBLayerImpl.java:61) ERROR - Cant read setting from Topaz Settings db table. Context: platform
    java.lang.NullPointerException
    	at com.mercury.infra.setting.base.persistence.DBUtil.getConnection(DBUtil.java:44)
    	at com.mercury.infra.setting.base.persistence.DBLayerImpl.createConnection(DBLayerImpl.java:40)
    	at com.mercury.infra.setting.base.persistence.DBLayerImpl.getContextResultSet(DBLayerImpl.java:160)
    	at com.mercury.infra.setting.base.persistence.DBLayerImpl.getResultSet(DBLayerImpl.java:52)
    	at com.mercury.infra.setting.base.context.DBContextHolder.getContext(DBContextHolder.java:127)
    	at com.mercury.infra.setting.base.context.DBContextHolder.getOverwriteContext(DBContextHolder.java:113)
    	at com.mercury.infra.setting.base.context.DBContextHolder.getMerge(DBContextHolder.java:98)
    	at com.mercury.infra.setting.base.context.DBContextHolder.getContextAPI(DBContextHolder.java:51)
    	at com.mercury.infra.setting.base.settingApi.SettingServiceAPIImpl.getGlobalVariable(SettingServiceAPIImpl.java:169)
    	at com.mercury.infra.setting.base.settingApi.SettingServiceExternalDelegatorDecorator.getGlobalVariable(SettingServiceExternalDelegatorDecorator.java:188)
    	at com.mercury.topaz.util.ContextRootUtil.getPlatformGlobal(ContextRootUtil.java:56)
    	at com.mercury.topaz.util.ContextRootUtil.getMainContextRoot(ContextRootUtil.java:46)
    	at com.hp.opr.configuration.contextroot.UpdateContextRoot.main(UpdateContextRoot.java:20)

     

     

     !?

  • Hi elmassimo,

    thanks for the update, and sorry for my delay in getting back to you.
    Assuming that your issue is still current:

    BSM fails when it tries to read a specific entry from the SETTINGS table in the Management DB;
    from the context I assume we do something like
     select * from management_db.SETTING_PARAMETERS where SP_CONTEXT='platform'

    but all this doesn't make really sense. If the DB or table would be bad or broken, the code would have returned a SQL error.

    You can give it a shot and check in <BSM>\conf\topazinfra.ini the entries under
    [ManagementDb]

    is it the correct database? Is a SETTING_PARAMETERS table in it? Does this table contain entries?

    If all this looks good, I can only recommend to open a support vcase so that this can be analyzed in greater detail.

    Greetings
    Siggi

  • Verified Answer

    It happens that this a known issue in BSM 9.23 version. and it should be gone with version 9.25 and above.

    Anyway this problem did not block the configuration wizard as it is the last step and would only generate a temporarily file but the real configuration should be already done if arriving to this step.

    This is what I come to after opening a support case.

    Wassim

  • Verified Answer

    It happens that this a known issue in BSM 9.23 version. and it should be gone with version 9.25 and above.

    Anyway this problem did not block the configuration wizard as it is the last step and would only generate a temporarily file but the real configuration should be already done if arriving to this step.

    This is what I come to after opening a support case.

    Wassim