CCC Last Comment plugin - last-comment-searcher is invalid?

[Mike Rocheleau]

After upgrading JIRA to 6.1.6 and CCC to 3.0.0, we're getting floods of this in catalina.out and atlassian-jira.log Unknown if this is actually causing any problems, but definitely flooding the logs:

Note that I've removed the username and replaced with "usernameher" in this text quote below:

2014-02-25 10:12:22,872 http-bio-443-exec-26424 WARN usernamehere 612x1193570x5 1vpir5n 10.217.132.115 /secure/QueryComponent!Default.jspa [jira.issue.managers.DefaultCustomFieldManager] Custom field searcher module: com.capitalcityconsultants.jira.plugins.customfields.ccc-lastcomment:last-comment-searcher is invalid. Null being returned.

2014-02-25 10:12:23,887 http-bio-443-exec-26134 WARN usernamehere 612x1193594x5 1vpir5n 10.217.132.115 /secure/QueryComponent!Default.jspa [jira.issue.managers.DefaultCustomFieldManager] Custom field searcher module: com.capitalcityconsultants.jira.plugins.customfields.ccc-lastcomment:last-comment-searcher is invalid. Null being returned.

2014-02-25 10:12:25,378 http-bio-443-exec-26134 WARN usernamehere 612x1193640x4 1vpir5n 10.217.132.115 /rest/issueNav/1/issueTable [jira.issue.managers.DefaultCustomFieldManager] Custom field searcher module: com.capitalcityconsultants.jira.plugins.customfields.ccc-lastcomment:last-comment-searcher is invalid. Null being returned.

There's maybe 1-5 of these every minute all day long. Is this normal?

[Mike Rocheleau · Accepted solution]

The issue turned out to be:

We had it installed before, removed it, ran JIRA for a while without it installed and then reinstalled it. Our custom field was actually still the one from the OLD version, for whatever reason. Was instructed to remove the field and re-add it, then reindex. That seems to have worked.

Thanks William.

[MartinS]

• Find the custom field that is causing this, e.g. on mysql:

  select * from customfield where CUSTOMFIELDSEARCHERKEY = "com.capitalcityconsultants.jira.plugins.customfields.ccc-lastcomment:last-comment-searcher"

  note the value of the field "cfname"

• find the cfname at $BASEURL/secure/admin/ViewCustomFields.jspa, click "Edit" next to it.
• Pick a new search template (or if it says "There are no search templates for this custom field type", just ignore that)
• important: click SAVE

• check the database 

  select * from customfield where CUSTOMFIELDSEARCHERKEY = "com.capitalcityconsultants.jira.plugins.customfields.ccc-lastcomment:last-comment-searcher"

  -> should be empty

[William Crighton [CCC]]

Sorry man (and I know you know this now, adding comment for anyone else who has experienced the same thing but didn't remind me of it) - this was a silly permissions mistake in our project configurattion which has since been resolved. You still have to be logged into the OnDemand instance to be able to create/comment on issues, but your email address is hidden from all other users and you can use whatever username you'd like.

Cheers,

-wc

ps....if you're feeling generous I'll take the points

[Mike Rocheleau]

Hi William,

I haven't been able to respond on the ticket as you requested because I'm only a watcher. You'll need to add me as a requester or somesuch so I can comment.

I sent you what you asked for via email, but not sure if I had the right address or if you got it, so responding here as well. Let me know if you didn't receive a message from me yesterday.

[Mike Rocheleau]

Thanks William!

I was hoping it to be a safe one to ignore, but the prevalance of the messages made me wonder. I've got the issue on your OnDemand instance watched, let me know if I can provide anything further.

Cheers,

Mike

[William Crighton [CCC]]

Mike,

Hopefully you won't mind - I've copied this issue to our OnDemand instance, link below:

The issue is located here: https://capitalplugins.atlassian.net/browse/LCCF-45

When you get a chance please create an account on our OnDemand instance - it's free - and then watch that issue (long ugly link to watch LCCF-45).

However - I believe you can safely ignore these messages. I'm going to go ahead and make sure we aren't destabilizing the application server (via memory leak or other annoyance) and if there's a way to cleanly resolve what's throwing that message. What I believe it is:

The 3.0.0 release of Last Comment removed the need for us to ever write any information into the database - so there's actually nothing for the searcher to 'search' on - however I'm going to see if we can trick it into indexing the document that makes up the last comment on the issue (the entire comment, not just the part that shows up in the field). That would solve another request or two in a way that'd be easier than writing a search function. Probably have better performance as well.

I'll try to get you an update within 1 week. Please let me know, via issue LCCF-45, if you encounter anything else - any other problems.

Thanks,

-wc

[Michael Kelly [Praecipio]]

How can you find what field needs to be deleted and recreated to fix this problem, the log doesn't give any hints to the ID of the field?

[William Crighton [CCC]]

Michael,

Sorry we didn't see this before now - just FYI we're better at responding to issues raised at https://capitalplugins.atlassian.netthan we are to comments added in answers.

If you have a question still on what field to remove and which one to leave you can post the relevant database column data here or in an issue or just email me - my email's pretty easy to find. I can take a look at give you my opinion.

In general it'll be the field with a lower 'id' value, meaning it was (most likely) created earlier. The other safe items to look for would be the custom field type column - the one that better matches the plugin key (and the custom field type module defined in the plugin when viewed at the 'manage add-ons page') is the one to keep.

Hope that helps

-wc