[JBoss JIRA] (JBDS-2643) Problem switching between Console and Error log view when server's running
by Tomas Remes (JIRA)
[ https://issues.jboss.org/browse/JBDS-2643?page=com.atlassian.jira.plugin.... ]
Tomas Remes updated JBDS-2643:
------------------------------
Attachment: error.log
Attaching error log
> Problem switching between Console and Error log view when server's running
> --------------------------------------------------------------------------
>
> Key: JBDS-2643
> URL: https://issues.jboss.org/browse/JBDS-2643
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 7.0.0.Beta1
> Reporter: Tomas Remes
> Attachments: error.log
>
>
> There is no way how to close Error log view or switch to Console view when they are both open and EAP 6.1 server is running. The behavior is really weird. It doesn't matter on active perspective. Reproducible by following steps:
> 1. Show Console View.
> 2. Show Error log view.
> 3. Create runtime for EAP 6.1
> 4. Start server.
> 5. Switch to Error log view.
> 6. Try to switch back to Console view.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBDS-2643) Problem switching between Console and Error log view when server's running
by Tomas Remes (JIRA)
Tomas Remes created JBDS-2643:
---------------------------------
Summary: Problem switching between Console and Error log view when server's running
Key: JBDS-2643
URL: https://issues.jboss.org/browse/JBDS-2643
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 7.0.0.Beta1
Reporter: Tomas Remes
There is no way how to close Error log view or switch to Console view when they are both open and EAP 6.1 server is running. The behavior is really weird. It doesn't matter on active perspective. Reproducible by following steps:
1. Show Console View.
2. Show Error log view.
3. Create runtime for EAP 6.1
4. Start server.
5. Switch to Error log view.
6. Try to switch back to Console view.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBIDE-14568) Cannot start EAP 6.1 on MacOSX with default JDK 6
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14568?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-14568.
---------------------------------
Fix Version/s: 4.1.0.Beta1
Resolution: Done
this made it into beta1
> Cannot start EAP 6.1 on MacOSX with default JDK 6
> -------------------------------------------------
>
> Key: JBIDE-14568
> URL: https://issues.jboss.org/browse/JBIDE-14568
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.Beta1
> Environment: MacOSX with JDK 6 configured in JBDS 7.Beta1
> Reporter: Xavier Coulon
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.1.0.Beta1
>
> Attachments: java6.txt, Screen Shot 2013-05-22 at 9.47.22 AM.png
>
>
> I created a server adapter (tech preview) for JBoss EAP 6.1 using the wizard.
> When I try to start it from the Servers View, I get an error dialog with the following message:
> "The following server requires a JDK to run properly: JBoss EAP 6.1 Runtime Server"
> If I edit the Runtime Environment for this server, I get a dialog with the following warning:
> "This runtime type requires a JDK for launching a server. We cannot guarantee the default virtual machine for this execution environment is a JDK." while the selected JRE is "Default JRE for JavaSE-1.6". If I switch to "Java SE 6 (MacosX default)" which is the only Java Runtime I configured in JBDS, I get the same error message as above.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBIDE-14658) Management poller too slow for synchronous polling, should be disabled
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-14658:
-----------------------------------
Summary: Management poller too slow for synchronous polling, should be disabled
Key: JBIDE-14658
URL: https://issues.jboss.org/browse/JBIDE-14658
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.1.0.Beta1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.1.0.Beta2
The management poller has a timeout of 5000 ms deep in the app server client jar code. I haven't figured out how to isolate it yet, or to change the timeout value, and so until that can be done, it'd be better to ensure that the management poller is disabled for synchronous calls when the server is likely down (ie during a 'startup' call) until that can be figured out.
This would have the effect of the web port poller being used for such synchronous calls. This could be reversed once sufficient api was discovered / added to control the timeouts.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (TOOLSDOC-342) NeedInfo: Questions about the servlet window in new JSF project wizard
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-342?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-342:
-------------------------------------
Attachment: JSF_Servletversion2.png
> NeedInfo: Questions about the servlet window in new JSF project wizard
> ----------------------------------------------------------------------
>
> Key: TOOLSDOC-342
> URL: https://issues.jboss.org/browse/TOOLSDOC-342
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: User Guide - JSF Tools
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Alexey Kazakov
> Fix For: 4.1.0
>
> Attachments: JSF_Servletversion2.png
>
>
> In the new JSF project wizard, the second window requires information about Servlets and Servers (screen capture attached).
> So that I can correctly document it for users, I have the following questions:
> * Is 'ServletVersion' linked to the JSF version a user chooses? Or are they completely independent?
> * What is 'context path'?
> * What is the difference between 'runtime' and 'target server'?
> Thanks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (TOOLSDOC-342) NeedInfo: Questions about the servlet window in new JSF project wizard
by Michelle Murray (JIRA)
Michelle Murray created TOOLSDOC-342:
----------------------------------------
Summary: NeedInfo: Questions about the servlet window in new JSF project wizard
Key: TOOLSDOC-342
URL: https://issues.jboss.org/browse/TOOLSDOC-342
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Task
Security Level: Public (Everyone can see)
Components: User Guide - JSF Tools
Affects Versions: 4.1.0
Reporter: Michelle Murray
Assignee: Alexey Kazakov
Fix For: 4.1.0
In the new JSF project wizard, the second window requires information about Servlets and Servers (screen capture attached).
So that I can correctly document it for users, I have the following questions:
* Is 'ServletVersion' linked to the JSF version a user chooses? Or are they completely independent?
* What is 'context path'?
* What is the difference between 'runtime' and 'target server'?
Thanks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months