ALBPM Webservice timeout

{color:#999999}Hi Blazers,
in ALBPM 6.04 on WLS9.2, I would like to to set the WebService Timeout.
I have tried to set the parameter -Dfuego.webservices.timeout=300 as startup ARGUMENTS of WLS Server.
But it didn't work. I got timeout error after only 1 minute.
Someone has alredy done?
Thanks
Marco{color}

Hi,
I had the same problem look this :
Web services access timeout is not configurable. System property 'fuego.webservices.timeout' can be used to set it (value in seconds). Default timeout is 60sec. (Issue #25878)
Version :
AquaLogic BPM 6.0 MP 4 build #88762
in link : http://albpmsupport.bea.com/Download/v60/mp4/Release_Notes_BEA_AquaLogic_BPM_6-0-4_HF.htm
after test in version 6.0.4, worked fine.

Similar Messages

  • Webservice timeout ? where can we set it up in BO ?

    Hi, I post this question in this part of the forum as well in case some Xcelsius user would have had the same problem :
    Hi,
    we are using BO XI R2 Edge and we have a number of concurrent accesses licences.
    We have a problem handling the life duration of a webservice.
    We use Query as webservice to build a webservice from our universe, and use the advanced feature to set a timeout of 1 minute for the webservice.
    Then we use Xcelsius to generate a table that is exported to WebI and integrated in Infoview as an object.
    When we display this object from the infoview, the xcelsius calls the webservice to get data, and when a user clicks on a part of the graph, he gets another table from another Xcelsius object, with another webservice.
    The problem is that a webservice is still active during 20 minutes, so our concurrents licences are consumed really fas by a single person browsing xcelsius documents ...
    Webservices are going through Tomcat, which has been set to 1 minute as session timeout, as well as 2 minutes for IIS (infoview sessions).
    Still, no result, there seems to be a timeout period of 20 minutes set up in BO, but we cannot find where.
    Could you please indicate use where this parameter can be set ?
    Thank you for your help in this blocking problem for us.
    Sébastien

    If you use Query As A Web Service, you can configure the timeout of web service to other time but not 20 minutes default:
    1. Open Business Objects\Tomcat\webapps\dswsbobje\WEB-INF\classes\dsws.properties.
    2. Find and configure the property "session.timeout=". If this property does not exist, add it.
        Note the time is measured by seconds. If you want to set 60 minutes, you should configure session.timeout=3600.
    3. Restart tomcat.
    Further information you can refer:
    http://dallasmarks.blogspot.com/2008/10/xcelsius-and-session-management-in.html
    Tammy
    Xcelsius QA

  • Webservice Timeout

    Perhaps this is a stupid question, but I haven't been able to
    find any information online on how to do this. I was wondering if
    it is possible to determine if a web service call fails. A failure
    which is not a fault sent by the web service, but that the service
    is not up and running and just doesn't respond (basically timing
    out). Right now all my application does is nothing. I have tried to
    listen to the FaultEvent.Event and that never gets fired. Am I
    missing something important here?

    Let's assume you're testing using
    http://localhost:8080/webservice-whatever...
    Then In your MXML <mx:WebService..., add an
    'endpointURI=http://localhost:8088' parameter.
    Fire up TCPMon and add an 8088 listener port.
    That way you can see the request as it passes to your server.
    Also, 'tail' your server logs to see if the request is being
    dispatched properly.
    Finally, if there's a problem on the Flex side, you will
    usually get some sort of error dialog before any messages are sent
    to a server.

  • WebService Socket Timeout Exception before reaching timeout duration

    Hi
    My Server is Websphere Application Server 6.0.2.17
    i got some times socket timeout exception before reach timeout duration. and also i have only default websphere settings for web service .
    The exception is occurred in 19 seconds after hitting the service . i am not able to get the exact problem . because default timeout time is 300 seconds (i think like that)
    Error Log
    2/12/09 11:01:28:323 CET 00000f6a SystemOut O WebService Started --> Begin webservice method invocation (Method Name : getCustomerInfo(String cusID))
    2/12/09 11:01:47:840 CET 00000f6d SystemOut Exception Occurred : java.net.SocketTimeoutException: Socket operation timed out before it could be completed
    WebService Method Invocation Started time 11:01:28
    WebService Timeout exception raised time 11:01:47
    TimeoutDuration 00:00:19

    Hi Mark,
    with synchronous messages it is important to consider timeouts from each connection to be established. So soapUI-PI, then PI-BackendSystem plus anything that might be in between. If your timeout soapUI-PI is smaller than the following ones, you'll get that phenomenon. soapUI will cut the connection, but PI will hold it and maybe receive an answer from the backend. This answer will end up in the void, since the original requester (your soapUI) has already disconnected. But for PI, this will be OK and status "successful". PI does not control and monitor the client's connection.
    In other words, the cancel of the connection is only performed for that same connection, it is not propagated to any subsequent connections.
    Hope that I was clear enough,
    Jörg

  • Invoking ALBPM Process from ALSB

    Hi,
    I am presently trying to invoke ALBPM(Oracle BPM) process by registering my process as webservice to ALSB (OSB). I am however not able to trigger my processes from ALSB. I have posted the steps followed. Please help me in figuring out the missing piece
    a) Registered the ALBPM Process WSDL in ALSB by importing manually
    b) Created a Business Service based on the WSDL
    c) Created a Proxy Service based on the WSDL.
    Invoked the "startSession" operation to generate the sessionID using ALSB test browser. ALSB receives an error response.
    I was however able to generate my sessionID and also invoke my processes successfully by using any generic Soap client.
    Please do help me in figuring out my missing steps.
    Thanks in Advance,
    Rudraksh

    Hi,
    Thanks for your response. I am getting an echo of the request as the response. I am just trying to invoke my "startSession" from test browser . I am presently using the default proxy services to trigger the ALBPM webservices. I haven't configured any message flows.I have posted the invocation trace response below.
    Invocation trace ::
    Routed Service
    No Service has been invoked, the request is echoed.
    I also happened to try out the option of registering the endpoint to connect to OSB from with OBPM. I am presently getting this stack trace everytime I try to register.
    fuego.lang.exception.ProgramException: Couldn't invoke method 'publish' on fuego.alsb.deployment.ProcessesDeploymentModel@7846a9
         at fuego.lang.exception.ProgramException.wrap(ProgramException.java:55)
         at fuego.lang.reflect.MethodUtils.invokeMethod(MethodUtils.java:50)
         at fuego.ui.wizards.ui.InvokeMethodActionListener.actionPerformed(InvokeMethodActionListener.java:49)
         at fuego.ui.peer.swt.SwtButton$1.widgetSelected(SwtButton.java:63)
         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
         at fuego.ui.peer.swt.SwtWindow.setVisible(SwtWindow.java:179)
         at fuego.ui.UiComponent.setVisible(UiComponent.java:832)
         at fuego.ui.Dialog.setVisible(Dialog.java:218)
         at fuego.designer.action.OpenAlsbProcessDeploymentDialogAction.run(OpenAlsbProcessDeploymentDialogAction.java:61)
         at fuego.eclipse.ui.EclipseAction.run(EclipseAction.java:180)
         at fuego.eclipse.ui.EclipseAction.run(EclipseAction.java:199)
         at fuego.eclipse.studio.actions.EclipseActionDelegate.run(EclipseActionDelegate.java:39)
         at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:256)
         at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:229)
         at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:546)
         at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490)
         at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:443)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
         at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
         at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
         at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
         at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
         at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
         at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
         at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
         at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
         at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
         at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
         at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
         at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
         at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
    Caused by: java.lang.reflect.InvocationTargetException
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:252)
         at org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:198)
         at fuego.lang.reflect.MethodUtils.invokeMethod(MethodUtils.java:40)
         ... 43 more
    Caused by: java.lang.UnsupportedClassVersionError: Bad version number in .class file
         at java.lang.ClassLoader.defineClass1(Native Method)
         at java.lang.ClassLoader.defineClass(Unknown Source)
         at java.security.SecureClassLoader.defineClass(Unknown Source)
         at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:338)
         at weblogic.rmi.utils.WLRMIClassLoaderDelegate.loadClass(WLRMIClassLoaderDelegate.java:210)
         at weblogic.rmi.utils.WLRMIClassLoaderDelegate.loadClass(WLRMIClassLoaderDelegate.java:128)
         at weblogic.rmi.utils.Utilities.loadClass(Utilities.java:308)
         at weblogic.rjvm.MsgAbbrevInputStream.resolveClass(MsgAbbrevInputStream.java:400)
         at weblogic.utils.io.ChunkedObjectInputStream$NestedObjectInputStream.resolveClass(ChunkedObjectInputStream.java:255)
         at java.io.ObjectInputStream.readNonProxyDesc(Unknown Source)
         at java.io.ObjectInputStream.readClassDesc(Unknown Source)
         at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.readObject(Unknown Source)
         at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:195)
         at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:565)
         at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:191)
         at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:62)
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:201)
         at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:224)
         at javax.management.remote.rmi.RMIConnectionImpl_1030_WLStub.invoke(Unknown Source)
         at weblogic.management.remote.common.RMIConnectionWrapper$15.run(ClientProviderBase.java:606)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.security.Security.runAs(Security.java:61)
         at weblogic.management.remote.common.RMIConnectionWrapper.invoke(ClientProviderBase.java:604)
         at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(Unknown Source)
         at javax.management.MBeanServerInvocationHandler.invoke(Unknown Source)
         at $Proxy23.importUploaded(Unknown Source)
         at fuego.alsb.dao.impl.AlsbManagerImpl.importJar(AlsbManagerImpl.java:404)
         at fuego.alsb.process.ProjectHelper.publishProcess(ProjectHelper.java:534)
         at fuego.alsb.process.ProjectHelper.publish(ProjectHelper.java:139)
         at fuego.alsb.deployment.ProcessesDeploymentModel.publish(ProcessesDeploymentModel.java:138)
         ... 50 more
    I am stuck.I really appreciate any help in this regard.
    Rudraksh
    Edited by: rudraksh on Jul 17, 2009 1:59 PM

  • Session Timeout - Process as a webservice

    Hi ,
    I am using ALBPM v5.7.
    In this we are exposing our process as webservice.
    We are Invoking these webservice methods from portal deployed in BEA Weblogic Server,
    The procedure we are following is , starting the session and then invoking our methods -- method1 and method2.
    But , After invoking method1, In the portal, we are waiting for five minutes and then trying to invoke method2 of BPM using the same session,
    When we do this, It is throwing an exception,
    Invalid Session.
    We observed that if we invoke method2 before five minutes then it is working fine.
    So do we have any session timeout for the BPM Process, when we expose our process as a webservice.
    If so , could you please help me in resolving this issue?
    Thanks & Regards,
    Krishnaveni.

    Just input paramters inside the Begin Activity...
    Right Click on the Process and open Process Web-Service and add a Web-Service to it..
    Then start the engine in Studio..
    And then click on Launch Deployed WebServices Webapp..
    And you would get the endpoint..

  • HTTP(S) Timeout while invoking WebService over HTTPS.

    Hello,
    I have some stress with my webservice client implementation.
    I do the following (I can post source code if needed):
    - As usual:
    System.setProperty("java.protocol.handler.pkgs","com.sun.net.ssl.internal.www.protocol");
    Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
    - Install my TrustManager
    - Install my DefaultHostnameVerifier
    - Register a custom type
    - Make a javax.xml.rpc.Call to access a webservice
    My observations:
    The code works well when using an HTTP URL, just changing the target URL to HTTPS causes the problem.
    The HTTPS web service (on server) works well seeing a HTTPS client using the weblogic SSL implementation, or an AXIS client can easily connect.
    When I use a simple and direct "Open HttpsURLConnection on URL("https://xxx.service?WSDL"); print-out-all-that's-coming-in", it works well. I think my SSL access is made correctly.
    The client does not complain about not-installed SSL things, all certificates are accepted, etc. No problem at this part.
    System.setProperty("javax.net.debug", "all") is set, but i dont see anything of interrest.
    I use the packages contained in 'java_xml_pack-summer-02_01' of SUN (jaxm-1.1_01, jaxp-1.2_01,jaxr-1.0_02 etc and the jsse 1.0.3).
    The server is weblogic 7.
    Calling
    call.setTargetEndpointAddress("http://arakis:7001/traces_ws/searchCertificate");
    works well while
    call.setTargetEndpointAddress("https://arakis:7002/traces_ws/searchCertificate");
    causes (after 2 minutes):
    HTTP transport error: java.net.SocketException: Unexpected end of file from server
    at com.sun.xml.rpc.client.http.HttpClientTransport.invoke(HttpClientTransport.java:189)
    at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:73)
    at com.sun.xml.rpc.client.dii.CallInvokerImpl.doInvoke(CallInvokerImpl.java:54)
    at com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:279)
    at SSLSOAPClient.main(SSLSOAPClient.java:264)
    CAUSE:
    java.net.SocketException: Unexpected end of file from server
    at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:699)
    at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:604)
    at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:697)
    at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:604)
    at com.sun.xml.rpc.client.http.handler.HttpURLConnection.getInputStream(HttpURLConnection.java:543)
    at com.sun.xml.rpc.client.http.handler.HttpURLConnection.getResponseCode(HttpURLConnection.java:920)
    at com.sun.xml.rpc.client.http.HttpClientTransport.invoke(HttpClientTransport.java:123)
    at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:73)
    at com.sun.xml.rpc.client.dii.CallInvokerImpl.doInvoke(CallInvokerImpl.java:54)
    at com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:279)
    at SSLSOAPClient.main(SSLSOAPClient.java:264)
    Exception in thread "main"
    What I note is that the call is using a HttpURLConnection object and NOT a HttpsURLConnection object (so problems are 'normal' i guess), but I dont have any clue what I have to do to instruct the client to use HTTPS other than specifying HTTPS in the target.
    Hope someone has an idea
    Tasha

    Hello,
    The default timeout in Axis is 60 seconds, you can change it by your client code, and you can still keep the session to call many times
    ((org.apache.axis.client.Stub)service).setMaintainSession(true); //keep session
    ((org.apache.axis.client.Stub)service).setTimeout(60*1000*30); //half hour
    Lixin

  • Setting timeout for webservice

    hello all,
    I have made client program to connect to a webservice using dynamic url, my problem is i am unable to set the timeout of the webservice if anybody knows please let me know. my code is as follows.
    WebServiceClient ann = testpackage.TestClassService.class.getAnnotation(WebServiceClient.class);
    try {
    testpackage.TestClassService service = new testpackage.TestClassService(new URL("MY URL"), new QName(ann.targetNamespace(), ann.name()));
    testpackage.TestClass port = service.getTestClassPort();
    String result = port.getUserTask("HELLO");
    System.out.println(result);
    } catch (MalformedURLException ex) {
    using this code how can i set timeout at client side
    thanks in advance

    hi there thanks for your reply but your solution didn't worked for me. may be because of mistake in my question explanation i will explain it again
    WebServiceClient ann = testpackage.TestClassService.class.getAnnotation(WebServiceClient.class);
    try {
    testpackage.TestClassService service = new testpackage.TestClassService(new URL("MY URL"), new QName(ann.targetNamespace(), ann.name()));
    testpackage.TestClass port = service.getTestClassPort();
    String result = port.getUserTask("HELLO");
    System.out.println(result);
    } catch (MalformedURLException ex) {
    using this code i am calling my webservice and the function "getUserTask" which give me some output in return.
    now, what situation i am facing is whenever i make a call to the above function and if RTO occurs after the call of the function then my application comes in to a hang mode situation. and i am unable to do anything untill the reconnection of the network occurs.Either i have to wait for the reconnection or i have to terminate my applicartion.
    My desire is, i should be able to set my timeout period of a web service request. if no reply comes in the given time period then i should be able to raise any message to the user.
    I think ihave made myself a bit more clear.
    thanks for your reply once again.

  • Setting timeout for SOAP requests in a webservice client

    I am trying to set the timeout for a synchronous SOAP request sent to a Web Service deployed on weblogic 8.1 SP2. I tried setting timeout thru bindinginfo setTimeout() and also javax.xml.rpc.Stub _setProperty(). Both of them seem to be not working. I set the value to as low as 1 sec but i still donot get a timeout. Other properties/method from these two classes work fine though (like endpointaddress property in javax.xml.rpc.Stub and setVerbose flag to true in BindingInfo).
    Can someone please help.
    Thanks in Advance
    srini

    Our application calls the webservice provided by another company over the internet using the ssl. We use the wsdl url of the webservice on the destination while creating the port. If the destination is not available statement which creates the port blocks for around 4 minutes.
    I think the first network call gets the wsdl from the remote server. Thus we encounter delays before getting the stub created. How can I timeout such a calls.
    try {
    port = (new ServiceName_Impl(remoteWsdlURL)).getServiceNameSoap();
    } catch (IOException e) {                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • How to call WebService in ALBPM WorkFlow

    Hi,
    I want to call one webservice in ALBPM. My requirements are to integrate it with other system like ALSB/OSB using Webservice & to expose OBPM as webservice , so that some other system can consume it. I have some queries regarding webservices.
    1.)     I have built one web service, I need to call it in BPM process. For that I called the WSDL in Catalog-> Module-> webservices. By that, wsdl & xmls are imported in catalog. But Im struck in how to call the webservice operation in BPM activities. How to make soap request in BPM flow, in order to hit this webservice.

    Hi
    Dont think so PDF is available for this
    Option could be
    1. [Secured WebServices - I|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417200)ID1178704850DB02001712700357265408End?blog=/pub/wlg/4999]
    2.[Invoking Rules web service from WebDynpro Application CE7.1|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417200)ID1178704850DB02001712700357265408End?blog=/pub/wlg/13520]
    3.[Webservice Calls From a User Defined Function.|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417200)ID1178704850DB02001712700357265408End?blog=/pub/wlg/5001]
    BR
    Satish Kumar

  • Need PBL code to call webservice in ALBPM

    I have make one HelloWorld webservice as below:-
    package webBased;
    import javax.jws.*;
    @WebService
    public class HelloWorld {
         @WebMethod
         public int hello(int a,int b) {
              int c=a+b;
              return c;
    I have Created wsdl of it and imported in ALBPM by doing following steps:-
    Catalog-> New Module -> WebService. All the xmls and wsdl are imported.
    Now i want to call it in ALBPM flow and created Global activity. In main task of activity, I need to write PBL code to call that webservice.
    Can anyone help me in this PBL code to call it.
    or is there any other way to call this web service in ALBPM process flow.
    Thanx,
    Vinny

    Thanx. I have drag and drop only two things
    hello(OSBWeb.HelloWorldService.HelloWorldService, a : 10, b : 29, out @return : c)
    helloWorldService = OSBWeb.HelloWorldService.HelloWorldService(endPoint : "http://localhost:7001/TestPOC/HelloWorld")
    and successfully hit the service from Global Activity in ALBPM.

  • Webservice Connection Timeout Error in Sun Java System Application server

    I have a java code to connect to Ebay Shopping Webservice that uses the client stub generated through Axis. The code works fine when I run it from the main method of a stand alone Java application. Which means there is no issue with the Proxy settings or any other network setting that could block the webservice from my system. However when I use the same code inside a JSF based Web Application, a connection timeout error comes up. The Web application is deployed on the Sun Java System Application server. The stacktrace of the exception is
    java.net.ConnectException: Connection timed out: no further information
         at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
         at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:527)
         at com.sun.enterprise.server.ss.provider.ASClientSocketImpl.connect(ASClientSocketImpl.java:206)
         at java.net.Socket.connect(Socket.java:520)
         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 org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:153)
         at org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:125)
         at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:191)
         at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:404)
         at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
         at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
         at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
         at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
         at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
         at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
         at org.apache.axis.client.Call.invoke(Call.java:2767)
         at org.apache.axis.client.Call.invoke(Call.java:2443)
         at org.apache.axis.client.Call.invoke(Call.java:2366)
         at org.apache.axis.client.Call.invoke(Call.java:1812)
         at com.ebay.api.soap.ShoppingBindingStub.findProducts(ShoppingBindingStub.java:1217)
         at com.shopping.ebay.EbayServiceUtility.performEBaySearch(EbayServiceUtility.java:66)
         at searchProduct.SearchProductBean.search(SearchProductBean.java:98)
         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.sun.el.parser.AstValue.invoke(AstValue.java:151)
         at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283)
         at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:77)
         at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:96)
         at javax.faces.component.UICommand.broadcast(UICommand.java:383)
         at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:450)
         at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:759)
         at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:97)
         at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:244)
         at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:113)
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
         at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:278)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
         at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
         at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
         at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
         at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:239)
         at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
         at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
         at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
         at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
         at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
         at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
         at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
    The JDK version on my machine is 1.5.0_14. Can somebody point me as where I should be looking for errors?

    You need to delete all the files under the 'generated' directory to force the server to recompile them after the JDK upgrade. Also check in domain.xml and make sure the JVM parameter is pointing to the JDK that you have installed. It is also worthwhile to check asenv.conf to see which JDK that file is pointing to as well.

  • Need help about setting timeout webservice client.

    Hi,
    I trying to set timeout before make call to the webservices, my target webservice is deployed on WebLgic server 8.14 (service pack 4). Nothing just Thread.sleep for 1 min. then return some string. Here is my client code. I use the proxy generated by the workshop testing browser, "Java proxy" button.
    public static void main(String a[]) {
    try {
    EjbTimeout_Impl proxy = new EjbTimeout_Impl();
    EjbTimeoutSoap_Stub myStub = (EjbTimeoutSoap_Stub)proxy.getEjbTimeoutSoap();
    BindingInfo bInfo = (BindingInfo)myStub._getProperty("weblogic.webservice.bindinginfo");
    System.out.println(bInfo.getTimeout()); // print out '-1' no timeout I guess
    bInfo.setTimeout(5); //secs
    System.out.println(bInfo.getTimeout()); // print out '5', value change accepted
    myStub._setProperty("weblogic.webservice.rpc.timeoutsecs", "5");
    System.out.println(myStub._getProperty
    ("weblogic.webservice.rpc.timeoutsecs")); // also print '5'
    String ss = myStub.sayHello("WEBLOGIC");
    System.out.println(ss);
    } catch (Exception e) {
    System.out.println(e.toString());
    As you see the timeout value is changed but when I call webservice from this client everything is fine. The output string ruturn from webservice is printed out after Thread.sleep(60000).
    Are there any missing things about this client code, my webservice code is quite simple, or if there is some way else to achieve this ???
    Many thanks.

    Before you use the JMS, you need to deploy some drivers related to specific MQseries, Kindly ensure that proper driver are deployed....
    If you use MQSeries 53x.xxx, you must enter the following JAR files in aii_af_jmsproviderlib.sda.
    com.ibm.mq.jar, com.ibm.mqbind.jar, com.ibm.mqjms.jar, connector.jar (use the JAR file from the J2EE client directory)
    check this link it will give you more inofmration
    http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/content.htm
    check this to get the condifuration the JMS
    How to use conversion modules in JMS - https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
    Ref How To Use the Content Conversion Module in JMS Adapter - https://websmp106.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000582377&

  • Transaction timeout in BPEL for webservice invocation

    [ERROR] [] [oracle.soa.bpel.engine.dispatch] [tid: orabpel.invoke.pool-4.thread-3] [userId: <anonymous>] [ecid: e8538d226bae7c2a:1914e8c0:148c67a5f26:-8000-00000000000031a2,1:27459] [APP: soa-infra] failed to handle message[[
    weblogic.transaction.internal.TimedOutException: Transaction timed out after 299 seconds
    BEA1-166C02569896A59BE380
                    at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1788)
                    at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1676)
                    at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1988)
                    at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1586)
                    at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
                    at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
                    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
                    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
                    at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Message handle error.
    error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 299 seconds
    BEA1-166C02569896A59BE380
    This is happening when invoking a webservices from BPEL and if it takes more than 5 minutes we are getting above Error
    we have tried out SyncMaxWaitTime Property in BPEL configurations through SOA administration menu of EM. Also tried by increasing JTA timeout seconds in Service--JTA @ weblogic console.
    Any suggestion or pointers..

    Hi,
    Could help set the following...
    The timeouts should be configured based on the below condition
    SyncMaxWaitTime < BPEL EJB's transaction timeout < Global Transaction Timeout
    The values could be: SyncMaxWaitTime (3600) ; BPEL EJB's transaction timeout (3600); Global Transaction Timeout JTA (7200)
    Setting the SyncMaxWaitTime :
    This is the maximum time a synchronous BPEL process waits before it times out to get the response from another BPEL or a web service
    Login to EM console
    Expand SOA and right click on "soa-infra"
    From context menu, select SOA Administration –> BPEL properties
    Click on "More BPEL Configuration properties"
    Enter the appropriate value for the SyncMaxWaitTime
    Setting the global transaction timeout at Weblogic Domain Level:
    This property controls the transaction timeout seconds for active transactions. If the transaction is still in the "active" state after this time, it is automatically rolled back. 
    Log into Oracle Weblogic Administration Console.
    Click Services -> JTA.
    Change the value of Timeout Seconds to the required value (the default is 30)
    Click Save.
    Restart Oracle Weblogic Server.
    Overriding the transaction timeout setting for BPEL EJB's:
    The timeout properties for the EJB's control the particular timeout setting for the SOA application, overriding the global setting specified by the JTA timeout 
    Log into Oracle Weblogic Administration Console.
    Click Deployments.
    Expand soa-infra -> EJBs.
    Click on the configuration tab for the timeout setting for each of EJB’s listed below and the change the time out values as required.
    Following EJBs need to be updated:
    BPELActivityManagerBean  
    BPELDeliveryBean
    BPELDispatcherBean
    BPELEngineBean
    BPELFinderBean
    BPELInstanceManagerBean
    BPELProcessManagerBean
    BPELSensorValuesBean
    BPELServerManagerBean
    Click Save.
    Restart Oracle Weblogic Server.
    I hope you find it useful!
    hugs!

  • Wls 10.3 weblogic-webservices.xml transaction-timeout attribute not working

    Hi, need some urgent need.
    I have a stateless ejb webservice and I'm trying to set the transaction timeout for some of the methods. Right now my webservice transaction is timing out to the default of 30 secs. I've tried setting in the admin console the JTA transaction timeout option, didn't work (file a case with bea support #81233). And after days of researching and searching I came across that you can setup the weblogic webservice transaction-timeout thru the weblogic-webservices.xml deployment descriptor. Tried setting the transaction-timeout attribute to 120 secs. and that didn't work. Here is the snippet of the xml file.
    <?xml version='1.0' encoding='UTF-8'?>
    <weblogic-webservices xmlns="http://www.bea.com/ns/weblogic/weblogic-webservices" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-webservices http://www.bea.com/ns/weblogic/weblogic-webservices/1.0/weblogic-webservices.xsd">
    <webservice-description>
    <webservice-description-name>com.starcomsoft.pp.system.jws.SystemWSImpl</webservice-description-name>
    <webservice-type>JAXRPC</webservice-type>
    <port-component>
    <port-component-name>SystemWSSoapPort</port-component-name>
    <service-endpoint-address>
    <webservice-contextpath>starcomsoft_ws</webservice-contextpath>
    <webservice-serviceuri>/SystemWSImpl</webservice-serviceuri>
    </service-endpoint-address>
         <transaction-timeout>120</transaction-timeout>
         <reliability-config>
              <inactivity-timeout>P0DT600S</inactivity-timeout>
         </reliability-config>
    </port-component>
    </webservice-description>
    </weblogic-webservice>
    Does anybody have any clue to solve my urgent need.
    Thanks in advance for your help or suggestion.

    Unhandled exception
    Type=Segmentation error vmState=0x00040000
    J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000033
    Handler1=F144C588 Handler2=F1446A9C
    Module=/app/oracle/product/Middleware/wlserver_10.3/server/native/aix/ppc/libmuxer.so
    Module_base_address=D8457000
    Target=2_40_20091214_049398 (AIX 5.3)
    CPU=ppc (4 logical CPUs) (0x600000000 RAM)
    ----------- Stack Backtrace -----------
    (0xD696E748 [libj9vm24.so+0x48748])
    (0xD8383EDC [libjclscar_24.so+0x10edc])
    (0xD8384514 [libjclscar_24.so+0x11514])
    (0xD6967718 [libj9vm24.so+0x41718])
    (0xD6967158 [libj9vm24.so+0x41158])
    (0xD69640D0 [libj9vm24.so+0x3e0d0])
    (0xD6932C9C [libj9vm24.so+0xcc9c])
    (0xD69BBA18 [libj9prt24.so+0x3a18])
    (0xD6932BB8 [libj9vm24.so+0xcbb8])
    (0xD69A77CC [libj9thr24.so+0x27cc])
    pthreadbody+0x118 (0xD010D784 [libpthreads.a+0x3784])

Maybe you are looking for