[JBoss JIRA] (JBIDE-26042) shutting down ssp via cmdline shows tons of socket errors
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26042?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-26042:
-----------------------------------
Assignee: Rob Stryker
> shutting down ssp via cmdline shows tons of socket errors
> ---------------------------------------------------------
>
> Key: JBIDE-26042
> URL: https://issues.jboss.org/browse/JBIDE-26042
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: stack-server-protocol
> Affects Versions: 4.6.0.AM1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.6.0.AM2
>
>
> mvn clean install
> cd distribution/target
> unzip org.jboss.tools.ssp.distribution-0.0.9-SNAPSHOT.zip
> cd ssp-distribution
> java -jar bin/felix.jar
> Note following output:
> {code}
> API Bundle Started
> Launching Bundle Started
> Server bundle started
> The server management server is running on port 27511
> Wildfly Server bundle started
> Enter any character to stop
> ____________________________
> Welcome to Apache Felix Gogo
> {code}
> Then press enter. The server will shutdown, but will print tons of garbage about sockets trying to reconnect. This is because the attempt to connect to clients is in a loop with a while(true) (HA).
> Easy fix: let it know when it's time to shutdown and to stop attempting to receive connections.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26042) shutting down ssp via cmdline shows tons of socket errors
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26042?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-26042.
---------------------------------
Resolution: Done
pushed to master
> shutting down ssp via cmdline shows tons of socket errors
> ---------------------------------------------------------
>
> Key: JBIDE-26042
> URL: https://issues.jboss.org/browse/JBIDE-26042
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: stack-server-protocol
> Affects Versions: 4.6.0.AM1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.6.0.AM2
>
>
> mvn clean install
> cd distribution/target
> unzip org.jboss.tools.ssp.distribution-0.0.9-SNAPSHOT.zip
> cd ssp-distribution
> java -jar bin/felix.jar
> Note following output:
> {code}
> API Bundle Started
> Launching Bundle Started
> Server bundle started
> The server management server is running on port 27511
> Wildfly Server bundle started
> Enter any character to stop
> ____________________________
> Welcome to Apache Felix Gogo
> {code}
> Then press enter. The server will shutdown, but will print tons of garbage about sockets trying to reconnect. This is because the attempt to connect to clients is in a loop with a while(true) (HA).
> Easy fix: let it know when it's time to shutdown and to stop attempting to receive connections.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26042) shutting down ssp via cmdline shows tons of socket errors
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-26042:
-----------------------------------
Summary: shutting down ssp via cmdline shows tons of socket errors
Key: JBIDE-26042
URL: https://issues.jboss.org/browse/JBIDE-26042
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: stack-server-protocol
Affects Versions: 4.6.0.AM1
Reporter: Rob Stryker
mvn clean install
cd distribution/target
unzip org.jboss.tools.ssp.distribution-0.0.9-SNAPSHOT.zip
cd ssp-distribution
java -jar bin/felix.jar
Note following output:
{code}
API Bundle Started
Launching Bundle Started
Server bundle started
The server management server is running on port 27511
Wildfly Server bundle started
Enter any character to stop
____________________________
Welcome to Apache Felix Gogo
{code}
Then press enter. The server will shutdown, but will print tons of garbage about sockets trying to reconnect. This is because the attempt to connect to clients is in a loop with a while(true) (HA).
Easy fix: let it know when it's time to shutdown and to stop attempting to receive connections.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26041) Add distribution step / packaging for osgi ssp
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26041?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-26041:
-------------------------------------
https://github.com/robstryker/org.jboss.tools.ssp/commit/ea95f28f84d5571f...
Commit made. It generates a proper zip. There's a small issue with it, though, in that it still generates an unnecessary extra zip.
{code}
[rob@rawbdorable distribution] (master)$ ls -1 target/
archive-tmp
felix-framework-5.6.10
maven-archiver
org.jboss.tools.ssp.distribution-0.0.9-SNAPSHOT.jar
org.jboss.tools.ssp.distribution-0.0.9-SNAPSHOT.zip
{code}
The top 3 folders are not in question. We're left with a jar and a zip. The zip is the correct distribution. The jar contains absolutely nothing of value:
{code}
[rob@rawbdorable distribution] (master)$ unzip -l target/org.jboss.tools.ssp.distribution-0.0.9-SNAPSHOT.jar
Archive: target/org.jboss.tools.ssp.distribution-0.0.9-SNAPSHOT.jar
Length Date Time Name
--------- ---------- ----- ----
0 05-24-2018 23:20 META-INF/
128 05-24-2018 23:20 META-INF/MANIFEST.MF
0 05-24-2018 23:20 META-INF/maven/
0 05-24-2018 23:20 META-INF/maven/org.jboss.tools.ssp/
0 05-24-2018 23:20 META-INF/maven/org.jboss.tools.ssp/org.jboss.tools.ssp.distribution/
3693 05-24-2018 23:20 META-INF/maven/org.jboss.tools.ssp/org.jboss.tools.ssp.distribution/pom.xml
145 05-24-2018 23:20 META-INF/maven/org.jboss.tools.ssp/org.jboss.tools.ssp.distribution/pom.properties
--------- -------
3966 7 files
{code}
Help me [~nickboldt]
> Add distribution step / packaging for osgi ssp
> ----------------------------------------------
>
> Key: JBIDE-26041
> URL: https://issues.jboss.org/browse/JBIDE-26041
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: stack-server-protocol
> Affects Versions: 4.6.0.AM1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.6.0.AM2
>
>
> We need to generate a zip file containing apache felix, and inside felix should be the bundles necessary on the server side.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26041) Add distribution step / packaging for osgi ssp
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-26041:
-----------------------------------
Summary: Add distribution step / packaging for osgi ssp
Key: JBIDE-26041
URL: https://issues.jboss.org/browse/JBIDE-26041
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: stack-server-protocol
Affects Versions: 4.6.0.AM1
Reporter: Rob Stryker
We need to generate a zip file containing apache felix, and inside felix should be the bundles necessary on the server side.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25553) Cannot create Hibernate Console Configuration for projects with java 9
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25553?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-25553:
------------------------------------
Sorry, that was my fault -- updated the job config and caused a typo.
Here's a fresh build with the old test failure in it:
{code}
14:44:12 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:1.1.0:test (default-test) on project org.jboss.tools.hibernate.orm.test: An unexpected error occured while launching the test runtime (return code 137). See log for details. -> [Help 1]
14:44:12 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:1.1.0:test (default-test) on project org.jboss.tools.hibernate.orm.test: An unexpected error occured while launching the test runtime (return code 137). See log for details.{code} --https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/devstudio_master/job/jbosstools-hibernate-jdk9_master/367/console
> Cannot create Hibernate Console Configuration for projects with java 9
> ----------------------------------------------------------------------
>
> Key: JBIDE-25553
> URL: https://issues.jboss.org/browse/JBIDE-25553
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.5.2.AM2
> Reporter: Rastislav Wagner
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.6.0.AM2
>
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26038) [Red Hat Central] Update to latest Subclipse
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26038?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-26038 at 5/24/18 2:56 PM:
-------------------------------------------------------------
[~dstephan] Is it safe to assume this issue is not urgent for 11.x (since a workaround exists) and thus need only be fixed for 12.0.0?
was (Author: nickboldt):
[~dstephan] Is it safe to assume this issue is not urgent for 11.x and thus can be fixed for 12.0.0, rather than requiring a backport for the 11.x users?
> [Red Hat Central] Update to latest Subclipse
> --------------------------------------------
>
> Key: JBIDE-26038
> URL: https://issues.jboss.org/browse/JBIDE-26038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central-update
> Affects Versions: 4.5.3.Final
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Fix For: 4.6.0.AM3
>
>
> An error has been reported on the sme-jbds mail ling list:
> {noformat}
> Hi,
> I have a customer who is having issues with Subversion in JBDS 11.3.
> They have installed Subclipse + SVNKit from RedHat Central and then create a new project, then add the project to SVN. They then update a dummy text file in the project.
> They then try to synchronize the project and after this all of the team options are greyed out.
> The only exception in the log is:
> !ENTRY org.tigris.subversion.subclipse.core 4 -6 2018-05-10 15:41:57.217
> !MESSAGE The SVN synchronization information for 'jClaretyBatchClientProject' has become corrupt or does not exist.
> !ENTRY org.tigris.subversion.subclipse.ui 4 -6 2018-05-10 15:41:57.217
> !MESSAGE Property Exception
> !STACK 0
> java.lang.NullPointerException
> at org.tigris.subversion.subclipse.ui.properties.SVNPropertyPage.getStatus(SVNPropertyPage.java:290)
> at org.tigris.subversion.subclipse.ui.properties.SVNPropertyPage.createContents(SVNPropertyPage.java:81)
> at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:241)
> at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1426)
> at org.eclipse.jface.preference.PreferenceDialog$8.run(PreferenceDialog.java:1193)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil.lambda$0(JFaceUtil.java:44)
> ...
> If they download the latest Subclipse version plus JavaHL and use this instead of SVNKit it works.
> They wanted to have JavaHL as an option in RedHat Central but I advised this wasn't going to happen as per [1].
> They raised the issue with Subclipse with this response:
> "There are no options in the product that are predicated on using one adapter or the other. There can be bugs or slight differences in behavior in one API implementation or the other, but both provide all of the API's we use. JavaHL is already the default implementation provided that it has been installed and is available.
> So obviously you had some kind of problem here, but your diagnosis of the causes was not correct. I do generally recommend you use JavaHL if possible, since that is the API implementation that comes from Subversion itself so is going to be most compatible with the SVN command line and other clients you might be using. That said, SVNKit generally offers very good compatibility as well.
> I am closing this just because I do not see that there is anything here that can be acted upon."
> Any ideas on why SVNKit might not be working here?
> Cheers
> Dave
> [1] https://issues.jboss.org/browse/JBIDE-14795
> SF case ref: https://gss--c.na7.visual.force.com/apex/Case_View?id=500A000000aqrrSIAQ
> Portal Case Ref: https://access.redhat.com/support/cases/#/case/02094880
> {noformat}
> I tried and was able to reproduce.
> I then tried but installed from https://dl.bintray.com/subclipse/releases/subclipse/4.2.x instead of Red Hat Central and the error is gone
> So I compared both update sites (https://devstudio.redhat.com/11/stable/updates/ and https://dl.bintray.com/subclipse/releases/subclipse/4.2.x) and noticed that org.tmatesoft.svnkit is 1.8.15 in DevStudio and 1.8.12 in Subclipse
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26038) [Red Hat Central] Update to latest Subclipse
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26038?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-26038:
-------------------------------
Description:
An error has been reported on the sme-jbds mail ling list:
http://post-office.corp.redhat.com/archives/sme-jbds/2018-May/msg00004.html
{noformat}
Hi,
I have a customer who is having issues with Subversion in JBDS 11.3.
They have installed Subclipse + SVNKit from RedHat Central and then create a new project, then add the project to SVN. They then update a dummy text file in the project.
They then try to synchronize the project and after this all of the team options are greyed out.
The only exception in the log is:
!ENTRY org.tigris.subversion.subclipse.core 4 -6 2018-05-10 15:41:57.217
!MESSAGE The SVN synchronization information for 'jClaretyBatchClientProject' has become corrupt or does not exist.
!ENTRY org.tigris.subversion.subclipse.ui 4 -6 2018-05-10 15:41:57.217
!MESSAGE Property Exception
!STACK 0
java.lang.NullPointerException
at org.tigris.subversion.subclipse.ui.properties.SVNPropertyPage.getStatus(SVNPropertyPage.java:290)
at org.tigris.subversion.subclipse.ui.properties.SVNPropertyPage.createContents(SVNPropertyPage.java:81)
at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:241)
at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1426)
at org.eclipse.jface.preference.PreferenceDialog$8.run(PreferenceDialog.java:1193)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil.lambda$0(JFaceUtil.java:44)
...
If they download the latest Subclipse version plus JavaHL and use this instead of SVNKit it works.
They wanted to have JavaHL as an option in RedHat Central but I advised this wasn't going to happen as per [1].
They raised the issue with Subclipse with this response:
"There are no options in the product that are predicated on using one adapter or the other. There can be bugs or slight differences in behavior in one API implementation or the other, but both provide all of the API's we use. JavaHL is already the default implementation provided that it has been installed and is available.
So obviously you had some kind of problem here, but your diagnosis of the causes was not correct. I do generally recommend you use JavaHL if possible, since that is the API implementation that comes from Subversion itself so is going to be most compatible with the SVN command line and other clients you might be using. That said, SVNKit generally offers very good compatibility as well.
I am closing this just because I do not see that there is anything here that can be acted upon."
Any ideas on why SVNKit might not be working here?
Cheers
Dave
[1] https://issues.jboss.org/browse/JBIDE-14795
SF case ref: https://gss--c.na7.visual.force.com/apex/Case_View?id=500A000000aqrrSIAQ
Portal Case Ref: https://access.redhat.com/support/cases/#/case/02094880
{noformat}
I tried and was able to reproduce.
I then tried but installed from https://dl.bintray.com/subclipse/releases/subclipse/4.2.x instead of Red Hat Central and the error is gone
So I compared both update sites (https://devstudio.redhat.com/11/stable/updates/ and https://dl.bintray.com/subclipse/releases/subclipse/4.2.x) and noticed that org.tmatesoft.svnkit is 1.8.15 in DevStudio and 1.8.12 in Subclipse
was:
An error has been reported on the sme-jbds mail ling list:
{noformat}
Hi,
I have a customer who is having issues with Subversion in JBDS 11.3.
They have installed Subclipse + SVNKit from RedHat Central and then create a new project, then add the project to SVN. They then update a dummy text file in the project.
They then try to synchronize the project and after this all of the team options are greyed out.
The only exception in the log is:
!ENTRY org.tigris.subversion.subclipse.core 4 -6 2018-05-10 15:41:57.217
!MESSAGE The SVN synchronization information for 'jClaretyBatchClientProject' has become corrupt or does not exist.
!ENTRY org.tigris.subversion.subclipse.ui 4 -6 2018-05-10 15:41:57.217
!MESSAGE Property Exception
!STACK 0
java.lang.NullPointerException
at org.tigris.subversion.subclipse.ui.properties.SVNPropertyPage.getStatus(SVNPropertyPage.java:290)
at org.tigris.subversion.subclipse.ui.properties.SVNPropertyPage.createContents(SVNPropertyPage.java:81)
at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:241)
at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1426)
at org.eclipse.jface.preference.PreferenceDialog$8.run(PreferenceDialog.java:1193)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil.lambda$0(JFaceUtil.java:44)
...
If they download the latest Subclipse version plus JavaHL and use this instead of SVNKit it works.
They wanted to have JavaHL as an option in RedHat Central but I advised this wasn't going to happen as per [1].
They raised the issue with Subclipse with this response:
"There are no options in the product that are predicated on using one adapter or the other. There can be bugs or slight differences in behavior in one API implementation or the other, but both provide all of the API's we use. JavaHL is already the default implementation provided that it has been installed and is available.
So obviously you had some kind of problem here, but your diagnosis of the causes was not correct. I do generally recommend you use JavaHL if possible, since that is the API implementation that comes from Subversion itself so is going to be most compatible with the SVN command line and other clients you might be using. That said, SVNKit generally offers very good compatibility as well.
I am closing this just because I do not see that there is anything here that can be acted upon."
Any ideas on why SVNKit might not be working here?
Cheers
Dave
[1] https://issues.jboss.org/browse/JBIDE-14795
SF case ref: https://gss--c.na7.visual.force.com/apex/Case_View?id=500A000000aqrrSIAQ
Portal Case Ref: https://access.redhat.com/support/cases/#/case/02094880
{noformat}
I tried and was able to reproduce.
I then tried but installed from https://dl.bintray.com/subclipse/releases/subclipse/4.2.x instead of Red Hat Central and the error is gone
So I compared both update sites (https://devstudio.redhat.com/11/stable/updates/ and https://dl.bintray.com/subclipse/releases/subclipse/4.2.x) and noticed that org.tmatesoft.svnkit is 1.8.15 in DevStudio and 1.8.12 in Subclipse
> [Red Hat Central] Update to latest Subclipse
> --------------------------------------------
>
> Key: JBIDE-26038
> URL: https://issues.jboss.org/browse/JBIDE-26038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central-update
> Affects Versions: 4.5.3.Final
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Fix For: 4.6.0.AM3
>
>
> An error has been reported on the sme-jbds mail ling list:
> http://post-office.corp.redhat.com/archives/sme-jbds/2018-May/msg00004.html
> {noformat}
> Hi,
> I have a customer who is having issues with Subversion in JBDS 11.3.
> They have installed Subclipse + SVNKit from RedHat Central and then create a new project, then add the project to SVN. They then update a dummy text file in the project.
> They then try to synchronize the project and after this all of the team options are greyed out.
> The only exception in the log is:
> !ENTRY org.tigris.subversion.subclipse.core 4 -6 2018-05-10 15:41:57.217
> !MESSAGE The SVN synchronization information for 'jClaretyBatchClientProject' has become corrupt or does not exist.
> !ENTRY org.tigris.subversion.subclipse.ui 4 -6 2018-05-10 15:41:57.217
> !MESSAGE Property Exception
> !STACK 0
> java.lang.NullPointerException
> at org.tigris.subversion.subclipse.ui.properties.SVNPropertyPage.getStatus(SVNPropertyPage.java:290)
> at org.tigris.subversion.subclipse.ui.properties.SVNPropertyPage.createContents(SVNPropertyPage.java:81)
> at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:241)
> at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1426)
> at org.eclipse.jface.preference.PreferenceDialog$8.run(PreferenceDialog.java:1193)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil.lambda$0(JFaceUtil.java:44)
> ...
> If they download the latest Subclipse version plus JavaHL and use this instead of SVNKit it works.
> They wanted to have JavaHL as an option in RedHat Central but I advised this wasn't going to happen as per [1].
> They raised the issue with Subclipse with this response:
> "There are no options in the product that are predicated on using one adapter or the other. There can be bugs or slight differences in behavior in one API implementation or the other, but both provide all of the API's we use. JavaHL is already the default implementation provided that it has been installed and is available.
> So obviously you had some kind of problem here, but your diagnosis of the causes was not correct. I do generally recommend you use JavaHL if possible, since that is the API implementation that comes from Subversion itself so is going to be most compatible with the SVN command line and other clients you might be using. That said, SVNKit generally offers very good compatibility as well.
> I am closing this just because I do not see that there is anything here that can be acted upon."
> Any ideas on why SVNKit might not be working here?
> Cheers
> Dave
> [1] https://issues.jboss.org/browse/JBIDE-14795
> SF case ref: https://gss--c.na7.visual.force.com/apex/Case_View?id=500A000000aqrrSIAQ
> Portal Case Ref: https://access.redhat.com/support/cases/#/case/02094880
> {noformat}
> I tried and was able to reproduce.
> I then tried but installed from https://dl.bintray.com/subclipse/releases/subclipse/4.2.x instead of Red Hat Central and the error is gone
> So I compared both update sites (https://devstudio.redhat.com/11/stable/updates/ and https://dl.bintray.com/subclipse/releases/subclipse/4.2.x) and noticed that org.tmatesoft.svnkit is 1.8.15 in DevStudio and 1.8.12 in Subclipse
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months