[GRADLE-2089] Cannot use daemon with ibm jvm Created: 08/Feb/12  Updated: 04/Jan/13  Resolved: 22/Feb/12

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-8
Fix Version/s: 1.0-milestone-8

Type: Bug
Reporter: Adam Murdoch Assignee: Unassigned
Resolution: Fixed Votes: 0


The IBM java command adds extra jvm args, so the jvm arg matching fails to match the daemon.

Comment by Szczepan Faber [ 11/Feb/12 ]

I think we shouldn't build the daemon context in the daemon server using java's getInputArguments(). Instead, we might tell the daemon on startup what is his context.

Another problem with getInputArguments() is that it does not cope with system properties that contain a space, for example: -DsomeProp="i have spaces". For such system property input arguments for java <=6 are: "-DsomeProp=i", " have", " spaces". For gradle it means that if org.gradle.jvmargs contain sys properties that have spaces we will never connect to that daemon. The inputArguments() issue is documented here: http://bugs.sun.com/bugdatabase/view_bug.do;jsessionid=f84d44729bd8affffffffeb9b87963e2d752?bug_id=6459832 I found this problem few days ago when working with windows daemon.

Generated at Wed Jun 30 12:12:30 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.