Re: [Firebird-devel] Concurrency bugs in posting events?

2017-04-10 Thread Adriano dos Santos Fernandes
Here is a better description of the problem and a possible fix that Vlad can use and discard, as he surely better understand this part. Sorry for some imprecision in my previous description. Jaybird synchronized the op_queue_events send/response. Remote queue_events synchronizes with the *sync*

[Firebird-devel] [FB-Tracker] Created: (CORE-5517) Classical server periodically raise "Global mapping memory overflow" and need to be restarted to accept new connections

2017-04-10 Thread Christian Pradelli (JIRA)
Classical server periodically raise "Global mapping memory overflow" and need to be restarted to accept new connections --- Key: CORE-5517 URL:

[Firebird-devel] [FB-Tracker] Created: (CORE-5516) Firebird service crashes when stopping

2017-04-10 Thread JIRA
An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: --- org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getText' in class com.atlassian.jira.web.bean.I18nBean threw exception class

Re: [Firebird-devel] Concurrency bugs in posting events?

2017-04-10 Thread Adriano dos Santos Fernandes
On 10/04/2017 06:17, Mark Rotteveel wrote: > >> This code runs concurrently and find the same empty slot for >> simultaneous events being registered. > In the specific example, Jaybird uses a single connection to register > for events, and it takes a lock on the database handle, so there >

Re: [Firebird-devel] Concurrency bugs in posting events?

2017-04-10 Thread Mark Rotteveel
On 9-4-2017 21:33, Adriano dos Santos Fernandes wrote: > Vlad, > > I think have found the problem in server. > > Look at this: > > > ISC_STATUS rem_port::que_events(P_EVENT * stuff, PACKET* sendL) > { > ... > > Rvnt* event; > for (event = rdb->rdb_events; event; event =

Re: [Firebird-devel] Concurrency bugs in posting events?

2017-04-10 Thread Vlad Khorsun
09.04.2017 22:33, Adriano dos Santos Fernandes wrote: > Vlad, > > I think have found the problem in server. > > Look at this: > > > ISC_STATUS rem_port::que_events(P_EVENT * stuff, PACKET* sendL) > { > ... > > Rvnt* event; > for (event = rdb->rdb_events; event; event =