Bug 778398 (SOA-882) - Enterprise console - seeing exception trying to connect to SOA-P server after restarting JON server + agent
Summary: Enterprise console - seeing exception trying to connect to SOA-P server after...
Keywords:
Status: CLOSED WORKSFORME
Alias: SOA-882
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Monitoring and Management
Version: 4.3 IR5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: JON
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-26 18:49 UTC by Len DiMaggio
Modified: 2009-02-13 14:27 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-02-13 14:27:08 UTC
Type: Bug


Attachments (Terms of Use)
BUG_connection_properties.zip (256.58 KB, application/zip)
2008-10-02 12:47 UTC, Burr Sutter
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-882 0 None None None Never

Description Len DiMaggio 2008-09-26 18:49:26 UTC
Date of First Response: 2008-10-02 08:47:51
project_key: SOA

Platform JIRA for project JIRA:  JBNADM-3531

Comment 1 Len DiMaggio 2008-09-26 18:49:36 UTC
Link: Added: This issue depends JBNADM-3531


Comment 2 Len DiMaggio 2008-10-01 12:21:54 UTC
Nonreproducible, change fixed-in to CONTINUING

Comment 3 Len DiMaggio 2008-10-01 18:52:54 UTC
Removed "Not Easily Reproducible" component.

I'm seeing JBNADM-3524 every time a new server is set up.

I'm seeing JBNADM-3531 every time the server and agent are both restarted. Restarting the server alone does not cause this problem.

The same workaround - pressing back/forward in the browser gets the user past the problem.

This is with JON build 6470 and SOA-P IR5. 

Comment 4 Len DiMaggio 2008-10-01 20:26:25 UTC
My mistake - JBNADM-3531 is still not 100% reproducible at will. 

Comment 5 Burr Sutter 2008-10-02 12:47:51 UTC
I've attached my log, stack trace, screenshots related to this issue.  Normally a couple of visits to the connection properties page and eventually clears it up.

Comment 6 Burr Sutter 2008-10-02 12:47:51 UTC
Attachment: Added: BUG_connection_properties.zip


Comment 7 Len DiMaggio 2008-10-03 02:49:23 UTC
I'm unable to recreate the problem with this build of the server + agent:

http://jon01.qa.atl2.redhat.com:8042/dist/qa/jon-agent-2.1.0.CR1.zip
http://jon01.qa.atl2.redhat.com:8042/dist/qa/jon-server-2.1.0.CR1.zip



Comment 8 Len DiMaggio 2009-02-13 14:27:08 UTC
Cannot reproduce problem with JON 2.1 bits


Note You need to log in before you can comment on or make changes to this bug.