Web Client (Ajax) Release Candidate 5 Questions

6 views
Skip to first unread message

bodie0293

unread,
Dec 18, 2008, 1:30:16 PM12/18/08
to i2b2
Hi,

Is anyone using the RC5 Web Client? I installed it locally and tried
running against the i2b2.org host, and received the message: "The
message from the PM Cell was corrupted in transport. Try again".

I then installed the RC5 VMWare image, and ran the Web Client (locally
in the VM Image), and connected to localhost. This connected
successfully, but is having trouble reading the Ontology.
In this case, I get a series of messages that state the "xxx cell's
message could not be interpreted as valid xml".

Paul Ranauro
UMass Medical

ELI

unread,
Dec 19, 2008, 11:14:57 AM12/19/08
to i2b2
Paul -

We installed RC5 from source on RH Linux. We got the client up and
running with little or no trouble. Initially we were getting the
"corruped in transport" message as well. Make sure the
i2b2_config_data.js is configured correctly (the RC5 release takes
advantage of pointing to multiple projects per domain - if you have it
configured for RC4 where it only pointed to 1 project which was
preset, you may have problems). Because we're dealing with the client
level, pages are cached so if you make any changes to the client code,
you'll need to delete/clear your cache. I learned that the hard way
after an hour of banging my head, wondering why my changes weren't
being implemented.

Also, it may be worth your while to review the tomcat/jboss/ or even
apache logs to help troubleshoot. This has been a tremendous help to
me in troubleshooting the ajax client.
Reply all
Reply to author
Forward
0 new messages