[JBoss JIRA] (JBIDE-21869) Encoding issue in when streaming Build Logs to the console
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21869?page=com.atlassian.jira.plugi... ]
Jeff Cantrill updated JBIDE-21869:
----------------------------------
Priority: Minor (was: Major)
> Encoding issue in when streaming Build Logs to the console
> ----------------------------------------------------------
>
> Key: JBIDE-21869
> URL: https://issues.jboss.org/browse/JBIDE-21869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Priority: Minor
>
> Create a new nodejs app, when a build is running, in the OpenShift Explorer, right click on the build and select the Build Log... menu.
> It'll start to spew weird characters eventually :
> {noformat}
> I0315 10:38:28.749220 1 docker.go:286] Image "registry.access.redhat.com/openshift3/nodejs-010-rhel7:latest" not available locally, pulling ...
> I0315 10:39:16.195418 1 source.go:197] Downloading "https://github.com/openshift/nodejs-ex.git" ...
> I0315 10:39:19.670243 1 install.go:236] Using "assemble" installed from "image:///usr/libexec/s2i/assemble"
> I0315 10:39:19.670318 1 install.go:236] Using "run" installed from "image:///usr/libexec/s2i/run"
> I0315 10:39:19.670356 1 install.go:236] Using "save-artifacts" installed from "image:///usr/libexec/s2i/save-artifacts"
> ---> Installing application source
> ---> Building your Node application from source
> E0315 10:39:21.193046 1 util.go:91] npm info it worked if it ends with ok
> E0315 10:39:21.193216 1 util.go:91] npm info using npm(a)2.14.13
> E0315 10:39:21.193229 1 util.go:91] npm info using node(a)v0.10.40
> ...
> E0315 10:39:27.511826 1 util.go:91] npm info prepublish nodejs-ex(a)0.0.1
> ejs(a)2.4.1 node_modules/ejs
> express(a)4.13.4 node_modules/express
> ��������� escape-html(a)1.0.3
> ��������� array-flatten(a)1.1.1
> ��������� utils-merge(a)1.0.0
> ��������� cookie-signature(a)1.0.6
> ��������� merge-descriptors(a)1.0.1
> ��������� fresh(a)0.3.0
> ��������� methods(a)1.1.2
> ��������� range-parser(a)1.0.3
> ��������� vary(a)1.0.1
> ��������� path-to-regexp(a)0.1.7
> ��������� cookie(a)0.1.5
> ��������� parseurl(a)1.3.1
> ��������� content-type(a)1.0.1
> ��������� etag(a)1.7.0
> ��������� content-disposition(a)0.5.1
> ��������� serve-static(a)1.10.2
> ��������� depd(a)1.1.0
> ��������� qs(a)4.0.0
> ��������� finalhandler(a)0.4.1 (unpipe(a)1.0.0)
> ��������� on-finished(a)2.3.0 (ee-first(a)1.1.1)
> ��������� debug(a)2.2.0 (ms(a)0.7.1)
> ��������� proxy-addr(a)1.0.10 (forwarded(a)0.1.0, ipaddr.js(a)1.0.5)
> ��������� send(a)0.13.1 (destroy(a)1.0.4, statuses(a)1.2.1, ms(a)0.7.1, mime(a)1.3.4, http-errors(a)1.3.1)
> ��������� type-is(a)1.6.12 (media-typer(a)0.3.0, mime-types(a)2.1.10)
> ��������� accepts(a)1.2.13 (negotiator(a)0.5.3, mime-types(a)2.1.10)
> mongodb(a)2.1.8 node_modules/mongodb
> ��������� es6-promise(a)3.0.2
> ��������� mongodb-core(a)1.3.5 (bson(a)0.4.22, require_optional(a)1.0.0)
> ��������� readable-stream(a)1.0.31 (inherits(a)2.0.1, isarray(a)0.0.1, string_decoder(a)0.10.31, core-util-is(a)1.0.2)
> E0315 10:39:27.684535 1 util.go:91] npm info ok
> I0315 10:39:42.202321 1 sti.go:245] Using provided push secret for pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image
> I0315 10:39:42.202361 1 sti.go:249] Pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image ...
> {noformat}
> I'm running on OSX
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3566) include AERI in JBDS 9.1
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3566:
----------------------------------
After a fresh install of jboss-devstudio-9.1.0.CR1-v20160311-1249-B402-installer-standalone.jar, I enabled the debug mode flag on the Error Reporting preferences page, then tried to load an invalid update site via Help > Install New > http://not-a-site. No AERI.
Also tried starting JBDS 9.1 with -debug -console -consolelog and ... nope, again, no AERI.
And, I discovered that if you hit ESC on the dialog "Configure Automated Error Reporting" EVEN IF both boxes are checked to "On", both boxes will be set to "Off". Apparently the escape event == Disable, not "keep current settings". Somehow I also got Eclipse to switch me from 'Notify me of new problems' to 'Never send reports'.
So... still not sure how to enable AERI. Can you suggest a better error that it might want to report than java.net.UnknownHostException or org.eclipse.equinox.p2.core.ProvisionException ?
> include AERI in JBDS 9.1
> ------------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aeri, build, target-platform
> Affects Versions: 9.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 9.1.0.CR1
>
> Attachments: aeri-in-jbds91.png, error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21822) Remote invocation problem when deploying and running EAP apps from JBDS
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21822?page=com.atlassian.jira.plugi... ]
Fred Bricon edited comment on JBIDE-21822 at 3/16/16 9:52 AM:
--------------------------------------------------------------
Eclipse supports project names != from folder names, when they're imported from *outside* the workspace folder.
m2e sets the project name with the artifactId value by default. But users can use a different pattern if they like.
JBoss folks have a specialty in that they consistently use artifactId != folder, which can cause some problems because Example projects are usually imported *inside* the workspace and that causes a project name / folder mismatch, which may then cause a context root mismatch for web apps.
was (Author: fbricon):
Eclipse supports project names != from folder names, when they're imported from *outside* the workspace folder.
m2e sets the project name with the artifactId value by default. But users can use a different pattern if they like.
JBoss folks have a specialty in that they consistently use artifactId != folder, which can cause some problems because Example projects are usually imported *inside* the workspace and that causes a project name / folder mismatch, which cause may cause a context root mismatch.
> Remote invocation problem when deploying and running EAP apps from JBDS
> -----------------------------------------------------------------------
>
> Key: JBIDE-21822
> URL: https://issues.jboss.org/browse/JBIDE-21822
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport, server
> Affects Versions: 4.3.0.Final
> Environment: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Maven home: /opt/apache-maven-3.3.9
> Java version: 1.8.0_74, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_74/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.4.3-300.fc23.x86_64+debug", arch: "amd64", family: "unix"
> Fedora 23
> Reporter: Michal Jurc
> Assignee: Rob Stryker
>
> When attempting to follow the steps in ejb-remote quickstart for EAP 6.4.6.GA and 7.0.0.ER6, after deploying the server-side application, the client application has problem with remote invocation of the application deployed:
> {code}
> Exception in thread "main" java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:jboss-ejb-remote-server-side, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@731a74c
> at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:798)
> at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:128)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183)
> at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146)
> at com.sun.proxy.$Proxy0.add(Unknown Source)
> at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.invokeStatelessBean(RemoteEJBClient.java:57)
> at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.main(RemoteEJBClient.java:38)
> {code}
> The same quickstart can be completed when ran from terminal on standalone EAP (EAP not launched and managed by JBDS).
> I was so far unable to reproduce the issue on other machines.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21821) JBT 4.3.0.Final / JBDS 9.0.0.GA target platforms include org.eclipse.egit.importer.ui 4.0, which installs jgit 4.0; this breaks egit 4.1.1 views when JBT 4.3.0 or JBDS 9.0.0 are installed into Mars.2
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21821?page=com.atlassian.jira.plugi... ]
Nick Boldt resolved JBIDE-21821.
--------------------------------
Resolution: Done
Re-resolved.
Here's a PR for the blog that Max requested:
https://github.com/jbosstools/jbosstools-website/pull/554/
https://github.com/nickboldt/jbosstools-website/blob/mars.2-patchfix-JBID...
> JBT 4.3.0.Final / JBDS 9.0.0.GA target platforms include org.eclipse.egit.importer.ui 4.0, which installs jgit 4.0; this breaks egit 4.1.1 views when JBT 4.3.0 or JBDS 9.0.0 are installed into Mars.2
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21821
> URL: https://issues.jboss.org/browse/JBIDE-21821
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, marketplace
> Reporter: Thomas Mäder
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.3.1.CR1, 4.3.0.Final
>
> Attachments: FrameworkEvent ERROR.txt, jbt-error, jgit40_41_JBDS.installed.txt, jgit40_41_JBT.installed.txt
>
>
> Installing Red Hat JBoss Developer Studio 9.0.0GA into a fresh Eclipse 4.5.2 (for Eclipse Committers) causes Egit to break.
> # Install Eclipse 4.5.2
> # In the Marketplace, search for "jboss developer studio"
> # You get a single result: Red Hat JBoss Developer Studio 9.0.0 GA
> # Install it
> # Restart
> # Observe: the EGit views and preferences are missing
> # Observe: you get messages in the Eclipse error log concerning a dependency version incompatibility
> -----
> JBT 4.3.0.Final / JBDS 9.0.0.GA target platforms include org.eclipse.egit.importer.ui 4.0.0.201506090130-r (Mars.1 version), which installs jgit 4.0.3.201509231615-r (Mars.1 version); this breaks egit 4.1.1 views when installed into Mars.2, because Mars.2 site does not include org.eclipse.egit.ui.importer 4.1.1.201511131810-r, and you confuse egit when you have both jgit 4.0 and 4.1 installed, disabling views and preferences.
> Solution proposed is to add org.eclipse.egit.ui.importer 4.1.1.201511131810-r to the composite site from which JBT 4.3.0.Final and JBDS 9.0.0.GA are installed, so that when org.eclipse.egit.ui.importer is installed, p2 can select the 4.1.1 version instead of the 4.0.0 version.
> I would want to pull a mirror of http://download.eclipse.org/egit/updates-4.1.1/ onto download.jboss.org if we're cool with this solution.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21822) Remote invocation problem when deploying and running EAP apps from JBDS
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21822?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21822:
-------------------------------------
Eclipse supports project names != from folder names, when they're imported from *outside* the workspace folder.
m2e sets the project name with the artifactId value by default. But users can use a different pattern if they like.
JBoss folks have a specialty in that they consistently use artifactId != folder, which can cause some problems because Example projects are usually imported *inside* the workspace and that causes a project name / folder mismatch, which cause may cause a context root mismatch.
> Remote invocation problem when deploying and running EAP apps from JBDS
> -----------------------------------------------------------------------
>
> Key: JBIDE-21822
> URL: https://issues.jboss.org/browse/JBIDE-21822
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport, server
> Affects Versions: 4.3.0.Final
> Environment: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Maven home: /opt/apache-maven-3.3.9
> Java version: 1.8.0_74, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_74/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.4.3-300.fc23.x86_64+debug", arch: "amd64", family: "unix"
> Fedora 23
> Reporter: Michal Jurc
> Assignee: Rob Stryker
>
> When attempting to follow the steps in ejb-remote quickstart for EAP 6.4.6.GA and 7.0.0.ER6, after deploying the server-side application, the client application has problem with remote invocation of the application deployed:
> {code}
> Exception in thread "main" java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:jboss-ejb-remote-server-side, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@731a74c
> at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:798)
> at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:128)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183)
> at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146)
> at com.sun.proxy.$Proxy0.add(Unknown Source)
> at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.invokeStatelessBean(RemoteEJBClient.java:57)
> at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.main(RemoteEJBClient.java:38)
> {code}
> The same quickstart can be completed when ran from terminal on standalone EAP (EAP not launched and managed by JBDS).
> I was so far unable to reproduce the issue on other machines.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years