[JBoss JIRA] (JBIDE-23431) Remote server over ssh does not work with cygwin
by Martin Malina (JIRA)
Martin Malina created JBIDE-23431:
-------------------------------------
Summary: Remote server over ssh does not work with cygwin
Key: JBIDE-23431
URL: https://issues.jboss.org/browse/JBIDE-23431
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.4.2.AM2
Reporter: Martin Malina
Assignee: Rob Stryker
Today [~rawagner] reported to me that he cannot run a remote server over ssh on Windows.
So I tried it and I get the same error as him:
{code}
cd /
cd /
echo $PWD'>'
echo $PWD'>'
java "-Dprogram.name=JBossTools: WildFly 10.x" -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone/log/boot.log" "-Dlogging.configuration=file:/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone/configuration/logging.properties" "-Djboss.home.dir=/cygdrive/c/mmalina/wildfly-10.0.0.Final" -Dorg.jboss.logmanager.nocolor=true -jar /cygdrive/c/mmalina/wildfly-10.0.0.Final/jboss-modules.jar -mp "/cygdrive/c/mmalina/wildfly-10.0.0.Final/modules" org.jboss.as.standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base.dir=/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone&
echo "JBTOOLS_SERVER_START_CMD:WildFly 10.x1478166494076:"$!
Last login: Thu Nov 3 10:47:34 2016 from 10.40.4.40
0;~
jbossqa@DESKTOP-QOUU1SV ~
$ cd /
0;/
jbossqa@DESKTOP-QOUU1SV /
$
0;/
jbossqa@DESKTOP-QOUU1SV /
$ cd /
0;/
jbossqa@DESKTOP-QOUU1SV /
$
0;/
jbossqa@DESKTOP-QOUU1SV /
$ echo $PWD'>'
/>
0;/
jbossqa@DESKTOP-QOUU1SV /
$ echo $PWD'>'
/>
0;/
jbossqa@DESKTOP-QOUU1SV /
$ java "-Dprogram.name=JBossTools: WildFly 10.x" -Xms64m -Xmx512m -Dorg.jboss.re solver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInter val=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs= org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=/cygdrive/ c/mmalina/wildfly-10.0.0.Final/standalone/log/boot.log" "-Dlogging.configuration =file:/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone/configuration/logging. properties" "-Djboss.home.dir=/cygdrive/c/mmalina/wildfly-10.0.0.Final" -Dorg.jb oss.logmanager.nocolor=true -jar /cygdrive/c/mmalina/wildfly-10.0.0.Final/jboss -modules.jar -mp "/cygdrive/c/mmalina/wildfly-10.0.0.Final/modules" org.jboss.as .standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base.dir=/c ygdrive/c/mmalina/wildfly-10.0.0.Final/standalone&
[1] 7888
0;/
jbossqa@DESKTOP-QOUU1SV /
$ echo "JBTOOLS_SERVER_START_CMD:WildFly 10.x1478166494076:"$!
JBTOOLS_SERVER_START_CMD:WildFly 10.x1478166494076:7888
0;/
jbossqa@DESKTOP-QOUU1SV /
$ Error: Unable to access jarfile /cygdrive/c/mmalina/wildfly-10.0.0.Final/jboss-modules.jar
wait 7888; echo "JBTOOLS_SERVER_LAUNCH_TERMINATED_CMD:WildFly 10.x147816649407 6:" $?
[1]+ Exit 1 java "-Dprogram.name=JBossTools: WildFly 10.x" -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone/log/boot.log" "-Dlogging.configuration=file:/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone/configuration/logging.properties" "-Djboss.home.dir=/cygdrive/c/mmalina/wildfly-10.0.0.Final" -Dorg.jboss.logmanager.nocolor=true -jar /cygdrive/c/mmalina/wildfly-10.0.0.Final/jboss-modules.jar -mp "/cygdrive/c/mmalina/wildfly-10.0.0.Final/modules" org.jboss.as.standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base.dir=/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone
JBTOOLS_SERVER_LAUNCH_TERMINATED_CMD:WildFly 10.x1478166494076: 1
{code}
I'm not sure what's going on, /cygdrive/c/mmalina/wildfly-10.0.0.Final/jboss-modules.jar is accessible for me just fine over ssh. One may think that perhaps the java process has to use windows paths. But when I try to run ./standalone.sh in cygwin there, it works just fine. So I guess there is no reason why it shouldn't work over ssh then. We just need to figure out what's wrong.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4129) Bundled JDK is trying to install from non existing location
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4129?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-4129.
-----------------------------
Verified in B208.
> Bundled JDK is trying to install from non existing location
> -----------------------------------------------------------
>
> Key: JBDS-4129
> URL: https://issues.jboss.org/browse/JBDS-4129
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.2.0.AM3
> Environment: Windows 10
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 10.2.0.AM3
>
>
> OpenJDK fails to install from bundled installer, it is trying to execute the msi from the location it would normally be downloaded into by the online installer. But it is just not there, since it's bundled instead.
> {noformat}
> Thu, 20 Oct 2016 18:53:13 GMT-INFO: jdk - Execute msiexec /i,C:\Users\jbossqa\AppData\Local\Temp\jdk.msi,INSTALLDIR=c:\DevelopmentSuite\jdk8,/qn,/norestart,/Lviwe,c:\DevelopmentSuite\openjdk.log
> Thu, 20 Oct 2016 18:53:13 GMT-ERROR: jdk - Error: Command failed: msiexec /i C:\Users\jbossqa\AppData\Local\Temp\jdk.msi INSTALLDIR=c:\DevelopmentSuite\jdk8 /qn /norestart /Lviwe c:\DevelopmentSuite\openjdk.log
> Thu, 20 Oct 2016 18:53:13 GMT-ERROR: jdk -
> Thu, 20 Oct 2016 18:53:13 GMT-ERROR: jdk failed to install: Error: Command failed: msiexec /i C:\Users\jbossqa\AppData\Local\Temp\jdk.msi INSTALLDIR=c:\DevelopmentSuite\jdk8 /qn /norestart /Lviwe c:\DevelopmentSuite\openjdk.log
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23368) Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23368?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23368:
------------------------------------------
Resolving this as invalid issue, since ports should not be added to the replication controller.
> Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23368
> URL: https://issues.jboss.org/browse/JBIDE-23368
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.2.AM3
>
>
> When deploying a docker image via Deploy Docker Wizard to an OpenShift instance, there is a wizard page with mapping of pod ports to service ports. If I add a new port mapping there, it is propagated to a created Service. But created replication controller does not contain those new mappings (results into creating pods without those ports available)
> Either way this should be fixed, to also Replication Controller should contain mapped ports, because having a service which has mapped pod ports to service ports but pods itself does not have this port exposes is useless. Or having Add... button does not make sense there, or there is no known use case where it would be useful (existing mapping could be edited but a new one would be useless).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23368) Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23368?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-23368.
--------------------------------------
Resolution: Rejected
> Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23368
> URL: https://issues.jboss.org/browse/JBIDE-23368
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.2.AM3
>
>
> When deploying a docker image via Deploy Docker Wizard to an OpenShift instance, there is a wizard page with mapping of pod ports to service ports. If I add a new port mapping there, it is propagated to a created Service. But created replication controller does not contain those new mappings (results into creating pods without those ports available)
> Either way this should be fixed, to also Replication Controller should contain mapped ports, because having a service which has mapped pod ports to service ports but pods itself does not have this port exposes is useless. Or having Add... button does not make sense there, or there is no known use case where it would be useful (existing mapping could be edited but a new one would be useless).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23368) Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23368?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-23368:
----------------------------------------
Assignee: Andre Dietisheim
> Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23368
> URL: https://issues.jboss.org/browse/JBIDE-23368
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.2.AM3
>
>
> When deploying a docker image via Deploy Docker Wizard to an OpenShift instance, there is a wizard page with mapping of pod ports to service ports. If I add a new port mapping there, it is propagated to a created Service. But created replication controller does not contain those new mappings (results into creating pods without those ports available)
> Either way this should be fixed, to also Replication Controller should contain mapped ports, because having a service which has mapped pod ports to service ports but pods itself does not have this port exposes is useless. Or having Add... button does not make sense there, or there is no known use case where it would be useful (existing mapping could be edited but a new one would be useless).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23208) SSLCertificatesPreference.isValid(String): Could not parse
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23208?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-23208 at 11/3/16 5:49 AM:
-------------------------------------------------------------------
[~mmalina] in the above comment, where you cannot replicate, you operate on the very same workspace which has the czech certificates in preferences? And you operate without the patch applied?
I think that we should apply the current incomplete patch, if you can confirm it works fine. It fixates locales when parsing certificate dates and makes us always use english.
Can you please confirm this?
was (Author: adietish):
[~mmalina] in the above comment, where you cannot replicate, you operate on the very same workspace which has the czech certificates in preferences?
> SSLCertificatesPreference.isValid(String): Could not parse
> ----------------------------------------------------------
>
> Key: JBIDE-23208
> URL: https://issues.jboss.org/browse/JBIDE-23208
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.4.2.AM1
> Reporter: Martin Malina
> Fix For: 4.4.x
>
>
> When I start CDK and OpenShift connection is established, I get this in the Error Log view:
> org.jboss.tools.openshift.ui
> SSLCertificatesPreference.isValid(String): Could not parse 'Čt, 20 Zář 2018 12:54:07' in format E, d MMM yyyy HH:mm:ss
> An exception stack trace is not available.
> As you can see, the date is localized. I think this started happening after I updated to macOS Sierra last night - I never noticed it before. If we can figure out where the parsing is happening, perhaps we can come up with a switch for using english date here.
> Env:
> devstudio-10.2.0.AM1-v20160920-0457-B6061-installer-standalone.jar
> cdk 2.2.rc5
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4133) org.jboss.tools.ws.jaxrs.core :: error occurred during JAX-RS Metamodel build - java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBDS-4133?page=com.atlassian.jira.plugin.... ]
Xavier Coulon commented on JBDS-4133:
-------------------------------------
ok, so the PR that Jeff proposed fails, but I'd like to ask first: why do we have Lucene 5.4.1 rpms at first ? Can't we use the 5.2 version that is also available in Eclipse Orbit ? Then I would be able to upgrade the Webservices plugins to depend on that version of Lucene.
For the record, Lucene is used to index JAX-RS elements in memory, so there is no impact if the lucene index format changed, since data is only available during the workbench session. Lucene indexes are re-built during the a full/clean build of a project.
> org.jboss.tools.ws.jaxrs.core :: error occurred during JAX-RS Metamodel build - java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4133
> URL: https://issues.jboss.org/browse/JBDS-4133
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm, webservices
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 10.2.0.AM3
>
> Attachments: lucene3.5corevs.5.4.1analyzers-common.png, lucene3.5corevs.5.4.1queryparser.png
>
>
> I'm getting this problem after running the HTML5 quickstart. I've installed this [1] version of the rpm.
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2016-10-26 16:22:07.578
> !MESSAGE An internal error occurred during: "JAX-RS Metamodel build...".
> !STACK 0
> java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.<init>(JaxrsMetamodel.java:163)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.create(JaxrsMetamodel.java:278)
> at org.jboss.tools.ws.jaxrs.core.metamodel.domain.JaxrsMetamodelLocator.get(JaxrsMetamodelLocator.java:120)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedBuildJob.run(ResourceChangedBuildJob.java:68)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: org.apache.lucene.analysis.standard.StandardAnalyzer cannot be found by org.jboss.tools.ws.jaxrs.core_1.9.2.v20161011-1002
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 5 more
> {code}
> [1] https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_master/20...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23208) SSLCertificatesPreference.isValid(String): Could not parse
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23208?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23208:
------------------------------------------
[~mmalina] in the above comment, where you cannot replicate, you operate on the very same workspace which has the czech certificates in preferences?
> SSLCertificatesPreference.isValid(String): Could not parse
> ----------------------------------------------------------
>
> Key: JBIDE-23208
> URL: https://issues.jboss.org/browse/JBIDE-23208
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.4.2.AM1
> Reporter: Martin Malina
> Fix For: 4.4.x
>
>
> When I start CDK and OpenShift connection is established, I get this in the Error Log view:
> org.jboss.tools.openshift.ui
> SSLCertificatesPreference.isValid(String): Could not parse 'Čt, 20 Zář 2018 12:54:07' in format E, d MMM yyyy HH:mm:ss
> An exception stack trace is not available.
> As you can see, the date is localized. I think this started happening after I updated to macOS Sierra last night - I never noticed it before. If we can figure out where the parsing is happening, perhaps we can come up with a switch for using english date here.
> Env:
> devstudio-10.2.0.AM1-v20160920-0457-B6061-installer-standalone.jar
> cdk 2.2.rc5
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBTIS-977) Fuse - Investigate whether we stiil need to wait for a dialog "Please confirm ..."
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-977:
---------------------------------------
Summary: Fuse - Investigate whether we stiil need to wait for a dialog "Please confirm ..."
Key: JBTIS-977
URL: https://issues.jboss.org/browse/JBTIS-977
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: Fuse IDE, QE
Affects Versions: 4.4.0.Alpha1
Reporter: Andrej Podhradsky
Assignee: Tomáš Sedmík
After each save the tests wait for a dialog "Please confirm ..." which is probably not needed anymore. This waiting takes 10 s after each save, so please consider removing this condition.
{code:title=CamelEditor.java}
public void save() {
activate();
new ShellMenu("File", "Save").select();
try {
new WaitUntil(new ShellWithTextIsAvailable("Please confirm..."));
new DefaultShell("Please confirm...");
new YesButton().click();
throw new CamelEditorException("There are unconnected endpoints in the diagram!");
} catch (WaitTimeoutExpiredException e) {
// The dialog "Please confirm..." didn't show up => everything is OK
}
}
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months