July 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-9442) Investigate possibility for remote debug launch of app servers

by Rob Stryker (JIRA)

Investigate possibility for remote debug launch of app servers -------------------------------------------------------------- Key: JBIDE-9442 URL: https://issues.jboss.org/browse/JBIDE-9442 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.3.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7271) Ensure Tools work with out-of-the-box platforms

by Rob Stryker (JIRA)

Ensure Tools work with out-of-the-box platforms ----------------------------------------------- Key: JBIDE-7271 URL: https://jira.jboss.org/browse/JBIDE-7271 Project: Tools (JBoss Tools) Issue Type: Task Components: JBossAS Affects Versions: 3.2.0.M2 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.2.0.CR1 I've recently started re-testing with out-of-the box platforms (EPP, EAP, SOA-P), fresh unzipped installations, and I'm realizing most of them do not have JMX enabled. This is a problem for our tools. It means things like putting the our deployments into a metadata location rather than config/deploy cannot work, because we cannot tell the Deployment Scanner (via JMX) that thats where our deployments are. Also, without JMX enabled, I've noticed my shutdown scripts fail. Originally I thought this was just a toolset issue, but when I started using the command line to see if there was some problem in the tools or not, I started realizing, I have absolutely *NO* idea how to properly shut down these platform servers without modifying property files. IS there a way? Or are all new users of EAP / EPP / SOA-P expected to go expose their jmx console in order to use the ./shutdown.sh script? For EAP and EPP, I am only able to properly shut down the server if I modify the default/conf/props/jmx-console-users.properties file. Is this correct? There is no way to shut down the server from the command line without exposing a user via JMX? When trying SOA-P 5.1, I notice the same behaviour. The shutdown script does not work at all without JMX exposed, *AND*, in this case, the "soa-users.properties" file is the one containing the usernames and passwords admin=admin. A summary, In order to enable *command line* shutdowns (and thus tooling shutdowns), it seems I must modify a properties file (who's name changes between platforms??) to expose the jmx console. So again, I ask, am I doing this right? This is all command-line. The next problem is, assuming all my assumptions are correct, what should our tools do to help users with a fresh *manually downloaded* EAP / EPP / SOA-P installations do to get set up? (As far as I know, JBDS bundles customize the configuration slightly). Should we offer to expose their consoles FOR them by changing this properties file? Or should we simply deploy all objects in server/{config}/deploy instead of in workspace.metadata.folder and use jmx to add that folder to the deployment scanner? -- 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, 6 months

4
8
0 / 0

[JBoss JIRA] (JBIDE-12157) Cannot start Gatein 3.3 JBoss 7 with default configuration

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-12157: --------------------------------------- Summary: Cannot start Gatein 3.3 JBoss 7 with default configuration Key: JBIDE-12157 URL: https://issues.jboss.org/browse/JBIDE-12157 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers, Portal/GateIn Affects Versions: 3.3.0.CR1 Environment: JBDS 5 CR1b, GateIn-3.3.0-GA-jbossas7 Reporter: Lucia Jelinkova Assignee: Rob Stryker Fix For: 3.3.0.Final When I add new Gatein 3.3 with JBoss AS7 to JBT, I need to modify the launch configuration manually in order for server to start. I needed to modify -mp parameter in Program arguments {code} -mp "/home/ljelinko/programs/jboss/GateIn/GateIn-3.3.0-GA-jbossas7/modules:/home/ljelinko/programs/jboss/GateIn/GateIn-3.3.0-GA-jbossas7/gatein/modules" {code} And add the following into the VM arguments {code} -Dexo.conf.dir=/home/ljelinko/programs/jboss/GateIn/GateIn-3.3.0-GA-jbossas7/bin/../standalone/configuration/gatein -Dexo.conf.dir.name=gatein {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, 6 months

3
3
0 / 0

[JBoss JIRA] (JBIDE-10525) server editor Server behavior expansion too tall

by Martin Malina (Created) (JIRA)

server editor Server behavior expansion too tall ------------------------------------------------ Key: JBIDE-10525 URL: https://issues.jboss.org/browse/JBIDE-10525 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.M4 Reporter: Martin Malina Assignee: Max Rydahl Andersen Priority: Critical Fix For: 3.3.0.M5 Just noticed that server behavior tab does not render/expand for me. See http://screencast.com/t/jZOxxGjoRyI -- 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, 6 months

4
6
0 / 0

[JBoss JIRA] (JBIDE-11983) Investigate what's up with Equinox Resource Monitoring

by Martin Malina (JIRA)

Martin Malina created JBIDE-11983: ------------------------------------- Summary: Investigate what's up with Equinox Resource Monitoring Key: JBIDE-11983 URL: https://issues.jboss.org/browse/JBIDE-11983 Project: Tools (JBoss Tools) Issue Type: Task Components: jmx Affects Versions: 3.3.0.Beta3 Reporter: Martin Malina Assignee: Rob Stryker Fix For: 3.3.x While reviewing docs for JBDS 5 (JBDS-2029) I came upon the chapter describing how to make a JMX connection to Equinox Resource Monitoring which provides a JMX server for management of running plugins. It turned out the monitoring feature apparently never made it out of the eclipse incubator and I found no way how to download it and install in Eclipse. The project page is here: http://www.eclipse.org/equinox/incubator/monitoring/index.php We decided that for the time being we will remove this from our JMX Guide and Rob asked for this JIRA to investigate what else can be done here. -- 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, 6 months

2
2
0 / 0

[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, 6 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, 6 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, 6 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, 6 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, 6 months

5
13
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 July 2012