[JBoss JIRA] (JBIDE-21942) Null pointer when trying to start CDK sometimes
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21942?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-21942.
---------------------------------
[~jcantrill], please let us know if you're still experiencing this. I haven't seen this and I'm closing this JIRA for now.
> Null pointer when trying to start CDK sometimes
> -----------------------------------------------
>
> Key: JBIDE-21942
> URL: https://issues.jboss.org/browse/JBIDE-21942
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.Beta2
> Reporter: Jeff Cantrill
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.3.1.CR1
>
>
> Trying to start the CDK after, laptop hibernate, and CDK was started before sometimes throws. Looks like there should be some null check
> {code}
> Exception in thread "Loading ADBInfo to configure dependent frameworks" java.lang.NumberFormatException: null
> at java.lang.Integer.parseInt(Integer.java:542)
> at java.lang.Integer.parseInt(Integer.java:615)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKDockerUtility.buildDockerConnection(CDKDockerUtility.java:83)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKDockerUtility.createDockerConnection(CDKDockerUtility.java:92)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureDocker(ConfigureDependentFrameworksListener.java:60)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.launchChange(ConfigureDependentFrameworksListener.java:45)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.access$0(ConfigureDependentFrameworksListener.java:34)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener$1.run(ConfigureDependentFrameworksListener.java:28)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-637) Cannot install JBoss Integration & SOA Dev
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-637?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky commented on JBTIS-637:
-----------------------------------------
I think it would be enought just to update com.jboss.devstudio.integration-stack.soa.feature/features.xml and comment out the Fuse tooling.
> 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
> 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}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-637) Cannot install JBoss Integration & SOA Dev
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-637:
---------------------------------------
Summary: 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
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}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22078) Error publishing war file to wildfy 10.0 on windows
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22078?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22078:
--------------------------------
Steps to Reproduce:
- have a wildfly 10 server running
- create a new Maven project
- click "Create a simple project", next
- fill in, groupId, artifactId, packaging = war, click finish
- right click on project > JavaEE tools > Generate Deployment descriptor stub (just to get rid of Maven's error about missing web.xml)
- right mouse click on the server in the server view --> Add and remove... --> add the project
- test the project in the browser
- right mouse click on the server in the server view --> Clean...
- test the project in the browser again
was:
- create a new Maven project
- click "Create a simple project", next
- fill in, groupId, artifactId, packaging = war, click finish
- right mouse cick on the server in the server view --> Add and remove... --> add the project
- right click on project > JavaEE tools > Generate Deployment descriptor stub (just to get rid of Maven's error about missing web.xml)
- run as > run on server
- select Wildfly 10 (configure it if necessary)
- test the project in the browser
- right mouse click on the server in the server view --> Clean...
- test the project in the browser again
> Error publishing war file to wildfy 10.0 on windows
> ---------------------------------------------------
>
> Key: JBIDE-22078
> URL: https://issues.jboss.org/browse/JBIDE-22078
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Final
> Environment: - Windows 7 x64
> - jdk1.8.0_77 (32-bit)
> - Eclipse Mars.2 (32-bit)
> - JBoss Tools 4.3.0.FINAL
> - Wildfly 10.0.0.FINAL
> Reporter: Tobias van den Berg
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> The following error is thrown after publishing a maven webapplication (.war) to Wildfly 10.0:
> "Error renaming C:\wildfly-10.0.0.Final\standalone\tmp\tmp8945090880188299781.properties to C:\wildfly-10.0.0.Final\standalone\deployments\WebViewer-0.0.3-SNAPSHOT.war\META-INF\maven\nl.incad.webviewer\WebViewer\pom.properties.
> This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination.
> You may adjust these settings in the server editor."
> The webapplication is no longer available/online after the error. The only solution is to restart the server and to re-add the webapplication to the server. This makes it very hard to develop/test a webapplication on wildfly 10. The same error is thrown on wildfly 8.0/8.1, but the difference is that the webapplication is still available/online after the error.
> I've tried/tested the following:
> - Checked/updated Windows file permisions for the wildfly directory
> - Take ownership of the wildfly directory (recursively)
> - Disabled Windows User Account Control (UAC)
> - Run Eclipse as Admin
> Relates to:
> - JBIDE-18697
> - JBIDE-17545
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22078) Error publishing war file to wildfy 10.0 on windows
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22078?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22078:
--------------------------------
Steps to Reproduce:
- create a new Maven project
- click "Create a simple project", next
- fill in, groupId, artifactId, packaging = war, click finish
- right mouse cick on the server in the server view --> Add and remove... --> add the project
- right click on project > JavaEE tools > Generate Deployment descriptor stub (just to get rid of Maven's error about missing web.xml)
- run as > run on server
- select Wildfly 10 (configure it if necessary)
- test the project in the browser
- right mouse click on the server in the server view --> Clean...
- test the project in the browser again
was:
- create a simple maven webproject (.war)
- right mouse cick on the server in the server view --> Add and remove... --> add the project
- test the project in the browser
- right mouse click on the server in the server view --> Clean...
- test the project in the browser again
> Error publishing war file to wildfy 10.0 on windows
> ---------------------------------------------------
>
> Key: JBIDE-22078
> URL: https://issues.jboss.org/browse/JBIDE-22078
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Final
> Environment: - Windows 7 x64
> - jdk1.8.0_77 (32-bit)
> - Eclipse Mars.2 (32-bit)
> - JBoss Tools 4.3.0.FINAL
> - Wildfly 10.0.0.FINAL
> Reporter: Tobias van den Berg
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> The following error is thrown after publishing a maven webapplication (.war) to Wildfly 10.0:
> "Error renaming C:\wildfly-10.0.0.Final\standalone\tmp\tmp8945090880188299781.properties to C:\wildfly-10.0.0.Final\standalone\deployments\WebViewer-0.0.3-SNAPSHOT.war\META-INF\maven\nl.incad.webviewer\WebViewer\pom.properties.
> This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination.
> You may adjust these settings in the server editor."
> The webapplication is no longer available/online after the error. The only solution is to restart the server and to re-add the webapplication to the server. This makes it very hard to develop/test a webapplication on wildfly 10. The same error is thrown on wildfly 8.0/8.1, but the difference is that the webapplication is still available/online after the error.
> I've tried/tested the following:
> - Checked/updated Windows file permisions for the wildfly directory
> - Take ownership of the wildfly directory (recursively)
> - Disabled Windows User Account Control (UAC)
> - Run Eclipse as Admin
> Relates to:
> - JBIDE-18697
> - JBIDE-17545
--
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 commented on JBIDE-22075:
------------------------------------------
I cant attach the remote debugger at all. Even with the workaround - stop port forwarding and restart it, checking "find free ports", I get the following error:
!error-launching-remote-debugger.png!
{code}
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at java.net.Socket.connect(Socket.java:538)
at java.net.Socket.<init>(Socket.java:434)
at java.net.Socket.<init>(Socket.java:211)
at org.eclipse.jdi.internal.connect.SocketTransportService$2.run(SocketTransportService.java:148)
at java.lang.Thread.run(Thread.java:745)
{code}
> 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
> Attachments: error-in-launching-remote-debugger.png, error-launching-remote-debugger.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:
-------------------------------------
Attachment: error-launching-remote-debugger.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
> Attachments: error-in-launching-remote-debugger.png, error-launching-remote-debugger.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