September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-16066: ------------------------------------------- The issue appears to be an incompatibility with Java versions in the runtime settings. The Eclipse instance is running on Java 7, but the Execution Environment for the JBoss Runtime (Preferences/Runtime Environment) was set to JavaSE-1.8 instead of JavaSE-1.7. Apparently that was throwing things off in my Eclipse instance when it tried to kick off the server. > Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-16066 > URL: https://issues.jboss.org/browse/JBIDE-16066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.CR1 > Environment: JBDS 7.1.0 CR1, EAP-6.1 > Reporter: Radoslav Rábara > Assignee: Brian Fitzpatrick > Fix For: 4.2.0.CR2 > > Attachments: topDownServer.log > > > Deployment isn't successful when Top-Down web service is created with slider level selected to "Start service" or "Test service". Project is deployed to the server but the service endpoint isn't added so the service is not accessible. > It works with other slider levels and all levels works when the server isn't started before the web service is created. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14035) Make browserSim available for download from JBoss Tools site

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14035?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-14035: ------------------------------------------------ [~nickboldt], building zip works on [nightly|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-vp...], zip archive is on [Nexus|https://repository.jboss.org/nexus/content/repositories/snapshots/o...]. I think we should create "release jobs" for standalone browsersim and give direct links on website for its result. > Make browserSim available for download from JBoss Tools site > ------------------------------------------------------------ > > Key: JBIDE-14035 > URL: https://issues.jboss.org/browse/JBIDE-14035 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: browsersim > Affects Versions: 4.1.0.Beta1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Fix For: 4.2.0.Final > > > Since we make standalone build of browserSim on Hudson, it will be glad to allow users to download standalone browserSim app. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-16066: ------------------------------------- Jstack will get a stack of all threads in a current java process. {code} [rob@localhost jbosstools-server]$ locate jstack /usr/lib/jvm/jdk1.7.0_51/bin/jstack [rob@localhost jbosstools-server]$ /usr/lib/jvm/jdk1.7.0_51/bin/jstack Usage: jstack [-l] <pid> (to connect to running process) jstack -F [-m] [-l] <pid> (to connect to a hung process) jstack [-m] [-l] <executable> <core> (to connect to a core file) jstack [-m] [-l] [server_id@]<remote server IP or hostname> (to connect to a remote debug server) Options: -F to force a thread dump. Use when jstack <pid> does not respond (process is hung) -m to print both java and native frames (mixed mode) -l long listing. Prints additional information about locks -h or -help to print this help message {code} > Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-16066 > URL: https://issues.jboss.org/browse/JBIDE-16066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.CR1 > Environment: JBDS 7.1.0 CR1, EAP-6.1 > Reporter: Radoslav Rábara > Assignee: Brian Fitzpatrick > Fix For: 4.2.0.CR2 > > Attachments: topDownServer.log > > > Deployment isn't successful when Top-Down web service is created with slider level selected to "Start service" or "Test service". Project is deployed to the server but the service endpoint isn't added so the service is not accessible. > It works with other slider levels and all levels works when the server isn't started before the web service is created. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18456) Central connectors linked to earlyaccess URLs

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18456?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18456: ---------------------------------------- Priority: Blocker (was: Major) > Central connectors linked to earlyaccess URLs > --------------------------------------------- > > Key: JBIDE-18456 > URL: https://issues.jboss.org/browse/JBIDE-18456 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: discovery > Affects Versions: 4.2.0.CR1 > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.2.0.CR2 > > > Some connectors on Central are actually linking to Early Access URLs. They should point to the main URL (8.0-staging/). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12351) Remote JMX connection to servers cannot be established with IPv6

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12351?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-12351: ---------------------------------------- Labels: f2f2014 (was: ) > Remote JMX connection to servers cannot be established with IPv6 > ---------------------------------------------------------------- > > Key: JBIDE-12351 > URL: https://issues.jboss.org/browse/JBIDE-12351 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 3.3.0.Final > Environment: Fedora 17 32bit > EAP 6.0.0.GA > Reporter: Martin Malina > Labels: f2f2014 > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > When I set up a remote server accessible over IPv6, start the server and then try to open the server in MBean Explorer, it's stuck on "Loading" and keeps printing this error in the log: > {code} > ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed > Jul 20, 2012 2:41:24 PM org.xnio.Xnio <clinit> > INFO: XNIO Version 3.0.4.GA-redhat-1 > Jul 20, 2012 2:41:25 PM org.xnio.nio.NioXnio <clinit> > INFO: XNIO NIO Implementation Version 3.0.4.GA-redhat-1 > Jul 20, 2012 2:41:25 PM org.jboss.remoting3.EndpointImpl <clinit> > INFO: JBoss Remoting version 3.2.8.GA-redhat-1 > Jul 20, 2012 2:41:25 PM org.jboss.remoting3.remote.RemoteConnection handleException > ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed > Jul 20, 2012 2:41:25 PM org.xnio.Xnio <clinit> > INFO: XNIO Version 3.0.4.GA-redhat-1 > Jul 20, 2012 2:41:25 PM org.xnio.nio.NioXnio <clinit> > INFO: XNIO NIO Implementation Version 3.0.4.GA-redhat-1 > Jul 20, 2012 2:41:25 PM org.jboss.remoting3.EndpointImpl <clinit> > INFO: JBoss Remoting version 3.2.8.GA-redhat-1 > Jul 20, 2012 2:41:26 PM org.jboss.remoting3.remote.RemoteConnection handleException > ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-16066: ------------------------------------------- [~maxandersen] Have never used jstack - point me at a download and directions? > Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-16066 > URL: https://issues.jboss.org/browse/JBIDE-16066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.CR1 > Environment: JBDS 7.1.0 CR1, EAP-6.1 > Reporter: Radoslav Rábara > Assignee: Brian Fitzpatrick > Fix For: 4.2.0.CR2 > > Attachments: topDownServer.log > > > Deployment isn't successful when Top-Down web service is created with slider level selected to "Start service" or "Test service". Project is deployed to the server but the service endpoint isn't added so the service is not accessible. > It works with other slider levels and all levels works when the server isn't started before the web service is created. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12351) Remote JMX connection to servers cannot be established with IPv6

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12351?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-12351: ---------------------------------------- Fix Version/s: 4.2.1.Final 4.3.0.Alpha1 > Remote JMX connection to servers cannot be established with IPv6 > ---------------------------------------------------------------- > > Key: JBIDE-12351 > URL: https://issues.jboss.org/browse/JBIDE-12351 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 3.3.0.Final > Environment: Fedora 17 32bit > EAP 6.0.0.GA > Reporter: Martin Malina > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > When I set up a remote server accessible over IPv6, start the server and then try to open the server in MBean Explorer, it's stuck on "Loading" and keeps printing this error in the log: > {code} > ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed > Jul 20, 2012 2:41:24 PM org.xnio.Xnio <clinit> > INFO: XNIO Version 3.0.4.GA-redhat-1 > Jul 20, 2012 2:41:25 PM org.xnio.nio.NioXnio <clinit> > INFO: XNIO NIO Implementation Version 3.0.4.GA-redhat-1 > Jul 20, 2012 2:41:25 PM org.jboss.remoting3.EndpointImpl <clinit> > INFO: JBoss Remoting version 3.2.8.GA-redhat-1 > Jul 20, 2012 2:41:25 PM org.jboss.remoting3.remote.RemoteConnection handleException > ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed > Jul 20, 2012 2:41:25 PM org.xnio.Xnio <clinit> > INFO: XNIO Version 3.0.4.GA-redhat-1 > Jul 20, 2012 2:41:25 PM org.xnio.nio.NioXnio <clinit> > INFO: XNIO NIO Implementation Version 3.0.4.GA-redhat-1 > Jul 20, 2012 2:41:25 PM org.jboss.remoting3.EndpointImpl <clinit> > INFO: JBoss Remoting version 3.2.8.GA-redhat-1 > Jul 20, 2012 2:41:26 PM org.jboss.remoting3.remote.RemoteConnection handleException > ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2852) Database/source/connection Usability

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2852?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen reassigned JBDS-2852: ----------------------------------------- Assignee: Max Rydahl Andersen (was: Burr Sutter) > Database/source/connection Usability > ------------------------------------ > > Key: JBDS-2852 > URL: https://issues.jboss.org/browse/JBDS-2852 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: integration, requirements > Reporter: Burr Sutter > Assignee: Max Rydahl Andersen > Labels: QE_JBDS80_needinfo > > Connecting to a database from within JBDS/Eclipse is a multi-step, multi-screen, potentially error-prone challenge. > Forge is involved as it can generate entities from schema > Datasources are needed in/on AS/Wildfly/EAP in order for the project deploy > Persistence.xml may needed to be tweaked for the datasource > End-user would like to navigate the schema in the DTP/Hibernate Tools, interactively review the data and there was once a feature for viewing an ORM diagram that I seem to have forgotten how it is displayed. > What happens when a project that needs a database connection is imported into the IDE? > This was partially addressed with > https://issues.jboss.org/browse/JBIDE-15263 > Let's see if we can continue to improve the workflow by reducing steps, making it more obvious what steps are required (e.g. hey developer, get the mysql driver .jar), auto generating the -ds.xml, with a decent explanation for the end-user to follow. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3119) XML Schema validation fails when importing external schema

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3119?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3119: -------------------------------------- Component/s: ver server > XML Schema validation fails when importing external schema > ---------------------------------------------------------- > > Key: JBDS-3119 > URL: https://issues.jboss.org/browse/JBDS-3119 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: 3rd-party-dependencies, server, ver > Affects Versions: 8.0.0.Beta3 > Reporter: Mustafa Musaji > Assignee: Rob Stryker > > Product JIRA for upstream bug - https://bugs.eclipse.org/bugs/show_bug.cgi?id=315741 > This is to track the upstream bug in Eclipse that we need to pull in to JBDS at some point. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3119) XML Schema validation fails when importing external schema

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3119?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3119: -------------------------------------- Assignee: Rob Stryker > XML Schema validation fails when importing external schema > ---------------------------------------------------------- > > Key: JBDS-3119 > URL: https://issues.jboss.org/browse/JBDS-3119 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: 3rd-party-dependencies > Affects Versions: 8.0.0.Beta3 > Reporter: Mustafa Musaji > Assignee: Rob Stryker > > Product JIRA for upstream bug - https://bugs.eclipse.org/bugs/show_bug.cgi?id=315741 > This is to track the upstream bug in Eclipse that we need to pull in to JBDS at some point. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 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 September 2014