The real problem that I'm hoping to solve is why is OFBiz trying to
create two UserLoginHistory records within one second in the first
place? There is something not right there...
-David
On Apr 27, 2007, at 2:57 PM, Krzysztof Podejma wrote:
go to party manager click logout (upper right c
go to party manager click logout (upper right corner), click login in the
middle, then logout (upper right), and login
if You don't get error try it several times
i think it is mysql timestamp issue, derby has milliseconds in timestamps,
mysql not.
see my comment in jira
Krzysztof Podejma
2007
I guess what I'm looking for is what do you do to make this problem
happen? You mentioned a login twice in one second, but how do you do
that?
-David
On Apr 27, 2007, at 2:45 PM, Krzysztof Podejma wrote:
MySQL and firefox with savet login and password
try to login twice in a one second
MySQL and firefox with savet login and password
try to login twice in a one second and You will get this error in console:
(Duplicate entry 'admin-10011-2007-04-27 22:43:31' for key 1))). Rolling
back transaction.
Krzysztof Podejma
2007/4/27, David E. Jones <[EMAIL PROTECTED]>:
What is your t
What is your test case that is failing now?
-David
On Apr 27, 2007, at 2:17 PM, Krzysztof Podejma wrote:
I showed possible workaround in
https://issues.apache.org/jira/browse/OFBIZ-925
after revs 532993 and 532994 even with my modifications there are
still this
error in console log becaus
I showed possible workaround in
https://issues.apache.org/jira/browse/OFBIZ-925
after revs 532993 and 532994 even with my modifications there are still this
error in console log because visitid doesn't increment anymore ...
without changes in revs 532993 and 532994 worked well
Regards
Krzysztof P
The funny logout/login problem should now be fixed (not the
underlying timestamp resolution problem, but the logout/login loop)
in revs 532993 and 532994.
-David
On Mar 16, 2007, at 9:06 AM, Jonathon -- Improov wrote:
Found the problem. To reproduce problem:
1. Use MySQL
2. Enter a URL
Found the problem. To reproduce problem:
1. Use MySQL
2. Enter a URL like https:partymgr/control/logout
3. Login.
I've fixed it in RequestHandler.java, preventing a "do previous URL" whenever the URL is
"/logout". Brutish, yes, but no more awkward than what was in place originally.
Flow t
I get an error message like "Duplicate entry 'admin-2007-03-12 12:12:44' for key 1" when trying to
login (using user login 'admin'). I'm using MySQL.
To reproduce, simply go to say http:///partymgr/control/login , login successfully, then
logout, then go to http:///partymgr/control/login and th
