[JBoss JIRA] (JBIDE-23549) JSF New and Noteworthy for 4.4.2.Final
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23549?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-23549.
----------------------------------
Fix Version/s: 4.4.2.Final
Resolution: Rejected
> JSF New and Noteworthy for 4.4.2.Final
> -----------------------------------------------------
>
> Key: JBIDE-23549
> URL: https://issues.jboss.org/browse/JBIDE-23549
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jsf, jsp/jsf/xml/html-source-editing
> Reporter: Jeff MAURY
> Assignee: Alexey Kazakov
> Priority: Critical
> Fix For: 4.4.2.Final
>
>
> Search for your component's New and Noteworthy issues:
> Queries:
> * [Completed JSF JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
> * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
> * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...]
> * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...]
> If no N&N issues are found for JSF, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them.
> Document the ones relevant for JSF by submitting a pull request against:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> If your PR's commit comment is of the form 'JBIDE-56789 #comment Create N&N for JSF4.4.2.Final #close', and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied.
> If there is nothing new or noteworthy for JSF for this milestone, please *reject* and *close* this issue.
> ----
> If there is nothing new or noteworthy for 4.4.2.Final since the AM3 release of JSF, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents.
> If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.4.2.Final.adoc file here:
> * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
> The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc.
> However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.4.2.Final.adoc file, adding: {code}page-include-previous: false{code}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23514) Server adapter: adapters for non-java app should not have a JMX child (double clicking it causes error)
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23514?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-23514:
-------------------------------------
[~adietish] We 100% need to get an API to describe what the openshift apps are. We need to an API for basic qualities about it, like whether it's java-based, whether it can expose debug ports, what type of deployment behavior it needs (ie does it need .dodeploy marker or not), etc.
There are a whole bunch of usecases here where the logic for an openshift adapter needs to know what it's referencing. Lots of behavior could change based on this.
> Server adapter: adapters for non-java app should not have a JMX child (double clicking it causes error)
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23514
> URL: https://issues.jboss.org/browse/JBIDE-23514
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Andre Dietisheim
> Labels: jmx, openshift_v3, server_adapter
> Fix For: 4.4.3.AM1
>
> Attachments: jmx-error-nodejs.png
>
>
> Most likely server adapters for non-java based apps should not have a jmx node.
> Steps to reproduce:
> # ASSERT: make sure that you have a nodejs app (with a service) running in OpenShift (ex. created via nodejs-example template)
> # ASSERT: make sure the build is finished, the pod is running.
> # ASSERT: make sure that you have a server adapter for your service
> # ASSERT: make sure that it is in "[Started, Synchronized]" state)
> # EXEC: unfold the server adapter and double click on the JMX child
> Result:
> An error shows up
> !jmx-error-nodejs.png!
> {code}
> java.io.IOException: org.jolokia.client.exception.J4pRemoteException: Service Unavailable
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:328)
> at org.jboss.tools.openshift.core.server.OpenshiftJMXConnectionProvider$1.verifyServerReachable(OpenshiftJMXConnectionProvider.java:83)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.jolokia.client.exception.J4pRemoteException: Service Unavailable at org.jolokia.client.J4pClient.extractJsonResponse(J4pClient.java:278)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:191)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23430) Run as -> Run on server -> browser might open too early causing http 404
by Josef Ludvicek (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23430?page=com.atlassian.jira.plugi... ]
Josef Ludvicek commented on JBIDE-23430:
----------------------------------------
Thanks for explanation of {{JBoss7ModuleStateVerifier}} [~rob.stryker].
I thought that credentials were defined, but it's possible that there was something missing on my side.
Np :)
> Run as -> Run on server -> browser might open too early causing http 404
> ------------------------------------------------------------------------
>
> Key: JBIDE-23430
> URL: https://issues.jboss.org/browse/JBIDE-23430
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.2.AM2
> Reporter: Josef Ludvicek
> Assignee: Rob Stryker
> Fix For: 4.5.0.AM1
>
> Attachments: runas.png
>
>
> There should be some mechanism to detect when application is succesfully deployed.
> It is possible that on slow machine it starts to deploy and open internal web browser too early - before app is fully deployed.
> Stepps:
> * start eap server
> * right click on app -> Run as -> run on server
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23431) Remote server over ssh does not work with cygwin
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23431?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-23431:
--------------------------------
Fix Version/s: 4.5.0.AM1
> 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
> Fix For: 4.5.0.AM1
>
>
> 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, 4 months