Labview gpib timeout when calling cvi dll

Equipment used :
VXI Rack with Slot 0 controller
Labview V5.0.1
Lab Windows V5.0.1
GPIB controlled Power10 I63 PSU
We run an intermediate Labview driver which communicates with a low level CVI driver (dll) to control a PSU. We recently tried to run the Labview driver on a Slot 0 controller and we get timeout errors when waiting for a response after commanding the PSU to switch off ( "CST OFF" is sent , and the driver waits on "ST OFF" being returned - it never does and times out). Ni Spy is on when it fails. In the same driver, a call to return the Instrument ID is carried out happily, with the ID being returned with no errors.
I can run the low level CVI driver with an interactive script and it works fine with no errors.
I can run the Labview driver with NI Spy switched off and it works ok too, Our customer cannot get it to work even with Ni Spy switched off. They have the same setup as us.
Any ideas?

The solution I had previously documented only partly worked. It cleared the timeout error, but I am still experiencing various errors in testing the PSU with Labview (still no problems with running the functions with Labwindows directly). Also, if NISpy is running I see no errors, which still leads me to believe its a timing problem. I saw another thread on here from someone with similar problems and I tried all the recomendations in that, but it still did not fix it. The last recomendation was to re-write the GPIB driver to slow down the message transfer to the instrument!
A link to the thread with similar problems to mine.....
http://forums.ni.com/ni/board/message?board.id=140&message.id=20031
Message Edited by edinsofty1 on 09-09-2008 07:21 AM
Message Edited by edinsofty1 on 09-09-2008 07:21 AM

Similar Messages

LabVIEW 2010 crash when calling user32.dll

Interesting LabVIEW 2010 "feature" I discovered this morning.
Attached are two identical VIs, one saved in 2010 and one saved in 2009. These VIs were specifically written to demonstrate the bug I stumbled upon this afternoon. Each VI when run should allow you to find a specific program (window) open in Microsoft Windows and bring it to the foreground. It relies on "user32.dll" to perform this operation. It also allows you to specify the calling convention for the function call.
In LV 2009, either calling convention works, without error. However, in LV 2010 the calling convention for the function must be "stdcall (WINAPI)" and not the default "C". If the calling convention is "C" then LabVIEW crashes and closes without warning.
If you happen to have both LV 2009 and LV 2010 on your computer, I would love to hear if this phenomenon is duplicated so that I can pinpoint whether the bug is LV 2010 related or is more specific to my personal setup.
Thanks,
~David
Solved!
Go to Solution.
Attachments:
LV2010 test.vi ‏13 KB
LV2009 test.vi ‏14 KB

221113
Return
CLFN with the wrong calling convention may siliently crash LabVIEW.
LabVIEW 8.5 through 2009 could adjust the calling convention at run time if the user selected the wrong option. In 2010 this no longer happens. More information is found in KnowledgeBase 59KB14WI
Workaround: Use the correct calling convention
Reported Version: 2010 32-bit
Resolved Version: N/A
Added: 07/23/2010
From 2010 release notes.
Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA

Trouble when Labview call CVI DLL in after compiled to EXE

Hi,
I m developing a program by LabVIEW, and have to call a DLL, which developed by using CVI.
The UI of the DLL consist of a table and a listbox.
The DLL run smoothly but when I compiled the project to EXE, when the program call the DLL, the DLL won't show properly.
The DLL UI only show the table, and the listbox has "disappeared".
Any common known-problem caused it ? Please advise. Thanks a lot.

Hi Engwei,
I'm not familiar with any such issue. Would it be possible for you to post the corresponding CVI and LabVIEW codes and the built DLL and executable? I would like to investigate this issue further. Also, what version of CVI and LabVIEW are you using?
Thanks!
Joshua de la Llana
NI Applications Engineer

Array limitation when calling VB Dll?

Today I encountered a problem when calling a Visual Basic DLL in Labview 8.2.1
I had to pass a 3D Array, with one dimension exceeding 30 000. around that array size I ended up with error -2146828282 when calling the Dll.
The dll was working fine for weeks. So, is there any limition to the array size, which could cause the error?

Hi sthu,
Having 30,000 elements in one dimension of an array should not cause any problems by itself. The maximum number of elements per dimension in an array is (2^31) – 1 as described in the LabVIEW Help for Grouping Data with Arrays and Clusters. However, this is also dependent upon the memory available in your computer. If there is not enough memory available in RAM, you might receive an error when passing the array to the DLL.
I have included a couple links to pages that discuss LabVIEW memory usage and managing large data sets in LabVIEW. These might help get your application up and running with the larger array sizes.
VI Memory Usage
Managing Large Data Sets in LabVIEW
Donovan

LabVIEW crashes when calling a dll

I am trying to call a dll through my LabVIEW program. The dll implements a routine to access an ftp server. When the server is found, everything works as expected. However, if there is a delay in finding the server, LabVIEW throws an error � �An exception occured within the external code called by the Call Library Node�. The detailed error message is attached here.
The dll function times out after 25 seconds if the server is not found (it returns a signed integer). This error message pops up after roughly 20 seconds.
The dll was created in VC++ 6.0. It uses standard MFC calls.
Any information about why this could be happening will be appreciated.
Thanks.
Attachments:
LabVIEW_error.jpg ‏14 KB

Hi,
If you call a dll, everything should be just right, or it will crash (if you
use LV7, you're lucky, most of the times LV stays alive, and only gives a
message).
The first thing that should be checked is the calling convention. This
should probably be "stdcall (API)". This changes the way the parameters and
return address are pushed to the stack.
The second point are the parameters. Pointers should be set to pointers,
LONG to i32 etc. The return parameter can always be set to i32, or to
nothing.
My best guess is (since the dll crashes after a while), there should be a
pointer to a buffer (most likely a cluster, but could be a reference). The
connection succeeds, and the dll copies the information to the pointer. If
the pointer is not valid (the memory does
not belong to LabVIEW), an
exception is raised.
Perhaps you can give a function prototype? The prototype is the way to
start.
Regards,
Wiebe.
"gopinath" wrote in message
news:[email protected]..
I am trying to call a dll through my LabVIEW program. The dll
implements a routine to access an ftp server. When the server is
found, everything works as expected. However, if there is a delay in
finding the server, LabVIEW throws an error - "An exception occured
within the external code called by the Call Library Node". The
detailed error message is attached here.
The dll function times out after 25 seconds if the server is not found
(it returns a signed integer). This error message pops up after
roughly 20 seconds.
The dll was created in VC++ 6.0. It uses standard MFC calls.
Any information about why this could be happening will be appreciated.
Thanks.

Calling CVI DLL Function from Visual Studio

HI all ,
Iv'e created a DLL using CVI and i'm tring to call one of it's function from visual studio 6.0
I'm getting a general error , is there a specific prototype that i need to set my functions in ordrer to call them ?!
Kobi Kalif
Software Engineer

You will need to distribute the CVI RTE along with your DLL, since anything you write in CVI is going to use the RTE.
As far as calling the DLL functions, you can use the CVI defined macros
<return type> DLLEXPORT DLLSTDCALL <function name> (<param1 type> <param1> ...) {
to declare your functions in the DLL for access by a VS application.
for example
int DLLEXPORT DLLSTDCALL myfunction (int funparam1, double func param2) {
There are options for identifying which functions to export from your DLL, I use "functions marked for export" but there are other choices available. I also include a type library so when you type the name of a DLL funciton in VS6 you see a balloon popup with the function signature. This is a check box in the target settings. You have to create a ".fp" file (function panel file) to collect the function info for the library.
From VB6 you can access the DLL a couple of ways, but I usually add the DLL as a reference.

Stack overflow when calling a DLL

I have developped a DLL in Ada.
I tried to call a function of this DLL from a C++ executable.
My program crashed because of a stack overflow.
Then, I increased the stack size of my program (linker option), and now it
works.
Calling this DLL through the call library function from a 6.0 Labview
program causes the same stack overflow.
How could I increase the stack size of my Labview program ?
Thanks.

Hi,
I have never come across this issue but here are a few things you can try:
1) Change the Calling Convention between C and StdCall(WINAPI). The main difference between the two calling conventions has to do with when the stack is cleaned up. In one method, the stack is cleaned earlier than in the other method.
2) Call your dll with LabVIEW 7.0. You can find the evaluation version of the latest version at http://www.ni.com/labview
Good luck
Feroz

Intermittent problem with TestStand calling CVI DLL calling MSCV DLL

Sorry about cross post, but I am not sure which group is best to address
this issue.
Setup:
Windows 2000 SP1
TestStand 2.01f
CVI 6.0
MSVC++ 6.0 SP5
Problem:
I have a CVI Test Library DLL that contains test functions called by
TestStand using the C/CVI adapter. The CVI Test Library DLL in turn makes
several calls to another DLL written in MSVC++. I am experiencing an
intermittent problem with one of the MSVC functions. The problem ~appears~
to be stack related, but I am not sure. Among other things, this MSVC
function accepts a const char * argument that is a TestStand lookup string.
The function uses this string to access the TestStand API.
What happens is this: Everything works fine. I then recompile the CVI DLL
after making some mod, then run. The MSVC++ DLL asserts that the const char
* arg passed by the CVI DLL is NULL. However, this is not the case if I
single step through the CVI code. It has happened both with passing
variables as the const char * argument and as hardcoded strings literals, so
its not that I am actually passing NULL. The other argument to this
function is the TestStand sequence context dispatch pointer (LPDISPATCH
pobjSequenceContextDisp) and it always ~appears~ to be passed correctly.
The problem is frustrating and hard to debug because I can not
deterministically reproduce it. The problem ~never~ appears when I debug my
MSVC++ DLL in Visual Studio. And it only occasionally appears otherwise.
The problem, when it appears, always appears on the first run after
recompiling the CVI DLL, though the problem does not happen after ~every~
recompilation. I'd say it happens 1 in 6 times after a recompile.
Recompiling the exact same code does not always make the problem disappear.
If I change the CVI code (code that has nothing to do with the argument
itself though) and recompile the problem almost always goes away. Selecting
'Mark all for compilation' and rebuilding does not make the problem go away.
Only tweaking the CVI code and recompiling does (usually).
Whats more, the problem appears:
* With the CVI DLL built as Debug or Release mode.
* With the CVI default calling convention set to __stdcall or __cdecl.
* With the C/CVI TestStand adapter set to run in-process or external
instance of CVI.
The problem appears to be some sort of stack or argument passing problem
between CVI and MSVC, though thats just a guess based on the symptoms. I
have quadruple checked the calling conventions of all declared functions.
The CVI DLL functions all use TX_TEST (which resolves to __cdecl). The MSVC
DLL functions all explicitly use __stdcall. Is there a problem with calling
__stdcall MSVC functions from a __cdecl CVI function?
I can find no other memory leaks or indications of memory corruption
elsewhere in either the CVI or MSVC DLLs. Its only this one function that
exhibits this strange 'null const char *' problem.
Can anyone offer any ideas about what may be causing this problem? Anything
else I should check/verify?
Regards,
Joe

Silvius,
> Although I'm not sure if any of the following are the real cause of
> your problem, I have the following suggestions:
Thanks for the reply. At this point any and all suggestions are welcome...
> 1. There could be a problem with calling
> __stdcall MSVC functions from a __cdecl CVI function. As a workaround
> wrap the _cdecl call inside a _stdcall call that is exposed or
> exported to TestStand or vice-versa. This can be a problem because if
> _cdecl is used, the calling function is responsible for cleaning up
> the stack and if _stdcall is used, the called function is responsible
> for cleaning up the stack.
I was under the impression that as long as everything was explicitly and
consistently declared, you could safely mix cdecl and stdcall f
unction
calls. Is it bad to do this? Is this a known issue with the CVI compiler?
I've never seen a problem with doing this under MSVC++.
I'll try wrapping them in cdecl calls for CVI - though we have a
depressingly large number of stdcall functions in the MSVC DLL ;-). They
need to remain stdcall in the DLL because we also call them from Visual
Basic.
> 2.Don't mix Debug version of one DLL with the Release version of the
> other DLL. I had some bad experiences doing this and both DLLs where
> developed in MSVC. Allways use either Debug either Release versions of
> DLLs.
I verified that the MSVC DLLs were either ALL Debug or Release. I too have
seen nasty problems when MSVC Debug and Release is mixed.
One thing I had not thought of until your reply: What about mixing CVI Debug
DLLs with MSVC Release DLLs? Have you ever seen issues with doing this?
Thanks!
Joe

Timeout when calling long running Oracle Apps Adapter API calls

When making a Oracle Apps Based adapter from ESB, Transactions are getting timedout for running calls (~ > 5 mins)
1) Created a Oracle Apps Adapter to execute a API call that returns, in our case, customer data.
2) Created a BPEL Which invokes this API based Adapter via. a partner link.
3) Following errors for calls which take ~ >5, transaction is timeout, when invoked from BPEL/ESB/SOAP UI Client.
From domain.log
==========
<2009-04-21 18:54:25,718> <DEBUG> <yeruvp.collaxa.cube.ws> <WSIFInvocationHandler::invoke> invoke failed
org.collaxa.thirdparty.apache.wsif.WSIFException: exception during SOAP invoke: Timed out; nested exception is:
     javax.xml.rpc.soap.SOAPFaultException: Timed out
     at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.populateFaultMessage(WSIFOperation_JaxRpc.java:3086)
     at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeOperation(WSIFOperation_JaxRpc.java:1728)
     at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeRequestResponseOperation(WSIFOperation_JaxRpc.java:1473)
     at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.executeRequestResponseOperation(WSIFOperation_JaxRpc.java:1196)
     at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:476)
     at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:436)
     at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:251)
     at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:790)
     at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:395)
     at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:195)
     at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3715)
     at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1655)
     at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:220)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:317)
     at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5710)
     at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1085)
     at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.createAndInvoke(CubeEngineBean.java:132)
     at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.syncCreateAndInvoke(CubeEngineBean.java:161)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
     at com.evermind.server.ThreadState.runAs(ThreadState.java:646)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.TxRequiresNewInterceptor.invoke(TxRequiresNewInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
     at CubeEngineBean_LocalProxy_4bin6i8.syncCreateAndInvoke(Unknown Source)
     at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyType(DeliveryHandler.java:515)
     at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(DeliveryHandler.java:457)
     at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHandler.java:131)
     at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:95)
     at sun.reflect.GeneratedMethodAccessor129.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
     at com.evermind.server.ThreadState.runAs(ThreadState.java:646)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
     at DeliveryBean_RemoteProxy_4bin6i8.request(Unknown Source)
     at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processNormalOperation(SOAPRequestProvider.java:451)
     at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processBPELMessage(SOAPRequestProvider.java:274)
     at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processMessage(SOAPRequestProvider.java:120)
     at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:956)
     at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
     at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:466)
     at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
     at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96)
     at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
     at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:396)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:410)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)
Caused by: javax.xml.rpc.soap.SOAPFaultException: Timed out
     at oracle.j2ee.ws.client.StreamingSender._raiseFault(StreamingSender.java:568)
     at oracle.j2ee.ws.client.StreamingSender._sendImpl(StreamingSender.java:396)
     at oracle.j2ee.ws.client.StreamingSender._send(StreamingSender.java:112)
     at oracle.j2ee.ws.client.dii.CallInvokerImpl.directInvoke(CallInvokerImpl.java:726)
     at oracle.j2ee.ws.client.dii.BasicCall.directInvoke(BasicCall.java:743)
     at oracle.j2ee.ws.client.dii.BasicCall.invoke(BasicCall.java:649)
     at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeOperation(WSIFOperation_JaxRpc.java:1714)
     ... 83 more
<2009-04-21 18:54:25,721> <ERROR> <yeruvp.collaxa.cube.ws> <WSIFInvocationHandler::invoke> Fault happened: exception during SOAP invoke: Timed out; nested exception is:
     javax.xml.rpc.soap.SOAPFaultException: Timed out
<2009-04-21 18:54:25,752> <DEBUG> <yeruvp.collaxa.cube.engine> AJPRequestHandler-RMICallHandler-61, a4 <invoke> partner OrgCustAdapter_pl, wikey:7990001-BpInv0-BpSeq0.3-3, bpel code line:84, Connection info:oracle_jdbc_driver_T4CConnection_Proxy@17f3851, connection hashCode:25114705, autocommit:false, Transaction info:[Transaction : orabpel : Xid( Global Id 1b.16.00.7d.00.00.00.00.2f.d3.6d.ca.20.01.00.00.17.41.03.00.00.00.00.00, Format Id 1330790740)], jtaTxState:1, CubeInstance:7990001, Process name:testCustomer_BPEL
Now looking to troubleshoot this Timed out issue.
i, Does this need to increase any configuration file timeout parameter on EBS Adapter or other component ?
Any suggessions to fix/towards resolution is appricated.
Thanks,
sgaraga

After increasing sync-time-out and global transaction time out to 1800. Issue is still reported.
We are not using the jdbc pool.
Still not sure what we are missing here and running into this:
WSIFInvocationHandler::invoke> invoke failed
org.collaxa.thirdparty.apache.wsif.WSIFException: exception during SOAP invoke: Timed out; nested
exception is:
javax.xml.rpc.soap.SOAPFaultException: Timed out
In addition:
========
Tested calling this PL/SQL API (exactly the same API CALLED in BPEL) in TOAD and this ran for 20 mts in DB.
With the changes(sync-time-out,global transaction time,hpptd.conf, and transaction-manager.xml ) in SOA configuration then we are getting the exception ..
So, we need help with SOA configuration to get the BPEL service working when the API called within BPEL service is taking approximately 20 mts.
Edited by: sgaraga on Apr 22, 2009 4:29 PM

Timeout when calling Oracle Apps Adapter API calls.

1) Create a Oracle Apps Adapter to execute a API call that returns, in our case, customer data.
2) Create a BPEL Which invokes this API based Adapter via. a partner link.
Observations:
A) Posts the following errors for calls which take ~ >5, transaction is timeout, when invoked from BPEL/ESB/SOAP UI Client.
<2009-04-21 18:54:25,718> <DEBUG> <yeruvp.collaxa.cube.ws> <WSIFInvocationHandler::invoke> invoke failed
org.collaxa.thirdparty.apache.wsif.WSIFException: exception during SOAP invoke: Timed out; nested exception is:
     javax.xml.rpc.soap.SOAPFaultException: Timed out
     at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.populateFaultMessage(WSIFOperation_JaxRpc.java:3086)
     at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeOperation(WSIFOperation_JaxRpc.java:1728)
     at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeRequestResponseOperation(WSIFOperation_JaxRpc.java:1473)
     at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.executeRequestResponseOperation(WSIFOperation_JaxRpc.java:1196)
     at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:476)
     at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:436)
     at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:251)
     at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:790)
     at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:395)
     at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:195)
     at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3715)
     at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1655)
     at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:220)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:317)
     at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5710)
     at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1085)
     at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.createAndInvoke(CubeEngineBean.java:132)
     at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.syncCreateAndInvoke(CubeEngineBean.java:161)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
     at com.evermind.server.ThreadState.runAs(ThreadState.java:646)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.TxRequiresNewInterceptor.invoke(TxRequiresNewInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
     at CubeEngineBean_LocalProxy_4bin6i8.syncCreateAndInvoke(Unknown Source)
     at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyType(DeliveryHandler.java:515)
     at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(DeliveryHandler.java:457)
     at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHandler.java:131)
     at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:95)
     at sun.reflect.GeneratedMethodAccessor129.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
     at com.evermind.server.ThreadState.runAs(ThreadState.java:646)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
     at DeliveryBean_RemoteProxy_4bin6i8.request(Unknown Source)
     at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processNormalOperation(SOAPRequestProvider.java:451)
     at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processBPELMessage(SOAPRequestProvider.java:274)
     at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processMessage(SOAPRequestProvider.java:120)
     at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:956)
     at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
     at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:466)
     at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
     at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96)
     at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
     at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:396)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:410)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
     at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)
Caused by: javax.xml.rpc.soap.SOAPFaultException: Timed out
     at oracle.j2ee.ws.client.StreamingSender._raiseFault(StreamingSender.java:568)
     at oracle.j2ee.ws.client.StreamingSender._sendImpl(StreamingSender.java:396)
     at oracle.j2ee.ws.client.StreamingSender._send(StreamingSender.java:112)
     at oracle.j2ee.ws.client.dii.CallInvokerImpl.directInvoke(CallInvokerImpl.java:726)
     at oracle.j2ee.ws.client.dii.BasicCall.directInvoke(BasicCall.java:743)
     at oracle.j2ee.ws.client.dii.BasicCall.invoke(BasicCall.java:649)
     at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeOperation(WSIFOperation_JaxRpc.java:1714)
     ... 83 more
<2009-04-21 18:54:25,721> <ERROR> <yeruvp.collaxa.cube.ws> <WSIFInvocationHandler::invoke> Fault happened: exception during SOAP invoke: Timed out; nested exception is:
     javax.xml.rpc.soap.SOAPFaultException: Timed out
<2009-04-21 18:54:25,752> <DEBUG> <yeruvp.collaxa.cube.engine> AJPRequestHandler-RMICallHandler-61, a4 <invoke> partner OrgCustAdapter_pl, wikey:7990001-BpInv0-BpSeq0.3-3, bpel code line:84, Connection info:oracle_jdbc_driver_T4CConnection_Proxy@17f3851, connection hashCode:25114705, autocommit:false, Transaction info:[Transaction : orabpel : Xid( Global Id 1b.16.00.7d.00.00.00.00.2f.d3.6d.ca.20.01.00.00.17.41.03.00.00.00.00.00, Format Id 1330790740)], jtaTxState:1, CubeInstance:7990001, Process name:testCustomer_BPEL
Now i am looking to troubleshoot this Timed out issue.
i, Does this need to increase any configuration file timeout parameter on EBS Adapter or other component ?
Any suggestions to fix/towards resolution is appreciated.
Thanks,
sgaraga

After increasing sync-time-out and global transaction time out to 1800. Issue is still reported.
We are not using the jdbc pool.
Still not sure what we are missing here and running into this:
WSIFInvocationHandler::invoke> invoke failed
org.collaxa.thirdparty.apache.wsif.WSIFException: exception during SOAP invoke: Timed out; nested
exception is:
javax.xml.rpc.soap.SOAPFaultException: Timed out
In addition:
========
Tested calling this PL/SQL API (exactly the same API CALLED in BPEL) in TOAD and this ran for 20 mts in DB.
With the changes(sync-time-out,global transaction time,hpptd.conf, and transaction-manager.xml ) in SOA configuration then we are getting the exception ..
So, we need help with SOA configuration to get the BPEL service working when the API called within BPEL service is taking approximately 20 mts.
Edited by: sgaraga on Apr 22, 2009 4:29 PM

Error when calling external DLL function.

When calling a function in Oracle, the error happens
ORA-28575: '... error RPC connection to external procedures'
code:
create or replace library LibFunctions as 'c:\MyDLL.dll';
grant all PRIVILEGES on LibFunctions to public;
create or replace
FUNCTION Max(num1 in number, num2 in number) RETURN number IS
EXTERNAL LIBRARY LibFunctions
NAME "Max"
LANGUAGE C;
grant all PRIVILEGES on Max to public;
obs. Dll was created in Pascal.
What can this error?
tks,
Mauricio
Edited by: user13794390 on 19/01/2011 06:29

It's been a while since I used extproc. Anyway, it listener.ora make sure extproc is added. I'll assume you are on Unix:
(SID_DESC =
(SID_NAME = PLSExtProc)
(ENVS = "EXTPROC_DLLS=ANY,LD_LIBRARY_PATH=proper-directory-list")
(ORACLE_HOME = path-to-oracle-home)
(PROGRAM = extproc)
) SY.

TimeOut when calling RemoteWorklistServiceClient.getWorklistTasks

Hi
I have now approx. 1500 open usertasks
and my worklist application for evaluating tasks began
to timeout on call RemoteWorklistServiceClient.getWorklistTasks
Here is code sniplet ( taken from examples and working )
// 1. get a handle to the remove worklist service client
RemoteWorklistServiceClient client = new RemoteWorklistServiceClient();
client.init();
// 2. set approver's user and password
String user = "bpeladmin";
String password = "welcome";
System.out.println("worklistapp: connecting as " + user);
// 3. get worklist context for user
IWorklistContext ctx = client.authenticateUser(user, password);
System.out.println("worklistapp: got Worklist Context");
// 4. set filters for retrieving My tasks with Assigned status
Map filterMap = new HashMap();
filterMap.put(IWorklistService.FILTER_TYPE_TASK_FILTER,
IWorklistService.TASK_FILTER_MY);
filterMap.put(IWorklistService.FILTER_TYPE_STATUS_FILTER,
IWorklistService.STATUS_FILTER_ASSIGNED);
List tasks = client.getWorklistTasks(ctx,
filterMap,
IWorklistService.SORT_FIELD_TASK_TITLE,
IWorklistService.SORT_ORDER_ASCENDING);
Could you please advice me how to increase timeout
or possibly write better code for comleting tasks?
Thanks
Karel

Hi
i answer myself
run following query
select * from pc_task where state='ASSIGNED' and owner='bpeladmin' and title like 'xy%';
grab taskid and call client.customTaskOperation(context, taskid, action)
Karel

Input parameter setting when calling a DLL(Built from LabVIEW and a kind of VISA communication driver) in Teststand.

In labVIEW7.1 I wrote a COM port communications driver by using "VISA Write/Read". I put a string as the input of "VISA Write" and made it the input of the whole vi. Then I converted the vi into a DLL, which is called in Teststand3.1 by specifying DLL adapter. In "Edit C/C++ DLL Call" dialog, I pass a message of "60 6A 94 80 86 81" as the input parameter. My problem is I tried three kinds of methods to pass the message, see attached 1.jpg,2.jpg and 3.jpg. and found the first one sometimes doesn't work, the second work fine and the last doesn't work all time. I don't know why the first one and last one don't work well.
Thanks!
Jacky
Attachments:
31.jpg ‏38 KB
11.jpg ‏36 KB
21.jpg ‏49 KB

Hi Srinivas,
Just another note, I noticed that the Math Interface Toolkit version (MIT) 1.0 is not compatible with LabVIEW 7.1. You’ll need version 1.0.1. of the MIT toolkit in order for it to work with LabVIEW 7.1.
The LabVIEW 7.0 lvanlys.dll is also attached. I had to rename it with a .txt extension, so you’ll want to delete the extension.
Kileen
Attachments:
lvanlys.dll.txt ‏516 KB

Error when calling a DLL function

Hi,
I am using external C++ code with labView. One of the DLL functions I use serves to call files. The directory and the name of the file is is passed as a parameter for this function. When the VI is running and arrives at this function (I use the Calling Library Function Node tool), the following message is displayed:
ERREUR de type class boost::filesystem::filesystem_error.
boost::filesystem:ath: invalid name "D:\Documents Johan\Johan\Stitching\Fichiers de mesure\front parfait\13z2" in path: "D:\Documents Johan\Johan\Stitching\Fichiers de mesure\front parfait\13z2"
I do not know why this message is sent to me.
Thanks for your answer
JF

Hello,
How are you passing the file path to the DLL -- are you passing it as a
string? If you are passing at as a string, I would do some basic
console output to make sure that your DLL is receiving the file path
corectly as a string and perform your appropriate C++ function in your
DLL. If the error is occuring with passing the file path you
might want to check out the links below for a little more information
on this.
http://zone.ni.com/devzone/conceptd.nsf/webmain/7d6a20fe02edbf318625690700704cf3#4
http://digital.ni.com/public.nsf/websearch/4E9234BA4C7C4ABE86256E3C0074760F?OpenDocument
http://digital.ni.com/public.nsf/websearch/3B994675B17C654A86256FDD00754DD2?OpenDocument
Hope this helps,
Travis M
NI
Travis M
LabVIEW R&D
National Instruments

VB6 applications crashes when calling C# dll's in production environment

Hi All,
I'm basically .NET developer, not much aware of VB language or VB visual Basic 6.0.
We are trying to work out with VB application running/ using C# dll's. The scenario is like VB exe applications using C# dll's and C# dll's are referenced to VB application using .tlb file.
In development environment(debug mode) the application looks fine and working as expected. But when the same code is put into production environment VB applications are crashing when pointing to C# method calls. We trying to know the reason but application
is getting killed. The issue seems to be sporadic and not able to catch in MsgView(debug tool).
In one more scenario, the VB application is loading C# form and getting data back to VB but when we repeat the same workflow again application is crashing either in 2nd attempt or 3rd attempt.
Has anybody seen such issue? Any input is welcomed.
Thanks,
Shesh

Hi Shesh.ugare
Welcome to MSDN.
I am afraid that these forums donot support VB6, you could refer to this thread:
Where to post your VB 6 questions
If this issue regarding VB6 then you could consider posting this issue in these forums below:
These forums do not support Visual Basic 6, however there are many third-party support sites that do. If you have a VB6-related question please visit these popular forums:
VB Forums
VB City
If not, then you could share more detailed code with us.
Thanks for your understanding.
Regards.
Youjun Tang
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Labview gpib timeout when calling cvi dll

Similar Messages

Maybe you are looking for