WebLogic JMS error queue

Hello. I have problem after sending message to JMS queue. Message by log file sending is success. But Message don't put to queue and put to error queue.
Message don't put to queue in 25 % cases.
Speak please, what can be reasons what message put to error queue ?

give me please need section link.
I closing the sender, session and connection in method destroy();
That class, That is EJB:
@Stateless(name = "BeanName", mappedName = "ejb.un.BeanName")
@Local(BeanLocal.class)
public class BeanName implements ReleaserLocal { 
@PreDestroy
public void destroy() {
try {
jmsSender.close();
} catch (Exception ex) {
try {
jmsSession.close();
} catch (Exception ex) {
try {
jmsConnection.close();
} catch (Exception ex) {
private void sendMessage(String payload, String channel, long qId){
try {
jmsSender.send(message);
if (log.isDebugEnabled()) {
log.debug("message SEND");
I running this app from depployed in weblogic.

Similar Messages

  • Examples for JMS Error Queue implementation in BPEL

    Hi ,
    Please anyone provide me examples for JMS error queue implementaion in BPEL.
    Regards
    Narsi p

    Hi Narsi p,
    Please remember to mark answers accordingly... Helpful or correct, following the forum rules
    https://forums.oracle.com/forums/ann.jspa?annID=330
    Can you tell us more about what are you trying to achieve here?
    If you are just trying to configure an error queue to put the messages that couldn't be delivered, you can do this in weblogic directly.
    Configuring an Error Destination for Undelivered Messages
    http://docs.oracle.com/cd/E17904_01/web.1111/e13727/manage_apps.htm#JMSPG254
    Cheers,
    Vlad

  • Example using of getMessage(s) with JMS error queues?

    Hi,
    I'm cobbling together various tools for easier management of replaying messages left in error queues and the likes, and whilst I've got messages being moved around the place on demand, I can't make any progress using getMessage() and getMessages() to print out vital statistics of a message / all the messages in a queue, including hopefully ripping out excerts of the XML payload in them. Can someone provide / point me to an example of these being in use? I can get a successful execution of getMessages() but am usure what to really do next with the object returned, how to iterate through and such.
    Thanks
    Chris.

    Hi Chris,
    There are open source solutions for message management.  In particular, you might want to investigate Hermes:
    http://blogs.oracle.com/jamesbayer/2008/01/hermes_jms_open_source_jms_con.html
    As for browsing messages via getMessages(), here's a code snippet.  Note that one should never attempt to get too many messages at a time via "getNext()" -- instead call getNext() multiple times.  Otherwise, if there are too many messages, the client or server might run out of memory.
    # create a cursor to get all the messages in the queue
    # by passing ‘true’ for selector expression, 
    # and long value for cursor timeout
    cursor1=cmo.getMessages(‘true’,9999999)
    # get the next 5 messages starting from the cursor’s
    # current end position
    # this will adjust the cursor’s current start position and
    # end position “forwards” by 5
    msgs = cmo.getNext(cursor1, 5)
    # print all the messages’ contents
    print msgs
    # get 3 messages upto the cursor’s current start position
    # this will adjust the cursor’s current start and end position backwards by 3
    # this will the current position of the message by 1
    msgs = cmo.getPrevious(cursor1, 3)
    # print all the messages’ contents
    print msgs
    Finally, here's code based on public APIs that can help with exporting messages to a file.   It uses Java, not WLST. I haven't tested it personally.  I'm not sure if there's away to do this in WLST.
      * pseudo code for JMS Message Export operation based on
      * current implementation in the Administration Console
      import java.io.File;
      import java.io.FileOutputStream;
      import java.io.OutputStreamWriter;
      import java.io.BufferedWriter;
      import java.io.Writer;
      import java.io.IOException;
      import java.util.ArrayList;
      import java.util.Collection;
      import org.w3c.dom.Document;
      import org.w3c.dom.Element;
      import org.w3c.dom.Node;
      import weblogic.apache.xerces.dom.DocumentImpl;
      import weblogic.apache.xml.serialize.OutputFormat;
      import weblogic.apache.xml.serialize.XMLSerializer; 
      import weblogic.management.runtime.JMSDestinationRuntimeMBean;
      import weblogic.management.runtime.JMSDurableSubscriberRuntimeMBean;
      import weblogic.management.runtime.JMSMessageManagementRuntimeMBean;
      import javax.management.openmbean.CompositeData;
      import weblogic.jms.extensions.JMSMessageInfo;
      import weblogic.jms.extensions.WLMessage;
      import weblogic.messaging.kernel.Cursor;
      public void exportMessages(
        String fileName,
        JMSDestinationRuntimeMBean destination,
        /* or JMSDurableSubscriberRuntimeMBean durableSubscriber */,
        String messageSelector) throws Exception {
        BufferedWriter bw = null;
        try {
          File selectedFile = new File(file);
          if (destination == null /* or durableSubscriber == null */) {
            throw new IllegalArgumentException("A valid destination runtime or durableSubscriber runtime mbean must be specified");
          JMSMessageManagementRuntimeMBean runtime = (JMSMessageManagementRuntimeMBean) destination /* durableSubscriber */;
          bw = new BufferedWriter(new OutputStreamWriter(new FileOutputStream(file),"UTF-8"));
          String xmlDeclaration = "<?xml version=\"1.0\" encoding=\"UTF-8\"?>";
          String exportStart = "<JMSMessageExport>";
          final String exportEnd = "</JMSMessageExport>";
          final String indent = "    ";
          bw.write(xmlDeclaration);
          bw.newLine();
          bw.write(exportStart);
          bw.newLine();
          bw.newLine();
          bw.write(indent);
          CompositeData[] messageInfos = null;
          OutputFormat of = new OutputFormat();
          of.setIndenting(true);
          of.setLineSeparator("\n"+indent);
          of.setOmitXMLDeclaration(true);
          XMLSerializer ser = getXMLSerializer(bw, of);
          String cursor = JMSUtils.getJMSMessageCursor(runtime, selector,0);
          while ((messageInfos = runtime.getNext(cursor,new Integer(20))) != null) {
            for (int i = 0; i < messageInfos.length; i++) {
              JMSMessageInfo mhi = new JMSMessageInfo(messageInfos);
    Long mhiHandle = mhi.getHandle();
    CompositeData m = runtime.getMessage(cursor, mhiHandle);
    // need to get the message with body
    JMSMessageInfo mbi = new JMSMessageInfo(m);
    WLMessage message = mbi.getMessage();
    ser.serialize(message.getJMSMessageDocument());
    messageInfos[i] = null;
    bw.newLine();
    bw.write(exportEnd);
    bw.flush();
    bw.close();
    runtime.closeCursor(cursor);
    LOG.success("jms exportmessage success");
    } catch (Exception e) {
    try {
    if(bw != null)
    bw.close();
    } catch (IOException ioe) { }
    LOG.error(e);
    LOG.error("jms exportmessage error");
    throw(e);
    LOG.success("jms exportmessage success");
    private XMLSerializer getXMLSerializer(
    Writer writer,
    OutputFormat of) {
    return new XMLSerializer(writer, of) {
    protected void printText(
    char[] chars,
    int start,
    int length,
    boolean preserveSpace,
    boolean unescaped) throws IOException {
    super.printText(chars,start,length,true,unescaped);
    protected void printText(
    String text,
    boolean preserveSpace,
    boolean unescaped ) throws IOException {
    super.printText(text,true,unescaped);
    public static String getJMSMessageCursor(
    JMSMessageManagementRuntimeMBean runtime,
    String selector,
    int cursorTimeout) throws weblogic.management.ManagementException
    return runtime.getMessages(
    selector,
    new Integer(cursorTimeout),
    new Integer(Cursor.ALL));
    Hope this helps,
    Tom                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Problem Configuring JMS Error Queue

    Domain configuration : one adminServer, One cluster, 2 managedservers in cluster
    Two distibuted Queues: InboundQueue, Error Queue
    I want to redirect any bad message from InboundQueue to ErrorQueue and discard it.
    It worked fine for 4 yrs in Wls 8.1 ( did configured in 8.1)..
    now i upgrde to wls 10.1 and i did same configuration but InboundQueue is not redirecting to Errorqueue..
    Dont know where i am missing..
    here is the config.xml entry and jms/JmModule.xml files..
    config.xml entry_
    <jms-system-resource>
    <name>JmsModule</name>
    <target>cluster1</target>
    <sub-deployment>
    <name>subdeployment1</name>
    <target>JmsServer1,JmsServer2</target>
    </sub-deployment>
    <descriptor-file-name>jms/JmsModule-jms.xml</descriptor-file-name>
    </jms-system-resource>
    JmsModule.xml_
    <?xml version='1.0' encoding='UTF-8'?>
    <weblogic-jms xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/920 http://www.bea.com/ns/weblogic/920.xsd">
    <uniform-distributed-queue name="ErrorQueue">
    <sub-deployment-name>subdeployment1</sub-deployment-name>
    <delivery-params-overrides>
    <delivery-mode>Non-Persistent</delivery-mode>
    <time-to-deliver>-1</time-to-deliver>
    <time-to-live>-1</time-to-live>
    <priority>-1</priority>
    <redelivery-delay>-1</redelivery-delay>
    </delivery-params-overrides>
    <delivery-failure-params>
    <redelivery-limit>0</redelivery-limit>
    </delivery-failure-params>
    <jndi-name>ErrorQueue</jndi-name>
    <load-balancing-policy>Round-Robin</load-balancing-policy>
    <forward-delay>-1</forward-delay>
    </uniform-distributed-queue>
    <uniform-distributed-queue name="InboundQueue">
    <sub-deployment-name>subdeployment1</sub-deployment-name>
    <delivery-params-overrides>
    <delivery-mode>Persistent</delivery-mode>
    <time-to-deliver>10</time-to-deliver>
    <time-to-live>10</time-to-live>
    <priority>2</priority>
    <redelivery-delay>10</redelivery-delay>
    </delivery-params-overrides>
    <delivery-failure-params>
    <error-destination>ErrorQueue</error-destination>
    <redelivery-limit>1</redelivery-limit>
    <expiration-policy>Redirect</expiration-policy>
    </delivery-failure-params>
    <jndi-name>InboundQueue</jndi-name>
    <load-balancing-policy>Round-Robin</load-balancing-policy>
    <forward-delay>10</forward-delay>
    </uniform-distributed-queue>
    </weblogic-jms>
    Any help
    Thanks
    ksr

    Are you still having a problem? If so, I recommend trying to simplify the reproducer by removing the "time-to-deliver", "redelivery-delay", and "time-to-live" settings.
    <time-to-deliver>10</time-to-deliver>
    <time-to-live>10</time-to-live>
    <redelivery-delay>10</redelivery-delay>
    Note that these are all set to a very small value (10 milliseconds), and that the message will expire before it can be delivered or redelivered. The delivery delay is 10 millis, so by the time the delivery delay completes, the time-to-live will have passed -- furthermore, if there was no delivery delay, the redelivery delay is at 10 millis -- so by the time the redel occurs the time-to-live expires).
    Tom

  • Weblogic JMS Error

    Hi All,
    I am using JMS adapter fro weblogic queue...
    process working fine....but some times geeting below error...
    WSIF JCA Execute of operation 'Produce_Message' failed due to: ERRJMS_TRX_BEGIN.
    CCI Local Transaction BEGIN failed due to: ERRJMS_GET_TRANSACTED_FAIL.
    Session.getTransaction() failed
    Please examine the log file to determine the problem.
    ; nested exception is:
         ORABPEL-12100
    ERRJMS_TRX_BEGIN.
    CCI Local Transaction BEGIN failed due to: ERRJMS_GET_TRANSACTED_FAIL.
    Session.getTransaction() failed
    Please examine the log file to determine the problem.
    Please examine the log file to determine the problem.
    Can any one explain why this error coming and how to fix this issue?

    give me please need section link.
    I closing the sender, session and connection in method destroy();
    That class, That is EJB:
    @Stateless(name = "BeanName", mappedName = "ejb.un.BeanName")
    @Local(BeanLocal.class)
    public class BeanName implements ReleaserLocal { 
    @PreDestroy
    public void destroy() {
    try {
    jmsSender.close();
    } catch (Exception ex) {
    try {
    jmsSession.close();
    } catch (Exception ex) {
    try {
    jmsConnection.close();
    } catch (Exception ex) {
    private void sendMessage(String payload, String channel, long qId){
    try {
    jmsSender.send(message);
    if (log.isDebugEnabled()) {
    log.debug("message SEND");
    I running this app from depployed in weblogic.

  • JMS Error destination..

    Hi,
    I am developing a JMS application where i am processing message in a Queue and configured redelivery delay and redelivery limit. When the maximum redelivery limit has reached, i will move the message to an error destination which is again a Queue. I can send an email to the administartor with the message information indicating that the processing for the message has failed. But the requirment is, the administrator wants to view the message from the persistent store and resubmit the message. Is it possible? If that is the case what can be value for time-to-live for the message? I am using ServiceBus 10.3 and using the underlying weblogic server as JMS provider. Besides, i have a question on the relationship between redelivery delay, redelivery limit and time-to-live override. When i tested, if time-to-live is less than the redeliverylimit*redelivery delay, then will the message be deleted and the redelivery limit(number of retries) is not taking into effect. But if time-to-live is greater than also the message is deleted after maximum retry means time-to-live doesn't have effect. This means i am i right to say, if i specify time-to-live and there is no need to specify redeliverylimit and redelivery delay. If that is the case on what basis, the retry is made?
    Thanks in advance for your replies,
    Sam

    Hi,
    I am using ServiceBus 10.3 and using the underlying weblogic server as JMS provider. I think OSB tends to decorate JMS messages with its own private information, so I don't know if it can support arbitrarily moving them between destinations. You may be better off posting to an OSB specific forum.
    But the requirment is, the administrator wants to view the message from the persistent store and resubmit the message. Is it possible? That said, you can view, delete, move, and file import/export WebLogic JMS messages using the message management screens on the console. If you need a more sophisticated capability than the console provides, it is possible to write Java or WLST program's for the purpose.
    If you're interested in scripting, the following might be enough to get you started:
    For scripting and tracing examples, see the July 29th and August 10th 2009 newsgroup post with subject "Example using of getMessage(s) with JMS error queues?" [ here | http://forums.oracle.com/forums/thread.jspa?messageID=3657916] and the June 10th 2009 newsgroup post with subject "JMSDestinationRuntimeMBean - possible STATE values " [ here | http://forums.oracle.com/forums/thread.jspa?messageID=3531603 ]. Also take a look at the +Sept 23 2009 newsgroup posts with subject "Enable JMS - Queue/Topic Trace on console"+ [ here | http://forums.oracle.com/forums/thread.jspa?messageID=3782486].
    +WARNING: Exporting too many messages at a time can cause out-of-memory errors.+
    Besides, i have a question on the relationship between redelivery delay, redelivery limit and time-to-live override. When i tested, if time-to-live is less than the redeliverylimit*redelivery delay, then will the message be deleted and the redelivery limit(number of retries) is not taking into effect. But if time-to-live is greater than also the message is deleted after maximum retry means time-to-live doesn't have effect. This means i am i right to say, if i specify time-to-live and there is no need to specify redeliverylimit and redelivery delay. If that is the case on what basis, the retry is made?By definition, an expired message is automatically deleted -- no matter what the delivery count is. If you want expired messages to be automatically redirected to a destinatin's error destination you can configure an "expiration policy" of "redirect" on the destination.
    Whether you want to use message expiration, redelivery limit, or redelivery delay very much depends on your specific use case.
    -- Redelivery limits detect messages that are rolled back many times by receiving applications (rollbacks can occur due to any number of reasons, such as database failure, application bug, etc.)
    -- Redelivery delays prevent rolled back messages from being immediately redelivered. This helps prevent zooming up CPU usage to 100% with tight loop retries of processing a problem message, assumes that whatever condition caused the original rollback is temporary, and assumes that if the message is immediately redelivered that this is too soon for the problem condition to have cleared up.
    -- Expiration detects if a message has been sitting around for a long time. It doesn't detect whether the application has attempted to process the message...
    In general, if you are coding a new application, it is sometimes helpful to avoid error destinations. Instead, let your application decide what to do with problem messages (such as queue them to another destination). This helps your application provide more customizable behavior.
    Hope this helps,
    Tom
    PS Especially for developers new to WebLogic JMS, I highly recommend purchasing a copy of the book "Professional Oracle WebLogic". In addition, I recommend reading the new "Best Practices" chapter of the JMS configuration guide, and the new "Tuning Checklist" in the JMS chapter of the Performance and Tuning guide. These new sections are in the 10.3.2 documentation.

  • How to configure a error queue for weblogic jms topic

    Hi guys.
    I want to configure a error queue for weblogic jms topic. Wanted: The message goes to error destination when messages have expired or reached their redelivery limit.
    1. using jms transport configure proxy service:
    Retry Count :3
    Retry Interval:10
    Error Destination: ErrorTopic
    Expiration Policy: Redirect
    I tried use the proxy service to consume message from the jms topic . and generation an error in the proxy message flow. But the message didn't goes into the error topic.
    Any suggestions for this topic? Can anyone provide some helps or any useful links.
    Thanks in advance.
    Mingzhuang

    Mingzhuang
    I want to configure a error queue for weblogic jms topic. Wanted: The message goes to error destination when messages have expired or reached their redelivery limit.
    1. using jms transport configure proxy service:
    Retry Count :3
    Retry Interval:10
    Error Destination: ErrorTopic
    Expiration olicy: RedirectUnlike File/SFTP, JMS proxy service definition does not have the concept of Error Destination. To accomplish similar functionality go to JMSQ on (for which proxy is configured) server console (http://localhost:7001/console) and configure the Error Destination. Following URL will help in how to configure JMS Q.
    http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/jms_modules/queues/ConfigureQueues.html
    http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/jms_modules/queues/ConfigureQueueDeliveryFailure.html
    I tried use the proxy service to consume message from the jms topic . and generation an error in the proxy message flow. But the message didn't goes into the error topic.If every thing is configured as per above step, then the after retries, the weblogic server will put the message into JMS topic configured. Your proxy will receive from this topic.
    Let me know if we are not on same page.
    Cheers
    Manoj

  • Error when trying to enqueue message on to weblogic JMS queue

    Hi,
    I have developed a BPEL process to enqueue message on to a JMS queue in weblogic 10.3.1.BPEL process manager version is 10.1.3.4. I have referred the Oracle note 549016.1 for configuring the Jms adapter for BEA Weblogic JMS Provider.
    In the invoke activity, I am getting the following error:
    "Missing class: weblogic.security.acl.UserInfo
    Dependent class: weblogic.jndi.WLInitialContextFactory
    Loader: JmsAdapter:0.0.0
    Code-Source: /D:/product/10.1.3.1/orasoa/j2ee/oc4j_soa/connectors/JmsAdapter/JmsAdapter/weblogic.jar
    Configuration: &lt;code-source> in D:\product\10.1.3.1\orasoa\j2ee\oc4j_soa\connectors\JmsAdapter\JmsAdapter
    The missing class is not available from any code-source or loader in the system."
    I could not find a resolution. Please provide your inputs.
    Thanks.
    John

    Could be this, if the above fix was by generating a wlfull client jar:
    http://download.oracle.com/docs/cd/E14571_01/web.1111/e13717/jarbuilder.htm#BABCGHFH
    Edited by: atheek1 on Jul 28, 2010 9:39 PM

  • JMS error: weblogic.jms.frontend.FEConnectionFactoryImpl_1032_WLStub

    hi weblogic users,
    i have a problem in sending jms messages
    across two different weblogic host/domain.
    the configuration is:
    jms client:
    -JAX-WS webservice web app
    -deployed in WebLogic Server Version: 10.3.1.0
    -host: 192.168.30.133:7011
    -domain: ChSoaAdminServer1
    -can access server's console: http://192.168.1.22:6001/console
    server:
    -jms server, jms module, cf, queue configured
    with subdeployment targeted to the jmsserver
    -deployed in WebLogic Server Version: 10.3.2.0
    -host: 192.168.1.22:6001
    -domain: soa_domain
    -cannot access client's console: http://192.168.30.133:7011/console
    i use standard lookup method in my java client code:
    String settingJmsServer="t3://192.168.1.22:6001";
    String settingCF="jms/adminduk/cf";
    String settingQueue="jms/adminduk/queue/central";
    env=new Hashtable();
    env.put( Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory" );
    env.put(Context.PROVIDER_URL, settingJmsServer);
    ctx = new InitialContext( env );
    System.out.println("-- Destination");
    ds = (Destination) ctx.lookup(settingQueue);
    System.out.println("-- ConnectionFactory");
    cf = (ConnectionFactory) ctx.lookup(settingCF);
    but it's getting exception
    when looking up the connection factory (look at the bottom of my post):
    ok now, how to solve this problem?
    -i tried to change the server to another host with WL 10.3.1.0 installed (so
    it's the same version with the client) and its ok (receiving messages)
    -i tried to deploy the WS client to the same host as the jms (WL 10.3.2.0), so no
    remote lookup needed (java lookup code adjusted), it's ok
    -based on the stack trace:
    "Could not find dynamically generated class:
    'weblogic.jms.frontend.FEConnectionFactoryImpl_1032_WLStub
    (class not found) ..."
    -does it mean do i've to use the same version of WL installed in the client side ??
    -is WL 10.3.2.0 compatible with WL 10.3.1.0 ?
    -is it possible to use a different version of weblogic (in the client/server)
    in using the jms feature ?
    -do the jms server must have access to client's port (7011) for it to work ?
    thanks,
    any info/hints/helps will be appreciated :)
    ---------- start error ---------
    ####<Mar 23, 2010 4:24:51 PM ICT> <Error> <com.sun.xml.ws.server.sei.EndpointMethodHandler>
    <coolpie> <ChSoaAdminServer1> <[ACTIVE] ExecuteThread: '1' for queue:
    'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1269336291921> <BEA-000000>
    <***** ASSERTION FAILED *****[ Could not find dynamically generated class:
    'weblogic.jms.frontend.FEConnectionFactoryImpl_1032_WLStub' ]
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not find dynamically
    generated class: 'weblogic.jms.frontend.FEConnectionFactoryImpl_1032_WLStub' ]
         at weblogic.utils.classfile.utils.CodeGenerator.generateClass(CodeGenerator.java:78)
         at weblogic.rmi.internal.StubGenerator.hotCodeGenClass(StubGenerator.java:775)
         at weblogic.rmi.internal.StubGenerator.getStubClass(StubGenerator.java:759)
         at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:786)
         at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:779)
         at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:74)
         at weblogic.rmi.internal.StubInfo.resolveObject(StubInfo.java:213)
         at weblogic.rmi.internal.StubInfo.readResolve(StubInfo.java:207)
         at sun.reflect.GeneratedMethodAccessor126.invoke(Unknown Source)
         at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at java.io.ObjectStreamClass.invokeReadResolve(ObjectStreamClass.java:1061)
         at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1762)
         at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
         at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
         at
    weblogic.jms.client.JMSConnectionFactory.readExternal(JMSConnectionFactory.java:382)
         at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1792)
         at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1751)
         at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
         at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
         at
    weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:197)
         at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:564)
         at
    weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:193)
         at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:62)
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:240)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
         at weblogic.jndi.internal.ServerNamingNode_1031_WLStub.lookup(Unknown Source)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:400)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:388)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at
    weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:194)
         at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
         at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
         at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:388)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at siak.model.MessageManager.init(MessageManager.java:101)
         at siak.ws.SiakWS.sendEvent(SiakWS.java:37)
         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:597)
         at
    weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:101)
         at
    weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:83)
         at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:152)
         at
    com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:264)
         at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
         at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:604)
         at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:563)
         at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:548)
         at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:445)
         at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:249)
         at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:453)
         at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:250)
         at
    com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:140)
         at
    weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:298)
         at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:211)
         at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:297)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:87)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at
    weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java
    :227)
         at
    weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:202)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletConte
    xt.java:3588)
         at
    weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at
    weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2200)
         at
    weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2106)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1428)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    java.lang.ClassNotFoundException: weblogic.jms.frontend.FEConnectionFactoryImpl_1032_WLStub
         at
    weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:296)
         at
    weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:269)
         at
    weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:55)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
         at
    weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:177)
         at
    weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:36)
         at
    weblogic.utils.classloaders.FilteringClassLoader.findClass(FilteringClassLoader.java:100)
         at
    weblogic.wsee.util.JAXWSClassLoaderFactory$1.findClass(JAXWSClassLoaderFactory.java:45)
         at
    weblogic.utils.classloaders.FilteringClassLoader.loadClass(FilteringClassLoader.java:85)
         at
    weblogic.utils.classloaders.FilteringClassLoader.loadClass(FilteringClassLoader.java:80)
         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:247)
         at
    weblogic.utils.classloaders.GenericClassLoader.defineCodeGenClass(GenericClassLoader.java:516
         at weblogic.utils.classfile.utils.CodeGenerator.generateClass(CodeGenerator.java:73)
         at weblogic.rmi.internal.StubGenerator.hotCodeGenClass(StubGenerator.java:775)
         at weblogic.rmi.internal.StubGenerator.getStubClass(StubGenerator.java:759)
         at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:786)
         at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerator.java:779)
         at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:74)
         at weblogic.rmi.internal.StubInfo.resolveObject(StubInfo.java:213)
         at weblogic.rmi.internal.StubInfo.readResolve(StubInfo.java:207)
         at sun.reflect.GeneratedMethodAccessor126.invoke(Unknown Source)
         at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at java.io.ObjectStreamClass.invokeReadResolve(ObjectStreamClass.java:1061)
         at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1762)
         at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
         at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
         at
    weblogic.jms.client.JMSConnectionFactory.readExternal(JMSConnectionFactory.java:382)
         at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1792)
         at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1751)
         at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
         at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
         at
    weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:197)
         at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:564)
         at
    weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:193)
         at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:62)
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:240)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
         at weblogic.jndi.internal.ServerNamingNode_1031_WLStub.lookup(Unknown Source)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:400)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:388)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at
    weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:194)
         at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
         at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
         at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:388)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at siak.model.MessageManager.init(MessageManager.java:101)
         at siak.ws.SiakWS.sendEvent(SiakWS.java:37)
         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:597)
         at
    weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:101)
         at
    weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:83)
         at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:152)
         at
    com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:264)
         at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
         at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:604)
         at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:563)
         at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:548)
         at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:445)
         at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:249)
         at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:453)
         at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:250)
         at
    com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:140)
         at
    weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:298)
         at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:211)
         at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:297)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:87)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at
    weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java
    :227)
         at
    weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:202)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at
    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletConte
    xt.java:3588)
         at
    weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at
    weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2200)
         at
    weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2106)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1428)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    ---------- end error ---------

    1 - A class-not-found is an odd exception to get on a server. Did you perhaps try to add client-only jars to the server classpath? The server classpath is already setup properly to act as a client.
    2 - Its usually not a good practice to create contexts in client code (instead of simply using the Servlet context in your case), or to hard code URLs, dests, and CF references into the code. It works, but can be hard to maintain and inefficient.
    3 - See:
    [ Enhanced Support for Using WebLogic JMS with EJBs and Servlets |  http://download.oracle.com/docs/cd/E15523_01/web.1111/e13727/j2ee.htm#g1329180 ]
    and
    [ Integrating Remote JMS Providers | http://download.oracle.com/docs/cd/E15523_01/web.1111/e13727/interop.htm#JMSPG553 ]
    and the cross-domain advice in
    [ Integration and Multi-Domain Best Practices |
    http://download.oracle.com/docs/cd/E15523_01/web.1111/e13738/best_practice.htm#CACFBCHB ]
    Hope this helps,
    Tom

  • Using JMS Event Generator w/ remote WebLogic 8.1 queue

    Hello,
    I'm trying to create a workflow that is started by a JMS message queue event.
    I'm trying to use the WLIJMSEventGenTool in WebLogic 8.1 to listen to a queue
    on a remote WebLogic 8.1 installation, publish the incoming messages to a channel,
    then initiate a workflow by subscribing to that channel. Here's a copy of my configuration
    file for the tool:
    <message-broker-jms-event-generator-def source-jndi-name="SearchInputQueue"> <channel
    name="/srm/sInput/sInput" /> </message-broker-jms-event-generator-def >
    I tried to tackle this by configuring a foreign JMS Server, Connection Factory,
    and Destination using the Weblogic Admin Console. Below are the parameters I used
    to define the remote connection
    Foreign JMS Server:
    jndi initial context factory: weblogic.jndi.WLInitialContextFactory jndi connection
    url: //OPER1090:7001
    Foreign connection factory:
    local jndi name: FtsFactory remote jndi name: weblogic.jws.jms.QueueConnectionFactory
    (Are username and password required?)
    Foreign JMS Destination:
    local jndi name: SearchInputQueue remote jndi name: InternalSearchInputQueue
    After I try to deploy my generated JMS Event jar, I receive the following error:
    <Jun 6, 2003 10:31:50 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven
    E JB: SearchInputQueue-UnorderedMessageListener is unable to connect to the JMS
    de stination: SearchInputQueue. The Error was: [EJB:011010]The JMS destination
    with the JNDI name: SearchInputQueue could not b e found. Please ensure that the
    JNDI name in the weblogic-ejb-jar.xml is correct , and the JMS destination has
    been deployed.>
    I'm pretty sure the problem is simply that my syntax is off somewhere in my configuration.
    I found the existing BEA documentation to be a bit too generic, containing no
    specific examples of the proper syntax to use for this task. Can anyone offer
    any advice or better, a working example? Any BEA reps out there?

    Hello,
    I'm trying to create a workflow that is started by a JMS message queue event.
    I'm trying to use the WLIJMSEventGenTool in WebLogic 8.1 to listen to a queue
    on a remote WebLogic 8.1 installation, publish the incoming messages to a channel,
    then initiate a workflow by subscribing to that channel. Here's a copy of my configuration
    file for the tool:
    <message-broker-jms-event-generator-def source-jndi-name="SearchInputQueue"> <channel
    name="/srm/sInput/sInput" /> </message-broker-jms-event-generator-def >
    I tried to tackle this by configuring a foreign JMS Server, Connection Factory,
    and Destination using the Weblogic Admin Console. Below are the parameters I used
    to define the remote connection
    Foreign JMS Server:
    jndi initial context factory: weblogic.jndi.WLInitialContextFactory jndi connection
    url: //OPER1090:7001
    Foreign connection factory:
    local jndi name: FtsFactory remote jndi name: weblogic.jws.jms.QueueConnectionFactory
    (Are username and password required?)
    Foreign JMS Destination:
    local jndi name: SearchInputQueue remote jndi name: InternalSearchInputQueue
    After I try to deploy my generated JMS Event jar, I receive the following error:
    <Jun 6, 2003 10:31:50 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven
    E JB: SearchInputQueue-UnorderedMessageListener is unable to connect to the JMS
    de stination: SearchInputQueue. The Error was: [EJB:011010]The JMS destination
    with the JNDI name: SearchInputQueue could not b e found. Please ensure that the
    JNDI name in the weblogic-ejb-jar.xml is correct , and the JMS destination has
    been deployed.>
    I'm pretty sure the problem is simply that my syntax is off somewhere in my configuration.
    I found the existing BEA documentation to be a bit too generic, containing no
    specific examples of the proper syntax to use for this task. Can anyone offer
    any advice or better, a working example? Any BEA reps out there?

  • Connect from Weblogic JMS queue to SAP WAS JMS queue

    Hi,
    I am trying to setup a WLS 8.1 messaging bridge between a weblogic JMS queue and a SAP WAS JMS queue. I have configured a queue on both Weblogic and SAP WAS and I have set up the messaging bridge and bridge destintations in weblogic. However when weblogic tries to get the SAP initial context factory it fails with the error below.
    I have added the SAP Client jars to the weblogic system classpath, and in the weblogic startup script but it still fails. Has anyone connected from an external JMS queue to a SAP WAS JMS queue that could provide me with some guidence?
    <10/08/2006 08:23:45 AM WST> <Warning> <Connector> <BEA-190032> << Weblogic Mess
    aging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAllocatio
    nException of javax.resource.ResourceException: ConnectionFactory: failed to get
    initial context (InitialContextFactory =com.sap.engine.services.jndi.InitialCon
    textFactoryImpl, url = ux0800:55304, user name = username) on createManagedConnectio
    n.>
    Thanks
    Warren

    Stoyan,
    Thanks for that.
    My problem ended up being a classpath problem. I referenced the directory of the SAP jars in the weblogic start up script. When I changed this to reference each jar individually it worked.
    I have a new issue now which may have something to do with security. The trace suggests it is logging on as the guest user, even though I entered my username and password in the Messaging bridge.
    #1.5#000E7FED310600A30000008A0000302D00041AA399E338B4#1155189870559#com.sap.jms##com.sap.jms.server.sessioncontainer.InboundBus instance=BWIP#J2EE_GUEST#0####165536f0283611db8903000e7fed3106#SAPEngine_Application_Thread[impl:3]_126##0#0#Error##Plain###com.sap.jms.server.exception.JMSServerInvalidDestinationException: No destination with ID=0 found.
            at com.sap.jms.server.service.impl.RegistryServiceImpl.getDestinationContext(RegistryServiceImpl.java:404)
            at com.sap.jms.server.sessioncontainer.InboundBus.getDestinationContext(InboundBus.java:98)
            at com.sap.jms.server.sessioncontainer.InboundBus.process(InboundBus.java:153)
            at com.sap.jms.server.sessioncontainer.InboundBus.enqueue(InboundBus.java:116)
            at com.sap.jms.server.sessioncontainer.SessionContainer.receiveFromDispatcher(SessionContainer.java:63)
            at com.sap.jms.server.routingcontainer.RoutingContainer.receiveFromDispatcher(RoutingContainer.java:447)
            at com.sap.jms.server.JMSServerContainer.dispatchRequest(JMSServerContainer.java:635)
            at com.sap.jms.server.JMSServerFrame.request(JMSServerFrame.java:536)
            at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
            at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
            at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Warren

  • Weblogic JMS Client App fails creating queue connection

    Using the example provided from installation: ...\bea\wlserver_10.0\samples\server\examples\src\examples\jms\queue\QueueBrowse.java
    I can successfully connect and display the queue when this test app runs on the local Weblogic Server. When I run the test app on a remote server (not the Weblogic server), I get the following error:
    Exception in thread "main" weblogic.jms.common.JMSException: [JMSClientExceptions:055053]Error creating connection to the server: java.rmi.MarshalException: failed to marshal connectionCreateRequest(Lweblogic.jms.frontend.FEConnectionCreateRequest;); nested exception is:
         java.rmi.UnexpectedException: Failed to parse descriptor file; nested exception is:
         java.lang.NullPointerException
         at weblogic.jms.client.JMSConnectionFactory.setupJMSConnection(JMSConnectionFactory.java:258)
         at weblogic.jms.client.JMSConnectionFactory.createConnectionInternal(JMSConnectionFactory.java:285)
         at weblogic.jms.client.JMSConnectionFactory.createQueueConnection(JMSConnectionFactory.java:165)
         at com.lodestarcorp.custom.QueueBrowse.init(QueueBrowse.java:53)
         at com.lodestarcorp.custom.QueueBrowse.main(QueueBrowse.java:129)
    Caused by: java.rmi.MarshalException: failed to marshal connectionCreateRequest(Lweblogic.jms.frontend.FEConnectionCreateRequest;); nested exception is:
         java.rmi.UnexpectedException: Failed to parse descriptor file; nested exception is:
         java.lang.NullPointerException
         at weblogic.rjvm.BasicOutboundRequest.marshalArgs(BasicOutboundRequest.java:91)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:332)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
         at weblogic.jms.frontend.FEConnectionFactoryImpl_1001_WLStub.connectionCreateRequest(Unknown Source)
         at weblogic.jms.client.JMSConnectionFactory.setupJMSConnection(JMSConnectionFactory.java:224)
         ... 4 more
    Caused by: java.rmi.UnexpectedException: Failed to parse descriptor file; nested exception is:
         java.lang.NullPointerException
         at weblogic.rmi.internal.DescriptorManager.createRuntimeDescriptor(DescriptorManager.java:118)
         at weblogic.rmi.internal.DescriptorManager.getBasicRuntimeDescriptor(DescriptorManager.java:89)
         at weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManager.java:55)
         at weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManager.java:41)
         at weblogic.rmi.internal.OIDManager.makeServerReference(OIDManager.java:194)
         at weblogic.rmi.internal.OIDManager.getReplacement(OIDManager.java:175)
         at weblogic.rmi.utils.io.RemoteObjectReplacer.replaceSmartStubInfo(RemoteObjectReplacer.java:116)
         at weblogic.rmi.utils.io.RemoteObjectReplacer.replaceObject(RemoteObjectReplacer.java:102)
         at weblogic.rmi.utils.io.InteropObjectReplacer.replaceObject(InteropObjectReplacer.java:62)
         at weblogic.utils.io.ChunkedObjectOutputStream.replaceObject(ChunkedObjectOutputStream.java:40)
         at weblogic.utils.io.ChunkedObjectOutputStream$NestedObjectOutputStream.replaceObject(ChunkedObjectOutputStream.java:141)
         at java.io.ObjectOutputStream.writeObject0(Unknown Source)
         at java.io.ObjectOutputStream.writeObject(Unknown Source)
         at weblogic.messaging.dispatcher.DispatcherWrapper.writeExternal(DispatcherWrapper.java:152)
         at weblogic.jms.frontend.FEConnectionCreateRequest.writeExternal(FEConnectionCreateRequest.java:98)
         at java.io.ObjectOutputStream.writeExternalData(Unknown Source)
         at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source)
         at java.io.ObjectOutputStream.writeObject0(Unknown Source)
         at java.io.ObjectOutputStream.writeObject(Unknown Source)
         at weblogic.rjvm.MsgAbbrevOutputStream.writeObject(MsgAbbrevOutputStream.java:614)
         at weblogic.rjvm.MsgAbbrevOutputStream.writeObjectWL(MsgAbbrevOutputStream.java:605)
         at weblogic.rmi.internal.ObjectIO.writeObject(ObjectIO.java:38)
         at weblogic.rjvm.BasicOutboundRequest.marshalArgs(BasicOutboundRequest.java:87)
         ... 8 more
    Caused by: java.lang.NullPointerException
         at weblogic.rmi.internal.BasicRuntimeDescriptor.createSkeletonClass(BasicRuntimeDescriptor.java:272)
         at weblogic.rmi.internal.BasicRuntimeDescriptor.<init>(BasicRuntimeDescriptor.java:158)
         at weblogic.rmi.internal.BasicRuntimeDescriptor.<init>(BasicRuntimeDescriptor.java:140)
         at weblogic.rmi.internal.DescriptorManager.createRuntimeDescriptor(DescriptorManager.java:110)
         ... 30 more
    FYI: I did create the wlfullclient.jar from the installation.
    Could the problem be related to a proxy issue? It's not a DNS problem (I've tested with the IP address).
    Thanks,
    Brian

    I had this very same issue, in a project I was importing directly individual jars:
         <classpathentry kind="lib" path="lib/javax.jms_1.1.1.jar"/>
         <classpathentry kind="lib" path="lib/weblogic.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.weblogic.security.identity_1.1.2.1.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.weblogic.workmanager_1.9.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.weblogic.workmanager.ja_1.9.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.transaction_2.7.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.weblogic.rmi.client.ja_1.8.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.weblogic.rmi.client_1.8.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.weblogic.security.wls_1.0.0.0_6-1-0-0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.utils.full_1.9.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.weblogic.security_1.0.0.0_6-1-0-0.jar"/>
         <classpathentry kind="lib" path="lib/wlclient.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.utils.classloaders_1.8.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.management.core_2.8.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.descriptor_1.9.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.logging_1.8.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.timers_1.7.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.weblogic.socket.api_1.2.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.weblogic.security.digest_1.0.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.weblogic.lifecycle_1.4.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.store_1.7.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.common.security.api_1.0.0.0_6-1-0-0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.utils.wrapper_1.4.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.messaging.kernel_1.8.0.0.jar"/>
         <classpathentry kind="lib" path="lib/com.bea.core.utils.expressions_1.4.0.0.jar"/>
    and everything was working;
    in another project I was importing the "Weblogic System Libraries" libraries, and I was getting the NullPointerException...
    I have the sensation that there is room for improvement in the way libraries are managed.

  • Configure backout queue and Dead letter queue in weblogic JMS provider

    Hi,
    How to configure the JMS backout queue and dead letter queue in weblogic JMS provider in weblogic application server console?
    Any links or documents are highly appreciated.
    Thanks.

    Thanks anon. When i say backout message the poisonous message , A poison message is one which cannot be processed by a receiving MDB application. If a poison message is encountered, the JMS MessageConsumer and ConnectionConsumer objects can requeue it according to two queue properties, BOQUEUE, and BOTHRESH.
    Normally this happens in the websphere MQ . Where we will configure the backout queue and dead letter queue.
    The dead letter queue was always used in MQSeries (the last time I used MQ) to store messages that arrived at the queue manager but the queue didn't exist. For eample, if the message was address to queue manager X and queue Y, it would arrive via a channel at manager X. If the receiver channel discovered there was no queue Y, it would be placed in the dead letter queue.
    The backout queue, on the other hand, is more of an application-level thing (at least in terms of MQ). When an MQ client cannot process the message for some reason, it can back it out for later processing (back to it's original queue).If it's backed out too many times (the threshold can be configured), it gets moved to the backout queue.
    The Dead Letter Queue behaves the same as a Backout. I treat the Dead Letter Queue as the Crematorium for messages that cannot be recovered in the Error or Backout queues and have some last, non-business specific data that need be collected. Once the info is captured, the message is put down for good. Backout is good for analyzing messages for data that may need to be recovered to completely reprocess or be sent back to an application area for them to decision on.
    How we configure these in weblogic server both Backout and Deadletter queue , whether this is a simple queue in which we will set the error destination in case of any poisonous message so that it will logged in those queue?
    Thanks.

  • Weblogic JMS bridge between Weblogic and oracle Advanced Queue

    Hi,
    We are facing some issues when we are trying to integrate with Oracle AQ JMS through Weblogic.
    We have configured a Foreign AQ server which points to the oracle Advanced Queue and we are trying to create a Weblogic JMS bridge between AQ and weblogic. The bridge works perfectly if create the connection factories and bridge destinations with NonTX mode. The issue is with XA mode. Also we have deployed the Resource adaper for XAResource to use XA transactions.
    No help is available for the exception on google too :)
    Following is the exception we are getting.
    <An error occurred in bridge "aqjmsbridge" during the transfer of messages (javax.resource.ResourceException: Failed to setup the Resource Adapter Connection for enlistment in the transaction, Pool = 'eis/jms/WLSConnectionFactoryJNDIXA', javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XA_OK
    javax.transaction.xa.XAException: method start should not be called on weblogic.transaction.internal.IgnoreXAResource
    at weblogic.jms.foreign.IgnoreXAResourceImpl.start(ForeignAQIntegration.java:260)
    at weblogic.connector.security.layer.AdapterLayer.start(AdapterLayer.java:513)
    at weblogic.connector.transaction.outbound.XAWrapper.start(XAWrapper.java:466)
    at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1184)
    at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1117)
    at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:275)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:516)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:443)
    at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:118)
    at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
    at $Proxy59.receive(Unknown Source)
    at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1427)
    at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1002)
    at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1079)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    .).>
    Will appriciate any help for the above.
    Thanks and Regards,
    Navin

    Maybe this if of any help:
    - Re: Help with creating AQ JMS
    or
    - Re: AQ Weblogic integration - JMS-107: Operation not allowed on Connection

  • Oracle PL/SQL send/receive message in weblogic jms queue

    I am looking for a very simple way using oracle plsql to send and receive messages in a weblogic jms queues.
    Thanks

    Even i am looking for the same . Would be great if someone would help ..The jms setup has to be done in weblogic like the jms server, jms module, Jms connection factory , jms queue and then the jndi names . Now thw Problem here lies to me is that i really dont knw what should be the connection factory targets ,jndi names and where do i give the schema details as in the user name ,password , db name . Also if there is any explaination with eg on how to send /receive messages from a db trigger to jms queues .

Maybe you are looking for

  • Caret position in JEditorPane HTML

    Hi everyone, I need the position of caret in HTML source on JEditorPane. I The value of getCaretPosition() seems not what I wanted. CaretEvent.getDot() gives the same value of getCaretPosition. These methods only gets position on the view. Please hel

  • Swing Framework Suggestions

    Hi, I'm new to Swing and am looking for a good book and/or white paper on the correct way to structure a swing application in JDK 1.6. There are a lot of ways to do things but I'm looking for suggestions for the simple stuff: best way to start up and

  • Sharing folders between accounts

    How do I share a folder between accounts in the same iMac without having to move the original folders to public folders or without having to connect via AFP/SMB? I want another user to log in to his account and being able to see a shared folder in hi

  • Export ProRes on New MacPro running Mavrick OS.

    Source material was  mix of ProRes and ProResHQ QuickTime - 1280x720 and maybe 1920x1080 on the same timeline. Some of the frames were corrupted - there is picture but it's just digital garbage on screen. The only workaround we found was to turn off

  • Batch Input ME47 - Get Item position error

    I'm doing BDC to ME47 passing header and several positions in a RFC. The functional wants  the RFC inform which position caused the error. In the message table of the call transaction doesn't show any info of the position. I think it can't be done bu