Bug 1146420

Hello Juraj,

This is the default dblogging installation that was added at Van's request. Is the functionality broken in some way? 

Thanks,
Tom

DV is installing the logging datasource by default, which is used by the command and audit logging.   We want that to be the default for production environments.

Thomas,

We should be able to default the H2 username/password to sa/sa so that the dialog to set those don't need to be presented.

Hi Tom,

if you will follow steps to reproduce you will see, that datasource is installed, but its URL is "Logging database URL" and refers to driver "Name of the database driver". It means that after installation server starts with ERROR.

Yes, there is a dialog with URL and driver setup (in case you select "Perform advanced configuration"), but if you do not want to install this datasource ("Perform default configuration" shows no dialog - see "Configure runtime environment.png") it should not be present in standalone.xml.

Hi Juraj,

You're correct. I misread the reproduction procedure. The datasource is being added erroneously when the configuration option is deselected. Thanks!

Tom

Hi,

I've made the changes so that if the radio button on the "Configure Runtime Environment" panel is set to "Perform default configuration" the datasource will no longer be installed.

I've also made it so that if no Jdbc driver is installed, the default H2 Username/Password will be sa/sa and will each be displayed in a textbox.

The error still persists in ER4, but in slightly different scenario.
When using graphical or console installer, then the datasource is installed properly. 

Problem occurs when installed utilizing installation-script generated from the original installation. Then there is again  <connection-url>Logging database URL</connection-url> in datasource definition in the standalone.xml after the install and start of the server ends up with error.

Below is the datasource definition in both cases.

after automated install:
<datasource jndi-name="java:/teiid-log-ds" pool-name="teiid-log-ds" enabled="true" use-java-context="true"> 
                    <connection-url>Logging database URL</connection-url> 
                    <driver>h2</driver> 
                    <security> 
                        <user-name>sa</user-name> 
                        <password>${VAULT::teiid::dblogging.password::1}</password> 
                    </security> 
                </datasource> 

after gui install:
<datasource jndi-name="java:/teiid-log-ds" pool-name="teiid-log-ds" enabled="true" use-java-context="true">
                    <connection-url>jdbc:h2:file:${jboss.server.data.dir}/teiid-logging/teiid-logging-ds;DB_CLOSE_ON_EXIT=FALSE;DB_CLOSE_DELAY=-1</connection-url>
                    <driver>h2</driver>
                    <security>
                        <user-name>sa</user-name>
                        <password>${VAULT::teiid::dblogging.password::1}</password>
                    </security>
                </datasource>

This issue was caused by a variable not being set during automated installations. 

The issue should be resolved in the next build.