Hi Thorsten, Thanks for your comments. Weird thing is it only happens rarely in production. I have tried to reproduce this locally simulating random user access with no success.
On Wed, May 4, 2016 at 7:11 PM, Thorsten Schöning <tschoen...@am-soft.de> wrote: > Guten Tag Ernesto Reinaldo Barreiro, > am Mittwoch, 4. Mai 2016 um 12:27 schrieben Sie: > > > I have tried to reproduce this locally in "development" and "production" > > modes with no success. Are there any known issues that can cause this? > Any > > leads would be appreciated. > > I often have problems with an error message like yours, not with the > strange ids though, during development, if I e.g. change markup and > just reload a formerly working page in the browser instead of > requesting a new and/or restarting Tomcat. > > So if your customer is not changing markup, he maybe has customers > accessing old versions of pages referencing things in markup which > don't exist anymore because of upgrades and such. > > Mit freundlichen Grüßen, > > Thorsten Schöning > > -- > Thorsten Schöning E-Mail: thorsten.schoen...@am-soft.de > AM-SoFT IT-Systeme http://www.AM-SoFT.de/ > > Telefon...........05151- 9468- 55 > Fax...............05151- 9468- 88 > Mobil..............0178-8 9468- 04 > > AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln > AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Regards - Ernesto Reinaldo Barreiro
