A JIRA user seems to be having strange issues resulting in SOAP not behaving properly. The problem "goes away" when disabling Greenhopper. It appears to be related to a Greenhopper listener. From their log, it appears that there are lots of other related failures as well but they may not be showing up for them.
In terms of the relevant parts of the log:
2011-10-07 09:18:03,552 http-8080-11 ERROR president.bush 558x38788x1 127.0.0.1 /secure/CreateIssueDetails.jspa [atlassian.event.internal.EventPublisherImpl] There was an exception thrown trying to dispatch event 'com.atlassian.jira.event.issue.IssueEvent@70b79067[issue=IR-22,comment=<null>,worklog=<null>,changelog=<null>,eventTypeId=1,sendMail=true,params={eventsource=workflow, baseurl=http://jira.whatever.com:8080},subtasksUpdated=false]' from the invoker 'com.atlassian.event.internal.SingleParameterMethodListenerInvoker@1625b930'.
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:54)
at com.atlassian.event.internal.AsynchronousAbleEventDispatcher$2.run(AsynchronousAbleEventDispatcher.java:60)
...
Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
at com.atlassian.activeobjects.tx.TransactionalProxy$1.doInTransaction(TransactionalProxy.java:47)
at com.atlassian.sal.core.transaction.HostContextTransactionTemplate$1.doInTransaction(HostContextTransactionTemplate.java:25)
...
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor733.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
...
Caused by: java.lang.reflect.UndeclaredThrowableException
at $Proxy1380.save(Unknown Source)
at com.atlassian.greenhopper.service.rank.RankDaoImpl.setNextForIssue(RankDaoImpl.java:99)
...
Caused by: java.sql.SQLException: Binary logging not possible. Message: Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1055)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956)
This appears to be me to be a database-related issue, but I'm not sure what the exact problem is. Any suggestions on how to debug this? We have verified that disabling Greenhopper makes the issue go away. The user has said that they have upgraded Greenhopper to the latest (which appears to have been re-released?)
