microsoft / microsoft/azure-tools-for-java
[IntelliJ] Uncaught Exception Exception thrown by subscriber method onEvent(com.microsoft.azure.toolkit.lib.common.event.AzureEvent) on subscriber com.microsoft.azure.toolkit.lib.common.event.AzureEventBus$EventListener@34f8c35e when dispatching event: com
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.1 IU-261.22158.277
OS: Mac OS X
JDK: JetBrains s.r.o. 25.0.2
Plugin version: 3.97.5-2026.1
Additional Info: None
Parent component:
com.intellij.openapi.wm.impl.IdeRootPane[,0,0,1920x958,invalid,layout=com.intellij.openapi.wm.impl.IdeRootPane$CustomHeaderRootLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=449,maximumSize=,minimumSize=,preferredSize=]
Error message:
IdeaLoggingEvent[message=Exception thrown by subscriber method onEvent(com.microsoft.azure.toolkit.lib.common.event.AzureEvent) on subscriber com.microsoft.azure.toolkit.lib.common.event.AzureEventBus$EventListener@34f8c35e when dispatching event: com.microsoft.azure.toolkit.lib.common.event.AzureEventBus$SimpleEvent@456910bd, throwable=com.microsoft.azure.toolkit.lib.common.operation.OperationException: load Resource group (WeEu-S09-Tst-Rsg-Cognitive-Service-DA-Text-Analytics)
at com.microsoft.azure.toolkit.lib.common.operation.AzureOperationAspect.afterThrowing(AzureOperationAspect.java
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 with the reported AzureEventBus subscriber exception and the AzureOperationAspect.afterThrowing stack-trace path. Reproduce loading the named resource group in the IntelliJ plugin, then trace why the event dispatch surfaces an OperationException. Done means the underlying failure is identified and the uncaught exception is handled or fixed, with a regression test if the relevant test location is found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, java
- Domain
- cloud, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100