Also because weblogic will queue up the requests during server starts up, we always end up with multiple threads calling to the same proc when the class initialization is done. This causes failure for all the future calls to the proc.īecause this proc is a frequent call when the server starts up, we always see trouble in this proc but not in the others. When the same proc being called by multiple threads, the proc compilation is messed up.
#Jrebel weblogic code
Looking at Spring source code of StoredProcedure class, we found the “isCompiled()” method is not synchronized/thread safe. Seems like Spring executed the proc before it was compiled.
We see the proc execute time exception immediately without the “proc compiled” log line. 14:42:04,148 DEBUG () ExecuteThread: '2' for queue: ' (self-tuning)'] RdbmsOperation with SQL compiledīut at times when we have trouble we don’t see the above. : CallableStatementCallback bad SQL grammar On production server, we see SP error when server starts up as below: If all you are doing is monitoring remote boxes then I don't see why you need to use recursion.Recently, I resolved a weird Spring JDBC problem related to stored procedure compilation on multi-threading environment. If you can show us some code we would be in a better position to advise you further. Is it the batch program flow itself that's using up your stack or is it an executable? Or, is it your recursion that's the problem? It might be possible to do whatever you are doing using a different method - if need be, to create a disk file-based stack but this would seriously impede execution time. It might help us understand why you are running out of stack space if you explain what it is you are attempting to do. The exception to this is where there was a bug in the program logic. In batch files there is no way to directly manipulate the stack - nor allocate more memory.Ī recursive program will indeed use the system's stack but I have never come across an occasion when I myself have run out of stack space. Running out of stack space is associated to bad program design.
and (2) now manually delete the sentinel file with: 'DEL SENTINEL' command, and the batch file (in the first DOS box) will grind to an end. While the batch file is running, open up antoher DOS box and (1) try to run another instance of the batch file - it won' run. The following line is for example purposes This is how it would look like in a batch off So, here's an overview of how it works (in English off In other words, the sentinel file can be manually deleted, or deleted using another batch file. The reason the batch file needs to check for the presence of the sentinel file is because you have control of the sentinel file outside of the batch file. Somewhere in the batch file, you need to check that the sentinel file is STILL present, and if it isn't then exit either immediately or gracefully. Then the batch file continues - even looping if necessary. The first thing the batch file does is create a sentinel file.
If it is not present, then the batch file will procede. This has other advantages too -0 for example, you can prevent multiple instances of the same batch file running at the same time.Īt the start of your batch file, it looks to see if a particular file, the sentinel file, is present or not.
0 kommentar(er)
