[JBoss JIRA] (JBIDE-19454) Malformed strings when starting a remote host via localhost
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19454?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-19454:
-------------------------------
Fix Version/s: 4.4.3.AM2
(was: 4.4.3.AM1)
> Malformed strings when starting a remote host via localhost
> -----------------------------------------------------------
>
> Key: JBIDE-19454
> URL: https://issues.jboss.org/browse/JBIDE-19454
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.3.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.3.AM2
>
>
> This is strange.
> When I create a remote WildFly 8.2 server on a remote server (I use a SSH-only remote host), everything works fine.
> But when I try to create a remote host that is actually localhost and then start WildFly, I get errors because some of the strings are broken.
> This is in the console in Eclipse:
> {code}
> echo $PWD'>'
> echo $PWD'>'
> java "-Dprogram.name=JBossTools: WildFly 8 remote localhost" -Xms64m -Xmx512m -XX:MaxPermSize=256m -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=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/log/boot.log" "-Dlogging.configuration=file:/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/configuration/logging.properties" "-Djboss.home.dir=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final" -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=LOCALHOST -jar /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/jboss-modules.jar -mp "/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base.dir=/Users/rasp/jbossqa/runtimes/wildfly-nattura:/ rasp$
> nattura:/ rasp$ cd /
> echo $PWD'>'
> echo $PWD'>'
> java "-Dprogram.name=JBossTools: WildFly 8 remote localhost" -Xms64m -Xmx512m -XX:MaxPermSize=256m -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=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/log/boot.log" "-Dlogging.configuration=file:/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/configuration/logging.properties" "-Djboss.home.dir=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final" -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=LOCALHOST -jar /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/jboss-modules.jar -mp "/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base.dir=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.janattura:/ rasp$
> nattura:/ rasp$ echo $PWD'>'
> echo $PWD'>'
> java "-Dprogram.name=JBossTools: WildFly 8 remote localhost" -Xms64m -Xmx512m -XX:MaxPermSize=256m -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=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/log/boot.log" "-Dlogging.configuration=file:/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/configuration/logging.properties" "-Djboss.home.dir=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final" -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=LOCALHOST -jar /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/jboss-modules.jar -mp "/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base.dir=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.javal/java "-Dne&/>
> nattura:/ rasp$ echo $PWD'>'
> />
> java "-Dprogram.name=JBossTools: WildFly 8 remote localhost" -Xms64m -Xmx512m -XX:MaxPermSize=256m -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=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/log/boot.log" "-Dlogging.configuration=file:/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/standalone/configuration/logging.properties" "-Djboss.home.dir=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final" -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=LOCALHOST -jar /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/jboss-modules.jar -mp "/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base.dir=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.javal/java "-Dne&
> eeeeeeeeTOOLnattura:/ rasp$ java "-Dprogram.name=JBossTools: WildFly 8 remote localhost" -Xm s64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net. preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.serve r.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.he adless=true "-Dorg.jboss.boot.log.file=/Users/rasp/jbossqa/runtimes/wildfly-8.2. 0.Final/standalone/log/boot.log" "-Dlogging.configuration=file:/Users/rasp/jboss qa/runtimes/wildfly-8.2.0.Final/standalone/configuration/logging.properties" "-D jboss.home.dir=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final" -Dorg.jboss.log manager.nocolor=true -Djboss.bind.address.management=LOCALHOST -jar /Users/rasp/ jbossqa/runtimes/wildfly-8.2.0.Final/jboss-modules.jar -mp "/Users/rasp/jbossqa /runtimes/wildfly-8.2.0.Final/modules" -jaxpmodule javax.xml.jaxp-provider org.j boss.as.standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base .dir=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.javal/java "-Dne&
> > eeeeeeeeTOOLS_SERVER_START_CMD:WildFly 8 remote localhost:"$!
> 13:51:37,472 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
> java.lang.IllegalStateException: JBAS018702: Server base directory does not exist: /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.javal/java
> at org.jboss.as.server.ServerEnvironment.<init>(ServerEnvironment.java:365)
> at org.jboss.as.server.Main.determineEnvironment(Main.java:262)
> at org.jboss.as.server.Main.main(Main.java:92)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.modules.Module.run(Module.java:312)
> at org.jboss.modules.Main.main(Main.java:460)
> nattura:/ rasp$
> {code}
> The correct path to the server is /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final as was set up. But for some reason, some of the strings are wrong in the startup command. Most notably this: -Djboss.server.base.dir=/Users/rasp/jbossqa/runtimes/wildfly-8.2.0.javal/java
> PS: I'm on OS X, so it might have something to do with that.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23707) Explorer: Job that initially loads resources for connection displays "Load Project"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23707?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23707:
-------------------------------------
Sprint: devex #126 January 2017
> Explorer: Job that initially loads resources for connection displays "Load Project"
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-23707
> URL: https://issues.jboss.org/browse/JBIDE-23707
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: explorer, openshift_v3
> Fix For: 4.4.3.AM2
>
> Attachments: load-project-job.png
>
>
> # ASSERT: make sure that you have a connection to an OpenShift server that is *NOT* running
> # EXEC: restart your eclipse and unfold the connection
> # ASSERT: a child "Loading...." is appearing below the connection item in the OpenShift Explorer
> # EXEC: look at the status bar and the Progress view to inspect what the job is reporting
> Result:
> The job is reporting "Load Project" which is not very insightful. I'd expect something like "Loading resources for server 10.1.2.2:8443..."
> !load-project-job.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-22805) Add Scale... menus on Pod resources
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22805?page=com.atlassian.jira.plugi... ]
Jan Richter edited comment on JBIDE-22805 at 1/10/17 9:03 AM:
--------------------------------------------------------------
Scale menu
- works fine on a pod in OS explorer
- works fine on a pod in properties view when an application is selected in OS explorer
however
- Scale menu is missing on a pod in properties view when a project is selected in OS explorer
was (Author: jrichter1):
Scale menu
- works fine on a pod in OS explorer
- works fine on a pod in properties view when an application is selected in OS explorer
however
- Scale menu is missing in properties view when a project is selected in OS explorer
> Add Scale... menus on Pod resources
> -----------------------------------
>
> Key: JBIDE-22805
> URL: https://issues.jboss.org/browse/JBIDE-22805
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Reporter: Fred Bricon
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.4.3.AM1
>
>
> I'm regularly confused/frustrated to not find the Scale... menus on the running pods. Each time I need to slap myself in the face to remind me I need to go to the Service level.
> I think it'd be more intuitive if the scale menus were present on the running pods (not on the build ones).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23707) Explorer: Job that initially loads resources for connection displays "Load Project"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23707?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23707:
-------------------------------------
Description:
# ASSERT: make sure that you have a connection to an OpenShift server that is *NOT* running
# EXEC: restart your eclipse and unfold the connection
# ASSERT: a child "Loading...." is appearing below the connection item in the OpenShift Explorer
# EXEC: look at the status bar and the Progress view to inspect what the job is reporting
Result:
The job is reporting "Load Project" which is not very insightful. I'd expect something like "Loading resources for server 10.1.2.2:8443..."
!load-project-job.png!
> Explorer: Job that initially loads resources for connection displays "Load Project"
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-23707
> URL: https://issues.jboss.org/browse/JBIDE-23707
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: explorer, openshift_v3
> Fix For: 4.4.3.AM2
>
> Attachments: load-project-job.png
>
>
> # ASSERT: make sure that you have a connection to an OpenShift server that is *NOT* running
> # EXEC: restart your eclipse and unfold the connection
> # ASSERT: a child "Loading...." is appearing below the connection item in the OpenShift Explorer
> # EXEC: look at the status bar and the Progress view to inspect what the job is reporting
> Result:
> The job is reporting "Load Project" which is not very insightful. I'd expect something like "Loading resources for server 10.1.2.2:8443..."
> !load-project-job.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23639) Application wizard: Templates parameters show wrong values if using existing eclipse project
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23639?page=com.atlassian.jira.plugi... ]
Jan Richter closed JBIDE-23639.
-------------------------------
Verified in JBT 4.4.3.AM1 / devstudio 10.3.0.AM1 staged build.
> Application wizard: Templates parameters show wrong values if using existing eclipse project
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-23639
> URL: https://issues.jboss.org/browse/JBIDE-23639
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.Final
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.3.AM1
>
>
> When creating a new OpenShift 3 application based on an eclipse project from workspace using a template, template parameters shows wrong values. E.g. I am having a project with git repo URL URL_A and template is based on source code from git repo URL URL_B. In the wizard, if I select at first template and then eclipse project, the template parameters values on the next wizard page shows values of the template instead of eclipse project. But correct values are shown.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months