[JBoss JIRA] (JBTIS-637) Cannot install JBoss Integration & SOA Dev
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-637?page=com.atlassian.jira.plugin.... ]
Paul Leacu reassigned JBTIS-637:
--------------------------------
Assignee: Paul Leacu
> Cannot install JBoss Integration & SOA Dev
> ------------------------------------------
>
> Key: JBTIS-637
> URL: https://issues.jboss.org/browse/JBTIS-637
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 9.0.0.CR1
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Blocker
>
> The following error occurs if you try to install com.jboss.devstudio.integration-stack.soa.feature from
> https://devstudio.redhat.com/9.0/staging/updates/integration-stack/
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: JBoss Integration and SOA Development 9.0.0.CR1 (com.jboss.devstudio.integration-stack.soa.feature.feature.group 9.0.0.CR1)
> Missing requirement: JBoss Integration and SOA Development 9.0.0.CR1 (com.jboss.devstudio.integration-stack.soa.feature.feature.group 9.0.0.CR1) requires 'org.fusesource.ide.camel.editor.feature.feature.group 0.0.0' but it could not be found
> {code}
> EDIT: Note that this will be a problem when installing JBDS-IS from Marketplace (I think the above feature is used in marketplace)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22112) Profile button should be disabled for OpenShift servers
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-22112:
-------------------------------------
Summary: Profile button should be disabled for OpenShift servers
Key: JBIDE-22112
URL: https://issues.jboss.org/browse/JBIDE-22112
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Fred Bricon
Assignee: Fred Bricon
Priority: Minor
Fix For: 4.3.1.CR1, 4.4.0.Alpha1
Profile button is enabled an OpenShift Servers but it's not supported. We should disable it
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22075) Cannot debug OpenShift application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22075:
-------------------------------------
Attachment: remote-debugger-already-launched.png
> Cannot debug OpenShift application
> ----------------------------------
>
> Key: JBIDE-22075
> URL: https://issues.jboss.org/browse/JBIDE-22075
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Critical
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha1
>
> Attachments: error-in-launching-remote-debugger.png, error-launching-remote-debugger.png, remote-debugger-already-launched.png
>
>
> When I am trying to run remote debugging of an application on OpenShift I get following error
> {code}
> Failed to connect to remote VM
> com.sun.jdi.connect.spi.ClosedConnectionException
> at org.eclipse.jdi.internal.connect.SocketTransportService.readHandshake(SocketTransportService.java:222)
> at org.eclipse.jdi.internal.connect.SocketTransportService.access$7(SocketTransportService.java:214)
> at org.eclipse.jdi.internal.connect.SocketTransportService$3.run(SocketTransportService.java:185)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> I guess this is something related to port forwarding. Even the port for debugging is forwarded on a free port and it looks like started, it fails. When I stop port forwarding, start it again and use a port, which is used as a forwarded port for remote debug port, in debug configuration, it works.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22075) Cannot debug OpenShift application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22075:
-------------------------------------
Fix Version/s: 4.4.0.Alpha1
> Cannot debug OpenShift application
> ----------------------------------
>
> Key: JBIDE-22075
> URL: https://issues.jboss.org/browse/JBIDE-22075
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Critical
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha1
>
> Attachments: error-in-launching-remote-debugger.png, error-launching-remote-debugger.png, remote-debugger-already-launched.png
>
>
> When I am trying to run remote debugging of an application on OpenShift I get following error
> {code}
> Failed to connect to remote VM
> com.sun.jdi.connect.spi.ClosedConnectionException
> at org.eclipse.jdi.internal.connect.SocketTransportService.readHandshake(SocketTransportService.java:222)
> at org.eclipse.jdi.internal.connect.SocketTransportService.access$7(SocketTransportService.java:214)
> at org.eclipse.jdi.internal.connect.SocketTransportService$3.run(SocketTransportService.java:185)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> I guess this is something related to port forwarding. Even the port for debugging is forwarded on a free port and it looks like started, it fails. When I stop port forwarding, start it again and use a port, which is used as a forwarded port for remote debug port, in debug configuration, it works.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3770) Truncated error message display connecting to server
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3770?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-3770:
-------------------------------
Attachment: bad_token_2.png
bad_token_1.png
> Truncated error message display connecting to server
> ----------------------------------------------------
>
> Key: JBDS-3770
> URL: https://issues.jboss.org/browse/JBDS-3770
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 9.1.0.CR1
> Environment: Version: 9.1.0.GA
> Build id: GA-v20160403-1700-B477
> Build date: 20160403-1700
> Reporter: Len DiMaggio
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Attachments: bad_token_1.png, bad_token_2.png
>
>
> See attached screenshot - the error message is truncated until the user expands the width of the dialog.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years