Cannot determine current directory

前端 未结 11 1346
旧时难觅i
旧时难觅i 2021-02-03 16:40

I am trying to run a .jar file that was created successfully in Netbeans and I am receiving the following error:

Error occurred during initialization of V

相关标签:
11条回答
  • 2021-02-03 17:21

    I got this error on Mac OS X and this is a genuine error since the directory has vanished. The directory I was when I am executing the commands is <PROJECT DIR>\target.

    The problem was I opened two terminals in the other terminal I ran mvn clean install and the target directory from PROJECT DIR got deleted and recreated.

    My old terminal from where I was executing Java commands is not in a valid directory.

    The file descriptor is invalid since the directory got deleted by Maven.

    When I moved back to the parent directory and the changed back to the target directory, the java command started working correctly as expected.

    0 讨论(0)
  • 2021-02-03 17:24

    I was getting the same error message, but I'm not sure if it was for the same reason as I don't use Netbeans. I use my terminal and compile with ant.

    I cd'd to a directory to run a javafile.class file. The file I want to run is part of a bigger package. The directory structure of the package looked something like this: a/b/c/javafile.class. The a, b, and c directories are all part of a larger package.

    To run my javafile.class, I cd'd into a and ran the file from there: java b/c/javafile. After I made some changes and recompiled with my ant script, the directory I was in had been deleted and remade by ant. So, when I ran javafile.class again, I got the error you're getting.

    I fixed my problem by cding out of the directories that are deleted and remade by ant and then running my javafile.class again.

    0 讨论(0)
  • 2021-02-03 17:24

    Just now, i got the same error. because i use java to setreuid/setregid to apache:apache, when i change back to root:root, i changed gid before uid, the real result is root:apache. everything going wrong, such as the error say "java.lang.Error: Properties init: Could not determine current working directory. "

    you can check it.

    0 讨论(0)
  • 2021-02-03 17:25

    Under CentOS, rhel, SL or SLC? Not an issue under debian/ubuntu.

    I found you need to logout of the shell you are using and log back in. The environment is not set up initially correctly for the current shell. After login I see that: java -version will work.

    Also ensure that /etc/alternatives/java actually points to something reasonable like:

    ls -lisa /etc/alternatives/java
    72645 0 lrwxrwxrwx. 1 root root 46 May 27 11:29 /etc/alternatives/java -> /usr/lib/jvm/jre-1.7.0-openjdk.x86_64/bin/java
    
    0 讨论(0)
  • 2021-02-03 17:27

    You may get this error if you issue "java -version" or other java command from a read-only directory. For example using openjdk 8 on centos (as non-root user):

    cd /usr/bin
    java -version
    

    Error occurred during initialization of VM java.lang.Error: Properties init: Could not determine current working directory.

    0 讨论(0)
  • 2021-02-03 17:29

    I got the same error -

    Error occurred during initialization of VM

    java.lang.Error: Properties init: Could not determine current working directory.

    by just doing 'java -version' (you would think it wouldn't need to bring up a virtual machine just to answer a simple question like 'what version are you?')

    A higher up element (that between the slashes) of the directory path of the pwd had spaces in it. When I made the current working directory one which from / downward didn't have any spaces the 'java -version' command got a proper response.

    I'm concluding they didn't account for directories with spaces when they programmed it. But that was version 1.7. I've now loaded version 8 so hopefully it has been corrected.

    0 讨论(0)
提交回复
热议问题