jsessionid/404 symptoms?

Sorry if I got a little long-winded, and I don't know if it helps, but...

Status = logged out (intentionally).
New browser session.

Upon browser open to any existing 'thread' or 'message' (basically, anywhere other than the front page in forums.acobe.com), links have jsessionid and so called "meatball" graphics are only showing as their respective alt attributes [User | Participant | Employee, etc.]

If this initial page is a 'thread' page showing the subject headers ( http://forums.adobe.com/community/general/forum_comments?view=discussions ), I can click on a subject with no problem. The [Next] or [2] links merely append an octothorpe # do nothing whatsoever. If I click on the dated "last post" above "whoever" link on the right side, I see the Error 404 that others have mentioned.

This appears to be the case whether this new session is opened to a "Discussions" page showing a list of subject headers (topics) or a "Message" thread showing messages in the thread (I am still trying to come to terms with Jive terminology). ie: whether the link is forums.adobe.com/thread/* or forums.adobe.com/message/* and even when the new session is http://forums.adobe.com/index.jspa?showpersonalized=true (Your View)

Most internal links have jsessionid in the URL and the hover JavaScripts (ie: user profile) do not work. Some internal links do not work at all (no jsessionid included) such as the previously mentioned [Next] or [2] from a /thread/* page.

Click on any *working* internal Jive link from here and, upon next page load, all subsequent jsessionid's are no longer required or included in internal links - and the links work fine (sans browser Back button/keyboard shortcut). The "meatball" graphics appear with their respective images. Hover over users now brings up their stats and links through the JS hovers.

Status = logged in.
New browser session.

Same symptoms.

It seems that the initial browser session load of any Adobe Jive page requires a click on a (working) internal link to rid itself of the jsessionid link.

Conclusion?
If you are experiencing 404 errors due to entering the forum in a new session, try clicking on a link that actually works first, ie a "subject" link rather than a "date" link. Or click the forum breadcrumb even to get to the same forum thread index.

I am clearly not a Java/JavaScript enthusiast, but it seems as though it might be as simple as PHP's session.use_trans_sid when compiling the server software - or with a simple server config setting. Or it could be caused somewhere in the over-zealous and voluminous JavaScript (or maybe server-side Java?) used by Jive.

IMHO, Java should be used by refrigerators or PDAs and JavaScript should be used only to enhance a site. It should NOT be required to view or post content for a site. JS should never interfere with function.

--
Mark A. Boyd
Keep-On-Learnin' 🙂
This message was processed and edited by Jive.
It shall not be considered an accurate representation of my words.
It might not even have been intended as a reply to your message.