[JBoss JIRA] (JBIDE-24006) Wildfly server adapter does not report error and works inconsistently
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24006?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-24006:
-------------------------------------
Steps to replicate:
1) Start a server on port 9990. Easiest way is to run a simple java class:
{code}
public class DateServer {
public static void main(String[] args) throws IOException {
ServerSocket listener = new ServerSocket(9990);
try {
while (true) {
Socket socket = listener.accept();
try {
PrintWriter out =
new PrintWriter(socket.getOutputStream(), true);
out.println(new Date().toString());
System.out.println("Doin' a business");
} finally {
socket.close();
}
}
}
finally {
listener.close();
}
}
}
{code}
Step 2: Start WF or EAP server that requires use of port 9990. Server gets set to 'starting', and console shows output.
Step 3: Note that the server terminates itself. It failed to start up successfully, and so aborted. Older servers may not do this. They may stay up despite having no services capable of loading. But WF11 (and some earlier ones, not sure which) will terminate themselves automatically.
Step 4: Note that the error log view has no clear error listed, and no error dialog pops up.
Suggested new error string for this case: TERMINATED_PREMATURE=Server processes have terminated prematurely. Please check your server logs for more details.
This string will only be used if the server is switched from 'starting' to 'stopped' with no poller or other mechanism ever accepting the server as started.
> Wildfly server adapter does not report error and works inconsistently
> ---------------------------------------------------------------------
>
> Key: JBIDE-24006
> URL: https://issues.jboss.org/browse/JBIDE-24006
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.3.Final
> Reporter: Jeff MAURY
> Assignee: Rob Stryker
> Labels: server, server_adapter, wildfly
> Fix For: 4.4.4.AM2
>
>
> If Wildfly uses 9999 as the management port, then no error is reported but the adapter does not work.
> Here is an except we've got from the customer:
> {noformat}
> I have an important update on this. I think it's mostly good news.
> I debugged the issue via a virtual session with the person that develops the WildFly plugin for NetBeans. What we found out is that the management port I was using, 9999, conflicts with Netty. For context, I had to specify a port override since 9990 commonly conflicts with NVIDIA drivers on Windows. As soon as I used a port other than 9999 and 9990 everything worked absolutely perfectly. As soon as I switch to 9999 everything basically breaks without a real error message indicating the underlying issue. Using 9990 on the other hand clearly indicated a port conflict.
> I tried the same thing on Eclipse with exactly the same results.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24006) Wildfly server adapter does not report error and works inconsistently
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24006?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-24006:
-------------------------------------
Is anyone able to get specific steps to reproduce here? Including versions to use, and whether I need to designate an override to reproduce, or if that's the workaround? I'll play with it, but some more clear instructions would definitely help.
> Wildfly server adapter does not report error and works inconsistently
> ---------------------------------------------------------------------
>
> Key: JBIDE-24006
> URL: https://issues.jboss.org/browse/JBIDE-24006
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.3.Final
> Reporter: Jeff MAURY
> Assignee: Rob Stryker
> Labels: server, server_adapter, wildfly
> Fix For: 4.4.4.AM2
>
>
> If Wildfly uses 9999 as the management port, then no error is reported but the adapter does not work.
> Here is an except we've got from the customer:
> {noformat}
> I have an important update on this. I think it's mostly good news.
> I debugged the issue via a virtual session with the person that develops the WildFly plugin for NetBeans. What we found out is that the management port I was using, 9999, conflicts with Netty. For context, I had to specify a port override since 9990 commonly conflicts with NVIDIA drivers on Windows. As soon as I used a port other than 9999 and 9990 everything worked absolutely perfectly. As soon as I switch to 9999 everything basically breaks without a real error message indicating the underlying issue. Using 9990 on the other hand clearly indicated a port conflict.
> I tried the same thing on Eclipse with exactly the same results.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24084) To succesfully start CDKv3 Server adapter with hyperV provider, IDE must be start with admin rights
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24084?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-24084:
-------------------------------------
[~odockal] Steps to reproduce are supposed to be steps to reproduce the bug and how it fails ;)
"Workaround Description" is supposed to be how you get around it.
Right now you've provided a workaround description. Mind adding steps to reproduce? =P
> To succesfully start CDKv3 Server adapter with hyperV provider, IDE must be start with admin rights
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24084
> URL: https://issues.jboss.org/browse/JBIDE-24084
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.4.AM1
> Environment: Windows 10 Pro, x86_64
> HyperV allowed
> Reporter: Ondrej Dockal
> Priority: Critical
> Fix For: 4.4.4.AM2
>
>
> One must run devstudio with admin rights to be able to start CDKv3 server adapter with hyperV vm-provider. Also, setup-cdk command must be run in cli before server adapter is started in IDE.
> I am not sure, if those issues are bugs or more features requests/enhancements, but we should definitely do something about it, at least document it properly.
> Following steps to reproduce will lead to successfully started CDK3 server adapter in IDE.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23833) Could not load repository template extension contributed by 'org.jboss.tools.common.mylyn' with connectorKind 'jira'
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23833?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23833:
------------------------------------
>From your log:
{code}
Installing org.jboss.tools.common.mylyn.feature.feature.group 3.8.3.v20161219-1810.
{code}
You want to install 3.8.4 to test my fix, as per the PR [1] . Which site were you using for the installation? Was it from the latest 4.4.x / 4.4.neon snapshot site? Or the last stable/staging site? If snapshots, you should see the fix. If anything older (staging for AM1, stable for 4.4.3.Final / 10.3.0.GA) then that's why it's not working. :D
[1] https://github.com/jbosstools/jbosstools-base/pull/569/files#diff-96e63b7...
> Could not load repository template extension contributed by 'org.jboss.tools.common.mylyn' with connectorKind 'jira'
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23833
> URL: https://issues.jboss.org/browse/JBIDE-23833
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, common
> Affects Versions: 4.4.3.AM2, 4.4.4.AM1
> Reporter: Mat Booth
> Assignee: Nick Boldt
> Fix For: 4.4.4.AM2
>
>
> Doing a smoke test for the release of 4.4.3.AM2 when I saw this error:
> {noformat}
> !ENTRY org.eclipse.mylyn.tasks.core 4 0 2017-02-01 16:23:23.127
> !MESSAGE Unexpected error while loading repository template extensions
> !SUBENTRY 1 org.eclipse.mylyn.tasks.core 4 0 2017-02-01 16:23:23.127
> !MESSAGE Could not load repository template extension contributed by 'org.jboss.tools.common.mylyn' with connectorKind 'jira'
> {noformat}
> I saw this in the log after performing the following:
> 0. Downloaded Neon.2 (I happened to choose the C/C++ distribution)
> 1. Install Abridged category from http://download.jboss.org/jbosstools/neon/development/updates/
> 2. Open Central Software/Updates tab, enable Early Access select and install everything
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23833) Could not load repository template extension contributed by 'org.jboss.tools.common.mylyn' with connectorKind 'jira'
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23833?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-23833:
----------------------------------
Assignee: Lukáš Valach (was: Nick Boldt)
> Could not load repository template extension contributed by 'org.jboss.tools.common.mylyn' with connectorKind 'jira'
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23833
> URL: https://issues.jboss.org/browse/JBIDE-23833
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, common
> Affects Versions: 4.4.3.AM2, 4.4.4.AM1
> Reporter: Mat Booth
> Assignee: Lukáš Valach
> Fix For: 4.4.4.AM2
>
>
> Doing a smoke test for the release of 4.4.3.AM2 when I saw this error:
> {noformat}
> !ENTRY org.eclipse.mylyn.tasks.core 4 0 2017-02-01 16:23:23.127
> !MESSAGE Unexpected error while loading repository template extensions
> !SUBENTRY 1 org.eclipse.mylyn.tasks.core 4 0 2017-02-01 16:23:23.127
> !MESSAGE Could not load repository template extension contributed by 'org.jboss.tools.common.mylyn' with connectorKind 'jira'
> {noformat}
> I saw this in the log after performing the following:
> 0. Downloaded Neon.2 (I happened to choose the C/C++ distribution)
> 1. Install Abridged category from http://download.jboss.org/jbosstools/neon/development/updates/
> 2. Open Central Software/Updates tab, enable Early Access select and install everything
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23889) jbosstools-composite-install_master sends lots of nag emails when something goes awry (as it should)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23889?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23889:
------------------------------------
{quote}Could we change SLEEPTIME back to 30 minutes?{quote}
Done.
> jbosstools-composite-install_master sends lots of nag emails when something goes awry (as it should)
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23889
> URL: https://issues.jboss.org/browse/JBIDE-23889
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.3.AM2
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.4.4.AM1
>
> Attachments: composite.png
>
>
> jbosstools-composite-install_master re-runs itself on failure. However, it seems like the SLEEP_TIME parameter is now ignored, resulting on constant re-run of the job and a lot of spam (multiple mails per minutes). Additionally to spam, this adds a relatively big load on Jenkins and slaves queue.
> I've removed the re-run on failure block of the downstream job trigger as a temporary workaround.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23889) jbosstools-composite-install_master sends lots of nag emails when something goes awry (as it should)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23889?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-23889.
------------------------------
> jbosstools-composite-install_master sends lots of nag emails when something goes awry (as it should)
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23889
> URL: https://issues.jboss.org/browse/JBIDE-23889
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.3.AM2
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.4.4.AM1
>
> Attachments: composite.png
>
>
> jbosstools-composite-install_master re-runs itself on failure. However, it seems like the SLEEP_TIME parameter is now ignored, resulting on constant re-run of the job and a lot of spam (multiple mails per minutes). Additionally to spam, this adds a relatively big load on Jenkins and slaves queue.
> I've removed the re-run on failure block of the downstream job trigger as a temporary workaround.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years