jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Guggisberg <stefan.guggisb...@gmail.com>
Subject Re: RepositoryException
Date Mon, 20 Jun 2011 15:05:27 GMT
On Mon, Jun 20, 2011 at 4:58 PM, Shah, Sumit (CGI Federal)
<Sumit.Shah@cgifederal.com> wrote:
> Hi Stefan,
>
> As Jukka suggested, we are going to try upgrading to the latest IBM JDK. It seems like
we are at SR6.

i can't follow you here. how is the problem you're describing in this
thread related to a JVM version?

>
> Thanks
> Sumit
>
> -----Original Message-----
> From: Stefan Guggisberg [mailto:stefan.guggisberg@gmail.com]
> Sent: Monday, June 20, 2011 7:56 AM
> To: users@jackrabbit.apache.org
> Subject: Re: RepositoryException
>
> hi sumit,
>
> On Sat, Jun 18, 2011 at 11:02 PM, Shah, Sumit (CGI Federal)
> <Sumit.Shah@cgifederal.com> wrote:
>> All,
>>
>> I am seeing this error on my Jackrabbit 2.2.5 environment:
>>
>> 13:12:26.171 [RMI TCP Connection(5988)-206.137.126.43] WARN  o.a.j.core.ItemSaveOperation
- /momroot/BillingStatement/&1786&F0004645/jcr:lockToken: failed to restore transient
state
>> javax.jcr.RepositoryException: org.apache.jackrabbit.core.state.ItemStateException:
there's already a property state instance with id 8afcfef0-593b-40c1-aec8-eba53edf3e2c/{http://www.jcp.org/jcr/1.0}lockToken
>>                at org.apache.jackrabbit.core.PropertyImpl.restoreTransient(PropertyImpl.java:195)
~[jackrabbit-core-2.2.5.jar:2.2.5]
>>                at org.apache.jackrabbit.core.ItemSaveOperation.restoreTransientItems(ItemSaveOperation.java:878)
[jackrabbit-core-2.2.5.jar:2.2.5]
>>                at org.apache.jackrabbit.core.ItemSaveOperation.perform(ItemSaveOperation.java:276)
[jackrabbit-core-2.2.5.jar:2.2.5]
>>                at org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:188)
[jackrabbit-core-2.2.5.jar:2.2.5]
>>                at org.apache.jackrabbit.core.ItemImpl.perform(ItemImpl.java:91)
[jackrabbit-core-2.2.5.jar:2.2.5]
>>                at org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:329)
[jackrabbit-core-2.2.5.jar:2.2.5]
>>                at org.apache.jackrabbit.core.session.SessionSaveOperation.perform(SessionSaveOperation.java:42)
[jackrabbit-core-2.2.5.jar:2.2.5]
>>                at org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:188)
[jackrabbit-core-2.2.5.jar:2.2.5]
>>                at org.apache.jackrabbit.core.SessionImpl.perform(SessionImpl.java:355)
[jackrabbit-core-2.2.5.jar:2.2.5]
>>                at org.apache.jackrabbit.core.SessionImpl.save(SessionImpl.java:758)
[jackrabbit-core-2.2.5.jar:2.2.5]
>>                at org.apache.jackrabbit.rmi.server.ServerSession.save(ServerSession.java:263)
[jackrabbit-jcr-rmi-2.2.5.jar:na]
>>
>>
>> Can someone please explain what this means, the cause and how it can be resolved?
>
> first of all it's logged as a warning, so nothing to be seriously
> worried about.
>
> when a save operation fails the transient session state will be
> restored as it was
> before the #save() call. in this particular case there's been a
> problem restoring
> the transient session state.
>
> however, it would be interersting to see why the #save() call failed
> in the first place.
>
> cheers
> stefan
>
>>
>> Thanks
>> Sumit
>>
>

Mime
View raw message