August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22321) Use Same ServerHotCodeReplaceListener as for local wildfly

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22321?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22321: -------------------------------- Fix Version/s: 4.4.x (was: 4.4.1.Final) > Use Same ServerHotCodeReplaceListener as for local wildfly > ---------------------------------------------------------- > > Key: JBIDE-22321 > URL: https://issues.jboss.org/browse/JBIDE-22321 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Thomas Mäder > Assignee: Fred Bricon > Fix For: 4.4.x > > > We need to port the fix we have for wildfly to the OpenShiftServer -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23005) Server Adapter: Stuck on creating/publishing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23005?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-23005: ---------------------------------------- Assignee: Andre Dietisheim > Server Adapter: Stuck on creating/publishing > -------------------------------------------- > > Key: JBIDE-23005 > URL: https://issues.jboss.org/browse/JBIDE-23005 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.4.1.Final > > Attachments: stucked_server_adapter > > > When I am trying to create a new OpenShift 3 server adapter, many times creation does not work. Server get stucked at publishing and there is a hanging job Check module status for server eap-app at OpenShift... I am using CDK OpenShift and build an application on eap 6.4 template with kitchensink context_dir. Connection is not established. While this is happening (job is hanging) there is no error in error log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22439) Tests: include different checkers in our build or jenkins

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22439?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22439: ------------------------------------------ Getting our internal Sonar instance working is tracked at https://projects.engineering.redhat.com/browse/MWQEINFRA-89 > Tests: include different checkers in our build or jenkins > --------------------------------------------------------- > > Key: JBIDE-22439 > URL: https://issues.jboss.org/browse/JBIDE-22439 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.1.Final > > Attachments: sornarcube-github-signup-error.png > > Original Estimate: 2 days > Time Spent: 2 hours, 30 minutes > Remaining Estimate: 1 day, 5 hours, 30 minutes > > We should have different checkers in our build so that problems are forced on us. Just having them in sonar isnt good enough since it tends to get forgotten. > - Findbugs > - PMC > - Code-format-Checkers > - Code-duplication (like [cpd|http://pmd.sourceforge.net/pmd-4.3.0/cpd.html] or [simian|http://www.harukizaemon.com/simian/]) > - ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23009) Cannot connect to cdk docker in Docker Explorer

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23009?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-23009: ------------------------------------- Assignee: Xavier Coulon > Cannot connect to cdk docker in Docker Explorer > ----------------------------------------------- > > Key: JBIDE-23009 > URL: https://issues.jboss.org/browse/JBIDE-23009 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.4.1.AM3 > Reporter: Martin Malina > Assignee: Xavier Coulon > Priority: Blocker > > When I start CDK 2.2, docker connection is correctly created, but it cannot connect. There is no error message anywhere. > If I try to create a connection manually, using details from "vagrant service-manager env", the ping fails and it doesn't work either. > Connection from CLI, on the other hand, to this docker daemon works fine - when I run the export commands: > {code} > export DOCKER_HOST=tcp://172.28.128.3:2376 > export DOCKER_CERT_PATH=/Users/rasp/jbossqa/cdk2.2.rc1/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker > export DOCKER_TLS_VERIFY=1 > export DOCKER_API_VERSION=1.22 > {code} > and then try for example "docker ps" or "docker run hello-world". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-339) Support generation of update sites both with and without references to upstream TP content

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-339?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-339. ----------------------------------- Closing this issue since it was done a long time ago > Support generation of update sites both with and without references to upstream TP content > ------------------------------------------------------------------------------------------ > > Key: JBTIS-339 > URL: https://issues.jboss.org/browse/JBTIS-339 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Final > > Attachments: content.xml.new, content.xml.orig > > > Instead of associating statically sites (target-platform) when creating a repository, the generate-repository-facade mojo could create some indirection files allowing to access the repository in 2 flavours: > * One plain content only, without any reference: for downstream project aggregation > * One that also references its dependencies for easy install and testers > Example: > {code} > /integration-stack <-- composited without side effects into /earlyaccess/development/luna/ > content.jar > artifacts.jar > /withdeps <--- good for testing/single installs > /compositeContent.xml -> ../ and ../targetplatform-link/ > /compositeArtifacts.xml > /targetplatform-link <--- point to what is needed for install (not to be used by higher up composites/aggregates [JBT content, JBT IS content, JBT TP, JBT IS TP, etc.] > content.xml -> associate pointer to TP using ONLY: > <references size="4"> > <repository options="1" type="0" uri="http://download.jboss.org/jbosstools/updates/development/luna/" url="http://download.jboss.org/jbosstools/updates/development/luna/"/> (this currently includes *latest* JBT + JBT TP) > <repository options="1" type="1" uri="http://download.jboss.org/jbosstools/updates/development/luna/" url="http://download.jboss.org/jbosstools/updates/development/luna/"/> > <repository options="1" type="0" uri="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..." url="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..."/> > <repository options="1" type="1" uri="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..." url="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..."/> > </references> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-704) Marketplace entries use the old license

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-704?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-704: ------------------------------------ Fix Version/s: 9.0.2.GA (was: 9.0.1.GA) > Marketplace entries use the old license > --------------------------------------- > > Key: JBTIS-704 > URL: https://issues.jboss.org/browse/JBTIS-704 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 9.0.2.GA > > Attachments: jbdsis901ga_marketplace.png > > > The following features still use the old license > - com.jboss.devstudio.integration-stack.bpr.feature > - com.jboss.devstudio.integration-stack.ds.feature (on EA) > - com.jboss.devstudio.integration-stack.fuse.feature (on EA) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20362) Extracting of a download runtime is slow on Mac

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20362?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20362: ------------------------------- Fix Version/s: 4.4.1.Final (was: 4.4.x) > Extracting of a download runtime is slow on Mac > ----------------------------------------------- > > Key: JBIDE-20362 > URL: https://issues.jboss.org/browse/JBIDE-20362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.1.Final > > > While playing with the Download runtime fuctionality, I noticed that once a runtime (e.g. EAP 6.2) is downloaded, the extraction takes very long. I think it used to be fast and the extraction was done without any progress reporting. But now it seems that every subdirectory in the archive is being printed out which slows it down. > This extraction process took 1 min 23 sec for EAP 6.2 and I have an SSD. On a command line, this would take a few seconds. > I think the solution may be to simply show "Extracting" without printing out each file/directory that is being extracted. > (Furthermore, the progress bar does not reflect the progress - it seems there is still only perhaps 5 % done and then it's suddenly over.) > I can record a screencast if you like, but I think this should be easy to replicate. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20108) Cannot connect to remote server in JMX Navigator - Authentication fails

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20108?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20108: ------------------------------- Fix Version/s: 4.4.1.Final (was: 4.4.x) > Cannot connect to remote server in JMX Navigator - Authentication fails > ----------------------------------------------------------------------- > > Key: JBIDE-20108 > URL: https://issues.jboss.org/browse/JBIDE-20108 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.1.Final > > > When I try to connect to a remote server via JMX Navigator, it fails on authentication: > {code} > !ENTRY org.jboss.ide.eclipse.as.jmx.integration 4 0 2015-06-17 18:07:30.854 > !MESSAGE Error connecting to jmx for server JBoss EAP 6.4 marvin > !STACK 1 > org.jboss.tools.jmx.core.JMXException: Authentication against the remote JBoss instance has failed. Please verify your management credentials in the server editor. > at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:94) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:202) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:162) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:332) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connect(JBossServerConnection.java:76) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: javax.security.sasl.SaslException: Authentication failed: the server presented no authentication mechanisms > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:388) > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) > at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) > at org.xnio.ssl.JsseConnectedSslStreamChannel.handleReadable(JsseConnectedSslStreamChannel.java:183) > at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.nio.NioHandle.run(NioHandle.java:90) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:198) > at ...asynchronous invocation...(Unknown Source) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333) > at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:230) > at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:151) > at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:102) > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270) > at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:84) > ... 7 more > !SUBENTRY 1 org.jboss.ide.eclipse.as.core 4 0 2015-06-17 18:07:30.854 > !MESSAGE Authentication against the remote JBoss instance has failed. Please verify your management credentials in the server editor. > !STACK 0 > javax.security.sasl.SaslException: Authentication failed: the server presented no authentication mechanisms > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:388) > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) > at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) > at org.xnio.ssl.JsseConnectedSslStreamChannel.handleReadable(JsseConnectedSslStreamChannel.java:183) > at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.nio.NioHandle.run(NioHandle.java:90) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:198) > at ...asynchronous invocation...(Unknown Source) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333) > at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:230) > at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:151) > at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:102) > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270) > at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:84) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:202) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:162) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:332) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connect(JBossServerConnection.java:76) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > This is different than JBIDE-19463 where the main problem was the missing runtime and we assumed that otherwise it would work. > Note: I tried WildFly 8.2, WildFly 9.0.0.CR2, EAP 6.4 and all failed the same way. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18912) Custom deploy dir with remote server using filesystem operations does not work

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18912?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-18912: ------------------------------- Fix Version/s: 4.4.1.Final (was: 4.4.x) > Custom deploy dir with remote server using filesystem operations does not work > ------------------------------------------------------------------------------ > > Key: JBIDE-18912 > URL: https://issues.jboss.org/browse/JBIDE-18912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.1.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: help_wanted > Fix For: 4.4.1.Final > > > This is a follow up of JBIDE-17180 and JBIDE-13445 which added the option to add a custom deployment directory if your remote server is using filesystem operations (for management api it's not relevant since the deployment happens directly, no directory is used). > Unfortunately it does not work. It seems I haven't really tried it when reviewing those other JIRAs because there were other obstacles. > I tried this several times and still could not get it to work. > Perhaps it might be worth to try and get this in the final 4.2.1.Final build? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22741) JMX connection to remote server does not work (fs operations)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22741?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22741: ------------------------------- Fix Version/s: 4.4.1.Final > JMX connection to remote server does not work (fs operations) > ------------------------------------------------------------- > > Key: JBIDE-22741 > URL: https://issues.jboss.org/browse/JBIDE-22741 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.4.1.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.1.Final > > > I wanted to replicate JBIDE-17181 today. And I cannot replicate that problem. > But I noticed that jmx connection to a remote wf 8.2 with fs operations doesn't seem to work. I thought there was a long standing issue open for this already, but it turns out this other JIRA is for management mode: JBIDE-20108 > So it seems that neither works right now. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

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 August 2016