SV: Alert! Issue has been modified, please review before submitting your changes.

Yes, you assume right. We are not editing the same issue simultaneously and
I cannot submit the changes. It does not happen on all defects. I can create
defects and they work fine all the way through. 

I have narrowed the problem down to the defects I have changed earlier today
actually.

None of the logfiles gets log entries when I reproduce the problem. 

We run tomcat/MySQL/linux suse 10.1 and we have restarted tomcat with no
effect.

 

This is one error I found in scarab.log from today, but it does not occur
exactly when I reproduce the problem either.

java.lang.Exception: Userid cannot be null

        at
org.tigris.scarab.om.ScarabUserImpl.isPasswordExpired(ScarabUserImpl.java:77
1)

        at
org.tigris.scarab.pipeline.FreshenUserValve.invoke(FreshenUserValve.java:116
)

        at
org.apache.turbine.pipeline.TurbinePipeline.invokeNext(TurbinePipeline.java:
231)

        at
org.apache.turbine.pipeline.DefaultSessionValidationValve.invoke(DefaultSess
ionValidationValve.java:131)

        at
org.apache.turbine.pipeline.TurbinePipeline.invokeNext(TurbinePipeline.java:
231)

        at
org.apache.turbine.pipeline.DefaultLoginValve.invoke(DefaultLoginValve.java:
109)

        at
org.apache.turbine.pipeline.TurbinePipeline.invokeNext(TurbinePipeline.java:
231)

        at
org.tigris.scarab.pipeline.AnonymousLoginValve.invoke(AnonymousLoginValve.ja
va:65)

        at
org.apache.turbine.pipeline.TurbinePipeline.invokeNext(TurbinePipeline.java:
231)

        at
org.apache.turbine.pipeline.DefaultSessionTimeoutValve.invoke(DefaultSession
TimeoutValve.java:121)

        at
org.apache.turbine.pipeline.TurbinePipeline.invokeNext(TurbinePipeline.java:
231)

        at
org.tigris.scarab.pipeline.DetermineTargetValve.invoke(DetermineTargetValve.
java:102)

 

From services.log

2008-02-07 11:21:41,657 [http-8082-Processor24] ERROR
org.apache.fulcrum.TurbineServices - java.beans.IntrospectionException:
Method not fo

und: isConditionsArray

 

Nothing in turbine.log

 

From velocity.log

2008-02-07 11:21:41,844 [http-8082-Processor24] ERROR org.apache.velocity -
Error in evaluation of == expression. Both arguments must be of

 the same Class. Currently left = class java.lang.Integer, right = class
java.lang.String. viewIssue/ViewIssueTab1.vm [line 49, column 59] 

(ASTEQNode)

 

  _____  

Från: Jorge Uriarte Aretxaga [mailto:[email protected]] 
Skickat: den 7 februari 2008 11:00
Till: [email protected]
Ämne: Re: Alert! Issue has been modified, please review before submitting
your changes.

 

Mikael; this message should only appear in the case of simultaneous editing
of an issue, and must be solved just submitting again as it suggests. I
assume by your email that this is not the case and that you're stuck getting
the message continuosly, and that's weird...

Can you take a look at the logs? anything strange? Can you change other
defects or is the whole system "locked"?

_
Jorge

On 2/7/08, Mikael Brodd <[email protected]> wrote:

Hi,

 

We are using scarab b20.

Everything has been working fine until today when we suddenly couldn't
change several defects. Every attempt to change a defect resulted in a
warning stating

Alert! Issue has been modified, please review before submitting your
changes.

There is no way out of it as it seems. We have reviewed the changes and want
to submit them, but how? What does the message actually mean and why does it
appear now? This is the first time we see it after more than a year of using
the same version of scarab.

We are sure that the user trying to change the defect has the permission to
do it.

 

What to do?

 

Regards – Mikael Brodd