[JBoss JIRA] (JBIDE-22110) Unexpected error when cancelling installation (using D&D to Central)
by Radim Hopp (JIRA)
Radim Hopp created JBIDE-22110:
----------------------------------
Summary: Unexpected error when cancelling installation (using D&D to Central)
Key: JBIDE-22110
URL: https://issues.jboss.org/browse/JBIDE-22110
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: discovery
Affects Versions: 4.3.1.CR1
Reporter: Radim Hopp
Screencast: https://youtu.be/LObzeMo8TDw
Cancelling installation in phase "Retrieving listing" causes 3 unexpected errors:
{noformat}
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86)
at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157)
at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66)
at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223)
at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor121.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84)
... 8 more
Caused by: org.eclipse.core.runtime.OperationCanceledException
at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999)
at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359)
at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101)
at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156)
... 12 more
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22057) Changes done to OpenShift application are thrown away when debugging is enabled
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22057?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22057:
---------------------------------------
[~scabanovich]
1) Nope. Changes are still not there. Conclusion: Restarting in debug mode does not fix it.
2) Changes are there. Conclusion: mode does matter.
I still think the cause is, as I wrote in description - when we restart a server adapter in debug mode, we change deployment config and therefore a new pod is spinned up where changes are not propagated (new pod mean new instance of EAP). But I could be wrong...
> Changes done to OpenShift application are thrown away when debugging is enabled
> -------------------------------------------------------------------------------
>
> Key: JBIDE-22057
> URL: https://issues.jboss.org/browse/JBIDE-22057
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.0.Alpha1
>
>
> When I have an OpenShift application and I do any changes locally which are either incrementally or fully published, enabling of debugging discard those changes and start debugging on something different.
> I think this is caused because enabling debugging inject another env. vars to OpenShift and it spin up a new pod but does not keep changes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years