microsoft / microsoft/azure-tools-for-java
[IntelliJ] Uncaught Exception com.intellij.openapi.vfs.InvalidVirtualFileAccessException: Accessing invalid virtual file: file:///Users/jatinupadhyaya/Documents/Workspace/cat-pre-allocation-query-api/service/pom.xml; original:148431; found:200290; File.ex
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 262
- Forks
- 185
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 1
Description
IntelliJ build version: 2025.2.1 IU-252.25557.131
OS: Mac OS X
JDK: JetBrains s.r.o. 21.0.8
Plugin version: 3.95.0-2025.2
Additional Info: None
Parent component:
com.intellij.openapi.wm.impl.IdeRootPane[,0,0,1728x1018,layout=com.intellij.openapi.wm.impl.IdeRootPane$CustomHeaderRootLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=449,maximumSize=,minimumSize=,preferredSize=]
Error message:
IdeaLoggingEvent[message=null, throwable=com.intellij.openapi.vfs.InvalidVirtualFileAccessException: Accessing invalid virtual file: <REDACTED: user-file-path>; original:148431; found:200290; File.exists()=true
at com.intellij.psi.impl.file.impl.FileManagerImpl.findFile(FileManagerImpl.java:515)
at com.microsoft.azure.toolkit.intellij.java.sdk.MavenProjectReportGenerator.lambda$checkDependencyManagement$7(MavenProjectReportGenerator.java:269)
at com.microsoft.azure.toolkit.intellij.java.sdk.MavenProjectReportGenerator.checkDependencyManagement(MavenProjectReportGenerator.java:269)
at com.microsoft.azure.toolkit.intellij.java.sdk.MavenProjectReportGenerator.analyzePom(MavenProjectReportGenerator.java:15
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at MavenProjectReportGenerator.java, especially checkDependencyManagement line 269 and analyzePom line 15, where the stack trace reports the failure. Reproduce with IntelliJ 2025.2.1, JDK 21.0.8, plugin 3.95.0-2025.2, and the reported pom.xml path. Done means the dependency-management analysis no longer raises the reported InvalidVirtualFileAccessException.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100