MDB on OC4J consuming from a forign JMS Server

I would like to create MDBs and deploy them to OC4J. But these MDBs need to consume messages from non-AQ JMS Servers. We are currently using MDBs in OC4J that consume from Oracle AQ using resource adapters. But we now have a need to use other JMS servers such as OpenJMS and JbossMQ.
I have read documents that seem to indicate
Message-driven beans are supported only for Oracle JMS.
Does this mean I cannot create a resource adapter for JbossMQ and deploy a MDB to OC4J that consumes from this JMS Server?
Any help would be most appreciated!
Thanks, Paul.

Anybody has faced similar issue?

Similar Messages

  • MDB unable to listen anymore after remote JMS server crashed and restarted

    I'm running Weblogic Server 8.1 SP4 on a Win 2k server. My remote JMS server is running Sonic 6.0 on a Win 2k server. Both are connected in the same network. My problem is that whenever I restart the JMS server after it crashes (improper shutdown), my MDBs will not be able to listen to any messages sent to the topic/queue. WL console does not display any error about MDB unable to connect to the topic/queue as if the JMS server was never down. I have to re-deploy my apps in order to get the MDBs working. Is there a workaround or patch for this 'bug'?

    The options I can think of are:
              (1) Configure a WebLogic messaging bridge that runs in "synchronous" mode for forwarding messages from Sonic to a WL destination. Then change MDB to refer to the WL destination. Alternatively, if you haven't already, try using a transactional MDB - which may or may not use synchronous receives to get messages from Sonic (depends on the version of Sonic I believe). The reason I think this might help in either method is that I think the use of synchronous receives may yield a better chance of detecting failures in Sonic.
              (2) See if Sonic itself requires a patch.
              (3) Try out WL 9.2 instead of WL 8.1 (it may be that the Sonic work-around I vaguely recall isn't in 8.1???)
              (4) Contact customer support.

  • Weblogic 10.3 not suporting for MDB to connect remote Weblogic JMS server

    Hi,
    I have a problem with MDB deployed on Weblogic 10.3.It's simple MDB which is communicating with remote weblogic JMS server. I am getting below exception. could some one help how to resolve this issue.
    <Apr 14, 2009 11:28:52 AM PDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: ReceiverFromDocumentum is unable to con
    nect to the JMS destination: FMAContractOutboundQueue. The Error was:
    [EJB:011013]The Message-Driven EJB attempted to connect to the JMS connection factory with the JNDI name: FMAConnectionFacto
    ry. However, the object with the JNDI name: FMAConnectionFactory is not a JMS connection factory. NestedException Message is
    :weblogic.jms.client.JMSConnectionFactory cannot be cast to javax.jms.XAConnectionFactory>
    -Sreekanth

    I recall that this particular warning message is sometimes misleading about the root cause of the problem, an issue that I think has been fixed in a patch. The actual problem can be various:
    * The MDB is configured to be transactional, the connection factory exists, but the connection factory isn't configured to be "XA enabled". (I think this is the most likely problem).
    * The connection factory doesn't exist.
    * The object in JNDI with the specified connection factory name isn't actually a connection factory.
    * The dest object in JNDI with the specified name isn't actually a javax.jms.Destination
    Note that its unusual to configure the connection factory name for an MDB that consumes from WebLogic JMS. The default name iis usually sufficient unless custom tuning is required on the connection factory. See the MDB section of the EJB developer guide for more information.
    Tom

  • MDBs failed to connect to remote JMS server

    Hi,
              We currently have 2 clusters: one is a regular cluster (cluster1) and the other is JMS cluster (cluster2). Our JMS server and filestore are targeted to a migratable server in JMS cluster.
              In our weblogic-ejb-jar.xml, we added element <provider-url> to the <message-driven-descriptor> to allow JMS remote connection as follows:
              <weblogic-enterprise-bean>
                   <ejb-name>MyBean</ejb-name>
                   <message-driven-descriptor>
                        <destination-jndi-name>MyTopic</destination-jndi-name>
              <provider-url>t3://myhost:19009,myhost:19011</provider-url>
              <connection-factory-jndi-name>MyConnectionFactory</connection-factory-jn
              di-name>
                   </message-driven-descriptor>
              </weblogic-enterprise-bean>
              When we deployed our application, the Connection Status of MyBean showed "disconnected". I have tried different values (t3://myhost:19009;t3://myhost:19011) and
              (t3://myhost:19009) but got the same result.
              When I re-targeted the JMS server and filestore to a regular server (instead of migratable server), I was able to connect remotely. But because we want to be able to migrate our JMS server (auto and manually), I have to target it to a migratable server.
              I could not figure out why my MDBs failed to connect to a remote JMS server when it is targeted to a migratable server? Is there a restriction that we have to target to a regular server in order to connect remotely or I'm doing something wrong?
              Any help would be greatly appreciated.
              Thanks,
              Thao

    I'm using WL9.2 and my migratable server is actually up and running (is that what you mean about booted?).                    I meant checking your log files to make sure that the JMS server itself actually booted, not checking that the host WL server was up. (For example you should see INFO messages indicating that the JMS server has loaded "X" records from its persistent store).
              >>> Could you elaborate on the known problem?
              9.x MDBs have special code for enhanced handling of remote distributed destinations. I'm guessing that this code is somehow causing problems when the remote JMS server is migratable. I don't have enough information to elaborate further than that.
              >>> What else I can try?
              Beyond contacting customer support, I'm not sure.
              Tom

  • JMS server in a cluster

              I have a JMS server deployed to one of the instances in my 2 instance cluster.
              I have an MDB attached to a queue on the JMS server (NOT a distributed destination).
              If I run both weblogic instances on one physical server, both instances can see
              and use the JMS server. My MDB correctly finds its destination on both instances.
              If I put the instances on separates physical servers, then the server that doesn't
              have the JMS server deployed cannot find the JMS destination for its MDB.
              Why should the behavior be different if I run the cluster all on one machine or
              spread it between 2 machines?
              I've attached my config.xml for reference. Thanks for any help,
              Colin
              

    I have seen other users as well complaining about the same issue "[Security:090398]Invalid Subject" frequently. You may check with Oracle Support for possible solution for your system version.
    Regards,
    Anuj

  • Messaging Bridge/Foreign JMS Server

    Can someone clarify what is the difference in using messaging bridge or Foreign JMS Server in listening to a topic from other weblogic server of same version.
    Edited by: user11359157 on 6 Jul, 2009 3:17 PM

    I always thought one has to use remote classes from the foreign JMS server in local the classpath to send or receive messages stored at
    the foreign JMS server / the remote side.
    <Jayesh> that is true of the remote side of the JMS is non-weblogic. </Jayesh>
    Also in the WLS bridge this can be specified. IMHO the bridge has the advantage that I can use the wls classe and the bridge knows
    the classpath and bridges to the foreign jms server, so the application developer doesn't have to use foreign classes, eg. tibco or mq.
    <Jayesh> When you have remote JMS is WebLogic it is obvious considering that both remote and local jms uses same weblogic classes. </Jayesh>
    Now, where does this happen for the foreign jms server (which is kind of alternative to wls bridge, without store and forward)?
    All I can see is a local JNDI lookup being translated to a remote one.
    Is really the local JMS implementation used to talk to the remote JMS server?
    When a JNDI lookup for a queue happens will then be WLS queue implementation returned?
    <Jayesh> No there is not local JMS store is used. Foreign JMS server just provides administrative convenience by moving remote JMS destination JNDI definitions in local JNDI definition. It allows to use this local definition by all EJBs, servlets and messaging bridges. If the remote definitions changes you can change those definition in admin console and does not need change in deployment descriptors of the EJBs and servlets to prevent redeployment. Again this is no administrative convenience and during run time it will behave exactly same as you are sending or receiving message directly from remote JMS destination.
    </Jayesh>
    Hope this clears confusion.
    jayesh@yagna

  • Load balancing MQ 7.0 Foreign JMS Server and Weblogic 10 MDBs?

    We have the following configuration and we are trying to troubleshoot what appears to be a load balancing issue.
    We have 3 Solaris servers. Each Solaris server has two Weblogic managed servers running on it. There are a total of 6 managed servers in the Weblogic cluster.
    MQ Series 7.0 is also installed on each Solaris server. The MQ queue managers are in a MQ cluster. Each queue manager has the same queues defined.
    We have a foreign JMS Server configured on Weblogic that has destinations and a connection factory defined. There aren't many configuration options available for the connection factory. The destinations are bound to the queues defined on MQ using the MQ bindings file.
    The MQ bindings file was generated using the TRANSPORT(BIND) mechanism. Each bindings file points to the queue manager running on that machine. So the 2 managed servers running on one machine are accepting messages from the queue manager on that machine.
    The MDB's listenning for messages on the MQ queues are configured as follows in the weblogic-ejb-jar.xml:
         <max-beans-in-free-pool>16</max-beans-in-free-pool>
    We also created a custom work manager with min threads constraint=5 and max threads constraint=16. The dispatch-policy of all the MDBs is set to the custom work manager.
    The open input count on each MQ queue managers shows up as 32 which is expected.
    The default load algorithm on the cluster is round-robin.
    When we run a load test (injecting 40 messages per second on one MQ queue), we notice that one managed server ends up being significantly loaded than the other. Each MQ queue manager in the MQ cluster receives approximately the same number of messages in the load test. But it seems like one managed server is preferred over the other in Weblogic.
    What can be done to equally balance the load among the two managed servers on each Solaris server?
    Thanks for the help.

    Load balancing generally applies at determing how many consumer threads has to be created on each of the clustered queue instance. In that sense you have achieved perfect load balancing as your queue instances has the same no of consumer threads.
    Once you have set 'x' consumer threads on a queue, it is upto messaging provider to decide which thread to deliver a particular message and you will hardly have any control over this. Since your 32 threads are listening on the same queue, MQ can select any thread for delivering the message and the behaviour could be non deterministic.
    One option to change your design is to have a dispacther mdb which picks the messages off the MQ and then routes to a weblogic distributed destination and you can have your core mdb which does all processing listen to this distributed destination. You can enable load balancing when the disaptcher mdb routes the message to the distributed destination. Since dispatcher MDB is nothing more than a router, the unbalanced consumption off the MQ shouldn't seriously affect the server.

  • MDB (2-phase commit) behavior during abnormal JMS termination

    Hello to everyone!
    I plan to test the following scenario tomorrow (sort of a bug replication in our system).
    Anyway, wanted to know in advance the expected behavior (just in case one of you already know
    or have an experience related to this test). Thank you in advance.
    Scenario:
    I want to test/know the behavior of a 2-phase commit (2PC) MDB when JMS server abnormally exits
    (say the process was killed).
    Test flow:
    start app server --> deploy 2pc-mdb --> send dummy data --> kill jms process --> restart jms process
    1. will the connection be closed properly?
    2. when jms server restarts, will the value of active consumer(count) doubled?
    note: i think after mdb deployment, corresponding destination consumer count is 1.
    the problem that occurred in our system was that the consumer count doubled after server restarted.
    it seem like the previous connection was not closed when the jms server abnormally terminated.
    any inputs will be greatly appreciated.
    thanks and best regards.

    You have to use TxDataSource for container managed tx or if you are using JTA (in
    addition to ofcourse doing 2PC).
    S
    "Dale Olzer" <[email protected]> wrote:
    >
    Using weblogic 6.1 SP 4
    I have a simple container managed Message Driven Bean. Using a destination
    type
    javax.jms.Queue.
    When the onMessage method finishes the Message is still Pending on the
    queue.
    see the ejb-jar.xml below
    <ejb-jar>
    <enterprise-beans>
    <message-driven>
    <display-name>IvrMessageBean</display-name>
    <ejb-name>IvrMsgBean</ejb-name>
    <ejb-class>com.edocs.ps.ivr.IvrMsgBean</ejb-class>
    <transaction-type>Container</transaction-type>
    <acknowledge-mode>Auto-acknowledge</acknowledge-mode>
    <message-driven-destination>
    <destination-type>javax.jms.Queue</destination-type>
    </message-driven-destination>
    </message-driven>
    </enterprise-beans>
    </ejb-jar>
    I noticed when I set a JDBC TX DataSource to 2 Phase Commit, the JMS
    transaction
    started commitig and nothing was left pending in the Queue.
    Does 2PC have to be set in a DataSource for Container Managed MDB's to
    work?

  • Cases where messages are not being consumed from a queue

    MQ 4.0
    I have a cluster of 3 brokers. Java clients use RANDOMIZE to connect to the cluster of brokers. Message selectors are not used. My consumers are all synchronous, and connection.start() is called prior to calling MessageConsumer.receive().
    What I have seen on random occassions are messages not being consumed from the queue. The problem seems to be sporadic.
    I was thinking that the reason it is sporadic is because of the RANDOMIZE configuration of the client connetion / object-store.
    That is, there is a possibility for the following to happen:
    1) There were messages produced on a queue on broker A, but before these messages were consumed, all the consumers have been shutdown. Thus, the messages on queue stayed on broker A .... and have not been copied / clustered to the other brokers in the cluster ( As per online documentation, a queue is "copied" to other brokers only when there is a consumer for that queue on the other brokers ).
    2) Then the client applications started up produced and consumers again. This time, the producers were all connected to broker B, and all consumers for the queue were also connected to broker B.
    3) Because there are no other consumers for the queue on the other brokers, the messages in the queue on broker A are never consumed.
    Can someone confirm that this is a possibility ?

    Well ... it does seem to be the case.
    I changed the object-store so that instead of using RANDOMIZE for imqAddressListBehavior, it uses PRIORITY. Therefore, all clients ( producers and consumers ) will connect to only 1 broker out of the 3 in the cluster.
    After restarting all JMS clients with the new imqAddressListBehavior, there were messages in various queues in the other brokers that were not being consumed, because there are no longer any consumers on any of the other brokers.
    All the messages in that broker that all JMS clients connect to are being consumed ...
    Except for about 6 messages that stays in the queue for whatever reason. All consumers receiving with receive( 10000 ), and after consuming all messages above the 6, it returns without any more messages in the queue.
    Well ... so much for cluster of brokers. I'll have to think of an alternative.

  • Weblogic 6.1 sp1 Application Server MDB does not consume messages

    I have the following situation:
    WebLogic Application Server 6.1 sp1. A deployed mdb does nothing - just sits idle
    even when the JMS queue it points to has many messages waiting to be consumed.
    When the application server is bounced (i.e., shutdown and restarted), the mdb
    starts processing the messages. JMS server has a JDBC backing store.
    Any ideas?
    Thanks,
    Prakash

    Tobin is right, my apoplication is called "portal", I am not using WLPortal. Anyway,
    I managed to resolve my problem,I had sax2 , xp and xt parsers placed in the WEB-INF\lib
    directory of my application in addition to my own jar file. I removed the parsers
    , and now my application is running fine.
    It is strange though, since my application used to load and work flawlessly on
    weblogic 6 as well as weblogic 6.1 sp1 with the parsers in the lib directory....
    Anyhow, thanks a lot for the help.
    Regards,
    Lalitha
    "Tobin Paterson" <[email protected]> wrote:
    >
    Having applied WLS 6.1 sp2 upgrade today I am seeing the same fault.
    I am not using
    WL Portal. Also I think the original poster's application just happens
    to be called
    "portal" and is not using WL Portal.
    cheers,
    Tobin.
    "BEA Support" <[email protected]> wrote:
    Hello,
    Only WLCS and/or WLPS 3.5 sp 2 support WLS 6.1 sp 2
    WL Portal 4.0 support only WLS 6.1 sp 1.
    Regards,
    Developer Relations Engineer
    BEA Support
    "Lalitha" <[email protected]> a écrit dans le message de news:
    [email protected]..
    Hi
    For some reason, my application 'portal' does not run on weblogic
    6.1
    sp2,
    It used to run fine on 6.1 sp1 .
    I am attaching the weblogic.log file with this msg.
    Thanks,
    Regards,
    Lalitha

  • MDB for Foreign JMS server

    I am trying to access MQ que with Message Driven bean in weblogic 8.1.
              I have defined Foreign JMS server in weblogic pointing to MQ JNDI name.
              I am not sure what to define in "weblogic-ejb-jar.xml" and "ejb-jar.xml" to refer to que connection factory and que.
              Error message that I am getting while deploying is as follows:
              <The Message-Driven EJB: MesssageHandlerBean is unable to connect to the JMS destination: jms.MediaQueue. The Error was:
              [EJB:011010]The JMS destination with the JNDI name: jms.MediaQueue could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.xml is correct, and the JMS destination has been deployed.>
              Looks like it weblogic is not able to identify JNDI name that I have defined in foreign server for remote que.
              Please let me know how i can reference foreign JMS server JNDI names.
              Thanks a bunch for help.
              Please find attached configuration files.
              weblogic-ejb-jar.xml
              <weblogic-ejb-jar>
              <weblogic-enterprise-bean>
              <ejb-name>MesssageHandlerBean</ejb-name>
              <message-driven-descriptor>
              <destination-jndi-name>
              jms.MediaQueue
              </destination-jndi-name>
              <initial-context-factory>
              com.sun.jndi.fscontext.RefFSContextFactory
              </initial-context-factory>
              <provider-url>file://localhost/d:/mqm</provider-url>
              <connection-factory-jndi-name>
              jms.MediaQcf
              </connection-factory-jndi-name>
              </message-driven-descriptor>
              <jndi-name>MesssageHandlerBean</jndi-name>
              </weblogic-enterprise-bean>
              </weblogic-ejb-jar>
              ejb-jar.xml
              <enterprise-beans>      
              <message-driven>
              <ejb-name>MesssageHandlerBean</ejb-name>
              <ejb-class>com.ejb.MesssageHandlerBean</ejb-class>
              <transaction-type>Container</transaction-type>
              <message-driven-destination>
              <destination-type>javax.jms.Queue</destination-type>
              </message-driven-destination>
              </message-driven>
              </enterprise-beans>
              weblogic "config.xml" for foeign JMS server.
              <ForeignJMSServer ConnectionURL="file://localhost/d:/mqm" InitialContextFactory="com.sun.jndi.fscontext.RefFSContextFactory"
              JNDIProperties="" Name="MQJMS Server" Targets="cgServer">
              <ForeignJMSConnectionFactory LocalJNDIName="jms.MediaQcf"
              Name="MQ JMS Connection Factory" PasswordEncrypted=""
              RemoteJNDIName="jms/lMediaQcf" Username=""/>
              <ForeignJMSDestination LocalJNDIName="jms.MediaQueue"
              Name="MQJMS Destination" RemoteJNDIName="jms/IMediaQueue"/>
              </ForeignJMSServer>
              Message was edited by:
              [email protected]
              Message was edited by:
              [email protected]

    Thanks for going over the problem it is resolved now by changing weblogic-ejb-jar.xml. To point to weblogic initial context factory. Since weblogic has a foreign server defined so MDB is able to read from MQ que.
              Thanks
              Akash
              <weblogic-enterprise-bean> <ejb-name>MesssageHandlerBean</ejb-name> <message-driven-descriptor> <destination-jndi-name>jms.MediaQueue</destination-jndi-name> <initial-context-factory> weblogic.jndi.WLInitialContextFactory</initial-context-factory> <provider-url>t3://localhost:7001</provider-url> <connection-factory-jndi-name>jms.MediaQcf</connection-factory-jndi-name> </message-driven-descriptor> <jndi-name>MesssageHandlerBean</jndi-name> </weblogic-enterprise-bean>

  • Oc4j craches from time to time(

    I use BI EE 10.1.3.3.3 with oc4j and from time to time oc4j crashes. It can be some times a day, one time a day, or a week(more rare).It happens on different pc's. (win xp).
    One crash has happened recently.
    There were changed three logs in j2ee/home/log:
    jms
    rmi
    system-application
    But it was chanched only date of change of this files
    a part of jms.log
    What can i try to do or check?

    Ive got error log named "hs_err_pid1288.log"
    # An unexpected error has been detected by Java Runtime Environment:
    # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00c3dd8e, pid=1288, tid=6092
    # Java VM: Java HotSpot(TM) Client VM (1.6.0-b105 mixed mode)
    # Problematic frame:
    # J EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap$HashIterator.hasNext()Z
    # If you would like to submit a bug report, please visit:
    # http://java.sun.com/webapps/bugreport/crash.jsp
    --------------- T H R E A D ---------------
    Current thread (0x2bbfe000): JavaThread "TaskManager" [_thread_in_Java, id=6092]
    siginfo: ExceptionCode=0xc0000005, reading address 0x864a1127
    Registers:
    EAX=0x064a1128, EBX=0x2541d3e0, ECX=0x02a831b0, EDX=0x2541d9d8
    ESP=0x2e02f960, EBP=0x2e02f978, ESI=0x064a1128, EDI=0x00000016
    EIP=0x00c3dd8e, EFLAGS=0x00010216
    Top of Stack: (sp=0x2e02f960)
    0x2e02f960: 2e02f960 2541c578 2e02f988 2541cad0
    0x2e02f970: 00000000 2541c590 2e02f9b4 00973379
    0x2e02f980: 2541d9c8 00973379 02a831b0 00000001
    0x2e02f990: 05c51d40 2e02f98c 245f1259 2e02f9cc
    0x2e02f9a0: 246ae840 00000000 245f12d0 2e02f988
    0x2e02f9b0: 2e02f9cc 2e02f9f8 00972c71 00000000
    0x2e02f9c0: 00000000 02a831b0 05c51d40 05c40108
    0x2e02f9d0: 00000001 05a27588 2e02f9d0 232ef7ef
    Instructions: (pc=0x00c3dd8e)
    0x00c3dd7e: 90 90 8b 71 0c 83 fe 00 0f 84 67 00 00 00 3b 06
    0x00c3dd8e: 8b be ff ff ff 7f 83 ff 00 0f 85 a4 00 00 00 3b
    Stack: [0x2dfe0000,0x2e030000), sp=0x2e02f960, free space=318k
    Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
    J EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap$HashIterator.hasNext()Z
    j com.evermind.server.http.HttpApplication.removeUnusedCacheFiles()V+25
    j com.evermind.server.http.HttpSite.removeUnusedCacheFiles()V+31
    J com.evermind.server.http.SessionTimeoutTask.run()V
    J com.evermind.util.Task.schedule(Lcom/evermind/util/TaskManager;)V
    J com.evermind.util.TaskManager.run()V
    j com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run()V+24
    j java.lang.Thread.run()V+11
    v ~StubRoutines::call_stub
    --------------- P R O C E S S ---------------
    Java Threads: ( => current thread )
    0x2b197800 JavaThread "HTTPThreadGroup-9" [_thread_blocked, id=4472]
    0x2b3e0400 JavaThread "HTTPThreadGroup-8" [_thread_blocked, id=5348]
    0x2bb19400 JavaThread "HTTPThreadGroup-7" [_thread_blocked, id=3512]
    0x2b2e7800 JavaThread "HTTPThreadGroup-6" [_thread_blocked, id=1452]
    0x2b2fc000 JavaThread "HTTPThreadGroup-5" [_thread_blocked, id=5824]
    0x2b821400 JavaThread "Timer-13" [_thread_blocked, id=5300]
    0x2b2b0400 JavaThread "HTTPThreadGroup-4" [_thread_blocked, id=2580]
    0x2ad5b400 JavaThread "Thread-29" daemon [_thread_blocked, id=2464]
    0x2bbb8000 JavaThread "Thread-28" daemon [_thread_blocked, id=2396]
    0x2cf05400 JavaThread "Thread-27" daemon [_thread_blocked, id=1240]
    0x2b399c00 JavaThread "Thread-26" daemon [_thread_blocked, id=6124]
    0x00396800 JavaThread "DestroyJavaVM" [_thread_blocked, id=2944]
    =>0x2bbfe000 JavaThread "TaskManager" [_thread_in_Java, id=6092]
    0x2b365800 JavaThread "DefaultQuartzScheduler_QuartzSchedulerThread" [_thread_blocked, id=5880]
    0x2b31c400 JavaThread "DefaultQuartzScheduler_Worker-9" [_thread_blocked, id=5876]
    0x2bbff400 JavaThread "DefaultQuartzScheduler_Worker-8" [_thread_blocked, id=5872]
    0x2bbdd400 JavaThread "DefaultQuartzScheduler_Worker-7" [_thread_blocked, id=5844]
    0x2ba80400 JavaThread "DefaultQuartzScheduler_Worker-6" [_thread_blocked, id=5864]
    0x2bbf6c00 JavaThread "DefaultQuartzScheduler_Worker-5" [_thread_blocked, id=5856]
    0x2b55dc00 JavaThread "DefaultQuartzScheduler_Worker-4" [_thread_blocked, id=5840]
    0x2bc9f800 JavaThread "DefaultQuartzScheduler_Worker-3" [_thread_blocked, id=5868]
    0x2b314800 JavaThread "DefaultQuartzScheduler_Worker-2" [_thread_blocked, id=3792]
    0x2b80f400 JavaThread "DefaultQuartzScheduler_Worker-1" [_thread_blocked, id=1472]
    0x2baa5400 JavaThread "DefaultQuartzScheduler_Worker-0" [_thread_blocked, id=5836]
    0x2b84b800 JavaThread "Timer-12" [_thread_blocked, id=596]
    0x2b853400 JavaThread "Timer-11" [_thread_blocked, id=2820]
    0x2b71e000 JavaThread "SystemThreadGroup-6" [_thread_in_native, id=5616]
    0x2b7a9400 JavaThread "SystemThreadGroup-5" [_thread_in_native, id=4148]
    0x2b29b000 JavaThread "Timer-10" [_thread_blocked, id=5356]
    0x2b29a400 JavaThread "SystemThreadGroup-4" [_thread_blocked, id=5512]
    0x2b100400 JavaThread "Timer-9" [_thread_blocked, id=4188]
    0x2b103c00 JavaThread "Timer-8" [_thread_blocked, id=816]
    0x2b15e400 JavaThread "Timer-7" [_thread_blocked, id=400]
    0x2b016400 JavaThread "Timer-6" [_thread_blocked, id=4392]
    0x2b085000 JavaThread "Timer-5" [_thread_blocked, id=5328]
    0x2b21a400 JavaThread "Timer-4" [_thread_blocked, id=5244]
    0x2b02c400 JavaThread "Timer-3" [_thread_blocked, id=5236]
    0x2b3cb000 JavaThread "Timer-1" daemon [_thread_blocked, id=4836]
    0x2b294000 JavaThread "WorkExecutorWorkerThread-1" daemon [_thread_blocked, id=5072]
    0x2b358800 JavaThread "Thread-9" daemon [_thread_blocked, id=4828]
    0x2b1ef800 JavaThread "Timer-0" [_thread_blocked, id=4708]
    0x2b38f400 JavaThread "AWT-Windows" daemon [_thread_in_native, id=3272]
    0x2b16cc00 JavaThread "Java2D Disposer" daemon [_thread_blocked, id=3268]
    0x2b19e800 JavaThread "RMIServer [0.0.0.0:23943] count:1" [_thread_in_native, id=360]
    0x2b19e400 JavaThread "RMIServer [0.0.0.0:23791] count:1" [_thread_in_native, id=896]
    0x2b08a400 JavaThread "JMSServer[deniskin:9127]" [_thread_in_native, id=4700]
    0x2b33b400 JavaThread "WsMgmtWorkScheduler" daemon [_thread_blocked, id=4452]
    0x2b133000 JavaThread "WsMgmtWorkScheduler" daemon [_thread_blocked, id=4408]
    0x2b2e4000 JavaThread "Timer ServiceThread" [_thread_blocked, id=4580]
    0x2b2d2000 JavaThread "Scheduler ServiceThread" [_thread_blocked, id=828]
    0x2b2f7800 JavaThread "Event ServiceThread" [_thread_blocked, id=5276]
    0x2b3bcc00 JavaThread "LogFlusher" daemon [_thread_blocked, id=2544]
    0x2b6f9800 JavaThread "LogFlusher" daemon [_thread_blocked, id=4108]
    0x2b700400 JavaThread "LogFlusher" daemon [_thread_blocked, id=3076]
    0x2ad0d000 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=2560]
    0x2ad09400 JavaThread "CompilerThread0" daemon [_thread_blocked, id=5448]
    0x2ad07400 JavaThread "Attach Listener" daemon [_thread_blocked, id=3532]
    0x2ad06400 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=3364]
    0x2acf7000 JavaThread "Finalizer" daemon [_thread_blocked, id=3276]
    0x2acf2c00 JavaThread "Reference Handler" daemon [_thread_blocked, id=5576]
    Other Threads:
    0x2acef800 VMThread [id=580]
    0x2ad0fc00 WatcherThread [id=3924]
    VM state:not at safepoint (normal execution)
    VM Mutex/Monitor currently owned by a thread: None
    Heap
    def new generation total 1856K, used 758K [0x029f0000, 0x02bf0000, 0x05150000)
    eden space 1664K, 35% used [0x029f0000, 0x02a834e8, 0x02b90000)
    from space 192K, 88% used [0x02b90000, 0x02bba6f0, 0x02bc0000)
    to space 192K, 0% used [0x02bc0000, 0x02bc0000, 0x02bf0000)
    tenured generation total 22392K, used 20043K [0x05150000, 0x0672e000, 0x229f0000)
    the space 22392K, 89% used [0x05150000, 0x064e2d90, 0x064e2e00, 0x0672e000)
    compacting perm gen total 44288K, used 44130K [0x229f0000, 0x25530000, 0x2a9f0000)
    the space 44288K, 99% used [0x229f0000, 0x25508880, 0x25508a00, 0x25530000)
    No shared spaces configured.
    Dynamic libraries:
    0x00400000 - 0x00423000      C:\Sun\SDK\jdk\bin\java.exe
    0x7c900000 - 0x7c9b1000      C:\WINDOWS\system32\ntdll.dll
    0x7c800000 - 0x7c8f7000      C:\WINDOWS\system32\kernel32.dll
    0x77dc0000 - 0x77e6c000      C:\WINDOWS\system32\ADVAPI32.dll
    0x77e70000 - 0x77f02000      C:\WINDOWS\system32\RPCRT4.dll
    0x77fe0000 - 0x77ff1000      C:\WINDOWS\system32\Secur32.dll
    0x7c340000 - 0x7c396000      C:\Sun\SDK\jdk\jre\bin\msvcr71.dll
    0x6d870000 - 0x6dab7000      C:\Sun\SDK\jdk\jre\bin\client\jvm.dll
    0x7e360000 - 0x7e3f0000      C:\WINDOWS\system32\USER32.dll
    0x77f10000 - 0x77f57000      C:\WINDOWS\system32\GDI32.dll
    0x76b20000 - 0x76b4e000      C:\WINDOWS\system32\WINMM.dll
    0x76360000 - 0x7637d000      C:\WINDOWS\system32\IMM32.DLL
    0x6d3c0000 - 0x6d3c8000      C:\Sun\SDK\jdk\jre\bin\hpi.dll
    0x76be0000 - 0x76beb000      C:\WINDOWS\system32\PSAPI.DLL
    0x6d820000 - 0x6d82c000      C:\Sun\SDK\jdk\jre\bin\verify.dll
    0x6d460000 - 0x6d47f000      C:\Sun\SDK\jdk\jre\bin\java.dll
    0x6d860000 - 0x6d86f000      C:\Sun\SDK\jdk\jre\bin\zip.dll
    0x6d620000 - 0x6d633000      C:\Sun\SDK\jdk\jre\bin\net.dll
    0x71a90000 - 0x71aa7000      C:\WINDOWS\system32\WS2_32.dll
    0x77c00000 - 0x77c58000      C:\WINDOWS\system32\msvcrt.dll
    0x71a80000 - 0x71a88000      C:\WINDOWS\system32\WS2HELP.dll
    0x71a30000 - 0x71a70000      C:\WINDOWS\System32\mswsock.dll
    0x76f10000 - 0x76f37000      C:\WINDOWS\system32\DNSAPI.dll
    0x76fa0000 - 0x76fa8000      C:\WINDOWS\System32\winrnr.dll
    0x76f50000 - 0x76f7d000      C:\WINDOWS\system32\WLDAP32.dll
    0x76fb0000 - 0x76fb6000      C:\WINDOWS\system32\rasadhlp.dll
    0x2c050000 - 0x2c078000      C:\WINDOWS\system32\rsaenh.dll
    0x769a0000 - 0x76a54000      C:\WINDOWS\system32\USERENV.dll
    0x5bd50000 - 0x5bda4000      C:\WINDOWS\system32\netapi32.dll
    0x6d640000 - 0x6d649000      C:\Sun\SDK\jdk\jre\bin\nio.dll
    0x698b0000 - 0x69908000      C:\WINDOWS\system32\hnetcfg.dll
    0x71a70000 - 0x71a78000      C:\WINDOWS\System32\wshtcpip.dll
    0x6d800000 - 0x6d808000      C:\Sun\SDK\jdk\jre\bin\sunmscapi.dll
    0x77a70000 - 0x77b05000      C:\WINDOWS\system32\CRYPT32.dll
    0x77b10000 - 0x77b22000      C:\WINDOWS\system32\MSASN1.dll
    0x6d0b0000 - 0x6d273000      C:\Sun\SDK\jdk\jre\bin\awt.dll
    0x72fc0000 - 0x72fe6000      C:\WINDOWS\system32\WINSPOOL.DRV
    0x774d0000 - 0x7760d000      C:\WINDOWS\system32\ole32.dll
    0x5b260000 - 0x5b298000      C:\WINDOWS\system32\uxtheme.dll
    0x73720000 - 0x73769000      C:\WINDOWS\system32\ddraw.dll
    0x73b80000 - 0x73b86000      C:\WINDOWS\system32\DCIMAN32.dll
    0x6d360000 - 0x6d3b3000      C:\Sun\SDK\jdk\jre\bin\fontmanager.dll
    0x746e0000 - 0x7472b000      C:\WINDOWS\system32\MSCTF.dll
    0x75310000 - 0x7533e000      C:\WINDOWS\system32\msctfime.ime
    0x2c880000 - 0x2c89b000      C:\OracleBI\server\Bin\perfjni.dll
    0x2c8c0000 - 0x2c8da000      C:\OracleBI\web\bin\perfcoll_OracleBIPresentationServer.dll
    0x2c9a0000 - 0x2c9ba000      C:\OracleBI\server\Bin\perfcoll_OracleBIServer.dll
    VM Arguments:
    jvm_args: -Djava.library.path=C:\OracleBI\server\Bin;C:\OracleBI\web\bin -DSAROOTDIR=C:\OracleBI -DSADATADIR=C:\OracleBIData -XX:MaxPermSize=128m -Xmx512m
    java_command: C:\OracleBI\oc4j_bi\j2ee\home\oc4j.jar -config C:\OracleBI\oc4j_bi\j2ee\home\config\server.xml -userThreads
    Launcher Type: SUN_STANDARD
    Environment Variables:
    JAVA_HOME=C:\Sun\SDK\jdk
    CLASSPATH=.;C:\Program Files\QuickTime\QTSystem\QTJava.zip
    PATH=C:\oracle\product\11.1.0\client_1\bin;C:\Hyperion\AnalyticServices\bin;C:\OracleBI\server\Bin;C:\OracleBI\web\bin;C:\OracleBI\web\catalogmanager;C:\OracleBI\SQLAnywhere;C:\Sun\SDK\jdk\bin;C:\Oracle\Publisher\jre\1.4.2\bin\client;C:\Oracle\Publisher\jre\1.4.2\bin;C:\oracle\product\10.2.0\client_1\bin;C:\oracle\product\10.2.0\client_2\bin;C:\oracle\product\10.2.0\client_1;C:\Hyperion\AnalyticServices\bin;C:\ORACLE\DEVELOPER6i\bin;C:\OracleBI\web\bin;C:\OracleBI\web\catalogmanager;C:\OracleBI\SQLAnywhere;C:\Program Files\Sun\SDK\jdk\bin;C:\OracleBI\server\Bin;C:\Program Files\PC Connectivity Solution\;C:\ORACLE\CLIENT_920\bin;C:\ORACLE\CLIENT_817\bin;C:\Program Files\Oracle\jre\1.1.7\bin;C:\ORACLE\CLIENT_8\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\ORACLE\DEVELOPER6i\jdk\bin;C:\Program Files\QuickTime\QTSystem\;C:\Hyperion\common\ODBC\Merant\5.2\Drivers;C:\Sun\SDK\bin
    USERNAME=deniska
    OS=Windows_NT
    PROCESSOR_IDENTIFIER=x86 Family 6 Model 15 Stepping 6, GenuineIntel
    --------------- S Y S T E M ---------------
    OS: Windows XP Build 2600 Service Pack 2
    CPU:total 2 family 6, cmov, cx8, fxsr, mmx, sse, sse2
    Memory: 4k page, physical 2096300k(1053216k free), swap 4037920k(2731020k free)
    vm_info: Java HotSpot(TM) Client VM (1.6.0-b105) for windows-x86, built on Nov 29 2006 00:48:48 by "java_re" with unknown MS VC++:1310

  • Passing XML payload from Servlet to JMS

    Hi All,
    My requirement is that servlet will receive the HTTP request , convert it into XML format and publish it to JMS queue.
    Now, I am stuck at the part where I need to publish the XML payload to JMS queue.
    Is it possible to send the XML payload from servlet to JMS queue? Is yes, please let me know how can we achieve this.
    Thanks

    I suggest you go to the following page: [http://edocs.bea.com/wls/docs103/pdf.html] .
    In the "Programming" section, download and read at least "Programming WebLogic JMS" and perhaps "Developing Web Applications, Servlets, and JSPs for WebLogic Server" and "Developing Applications with WebLogic Server".

  • Configuring MDB to receive message from MQSeries Queues bound on WL JNDI

    Hi,
    I am using weblogic7.0 sp2. I need to configure my MDB to receive message from MQ Series (on a different server). The queue is bound to WL JNDI using a server startup program.
    Anyone with experiece, please help.
    Thanks,
    Fasih

    I'd start here:
    http://e-docs.bea.com/wls/docs70/faq/index.html
    -- Rob
    WLS Blog http://dev2dev.bea.com/blog/rwoollen/

  • Can a Web Service be Consumed from within JSX

    Hi all,
    In CS5, can a web service be consumed from within JSX, and if so - how?
    TIA,
    mlavie

    Kris,
    Thanks! Exactly what I needed!
    mlavie

Maybe you are looking for