8 replies to this topic

[Rick Young]

Anyone have experience with Bus & Tasks calls from a windows web server, to a Unix ProIV server? Even more specifically, in a .net and IIS environment?


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.


Thanks

Rick

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

[Chris Mackenzie]

Have you checked the MAXKERNELS setting?

and is COMPONENT_USERS set ?

[Rick Young]

The problem is at the windows .dll side, and must be to do with how they are trying to instantiate the .dll - something to do with "apartments" but I'm way out of my knowledge base on that one. Zero doubt.

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.

-Rick

[Rick Young]

Minor update

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
Rick

[Rick Young]

Soooo

the official word: p4com.dll is serialised only. p4api is not "thread safe", which therefore means it does not support multi-threading.

Unhappy.

[deepghosh]

Dont Use pro4_api.ocx. Its evil.

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.

[Rick Young]

Thanks for your input Deep.

We'll be looking at alternatives shortly.

[Mike Schoen]

Does anyone have access to (and can share with me) the pro-iv java bus/task interface?
We've heard that this does exist, but I dont know where to get a copy of it. It doesnt install with pro-iv, that only installs the c libraries.

[Joseph Bove]

Deep,

Dont Use pro4_api.ocx. Its evil.

I love your straightforward advice!

Regards,

Joseph