microsoft / microsoft/azure-tools-for-java

[IntelliJ] Uncaught Exception com.intellij.openapi.vfs.InvalidVirtualFileAccessException: Accessing invalid virtual file: file://C:/Users/pom.xml; original:22

Open
#12,225 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
262
Forks
185
Avg merge
2d 21h
Merged PRs (30d)
1

Description

IntelliJ build version: 2026.2 IU-262.8665.258
OS: Windows 11
JDK: JetBrains s.r.o. 25.0.3
Plugin version: 3.97.6-2026.2
Additional Info: None
Parent component:

com.intellij.openapi.wm.impl.IdeRootPane[,7,7,1536x912,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> - Bosch <REDACTED: user-file-path>; original:228281; found:-; File.exists()=true
	at com.intellij.psi.impl.file.impl.FileManagerImpl.findFile(FileManagerImpl.java:480)
	at com.microsoft.azure.toolkit.intellij.java.sdk.MavenProjectReportGenerator.lambda$checkDependencyManagement$0(MavenProjectReportGenerator.java:275)
	at com.microsoft.azure.toolkit.intellij.java.sdk.MavenProjectReportGenerator.checkDependencyManagement(MavenProjectReportGenerator.java:277)
	at com.microsoft.azure.toolkit.intellij.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in MavenProjectReportGenerator.java at checkDependencyManagement (around lines 275-277), then follow the FileManagerImpl.findFile stack frame. Reproduce the reported InvalidVirtualFileAccessException in the IntelliJ plugin context and identify the conditions that invalidate the virtual file. Done means dependency-management reporting no longer produces this uncaught exception.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.