[jbosstools-issues] [JBoss JIRA] (JBIDE-22516) NoStackTrace in AbstractModuleSlotUtil.ensureInCache

Martin Malina (JIRA) issues at jboss.org
Tue Jul 19 10:43:00 EDT 2016


     [ https://issues.jboss.org/browse/JBIDE-22516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Malina closed JBIDE-22516.
---------------------------------


I wonder what's the correct approach here. I checked the aeri page for this problem. And this was mostly reported with devstudio 10.0.0.GA or org.eclipse.epp.package.jee.product version ≤ 4.6.0.I20160606-1100 . Last occurrence was today, but that doesn't mean it was fixed yet - people just use older versions where this is not fixed (especially since the fix wasn't included in a release yet). So how do I know if this fix helps or not? I guess the only thing I can do is close this and Rob will notice if reports keep coming in?

Is there a way to tell aeri this was fixed in a particular version of the bundle, so it should reopen the problem if it keeps happening in a newer version?
And btw, [~rob.stryker], perhaps you should say something about it being fixed in the Resolution field in aeri?
{quote}
Resolution
Whether this problem has been resolved and, if so, how. If this problem is linked with a bug report, the resolution is regularly synchronized with your bug tracker.

You can add a custom resolution message, which a server response can communicate back to your users the next time they report this problem. Such a message may, e.g., describe a workaround to the problem or state in what version the problem has been fixed.
{quote}

I will add a note there.

> NoStackTrace in AbstractModuleSlotUtil.ensureInCache
> ----------------------------------------------------
>
>                 Key: JBIDE-22516
>                 URL: https://issues.jboss.org/browse/JBIDE-22516
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.4.0.Alpha1
>            Reporter: Automated Error Reporting Bot
>            Assignee: Rob Stryker
>             Fix For: 4.4.1.AM1
>
>
> The following problem was reported via the automated error reporting:
> Message: Resource '/zhgc' is not open.
> {noformat}
> com.ctrlflow.aer.NoStackTrace: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
>     at org.jboss.ide.eclipse.as.classpath.core.runtime.modules.manifest.AbstractModuleSlotUtil.ensureInCache(AbstractModuleSlotUtil.java:177)
>     at org.jboss.ide.eclipse.as.classpath.core.runtime.internal.ManifestChangeListener.ensureInCache(ManifestChangeListener.java:54)
>     at org.jboss.ide.eclipse.as.classpath.core.runtime.internal.ManifestChangeListener.resourceChanged(ManifestChangeListener.java:83)
>     at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:299)
>     at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
>     at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:289)
>     at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:152)
>     at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:374)
>     at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1469)
>     at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:46)
>     at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
> | org.eclipse.core.resources | 3.10.0.v20150423-0755 | 3.11.0.v20160503-1608 |
> | org.eclipse.core.runtime | 3.11.0.v20150405-1723 | 3.12.0.v20160506-0702 |
> | org.eclipse.jface | 3.11.0.v20150602-1400 | 3.12.0.v20160518-1929 |
> | org.eclipse.jst.jee | 1.0.700.v201404092004 | 1.0.700.v201404092004 |
> | org.eclipse.jst.jee.ui | 1.0.701.v201408251535 | 1.0.701.v201408251535 |
> | org.eclipse.ltk.core.refactoring | 3.6.200.v20140826-0859 | 3.7.0.v20160419-0705 |
> | org.eclipse.ltk.ui.refactoring | 3.7.200.v20140625-1835 | 3.8.0.v20160518-1817 |
> | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 |
> | org.eclipse.ui.navigator | 3.6.0.v20150422-0725 | 3.6.0.v20150422-0725 |
> | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.700.v201508251749 |
> | org.jboss.ide.eclipse.as.classpath.core | 3.1.0.Beta2-v20150723-0026-B29 | 3.3.1.Final-v20151021-0032-B49 |
> Operating Systems:
> | Linux | 2.6.32.3 | 4.4.6.fc23 |
> | MacOSX | 10.10.5 | 10.11.5 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/56f2c37be4b08ccb7be3584b] for the latest data.
> Thank you for your assistance.
>  Your friendly error-reports-inbox.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)



More information about the jbosstools-issues mailing list