Bug 780137 (SOA-2508) - Creating Modeshape server in JBDS 4.0 beta1 - intermittent problem where error raised regarding existing user "admin"
Summary: Creating Modeshape server in JBDS 4.0 beta1 - intermittent problem where erro...
Keywords:
Status: CLOSED NOTABUG
Alias: SOA-2508
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: EDS
Version: 5.1.0.ER3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Van Halbert
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-28 02:34 UTC by Len DiMaggio
Modified: 2010-11-02 03:12 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
SOA-P 5.1 ER3 build Version: 4.0.0.Beta1 Build id: v201010052359R
Last Closed: 2010-11-02 03:12:50 UTC
Type: Bug


Attachments (Terms of Use)
Screenshot-user-admin.png (199.22 KB, image/png)
2010-10-28 02:35 UTC, Len DiMaggio
no flags Details


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

Description Len DiMaggio 2010-10-28 02:34:48 UTC
project_key: SOA

This problem is being seen - but it is not reproducible - it's possible to hit a situation where after a project has been published to a Modeshape server, subsequent attempts to access or create a server result in an error indicating that the server cannot be created as the user admin already exists. See attached screen shot.

Will attach a .log file the next time the issue is seen.

Comment 1 Len DiMaggio 2010-10-28 02:35:46 UTC
Attachment: Added: Screenshot-user-admin.png


Comment 2 Van Halbert 2010-10-28 02:39:24 UTC
Link: Added: This issue depends MODE-988


Comment 3 Len DiMaggio 2010-10-28 02:41:35 UTC
Link: Added: This issue is a dependency of JBDS-1388


Comment 4 Anne-Louise Tangring 2010-10-28 16:18:55 UTC
Investigate for 5.1.0, if they should be in SOA 5.1.0, Van will set the Fixed Version.

Comment 5 Dan Florian 2010-10-29 21:30:13 UTC
The URL in the screen shot is wrong. It should not have the "repository" at the end of it. URLs should end in "modeshape-rest." With that said, it looks like you will get there error any time a ModeShape server is defined but can't be connected to. I think a good solution would be to only have servers that can be connected to show up in the publish dialog.

Comment 6 Van Halbert 2010-11-02 03:12:50 UTC
According to the engineer, the problem seen is what is suppose to happen when a new modeshape server is trying to be created when it already exists.     If there is a usability issue here, then there needs to be recommendations as to what should happen.


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