The "Balsamic Mockups for Confluence" plugin is generating NPE errors on any of the "Browse Space" pages in Confluence.
Example:
2011-03-23 17:38:58,673 ERROR [http-7070-2] [descriptor.web.conditions.AbstractConfluenceCondition] shouldDisplay Exception calculating condition :java.lang.NullPointerException: null
-- space: 7 | url: /spaces/spaceadmin.action | userName: aholtz | referer: http://wiki.company.com/display/~ahol... | action: spaceadmin
2011-03-23 17:38:58,675 ERROR [http-7070-2] [descriptor.web.conditions.AbstractConfluenceCondition] shouldDisplay Exception calculating condition :java.lang.NullPointerException: null
-- space: 7 | url: /spaces/spaceadmin.action | userName: aholtz | referer: http://wiki.company.com/display/~ahol... | action: spaceadmin
Disable or uninstall the Mockups plugin and revisit any of the "Browse Space" pages and the error goes away. Reinstall/Enable and the error is back.
I just updated to 2.0.19 and confirmed the problem still exists.
-
Hi alex,
sorry for this problem.
I am trying to reproduce it without success on confluence 3.5 using Mockups 2.0.19. I have a couple of test spaces and I can browse them without NPE.
What version of confluence are you using? Do you have a complete stack trace in the log files?
I can try to patch the function "blindly"...
Thanks for your help,
Paolo -
-
Sorry, I should have included that information.
I'm on Confluence 3.1.2.
And, again, regular pages don't cause the error. Only things like the spaceadmin.action pages, or the "mail tab" pages, etc.
I don't remember there being a full stack trace, just those short error messages I posted above, but I'll check the logs again in a bit and I'll provide more details a little later today. -
-
alex,
on confluence 3.1.2, browsing the pages you suggested caused a NPE report in my log file, I think it's the same you are experiencing.
I prepared a fix that is working for me, you can try it downloading our prerelease version of confluence plugin from:
http://balsamiq.com/products/mockups/...
Hope this fixes your issue,
let me know!
Paolo -
-
Hi Paolo, the changes in next.568 did the trick, the error has finally gone away!
We're updating to Confluence 3.5 sometime in the next month, so I was also pleased to hear the issue isn't present in 3.5. Thank you again for your time fixing this for us! -
-
-
Loading Profile...



Twitter,
Facebook, or email.

EMPLOYEE
EMPLOYEE
