March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21822) Remote invocation problem when deploying and running EAP apps from JBDS

by Michal Jurc (JIRA)

Michal Jurc created JBIDE-21822: ----------------------------------- Summary: 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: 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 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). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21822) Remote invocation problem when deploying and running EAP apps from JBDS

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21822?page=com.atlassian.jira.plugi... ] Radim Hopp reassigned JBIDE-21822: ---------------------------------- Assignee: Rob Stryker > 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: 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). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21802) Content assist for image names in "Deploy Docker Image" wizard

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21802?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-21802: ------------------------------------- Assignee: Andre Dietisheim (was: Xavier Coulon) [~adietish], could you review this patch, please ? > Content assist for image names in "Deploy Docker Image" wizard > --------------------------------------------------------------- > > Key: JBIDE-21802 > URL: https://issues.jboss.org/browse/JBIDE-21802 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > Fix For: 4.3.1.CR1 > > > The {{Image Name}} field could be enhanced with content assist based on the list of image names+tags retrieved from the selected Docker connection. > If the user inputs a name that does not match the list, a warning on the page would inform him/her that a remote call to the registry would be performed upon page completion, ie, when clicking on the {{Next}} button. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21821) JBoss Developer Studio Marketplace Install Breaks Egit in Mars.2

by Thomas Mäder (JIRA)

Thomas Mäder created JBIDE-21821: ------------------------------------ Summary: JBoss Developer Studio Marketplace Install Breaks Egit in Mars.2 Key: JBIDE-21821 URL: https://issues.jboss.org/browse/JBIDE-21821 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: marketplace Reporter: Thomas Mäder 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 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3590) add LICENSE file to root of installer jars

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3590?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3590. ----------------------------- Verified with 9.1.0.CR1-v20160307-0610-B390 and 10.0.0.Alpha1-v20160307-0526-B4927. > add LICENSE file to root of installer jars > ------------------------------------------ > > Key: JBDS-3590 > URL: https://issues.jboss.org/browse/JBDS-3590 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: build, installer > Affects Versions: 9.1.0.Beta2, 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.1.0.CR1, 10.0.0.Alpha1 > > > Denis Golovin asked: {quote} why do we need to do step 3 ("Add jbdevstudio-product/installer/LICENCE file with content similar to https://github.com/dgolovin/jbdevstudio-product/blob/master/plugins/com.j...") - can't we just have a copy of the EPL?{quote} > Richard Fontana replied:{quote} Sure we can include copy of EPL in that file. The same way thym does in https://github.com/eclipse/thym/blob/master/LICENSE.{quote} > Thus, we should add a LICENSE file into the root of the installer jars, so it's more obvious that the installer is EPL'd. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3589) no composite*.xml files in root of JBDS installer

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3589?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3589. ----------------------------- Verified with 9.1.0.CR1-v20160307-0610-B390 and 10.0.0.Alpha1-v20160307-0526-B4927. > no composite*.xml files in root of JBDS installer > ------------------------------------------------- > > Key: JBDS-3589 > URL: https://issues.jboss.org/browse/JBDS-3589 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.1.0.CR1, 10.0.0.Alpha1 > > > JBDS installer no longer includes composite*.xml in its root folder, so the jar won't work as an offline update site (eg., for an offline install of JBDS IS into Eclipse) > {code} > org.eclipse.equinox.p2.core.ProvisionException: No repository found at jar:file:/home/nboldt/tmp/JBDS_Installers/jboss-devstudio-9.1.0.Beta2-v20160127-2213-B262-installer-standalone.jar!/. > {code} > Workaround: > use jar:file:/home/nboldt/tmp/JBDS_Installers/jboss-devstudio-9.1.0.Beta2-v20160127-2213-B262-installer-standalone.jar!/jbds/ as the update site path -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3670) Build self executable bundled installer on Jenkins

by Denis Golovin (JIRA)

Denis Golovin created JBDS-3670: ----------------------------------- Summary: Build self executable bundled installer on Jenkins Key: JBDS-3670 URL: https://issues.jboss.org/browse/JBDS-3670 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: installer Affects Versions: 9.1.0.Beta2 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 9.1.0.CR1 Latest version of electron-packager-squirrel-windows cannot handle big installer with size more than 600Mb approximately. This forces us to use alternative approach for bundled installer that includes: * CDK; * SSH/rsync * openjdk8 * JBDS To create bundled installer, build should download all required binaries and put them along with installer exe file with with the same name that installer uses in online version. For example CDK binaries would go to cdk.zip, JBDS installer to jbds.jar and so on. Names are configured in browser/model/*.js files for every downloaded binary. Then 7zip extra package should be downloaded and used t produce self extracting archive from generated electron installer (gulp generate) and downloaded binaries. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3669) Inject version, timestamp and Jenkins build number into installer to show in installer window

by Denis Golovin (JIRA)

Denis Golovin created JBDS-3669: ----------------------------------- Summary: Inject version, timestamp and Jenkins build number into installer to show in installer window Key: JBDS-3669 URL: https://issues.jboss.org/browse/JBDS-3669 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: installer Affects Versions: 9.1.0.Beta2 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 9.1.0.CR1 Currently this information is not available in installer at execution time, we should create json or js file with this info before executing the build, include it in installer and use during installation to get required data. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3668) Add version, timestamp and build number to PDK installer exe file name

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3668?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3668: ----------------------------------- Assignee: Denis Golovin > Add version, timestamp and build number to PDK installer exe file name > ---------------------------------------------------------------------- > > Key: JBDS-3668 > URL: https://issues.jboss.org/browse/JBDS-3668 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.1.0.CR1 > > > Insatller file name should contain: > * version > * timestamp > * build number > To let report issues with reference to specific version/build -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3668) Add version, timestamp and build number to PDK installer exe file name

by Denis Golovin (JIRA)

Denis Golovin created JBDS-3668: ----------------------------------- Summary: Add version, timestamp and build number to PDK installer exe file name Key: JBDS-3668 URL: https://issues.jboss.org/browse/JBDS-3668 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: installer Affects Versions: 9.1.0.Beta2 Reporter: Denis Golovin Fix For: 9.1.0.CR1 Insatller file name should contain: * version * timestamp * build number To let report issues with reference to specific version/build -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2016