Loading Profile...
Salesforce plugin generating exceptions in catalina.out
My Salesforce-JIRA plugin throws an exception every time a new issue is created, saying "No Salesforce Case ID set for issue <issue>" . JIRA functions just fine, but it's filling up my "catalina.out" file like crazy.
Here's the thing, I have several issue types in JIRA, but I'm only mapping my salesforce stuff to only one issue type. I have one custom field that points back to a SF Case ID. All other issue types in JIRA have nothing to do with Salesforce. So, it seems that the listener is noticing that all of my other issue types do not have a Salesforce Case ID. Yes, this is correct, they don't. But this should not be an error.
Thanks for any help in resolving this issue.</issue>
Here's the thing, I have several issue types in JIRA, but I'm only mapping my salesforce stuff to only one issue type. I have one custom field that points back to a SF Case ID. All other issue types in JIRA have nothing to do with Salesforce. So, it seems that the listener is noticing that all of my other issue types do not have a Salesforce Case ID. Yes, this is correct, they don't. But this should not be an error.
Thanks for any help in resolving this issue.</issue>
I’m annoyed
2
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
-
Inappropriate?Hi Dan,
I would imagine that this is something we will need to make a new release to fix. I will get the development team to look into and will reply again shortly.
Kind Regards,
Charles1 Comment
Add a comment
This solves the problem
-
Charles,
To clarify, the thing throwing the exception come from the SFCaseUpdateListener. Turning on this listener generates a ton of exceptions if my issue type doesn't have a salesforce case-id in it.
It appears that this problem also causes a memory leak, that when aggregated over a few weeks of up-time, can gobble up a lot of memory.
So, for now, I'm going to turn off the SFCaseUpdateListener. This is not desirable for me, but I need the system to be more reliable. -
Inappropriate?Hi Dan,
In order to help us better analyse this problem, could you please send us your catalina.out logs to sfdc@customware.net
Also if you could get us a screenshot of your JIRA - Salesforce.com Mapping configurations that would help us in replicating the issue.
Currently I believe that the memory problems you are experiencing might be related to the exceptions that are happening.
Thank you. -
Inappropriate?I just installed the plugin to evaluate it and this is the first thing I saw as well. Issues in only a single project are mapped to Salesforce cases but the listener is blasting out error messages for each and every issue created in all the other projects.
What I don't know is whether the listener is required for "Sync to JIRA" functionality to work from salesforce. My assumption is "yes".
I suspect that adding the salesforce case id custom field to EVERY other project in my Jira installation, but not putting it on any screens for those projects, will probably make the errors go away, but that seems like way overkill.
I'm not sure we can use this plugin effectively with these errors.
I’m irritated
-
Inappropriate?This problem has now been fixed and will be shipped in our next release. Further details can be found at - http://greenhouse.customware.net/jira...
EMPLOYEE
EMPLOYEE
