on 2019 May 21 3:39 PM
Hello!
I have some clients running on ASA9 server, and one problem is in bothering. Whenever there are two (or more) simultaneous login requests via JDBC, any of the requests returns a JZ00L exception. I confirmed this behavior in the lab, wrote a program that performs infinite connections to the database, and when I fire the second instance of the program, the JZ00L error is generated in one of the running instances. Is this the expected behavior? Is there a way to resolve this situation?
Thank's
"Login procedure (ID: 758) caused SQLSTATE '<sqlstate>'!" is not a SQL Anywhere message. Your database must have a custom login procedure that is encountering errors. The errors reported were SQLState 42W18 is User '%1' has the row in '%2' locked and SQLSTATE 23W01 is Primary key for table '%1' is not unique: Primary key value ('%2'). Does that custom login procedure when it encounters an error cause the error SQLE_INVALID_LOGON to be reported? The login_procedure database option should point to the procedure that is used at login and can be used to determine if there is a custom login procedure.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
70 | |
10 | |
10 | |
7 | |
6 | |
6 | |
6 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.