Bug 1040814 - Installer cannot use generated install script if MySQL is configured
Summary: Installer cannot use generated install script if MySQL is configured
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: Installer
Version: 6.0.0 GA
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ER8
: 6.0.0
Assignee: Francisco Canas
QA Contact: Len DiMaggio
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 07:29 UTC by Jiri Sedlacek
Modified: 2015-08-02 23:45 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug

Attachments (Terms of Use)
install script (3.46 KB, application/xml)
2013-12-12 07:29 UTC, Jiri Sedlacek 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Jiri Sedlacek 2013-12-12 07:29:11 UTC 
Created attachment 835645 [details]
install script

I've configured installer to use MySQL, generated install script with it and then tried to run installation with this script, it failed with exception:

Connected to Management Interface.
[ ERROR: Invocation Problem calling : com.redhat.installer.postinstall.DatasourceScriptHelper, java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at com.izforge.izpack.installer.ProcessPanelWorker$ExecutableClass.run(ProcessPanelWorker.java:760)
	at com.izforge.izpack.installer.ProcessPanelWorker$ProcessingJob.run(ProcessPanelWorker.java:516)
	at com.izforge.izpack.installer.ProcessPanelWorker.runJob(ProcessPanelWorker.java:462)
	at com.izforge.izpack.installer.ProcessPanelWorker.run(ProcessPanelWorker.java:388)
	at com.izforge.izpack.panels.ProcessPanelAutomationHelper.runAutomated(ProcessPanelAutomationHelper.java:67)
	at com.izforge.izpack.installer.AutomatedInstaller.installPanel(AutomatedInstaller.java:500)
	at com.izforge.izpack.installer.AutomatedInstaller.doInstall(AutomatedInstaller.java:443)
	at com.izforge.izpack.installer.Installer.main(Installer.java:141)
Caused by: com.redhat.installer.postinstall.ServerCommands$BatchIsEmptyException: ServerCommands: The batch is empty.
	at com.redhat.installer.postinstall.ServerCommands.runBatch(ServerCommands.java:1414)
	at com.redhat.installer.postinstall.DatasourceScriptHelper.run(DatasourceScriptHelper.java:69)
	... 12 more
 ]

Install script is attached.
Comment 1 Francisco Canas 2013-12-12 15:54:09 UTC 
The issue has been fixed, and db installation works with auto install scripts again. Note you'll have to run the installer manually and create a new install xml script for it to work, because the problem was that some of the DB properties weren't being saved to the script for later use.

See commit:
http://git.app.eng.bos.redhat.com/installer-commons.git/commit/?h=6.1.1.ip&id=2e88b73a446602bbefb5d29a0ba5d6f855a7be23
Comment 2 Jiri Sedlacek 2013-12-18 15:41:01 UTC 
It blocks our automated testing with other DBs, waiting for new build.
Comment 3 Len DiMaggio 2014-01-06 20:21:45 UTC 
Verified in ER8
Note You need to log in before you can comment on or make changes to this bug.