[JBoss JIRA] (JBIDE-11514) AS6 run on server for war or ear-inside-war does not load browser fast
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-11514:
-----------------------------------
Summary: AS6 run on server for war or ear-inside-war does not load browser fast
Key: JBIDE-11514
URL: https://issues.jboss.org/browse/JBIDE-11514
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.3.0.Beta3
AS6 does not seem to have the mbeans as5 and below do for determining if a module is started or not. This means that attempts to poll via jmx to decide when to open the browser take the full timeout of 20 seconds.
Without a way to decide if the module is started or not, we have to hard-code a delay time. There is no easy answer here. If we go too quickly, the user will get 404. If we delay too long, the user will wait a long time to see the change.
--
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, 9 months
[JBoss JIRA] (JBIDE-11872) Auto-connection to jmx after rse server start leaves threads hanging around
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-11872:
-----------------------------------
Summary: Auto-connection to jmx after rse server start leaves threads hanging around
Key: JBIDE-11872
URL: https://issues.jboss.org/browse/JBIDE-11872
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.3.0.CR1
Because of the way the as7.1 mbean connector loads the client jar direct from the server installation, the auto-connection to jmx does not benefit from the remoting upgrade committed by JBIDE-11871. The client jar for a 7.1.0 installation, for example, will still use remoting 3.2.2 rather than the astools-bundled 3.2.7.
Possible solutions are prevent auto-connection of jmx or somehow force the 3.2.7 remoting jar onto the classpath before the as7.1.0 client jar to ensure 3.2.7 classes take precedence.
--
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, 9 months
[JBoss JIRA] (JBIDE-11854) AS7 management port not always detected correctly
by Martin Malina (JIRA)
Martin Malina created JBIDE-11854:
-------------------------------------
Summary: AS7 management port not always detected correctly
Key: JBIDE-11854
URL: https://issues.jboss.org/browse/JBIDE-11854
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Environment: jbdevstudio-product-universal-5.0.0.v201205101833M-H138-Beta3.jar
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 3.3.0.CR1
Sometimes when you change the management port in standalone.xml in your AS7 server, the changes doesn't get reflected in JBT tooling. Perhaps something to do with caching?
Important side question: Is the management port (in server editor) detected everytime you start the server? If only in the time of adding the server, then the UI should be different. But this JIRA is relevant anyway.
--
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, 9 months
[JBoss JIRA] (JBIDE-10930) For EAR projects, Run As > Run on Server should open the 1st webapp using the context root in application.xml
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-10930:
-----------------------------------
Summary: For EAR projects, Run As > Run on Server should open the 1st webapp using the context root in application.xml
Key: JBIDE-10930
URL: https://issues.jboss.org/browse/JBIDE-10930
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Reporter: Fred Bricon
Assignee: Rob Stryker
Attachments: non.default.context.root.zip
For EAR projects, Run As > Run on Server opens the webapp url using the context root defined on the webapp project, not the value of the context root in application.xml, which obviously leads to a 404 error page.
{quote}
(09:53:24) rawbdor: fbricon, EarArtifactAdapter
(09:53:36) rawbdor: takes the first web project in the ear
(09:53:48) rawbdor: and simply returns whatever the web artifact adapter would do for that app
{quote}
When lauching, we could maybe use a IModuleArtifact decorator that provides the correct url to be opened in the browser?
--
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, 9 months