[JBoss JIRA] (JBIDE-17510) JBT 4.2.0.Beta2 on Fedora 18 x64 crashes with SIGSEGV
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-17510?page=com.atlassian.jira.plugi... ]
André Dietisheim edited comment on JBIDE-17510 at 7/2/19 5:03 PM:
------------------------------------------------------------------
[~jkopriva], [~odockal] I see upstream Eclipse being fixed, does this very old bug (5y+) with webkit in Fedora still exist?
was (Author: adietish):
[~jkopriva], [~odockal] does this very old bug (5y+) with webkit in Fedora still exist?
> JBT 4.2.0.Beta2 on Fedora 18 x64 crashes with SIGSEGV
> -----------------------------------------------------
>
> Key: JBIDE-17510
> URL: https://issues.jboss.org/browse/JBIDE-17510
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream, xulrunner
> Affects Versions: 4.2.0.Beta2
> Environment: JBT 4.2.0.Beta2 (not respin-a)
> Fedora 18 x64
> $➔ uname -a
> Linux thunk 3.11.9-100.fc18.x86_64 #1 SMP Wed Nov 20 21:22:39 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
> $➔ java -version
> java version "1.8.0"
> Java(TM) SE Runtime Environment (build 1.8.0-b132)
> Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode)
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 4.2.x
>
>
> On Fedora 18 x64 w/ JDK 1.8.0, I get fairly frequent crashes. Sample Eclipse console log showing the crash and SIGSEGV:
> https://issues.jboss.org/secure/attachment/12382836/12382836_eclipse.log....
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-21448) Port Forwarding: Allow port-forwarding of ports not defined on pod metadata
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-21448?page=com.atlassian.jira.plugi... ]
André Dietisheim commented on JBIDE-21448:
------------------------------------------
given that port forwarding is also used for the server adapter, this should be important to provide if there's a way resources-wise.
> Port Forwarding: Allow port-forwarding of ports not defined on pod metadata
> ---------------------------------------------------------------------------
>
> Key: JBIDE-21448
> URL: https://issues.jboss.org/browse/JBIDE-21448
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Jiri Pechanec
> Priority: Critical
> Labels: openshift_v3, port_forwarding_wizard
> Fix For: 4.12.x
>
>
> Some of the pods have services that are available via ports that are not defined in pod template. It is useful to have an option to port-forward such ports too.
> And example is EAP CLI
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months