Bug 1016485
| Summary: | jboss-eap-6.0.0.fsw.ci-installer - Problem with connecting to DB if atypical installation path was chosen | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Fuse Service Works 6 | Reporter: | Martin Basovník <mbasovni> | ||||||||||
| Component: | Installer | Assignee: | Miles Tjandrawidjaja <mtjandra> | ||||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Len DiMaggio <ldimaggi> | ||||||||||
| Severity: | urgent | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 6.0.0 GA | CC: | atangrin, mbasovni, mtjandra, psrna, soa-p-jira, thauser, tsykora | ||||||||||
| Target Milestone: | CR1 | Keywords: | Reopened | ||||||||||
| Target Release: | 6.0.0 | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | Type: | Bug | |||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
I cannot run the server at all from a location like the one you have used in this test. An unzip of EAP 6.1 into such a location fails to launch the server. Since this is the case, I think that we should lean towards adding validation to the path, and warning the user that a path containing certain values is likely to cause issues among the multitude of components that make up FSW. I agree. I think it is appropriate solution. The install path in post-beta builds will no longer allow the following characters: \0 ; , | : Note: Not all of them caused problems on my local machine. On unix, the only ones that caused failures were \0 ; and :. It is probably best, however, to not allow any characters like this to be used. Re-opened - still an issue in ER8. Created attachment 846294 [details]
Screenshot #3
Created attachment 846295 [details]
Screenshot #2
Created attachment 846296 [details]
Screenshot #1
Added validation to target path. http://git.app.eng.bos.redhat.com/fsw-installer.git/commit/?id=87cd87a6010998147b9962891cb714cb0f2afd64 Verified in CR1 build. |
Created attachment 809183 [details] This error is thrown while connecting to Management Interface. Description of problem: Problem with connecting to database when setting "atypical" installation path. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Select the installation path: /home/mbasovni/development/test//\0/,:|; (change your home folder) 3. Do not change any settings. 2. Do not change default database configuration jdbc:h2://home/mbasovni/development/test/\0/,:|;/jboss-eap-6.1/standalone/data/h2/soa;mvcc=true Actual results: Successfully added administrative user account. Starting Application Server. ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /home/mbasovni/development/test/ JAVA: /usr/lib/jvm/default-java//bin/java JAVA_OPTS: -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true ========================================================================= Trying to connect to Management Interface...(1/5). Trying to connect to Management Interface...(2/5). Trying to connect to Management Interface...(3/5). Trying to connect to Management Interface...(4/5). Trying to connect to Management Interface...(5/5). Failed to connect to Management Interface after 5 attempts. Running onfail Server Check. Shutting server down. Trying to connect to Management Interface...(1/5). Trying to connect to Management Interface...(2/5). Trying to connect to Management Interface...(3/5). Trying to connect to Management Interface...(4/5). Trying to connect to Management Interface...(5/5). Failed to connect to Management Interface after 5 attempts. Finally an error window is thrown (attachment). Expected results: Server will start up. Additional info: