[JBoss JIRA] (JBDS-3345) Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBDS-3345?page=com.atlassian.jira.plugin.... ]
Rob Stryker commented on JBDS-3345:
-----------------------------------
> Now, I tried to install only "SwitchYard" + "RT-Gov Client-only" and it works as expected (I didn't get the error), so I assume that you used this configuration.
But when I install FSW as "SwitchYard + "RT-Gov Server+Client" then I get the error.
No... I always install with the default options, which is RT-Gov Server+Client". And I cannot replicate with the attached script, either.
So far I've been completely unable to replicate this issue, and I find it difficult to justify spending additional time working on it.
> Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8
> -----------------------------------------------------------------
>
> Key: JBDS-3345
> URL: https://issues.jboss.org/browse/JBDS-3345
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: server
> Affects Versions: 8.0.2.GA
> Environment: Fedora 21 x86_64
> JBDS 8.0.2.GA with Oracle JDK 1.8.0_25 and Oracle JDK 1.7.0_71
> Reporter: Andrej Podhradsky
> Priority: Critical
> Attachments: compiler.png, console.png, errors.txt, error_log.txt, installed_jre.png, run.sh, runtime_jre.png, server.log
>
>
> FSW 6.0.0.GA supports java 6 and 7, so if we want to run this server on JBDS 8 with jdk 8 we need to add another jdk to the JBDS, e.g. jdk 7. But this doesn't work, see errors in the attached file.
> Moreover, we are not able to stop the server from IDE, the process is still alive and we have to kill it manually.
> Note that this happens only when we install JBDS 8.0.2 with jdk 8, if we install it with jdk 7 the server works fine.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19755) Implement ServerPort portion of wst.servertools API
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19755?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19755:
-------------------------------------
Somehow, when monitoring management port using http, the connection continually gets interrupted / prematurely closed / etc. My management commands fail.
It only works when the monitoring protocol is set to TCP/IP
> tcp/ip monitor only uses http afaik
No... if you go via UI from the monitoring preference page, you'll see that there are two possible protocols listed: 1 is http, the 2nd is TCP/IP
> Implement ServerPort portion of wst.servertools API
> ---------------------------------------------------
>
> Key: JBIDE-19755
> URL: https://issues.jboss.org/browse/JBIDE-19755
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server, upstream
> Affects Versions: 4.3.0.Alpha2
> Reporter: Rob Stryker
> Fix For: 4.3.0.Beta1
>
>
> WTP has support for port monitoring in it. This is a piece of code that I've neglected to implement for, oh, 9 years. I think now's the time, since [~bbrodt] has been asking about it.
> Unfortunately, I've been hit by an upstream bug that hinders my progress:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=466109
> To be clear, I have a proposed patch which works for HTTP monitoring but simply doesn't function for monitoring the management port due to an upstream bug.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19637) Runtime download not working from New Server dialog
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19637?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19637:
-------------------------------------
[~mmalina] Test it in the next build plz ;)
> Runtime download not working from New Server dialog
> ---------------------------------------------------
>
> Key: JBIDE-19637
> URL: https://issues.jboss.org/browse/JBIDE-19637
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: help_wanted
> Fix For: 4.3.0.Beta1
>
>
> When you go through Servers view -> New Server -> EAP 6.1 -> New Runtime and then click "Download and install runtime...", it won't do anything.
> If you go through Preferences -> Server -> Runtime Environments -> Add -> EAP 6.1+ and then click the Download button, it will work.
> This issue applies to both JBDS 8.1.0.GA and JBoss Tools 4.3.0.Alpha2 testing build, but I doubt we will be able to fix this for 4.2.x.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19637) Runtime download not working from New Server dialog
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19637?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19637:
-------------------------------------
I'm going to merge it in anyway, and we'll see if it works for you in a build. The solution looks good and it seems to work for Fred ;)
> Runtime download not working from New Server dialog
> ---------------------------------------------------
>
> Key: JBIDE-19637
> URL: https://issues.jboss.org/browse/JBIDE-19637
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: help_wanted
> Fix For: 4.3.0.Beta1
>
>
> When you go through Servers view -> New Server -> EAP 6.1 -> New Runtime and then click "Download and install runtime...", it won't do anything.
> If you go through Preferences -> Server -> Runtime Environments -> Add -> EAP 6.1+ and then click the Download button, it will work.
> This issue applies to both JBDS 8.1.0.GA and JBoss Tools 4.3.0.Alpha2 testing build, but I doubt we will be able to fix this for 4.2.x.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months