[JBoss JIRA] (JBIDE-21572) Terminating application running in debug mode results in exception
by Rastislav Wagner (JIRA)
Rastislav Wagner created JBIDE-21572:
----------------------------------------
Summary: Terminating application running in debug mode results in exception
Key: JBIDE-21572
URL: https://issues.jboss.org/browse/JBIDE-21572
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core, jmx
Affects Versions: 4.3.1.Beta1
Reporter: Rastislav Wagner
Assignee: Rob Stryker
Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
{code}
org.jboss.tools.common.jdt.debug.tools.ToolsCoreException:
at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredVm(Tools.java:585)
at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getMonitoredVm(Tools.java:595)
at org.jboss.tools.common.jdt.debug.tools.ToolsCore.processIsRunning(ToolsCore.java:98)
at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModelsUsingTools(RemoteDebugActivator.java:168)
at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModel(RemoteDebugActivator.java:150)
at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModel(RemoteDebugActivator.java:156)
at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:107)
at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor33.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredVm(Tools.java:583)
... 9 more
Caused by: sun.jvmstat.monitor.MonitorException: 32347 not found
at sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:84)
at sun.jvmstat.perfdata.monitor.protocol.local.LocalMonitoredVm.<init>(LocalMonitoredVm.java:68)
at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:77)
at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:67)
... 13 more
Caused by: java.lang.IllegalArgumentException: Process not found
at sun.misc.Perf.attach(Native Method)
at sun.misc.Perf.attachImpl(Perf.java:270)
at sun.misc.Perf.attach(Perf.java:200)
at sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:64)
... 16 more
{code}
{code}
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor33.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredVm(Tools.java:583)
at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getMonitoredVm(Tools.java:595)
at org.jboss.tools.common.jdt.debug.tools.ToolsCore.processIsRunning(ToolsCore.java:98)
at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModelsUsingTools(RemoteDebugActivator.java:168)
at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModel(RemoteDebugActivator.java:150)
at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModel(RemoteDebugActivator.java:156)
at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:107)
at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
Caused by: sun.jvmstat.monitor.MonitorException: 32347 not found
at sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:84)
at sun.jvmstat.perfdata.monitor.protocol.local.LocalMonitoredVm.<init>(LocalMonitoredVm.java:68)
at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:77)
at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:67)
... 13 more
Caused by: java.lang.IllegalArgumentException: Process not found
at sun.misc.Perf.attach(Native Method)
at sun.misc.Perf.attachImpl(Perf.java:270)
at sun.misc.Perf.attach(Perf.java:200)
at sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:64)
... 16 more
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21572) Terminating application running in debug mode results in exception
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21572?page=com.atlassian.jira.plugi... ]
Rastislav Wagner updated JBIDE-21572:
-------------------------------------
Fix Version/s: (was: 4.3.1.Beta2)
> Terminating application running in debug mode results in exception
> ------------------------------------------------------------------
>
> Key: JBIDE-21572
> URL: https://issues.jboss.org/browse/JBIDE-21572
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core, jmx
> Affects Versions: 4.3.1.Beta1
> Reporter: Rastislav Wagner
> Assignee: Rob Stryker
> Fix For: 4.4.0.Alpha1
>
>
> {code}
> org.jboss.tools.common.jdt.debug.tools.ToolsCoreException:
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredVm(Tools.java:585)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getMonitoredVm(Tools.java:595)
> at org.jboss.tools.common.jdt.debug.tools.ToolsCore.processIsRunning(ToolsCore.java:98)
> at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModelsUsingTools(RemoteDebugActivator.java:168)
> at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModel(RemoteDebugActivator.java:150)
> at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModel(RemoteDebugActivator.java:156)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:107)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.GeneratedMethodAccessor33.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredVm(Tools.java:583)
> ... 9 more
> Caused by: sun.jvmstat.monitor.MonitorException: 32347 not found
> at sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:84)
> at sun.jvmstat.perfdata.monitor.protocol.local.LocalMonitoredVm.<init>(LocalMonitoredVm.java:68)
> at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:77)
> at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:67)
> ... 13 more
> Caused by: java.lang.IllegalArgumentException: Process not found
> at sun.misc.Perf.attach(Native Method)
> at sun.misc.Perf.attachImpl(Perf.java:270)
> at sun.misc.Perf.attach(Perf.java:200)
> at sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:64)
> ... 16 more
> {code}
> {code}
> java.lang.reflect.InvocationTargetException
> at sun.reflect.GeneratedMethodAccessor33.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredVm(Tools.java:583)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getMonitoredVm(Tools.java:595)
> at org.jboss.tools.common.jdt.debug.tools.ToolsCore.processIsRunning(ToolsCore.java:98)
> at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModelsUsingTools(RemoteDebugActivator.java:168)
> at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModel(RemoteDebugActivator.java:150)
> at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModel(RemoteDebugActivator.java:156)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:107)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> Caused by: sun.jvmstat.monitor.MonitorException: 32347 not found
> at sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:84)
> at sun.jvmstat.perfdata.monitor.protocol.local.LocalMonitoredVm.<init>(LocalMonitoredVm.java:68)
> at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:77)
> at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:67)
> ... 13 more
> Caused by: java.lang.IllegalArgumentException: Process not found
> at sun.misc.Perf.attach(Native Method)
> at sun.misc.Perf.attachImpl(Perf.java:270)
> at sun.misc.Perf.attach(Perf.java:200)
> at sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:64)
> ... 16 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21572) Terminating application running in debug mode results in exception
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21572?page=com.atlassian.jira.plugi... ]
Rastislav Wagner resolved JBIDE-21572.
--------------------------------------
Resolution: Done
> Terminating application running in debug mode results in exception
> ------------------------------------------------------------------
>
> Key: JBIDE-21572
> URL: https://issues.jboss.org/browse/JBIDE-21572
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core, jmx
> Affects Versions: 4.3.1.Beta1
> Reporter: Rastislav Wagner
> Assignee: Rob Stryker
> Fix For: 4.4.0.Alpha1
>
>
> {code}
> org.jboss.tools.common.jdt.debug.tools.ToolsCoreException:
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredVm(Tools.java:585)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getMonitoredVm(Tools.java:595)
> at org.jboss.tools.common.jdt.debug.tools.ToolsCore.processIsRunning(ToolsCore.java:98)
> at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModelsUsingTools(RemoteDebugActivator.java:168)
> at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModel(RemoteDebugActivator.java:150)
> at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModel(RemoteDebugActivator.java:156)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:107)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.GeneratedMethodAccessor33.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredVm(Tools.java:583)
> ... 9 more
> Caused by: sun.jvmstat.monitor.MonitorException: 32347 not found
> at sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:84)
> at sun.jvmstat.perfdata.monitor.protocol.local.LocalMonitoredVm.<init>(LocalMonitoredVm.java:68)
> at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:77)
> at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:67)
> ... 13 more
> Caused by: java.lang.IllegalArgumentException: Process not found
> at sun.misc.Perf.attach(Native Method)
> at sun.misc.Perf.attachImpl(Perf.java:270)
> at sun.misc.Perf.attach(Perf.java:200)
> at sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:64)
> ... 16 more
> {code}
> {code}
> java.lang.reflect.InvocationTargetException
> at sun.reflect.GeneratedMethodAccessor33.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredVm(Tools.java:583)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getMonitoredVm(Tools.java:595)
> at org.jboss.tools.common.jdt.debug.tools.ToolsCore.processIsRunning(ToolsCore.java:98)
> at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModelsUsingTools(RemoteDebugActivator.java:168)
> at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModel(RemoteDebugActivator.java:150)
> at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModel(RemoteDebugActivator.java:156)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:107)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> Caused by: sun.jvmstat.monitor.MonitorException: 32347 not found
> at sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:84)
> at sun.jvmstat.perfdata.monitor.protocol.local.LocalMonitoredVm.<init>(LocalMonitoredVm.java:68)
> at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:77)
> at sun.jvmstat.perfdata.monitor.protocol.local.MonitoredHostProvider.getMonitoredVm(MonitoredHostProvider.java:67)
> ... 13 more
> Caused by: java.lang.IllegalArgumentException: Process not found
> at sun.misc.Perf.attach(Native Method)
> at sun.misc.Perf.attachImpl(Perf.java:270)
> at sun.misc.Perf.attach(Perf.java:200)
> at sun.jvmstat.perfdata.monitor.protocol.local.PerfDataBuffer.<init>(PerfDataBuffer.java:64)
> ... 16 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21571) require a credential composite for when there is no stored password,
by Vlado Pakan (JIRA)
Vlado Pakan created JBIDE-21571:
-----------------------------------
Summary: require a credential composite for when there is no stored password,
Key: JBIDE-21571
URL: https://issues.jboss.org/browse/JBIDE-21571
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: common/jst/core
Affects Versions: 4.3.1.Beta2
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
Following up on https://issues.jboss.org/browse/JBIDE-21162
If the credential framework can tell that a selected username has no stored password, it might be beneficial to have a composite that will have a password text field in the case that a given workflow does not wish to have a pop-up appear, but rather wishes to provide a text field instead.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21378) EL Knowledge Base Problem with enums
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21378?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-21378.
-------------------------------
Verified with 9.1.0.Beta2-v20160122-0528-B256.
> EL Knowledge Base Problem with enums
> ------------------------------------
>
> Key: JBIDE-21378
> URL: https://issues.jboss.org/browse/JBIDE-21378
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Environment: Eclipse Mars.1 (4.5.1), Primefaces 5.x
> Reporter: Andrei Ivanov
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.3.1.Beta2
>
>
> Enum properties and method are not recognized:
> In this case, {{label}} is recognized and shows up in the completion suggestions, but {{name()}} is not and marked as unrecognized.
> {code:xml}
> <p:dataTable value="#{page.dataModel}" var="managerData" lazy="true"
> rowStyleClass="#{managerData.status.label} labor-protection-#{managerData.status.name().replace('_', '-').toLowerCase()}">
> ...
> </p:dataTable>
> {code}
> {code:java}
> public enum SignOffStatus {
> VALID("Valid"),
> ALMOST_EXPIRED("Almost expired"),
> EXPIRED("Expired");
> private final String label;
> private SignOffStatus(String label) {
> this.label = label;
> }
> public String getLabel() {
> return label;
> }
> }
> {code}
> In a different page:
> {code:xml}
> <p:selectOneMenu value="#{instancePage.instanceCriteria.status}">
> <f:selectItem itemLabel="--select--" itemValue="#{null}" />
> <f:selectItems value="#{appBean.getStatuses()}" var="stat" itemLabel="#{stat.label}" />
> </p:selectOneMenu>
> {code}
> The enum has a {{getLabel()}} as the one above, but in this context it's not recognized ({{"label" cannot be resolved}}).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21377) Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21377?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21377:
---------------------------------------------
btw. everyone please remember that just because something is a central connector does not mean it cannot *also* be in the main updatesite.
> Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21377
> URL: https://issues.jboss.org/browse/JBIDE-21377
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: updatesite
> Affects Versions: 4.3.1.Beta1
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
>
> Attachments: jbtcentral-p2diff-summary.txt, jbtcentral-p2diff.txt, jbtcentral-p2diff_460.txt
>
>
> There is a decent Yaml editor existing for Eclipse IDE: https://github.com/oyse/yedit . It has 21 stars and is included in STS ( JBDS-3465 ). Similarly to JSon Editor, we should provide it to JBoss Tools users by default.
> This would require adding it to the TP and adding a dependency from a JBT feature to it.
> On longer-term, we should get it touch with the author to get this plugin migrated to Eclipse.org world, most likely under the WTP/SSE project (cc [~vrubezhny])
> --
> Story points - 8 (fibonacci):
> * update Central TP,
> * update JBT/JBDS TPs,
> * update JBT/JBDS category.xml files,
> * update JBDS feature.xml,
> * send announcement email re: TP changes
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months