[JBoss JIRA] (JBDS-4200) Problem installing switchyard
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4200?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4200:
-----------------------------
Parent: JBDS-4175
Issue Type: Sub-task (was: Bug)
> Problem installing switchyard
> -----------------------------
>
> Key: JBDS-4200
> URL: https://issues.jboss.org/browse/JBDS-4200
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: rpm
> Affects Versions: 10.2.0.GA
> Environment: RHEL7
> Reporter: Lukáš Valach
> Fix For: 10.2.0.GA
>
> Attachments: rh-eclipse46-devstudio10.2.log.switchyard_plugin_test.txt
>
>
> I tried to install switchyard and this error appeared in the log after restart:
> {code}
> !ENTRY org.switchyard.tools.core 4 0 2016-11-23 09:45:11.118
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.switchyard.tools.core [1390]
> Bundle was not resolved because of a uses contraint violation.
> org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.switchyard.tools.core [osgi.identity; osgi.identity="org.switchyard.tools.core"; type="osgi.bundle"; version:Version="2.2.0.Final-v20161110-1803-B65"] because it is exposed to package 'org.slf4j' from resources org.slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"; osgi.identity="org.slf4j.api"] and slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.4"; osgi.identity="slf4j.api"] via two dependency chains.
> {code}
> See whole log here [^rh-eclipse46-devstudio10.2.log.switchyard_plugin_test.txt].
> Tested in 10.2-0.20161123.1426.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4200) Problem installing switchyard
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4200?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4200:
-----------------------------
Fix Version/s: 10.2.0.GA
> Problem installing switchyard
> -----------------------------
>
> Key: JBDS-4200
> URL: https://issues.jboss.org/browse/JBDS-4200
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: rpm
> Affects Versions: 10.2.0.GA
> Environment: RHEL7
> Reporter: Lukáš Valach
> Fix For: 10.2.0.GA
>
> Attachments: rh-eclipse46-devstudio10.2.log.switchyard_plugin_test.txt
>
>
> I tried to install switchyard and this error appeared in the log after restart:
> {code}
> !ENTRY org.switchyard.tools.core 4 0 2016-11-23 09:45:11.118
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.switchyard.tools.core [1390]
> Bundle was not resolved because of a uses contraint violation.
> org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.switchyard.tools.core [osgi.identity; osgi.identity="org.switchyard.tools.core"; type="osgi.bundle"; version:Version="2.2.0.Final-v20161110-1803-B65"] because it is exposed to package 'org.slf4j' from resources org.slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"; osgi.identity="org.slf4j.api"] and slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.4"; osgi.identity="slf4j.api"] via two dependency chains.
> {code}
> See whole log here [^rh-eclipse46-devstudio10.2.log.switchyard_plugin_test.txt].
> Tested in 10.2-0.20161123.1426.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4200) Problem installing switchyard
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4200?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-4200:
--------------------------------
Assignee: Nick Boldt
> Problem installing switchyard
> -----------------------------
>
> Key: JBDS-4200
> URL: https://issues.jboss.org/browse/JBDS-4200
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: rpm
> Affects Versions: 10.2.0.GA
> Environment: RHEL7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 10.2.0.GA
>
> Attachments: rh-eclipse46-devstudio10.2.log.switchyard_plugin_test.txt
>
>
> I tried to install switchyard and this error appeared in the log after restart:
> {code}
> !ENTRY org.switchyard.tools.core 4 0 2016-11-23 09:45:11.118
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.switchyard.tools.core [1390]
> Bundle was not resolved because of a uses contraint violation.
> org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.switchyard.tools.core [osgi.identity; osgi.identity="org.switchyard.tools.core"; type="osgi.bundle"; version:Version="2.2.0.Final-v20161110-1803-B65"] because it is exposed to package 'org.slf4j' from resources org.slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"; osgi.identity="org.slf4j.api"] and slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.4"; osgi.identity="slf4j.api"] via two dependency chains.
> {code}
> See whole log here [^rh-eclipse46-devstudio10.2.log.switchyard_plugin_test.txt].
> Tested in 10.2-0.20161123.1426.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-22035) Server adapter: Stopping of J2EE module does not work
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22035?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22035:
-------------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.4.x)
> Server adapter: Stopping of J2EE module does not work
> -----------------------------------------------------
>
> Key: JBIDE-22035
> URL: https://issues.jboss.org/browse/JBIDE-22035
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Rob Stryker
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.0.AM1
>
>
> Stopping of J2EE Web module lying under an OpenShift 3 Server Adapter does nothing. After discussion with Rob in JBIDE-21989, stop of J2EE module should create an .undeploy marker and rsync it, but that's not happening. Only output from rsync when stopping J2EE module is following
> {code}sent 46 bytes received 1,333 bytes 2,758.00 bytes/sec
> total size is 8,523,390 speedup is 6,180.85
> sending incremental file list
> ROOT.war.isdeploying
> sent 1,428 bytes received 149 bytes 3,154.00 bytes/sec
> total size is 8,523,390 speedup is 5,404.81{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-21962) See if we can use higher resolution for openshift/patternfly icons
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21962?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-21962.
---------------------------------
Resolution: Rejected
No.
> See if we can use higher resolution for openshift/patternfly icons
> ------------------------------------------------------------------
>
> Key: JBIDE-21962
> URL: https://issues.jboss.org/browse/JBIDE-21962
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Catherine Robson
> Priority: Minor
> Fix For: 4.4.x
>
>
> This is a follow up on JBIDE-21911. Current patternfly 16px icons used for openshift tooling were scaled down via icomoon.io or manually, eg.:
> - Route !https://raw.githubusercontent.com/jbosstools/jbosstools-openshift/master/plugins/org.jboss.tools.openshift.ui/icons/route.png!
> - Service !https://raw.githubusercontent.com/jbosstools/jbosstools-openshift/master/plugins/org.jboss.tools.openshift.ui/icons/service.png!
> Resolution seems suboptimal, would be nice to use nicer looking icons for the full openshift icons set.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-21822) Remote invocation problem when deploying and running EAP apps from JBDS
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21822?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21822:
-------------------------------------
Fix Version/s: 4.5.0.AM1
> 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.5.0.AM1
>
>
> 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
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-21822) Remote invocation problem when deploying and running EAP apps from JBDS
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21822?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21822:
-------------------------------------
Fix Version/s: (was: 4.4.x)
> 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.5.0.AM1
>
>
> 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
(v7.2.3#72005)
9 years, 4 months