[JBoss JIRA] (JBIDE-21822) Remote invocation problem when deploying and running EAP apps from JBDS
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21822?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-21822:
-----------------------------------
Fix Version/s: 4.4.x
(was: 4.4.0.Alpha1)
> 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: Mickael Istria
> Fix For: 4.4.x
>
>
> 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)
9 years, 11 months
[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift
by Thomas Mäder (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Thomas Mäder reassigned JBIDE-21857:
------------------------------------
Assignee: Thomas Mäder (was: Rob Stryker)
> Hot class reload doesn't work on OpenShift
> ------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Thomas Mäder
> Priority: Blocker
> Fix For: 4.4.0.Alpha1
>
> Attachments: HCRFailure.zip
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22043) Server adapter wizard: create unit tests
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22043?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-22043:
----------------------------------------
Assignee: Andre Dietisheim
> Server adapter wizard: create unit tests
> ----------------------------------------
>
> Key: JBIDE-22043
> URL: https://issues.jboss.org/browse/JBIDE-22043
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: server_adapter_wizard
> Fix For: 4.4.0.Alpha1
>
>
> The server adapter wizard should be unit tested. Given it's implemented using databinding and a presentation model (ServerSettingsWizardPageModel) the model can be unit tested (ex. #setService and then test all it's states: source path, deploy project etc.).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21422) Server adapter editor: details should be editable
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21422?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21422:
-------------------------------------
Sprint: devex #6 April 2016
> Server adapter editor: details should be editable
> -------------------------------------------------
>
> Key: JBIDE-21422
> URL: https://issues.jboss.org/browse/JBIDE-21422
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.0.Alpha1
>
>
> Currently when I open a server adapter overview (by double click on a server adapter) there is whole section of details to which project it is bind to, paths etc. in the Project Settings section. This area is not editable. It would be nice to allow user modify this, to allow to choose different eclipse project or fix path if it was filled in wrong...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22043) Server adapter wizard: create unit tests
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22043?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22043:
-------------------------------------
Sprint: devex #6 April 2016
> Server adapter wizard: create unit tests
> ----------------------------------------
>
> Key: JBIDE-22043
> URL: https://issues.jboss.org/browse/JBIDE-22043
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Andre Dietisheim
> Priority: Critical
> Labels: server_adapter_wizard
> Fix For: 4.4.0.Alpha1
>
>
> The server adapter wizard should be unit tested. Given it's implemented using databinding and a presentation model (ServerSettingsWizardPageModel) the model can be unit tested (ex. #setService and then test all it's states: source path, deploy project etc.).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22062) OpenShift Explorer : Make Pod/Build distinction more explicit
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22062?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22062.
---------------------------------
Verified in JBDS 10.0.0.Alpha1 B5227.
> OpenShift Explorer : Make Pod/Build distinction more explicit
> -------------------------------------------------------------
>
> Key: JBIDE-22062
> URL: https://issues.jboss.org/browse/JBIDE-22062
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Labels: ux
> Fix For: 4.4.0.Alpha1
>
>
> After witnessing a new user struggling with pods and builds in the OpenShift explorer today, I believe we need to make them more distinguishable.
> I propose we simply add the Pod/Build label like:
> !http://content.screencast.com/users/fbricon/folders/Jing/media/22e3242c-e97b-4b06-8451-85d7948c0281/00000376.png|width=650!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months