[JBoss JIRA] (JBIDE-10756) Debug button attempts to start already running server, reports port in use
10:53 a.m.
James Wilson created JBIDE-10756:
------------------------------------
Summary: Debug button attempts to start already running server, reports port
in use
Key: JBIDE-10756
URL: https://issues.jboss.org/browse/JBIDE-10756
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Indigo (Win XP)
Reporter: James Wilson
Assignee: Rob Stryker
Priority: Optional
I've added a JBoss AS (4.2) server to the Servers view. I select it and then press the
"Start the server in debug mode" button on the Servers view toolbar. When I want
to run my application I usually click on the Debug button on the main Eclipse toolbar,
which launches the last configuration run. In my Ganymede setup (so I think JBoss Tools
3.0) that didn't include starting the JBoss AS server, but in Indigo/JBoss Tools 3.3
(M5) it does. Thus the tooltip for the debug button becomes "Debug JBoss v4.2 at
localhost (already running)", and if I click on it I get a message box stating:
'Launching JBoss v4.2 at localhost' has encountered a problem.
Server port In Ue 80080-Http
In the Servers view my JBoss 4.2 AS server then shows as stopped. I can start it again and
it all works fine after that.
--
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
10:58 a.m.
[
https://issues.jboss.org/browse/JBIDE-10756?page=com.atlassian.jira.plugi...
]
James Wilson commented on JBIDE-10756:
--------------------------------------
Only entry in the Error Log view mirrors the dialog displayed, namely:
eclipse.buildId=M20110909-1335
java.version=1.7.0_02
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os win32 -ws win32 -arch x86 -product
org.eclipse.epp.package.jee.product
Error
Tue Jan 31 09:50:25 GMT 2012
Server port In Use 8080-Http
Debug button attempts to start already running server, reports port
in use
--------------------------------------------------------------------------
Key: JBIDE-10756
URL: https://issues.jboss.org/browse/JBIDE-10756
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Indigo (Win XP)
Reporter: James Wilson
Assignee: Rob Stryker
Priority: Optional
I've added a JBoss AS (4.2) server to the Servers view. I select it and then press
the "Start the server in debug mode" button on the Servers view toolbar. When I
want to run my application I usually click on the Debug button on the main Eclipse
toolbar, which launches the last configuration run. In my Ganymede setup (so I think JBoss
Tools 3.0) that didn't include starting the JBoss AS server, but in Indigo/JBoss Tools
3.3 (M5) it does. Thus the tooltip for the debug button becomes "Debug JBoss v4.2 at
localhost (already running)", and if I click on it I get a message box stating:
'Launching JBoss v4.2 at localhost' has encountered a problem.
Server port In Ue 80080-Http
In the Servers view my JBoss 4.2 AS server then shows as stopped. I can start it again
and it all works fine after that.
--
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
11:57 a.m.
[
https://issues.jboss.org/browse/JBIDE-10756?page=com.atlassian.jira.plugi...
]
James Wilson updated JBIDE-10756:
---------------------------------
Attachment: JBIDE-10756-screenshot.png
Screenshot showing error
Debug button attempts to start already running server, reports port
in use
--------------------------------------------------------------------------
Key: JBIDE-10756
URL: https://issues.jboss.org/browse/JBIDE-10756
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Indigo (Win XP)
Reporter: James Wilson
Assignee: Rob Stryker
Priority: Optional
Attachments: JBIDE-10756-screenshot.png
I've added a JBoss AS (4.2) server to the Servers view. I select it and then press
the "Start the server in debug mode" button on the Servers view toolbar. When I
want to run my application I usually click on the Debug button on the main Eclipse
toolbar, which launches the last configuration run. In my Ganymede setup (so I think JBoss
Tools 3.0) that didn't include starting the JBoss AS server, but in Indigo/JBoss Tools
3.3 (M5) it does. Thus the tooltip for the debug button becomes "Debug JBoss v4.2 at
localhost (already running)", and if I click on it I get a message box stating:
'Launching JBoss v4.2 at localhost' has encountered a problem.
Server port In Ue 80080-Http
In the Servers view my JBoss 4.2 AS server then shows as stopped. I can start it again
and it all works fine after that.
--
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
12:04 p.m.
[
https://issues.jboss.org/browse/JBIDE-10756?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10756:
---------------------------------------------
James - two different problems in here I believe:
1) Different behavior in run-as from Ganymede - that i'm not sure why that would not
include starting jboss since that is what run-as done for an app.
2) That the server view thinks your server is not running but it seems to be
running....that one is weird.
Any chance that server is not setup to run on 8080 or ?
Debug button attempts to start already running server, reports port
in use
--------------------------------------------------------------------------
Key: JBIDE-10756
URL: https://issues.jboss.org/browse/JBIDE-10756
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Indigo (Win XP)
Reporter: James Wilson
Assignee: Rob Stryker
Priority: Optional
Attachments: JBIDE-10756-screenshot.png
I've added a JBoss AS (4.2) server to the Servers view. I select it and then press
the "Start the server in debug mode" button on the Servers view toolbar. When I
want to run my application I usually click on the Debug button on the main Eclipse
toolbar, which launches the last configuration run. In my Ganymede setup (so I think JBoss
Tools 3.0) that didn't include starting the JBoss AS server, but in Indigo/JBoss Tools
3.3 (M5) it does. Thus the tooltip for the debug button becomes "Debug JBoss v4.2 at
localhost (already running)", and if I click on it I get a message box stating:
'Launching JBoss v4.2 at localhost' has encountered a problem.
Server port In Ue 80080-Http
In the Servers view my JBoss 4.2 AS server then shows as stopped. I can start it again
and it all works fine after that.
--
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
12:29 p.m.
[
https://issues.jboss.org/browse/JBIDE-10756?page=com.atlassian.jira.plugi...
]
James Wilson updated JBIDE-10756:
---------------------------------
Attachment: JBIDE-10756-server_settings.png
JBoss AS settings
Debug button attempts to start already running server, reports port
in use
--------------------------------------------------------------------------
Key: JBIDE-10756
URL: https://issues.jboss.org/browse/JBIDE-10756
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Indigo (Win XP)
Reporter: James Wilson
Assignee: Rob Stryker
Priority: Optional
Attachments: JBIDE-10756-screenshot.png, JBIDE-10756-server_settings.png
I've added a JBoss AS (4.2) server to the Servers view. I select it and then press
the "Start the server in debug mode" button on the Servers view toolbar. When I
want to run my application I usually click on the Debug button on the main Eclipse
toolbar, which launches the last configuration run. In my Ganymede setup (so I think JBoss
Tools 3.0) that didn't include starting the JBoss AS server, but in Indigo/JBoss Tools
3.3 (M5) it does. Thus the tooltip for the debug button becomes "Debug JBoss v4.2 at
localhost (already running)", and if I click on it I get a message box stating:
'Launching JBoss v4.2 at localhost' has encountered a problem.
Server port In Ue 80080-Http
In the Servers view my JBoss 4.2 AS server then shows as stopped. I can start it again
and it all works fine after that.
--
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
12:29 p.m.
[
https://issues.jboss.org/browse/JBIDE-10756?page=com.atlassian.jira.plugi...
]
James Wilson commented on JBIDE-10756:
--------------------------------------
Sorry, I guess I should have created 2 reports.
1) I've noticed something that may be interesting - in Indigo the JBoss server is an
entry in the 'Generic Servers' branch of Debug Configurations, in Ganymede I
can't see it anywhere. Also, though I've set up JBoss AS 6 and 7 servers in Indigo
they aren't in the Generic Servers branch (though I haven't started either
successfully yet, they're there for investigation when I get some time).
2) I think the server view is correct, when the error message is displayed the server is
terminated. It's more the other way around, when the Debug button on the main toolbar
is pressed presumably it should act in the same way as the debug button on the Servers
view, namely if the server is running it should stop it then start it again. It still
wouldn't be what I'd want, but it'd be more a 'feature' than a bug!
Yes, the port is 8080. I'll attach the server configuration.
Debug button attempts to start already running server, reports port
in use
--------------------------------------------------------------------------
Key: JBIDE-10756
URL: https://issues.jboss.org/browse/JBIDE-10756
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Indigo (Win XP)
Reporter: James Wilson
Assignee: Rob Stryker
Priority: Optional
Attachments: JBIDE-10756-screenshot.png, JBIDE-10756-server_settings.png
I've added a JBoss AS (4.2) server to the Servers view. I select it and then press
the "Start the server in debug mode" button on the Servers view toolbar. When I
want to run my application I usually click on the Debug button on the main Eclipse
toolbar, which launches the last configuration run. In my Ganymede setup (so I think JBoss
Tools 3.0) that didn't include starting the JBoss AS server, but in Indigo/JBoss Tools
3.3 (M5) it does. Thus the tooltip for the debug button becomes "Debug JBoss v4.2 at
localhost (already running)", and if I click on it I get a message box stating:
'Launching JBoss v4.2 at localhost' has encountered a problem.
Server port In Ue 80080-Http
In the Servers view my JBoss 4.2 AS server then shows as stopped. I can start it again
and it all works fine after that.
--
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
12:41 p.m.
[
https://issues.jboss.org/browse/JBIDE-10756?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10756:
---------------------------------------------
1) aaaah - so you actually did not use jboss tools for your server adapters but the
generic ganymede ones.
Have you tried using gneric serves in Indigo too and verified it have same behavior ?
I'm though still surprised that generic server adapters wouldn't start/stop
server on run as.
2) The error message hints that 8080 is already in use so it does not seem the server is
actually stopped.
Debug button attempts to start already running server, reports port
in use
--------------------------------------------------------------------------
Key: JBIDE-10756
URL: https://issues.jboss.org/browse/JBIDE-10756
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Indigo (Win XP)
Reporter: James Wilson
Assignee: Rob Stryker
Priority: Optional
Attachments: JBIDE-10756-screenshot.png, JBIDE-10756-server_settings.png
I've added a JBoss AS (4.2) server to the Servers view. I select it and then press
the "Start the server in debug mode" button on the Servers view toolbar. When I
want to run my application I usually click on the Debug button on the main Eclipse
toolbar, which launches the last configuration run. In my Ganymede setup (so I think JBoss
Tools 3.0) that didn't include starting the JBoss AS server, but in Indigo/JBoss Tools
3.3 (M5) it does. Thus the tooltip for the debug button becomes "Debug JBoss v4.2 at
localhost (already running)", and if I click on it I get a message box stating:
'Launching JBoss v4.2 at localhost' has encountered a problem.
Server port In Ue 80080-Http
In the Servers view my JBoss 4.2 AS server then shows as stopped. I can start it again
and it all works fine after that.
--
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
1:01 p.m.
[
https://issues.jboss.org/browse/JBIDE-10756?page=com.atlassian.jira.plugi...
]
James Wilson commented on JBIDE-10756:
--------------------------------------
1) Sorry, I don't understand that. I believe in both (definitely in Indigo, I think in
Ganymede though it was a while ago) to set up a server I right-clicked in the Servers view
and clicked New->Server, then picked the appropriate version of JBoss AS from the JBoss
Community branch. Is that not the right way to do it?
I've just tried to add a Generic Server in Ganymede and there are no entries in the
Server combo box.
2) When the Debug button is pressed the server isn't stopped. I believe what's
happening is it doesn't realise the server is already started so tries to do so again,
discovers the port is in use, then when it is aborting it manages to terminate the
already-running server. That's why the server is stopped in the screenshot, before the
error it's running fine.
Debug button attempts to start already running server, reports port
in use
--------------------------------------------------------------------------
Key: JBIDE-10756
URL: https://issues.jboss.org/browse/JBIDE-10756
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Indigo (Win XP)
Reporter: James Wilson
Assignee: Rob Stryker
Priority: Optional
Attachments: JBIDE-10756-screenshot.png, JBIDE-10756-server_settings.png
I've added a JBoss AS (4.2) server to the Servers view. I select it and then press
the "Start the server in debug mode" button on the Servers view toolbar. When I
want to run my application I usually click on the Debug button on the main Eclipse
toolbar, which launches the last configuration run. In my Ganymede setup (so I think JBoss
Tools 3.0) that didn't include starting the JBoss AS server, but in Indigo/JBoss Tools
3.3 (M5) it does. Thus the tooltip for the debug button becomes "Debug JBoss v4.2 at
localhost (already running)", and if I click on it I get a message box stating:
'Launching JBoss v4.2 at localhost' has encountered a problem.
Server port In Ue 80080-Http
In the Servers view my JBoss 4.2 AS server then shows as stopped. I can start it again
and it all works fine after that.
--
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
7:29 p.m.
[
https://issues.jboss.org/browse/JBIDE-10756?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-10756:
-------------------------------------
Hi James:
The screenshots you are showing indicate you are using generic server adapters, the jboss
server adapters bundled with eclipse and wtp. We can tell this because the server editor
(2nd pic) is pretty empty compared to ours, and the error dialog (first pic) is not
something we put up. These are definitely generic servers.
I've tested this issue using jboss tools in a new workspace with jboss-tools only
server adapters, and the only way i've been able to replicate anything remotely
similar is when you previously ran an app (dynwebProject1) on one server (server1), then
stopped it, then started server 2, then reran your "run on server" action from
the debug menu pull down, which immediately attempts to launch server1 again.
In JBossTools, though, a dialog is thrown up indicating another server is found running,
and would we like to set the new server adapter to 'running' without launching a
new instance, cancel the launch, or launch a new instance anyway. This dialog is not
showing up in your screenshots.
Either way, I can honestly assure you that you are using the generic server adapters and
not the jbosstools adapters. In the new server wizard, directly above "JBoss
Community", is another category "JBoss". I believe that you have been using
these adapters.
You can verify this if you want. In the servers view, right click on your server, then
select "properties". In the "general" tab you will see a button
"Switch Location". Press it. You will see a new project appear in your
workspace, "servers", inside which you will see a file named JBoss 4.2.server.
Right-click that file, open in -> text editor. You will almost 100% see the following
somewhere in that file:
server-type-id="org.eclipse.jst.server.generic.jboss42"
Good luck!
Debug button attempts to start already running server, reports port
in use
--------------------------------------------------------------------------
Key: JBIDE-10756
URL: https://issues.jboss.org/browse/JBIDE-10756
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Indigo (Win XP)
Reporter: James Wilson
Assignee: Rob Stryker
Priority: Optional
Attachments: JBIDE-10756-screenshot.png, JBIDE-10756-server_settings.png
I've added a JBoss AS (4.2) server to the Servers view. I select it and then press
the "Start the server in debug mode" button on the Servers view toolbar. When I
want to run my application I usually click on the Debug button on the main Eclipse
toolbar, which launches the last configuration run. In my Ganymede setup (so I think JBoss
Tools 3.0) that didn't include starting the JBoss AS server, but in Indigo/JBoss Tools
3.3 (M5) it does. Thus the tooltip for the debug button becomes "Debug JBoss v4.2 at
localhost (already running)", and if I click on it I get a message box stating:
'Launching JBoss v4.2 at localhost' has encountered a problem.
Server port In Ue 80080-Http
In the Servers view my JBoss 4.2 AS server then shows as stopped. I can start it again
and it all works fine after that.
--
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
7:35 p.m.
[
https://issues.jboss.org/browse/JBIDE-10756?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-10756:
-------------------------------------
I have just verified the string you are seeing is only for a generic server.
[rob@rawb servertools]$ pwd
/home/rob/code/eclipse/wtp-trunk/servertools
[rob@rawb servertools]$ grep -R "Server port In Use" *
plugins/org.eclipse.jst.server.generic.core/bin/org/eclipse/jst/server/generic/core/internal/GenericServerCoreMessages.properties:errorPortInUse=Server
port In Use {0}-{1}
plugins/org.eclipse.jst.server.generic.core/src/org/eclipse/jst/server/generic/core/internal/GenericServerCoreMessages.properties:errorPortInUse=Server
port In Use {0}-{1}
This shows the string is inside webtools source code inside the generic server framework.
A similar grep inside the JBossTools source code shows no results for this string.
Debug button attempts to start already running server, reports port
in use
--------------------------------------------------------------------------
Key: JBIDE-10756
URL: https://issues.jboss.org/browse/JBIDE-10756
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Indigo (Win XP)
Reporter: James Wilson
Assignee: Rob Stryker
Priority: Optional
Attachments: JBIDE-10756-screenshot.png, JBIDE-10756-server_settings.png
I've added a JBoss AS (4.2) server to the Servers view. I select it and then press
the "Start the server in debug mode" button on the Servers view toolbar. When I
want to run my application I usually click on the Debug button on the main Eclipse
toolbar, which launches the last configuration run. In my Ganymede setup (so I think JBoss
Tools 3.0) that didn't include starting the JBoss AS server, but in Indigo/JBoss Tools
3.3 (M5) it does. Thus the tooltip for the debug button becomes "Debug JBoss v4.2 at
localhost (already running)", and if I click on it I get a message box stating:
'Launching JBoss v4.2 at localhost' has encountered a problem.
Server port In Ue 80080-Http
In the Servers view my JBoss 4.2 AS server then shows as stopped. I can start it again
and it all works fine after that.
--
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
10:31 a.m.
[
https://issues.jboss.org/browse/JBIDE-10756?page=com.atlassian.jira.plugi...
]
James Wilson commented on JBIDE-10756:
--------------------------------------
Thanks Rob. I was sure I'd done it the right way but I was wrong; I deleted and
completely re-created my server using the option from "JBoss Community" branch
and it works how I'm used to.
Thanks so much for helping me and sorry to have wasted your time.
Debug button attempts to start already running server, reports port
in use
--------------------------------------------------------------------------
Key: JBIDE-10756
URL: https://issues.jboss.org/browse/JBIDE-10756
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Indigo (Win XP)
Reporter: James Wilson
Assignee: Rob Stryker
Priority: Optional
Attachments: JBIDE-10756-screenshot.png, JBIDE-10756-server_settings.png
I've added a JBoss AS (4.2) server to the Servers view. I select it and then press
the "Start the server in debug mode" button on the Servers view toolbar. When I
want to run my application I usually click on the Debug button on the main Eclipse
toolbar, which launches the last configuration run. In my Ganymede setup (so I think JBoss
Tools 3.0) that didn't include starting the JBoss AS server, but in Indigo/JBoss Tools
3.3 (M5) it does. Thus the tooltip for the debug button becomes "Debug JBoss v4.2 at
localhost (already running)", and if I click on it I get a message box stating:
'Launching JBoss v4.2 at localhost' has encountered a problem.
Server port In Ue 80080-Http
In the Servers view my JBoss 4.2 AS server then shows as stopped. I can start it again
and it all works fine after that.
--
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
10:39 a.m.
[
https://issues.jboss.org/browse/JBIDE-10756?page=com.atlassian.jira.plugi...
]
James Wilson resolved JBIDE-10756.
----------------------------------
Labels: error user (was: )
Resolution: Rejected
Debug button attempts to start already running server, reports port
in use
--------------------------------------------------------------------------
Key: JBIDE-10756
URL: https://issues.jboss.org/browse/JBIDE-10756
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Indigo (Win XP)
Reporter: James Wilson
Assignee: Rob Stryker
Priority: Optional
Labels: error, user
Attachments: JBIDE-10756-screenshot.png, JBIDE-10756-server_settings.png
I've added a JBoss AS (4.2) server to the Servers view. I select it and then press
the "Start the server in debug mode" button on the Servers view toolbar. When I
want to run my application I usually click on the Debug button on the main Eclipse
toolbar, which launches the last configuration run. In my Ganymede setup (so I think JBoss
Tools 3.0) that didn't include starting the JBoss AS server, but in Indigo/JBoss Tools
3.3 (M5) it does. Thus the tooltip for the debug button becomes "Debug JBoss v4.2 at
localhost (already running)", and if I click on it I get a message box stating:
'Launching JBoss v4.2 at localhost' has encountered a problem.
Server port In Ue 80080-Http
In the Servers view my JBoss 4.2 AS server then shows as stopped. I can start it again
and it all works fine after that.
--
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
4533
days inactive
4534
days old
jbosstools-issues@lists.jboss.org
11 comments
3 participants
participants (3)
-
James Wilson (JIRA) -
Max Rydahl Andersen (JIRA)
-
Rob Stryker (JIRA)