[JIRA] (JENKINS-58211) ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat
Title: Message Title Matthias Kraft edited a comment on JENKINS-58211 Re: ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat I am on the LTS versions of Jenkins. Upgrading to 2.290.1 now gives me the same stack trace [~cmolson] mentioned. Update:After installing the Build Symlink plugin the "NoSuchFieldError: SIZE" changed into the OP's "NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat". Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200271.1561558166000.8435.1572875460677%40Atlassian.JIRA.
[JIRA] (JENKINS-58211) ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat
Title: Message Title Matthias Kraft commented on JENKINS-58211 Re: ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat I am on the LTS versions of Jenkins. Upgrading to 2.290.1 now gives me the same stack trace Christian Molson mentioned. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200271.1561558166000.968.1571986920384%40Atlassian.JIRA.
[JIRA] [core] (JENKINS-14189) Discover permission gives Status Code 500 and Stacktrace
Matthias Kraft closed JENKINS-14189 as Fixed Discover permission gives Status Code 500 and Stacktrace This went away some time ago, already. But I am unable to say which version actually fixed it. Thanks for digging up ... closing it now. Change By: Matthias Kraft (22/May/14 6:13 AM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-14253) Discard Old Builds does not remove builds from Matrix-Axes
Matthias Kraft closed JENKINS-14253 as Fixed Discard Old Builds does not remove builds from Matrix-Axes I haven't heard anything back from our Jenkins admins. As I already wrote, there doesn't seem to be an issue anymore. I have no idea when or how this was resolved, though. Nevertheless I am closing this now. If a watcher to this issue disagrees, feel free to reopen or duplicate and explain to Daniel, how this behavior can be reproduced. Change By: Matthias Kraft (22/May/14 6:28 AM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-14253) Discard Old Builds does not remove builds from Matrix-Axes
Matthias Kraft commented on JENKINS-14253 Discard Old Builds does not remove builds from Matrix-Axes Meanwhile I am no longer in charge of our Jenkins. I looked at a couple of jobs that did have the issue in the past and they no longer seem to have it. I go confirming that with the responsible guy ... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-15682) archive artifacts hangs on ia64 slave due to JNA initialization error
Matthias Kraft commented on JENKINS-15682 archive artifacts hangs on ia64 slave due to JNA initialization error We are observing this issue with Jenkins 1.480.3 on RedHat Enterprise Linux Server and SUSE Linux Enterprise Server running on a Mainframe (s390x) using current IBM JDK 7 SR4. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15682) archive artifacts hangs on ia64 slave due to JNA initialization error
Matthias Kraft edited a comment on JENKINS-15682 archive artifacts hangs on ia64 slave due to JNA initialization error We are observing this issue with Jenkins 1.480.3 on RedHat Enterprise Linux Server and SUSE Linux Enterprise Server running on a Mainframe (s390x) using current IBM JDK 7 SR4. A very interesting observation is that on AIX - which also doesn't have an Oracle JDK - a message appears: "Failed to load native POSIX impl; falling back on Java impl. Unsupported OS." - and everything seems to work out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15682) archive artifacts hangs on ia64 slave due to JNA initialization error
Matthias Kraft edited a comment on JENKINS-15682 archive artifacts hangs on ia64 slave due to JNA initialization error We are observing this issue with Jenkins 1.480.3 on RedHat Enterprise Linux Server and SUSE Linux Enterprise Server running on a Mainframe (s390x) using current IBM JDK 7 SR4. A very interesting observation is that on AIX and HP-UX - which also don't have an Oracle JDK - a message appears: "Failed to load native POSIX impl; falling back on Java impl. Unsupported OS." - and everything seems to work out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15682) archive artifacts hangs on ia64 slave due to JNA initialization error
Matthias Kraft commented on JENKINS-15682 archive artifacts hangs on ia64 slave due to JNA initialization error A possible solution might be lined out in these comments: http://jira.codehaus.org/browse/JRUBY-6712 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14351) Outdated JRuby libs
Matthias Kraft updated JENKINS-14351 Outdated JRuby libs Raised to blocker, see related links. Change By: Matthias Kraft (26/Mar/13 1:09 PM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14253) Discard Old Builds does not remove builds from Matrix-Axes
Matthias Kraft created JENKINS-14253 Discard Old Builds does not remove builds from Matrix-Axes Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 29/Jun/12 7:46 AM Description: We are experiencing a strange behavior of our Matrix projects. Say you have a Free-Style project "Foo" preparing sources, then triggering a Matrix project "Bar" which builds from these sources on various slave machines. Both projects are configured to only keep the latest 10 builds. Looking on the project pages only the latest 10 builds are visible. Same in the project directories (e.g. jobs/Bar/builds). But when you look into the project pages from the slaves, as well as into the sub directories (e.g. jobs/Bar/configurations/axis-label/someslave/builds), all builds ever done are still there. This seems to happen only to Matrix projects called by upstream projects. Standalone Matrix projects seem also been cleaned up in their sub directories. As the Foo-project's build are not kept, clicking on an old build's trigger link within Bar's someslave project page only leads to a 404. Environment: SUSE Linux Enterprise Server 11.1 (x86_64); JDK 1.6.0_26; Jenkins 1.447.1 Project: Jenkins Priority: Major Reporter: Matthias Kraft This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14189) Discover permission gives Status Code 500 and Stacktrace
Matthias Kraft created JENKINS-14189 Discover permission gives Status Code 500 and Stacktrace Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 22/Jun/12 7:01 AM Description: I enabled the Discover permission for Anonymous on an existing job and logged out to see what changed. I was greeted by a Status Code: 500 and a long Stacktrace: Status Code: 500 Exception: org.apache.commons.jelly.JellyTagException: jar:file:/var/lib/jenkins/war/WEB-INF/lib/jenkins-core-1.471.jar!/hudson/model/View/index.jelly:44:43: st:include org.apache.commons.jelly.JellyTagException: jar:file:/var/lib/jenkins/war/WEB-INF/lib/jenkins-core-1.471.jar!/lib/hudson/projectView.jelly:60:22: d:invokeBody Please login to access job Promotion_Reports_Prototype Stacktrace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/lib/jenkins/war/WEB-INF/lib/jenkins-core-1.471.jar!/hudson/model/View/index.jelly:44:43: st:include org.apache.commons.jelly.JellyTagException: jar:file:/var/lib/jenkins/war/WEB-INF/lib/jenkins-core-1.471.jar!/lib/hudson/projectView.jelly:60:22: d:invokeBody Please login to access job Promotion_Reports_Prototype at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:625) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:135) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at
[JIRA] (JENKINS-14189) Discover permission gives Status Code 500 and Stacktrace
Matthias Kraft updated JENKINS-14189 Discover permission gives Status Code 500 and Stacktrace I changed it to Critical as anonymous users are unable to see any content, now. Change By: Matthias Kraft (22/Jun/12 7:07 AM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13269) Unable to connect to LDAP server
[ https://issues.jenkins-ci.org/browse/JENKINS-13269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Kraft closed JENKINS-13269. Fix Version/s: current Resolution: Cannot Reproduce Hm ... it went away with 1.458. I wonder what it was. Unable to connect to LDAP server Key: JENKINS-13269 URL: https://issues.jenkins-ci.org/browse/JENKINS-13269 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: openSUSE 11.4 x86_64, Jenkins 1.457, java.runtime.name=Java(TM) SE Runtime Environment, java.runtime.version=1.6.0_31-b04 Reporter: Matthias Kraft Priority: Critical Fix For: current After switching from 1.456 to 1.457 Jenkins was no longer able to communicate with the LDAP server for authentication. Switching back to 1.456 resolved the issue. Error message and stack trace: Unable to connect to XXLDAPserverXX:3268 : javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 775, vece] javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 775, vece] at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3067) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3013) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2815) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2729) at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:296) at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175) at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193) at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136) at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288) at javax.naming.InitialContext.init(InitialContext.java:223) at javax.naming.InitialContext.(InitialContext.java:197) at javax.naming.directory.InitialDirContext.(InitialDirContext.java:82) at hudson.security.LDAPSecurityRealm$DescriptorImpl.doServerCheck(LDAPSecurityRealm.java:575) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:485) at org.kohsuke.stapler.Stapler.service(Stapler.java:159) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:74) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at
[JIRA] (JENKINS-13269) Unable to connect to LDAP server
Matthias Kraft created JENKINS-13269: Summary: Unable to connect to LDAP server Key: JENKINS-13269 URL: https://issues.jenkins-ci.org/browse/JENKINS-13269 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: openSUSE 11.4 x86_64, Jenkins 1.457, java.runtime.name=Java(TM) SE Runtime Environment, java.runtime.version=1.6.0_31-b04 Reporter: Matthias Kraft Priority: Critical After switching from 1.456 to 1.457 Jenkins was no longer able to communicate with the LDAP server for authentication. Switching back to 1.456 resolved the issue. Error message and stack trace: Unable to connect to XXLDAPserverXX:3268 : javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 775, vece] javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 775, vece] at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3067) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3013) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2815) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2729) at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:296) at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175) at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193) at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136) at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288) at javax.naming.InitialContext.init(InitialContext.java:223) at javax.naming.InitialContext.(InitialContext.java:197) at javax.naming.directory.InitialDirContext.(InitialDirContext.java:82) at hudson.security.LDAPSecurityRealm$DescriptorImpl.doServerCheck(LDAPSecurityRealm.java:575) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:485) at org.kohsuke.stapler.Stapler.service(Stapler.java:159) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:74) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at
