on 10-25-2007 6:50 PM
Running SPS13 with EP usage type, etc... install on SUSE Linux/DB2 (32bit). I can connect to the WAS/Portal from Firefox fine on the console of the box, but there are problems when I try to connect from a client on the network. I have opened the appropriate ports in the SUSE firewall. The symptoms are that the login page shows up fine, then after logging in (as j2ee_admin), the content admin page loads, but none of the iviews on the page load, the browser just continues to try to open the iviews, but they never show up.
I've seen nothing in the server logs that has helped me, and HTTPWatch gives some generic error message: ERROR_HTTP_INVALID_SERVER_RESPONSE
I'd try first (before anything else) to <b>disable </b>the firewall and see if it works then. This will make sure, if it's network related or if you have a problem with the portal itself.
--
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well, the problem is fixed... It looks like the usage type was not completely installed. I'm still not sure why the systems showed those symptoms, but I opened SDM and rescanned the SPS files and found a few that were showing as not yet deployed. After manually deploying (with no errors) and restarting the J2EE, the system is behaving properly. I'm marking the question as answered and awarding points for all that contributed on the thread. Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
do you have java runtime environment?
Thanks,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think all processes are coming up ok, I can run the portal with no problems from a browser running on the console. So is it safe to assume the java processes are running? Are different processes used when servicing an http request from the network vs. local? Both browsers are connecting to the same port.
My next test is to run this on an isolated network(unplug from the LAN) and see if it behaves differently.
(Just ran this test, unplugged my hub from the LAN, same result, so it does not look like a network/filtering/router issue.)
Message was edited by:
Jon H Goldberg
Same problem both ways.... Portal server is not in DNS, using hosts file. I've tried FQDN, as well as just host name and IP address... I can connect and go through the initial login page with all those methods, all of them hang after rendering the TLN, and while trying to render the individual iviews on the page.
Hi,
Please try from other browser or update your browser. Also, I would suggest, stop EP and start it again. and clean ur cookies...
Thanks,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.