Bug 478098 - MIGRATED_FROM_JIRA: Server and Studio is out of sync when editing mappings
MIGRATED_FROM_JIRA: Server and Studio is out of sync when editing mappings
Product: penrose
Classification: Retired
Component: Studio (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Endi Sukma Dewata
Ben Levenson
Depends On:
Blocks: 471500
  Show dependency treegraph
Reported: 2008-12-27 02:59 EST by Chandrasekar Kannan
Modified: 2018-02-07 15:45 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Chandrasekar Kannan 2008-12-27 02:59:01 EST
I was editing my mapping and source definitions and made a few errors. I corrected them and resaved the configuration to Penrose; however, when I selected preview, the preview browser would sometimes not open. I restarted the server and checked the logs and noticed the error below. I also noticed an error earlier in my logs stating a source name was invalid. That source name did not exist in my penrose studio configuration - I had renamed it previously to a new name. Ultimately, I had to delete my configuration files and revert back to the defaults and then reimport my configuration on the studio side from a local backup to get the server working correctly again.

Two areas where I was making changes: renamed a database connection source, modifying mapping expressions. I had made numerous changes always saving the change each time and previewing it in the browser.

Discussion thread: http://groups.google.com/group/safehaus/browse_thread/thread/1ce6572860c91b25/9c220cd88c4fddff#9c220cd88c4fddff

Exception in thread "main" bsh.TokenMgrError: Lexical error at line 4, 
column 31.  Encountered: "i" (105), after : "'d" 
        at bsh.ParserTokenManager.getNextToken(Unknown Source) 
        at bsh.Parser.getNextToken(Unknown Source) 
Comment 1 Chandrasekar Kannan 2008-12-27 02:59:03 EST
Marking bug as MODIFIED as it was already resolved in Jira - PENROSE-109

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