Hi HomeAway,

The errors that you're seeing are not related to this bug report. Hercules matched this bug incorrectly, and it's not relevant to your case, as this one is about the JIRA Issues Macro not displaying any data. I have modified it so Hercules will no longer match this bug report incorrectly.

We will continue to work with you in the Support Case.

Kind regards,
Denise
Atlassian Support

Futhermore...
In this case, the macro is failing on a user who is admin to the project issues being referenced. Others before have failed on "anonyous" because in the new confluence the Jira Issue MAcro appears to assume anonymous access whereas before that was an explicit option. Therefore the jira project that is the target of the macro must now have browse project permission set to group "AnyOne" so that anonymous browsing is enabled.

Ok. We can deal with that, but it shouldn't crash confluence!

Thanks Edith, my environment is exactly as stated and I get a few hundred of these right before a crash..at least once a day...

2013-10-16 10:42:01,896 ERROR [http-10.28.1.113-80-78] [extra.jira.executor.FutureStreamableConverter] logStreamableError Unable to render JIRA issues macro, connection to JIRA has been timeout.
– space: 196611 | url: /pages/viewrecentblogposts.action | userName: sstone | action: viewrecentblogposts
java.util.concurrent.TimeoutException
...
I have a ticket open.

Hello atlassian8,

The bug described in this issue was resolved in version 5.2.4 of Confluence. I was unable to reproduce the errors you're seeing using the same versions of Confluence, JIRA and the JIRA Macros plugin described in your comment.

If you're still experiencing problems with the macro, could you please raise a support ticket so that we can investigate further?

Regards,
Edith Tom

Could also be:

2013-10-14 13:24:15,309 ERROR [http-10.28.1.113-80-13] [extra.jira.executor.FutureStreamableConverter] logStreamableError Unable to render JIRA issues macro, execution error.
– url: /pages/viewpage.action | page: 119294872 | userName: anonymous | action: viewpage
java.util.concurrent.ExecutionException: com.atlassian.confluence.macro.MacroExecutionException: com.atlassian.confluence.macro.MacroExecutionException: The URL filter is not available to you, perhaps it has been deleted or had its permissions changed
at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source)
at java.util.concurrent.FutureTask.get(Unknown Source)
at com.atlassian.confluence.extra.jira.executor.FutureStreamableConverter.writeTo(FutureStreamableConverter.java:42)
at com.atlassian.confluence.content.render.xhtml.transformers.DefaultFragmentTransformer$NonXmlSubstreamable.writeTo(DefaultFragmentTransformer.java:294)
at com.atlassian.confluence.content.render.xhtml.transformers.DefaultFragmentTransformer$AggregatedXmlStreamable.writeTo(DefaultFragmentTransformer.java:316)
at com.atlassian.confluence.content.render.xhtml.storage.StorageXhtmlTransformer.transform(StorageXhtmlTransformer.java:44)
at com.atlassian.confluence.content.render.xhtml.TransformerChain.transform(TransformerChain.java:41)
at com.atlassian.confluence.content.render.xhtml.PluggableTransformerChain.transform(PluggableTransformerChain.java:53)
at com.atlassian.confluence.content.render.xhtml.DefaultRenderer.render(DefaultRenderer.java:80)
at com.atlassian.confluence.content.render.xhtml.DefaultRenderer.ren

Could be erroneous, but Hercules says I have 490 instances of this failure in my logs:

Environment: Confluence 5.3, Jira Macros Plugin 5.1.1, Jira 6.0.6#6105

Suspected stack trace:
2013-10-14 13:23:08,992 ERROR [http-10.28.x.xxx-80-8] [atlassian.event.internal.AsynchronousAbleEventDispatcher] run There was an exception thrown trying to dispatch event 'com.atlassian.confluence.event.events.content.page.PageUpdateEvent@46275e67[originalPage=page: Rosetta Stone - Online v.936 (151388916),minorEdit=true,updateTrigger=UNKNOWN,page=page: Rosetta Stone - Online v.937 (48008186),timestamp=1381774988980]' from the invoker 'SingleParameterMethodListenerInvoker

'.
– url: /pages/doeditpage.action | page: 48008186 | userName: lkwan | referer: http://wiki.homeawaycorp.com/pages/editpage.action?pageId=48008186 | action: doeditpage
java.lang.RuntimeException: Could not parse Create JIRA Issue macros
at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:54)
at com.atlassian.event.internal.AsynchronousAbleEventDispatcher$2.run(AsynchronousAbleEventDispatcher.java:66)
at com.atlassian.event.internal.AsynchronousAbleEventDispatcher$1.execute(AsynchronousAbleEventDispatcher.java:32)
at com.atlassian.event.internal.AsynchronousAbleEventDispatcher.dispatch(AsynchronousAbleEventDispatcher.java:60)
at com.atlassian.event.internal.EventPublisherImpl.invokeListeners(EventPublisherImpl.java:160)
at com.atlassian.event.internal.EventPublisherImpl.publish(EventPublisherImpl.java:79)
at com.atlassian.event.legacy.LegacyEventManager.publishEvent(LegacyEventManager.java:36)
at com.atlassian.confluence.event.ConfluenceEventManager.publishEvent(ConfluenceEventManager.java:47)
at sun.reflect.GeneratedMethodAccessor145.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)

abm, can you please check that base URL in JIRA is set correctly - this is the most likely cause for the missing icons.

Upgrading to JIRA issues macro 5.0.2 to Confluence 5.2.3 solved this partly. Icons still missing.

Hi Graham, and anyone else experiencing issues with the JIRA Issues Macro displaying (${entries.size()} issues) after upgrade, this issue is now being tracked in CONF-30429. There is an additional complication being tracked in CONF-30428 - entering the URL for a filter now inserts the JQL directly and decouples the JIRA Issues Macro from the filter in JIRA.

Please watch those bugs for updates.

-Denise
Atlassian Support - Sydney

Thank you, Atlassian. It works.