Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bugcheck 167 (invalid SEND request) in SS when many parallel attachments begin to execute trigger not loaded into metadata cache [CORE1080] #1501

Closed
firebird-automations opened this issue Jan 6, 2007 · 13 comments
Closed

Bugcheck 167 (invalid SEND request) in SS when many parallel attachments begin to execute trigger not loaded into metadata cache [CORE1080] #1501

firebird-automations opened this issue Jan 6, 2007 · 13 comments
Assignees
@hvlad
Labels
affect-version: 1.5.3 affect-version: 2.0.0 fix-version: 2.0.1 fix-version: 2.1 Alpha 1 priority: major type: bug

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @hvlad

Duplicates CORE5

Attachments:
1080.zip

When several parallel attachments begin to execute trigger not loaded into metadata cache first of them will compile trigger request's BLR but others will not wait until request compilation finished. Hence other attachments will execute NULL request. We have protection from such failure in MET_procedure using dbb_sp_rec_mutex but not for triggers

Commits: f42d599 b9d0a9b
@firebird-automations
Copy link
Collaborator Author

Commented by: @hvlad

Extract core-1080.sql and CORE_1080.dpr
run command prompt
set ISC_USER and ISC_PASSWORD variables
change path to database in core-1080.sql
compile CORE_1080.dpr
run isql -i core-1080.sql
run CORE_1080.exe <path_to_database> <number_of_threads>

in my case 128 threads are enough

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

Attachment: 1080.zip [ 10210 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.1 [ 10041 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: skaushanskiy (skaushanskiy)

This is a "duplicate" of
CORE5

that issue can now be closed.

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

Fix Version: 2.0.1 [ 10090 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Link: This issue duplicates CORE5 [ CORE5 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @pcisar

Reopened to update ticket information.

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Closed [ 6 ] => Reopened [ 4 ]

resolution: Fixed [ 1 ] =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Fix Version: 2.1 Alpha 1 [ 10150 ]

Fix Version: 2.1.0 [ 10041 ] =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Reopened [ 4 ] => Closed [ 6 ]

resolution: Fixed [ 1 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 11471 ] => Firebird [ 15399 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

QA Status: No test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hvlad hvlad

Labels
affect-version: 1.5.3 affect-version: 2.0.0 fix-version: 2.0.1 fix-version: 2.1 Alpha 1 priority: major type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hvlad @firebird-automations