Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 5.2.0
-
Fix Version/s: 5.3.0
-
Component/s: Installation/Deployment
-
Security Level: Public
-
- Environment:
- Ubuntu 18.04.1 LTS (Bionic Beaver)
Attachments
Issue Links
| Depends | |||
|---|---|---|---|
|
|
|
||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Attachment | stacktrace.txt [ 10802 ] | |
| Priority | Blocker [ 1 ] | |
| Description |
I installed Petals ESB (default zip) on the "Téléchargements" directory and started it.
When put the petals-bc-mail.zip on the install, it correctly install but it refuses to start (whether with CLI or Cockpit) with this same error on Petals logs (and a big stack trace): "MalformedURIException: Opaque part contains invalid character: é" |
I installed Petals ESB (default zip) on the "Téléchargements" directory and started it.
When put the petals-bc-mail.zip on the install, it correctly install but it refuses to start (whether with CLI or Cockpit) with this same error on Petals logs (and a big stack trace): "MalformedURIException: Opaque part contains invalid character: é" I expect Petals to: - Tell me it cannot work in directory with French (or other non working languages) characters. OR - Change component state regardless the possible character used in the installation directory. |
| Status | New [ 10000 ] | Open [ 10002 ] |
| Component/s | Installation/Deployment [ 10041 ] |
| Link | This issue depends on PETALSDISTRIB-390 [ PETALSDISTRIB-390 ] |
| Summary | Cannot start component when Petals in directory with French characters | Cannot start component when Petals installed in directory with French characters |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 5.2.1 [ 10877 ] | |
| Resolution | Fixed [ 1 ] |
| Link | This issue depends on PETALSDISTRIB-390 [ PETALSDISTRIB-390 ] |
| Link | This issue blocks PETALSDISTRIB-390 [ PETALSDISTRIB-390 ] |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|

This issue seems due to a problem in 'File.toURI()' that returns invalid URI in few cases. See: http://www.garretwilson.com/blog/2008/10/25/javauriclassgotchas.xhtml