sorry tim .... i was asking for help and just for giving more help to fix
it ....

The problem is that we get the authorization problem logged more times than
before the upgrade, it is not a question about the filter, as i though, it
is working well sorry

On Thu, Dec 15, 2016 at 2:47 PM, Tim Bain <[email protected]> wrote:

> It's still Log4J, if that's what you're asking.
>
> You're more likely to get help with your original question by posting
> specific details about the problems you're encountering than by your
> current approach of saying "Something's broken, did anything change in the
> past five years of active development?"
>
> Tim
>
> On Dec 15, 2016 2:01 AM, "ALi" <[email protected]> wrote:
>
> > has something changed in logging from 5.8 to 5.13?
> >
> > On Mon, Dec 12, 2016 at 4:31 PM, ALi <[email protected]> wrote:
> >
> > > this is the code .....as authorization plugin
> > >
> > >
> > >  private void validateIfCreationDateIsExpired(long now, long
> > creationDate)
> > >   {
> > >     if (now > creationDate + this.minutesToExpire * 60000) {
> > >       String creationDateAsString = DATE_FORMAT.format(new
> > > Date(creationDate));
> > >
> > >       String nowAsString = DATE_FORMAT.format(new Date(now));
> > >       LOG.error("La fecha de creacion del token {} cumplio el tiempo de
> > > expiracion ({} minutos) sobre la fecha actual {}. Si esto sucede con
> > mucha
> > > frecuencia se recomienda revisar fecha y hora del servidor", new
> > Object[] {
> > > creationDateAsString, Integer.valueOf(this.minutesToExpire),
> nowAsString
> > > });
> > >
> > >       throw new SecurityException("La fecha " + creationDateAsString +
> "
> > > cumplio el tiempo de expiracion de " + this.minutesToExpire + " minutos
> > > sobre la fecha actual " + nowAsString);
> > >     }
> > >   }
> > >
> > >
> > > i dont know why as authorization code it is given much more exceptions
> > > ..... :(
> > >
> > > On Mon, Dec 12, 2016 at 2:02 PM, ALi <[email protected]> wrote:
> > >
> > >> We implemented a filter in activemq to validate messages from the date
> > >> sended, and we are having more issues in 5.13.2 than in  5.8, has the
> > >> filter implementation changed so much?
> > >>
> > >
> > >
> >
>

Reply via email to