August 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-1825) Issues when starting and stopping an EAP or SOA-P server using -Djboss.service.binding.set=ports-03 in JBDS

by Debbie Steigner (JIRA)

Issues when starting and stopping an EAP or SOA-P server using -Djboss.service.binding.set=ports-03 in JBDS ----------------------------------------------------------------------------------------------------------- Key: JBDS-1825 URL: https://issues.jboss.org/browse/JBDS-1825 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: servers Affects Versions: 4.0.0.GA Reporter: Debbie Steigner Changed my open launch configuration for SOA-P v5.1 to use ports-03(-Djboss.service.binding.set=ports-03). When starting the server, the server starts successfully, but on the lower right hand side of the JBDS IDE, the message "Starting JBoss Server...." does not remove itself once the server has successfully started. Also, when attempting to shutdown the server from the JBDS IDE, the server aborts abruptly, an error dialog is created stating to look at the log for more errors. Using the default ports, the server behavior for starting and shutdown works successfully with no errors. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

7
11
0 / 0

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

by Martin Malina (JIRA)

Martin Malina created JBIDE-12352: ------------------------------------- Summary: Remote connection to servers cannot be established with IPv6 Key: JBIDE-12352 URL: https://issues.jboss.org/browse/JBIDE-12352 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.1 Environment: JBDS 5.0.1 Fedora 17 32bit OpenJDK 1.6 Reporter: Martin Malina Assignee: Rob Stryker Fix For: 3.3.2, 3.4.x After creating JBIDE-12351 for JMX connection, I found out that the connection cannot be established at all - even when you don't try to connect via JMX. When you set up a remote as7/eap6 server accessible over IPv6 and start the server, the remote connection will fail with this error: {code} Jul 20, 2012 3:14:57 PM org.xnio.Xnio <clinit> INFO: XNIO Version 3.0.3.GA Jul 20, 2012 3:14:57 PM org.xnio.nio.NioXnio <clinit> INFO: XNIO NIO Implementation Version 3.0.3.GA Jul 20, 2012 3:14:57 PM org.jboss.remoting3.EndpointImpl <clinit> INFO: JBoss Remoting version 3.2.7.GA Jul 20, 2012 3:15:46 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 3:15:46 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 3:15:51 PM org.xnio.Xnio <clinit> INFO: XNIO Version 3.0.4.GA-redhat-1 Jul 20, 2012 3:15:51 PM org.xnio.nio.NioXnio <clinit> INFO: XNIO NIO Implementation Version 3.0.4.GA-redhat-1 Jul 20, 2012 3:15:51 PM org.jboss.remoting3.EndpointImpl <clinit> INFO: JBoss Remoting version 3.2.8.GA-redhat-1 Jul 20, 2012 3:15:52 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-7379) Importing / Exporting of AS servers ignore command line args, filesets, xpaths, and even runtimes

by Rob Stryker (JIRA)

Importing / Exporting of AS servers ignore command line args, filesets, xpaths, and even runtimes ------------------------------------------------------------------------------------------------- Key: JBIDE-7379 URL: https://jira.jboss.org/browse/JBIDE-7379 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.Beta1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.2.0.Beta2, 3.2.0.CR1 Exporting of servers is incomplete. It does not export any saved filesets, xpaths, or custom launch configuration args. Importing of servers is also incomplete, not importing any of these elements. Also, while the servers themselves are imported, sometimes their runtimes are not created at all, and you get a server with no runtime. This has been very hard to track down, but no runtimeAdded event is ever fired, and in our code it looks as if they're not even created or looked for. This needs to be re-visited and tested extensively. I expect I will move import / export functionality into the AS plugin for now since hte o.j.t.runtime plugin already depends on AS. This will allow me to use classes already in the AS test suite for filesets and xpaths properly. I will keep the handler in the runtimes plugin but merely have it delegate to the functionality stored in the as plugin. It currently seems to be saving only servers and not the runtimes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
9
0 / 0

[JBoss JIRA] (JBIDE-12156) Apps are not deployed after EAP 6 restart

by Martin Malina (JIRA)

Martin Malina created JBIDE-12156: ------------------------------------- Summary: Apps are not deployed after EAP 6 restart Key: JBIDE-12156 URL: https://issues.jboss.org/browse/JBIDE-12156 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.CR1 Environment: jbdevstudio-product-universal-5.0.0.v20120605-2229-H183-CR1.jar JBoss EAP 6 CR1 Reporter: Martin Malina Assignee: Rob Stryker Fix For: 3.3.1 Found this when verifying JBIDE-11509. When you have EAP 6 up and running with an app deployed (any app, e.g. a simple dynamic web project) and then you stop and start the server, the app won't be deployed anymore. This is specific to EAP. In AS 7.1.1 the app gets deployed at the server start. With EAP 6 CR1 you will be shown this in the server log: {code} 15:46:25,828 INFO [org.jboss.as.server.deployment.scanner] JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy {code} I understand this is an issue of EAP, but we need to decide if we can do something to overcome this limitation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-4681) investigate amazon

by Rob Stryker (JIRA)

investigate amazon ------------------ Key: JBIDE-4681 URL: https://jira.jboss.org/jira/browse/JBIDE-4681 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.1.0.M4 investigate amazon for server adapters -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

5
13
0 / 0

[JBoss JIRA] (JBIDE-12351) JMX connection not working over IPv6

by Martin Malina (JIRA)

Martin Malina created JBIDE-12351: ------------------------------------- Summary: JMX connection not working over 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 Assignee: Rob Stryker Fix For: 3.3.2, 3.4.x 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBDS-1229) ESB binary export from JBDS doesn't include source

by Stelios Koussouris (JIRA)

ESB binary export from JBDS doesn't include source -------------------------------------------------- Key: JBDS-1229 URL: https://jira.jboss.org/browse/JBDS-1229 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: libmanagement Affects Versions: 3.0.0.GA Reporter: Stelios Koussouris Trying to export ESB binary along with the source code of a) the esb actions b) the referenced jars The result of setting the references to other projects/jars via ESB Project --> Properties --> Module Assembly and then ESB Project --> Export --> ESB --> clicking the "export source files" the jars of the referenced projects are included but no source code for nether the ESB classes or the referenced projects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

4
6
0 / 0

[JBoss JIRA] (JBIDE-10788) Add setting ui for openshift source servers to use wtp context root if required

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-10788: ----------------------------------- Summary: Add setting ui for openshift source servers to use wtp context root if required Key: JBIDE-10788 URL: https://issues.jboss.org/browse/JBIDE-10788 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: JBossAS/Servers Affects Versions: 3.3.0.M5 Reporter: Rob Stryker Assignee: Rob Stryker Priority: Minor Fix For: 3.3.0.Beta1 link to JBIDE-10514 , a UI is required for this setting. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
4
0 / 0

[JBoss JIRA] (JBIDE-12282) Local AS7/EAP6 fails to stop when bound to IPv6 address or anything but localhost really

by Martin Malina (JIRA)

13 years, 8 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-11517) Support for launching an AS 7.1.2 application client the "appclient.bat/sh" way

by Wolfgang Knauf (JIRA)

Wolfgang Knauf created JBIDE-11517: -------------------------------------- Summary: Support for launching an AS 7.1.2 application client the "appclient.bat/sh" way Key: JBIDE-11517 URL: https://issues.jboss.org/browse/JBIDE-11517 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Reporter: Wolfgang Knauf Assignee: Rob Stryker Priority: Minor JBoss 7.1.x introduced a new way to start a JavaEE application client: now the batch file "bin\appclient.bat" or "bin/appclient.sh" has to be used. I don't know the details of this file, but it basically starts a small application server, initializes e.g. JNDI and starts the main file of the app client. This approach is needed if the app client has to use the Environment Naming Context or even uses EJB injection. See this forum thread for some more details and a sample app: https://community.jboss.org/thread/195232 It would be very helpful (especially for newbies) if an JavaEE application client could be started the same way directly inside Eclipse. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
4
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 2012