Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 21:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Incompatibly between Behaviours and Tempo 7.5/7.6

Yousef Hammouda
Contributor
May 16, 2013

I have the following caracteristics on my JIRA system:

  • Tempo: 7.4.3
  • Behavior: 0.5.3
  • JIRA: 5.2.11

I am trying to upgrade tempo to the last version. Nothing unnormal in the functionalities of neither Tempo or Behaviours, but iam getting this error in the logs each time the Log Work or Plan Time dialogue popups are called for an issue:

2013-05-16 08:26:08,370 http-bio-8080-exec-22 ERROR username 506x852x1 bmhm1k 0:0:0:0:0:0:0:1 /rest/com.onresolve.jira.plugin.Behaviours/1.0/behaviours/validators.json [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service
com.sun.jersey.api.ParamException$QueryParamException: java.lang.NumberFormatException: For input string: ""
	at com.sun.jersey.server.impl.model.parameter.QueryParamInjectableProvider$QueryParamInjectable.getValue(QueryParamInjectableProvider.java:74)
	at com.sun.jersey.server.impl.inject.InjectableValuesProvider.getInjectableValues(InjectableValuesProvider.java:46)
	at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$EntityParamInInvoker.getParams(DispatchProviderHelper.java:159)
	at com.atlassian.plugins.rest.common.interceptor.impl.DispatchProviderHelper$ResponseOutInvoker._dispatch(DispatchProviderHelper.java:228)
	at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)  <+11> (HttpMethodRule.java:288) (RightHandPathRule.java:147) (ResourceClassRule.java:108) (RightHandPathRule.java:147) (RootResourceClassesRule.java:84) (WebApplicationImpl.java:1469) (WebApplicationImpl.java:1400) (WebApplicationImpl.java:1349) (WebApplicationImpl.java:1339) (WebComponent.java:416) (ServletContainer.java:537)
	at com.atlassian.plugins.rest.module.RestDelegatingServletFilter$JerseyOsgiServletContainer.doFilter(RestDelegatingServletFilter.java:178)  <+1> (ServletContainer.java:795)
	at com.atlassian.plugins.rest.module.RestDelegatingServletFilter.doFilter(RestDelegatingServletFilter.java:73)  <+16> (DelegatingPluginFilter.java:74) (IteratingFilterChain.java:42) (ServletFilterModuleContainerFilter.java:77) (ServletFilterModuleContainerFilter.java:63) (DelegatingPluginFilter.java:74) (IteratingFilterChain.java:42) (DelegatingPluginFilter.java:66) (RestServletUtilsUpdaterFilter.java:26) (RestServletUtilsUpdaterFilter.java:40) (DelegatingPluginFilter.java:74) (IteratingFilterChain.java:42) (DelegatingPluginFilter.java:66) (ContextFilter.java:25) (DelegatingPluginFilter.java:74) (IteratingFilterChain.java:42) (DelegatingPluginFilter.java:66)
	at com.atlassian.mywork.client.filter.ServingRequestsFilter.doFilter(ServingRequestsFilter.java:37)  <+15> (DelegatingPluginFilter.java:74) (IteratingFilterChain.java:42) (ServletFilterModuleContainerFilter.java:77) (ServletFilterModuleContainerFilter.java:63) (ApplicationFilterChain.java:243) (ApplicationFilterChain.java:210) (AccessLogFilter.java:103) (AccessLogFilter.java:87) (ApplicationFilterChain.java:243) (ApplicationFilterChain.java:210) (XsrfTokenAdditionRequestFilter.java:54) (ApplicationFilterChain.java:243) (ApplicationFilterChain.java:210) (IteratingFilterChain.java:46) (DelegatingPluginFilter.java:66)

I created this issue hopping that Jamie could have the time to answer it.

Any hints that you may have, could help...

Thx

4 answers

1 accepted

0 votes
Answer accepted
Yousef Hammouda
Contributor
October 8, 2014

Upgrading to :

  • JIRA 6.3
  • Tempo 7.10.1
  • And Script Runner (Behaviours) 3.0.6

With the precedent versions, the problem doesn't exist anymore. smile

For older versions, see my second response.

0 votes
Cristian _Southend_ January 13, 2015

I have the error mentioned, this is my Jira configuration:

JIRA 6.1
Tempo 7.10.3
Script Runner 2.1.16
Behaviour Plugin 0.5.10

/rest/com.onresolve.jira.plugin.Behaviours/1.0/behaviours/validators.json [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service

0 votes
Yousef Hammouda
Contributor
May 21, 2013
ShamhoonJ August 27, 2013

Hi Yousef, What turnaround fix did you do? what did you fix in the "clientvaljq.js" file. Any help would be useful our logs are full of the above message.

Yousef Hammouda
Contributor
August 28, 2013

Hello Shamhoon,

Please check the clientvaljq.js i attached to the issue here.

(a simple compare on notpade++ with the original file and you will find out the expressions i added in some if conditions statements to ignore the issueid when it is null)

Yousef

0 votes
Sverrir Tynes [Tempo]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 19, 2013

This has also been reported to Tempo Support and the Tempo developers are in contact with the reporter.

Sverrir Tynes
Tempo support

MarkW
Contributor
May 9, 2014

Any update or link to the support ticket? This happens in JIRA 6.1, Tempo 7.8 and Behaviour 0.5.10.

Susanne Götz [Tempo]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 11, 2014

Hi Mark,

the support ticket is not open, but Tempo developers investigated this at the time (May last year) and came to the conclusion that this is a third-party issue. They suggested contacting the vendor of the Behaviours plugin.

Kind regards,

Susanne

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Upcoming Apps & Integrations Events