facing issues with JIRA cluster

java.lang.RuntimeException: com.opensymphony.module.propertyset.PropertyImplementationException: SQL Exception while executing the following:SELECT ID, propertytype FROM propertyentry WHERE ENTITY_NAME=? AND ENTITY_ID=? AND PROPERTY_KEY=? (Streaming result set com.mysql.jdbc.RowDataDynamic@70e447e4 is still active. No statements may be issued when any streaming result sets are open and in use on a given connection. Ensure that you have called .close() on any active streaming result sets before attempting more queries.)

5 answers

This widget could not be displayed.

There is no "JIRA Cluster", so we need a bit more information on what you're running and what you have configured here.  (Do you mean Data Centre?).  What's the rest of the error too?

This widget could not be displayed.

Same error here, after upgrading to JIRA 7

Still don't know what is meant by "JIRA Cluster"

I mean JIRA data center, I have installed 2 JIRA nodes, and configured to connect the same database. Configured HaProxy as load balance, to access the data center. Kindly help me in building JIRA data center with 2 or 3 JIRA nodes

Ok, data centre, good. We probably need more of the error message, what was it trying to do before the error was thrown? The error you've got is a root cause, but it should have logged an error in the processes leading up to that attempt to do something with the database. Secondly, a rough overview of your setup would be useful. Basically, which documents have you been following in order to try to get this working?

This widget could not be displayed.

I have configured JIRA data center.


machine A = database and load balancer

machine B = jira node 1

machine C= jira node 2


  JIRA node1 and 2 are pointed to same data base and same user. both the services are working fine individually.


  When I add user using machine B it is not appearing in machine C vise varsa. Below is the error in logs.


2016-01-13 11:20:51,464 http-nio-8080-exec-19 ERROR admin 680x35x1 i234i2 /secure/admin/user/UserBrowser.jspa [webwork.util.ValueStack] METHOD: "remoteUserPermittedToEditSelectedUser", exception:


        at com.atlassian.jira.user.LazyLoadingApplicationUser.getDirectoryId(LazyLoadingApplicationUser.java:40)

        at com.atlassian.jira.user.util.DefaultUserManager.userDirectoryAllowsUpdateUser(DefaultUserManager.java:428)

        at com.atlassian.jira.user.util.DefaultUserManager.canUpdateUser(DefaultUserManager.java:305)

        at com.atlassian.jira.web.action.admin.user.UserBrowser.isRemoteUserPermittedToEditSelectedUser(UserBrowser.java:224)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        ... 2 filtered

        at java.lang.reflect.Method.invoke(Method.java:497)

        at webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtils.java:70)

        at webwork.util.InjectionUtils.invoke(InjectionUtils.java:56)

        at webwork.util.ValueStack.findValue(ValueStack.java:517)

        at webwork.util.SimpleTest.test(SimpleTest.java:408)

        at webwork.util.ValueStack.test(ValueStack.java:157)

        at webwork.view.taglib.IfTag.doStartTag(IfTag.java:40)

        at jsp.secure.admin.user.views.userbrowser_jsp._jspx_meth_ww_005fif_005f17(userbrowser_jsp.java:4734)

        at jsp.secure.admin.user.views.userbrowser_jsp._jspx_meth_ww_005fiterator_005f2(userbrowser_jsp.java:2906)

        at jsp.secure.admin.user.views.userbrowser_jsp._jspService(userbrowser_jsp.java:184)

        at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)

        at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)

        ... 125 filtered

        at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)

        ... 50 filtered

        at com.atlassian.greenhopper.jira.filters.ClassicBoardRouter.doFilter(ClassicBoardRouter.java:59)

        ... 151 filtered

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

        at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)

        at java.lang.Thread.run(Thread.java:745)


Kindly help to fix the issue.

This widget could not be displayed.

Mm, that seems unrelated to the original error.  There's something wrong in your setup, but I think you need a lot more investigation and detail before you're going to get far.

I'd raise this with Atlassian support, it's something they're likely to have encountered before.

This widget could not be displayed.

Just ran into the same problem as OP. 

In our case it was part of a bigger problem with the nodes not being able to communicate with each other. It seems that using hazelcast for node discovery means using hostnames instead of ip. We had to make sure that our hosts-files contained the names of all the other nodes otherwise we'd get alot of "unknown host" errors on the logs.

Fixing the hostname issue fixed the user management issue as well. 

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted yesterday in New to Jira

Are you planning to trial, or are currently trialling Jira Software? - We want to talk to you!

Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in   talking to 20 people planning t...

81 views 1 0
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you