Bus & Tasks
Posted 03 November 2006 - 09:08 PM
The issue that my client is having, is that they seem unable to make the Bus & Tasks .dll, make multiple simultaneous calls to the Unix box. Eg. Throw 30 near-simultaneous transactions at it, and call an API that (for test purposes) wastes 3 seconds before returning data - and those 30 transactions here queued and made one-at-a-time, and only ever show 1 B&T kernel spawned by the daemon on the Unix box.
P.s. if you throw any .net code at me, I probably won't understand it, and will simply copy'n'paste it to my client
Posted 06 November 2006 - 01:42 PM
I can open multiple kernels directly from the 'nix box (using the p4task task tester), using a 32-bit windows version of same - it is only when my client makes the calls via their webserver that it fails to open multiple.
But yes, maxkernels and component_users are set adequately.
Posted 06 November 2006 - 04:31 PM
Now have one of our own inhouse developers attempting a similar thing - differences are: 1) using VB and not C#.net; 2) using OCX and not the .dll; 3) windows web server to windows proiv server (rather than windows web server to HP-UX proiv server).
Observationally, the results are the same - only 1 instance of the Bus & Tasks "open" can exist at one time, and concurrent "opens" are queued.
Maybe, if we take this out of the Bus & Tasks context, there is some tip on creating multiple instances?
I do reiterate first, however, that I am completely ignorant of all of this VB,.net etc coding.
Thanks in advance
Posted 11 November 2006 - 03:08 PM
That was an bad idea of someone which PROIV tried to replace using p4com.dll.
.NET and ASP type of pages should use a DLL and not OCX. I dont think even works with the OCX.
Using P4BUS from .net is a very important area of PROIV.
Unfortunately this is in competition to PROIVs home grown web solution Concerto and thats why the bugs/limitations in this area takes the low priority.
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users