Timeout when implemented Flowbox

hi everyone,
i met a problem when implemented the Flowbox,i created more than one flowbox instance on the stage then used code to add child into them dynamicly.but it blocked throwing timeout error.
i did a simple demo to reproduce it,please see the code as below :
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml"
                    layout="absolute"
                    xmlns:local="*">
     <local:FlowBox id="box1"
                       x="10"
                       y="188"
                       width="226"
                       height="133"
                       borderStyle="solid"
                       borderColor="#E36410"
                       borderThickness="2"/>
     <local:FlowBox id="box2"
                       x="290"
                       y="188"
                       width="223"
                       height="138"
                       borderStyle="solid"
                       borderColor="#37E015"
                       borderThickness="2"/>
     <local:FlowBox id="box3"
                       x="562"
                       y="188"
                       width="194"
                       height="133"
                       borderStyle="solid"
                       borderColor="#179EFC"
                       borderThickness="2"/>
     <mx:Button click="add()"
                  x="290"
                  y="77"
                  label="add"/>
     <mx:HSlider minimum="1"
                    maximum="100"
                    id="sl"
                    liveDragging="true"
                    x="353"
                    y="128"
                    snapInterval="1"
                    value="1"/>
     <mx:Script>
          <![CDATA[
               import mx.collections.ArrayCollection;
               import mx.containers.BoxDirection;
               import mx.controls.Label;
               private function add():void
                    var arr:ArrayCollection=new ArrayCollection();
                    for (var i:int=0; i < sl.value; i++)
                         var s:String=String(Math.random().toFixed(int(Math.random() * 10)));
                         var lbl:Label=new Label();
                         lbl.text=s;
                         box1.addChild(lbl);
                    for (var i:int=0; i < sl.value; i++)
                         var s:String=String(Math.random().toFixed(int(Math.random() * 10)));
                         var lbl:Label=new Label();
                         lbl.text=s;
                         box2.addChild(lbl);
                    for (var i:int=0; i < sl.value; i++)
                         var s:String=String(Math.random().toFixed(int(Math.random() * 10)));
                         var lbl:Label=new Label();
                         lbl.text=s;
                         box3.addChild(lbl);
          ]]>
     </mx:Script>
     <mx:Label x="255"
                 y="128"
                 text="element count:"/>
</mx:Application>
Thanks very much 

Hi,
There is no setting to increase the default timeout of 10 minutes for the Metapedia import process. If the Excel import file is so large that the import process times out, the import file will need to be split into multiple smaller import files that are imported separately.
or else
just try to import only the recent added categories and terms.
Thanks
Krishna

Similar Messages

  • Re: [iPlanet-JATO] Re: session timeout when not submitting to a handler

    Mark--
    I know what's happening here, but am curious about your approach. You said
    in an earlier email that you were generating links directly to JSPs, but
    from what you are describing, you are generating JATO-style links to access
    JATO pages. Nothing wrong with that, but there is a signficant difference.
    Actually, it just occurred to me, I'm wondering what your URLs look like.
    The way the request dispatching works in JATO is it ignores anything after
    an initial "." in the final part of the URL path. For example, a request
    for "/myapp/module1/MyPage.jsp" doesn't actually try to hit the JSP, instead
    it tries to hit the JATO page "/myapp/module1/MyPage".
    The end result is that you may think you are accessing a JSP directly, but
    are instead accessing a JATO page. The reason the request dispatching works
    this way is because it is illegal to access JATO JSPs directly, and there is
    actually a (disabled) JATO feature that piggybacks on the use of the
    dot-delimited URL.
    So, now I need to understand your intent. I wasn't really sure why you were
    generating direct JSP/page links to begin with. This works against the Type
    II architecture JATO uses, in which all JATO requests go back to the
    controller servlet.
    If you are trying to design something like a menu page, you may have thought
    that it was burdensome to create a number of HREF children, plus implement
    event handlers for each of them. This definitely would be burdensome beyond
    just a handful of links, but this is why JATO provides other mechanisms for
    doing what I'll call here "polymorphic HREFs".
    Assuming this menu page scenario, the easiest thing to do is to simply use
    one HREF child on the page, and add a value to it each time it is rendered
    that distinguishes it from the other instances on the page. In your event
    handler for the HREF, you simply check this value and use it to decide which
    page to forward to. You can add a value to an HREF or Button by using the
    "addExtraValue()" method. Or, if you are using JATO 1.2, you can add extra
    query string NVPs right in the JSP document using the "queryParams"
    attribute of the <jato:href> tag. Thus, your one HREFchild and event
    handler become "polymorphic" because what they do depends on the context in
    which they are invoked.
    Now, I still don't have confirmation that this is what you were trying to
    do, so until I do, let me explain the exception you're seeing. JATO assumes
    that when a request comes in for a page that includes the pageAttributes
    NVP, it is a request coming from a previously generated JATO page. Because
    of the way JATO works, this means that the request dispatching code should
    send the request back to the originally rendered page. For example, if Page
    A renders an HREF, which the user then activates, JATO sends the request
    back to Page A for handling. All of the HREFs and forms generated during
    rendering of Page A actually refer back to Page A, regardless of where those
    links or buttons actually pass the request in their event handlers/Command
    objects.
    So, what's happening when you include the pageAttributes in your HREFs is
    that JATO is assuming that a request is being sent to the target page, with
    the assumption that the target page has a mechanism in place to handle the
    request. This assumption relies on the specification of the "originator" of
    the request being specified in the request. For links/HREFs, the name and
    value of the HREF is sent along with the request. For forms, the name and
    value of the button that was pressed are sent in the request. JATO uses the
    presence of these name/value pairs to decide which event handler, or which
    Command object, to invoke to handle the request.
    The exception you are receiving is saying that there was no object on the
    target page that indicated it could handle the request. This is to be
    expected, since you have not specified a query parameter that indicates
    which CommandField child is responsible the request. However, this is where
    I see the disconnect, because that is not what I believe you were trying to
    do (as explained above).
    So now, given all the information above, can you tell me what you're trying
    to accomplish, and whether or not the info I've given you has helped you to
    design a mechanism more in line with a JATO approach? If not, given that I
    understand what you're trying to do, I can offer a more concrete solution.
    Todd
    ----- Original Message -----
    From: <Mark_Dubinsky@p...>
    Sent: Monday, November 05, 2001 2:54 PM
    Subject: [iPlanet-JATO] Re: session timeout when not submitting to a handler
    This is the exception we get:
    (And BTW, leaving a blank value for the pageAttributes doesn't help)
    [05/Nov/2001 17:49:18:4] error: <portalServlet.processRequest>
    javax.servlet.ServletException: The request was not be handled by the
    specified handler
    at java.lang.Throwable.fillInStackTrace(Native Method)
    at java.lang.Throwable.fillInStackTrace(Compiled Code)
    at java.lang.Throwable.<init>(Compiled Code)
    at java.lang.Exception.<init>(Compiled Code)
    at
    javax.servlet.ServletException.<init>(ServletException.java:107)
    at
    com.putnaminvestments.common.jato.ApplicationServletBase.dispatchRequ
    est(Compiled Code)
    at
    com.putnaminvestments.common.jato.ApplicationServletBase.processReque
    st(Compiled Code)
    at
    com.putnaminvestments.bp.portal.portalServlet.processRequest(Compiled
    Code)
    at
    com.putnaminvestments.common.jato.ApplicationServletBase.doPost(Compi
    led Code)
    at
    com.putnaminvestments.common.jato.ApplicationServletBase.doGet(Compil
    ed Code)
    at javax.servlet.http.HttpServlet.service(Compiled Code)
    at com.putnaminvestments.bp.bpServletBase.service(Compiled
    Code)
    at javax.servlet.http.HttpServlet.service(Compiled Code)
    at
    com.netscape.server.servlet.servletrunner.ServletInfo.service(Compile
    d Code)
    at
    com.netscape.server.servlet.servletrunner.ServletRunner.execute(Compi
    led Code)
    at com.kivasoft.applogic.AppLogic.execute(Compiled Code)
    at com.kivasoft.applogic.AppLogic.execute(Compiled Code)
    at com.kivasoft.thread.ThreadBasic.run(Native Method)
    at com.kivasoft.thread.ThreadBasic.run(Native Method)
    at com.kivasoft.thread.ThreadBasic.run(Native Method)
    at com.kivasoft.thread.ThreadBasic.run(Native Method)
    at com.kivasoft.thread.ThreadBasic.run(Compiled Code)
    at java.lang.Thread.run(Compiled Code)
    --- In iPlanet-JATO@y..., "Todd Fast" <Todd.Fast@S...> wrote:
    Mark--
    Initially we tried to add the pageAttributes NVP as well, but that
    was
    causing an exception, so we stopped doing that.That's odd--what was the exception?
    Our problem now is that when the SessionTimes out it does not go
    to
    onSessionTimeout method as in processRequestMethod of the
    ApplicationServletBase it looks for pageAttributes. If it is notnull
    then only onSessionTimeOut method is called.This is sadly the only technique for determining if a session hastimed out
    and a new one been created, versus the initial creation of thesession.
    Is there any work around for this? Maybe you can suggest how topass
    the pageAttributes without causing the initial exception?Definitely--let me know what the exception was and I'll be able tosuggest
    something. However, it shouldn't really be any harder thanappending a
    "jato.pageAttributes=" empty NVP on the HREF.
    Todd
    Todd Fast
    Senior Engineer
    Sun/Netscape Alliance
    todd.fast@s...
    For more information about JATO, please visit:
    http://developer.iplanet.com/tech/appserver/framework/index.jsp

    OK, here's what I'm trying to do: We have, like you said, a menu
    page. The pages that it goes to and the number of links are all
    variable and read from the database. In NetD we were able to create
    URLs in the form
    pgXYZ?SPIDERSESSION=abcd
    so this is what I'm trying to replicate here. So the URL that works
    is
    pgContactUs?GXHC_GX_jst=fc7b7e61662d6164&GXHC_gx_session_id_=cc9c6dfa5
    601afa7
    which I interpreted to be the equivalent of the old Netd way. Our
    javascript also loads other frames of the page in the same manner.
    And I believe the URL-rewritten frame sources of a frameset look like
    this too.
    This all worked except for the timeout problem. In theory we could
    rewrite all URLs to go to a handler, but that would be...
    inconvenient.

  • Return 504 Gateway TimeOut when access exchange service by domain/user and password

    hi,
    here is the scenario: a user of our app is in ntdev domain, and his exchange server located at apj.cloudmail.microsoft.com. our backend api is deployed at the Azure servers at US West.
    our api get 504 Gateway Timeout when calling the
    FindFolders API of exchangeService. does anyone know how to fix this issue? the following is the core code:
    var
    service = newExchangeService(ExchangeVersion.Exchange2010);
    service.Credentials =
    newNetworkCredential(username,
    password, domain);
    service.AutodiscoverUrl(emailAddress, RedirectionUrlValidationCallback);
    service.FindFolders(
    WellKnownFolderName.Root,
    newFolderView(1));

    That doesn't sound like its an EWS issue more an issue with the Network path your trying to traverse to the Exchange Server. My suggestion is that you test EWS using the EWSeditor
    https://ewseditor.codeplex.com/ (eg it sounds like you may have proxy server that expecting authentication etc.).
    Cheers
    Glen

  • 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

  • Graphics tab in REBDBU: Internal error when implementing extension

    Hello,
    Seek your kind help please.
    I have entered in the building master data using REBDBE. We have a tab called Graphics. The pictures etc of the building are uploaded using a software called Korasoft. When i am clicking on the Graphics tab, it is entering the screen but immediately afterwards flashing the following message, "Internal error when implementing extension".
    Doing a F1 on the error message shows the foll details:
    "Diagnosis
    An internal error occurred during the implementation of a customer-specific enhancement. A CHANGE-API module was called with an object reference (parameter IO_OBJECT) that was not instantiated in the required activity for changing (02). The API modules are function modules and begin with API_RE_.
    Procedure
    Within the BAdI implementation, transfer the parameter IO_OBJECT from the BAdI method directly to the API module. Make sure that the transferred instance is allowed to be changed."
    I found that the SAP note 1139014 causes this error message to be generated. Note 1139014 forms a part of support pack level 13 (release 600). Recently we have upgraded our systems from support pack level 8 to support pack level 13. Naturally even this note got implemented at that time.
    But now this note is causing this error message and so I will be grateful if someone can please tell me how to rectify the error.
    Regards,
    Suvarghya Dutta
    Edited by: Suvarghya Dutta on Feb 11, 2009 5:30 PM

    Hi Fabio,
    I would kindly ask you appy the SAP note [1521903|https://service.sap.com/sap/support/notes/1521903] and proceed as described in the note to resolve the issue.
    Hope this information is helpful for you.
    Regards, Franz

  • Internal error when implementing extension

    Hello everyone
    At the moment I create a new contract (transaction RECN) an error occurs and I can not solve.
    Someone could help me?
    Internal error when implementing extension (see long text)
    Message no. RECAAP093
    Diagnosis
    Call of GET_EXTENSION( ) method for enhancement CL_FILACI_VICN01_EXTENSION failed.
    It tried to use an add-on or customer-specific enhancement that is not implemented in your system.
    To be able to determine the technical attributes of enhancement CL_FILACI_VICN01_EXTENSION, the RECA_STORABLE_EXT Business Add-In has to supply the desired information. However, this was not the case. In an implementation of RECA_STORABLE_EXT, the GET_OBJNAME_EXT( ) method must supply the required enhancement CL_FILACI_VICN01_EXTENSION.
    Below is example code for GET_OBJNAME_EXT( ):
    CASE ID_OBJNAME_STD.
        WHEN '...'.
          APPEND 'CL_FILACI_VICN01_EXTENSION' TO CT_OBJNAME_EXT.
      ENDCASE.
    For more information, refer to the documentation for the RECA_STORABLE_EXT Business Add-In.
    Start BAdI Builder
    Procedure
    Contact your system administrator.
    tks a lot!

    Hi Fabio,
    I would kindly ask you appy the SAP note [1521903|https://service.sap.com/sap/support/notes/1521903] and proceed as described in the note to resolve the issue.
    Hope this information is helpful for you.
    Regards, Franz

  • Downloading timeout when installing flash player 11.5.502.149 on mac osx ?

    Downloading timeout when installing flash player 11? I have a new MacBook Pro. I have OS 10.8.2. I cannot get FlashPlayer to download. I have tried uninstalling and reinstalling Adobe Flash Player 11 from the Adobe website. Doesn't work. Every time I try to download, I get an error message that says "downloading timeout at 47%" Can someone PLEASE help? I've spent hours with this and am very frustrated.Check if Flash Player is installed on your computer on adobe website: blocked plug-in

    http://fpdownload.macromedia.com/get/flashplayer/current/licensing/mac/install_flash_playe r_11_osx.dmg

  • Unable to drag variables in "Use Associations" when implementing a task

    Nothing happens when i try to drag variables from right panel into fields on the left in "Use Association" window, when implementing a script task (or human task).
    i've cleared the repository and re-installed jdeveloper, but the problem is still there. The version of jdeveloper is 11.1.1.5.0
    any ideas about this?
    thanks.

    Hi. There are several ways for get that. Please describe a little more what are you doing. You can have the same data from different namespace, different data type and so on.
    Regards Dariel

  • [svn:osmf:] 18069: Fix FM-1035: Stream reconnect fails to timeout when reconnectTimeout is zero.

    Revision: 18069
    Revision: 18069
    Author:   [email protected]
    Date:     2010-10-07 11:28:56 -0700 (Thu, 07 Oct 2010)
    Log Message:
    Fix FM-1035: Stream reconnect fails to timeout when reconnectTimeout is zero.  This is similar to the other (recent) stream reconnection bugs, in that it only seems reproduceable when NetStream.bufferLength is non-zero upon receipt of the Buffer.Empty event.
    Ticket Links:
        http://bugs.adobe.com/jira/browse/FM-1035
    Modified Paths:
        osmf/trunk/framework/OSMF/org/osmf/net/NetLoader.as

    "Is it intended to cope with NetConnection.Connect.IdleTimeOut of FMS disconnecting clients after some time of inactivity?"
    The answer is no. Stream reconnect is all about trying to reconnect in the event of a dropped network connection. For the IdleTimeOut scenario, listen for the MediaErrorEvent.MEDIA_ERROR event on the MediaPlayer and check for an error of MediaErrorCodes.NETCONNECTION_TIMEOUT. You can handle that however you wish in your player.
    - charles

  • Lost Display Never Timeout When Plugged In

    I have a Droid X, using 2.3.  When I was at 2.1 (out of the box), there was an option for the display to never timeout when plugged in.  I have the dock that I keep on my desk, and it was a convenient to never timeout when plugged in, and revert back to my normal timeout setting when unplugged.
    Did the option go away, or am I just not looking in the right location in settings?
    Thanks,
    knjsax

    breezex,
    You are the best!  Thanks.  That is my one complaint, there are so many options and settings, I can't keep them all straight.
    Thanks again,
    knjsax

  • Whether or not to continue the use of network services when implementing IPv6

    Whether or not to continue use of network services when implementing IPv6

    Hi,
    Which network service do you specify?
    Could you detail your question?
    If you mean how to configure IPv6 in Windows Server, please refer to the link below,
    IPv6 for Microsoft Windows: Frequently Asked Questions
    http://technet.microsoft.com/en-us/network/cc987595.aspx
    Best Regards.
    Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • I met a Execption Time out ([HttpException (0x80004005): TimeOut)when I try to export custom section.

    I can export other config item . but I met a Execption Time out ([HttpException (0x80004005): TimeOut)when I try to export custom section.
    How I get the root cause? how to solve this problem.
    Thanks

    Hi Terry,
    Please try to add the following section into the <system.web> section in the Web\Portal\web.config
    <httpRuntime executionTimeout="43200" maxRequestLength="104856" />
    you can extend the timeout value to avoid the error when the custom section data is too large and take too long to load.
    hope this helps.
    Thanks,
    Jessie

  • Notification Timeout when Requested for Information

    Hi,
    We have implemented a approval notification for our customer which on a high level is as follows
    requester -> Approver 1-> Approver 2
    Once a request is submitted, the 'approval' notification goes to Approver 1 followed by Approver 2. The request is approved when both approves approve the request. If no action is taken by the approvers, the original notifications are cancelled and escalation notification is sent to supervisor of approver 2.
    We have a timeout of 48 hours set for the initial approval notifications sent to the approvers (1 & 2). In case Approver 2 requests for more information using the 'Request information' button, the TIMEOUT clock does not seem to reset and the notification is cancelled after 48 hrs even if the notification is in the queue of the requester.
    This is causing the escalation notification to be supervisor of approver 2.
    The question here is why does the timeout clock not reset when the notification goes back to the requester for additional information. Is this how the standard oracle workflow notification behaves ? Is there a way to customize and achieve this ?
    Warm Regards,
    Ashwin

    There is an enhancement request for this bug (Enhancement Request Bug 14492570
    Bug 14492570 : ER: TIMEOUT OCCURS EVEN THOUGH YOU SEND A REQUEST FOR MORE INFORMATION To Bottom )
    Also see Note [ID 1483552.1] regarding this issue

  • Apparent server timeout when running Webi report

    Hi,
    when running a Webi report in BOXIr2 SP4 we are getting the follwing error which appears to indicate that the reports is hitting the Webi Report Server timeout:
    "The Web Intelligence Java Report Panel cannot connect to the server. Close the report panel and try to connect again or see your BusinessObjects administrator. (Error: WIJ 20002)"
    However we get the error after approximately 5 minutes, but the Webi Report Server connection timeouts are all set to 60 mniutes.
    What other settings could be causing this 5 minute problem? The same report works fine when a shorter period of time (and so a smaller selection of data) is used in the parameters.
    thanks
    Keith

    Hi,
    Do you have a Windows Server?
    If so, please find the below information, you need to implement this on the server box.:
    Swap Timeout
    This is the amount of time before a user session WebI document would be removed. In other words, this controls the flushing interval of WebI temporary files. When you are in the Java Report Panel and you leave it idle for more then 5 minutes (Default), you will notice that you will no longer be able to save your
    WebI report into the CMS or your report will take longer to generate. This is because every 5 minutes the WebI cache is cleared so those temporary files would have to be regenerated by refreshing the document before you can actually save the document.
    The temporary files can be found in
    ..\BusinessObjects Enterprise 11.5\Data\ServerName\
    ServerName.Web_IntelligenceReportServer\sessions\SessionID\
    In order to modify this timeout you need to change the following registry key:
    HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite
    11.5\default\WebIntelligence\Server\Admin\SwapTimeOut
    Please let me know if this works for you.
    Thanks,
    Madhu.

Maybe you are looking for

  • How to create a file folder

    hi, The following codes throw an exception. The problem is that I can not create a folder "mytemp" under drive C. (Windows 2000) However, I have already given full permission to jre in the policy file. Can someone please tell me why? Thanks a lot. Fi

  • Bsp table view - functionality . future direction

    hi bsp'er, does anybody knows whether it is planned to make  bsp-extensions available that cover a functionality compareable to the ALV in abap or do we have do this stuff on our own. i have seen a tableView in cprojects which actually has a bit more

  • [SOLVED] Alsa won't start after upgrade

    This is my last update: [2010-07-18 08:59] Running 'pacman -Syu' [2010-07-18 08:59] synchronizing package lists [2010-07-18 08:59] starting full system upgrade [2010-07-18 09:00] upgraded gtk-aurora-engine (1.5.1-1 -> 1.5.1-2) [2010-07-18 09:00] ####

  • ITunes and Quicktime not running after upgrade

    After installing iTunes 5 I get the following error message when launching it: 'The instruction at "0xf4800000" referenced memory at "0xf4800000". The memory could not be "read".' When trying to run a quicktime clip embedded in a Acrobat document I g

  • Startup and shutdown of 11i Services in windows

    Hi friends, I am new for windows. how can we startup and shutdown of 11i instacne under windows. can we do it through services screen or can we do it through scripts as we do it on Unix/Linux which is the best method