Unable to access Management portlet for Portal 2.2.0RC1

[benkrembs]

I was just testing out the latest version of JBoss Portal and encountered two fairly show-stopping problems.

1. When I browse to the Management page, the management portlet never appears and instead the following error appears in the console: "ERROR [ApplicationImpl] Undefined component type org.apache.myfaces
.HtmlTree2"

2. Everything except for that management portlet works properly for the first server run. However, if I stop the server and restart it, some problems crop up. First, the portal immediately redirects all requests to the login page (even after clearing cookies) instead of presenting the general landing page. Second, after logging in, users get redirected to a standard Tomcat 401 page.

Info:
1. Jboss Portal 2.2 RC1 running on Postgres 8.0
2. Jboss AS 2.0.1RC1 running on default database

Anyone else experience this? I tried clearing out the database and deleting all temp files, but the above problems remained.

-Ben

[roy.russo]

Deploy on JBoss AS 4.0.3SP1 and try again, please.

[benkrembs]

Sorry, typo on my part. The portal is currently experiencing those problems on on Jboss AS 4.03 SP1 (I accidently copied the version from the portal before.

Any ideas?

-Ben

[julien1]

do you have any specific classloading configuration for JBoss ?

[lucluc]

I do have same problems

1. Jboss Portal 2.2 RC1 running on MySql 5.0
2. Jboss Jboss AS 4.03 SP1 running on PortalDS

No custom config.

thanks

[benkrembs]

I also have no custom config -- I'm running everything using the defaults.

Does it actually work for anyone?

-Ben

[julien1]

Check that the admin user does have the Admin role in your database. It may come from that.

[roy.russo]

ok. A few issues in this thread:

1. Do not deploy on MySQL5. We have not tested compatibility with it, and it will most likely not function properly. See this thread, if you insist on using 5: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=73683

2. Last time I tested deployment on 4.0.3SP1 installed via the INSTALLER, it did not work properly. My own test environment uses the zip version of 4.0.3SP1.