|
|
|
[
Permlink
| « Hide
]
Gary Weaver [21/Aug/08 01:49 PM]
Note: by "I don't remember seeing an error" I meant "I don't remember seeing an error immediately after I first started it and logged in as admin/admin.
It looks like that error happened immediately after login.
This is an intermittent issue with the remote WSRP producer, our only other option would be to remove the example channel completely.
Could you add a comment with URL (and Jira bug link if possible) to that bug? IMHO I'd just leave it here as a known bug referencing that other bug, that way people will know to vote for that other bug, and would only remove that example channel if that external bug wouldn't be fixed before 2.6.2. But I know you have enough on your plate, so sorry to bother you with this. Just mentioning it since it was part of my first experience with 3.0.1 and just wanted to report all the stuff I found/thought about it. Sorry for the deluge.
Thanks again! BTW- I'm easily able to reproduce this issue (every time so far) so I think it should be re-opened?
attaching logs from reproduction of bug:
logs-2.6.1.tar.gz note: the only difference from my distro and the standard quickstart 2.6.1 distro is the change I made to web.xml to comment out the HttpProxyServlet servlet element and servlet-mapping elements per http://www.ja-sig.org/wiki/display/UPC/Addressing+the+uPortal+2.6.1+ProxyServlet+Vulnerability There isn't an existing bug. The library search tries to use a remote service that JASIG has no control over. If that remote service is unavailable the channel will fail, there isn't anything we can do about it short of just removing the channel completely.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||