cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-14418) Cassandra not starting when using enhanced startup scripts in windows
Date Sat, 12 May 2018 12:35:00 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-14418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jason Brown resolved CASSANDRA-14418.
-------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 3.11.x)
                   3.11.3
                   3.0.17
                   4.0

Thanks for confirming, [~djoshi3].

Looks like this line (and a similar one with the same quoting problem) was introduced in CASSANDRA-10939
(committed to 3.0+). I've gone ahead and fixed both those lines for 3.0 and up. Committed
as sha {{b9b2a4e1a07af518cebd4441469c940d5ac0c2ea}}. Thanks, all!

> Cassandra not starting when using enhanced startup scripts in windows
> ---------------------------------------------------------------------
>
>                 Key: CASSANDRA-14418
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14418
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Shyam Phirke
>            Assignee: Shyam Phirke
>            Priority: Major
>             Fix For: 4.0, 3.0.17, 3.11.3
>
>
> I am using Apache Cassandra 3.11.2 with my application. 
> My application is getting installed under C:/Program Files/My Application/Some Folder/.
> And cassandra C:/Program Files/My Application/Some Folder/cassandra.
> So when I am using enhanced startup scripts cassandra not getting up and running and
I am getting below error:
> "Error: Could not find or load main class Files\My"
> One of the solution I got is moving cassandra to another location where location path
does not contain spaces. But this is not good way of getting this problem resolved.
> After doing detailed analysis of all the scripts I found the solution below:
> Inside file cassandra-env.ps1 at line number 380:
> Replace line:
> $env:JVM_OPTS = "$env:JVM_OPTS -XX:CompileCommandFile=$env:CASSANDRA_CONF\hotspot_compiler"
> with line
> $env:JVM_OPTS = "$env:JVM_OPTS -XX:CompileCommandFile=""$env:CASSANDRA_CONF\hotspot_compiler"""
> Fix here is the double quotes added before $env:CASSANDRA_CONF and at the end.
> At other places this case is well handled. But missed at this place.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message