You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@roller.apache.org by John Moylan <jo...@nuatech.net> on 2008/02/18 08:17:58 UTC

Re: Unable to access web authoring pages after upgrade from 3.1 to 4.0

Try turning password encryption off in roller-custom.properties.
Encryption is on be default in 4.

J

On Sun, 2008-02-17 at 17:55 -0500, Eric Wittle wrote:
> I was running 3.1 with Mysql 4.1 on an older server. I bought a new  
> better server, and decided to migrate Roller and upgrade it.
> 
> I successfully migrated roller (was able to run 3.1 just fine), but  
> after the 4.0 upgrade, I'm having problems.
> 
> The upgrade is partially successful; I can access my blog as an  
> anonymous user. However, when I log in, I get:
> 
> Permission Denied
> Possible causes:
> You requested a weblog entry that you do not have permission to edit  
> (perhaps one you've already submitted for review?).
> You tried to save an object from "stale" web page, left by an earlier  
> login under a different user account.
> You logged in using incorrect capitalization of your username. To  
> resolve this problem, logout and login again with your correct username.
> Your blog server's database connection is misconfigured. To resolve  
> this problem, see your system administrator.
> 
> The URL which is generating this page is: http://wittle.net:8080/roller/roller-ui/menu.rol 
> , which as far as I know is the general UI for administering my blog.  
> I get the same permission denied results when I log in as the admin  
> user, but the URL is different. My regular blog URL (http://wittle.net:8080/roller/ericw/ 
> ) works regardless of whether I'm logged in or not, or which account  
> I'm logged in with.
> 
> I cannot see anything interesting in the log file. (The last line in  
> the roller.log file is recording that it is initializing the Velocity  
> Rendering Engine, and this message is > 10 minutes old).
> 
> I doubt that this problem is any of the first three possibilities  
> listed above, and I can't find any details on the fourth item. It  
> seems unlikely the connection itself is misconfigured; if so how would  
> Roller be able to display the main view?
> 
> I'm looking for help on how to triage this further. My database has  
> been upgraded from the 1.X series of Roller, and I've had problems in  
> the past where old content in the DB has caused problems with newer  
> releases. I'm also running mysql 5.X on the new system, and was  
> running 4.1 on the old system.
> 
> Any help taking the next step in triage would be appreciated.
> 
> -Eric

Re: The type "class org.apache.roller.weblogger.pojos.TaskLock" has not been enhanced

Posted by Dave <sn...@gmail.com>.
On Feb 18, 2008 3:13 PM, Broderick, Andrew <An...@monster.com> wrote:
> Hi,
>
> I just built Roller 4, using the 'dist' task of the build file in
> roller/apps/weblogger. I deployed it in Tomcat 6, and am getting the
> above error message. I am using Windows XP and JDK 1.5.0_06 both to
> build and to run Tomcat.
>
> The full error message is:
>
> Feb 18, 2008 2:11:27 PM org.apache.catalina.core.StandardContext
> listenerStart
> SEVERE: Exception sending context initialized event to listener instance
> of class org.apache.roller.weblogger.ui.core.RollerContext
> java.lang.RuntimeException: <0.9.7-incubating fatal user error>
> org.apache.openjpa.persistence.ArgumentException: The type "class
> org.apache.roller.weblogger.pojos.TaskLock" has not been enhanced.
>         at
> org.apache.roller.weblogger.business.jpa.JPAPropertiesManagerImpl.initia
> lize(JPAPropertiesManagerImpl.java:92)
>         at
> org.apache.roller.weblogger.business.WebloggerImpl.initialize(WebloggerI
> mpl.java:301)
>         at
> org.apache.roller.weblogger.ui.core.RollerContext.contextInitialized(Rol
> lerContext.java:159)
>         at
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.j
> ava:3830)
>
> ....
>
>
> Caused by: <0.9.7-incubating fatal user error>
> org.apache.openjpa.persistence.ArgumentException: The type "class
> org.apache.roller.weblogger.pojos.TaskLock" has not been enhanced.
>         at
> org.apache.openjpa.meta.ClassMetaData.resolveMeta(ClassMetaData.java:160
> 6)
>         at
> org.apache.openjpa.meta.ClassMetaData.resolve(ClassMetaData.java:1580)
>         at
> org.apache.openjpa.meta.MetaDataRepository.processBuffer(MetaDataReposit
> ory.java:659)
>
> Any help appreciated.

I really don't know how to explain that one.

Did you make any changes to the code or the build script?

- Dave

The type "class org.apache.roller.weblogger.pojos.TaskLock" has not been enhanced

Posted by "Broderick, Andrew" <An...@Monster.com>.
Hi,

I just built Roller 4, using the 'dist' task of the build file in
roller/apps/weblogger. I deployed it in Tomcat 6, and am getting the
above error message. I am using Windows XP and JDK 1.5.0_06 both to
build and to run Tomcat.

The full error message is:

Feb 18, 2008 2:11:27 PM org.apache.catalina.core.StandardContext
listenerStart
SEVERE: Exception sending context initialized event to listener instance
of class org.apache.roller.weblogger.ui.core.RollerContext
java.lang.RuntimeException: <0.9.7-incubating fatal user error>
org.apache.openjpa.persistence.ArgumentException: The type "class
org.apache.roller.weblogger.pojos.TaskLock" has not been enhanced.
	at
org.apache.roller.weblogger.business.jpa.JPAPropertiesManagerImpl.initia
lize(JPAPropertiesManagerImpl.java:92)
	at
org.apache.roller.weblogger.business.WebloggerImpl.initialize(WebloggerI
mpl.java:301)
	at
org.apache.roller.weblogger.ui.core.RollerContext.contextInitialized(Rol
lerContext.java:159)
	at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.j
ava:3830)

....


Caused by: <0.9.7-incubating fatal user error>
org.apache.openjpa.persistence.ArgumentException: The type "class
org.apache.roller.weblogger.pojos.TaskLock" has not been enhanced.
	at
org.apache.openjpa.meta.ClassMetaData.resolveMeta(ClassMetaData.java:160
6)
	at
org.apache.openjpa.meta.ClassMetaData.resolve(ClassMetaData.java:1580)
	at
org.apache.openjpa.meta.MetaDataRepository.processBuffer(MetaDataReposit
ory.java:659)

Any help appreciated.

Thanks,

Andrew


NOTICE:
This message may contain privileged or otherwise confidential information. If you are not the intended recipient, please immediately advise the sender by reply email and delete the message and any attachments without using, copying or disclosing the contents. (FE1)

Re: Unable to access web authoring pages after upgrade from 3.1 to 4.0

Posted by Eric Wittle <er...@wittle.net>.
I already did that; I'm not having a problem logging in. When I'm not  
logged in, the blog menu items on my main page match the not logged in  
state (one of the choices is login), when I log in, the menu items  
match the logged in state (Settings, Logout, etc.). The logout link  
works fine, since it returns me to the main page.

-Eric

On Feb 18, 2008, at 2:17 AM, John Moylan wrote:

>
> Try turning password encryption off in roller-custom.properties.
> Encryption is on be default in 4.
>
> J
>
> On Sun, 2008-02-17 at 17:55 -0500, Eric Wittle wrote:
>> I was running 3.1 with Mysql 4.1 on an older server. I bought a new
>> better server, and decided to migrate Roller and upgrade it.
>>
>> I successfully migrated roller (was able to run 3.1 just fine), but
>> after the 4.0 upgrade, I'm having problems.
>>
>> The upgrade is partially successful; I can access my blog as an
>> anonymous user. However, when I log in, I get:
>>
>> Permission Denied
>> Possible causes:
>> You requested a weblog entry that you do not have permission to edit
>> (perhaps one you've already submitted for review?).
>> You tried to save an object from "stale" web page, left by an earlier
>> login under a different user account.
>> You logged in using incorrect capitalization of your username. To
>> resolve this problem, logout and login again with your correct  
>> username.
>> Your blog server's database connection is misconfigured. To resolve
>> this problem, see your system administrator.
>>
>> The URL which is generating this page is: http://wittle.net:8080/roller/roller-ui/menu.rol
>> , which as far as I know is the general UI for administering my blog.
>> I get the same permission denied results when I log in as the admin
>> user, but the URL is different. My regular blog URL (http://wittle.net:8080/roller/ericw/
>> ) works regardless of whether I'm logged in or not, or which account
>> I'm logged in with.
>>
>> I cannot see anything interesting in the log file. (The last line in
>> the roller.log file is recording that it is initializing the Velocity
>> Rendering Engine, and this message is > 10 minutes old).
>>
>> I doubt that this problem is any of the first three possibilities
>> listed above, and I can't find any details on the fourth item. It
>> seems unlikely the connection itself is misconfigured; if so how  
>> would
>> Roller be able to display the main view?
>>
>> I'm looking for help on how to triage this further. My database has
>> been upgraded from the 1.X series of Roller, and I've had problems in
>> the past where old content in the DB has caused problems with newer
>> releases. I'm also running mysql 5.X on the new system, and was
>> running 4.1 on the old system.
>>
>> Any help taking the next step in triage would be appreciated.
>>
>> -Eric
>