Web Services Vs JMS

Hi All,
I am in the process of benchmarking web services vs JMS.
My scenario is as follows:
I had implemented a delay in both web services as well in JMS. The delay is implemented
using a for loop. I am facing a problem here. Though the Web Services finishes
the for loop in one second. The MDB takes 4 seconds to finish the for loop.
I dont know the reason behind this.
Can anyone throw some light on the same?
Many Thanks in Advance,
C R Baradwaj
[POC.doc]

Hello,
You might want to take a look at the JMS performance guide:
http://dev2dev.bea.com/resourcelibrary/whitepapers/WL_JMS_Perform_GD.jsp
Also, your diagram seems to indicate you are using MQ series, so you
might want to take a look at this whitepaper:
http://dev2dev.bea.com/resourcelibrary/whitepapers/jmsproviders.jsp
Generally speaking, SOAP protocol associated with webservices is more
verbose and will be slower than using JMS as a transport.
Hope this helps,
Bruce
Raghuram Bharadwaj C wrote:
>
Hi All,
I am in the process of benchmarking web services vs JMS.
My scenario is as follows:
I had implemented a delay in both web services as well in JMS. The delay is implemented
using a for loop. I am facing a problem here. Though the Web Services finishes
the for loop in one second. The MDB takes 4 seconds to finish the for loop.
I dont know the reason behind this.
Can anyone throw some light on the same?
Many Thanks in Advance,
C R Baradwaj
Name: POC.doc
POC.doc Type: WINWORD File (application/msword)
Encoding: base64

Similar Messages

  • How to Create web service using JMS with PUB/SUB pattern.

    Hi All,
    I need to expose web service using JMS with PUB/SUB pattern.
    if you have any source for this.
    I tried to use @WLJmsTransport annotation but unable to get it done.
    I have configured all JMS server, topic, and connection factory.
    Thanks.

    Hi, I am having web sample web service program which is simple one.
    But I need to Modify this to JMS enable.
    Can any one help me?
    Thanks.

  • Asynchronous Web Services with JMS  does'nt do receive operation

    I am running Jdeveloper 9.0.3.1 and latest oc4j containers
    ( downloaded from Technet) on one machine with windows 2000 on it and my database is running on a different machine having windows2000 ,the version of database is 9.2.0.1.0.
    I dowloaded the tuturial "publish jms as a web service " from http://technet.oracle.com/tech/webservices/htdocs/series/jms/content.html.
    everything works fine except I don't get the receive message .. this is what is shows on the jdevelopers
    D:\jdeveloper9031\lib\xmlparserv\jdeveloper9031\lib\xmlparserv2.jar MyJMSWebServiceStub
    Doing the Send Operation ..on Element
    <employee>
    <name>Bob</name>
    <emp_id>1234</emp_id>
    <position>assistant manager</position>
    </employee>
    Doing the Receive operation ..
    I have tried searching metalink also..please help
    thanks
    Rajesh

    This may not be the right place to Ask this..
    But ur preveious post says you have done a gud RnD on this..please help meout..
    My problem is to during synchrous read of a file you have to mention proper filename.
    but i knows filename only a runtime.. so we have functions through which we can get IN file name...ans Set OUT file name..
    but is there ANY WAY TO SET IN filename....
    Reagrds
    Satyendra

  • Top down Web Services using JMS

    Hi,
    I am trying to set up a JMS web service. I m attempting to follow "Oracle® Application Server Advanced Web Services Developer's Guide 10g (10.1.3.1.0) Part Number B28975-02" documentation.
    IDE: JDeveloper Build JDEVADF_11.1.1.2.0_GENERIC_091029.2229.5536
    I get the following error when I run the ant script:
    genwsjms:
    [genInterface] WARNING: Failed to locate wsa.jar file. This may be caused because required "COMMON_COMPONENTS_HOME" environment variable or ant property has not been set.
    [genInterface] WARNING: binding "{http://oracle/communications/platform/demo/webservices/rpc/secure/gen}DemoSecRpcPortTypeJMSBinding" is ignored because it has an invalid attribute: transport="http://www.oracle.com/technology/oracleas/wsdl/jms"
    [genInterface] WARNING: Service "DemoSecRpcService" does not contain any usable portsAnt script run is:
      <path id="taskdef.path">
        <pathelement path="${patch.classpath}"/>
        <pathelement location="${wls-home}/server/lib/weblogic.jar"/>
        <pathelement location="${wls-home}/server/lib/webservices.jar"/>
        <pathelement location="${wls-home}/server/lib/xbean.jar"/>
        <pathelement location="${wsa.dir}/wsa.jar"/>
      </path>
    <taskdef name="genInterface" classname="oracle.j2ee.ws.tools.wsa.cli.ant.GenInterface" classpathref="taskdef.path"/>
      <target name="genwsjms">
        <genInterface wsdl="${wsdl-location}" output="${code-gen-jar}" packagename="${server-pkg-name}" databinding="true" unwrapparameters="false"/>
      </target>build.properties has the wsa jar location defined as:
    wsa.dir=../../../../Oracle/Middleware/oracle_common/modules/oracle.webservices_11.1.1
    WSDL definition has:
    xmlns:jms="http://www.oracle.com/technology/oracleas/wsdl/jms"Binding is defined as:
        <binding name="DemoSecRpcPortTypeJMSBinding" type="tns:DemoSecRpcPortType">
            <soap:binding style="document" transport="http://www.oracle.com/technology/oracleas/wsdl/jms"/>
            <operation name="getPhoneList">
                <soap:operation soapAction="http://oracle/communications/platform/demo/webservices/rpc/secure/gen/getPhoneList"/>
                <input><soap:body use="literal" parts="lastName" namespace="http://oracle/communications/platform/demo/webservices/rpc/secure/gen"/></input>
                <output><soap:body use="literal" parts="phoneListOut" namespace="http://oracle/communications/platform/demo/webservices/rpc/secure/gen"/></output>
            </operation>
            <operation name="createPhoneRecord"><soap:operation soapAction="http://oracle/communications/platform/demo/webservices/rpc/secure/gen/createPhoneRecord"/>
                <input><soap:body use="literal" parts="createPhoneIn" namespace="http://oracle/communications/platform/demo/webservices/rpc/secure/gen"/></input>
                <output><soap:body use="literal" parts="createPhoneOut" namespace="http://oracle/communications/platform/demo/webservices/rpc/secure/gen"/></output>
            </operation>
        </binding>Service defined:
        <service name="DemoSecRpcService">
            <port name="DemoSecRpcJMSPort" binding="tns:DemoSecRpcPortTypeJMSBinding">
                <jms:address jndiConnectionFactoryName="jms/JMSTransportConnectionFactory"jndiDestinationName="jms://localhost:7101/transports/DemoSecRpcServiceJMS?URI=DemoQueueIn">
                    <jms:propertyValue name="endpoint-location" type="string" value="DemoSecRpcService"/>
                </jms:address>
            </port>
        </service>Please help me identify the issue with the WSDL defined and/or the build script.
    Thanks,
    Sajitha

    Thank you Shay ....
    I was running into the following issue when trying to use wsdlc
    <Apr 7, 2010 10:46:23 AM CDT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException: [HTTP:101216]Servlet: "DemoSecRpcServiceServletjms" failed to preload on startup in Web application: "AppUIM-ProjUIM-context-root".
    java.lang.StringIndexOutOfBoundsException: String index out of range: -9
        at java.lang.String.substring(String.java:1937)
        at weblogic.wsee.server.jms.JmsDeploymentListener.jmsListenerDeploymentHelper(JmsDeploymentListener.java:164)
        at weblogic.wsee.server.jms.JmsDeploymentListener.process(JmsDeploymentListener.java:65)
        at weblogic.wsee.ws.init.WsDeploymentChain.process(WsDeploymentChain.java:42)Here are the steps that I followed.
    1. Created a WSDL
    2. ran the ant script: genws
    3. Edited the Implementation class to add the annotation: @WLJmsTransport(connectionFactory = "jms/JMSTransportConnectionFactory",
    contextPath = "DemoSecRpc", portName = "DemoSecRpcJMSPort",
    queue = "jms/DemoQueueIn", serviceUri = "DemoSecRpcJMSService")
    4. Edited the Implementation class to add the logic needed for the web service
    5. Removed the wsdlLocation variable(wsdlLocation="/wsdls/RISecRPC.wsdl") from the interface: DemoSecRpcPortType
    6. ran the ant script: build-service
    6. Defined Queue and Connection Factory through Admin console of the integrated weblogic server.
    Ant script
      <target name="genws">
        <wsdlc srcwsdl="${wsdl-location}" destjwsdir="${code-gen-jar}" destimpldir="./src"
               packagename="${server-pkg-name}" type="JAXRPC"></wsdlc>
        <unzip src="${code-gen-jar}/${wsdl_name}_wsdl.jar" dest="./src">
          <patternset><include name="**/*.java"/></patternset>
        </unzip>
      </target>
      <!-- ******************************************* -->
      <!-- Build the service with needed config files  -->
      <!-- ******************************************* -->
      <target name="build-service" description="Compiles the WebService App for HTTP transport">
        <mkdir dir="META-INF.tmp"/>
        <delete dir="${dest.dir}" includes="**/${SERVICE_NAME}*.war" quiet="true" verbose="true"/>
        <jwsc srcdir="${serverclass-dir}" destdir="${ear.dir}"
              applicationxml="META-INF.tmp/application.xml" keepgenerated="true"
              classpathref="taskdef.path" verbose="true">
          <jws name="${SERVICE_NAME}" file="/${PORT_NAME}Impl.java"
               compiledwsdl="${code-gen-jar}/${wsdl_name}_wsdl.jar" type="JAXRPC">
            <WLJMSTransport contextpath="/${SERVICE_NAME}" serviceuri="${JMS_SERVICE_URI}" portname="${JMS_PORT_NAME}" queue="${QUEUE_NAME}"/>
          </jws>
        </jwsc>
    <unwar src="${ear.dir}/${SERVICE_NAME}.war" dest="./public_html">
          <patternset>
            <include name="**/*.xml"/>
            <include name="**/*.wsdl"/>
          </patternset>
        </unwar>
        <unwar src="${ear.dir}/${SERVICE_NAME}.war" dest="./src">
          <patternset>
            <include name="**/*ImplPortType.java"/>
          </patternset>
        </unwar>
      </target>wsdl binding and service defined as:
        <binding name="DemoSecRpcPortTypeSOAP11JMSBinding" type="tns:DemoSecRpcPortType">
            <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/jms"/>
            <operation name="getPhoneList">
                <soap:operation style="document"  soapAction="http://oracle/communications/platform/demo/webservices/rpc/secure/gen/getPhoneList"/>
                <input> <soap:body use="literal" parts="lastName"/> </input>
                <output> <soap:body use="literal" parts="phoneListOut"/> </output>
            </operation>
            <operation name="createPhoneRecord">
                <soap:operation style="document" soapAction="http://oracle/communications/platform/demo/webservices/rpc/secure/gen/createPhoneRecord"/>
                <input> <soap:body use="literal" parts="createPhoneIn"/>  </input>
                <output> <soap:body use="literal" parts="createPhoneOut"/>  </output>
            </operation>
        </binding>
        <service name="DemoSecRpcService">
            <port name="DemoSecRpcJMSPort" binding="tns:DemoSecRpcPortTypeSOAP11JMSBinding">
                <soap:address location="jms://localhost:7001/DemoSecRpc/DemoSecRpcJMSService?URI=jms/DemoQueueIn" />
            </port>
        </service>Thanks,
    Sajitha

  • WL 8.1 SP6 to WL10.3 upgrade any TIPS on "JMS, EJB, Web Service, JDK" etc?

    We are upgrading from BEA Weblogic 8.1 SP6 to Oracle Weblogic 10.3. The application running on WL 8.1 SP6 provides the services like - Web Service consumer, JMS server/consumer, RMI server. The JDK under WL 8.1 being 1.4.
    We have a mix of client application that are essentially JMS clients/senders and RMI clients. These clients will also be upgraded to Oracle Weblogic 10.3 but not at the same time as JMS server/consumer. So some clients may still be running on WL 8.1 JDK 1.4 while the server is running on WL 10.3 (that needs JDK 1.6)
    Please share any TIPs on compatibility issues (and how to overcome) for this mismatch between WL versions as well as JDK.
    Are there any specific details as for as JMS configuration setup from WL 8.1 to WL10.3.
    Appreciate your help!

    Some thoughts:
    * WL 10.3 fully supports 8.1 clients, so you can simply continue to use the 8.1 client jars. The drawback is that the clients won't be able to use new features like unit-of-order, and you may not get some performance benefits of the later clients.
    * I think WL 10.3 clients support the 1.5 and 1.6 JVMs.
    * I think WL 9.2 clients support 1.5 and 1.4 JVMs, so you might consider using 9.x clients during your transition period. This will give you access to more new features without forcing the client to use the 1.5 or 1.6 JVM.
    * As for mix-and-matching of JDK versions, you will need to develop your applications and serializable applications objects so that they continue to use the lowest common denominator. For example, if the same application code must run on 1.4 and a 1.5 client, then don't use generics. Also, avoid using new 1.5 or later JDK classes for serializable objects, if the objects must be passed to older clients (which, of course, will not be able to unmarshal such classes).
    * WL 10.3 and later stand-alone "full clients" can no longer always simply just use the "weblogic.jar". You can only include the weblogic.jar in the client classpath if the jar is embedded with a full weblogic install, otherwise, you must generate a "full client jar" using a command line utility and reference the generated jar instead. See [ Overview of Stand-alone Clients | http://download.oracle.com/docs/cd/E12839_01/web.1111/e13717/basics.htm#i1062773 ].
    * WL 10.3 configuration is quite different than 8.1 configuration. Some things to keep in mind:
    -- You now must also configure "WL Stores" (target to same target as the JMS server that uses the store). For JMS purposes, I recommend configuring a custom store per server and avoiding use of the default store.
    -- You still must configure JMS server(s) (configure each to reference a WL store that has the same target)
    -- You now must configure "JMS Modules", which contains definitions for destinations.
    -- In most cases, best practice is that you should configure one system module per set of JMS servers in a cluster and define a single "subdeployment" target for the module that directly lists each JMS server, target the module itself to a cluster, target destinations within the module to the subdeployment. Avoid "default targeting" for destinations, but its OK for connection factories.
    -- If some destinations are distributed across multiple JMS servers, while others are restricted to a single JMS server, then use two modules each with its own subdeployment. One module for the restricted case that uses regular destinations, and the other for the distributed case.
    Hope this helps,
    Tom

  • Best way to call web service from Message Driven Bean

    I'm q'ing msgs up and would like to use a message driven bean to forward them to
    an external web service. Weblogic workshop does not seem to support web service
    controls in an EJB project. Any suggestions?
    Thanks,
    Paul

    Paul,
    A non-trivial alternative, since you have the WSDL, would be to forget about trying
    to use generated client code and just use JAX-RPC dynamic invocation instead.
    That's how I call external web services from within an EJB in situations in which
    generated client code cannot be incorporated prior to deployment. Minimally all
    that is required is the WSDL and the service name, port name, and operation name,
    although if non-builtin parameter types are used then you will have to manipulate
    the service's type mapping registry.
    Mark
    "Paul" <[email protected]> wrote:
    >
    I've taken our wsdl and generated a web service in Workshop 8.1 using
    XMLBeans.
    This produces a web page that contains a link"Java Proxy" for downloading
    generated
    client code. I assume this is the same as clientgen. It's interesting
    that
    it does not
    use XMLBeans like the web service that generated it. It uses a different
    serialization
    method.
    I've used this generated code to call the web service. Although the
    client seems
    to run
    successfully to completion, I get the following error in the weblogic
    server console:
    <Sep 29, 2003 7:46:24 AM EDT> <Error> <WLW> <000000> <Failure=com.bea.wlw.runtim
    e.core.request.ResponseValidationException: java.lang.RuntimeException:
    Protocol
    'http-soap' not available on this operation. [ServiceException]>
    <Sep 29, 2003 7:46:24 AM EDT> <Warning> <WLW> <000000> <Returning HTTP
    500 due
    t
    o SOAP fault occurring on DispFile=pjm.srcm.webservices.face.Receptor>
    Frustrating...
    Bruce Stephens <[email protected]> wrote:
    Hi Paul,
    Could you not first use clientgen on the external webservice, then take
    the stubs it created, then add these to your code along with the
    onMessage(Message msg) and roll it into the MBean?
    We don't have exactly that example, but you might take a look at this
    one to get some ideas:
    http://webservice.bea.com/message.zip
    Hope this helps,
    Bruce
    Paul wrote:
    Bruce,
    Don't think this will work for us. We are receiving data internallythrough
    a JMS queue. We need to pull it off the queue (MDB), massage it alittle and
    send it to an external web service. The link you sent me was howto implement
    a web service with JMS.
    I started out by trying to use the Web Service and JMS controls butit doesn't
    seem like I can use a JMS control because that requires a conversationID,
    which we don't have because nothing is comming in through a web services.
    Paul
    Bruce Stephens <[email protected]> wrote:
    Hi Paul,
    There is a chapter in the docs on this. See if this helps,
    http://edocs.bea.com/wls/docs81/webserv/jms.html#1067060
    Thanks,
    Bruce
    Paul wrote:
    I'm q'ing msgs up and would like to use a message driven bean to
    forward
    them to
    an external web service. Weblogic workshop does not seem to supportweb service
    controls in an EJB project. Any suggestions?
    Thanks,
    Paul

  • Aqualogic ESB Capabilities beyond web services ?

    I'm new to Aqualogic 2.0 ESB and I'm exploring integration posibilities and scenarios where it will be useful.
    I have some questions regarding limitations and interoperability with other:
    - is there an overlap between ALSB 2.0 and WebLogic Integration?
    - Is posible to integrate something like a back end system using CICS (ECI) and a client using web services via AquaLogic ? if so, How ?
    - How can I use the underlying capabilities of the underlying WebLogic 9.0 server (i.e J2EE Connectors, jdbc pools, etc) from Aqualogic ?
    - Can I publish an EJB remote interface running in another app. server as a "service" in Aqualogic 2.0
    thanx in advance

    I've only gone as far as reading high-level information and seeing some demos, but I think I can answer some of this.
    Concerning the difference between ALSB and WLI, it's expected that WLI could be used to build a service that would be an ALSB endpoint. ALSB is a "no coding" interface. You simply define endpoints, transports, and routing rules. WLI is a development platform.
    I'm not sure how to interpret the CICS question. Does your client have a web service invocation API? If so, then you could integrate that with ALSB.
    To sort of answer the last two questions with a summary, if you can provide a web compatible interface to a component, then you can integrate it with ALSB. That interface could a web service or JMS. Depending on what version of things you're using, you can automatically provide a web service interface to an EJB session bean.

  • NullPonterException while executing web service

    Hello, all.
    I have a strange problem with web services created via workshop 8.1beta. If I
    try to use JMS-XML method of invoking web service, the whole process seems ok.
    My code in method of a web service executes without problems, but the service
    response is as follows:
    Service Response Submitted at Fri Jul 11 14:20:11 CEST 2003 <error> <faultcode>JWSError</faultcode>
    <faultstring>java.lang.NullPointerException</faultstring> <detail> com.bea.wlw.runtime.core.dispatcher.ResponseValidationException:
    java.lang.NullPointerException at com.bea.wlw.runtime.jws.dispatcher.MimeXmlResponse.setReturnValue(MimeXmlResponse.java:37)
    at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:185)
    at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:45)
    at com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(SyncDispatcherBean.java:124)
    at com.bea.wlw.runtime.core.bean.SyncInput_l1w9sx_EOImpl.invoke(SyncInput_l1w9sx_EOImpl.java:46)
    at com.bea.wlw.runtime.core.bean.SyncInput_l1w9sx_EOImpl_WLSkel.invoke(Unknown
    Source) at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:166)
    at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:291)
    at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
    at com.bea.wlw.runtime.core.bean.SyncInput_l1w9sx_EOImpl_WLStub.invoke(Unknown
    Source) at com.bea.wlw.runtime.core.dispatcher.Dispatcher.remoteDispatch(Dispatcher.java:143)
    at com.bea.wlw.runtime.jws.bean.JMSTransportBean.onMessage(JMSTransportBean.java:113)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:364) at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:298)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:263) at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2514)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2442) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151) Caused by: java.lang.NullPointerException
    at com.bea.xml.marshal.MarshalContext.init(MarshalContext.java:38) at com.bea.wlw.runtime.core.dispatcher.DispMessage.marshalXml(DispMessage.java:408)
    at com.bea.wlw.runtime.jws.dispatcher.MimeXmlResponse.writePart(MimeXmlResponse.java:108)
    at com.bea.wlw.runtime.jws.dispatcher.MimeXmlResponse.writeOutputPart(MimeXmlResponse.java:98)
    at com.bea.wlw.runtime.jws.dispatcher.MimeXmlResponse.setReturnValue(MimeXmlResponse.java:33)
    .. 18 more
    </detail> </error>
    The next problem is that if I create a web service with JMS-XML method and test/deploy
    it on platform domain of weblogic 8.1 beta, it invokes normaly (and it ends with
    the response given above), but if I use a workshop platform, web service never
    starts. If I look at the jws.queue monitoring on weblogic console, I can see the
    messages there, but no consumer is present.
    This is not the last problem I am facing. The next problem is that my weblogic
    domain doesn't accept the system property weblogic.webservice.verbose. When I
    try to start weblogic, the console says:
    <2003.7.14 17:36:32 CEST> <Warning> <Management> <BEA-141087> <Unrecognized property:
    webservice.verbose.>
    I get the same message for jws.logging and jws.ProductionMode, which were put
    there into my start script by configuration wizard. The server runs in development
    mode and it is a platform domain server.
    Help in advance for all the answers.
    Best regards, Srecko Mandelj.

    Please post this on the Workshop (WLW) newsgroup.
    Regards
    Shridhar
    "Srecko Mandelj" <[email protected]> wrote:
    >
    Hello, all.
    I have a strange problem with web services created via workshop 8.1beta.
    If I
    try to use JMS-XML method of invoking web service, the whole process
    seems ok.
    My code in method of a web service executes without problems, but the
    service
    response is as follows:
    Service Response Submitted at Fri Jul 11 14:20:11 CEST 2003 <error> <faultcode>JWSError</faultcode>
    <faultstring>java.lang.NullPointerException</faultstring> <detail> com.bea.wlw.runtime.core.dispatcher.ResponseValidationException:
    java.lang.NullPointerException at com.bea.wlw.runtime.jws.dispatcher.MimeXmlResponse.setReturnValue(MimeXmlResponse.java:37)
    at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:185)
    at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:45)
    at com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(SyncDispatcherBean.java:124)
    at com.bea.wlw.runtime.core.bean.SyncInput_l1w9sx_EOImpl.invoke(SyncInput_l1w9sx_EOImpl.java:46)
    at com.bea.wlw.runtime.core.bean.SyncInput_l1w9sx_EOImpl_WLSkel.invoke(Unknown
    Source) at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:166)
    at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:291)
    at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
    at com.bea.wlw.runtime.core.bean.SyncInput_l1w9sx_EOImpl_WLStub.invoke(Unknown
    Source) at com.bea.wlw.runtime.core.dispatcher.Dispatcher.remoteDispatch(Dispatcher.java:143)
    at com.bea.wlw.runtime.jws.bean.JMSTransportBean.onMessage(JMSTransportBean.java:113)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:364) at
    weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:298)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:263)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2514)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2442) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151) Caused by:
    java.lang.NullPointerException
    at com.bea.xml.marshal.MarshalContext.init(MarshalContext.java:38) at
    com.bea.wlw.runtime.core.dispatcher.DispMessage.marshalXml(DispMessage.java:408)
    at com.bea.wlw.runtime.jws.dispatcher.MimeXmlResponse.writePart(MimeXmlResponse.java:108)
    at com.bea.wlw.runtime.jws.dispatcher.MimeXmlResponse.writeOutputPart(MimeXmlResponse.java:98)
    at com.bea.wlw.runtime.jws.dispatcher.MimeXmlResponse.setReturnValue(MimeXmlResponse.java:33)
    ... 18 more
    </detail> </error>
    The next problem is that if I create a web service with JMS-XML method
    and test/deploy
    it on platform domain of weblogic 8.1 beta, it invokes normaly (and it
    ends with
    the response given above), but if I use a workshop platform, web service
    never
    starts. If I look at the jws.queue monitoring on weblogic console, I
    can see the
    messages there, but no consumer is present.
    This is not the last problem I am facing. The next problem is that my
    weblogic
    domain doesn't accept the system property weblogic.webservice.verbose.
    When I
    try to start weblogic, the console says:
    <2003.7.14 17:36:32 CEST> <Warning> <Management> <BEA-141087> <Unrecognized
    property:
    webservice.verbose.>
    I get the same message for jws.logging and jws.ProductionMode, which
    were put
    there into my start script by configuration wizard. The server runs in
    development
    mode and it is a platform domain server.
    Help in advance for all the answers.
    Best regards, Srecko Mandelj.

  • Asynchronous web services

    If I set up an asynchronous web service using JMS transport, would I be able to receive the callbacks in the business service that invokes the ws?
    Is this the only approach to callbacks that I can use?

    If I set up an asynchronous web service using JMS transport, would I be able to receive the callbacks in the business service that invokes the ws?
    Is this the only approach to callbacks that I can use?

  • JMS Proxy to Web Service Problem

    Hi All,
    I have a JMS proxy that routes messages to a web service. I have set the delivery failure parameters on the JMS queue. When a message is put onto the queue and there is a problem within the message flow proper, the message is retried the appropriate number of times and put onto the Error Destination queue as necessary. However, if there is a problem calling the web service, message delivery is NOT retried, the message is NOT put onto the Error Destination queue, and the message is lost. The web service itself isn't throwing a SOAP Fault, but the business service can't reach the web service (firewall issue). My Route Error Handler in the message flow is hit and it performs a Reply With Failure.
    Can anyone please explain to me if this is by design and, if so, why? Also, how does a person work around this? I need the message to be retried. I understand that a web service cannot participate in an XA transaction, but it seems to me any failure within the message flow should cause a retry on the JMS queue.
    Thanks.
    Edited by mvcg at 06/11/2008 1:57 PM

    You should remove the Route Node since it should only be used in HttpProxy.
    Instead use just the request pipeline for your routing.
    if (condition1)
    Service Callout (or publish) to Service1
    else if (condition2)
    Service Callout (or publish) to Service2
    else
    Rasie error?
    You shouldn't need to reply with failure. Any errors in the service callout or publish should go to exception handling if you use QoS exactly-once.

  • Web Service Client - SOAP/jms: Specific response queue (not default queue)?

    Hi @ll
    I try to define a specific jms response queue for a web service client that communicates SOAP/jms, running on a WLS 9.2. The web service itself runs also on a WLS 9.2 where also the request and response queues are located. By default the client receives the responses from a temporary response queue. Is there a way to define a specific response queue e.g. setting the JMSReplyTo property in the request on the client side?
    /cheers&greetz
    Dani

    WLS do not have a light SOAP client with callbacks yet. It is
    not a planed feature for 7.0, but we will considering this for
    post 7.0.
    regards,
    -manoj
    "markhu" <[email protected]> wrote in message
    news:[email protected]..
    Hi, guys:
    I have a system : client written in Java/Swing, HTTPS authentication,
    and then subscribes to a WLS 61. SP2 based JMS Topic and also has the
    ability to send message to a Queue, since I can not bring down the size of
    the client side WLS JMS dependency lib, I am thinking about using SOAP /
    web service as the communication tier between my client and server, so the
    question is: since the client need get the price updates in a real time
    mode, I need build a server side based PUSH for all the new price updates
    which come into the JMS Topic, and broadcast as SOAP messages to client,is
    this mean that I have to build the Call - Back for the Java Swing Client,so
    it can automatically get the new price updates as it's getting from JMS
    Topic now ? Any Idea on how to build server side PUSH based SOAP message
    center as web service ?? Thanks a lot.
    regards,
    mark
    FYI:
    I need the same PUSH service for my .NET based client as well.

  • JMS Web Services in latest OC4J 9.0.3

    Just trying out the JMS Web services in OC4J 9.0.3 just released today. Using Ant 1.5 and updated the build.xml file as directed. Using JDK 1.3.02.
    Trying the JMS Web Service demo #2 based on JMS on top of Oracle AQ. Everything works fine - queues set up fine, OC4J configured nicely, and the following steps of the build work fine: clean, setup, compile, mdbjar ...
    But when I get to the assemble step it crashes with the following error:
    assemble:
    [echo] assembling Web Services EAR. ..
    [java] Please wait ...
    [java] java.io.IOException: CreateProcess: javac proxy\JmsDemo2Proxy.java error=2
    [java] at java.lang.Win32Process.create(Native Method)
    [java] at java.lang.Win32Process.<init>(Win32Process.java:66)
    [java] at java.lang.Runtime.execInternal(Native Method)
    [java] at java.lang.Runtime.exec(Runtime.java:551)
    [java] at java.lang.Runtime.exec(Runtime.java:418)
    [java] at java.lang.Runtime.exec(Runtime.java:361)
    [java] at java.lang.Runtime.exec(Runtime.java:325)
    [java] at oracle.j2ee.ws.tools.WsAssmProxyGenerator.doCompile(WsAssmProxyGenerator.java:284)
    [java] at oracle.j2ee.ws.tools.WsAssmProxyGenerator.processProxy(WsAssmProxyGenerator.java:131)
    [java] at oracle.j2ee.ws.tools.WsAssmProxyGenerator.clientGenerate(WsAssmProxyGenerator.java:120)
    [java] at oracle.j2ee.ws.tools.WsAssembler.assemble(WsAssembler.java:92)
    [java] at oracle.j2ee.ws.tools.WsAssembler.main(WsAssembler.java:64)
    [java] Exception in thread "main"
    BUILD FAILED
    file:D:/oc4j903/webservices/demo/basic/jms_service/demo2/build.xml:63: Java returned: 1
    What is interesting is the WSDL and proxy appear to have been generated successfully. Even the jmsws2.ear and mdb_service2.jar files appear generated ok. But the web.xml is missing so perhaps this is where it died. Any clues as to what might be wrong ... are changes required in the config.xml file driving the WebServicesAssembly tool?
    Thanks for any help.

    Went a little further ... given the assembly error seemed to occur on the last step creating the proxy.jar file, I simply skipped over it and did the deployment (changed the build.xml to continue assembly upon failure). This seemed reasonable as all the ear and war files where there; the only missing piece appeared to be the proxy.jar.
    The deployment of the service was successful and I downloaded the proxy.jar file from the OC4J instance which in turn allowed me to compile the Web service client. Things were looking up here.
    However, when I ran the service I got an error indicating the wrong number of arguments to the underlying queues. Given it got through to the database, I assume my configuration is set up correctly but it is a little hard to debug from here. Here is the error I got (note tried on 9.0.1 and 9.0.2 database):
    D:\oc4j903\webservices\demo\basic\jms_service\demo2>java -classpath client;proxy/JmsDemo2_proxy.jar;%CLASSPATH% JmsDemo2
    Client
    Doing the Send Operation ..on Element
    <employee>
    <name>Bob</name>
    <emp_id>1234</emp_id>
    <position>assistant manager</position>
    </employee>
    [SOAPException: faultCode=SOAP-ENV:Server; msg=oracle.jms.AQjmsException: ORA-06550: line 1, column 7:
    PLS-00306: wrong number or types of arguments in call to &apos;AQ$_JMS_ENQUEUE_OBJECT_MESSAGE&apos;
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    at JmsDemo2Proxy.makeSOAPCallDocument(JmsDemo2Proxy.java:73)
    at JmsDemo2Proxy.send(JmsDemo2Proxy.java:47)
    at JmsDemo2Client.main(client/JmsDemo2Client.java:19)
    The two oc4j configuration files requiring editing datasources.xml and application.xml are included below. Datasources was straightforward; I wasn't quite clear about the <resource-provider> entry in application.xml as it wasn't clear if this is a top level element or what. See the very end of this post to see where I put it.
    Datasources.xml
    <?xml version="1.0" standalone='yes'?>
    <!DOCTYPE data-sources PUBLIC "Orion data-sources" "http://xmlns.oracle.com/ias/dtds/data-sources.dtd">
    <data-sources>
         <data-source
              class="com.evermind.sql.DriverManagerDataSource"
              name="OracleDS"
              location="jdbc/OracleCoreDS"
              xa-location="jdbc/xa/OracleXADS"
              ejb-location="jdbc/OracleDS"
              connection-driver="oracle.jdbc.driver.OracleDriver"
              username="scott"
              password="tiger"
              url="jdbc:oracle:thin:@localhost:5521:oracle"
              inactivity-timeout="30"
         />
         <data-source
    class="com.evermind.sql.DriverManagerDataSource"
    name="OracleDS"
    location="jdbc/wsDemoEmulatedOracleCoreDS"
    xa-location="jdbc/xa/wsDemoEmulatedOracleXADS"
    ejb-location="jdbc/wsDemoEmulatedDS"
    connection-driver="oracle.jdbc.driver.OracleDriver"
    username="jemuser"
    password="jempasswd"
    url="jdbc:oracle:thin:@127.0.0.1:1521:O901"
    inactivity-timeout="30"
    />
    </data-sources>
    application.xml
    <?xml version="1.0" standalone='yes'?>
    <!DOCTYPE orion-application PUBLIC "-//Evermind//DTD J2EE Application runtime 1.2//EN" "http://xmlns.oracle.com/ias/dtds/orion-application.dtd">
    <!-- The global application config that is the parent of all the other
         applications in this server. -->
    <orion-application autocreate-tables="true"
         default-data-source="jdbc/OracleDS">
         <web-module id="defaultWebApp" path="../../home/default-web-app" />
         <web-module id="dms0" path="../../home/applications/dms0.war" />
         <web-module id="dms" path="../../home/applications/dms.war" />
    <connectors path="./oc4j-connectors.xml"/>
         <persistence path="../persistence" />
    <!-- Path to the libraries that are installed on this server.
         These will accesible for the servlets, EJBs etc -->
         <library path="../../home/lib" />
         <library path="../../../sqlj/lib" />
         <library path="../../../rdbms/jlib/xsu12.jar" />
         <!-- Path to the taglib directory that is shared
    among different applications. -->
    <library path="../../home/jsp/lib/taglib" />
    <!-- Uncomment the following element to use JAZN-XML as UserManager
         <jazn provider="XML" location="./jazn-data.xml" />
    -->
         <principals path="./principals.xml" />
         <log>
              <file path="../log/global-application.log" />
         </log>
    <commit-coordinator>
    <commit-class
    class="com.evermind.server.OracleTwoPhaseCommitDriver" />
    <property name="datasource"
    value="jdbc/OracleDS"/>
    <!-- Username and password are the optional properties
    replace with your commit_co-ordinator_super_user
         <property name="username"
         value="system" />
         <property name="password"
         value="manager" />
    -->
    </commit-coordinator>
         <data-sources path="data-sources.xml" />
         <namespace-access>
              <read-access>
                   <namespace-resource root="">
                        <security-role-mapping>
                             <group name="administrators" />
                        </security-role-mapping>
                   </namespace-resource>
              </read-access>
              <write-access>
                   <namespace-resource root="">
                        <security-role-mapping>
                             <group name="administrators" />
                        </security-role-mapping>
                   </namespace-resource>
              </write-access>
         </namespace-access>
         <resource-provider class="oracle.jms.OjmsContext" name="wsdemo">
    <description> OJMS/AQ </description>
    <property name="datasource" value="jdbc/wsDemoEmulatedDS">
    </property>
    </resource-provider>
    </orion-application>
    Any suggestions? Wait for production?
    Mike.

  • JMS Web Service Configuration

    Hi folks,
    I'm trying to set up a JMS web service on a WebLogic 7.0 server.
    I want this web service to listen for messages on a queue on
    another server running WebLogic 6.1 sp2. Here's what I've done:
    Created web service using WebLogic Workshop modeled after the
    workshop sample SimpleJMS.jws. A file Email.jws contains the
    following code snippet:
    package datatel.jms.email;
    import weblogic.jws.control.JwsContext;
    import EmailControl;
    import javax.jms.Message;
    public class Email
    // Public variables...
    public String m_Message = "default email response";
    public EmailJMS emailJMS = null;
    // Protected variables...
    protected String jmsURL = "http://predict.datatel-info.com:7250";
    // Private variables...
    private String name;
    * @jws:control
    private EmailControl Email_Ctrl;
    /** @jws:context */
    JwsContext context;
    * Initialize the JMS connection to the predict server...
    public Email()
    System.out.println("\nEntering Email.jws constructor...");
    // Initialize JMS on the Predict server...
    emailJMS = new EmailJMS(jmsURL);
    System.out.println("Exiting Email.jws constructor...");
    Notice that the Email() constructor code above references my object EmailJMS(jmsURL).
    This object intializes the JMS connection to the other WebLogic 6.1 server. Here's
    the JMS initialization code in my web service:
    public EmailJMS(String jmsURL) {
    System.out.println("\nEntering EmailJMS constructor with URL..."
    + jmsURL);
    Environment environ = new Environment();
    environ.setProviderUrl(jmsURL);
    try {
    ctx = environ.getInitialContext();
    System.out.println("Got new InitialContext..." + ctx.PROVIDER_URL
    + "\nTime is: " + new Date().toString());
    qconFactory = (QueueConnectionFactory) ctx.lookup(JMS_FACTORY);
    qcon = qconFactory.createQueueConnection();
    qsession = (WLQueueSession) qcon.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
    /** USER receive queue and listener
    queue = (Queue) ctx.lookup("USER_TX_Q");
    user_recvr = qsession.createReceiver(queue);
    user_recvr.setMessageListener(this);
    textMsg = qsession.createTextMessage();
    objMsg = qsession.createObjectMessage();
    isConnected = true;
    qcon.start();
    // --- more code follows ...
    The JMS connection is successfully made. When another JMS program sends a message
    to the USER_TX_Q, the web service receives the message via the onMessage handler
    in the EmailJMS class.
    The problem arises when I try to invoke my web service from the WebLogic Workshop
    browser Test Form. On invocation on my web service, the following exception occurs:
    start
    = 0.45-->
    name = Harmon .CONVPHASE = .START .CONVERSATIONID = 1023816206621
    Exception
    Submitted at Tue Jun 11 10:23:28 MST 2002
    start
    = 0.45-->
    javax.ejb.CreateException: Exception on Create: java.io.NotSerializableException:
    weblogic.jndi.internal.ServerNamingNode_WLStub at weblogic.knex.bean.WebProcessBean.ejbCreate(WebProcessBean.java:876)
    at weblogic.knex.bean.WebProcessBean_dp0iqg_Impl.ejbCreate(WebProcessBean_dp0iqg_Impl.java:172)
    at java.lang.reflect.Method.invoke(Native Method) at weblogic.ejb20.manager.ExclusiveEntityManager.create(ExclusiveEntityManager.java:731)
    at weblogic.ejb20.manager.ExclusiveEntityManager.remoteCreate(ExclusiveEntityManager.java:702)
    at weblogic.ejb20.internal.EntityEJBHome.create(EntityEJBHome.java:250) at
    weblogic.knex.bean.WebProcessBean_dp0iqg_HomeImpl.create(WebProcessBean_dp0iqg_HomeImpl.java:74)
    at weblogic.knex.bean.WebDispatcherBean.invoke(WebDispatcherBean.java:61)
    at weblogic.knex.bean.RemoteDispatcherBean.invoke(RemoteDispatcherBean.java:105)
    at weblogic.knex.bean.RemoteDispatcherBean_1a3xc3_EOImpl.invoke(RemoteDispatcherBean_1a3xc3_EOImpl.java:46)
    at weblogic.knex.bean.RemoteDispatcherBean_1a3xc3_EOImpl_WLSkel.invoke(Unknown
    Source) at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
    at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:262)
    at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:229)
    at weblogic.knex.bean.RemoteDispatcherBean_1a3xc3_EOImpl_WLStub.invoke(Unknown
    Source) at weblogic.knex.dispatcher.Dispatcher.remoteDispatch(Dispatcher.java:96)
    at weblogic.knex.dispatcher.Dispatcher.dispatch(Dispatcher.java:73) at weblogic.knex.dispatcher.HttpServer.exploreExec(HttpServer.java:464)
    at weblogic.knex.dispatcher.HttpServer.doGet(HttpServer.java:370) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:945)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:332)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:242)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5352)
    at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:718)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3032)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2466)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
    Service Response
    When I comment out the instantiation of my EmailJMS(jmsURL) object, the web service
    initializes just fine. However, I don't have the JMS connection to my other server.
    What is this stack trace telling me? How do I receive unsolicited JMS messages in
    a web service?
    Thanks,
    Bob Gontarz

    Hi Bob,
    I have tested the same functionality as mentioned by you, and could not see
    any errors, while testing using the Test Form. The JMS queue where I was
    sending messages is on a 6.1 sp2 server.
    Please find attached the two JWS files, which I used to simulate the
    condition, one used for dispatching the messages and the other for receiving
    the messages.
    Please do let me know if your case is any different from the one I have
    tested.
    I look forward to your response.
    Regards,
    Anurag
    Workshop Support
    "Bob Gontarz" <[email protected]> wrote in message
    news:[email protected]...
    >
    Hi folks,
    I'm trying to set up a JMS web service on a WebLogic 7.0 server.
    I want this web service to listen for messages on a queue on
    another server running WebLogic 6.1 sp2. Here's what I've done:
    Created web service using WebLogic Workshop modeled after the
    workshop sample SimpleJMS.jws. A file Email.jws contains the
    following code snippet:
    package datatel.jms.email;
    import weblogic.jws.control.JwsContext;
    import EmailControl;
    import javax.jms.Message;
    public class Email
    // Public variables...
    public String m_Message = "default email response";
    public EmailJMS emailJMS = null;
    // Protected variables...
    protected String jmsURL = "http://predict.datatel-info.com:7250";
    // Private variables...
    private String name;
    * @jws:control
    private EmailControl Email_Ctrl;
    /** @jws:context */
    JwsContext context;
    * Initialize the JMS connection to the predict server...
    public Email()
    System.out.println("\nEntering Email.jws constructor...");
    // Initialize JMS on the Predict server...
    emailJMS = new EmailJMS(jmsURL);
    System.out.println("Exiting Email.jws constructor...");
    Notice that the Email() constructor code above references my objectEmailJMS(jmsURL).
    This object intializes the JMS connection to the other WebLogic 6.1server. Here's
    the JMS initialization code in my web service:
    public EmailJMS(String jmsURL) {
    System.out.println("\nEntering EmailJMS constructor with URL..."
    + jmsURL);
    Environment environ = new Environment();
    environ.setProviderUrl(jmsURL);
    try {
    ctx = environ.getInitialContext();
    System.out.println("Got new InitialContext..." + ctx.PROVIDER_URL
    + "\nTime is: " + new Date().toString());
    qconFactory = (QueueConnectionFactory) ctx.lookup(JMS_FACTORY);
    qcon = qconFactory.createQueueConnection();
    qsession = (WLQueueSession) qcon.createQueueSession(false,Session.AUTO_ACKNOWLEDGE);
    >
    /** USER receive queue and listener
    queue = (Queue) ctx.lookup("USER_TX_Q");
    user_recvr = qsession.createReceiver(queue);
    user_recvr.setMessageListener(this);
    textMsg = qsession.createTextMessage();
    objMsg = qsession.createObjectMessage();
    isConnected = true;
    qcon.start();
    // --- more code follows ...
    The JMS connection is successfully made. When another JMS program sends amessage
    to the USER_TX_Q, the web service receives the message via the onMessagehandler
    in the EmailJMS class.
    The problem arises when I try to invoke my web service from the WebLogicWorkshop
    browser Test Form. On invocation on my web service, the followingexception occurs:
    >
    start
    = 0.45-->
    name = Harmon .CONVPHASE = .START .CONVERSATIONID = 1023816206621
    Exception
    Submitted at Tue Jun 11 10:23:28 MST 2002
    start
    = 0.45-->
    javax.ejb.CreateException: Exception on Create:java.io.NotSerializableException:
    weblogic.jndi.internal.ServerNamingNode_WLStub atweblogic.knex.bean.WebProcessBean.ejbCreate(WebProcessBean.java:876)
    atweblogic.knex.bean.WebProcessBean_dp0iqg_Impl.ejbCreate(WebProcessBean_dp0iq
    g_Impl.java:172)
    at java.lang.reflect.Method.invoke(Native Method) atweblogic.ejb20.manager.ExclusiveEntityManager.create(ExclusiveEntityManager.
    java:731)
    atweblogic.ejb20.manager.ExclusiveEntityManager.remoteCreate(ExclusiveEntityMa
    nager.java:702)
    atweblogic.ejb20.internal.EntityEJBHome.create(EntityEJBHome.java:250) at
    >
    weblogic.knex.bean.WebProcessBean_dp0iqg_HomeImpl.create(WebProcessBean_dp0i
    qg_HomeImpl.java:74)
    atweblogic.knex.bean.WebDispatcherBean.invoke(WebDispatcherBean.java:61)
    atweblogic.knex.bean.RemoteDispatcherBean.invoke(RemoteDispatcherBean.java:105
    atweblogic.knex.bean.RemoteDispatcherBean_1a3xc3_EOImpl.invoke(RemoteDispatche
    rBean_1a3xc3_EOImpl.java:46)
    atweblogic.knex.bean.RemoteDispatcherBean_1a3xc3_EOImpl_WLSkel.invoke(Unknown
    Source) atweblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
    atweblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :262)
    atweblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :229)
    atweblogic.knex.bean.RemoteDispatcherBean_1a3xc3_EOImpl_WLStub.invoke(Unknown
    Source) atweblogic.knex.dispatcher.Dispatcher.remoteDispatch(Dispatcher.java:96)
    at weblogic.knex.dispatcher.Dispatcher.dispatch(Dispatcher.java:73)at weblogic.knex.dispatcher.HttpServer.exploreExec(HttpServer.java:464)
    at weblogic.knex.dispatcher.HttpServer.doGet(HttpServer.java:370)at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) atweblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Servle
    tStubImpl.java:945)
    atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :332)
    atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
    :242)
    atweblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(W
    ebAppServletContext.java:5352)
    atweblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManage
    r.java:718)
    atweblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
    ntext.java:3032)
    atweblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
    :2466)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
    Service Response
    When I comment out the instantiation of my EmailJMS(jmsURL) object, theweb service
    initializes just fine. However, I don't have the JMS connection to myother server.
    What is this stack trace telling me? How do I receive unsolicited JMSmessages in
    a web service?
    Thanks,
    Bob Gontarz
    [SendMessages.jws]
    [HelloWorld.jws]

  • Receive asynchronous message from JMS  topic over web service

    Hi,
    I have a JMS topic and I want to expose it as a web service so that clients can
    make durable subcription to the topic and receive messages asynchronously. What
    is the best way of doing this ? Is there a portable (to other containers) way
    of do this ? If not, is there a web logic specific way of doing this ?
    Thanks,
    Siva

    So you expect clients to be receiving SOAP messages over HTTP? In this
    case, the clients are really servers that are capable of servicing SOAP
    requests, correct? And how about the senders: are they also using
    SOAP/HTTP to send messages that are delivered to the receivers?
    It should be possible to write this yourself using JMS not as the
    transport, but as a mechanism for distributing the message to a set of
    clients. You'll need to implement a Web Service for publishing to a
    topic, an operation for registering an end point to recieve messages,
    and an MDB (or other form of JMS subscriber) executing on the server to
    relay the message to the end point.
    Siva wrote:
    Hi,
    I have a JMS topic and I want to expose it as a web service so that clients can
    make durable subcription to the topic and receive messages asynchronously. What
    is the best way of doing this ? Is there a portable (to other containers) way
    of do this ? If not, is there a web logic specific way of doing this ?
    Thanks,
    Siva

  • Sending JMS messages as web services

    I am trying to read a JMS topic, retrieve an XMLBean from the queue, and send it
    via web services developed in Workshop. Everything seems to deploy fine, but
    when I post a message to the topic, it just disapears. No logging, no movement
    to the specified error queue, and println doesn't print. How do I do this?

    Hi Neil,
    Have you gone through the tutorial "how to" [1] on this subject? There
    is a basic JMS/webservice example [2], outside of WLW, that may be
    useful in validating your JMS/server configuration. Also, be sure to
    check the server log file for warning/error messages.
    Hope this is of some value,
    Bruce
    [1]
    http://edocs.bea.com/workshop/docs81/doc/en/workshop/guide/howdoi/howExchangeMessageswithaJMSQueueorTopicfromaWebService.html
    [2]
    http://webservice.bea.com/message.zip
    Neil Hornbeck wrote:
    >
    I am trying to read a JMS topic, retrieve an XMLBean from the queue, and send it
    via web services developed in Workshop. Everything seems to deploy fine, but
    when I post a message to the topic, it just disapears. No logging, no movement
    to the specified error queue, and println doesn't print. How do I do this?

Maybe you are looking for

  • One account for apps, one for iTunes Match. Work well?

    Who out there buys iPhone apps on one account, and is subscribed to iTunes Match on another account? Constant authentication when swapping from buying apps to listening to music, or not?

  • Can Aperture store projects on an external drive?

    Is it possible to store my aperture projects on an external drive or must it reside on the Mac drive? I use an external USB drive to store all of my photos on and just cannot see using HD space for these photos. Is it possible?

  • Creating list- data from child data source not appearing in output

    I am trying to create a list of leads created between a date range for customers in a specific state. My audience is Persons. When I run the list, it does not return any values. However, I noticed that the date fields are not in the output. How do I

  • Errors in ALE data transfer to E-Recruiting.

    Hello, I need help with my ALE for E-Recruiting. We are on E-Rec 604 with seperated standlone e-rec system. We have set up ALE Data transfer for object type P from ECC QA to E-Rec QA system but unfortunately the I-Doc is always gettign posted with st

  • Final Cut Pro - Vanished?

    I'm a graduate student in video art preparing for a big installation in less than a week, and this morning I go to open up my copy of Final Cut Pro and get the watermarked question mark of doom on the software's icon in the dock. Where the heck did i