Hi nillehammer

with further testing on Tomcat I'm finding the following in catalina.out:

Exception in thread "Timer-0" java.lang.NullPointerException
        at
com.mchange.v2.log.log4j.Log4jMLog$Log4jMLogger.isLoggable(Log4jMLog.java:25
5)
        at
com.mchange.v2.resourcepool.BasicResourcePool$CullTask.run(BasicResourcePool
.java:1934)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)

I'm also facing Tomcats Permanent Generation constantly growing with each
re-deploy. Just to mention, don't know, if this is related.


This is the dispatch-method:

        public boolean dispatch(Request request, Response response) throws
IOException {
                String path = request.getPath();
                String[] roles = sitemap.getRoles(path);
                
                logger.debug(roles == null ? "no roles attached" : "roles: "
+ roles.toString());
                
                //no roles defined means access for all
                if (roles == null) { return false; }
                
                User user = auth.getUser();
                
                logger.debug(user == null ? "no user attached" : "user " +
user.getName() + "; groups: " + user.getGroups().toString());
                
                boolean isAuthorized = false;
                for (String roleName : roles) {
                        if (user != null && user.isInGroup(roleName)) {
                                isAuthorized = true;
                        }
                }
                
                logger.debug("isAuthorized: " + isAuthorized);
                
                //if Authorization fails we hand over to the next renderer,
i.e. the PageRender
                if (!isAuthorized) {
                        PageRenderRequestParameters params =
                                new PageRenderRequestParameters(
                                                LOGINPAGE,
                                                new EmptyEventContext());
                        this.renderer.handle(params);
                        return true;
                }
                
                return false;
        }


I'll post, if I can get hold of anything else.

Many thanks
Jens

-- 
Jens Reufsteck
Marketing & Online Director

Staufenbiel Institut GmbH
Events & Recruiting Solutions

Wildunger Straße 6, 60487 Frankfurt am Main
www.staufenbiel.de www.mba-master.de www.absolventenkongress.de

Tel.:  +49 (0)69 25537-140
Fax:   +49 (0)69 25537-2140

Geschäftsführer: Judith Oppitz, Birgit Giesen, Graham Storey, Martin
Halliday
Amtsgericht Köln HRB 9301

Internet communications are not secure and therefore Staufenbiel Institut
GmbH does not accept legal responsibility
for the contents of this message. Any views or opinions presented are solely
those of the author and do not
necessarily represent those of Staufenbiel Institut GmbH unless otherwise
specifically stated.
> -----Original Message-----
> From: nille hammer [mailto:tapestry.nilleham...@winfonet.eu]
> Sent: Monday, November 15, 2010 8:31 PM
> To: Tapestry users
> Subject: Re: RE: contribute mystery
> 
> Hi Jens,
> 
> just to make sure:
> > maybe I wasn't quite clear: on some startups my dispatcher is used (and
than
> > is always used, which is what I want). On other startups (i.e.
restarting
> > jetty/tomcat) the dispatcher is never used. Though log show, that it is
> > instantiated. But then it feels, as if it wasn't included in the
dispatchers
> > chain of commands.
> 
> As far as I understand your mails, your  "AuthorizationDispatcher" is
certainly instanciated
> and contributed on every startup, but in about 50% of the times it feels
like it is not doing
> its work.
> 
> If so, could it be an error in the implementation of your "dispatch()"
method? If you parse
> Strings in the request, maybe in the 50% not working, the Strings are
presented a bit
> differently than in the other cases,  urlencoded characters. Or it
sometimes fails to load its
> dependencies (maybe SiteMap) or loads a mock implementation of that.
> 
> To clarify could you post your dispatch()-method?
> 
> Cheers nillehammer.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to