-
Notifications
You must be signed in to change notification settings - Fork 3
Unable to launch "-Dfile.encoding=UTF-8": 2 #2
Comments
David, can you confirm that you are using the latest version of the extension? My bet is that the jvm arguments are set in wrong order and the child process tries to start the encoding parameter as it was the final executable. This is where the arguments are processed: |
Hey David - I'm using trinidad-1.2.1 and trinidad_daemon_extension-0.2.8. Also, jruby-1.6.2 (in rvm) and java-1.6.0_24. I don't have access to the machine I was working on when I filed this (until Tuesday), but my recollection is that the command generated when I ran trinidad (without the extension) started with |
I ran the following and was able to launch trinidad successfully.
Copy config/trinidad.yml from above
jruby-1.6.2 |
Looks like I won't be able to follow up until next week. I'll see what I can find then. |
I followed the steps @btatnall described two comments up and got the same result as before:
I'm thinking this is something to do with my java/jruby environment. Even though the versions are the same, there might be other things at play. Will follow up here if I find anything. |
I'm running into the same issue. My error message is: running; |
solved it by using 1.6.x 64 bit java (via java preference pane). I was previously using 1.6.x 32 bit java. |
Given the following
config/trinidad.yml
:When I run
Then I get the following message (and no other output):
If I remove the daemon extension I can run
trinidad
with no problem.I've looked through the source code for trinidad, trinidad_daemon_extension and can not figure out where this message is coming from or what is causing it.
The text was updated successfully, but these errors were encountered: