[JBoss JIRA] (JBIDE-16133) No indication that management authentication fails
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16133?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-16133:
----------------------------------------
Assignee: Rob Stryker (was: Max Rydahl Andersen)
> No indication that management authentication fails
> --------------------------------------------------
>
> Key: JBIDE-16133
> URL: https://issues.jboss.org/browse/JBIDE-16133
> Project: Tools (JBoss Tools)
> Issue Type: Quality Risk
> Components: server
> Reporter: Steven Hawkins
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.1.1.CR1
>
>
> Running Developer Studio 7.1.0.CR1 and using either the server auto-detection or manually defining a server and using an incorrect management password results in a console log entry:
> 14:00:54,966 ERROR [org.jboss.remoting.remote.connection] (Remoting "..." read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer
> On server startup without any indication of what it means.
--
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, 4 months
[JBoss JIRA] (JBIDE-16133) No indication that management authentication fails
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16133?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-16133:
----------------------------------------
Fix Version/s: 4.1.1.CR1
> No indication that management authentication fails
> --------------------------------------------------
>
> Key: JBIDE-16133
> URL: https://issues.jboss.org/browse/JBIDE-16133
> Project: Tools (JBoss Tools)
> Issue Type: Quality Risk
> Components: server
> Reporter: Steven Hawkins
> Fix For: 4.1.1.CR1
>
>
> Running Developer Studio 7.1.0.CR1 and using either the server auto-detection or manually defining a server and using an incorrect management password results in a console log entry:
> 14:00:54,966 ERROR [org.jboss.remoting.remote.connection] (Remoting "..." read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer
> On server startup without any indication of what it means.
--
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, 4 months
[JBoss JIRA] (JBIDE-15622) Automatically open/send report when log has error
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15622?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-15622:
----------------------------------
Description:
Step 1:
!ReportError1.png!
Step 2:
!ReportBugStep2.png!
Step 3:
!ReportBugStep3.png!
!ReportBugStep3SourceView.png!
*Where to:*
1. Error Dialog (Steps 1,2,3) – when problem occurs Error Dialog appears and provides opportunity to report a bug
2. Error Log View (Steps 2,3) (Tool-bar, Menu, Context menu) – report problem for selected stack-trace
3. Help->Report Problem Dialog (Steps 2,3) – report problem which may be not related with any exceptions
1. We should filter this dialog appearance by Severity, by Existence (local in log file and remote in JIRA), by Time (not often then one time in a minute, in case of crash where could be a lot of exceptions in short period of time). Offer automatic send report?
1. and 2. should create issues in “special” project (see Preconditions). 3. may create issues directly to project Tools (JBoss Tools)?
*Feature list:*
1. Log in/Anonymous bug reporting (If the user has login to JIRA he can report issues with it. Or he can do it anonymously)
2. Check Exception Stack-trace for duplicate
3. Report should contain all needed (useful) information about user's environment (JDK/JRE version, eclipse version, OS version, configuration, etc)
4. As much as possible fields should be filled up automatically (project, issue type, priority, component/s, affects version/s, environment) may be some of them should be filled up later by Administrator
5. User should be able to see all the data he is going to send (see tab "Source View")
6. Show communication errors
7. Return link to created JIRA
8. Inform user about the general/common process of bug reporting (see Work-flow)
9. Option to attach log file
10. Option to attach screen-shot
*Preconditions:*
1. We need to create “special” project in JIRA to primary report issue to with anonymous (or dedicated) user.
2. We need person as Administrator (QE-?) to periodically verifying issue from “special” project.
*Work-flow:*
1. User decides/agrees to report the problem (see list Where to)
2. Report Problem dialog appears, user fills up the form
2. Dialog checks for existing exception stack-traces (when stack-trace available) or by key-words from field summary.
3. If validation passes dialog creates issue in “special” project of JIRA (see Preconditions)
4. User gets link to created issue and short description of what will happen next. (features 7. 8.)
5. Administrator should periodically check “special” project and verify all issues. Administrator may reject issue or correct (versions, components etc, if needed) and move to project Tools (JBoss Tools).
*Primary Description:*
JBT should set up an ILogListener on the Eclipse log and send an error report whenever something is logged as error.
As it's probably not possible to send the error report without asking users, it should show the "Report problem" page.
NetBeans does that and has reported an actual quality benefit.
was:
Step 1:
!ReportError1.png!
Step 2:
!ReportBugStep2.png!
Step 3:
!ReportBugStep3.png!
!ReportBugStep3SourceView.png!
*Where to:*
1. Error Dialog (Steps 1,2,3) – when problem occurs Error Dialog appears and provides opportunity to report a bug
2. Error Log View (Steps 2,3) (Tool-bar, Menu, Context menu) – report problem for selected stack-trace
3. Help->Report Problem Dialog (Steps 2,3) – report problem which may be not related with any exceptions
1. We should filter this dialog appearance by Severity, by Existence (local in log file and remote in JIRA), by Time (not often then one time in a minute, in case of crash where could be a lot of exceptions in short period of time). Offer automatic send report?
1. and 2. should create issues in “special” project (see Preconditions). 3. may create issues directly to project Tools (JBoss Tools)?
*Feature list:*
1. Log in/Anonymous bug reporting (If the user has login to JIRA he can report issues with it. Or he can do it anonymously)
2. Check Exception Stack-trace for duplicate
3. Report should contain all needed (useful) information about user's environment (JDK/JRE version, eclipse version, OS version, configuration, etc)
4. As much as possible fields should be filled up automatically (project, issue type, priority, component/s, affects version/s, environment) may be some of them should be filled up later by Administrator
5. User should be able to see all the data he is going to send
6. Show communication errors
7. Return link to created JIRA
8. Inform user about the general/common process of bug reporting (see Work-flow)
9. Option to attach log file
10. Option to attach screen-shot
*Preconditions:*
1. We need to create “special” project in JIRA to primary report issue to with anonymous (or dedicated) user.
2. We need person as Administrator (QE-?) to periodically verifying issue from “special” project.
*Work-flow:*
1. User decides/agrees to report the problem (see list Where to)
2. Report Problem dialog appears, user fills up the form
2. Dialog checks for existing exception stack-traces (when stack-trace available) or by key-words from field summary.
3. If validation passes dialog creates issue in “special” project of JIRA (see Preconditions)
4. User gets link to created issue and short description of what will happen next. (features 7. 8.)
5. Administrator should periodically check “special” project and verify all issues. Administrator may reject issue or correct (versions, components etc, if needed) and move to project Tools (JBoss Tools).
*Primary Description:*
JBT should set up an ILogListener on the Eclipse log and send an error report whenever something is logged as error.
As it's probably not possible to send the error report without asking users, it should show the "Report problem" page.
NetBeans does that and has reported an actual quality benefit.
> Automatically open/send report when log has error
> -------------------------------------------------
>
> Key: JBIDE-15622
> URL: https://issues.jboss.org/browse/JBIDE-15622
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Affects Versions: 4.1.1.Alpha1
> Reporter: Mickael Istria
> Attachments: ReportBugStep2.bmml, ReportBugStep2.bmml, ReportBugStep2.png, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.png, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.png, ReportError1.bmml, ReportError1.bmml, ReportError1.png
>
>
> Step 1:
> !ReportError1.png!
> Step 2:
> !ReportBugStep2.png!
> Step 3:
> !ReportBugStep3.png!
> !ReportBugStep3SourceView.png!
> *Where to:*
> 1. Error Dialog (Steps 1,2,3) – when problem occurs Error Dialog appears and provides opportunity to report a bug
> 2. Error Log View (Steps 2,3) (Tool-bar, Menu, Context menu) – report problem for selected stack-trace
> 3. Help->Report Problem Dialog (Steps 2,3) – report problem which may be not related with any exceptions
> 1. We should filter this dialog appearance by Severity, by Existence (local in log file and remote in JIRA), by Time (not often then one time in a minute, in case of crash where could be a lot of exceptions in short period of time). Offer automatic send report?
> 1. and 2. should create issues in “special” project (see Preconditions). 3. may create issues directly to project Tools (JBoss Tools)?
> *Feature list:*
> 1. Log in/Anonymous bug reporting (If the user has login to JIRA he can report issues with it. Or he can do it anonymously)
> 2. Check Exception Stack-trace for duplicate
> 3. Report should contain all needed (useful) information about user's environment (JDK/JRE version, eclipse version, OS version, configuration, etc)
> 4. As much as possible fields should be filled up automatically (project, issue type, priority, component/s, affects version/s, environment) may be some of them should be filled up later by Administrator
> 5. User should be able to see all the data he is going to send (see tab "Source View")
> 6. Show communication errors
> 7. Return link to created JIRA
> 8. Inform user about the general/common process of bug reporting (see Work-flow)
> 9. Option to attach log file
> 10. Option to attach screen-shot
> *Preconditions:*
> 1. We need to create “special” project in JIRA to primary report issue to with anonymous (or dedicated) user.
> 2. We need person as Administrator (QE-?) to periodically verifying issue from “special” project.
> *Work-flow:*
> 1. User decides/agrees to report the problem (see list Where to)
> 2. Report Problem dialog appears, user fills up the form
> 2. Dialog checks for existing exception stack-traces (when stack-trace available) or by key-words from field summary.
> 3. If validation passes dialog creates issue in “special” project of JIRA (see Preconditions)
> 4. User gets link to created issue and short description of what will happen next. (features 7. 8.)
> 5. Administrator should periodically check “special” project and verify all issues. Administrator may reject issue or correct (versions, components etc, if needed) and move to project Tools (JBoss Tools).
> *Primary Description:*
> JBT should set up an ILogListener on the Eclipse log and send an error report whenever something is logged as error.
> As it's probably not possible to send the error report without asking users, it should show the "Report problem" page.
> NetBeans does that and has reported an actual quality benefit.
--
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, 4 months
[JBoss JIRA] (JBIDE-15622) Automatically open/send report when log has error
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15622?page=com.atlassian.jira.plugi... ]
Daniel Azarov edited comment on JBIDE-15622 at 11/27/13 11:50 AM:
------------------------------------------------------------------
{quote}
** page needs a link to create a Jira account if user doesn't have one.
** page should be the last page (to avoid getting back if credentials aren't correct, which happens often with passwords)
{quote}
OK
{quote}
*I don't see the value of the "Source view" for the issue. Why not sticking just to the form?
{quote}
Form has hidden fields. But User should be able to see all the data he is going to send. All fields should be visible in tab Source View and I think this tab should be read-only.
was (Author: dazarov):
{quote}
** page needs a link to create a Jira account if user doesn't have one.
** page should be the last page (to avoid getting back if credentials aren't correct, which happens often with passwords)
{quote}
OK
{quote}
*I don't see the value of the "Source view" for the issue. Why not sticking just to the form?
{quote}
Form has hidden fields. But User should be able to see all the data he is going to send. All fields should be visible in Source View and I think this view should be read-only.
> Automatically open/send report when log has error
> -------------------------------------------------
>
> Key: JBIDE-15622
> URL: https://issues.jboss.org/browse/JBIDE-15622
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Affects Versions: 4.1.1.Alpha1
> Reporter: Mickael Istria
> Attachments: ReportBugStep2.bmml, ReportBugStep2.bmml, ReportBugStep2.png, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.png, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.png, ReportError1.bmml, ReportError1.bmml, ReportError1.png
>
>
> Step 1:
> !ReportError1.png!
> Step 2:
> !ReportBugStep2.png!
> Step 3:
> !ReportBugStep3.png!
> !ReportBugStep3SourceView.png!
> *Where to:*
> 1. Error Dialog (Steps 1,2,3) – when problem occurs Error Dialog appears and provides opportunity to report a bug
> 2. Error Log View (Steps 2,3) (Tool-bar, Menu, Context menu) – report problem for selected stack-trace
> 3. Help->Report Problem Dialog (Steps 2,3) – report problem which may be not related with any exceptions
> 1. We should filter this dialog appearance by Severity, by Existence (local in log file and remote in JIRA), by Time (not often then one time in a minute, in case of crash where could be a lot of exceptions in short period of time). Offer automatic send report?
> 1. and 2. should create issues in “special” project (see Preconditions). 3. may create issues directly to project Tools (JBoss Tools)?
> *Feature list:*
> 1. Log in/Anonymous bug reporting (If the user has login to JIRA he can report issues with it. Or he can do it anonymously)
> 2. Check Exception Stack-trace for duplicate
> 3. Report should contain all needed (useful) information about user's environment (JDK/JRE version, eclipse version, OS version, configuration, etc)
> 4. As much as possible fields should be filled up automatically (project, issue type, priority, component/s, affects version/s, environment) may be some of them should be filled up later by Administrator
> 5. User should be able to see all the data he is going to send (see tab "Source View")
> 6. Show communication errors
> 7. Return link to created JIRA
> 8. Inform user about the general/common process of bug reporting (see Work-flow)
> 9. Option to attach log file
> 10. Option to attach screen-shot
> *Preconditions:*
> 1. We need to create “special” project in JIRA to primary report issue to with anonymous (or dedicated) user.
> 2. We need person as Administrator (QE-?) to periodically verifying issue from “special” project.
> *Work-flow:*
> 1. User decides/agrees to report the problem (see list Where to)
> 2. Report Problem dialog appears, user fills up the form
> 2. Dialog checks for existing exception stack-traces (when stack-trace available) or by key-words from field summary.
> 3. If validation passes dialog creates issue in “special” project of JIRA (see Preconditions)
> 4. User gets link to created issue and short description of what will happen next. (features 7. 8.)
> 5. Administrator should periodically check “special” project and verify all issues. Administrator may reject issue or correct (versions, components etc, if needed) and move to project Tools (JBoss Tools).
> *Primary Description:*
> JBT should set up an ILogListener on the Eclipse log and send an error report whenever something is logged as error.
> As it's probably not possible to send the error report without asking users, it should show the "Report problem" page.
> NetBeans does that and has reported an actual quality benefit.
--
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, 4 months
[JBoss JIRA] (JBIDE-15622) Automatically open/send report when log has error
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15622?page=com.atlassian.jira.plugi... ]
Daniel Azarov commented on JBIDE-15622:
---------------------------------------
{quote}
** page needs a link to create a Jira account if user doesn't have one.
** page should be the last page (to avoid getting back if credentials aren't correct, which happens often with passwords)
{quote}
OK
{quote}
*I don't see the value of the "Source view" for the issue. Why not sticking just to the form?
{quote}
Form has hidden fields. But User should be able to see all the data he is going to send. All fields should be visible in Source View and I think this view should be read-only.
> Automatically open/send report when log has error
> -------------------------------------------------
>
> Key: JBIDE-15622
> URL: https://issues.jboss.org/browse/JBIDE-15622
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Affects Versions: 4.1.1.Alpha1
> Reporter: Mickael Istria
> Attachments: ReportBugStep2.bmml, ReportBugStep2.bmml, ReportBugStep2.png, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.png, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.png, ReportError1.bmml, ReportError1.bmml, ReportError1.png
>
>
> Step 1:
> !ReportError1.png!
> Step 2:
> !ReportBugStep2.png!
> Step 3:
> !ReportBugStep3.png!
> !ReportBugStep3SourceView.png!
> *Where to:*
> 1. Error Dialog (Steps 1,2,3) – when problem occurs Error Dialog appears and provides opportunity to report a bug
> 2. Error Log View (Steps 2,3) (Tool-bar, Menu, Context menu) – report problem for selected stack-trace
> 3. Help->Report Problem Dialog (Steps 2,3) – report problem which may be not related with any exceptions
> 1. We should filter this dialog appearance by Severity, by Existence (local in log file and remote in JIRA), by Time (not often then one time in a minute, in case of crash where could be a lot of exceptions in short period of time). Offer automatic send report?
> 1. and 2. should create issues in “special” project (see Preconditions). 3. may create issues directly to project Tools (JBoss Tools)?
> *Feature list:*
> 1. Log in/Anonymous bug reporting (If the user has login to JIRA he can report issues with it. Or he can do it anonymously)
> 2. Check Exception Stack-trace for duplicate
> 3. Report should contain all needed (useful) information about user's environment (JDK/JRE version, eclipse version, OS version, configuration, etc)
> 4. As much as possible fields should be filled up automatically (project, issue type, priority, component/s, affects version/s, environment) may be some of them should be filled up later by Administrator
> 5. User should be able to see all the data he is going to send
> 6. Show communication errors
> 7. Return link to created JIRA
> 8. Inform user about the general/common process of bug reporting (see Work-flow)
> 9. Option to attach log file
> 10. Option to attach screen-shot
> *Preconditions:*
> 1. We need to create “special” project in JIRA to primary report issue to with anonymous (or dedicated) user.
> 2. We need person as Administrator (QE-?) to periodically verifying issue from “special” project.
> *Work-flow:*
> 1. User decides/agrees to report the problem (see list Where to)
> 2. Report Problem dialog appears, user fills up the form
> 2. Dialog checks for existing exception stack-traces (when stack-trace available) or by key-words from field summary.
> 3. If validation passes dialog creates issue in “special” project of JIRA (see Preconditions)
> 4. User gets link to created issue and short description of what will happen next. (features 7. 8.)
> 5. Administrator should periodically check “special” project and verify all issues. Administrator may reject issue or correct (versions, components etc, if needed) and move to project Tools (JBoss Tools).
> *Primary Description:*
> JBT should set up an ILogListener on the Eclipse log and send an error report whenever something is logged as error.
> As it's probably not possible to send the error report without asking users, it should show the "Report problem" page.
> NetBeans does that and has reported an actual quality benefit.
--
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, 4 months
[JBoss JIRA] (JBIDE-16093) NPEs when compiling wildfly codebase
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16093?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-16093:
---------------------------------------
{quote}
We should have Zero validators running on all projects by default - that is a massive no no so this change is definitely important.
{quote}
Now, the Arquillian validator isn't run by default.
However, a lot of WTP validators, JBT validators/builders will be run because the JBoss Maven integration calls JSF, JPA, JAX-RS, CDI, Hibernate ... configurators by default.
{quote}
Do we have a way to enable arquillian without forcing updates to pom.xml and other files that already is setup for existing projects with arquillian ?
{quote}
The "Add Arquillian support" changes only pom.xml and .project.
I can add the "Update the pom.xml file" checkbox to the "Add Arquillian support" action by which a user will be able to enable/disable updating pom.xml.
Do you agree?
> NPEs when compiling wildfly codebase
> ------------------------------------
>
> Key: JBIDE-16093
> URL: https://issues.jboss.org/browse/JBIDE-16093
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.1.CR1
> Reporter: Andre Dietisheim
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Labels: respin-b
> Fix For: 4.1.1.CR1, 4.2.0.Alpha1
>
> Attachments: .log, npes-building-wildfly-2.png, npes-building-wildfly.png
>
>
> When having arquillian org.jboss.tools.arquillian.core_1.0.5.CR1-v20131116-1823-B79 installed and building the wildfly workspace I run into several NPEs caused by arquillian.
> !npes-building-wildfly.png!
> !npes-building-wildfly-2.png!
--
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, 4 months
[JBoss JIRA] (JBIDE-16133) No indication that management authentication fails
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16133?page=com.atlassian.jira.plugi... ]
Steven Hawkins commented on JBIDE-16133:
----------------------------------------
> what are the steps you do ?
>From the servers view create a server or select an existing one. Set the "Management Login Credentials" to an invalid name/password combo. Then perform any operation that uses a management command. The log will accumulate the entry shown above with each operation without any indication to the user that the connection is not authenticating. See the related bz entries as well.
> what did expect to see/what did you get in past ?
Don't know about the past, but I would expect to see something to the affect that I have a bad management password. If it matters what action/tool (if it's likely something being swallowed/mishandled higher up), then this can be moved. Barry Lafond thought is was applicable at this level.
> No indication that management authentication fails
> --------------------------------------------------
>
> Key: JBIDE-16133
> URL: https://issues.jboss.org/browse/JBIDE-16133
> Project: Tools (JBoss Tools)
> Issue Type: Quality Risk
> Components: server
> Reporter: Steven Hawkins
>
> Running Developer Studio 7.1.0.CR1 and using either the server auto-detection or manually defining a server and using an incorrect management password results in a console log entry:
> 14:00:54,966 ERROR [org.jboss.remoting.remote.connection] (Remoting "..." read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer
> On server startup without any indication of what it means.
--
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, 4 months