MDB queue clean-up?

Hi there,
Is there a way to clean up the queue for an MDB? I have a MDB that updates the state of my entity bean and the bean in turn sends out a message. For some reason it works fine the first time the appp is deployed, but when repeated, then the MDB is called three times. I am not sure what is going on. Can any one help?
Thanks in advance
-r
Here is my MDB

google on "poison messages"

Similar Messages

  • MDB QUeue example

    I looking for a example of a queue in OC4J. AT least I need the configuration for defining the QueueConnectionFactory (there's no example as a queue)

    Here's an example of a jms.xml file we use which works with queues. One of them is persistent while the other one is not.
    Apart from this file (jms.xml) the rest of the stuff is very similar to the topic example given by Oracle.
    A few points to note. Generally just change Topic for Queue in the sample code + don't forget the start the queue with the start() method.
    Hope this helps
    <?xml version="1.0"?>
    <!DOCTYPE jms-server PUBLIC "Orion JMS server" "http://xmlns.oracle.com/ias/dtds/jms-server.dtd">
    <jms-server port="9127" host="127.0.0.1">
         <!--Queue bindings, these queues will be bound to their respective JNDI path for later retrieval -->
         <queue-connection-factory location="jms/appointmentQCF" password="admin" port="9127" username="admin">
         </queue-connection-factory>
         <queue-connection-factory location="jms/objectMessageQCF" password="admin" port="9127" username="admin">
         </queue-connection-factory>      
         <queue-connection-factory location="jms/d0012QCF" password="admin" port="9127" username="admin">
         </queue-connection-factory>
         <!-- path to the log-file where JMS-events/errors are stored-->
         <!-- log>
              <file path="../log/jms.log" />
         </log -->
         <queue name="Appointment Queue" location="jms/appointmentQ" persistence-file="../persistence/MDB/appointment.queue" >
              <description>Appointment Queue</description>
         </queue>
         <queue name="Object Message Queue" location="jms/objectMessageQ" >
              <description>Object Message Queue</description>
         </queue>     
         <queue name="D0012 Queue" location="jms/d0012Q" persistence-file="../persistence/MDB/d012.queue" >
              <description>D012 queue</description>
         </queue>
    </jms-server>

  • MDB on MQSeries queue undeployment

    I just started testing MDBs listening on MQSeries queues. WLS 6.1 and MQ 5.1. I followed
    the instructions in the BEA foreign JMS providers white paper, deployed the MDBs,
    queued messages and things seemed to work. But shutting down the server revealed
    that the undeployment of each MDB was slow. Slower than SSBs or MDBs listening on
    BEA queues. Would appreciate any suggestions about what it could be. Thanks.

    I just started testing MDBs listening on MQSeries queues. WLS 6.1 and MQ 5.1. I followed
    the instructions in the BEA foreign JMS providers white paper, deployed the MDBs,
    queued messages and things seemed to work. But shutting down the server revealed
    that the undeployment of each MDB was slow. Slower than SSBs or MDBs listening on
    BEA queues. Would appreciate any suggestions about what it could be. Thanks.

  • R2_AQ_JMS MDB deployment Error--Urgent, please help!!

    Deploy a simple MDB to Oracle9iASR2, follow the steps:
    1. Define the MDB in ejb-jar.xml
    <message-driven>
    <description>MDB Queue Listener</description>
    <display-name>QueueListener Message Driven Bean</display-name>
    <ejb-name>QueueListenerMDB</ejb-name>
    <ejb-class>mdb.QueueListenerMDB</ejb-class>
    <transaction-type>Container</transaction-type>
    <message-driven-destination>
    <jms-destination-type>javax.jms.Topic</jms-destination-type>
    </message-driven-destination>
    </message-driven>
    2. Modify the orion-ejb-jar.xml
    <message-driven-deployment
    name="QueueListenerMDB"
    destination-location="jms/SalesTopic"
    connection-factory-location="jms/theTopicConnectionFactory"
    subscription-name="MDBSUB"
    >
    </message-driven-deployment>
    3. define the resource-provider in application.xml
    <resource-provider class="oracle.jms.OjmsContext" name="SalesJMS">
    <description> OJMS/AQ </description>
    <property name="url" value="jdbc:oracle:thin:@dell2400:1521:mydb"></property>
    <property name="username" value="user"></property>
    <property name="password" value="pssword"></property>
    </resource-provider>
    4. Deploy the ear file and got the following error:
    java.lang.NullPointerException
    at com.evermind.server.ejb.MessageDrivenHome.<init>(MessageDrivenHome.java:280)
    at com.evermind.server.ejb.EJBPackageDeployment.bindHomes(EJBPackageDeployment.java:239
    at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:589)
    at com.evermind.server.Application.postInit(Application.java:420)
    at com.evermind.server.administration.ServerApplicationInstallation.finish(ServerApplic
    ationInstallation.java:491)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:80)
    at com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java:64)
    Any idea on what's the cause of this. It seems that the Oracle 9i's support of MDB differs significantly from R1. The demo sample that works for R1 no longer work for R2. For example, the following DD doesn't seem to work with R2.
    <resource-ref>
    <res-ref-name>jms/Queue/senderQueueConnectionFactory</res-ref-name>
    <res-type>javax.jms.QueueConnectionFactory</res-type>
    <res-auth>Container</res-auth>
    <res-sharing-scope>Shareable</res-sharing-scope>
    </resource-ref>
    <resource-env-ref>
    <resource-env-ref-name>jms/Queue/senderQueue</resource-env-ref-name>
    <resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
    </resource-env-ref>
    <resource-ref>
    <res-ref-name>jms/Topic/senderTopicConnectionFactory</res-ref-name>
    <res-type>javax.jms.TopicConnectionFactory</res-type>
    <res-auth>Container</res-auth>
    <res-sharing-scope>Shareable</res-sharing-scope>
    </resource-ref>
    Please help!! This is very urgent! Thanks in advance!

    <jms-destination_type> tag should be <destination-type> its a oracle error

  • OC4J : configuring queues programmatically than in jms.xml file.

    Hi All,
    I'm using MDB-Queues and OC4J Scheduler in my application deployed in OC4J 10.1.3.1. I need to get rid of the dependency of "jms.xml" (under "<OC4J>\j2ee\home\config") where the queues are defined for the OC4J Scheduler. This is because, I cant always expect my client to add these entries into their app server setting. Can anyone please let me how this can be achieved..?
    Thanks
    Rajasekaran Iyanu

    hi,
    You can enter jms information in jms-server.xml which can be deploy with application and you dont need to configure AS .
    Regards

  • Unable to check for available downloads...  Try again later.

    "Unable to check for available downloads.  The iTunes Store is temporarily available.  Please try again later."   Forever, really.
    It all started when I attempted to "Download All Updates" (104 of them) and it crashed.  Now it tells me that I've already purchased the items, and to "Check for Available Downloads", which throws the above error for going on three days now.  Email support has not answered my inquiry / report.
    In the meantime, the "Genius Folks" in the Apple Store inspired me to a partial workaround, at least to whittle down the queue.  By installing the apps to my device, updating them there, and syncing them back to iTunes.  But I still have a few stuck in some weird state, that iTunes is unprepared to process.
    BTW, the geniuses never heard of this problem, even after I showed them that a quick Google search came right back with 404,000 hits.   I've seen iTunes unable to connect to the Store when there were too many updates, for years, on both Windows and OSX, and many released versions, but I've always been able to download them individually, instead of in bulk.  First time it crashed and left me hosed.
    Seems like a server-side issue.  Any suggestions on how to get through to the powers that be, and have my queue cleaned up?  And maybe get the attention of the Q/A and development departments to actually acknowledge and fix a long standing and most inconvenient bug?

    Thank you so much - I have spent the last 4 days scouring internet forums trying to solve this problem (I couldn't connect to the iTunes store/download any apps or updates) and just as I was about to give up I stumbled across your post. I can't believe I've had such big problems all because of the ampersand in my billing address! How did you discover this?! It's such a small detail! To my huge relief it's all sorted now and I can now update my apps and download again! I'll be cancelling my appointment at the genius bar tomorrow too! Thanks again very much!

  • MAM sync problems

    Hello,
    In my company we're using MAM3.0 and NetWeaver 70 this is connected to a ECC 6.0 backend.
    Everything was going fine till today, where because of a password expiration the RFC connection between backend and our middleware, could not succeed. Many RFC's failed and after the authorization problem was fixed, all were run again. Problem now is that many MI clients that synchronized meanwhile, can no longer synchronize properly. Just after reinstalling the application, we were able to fix the sync issue. The procedure of reinstalling is not nice since there are many users involved.
    Any idea of what could be done so that each PDA does not require a reinstallation?
    Best regards,
    Daniel Garrido

    Hello Oliver,
    Thanks for your answer.
    We have case where many users have a I-Waiting queue and others have the I-Waiting queue clean, but many O-Waiting. But when they sync the O-Waiting queue is not cleaned.
    We've tried to reinitialize the device, unfortunately that was not enough.
    We had to do a procedure similar to the one described in http://help.sap.com/saphelp_nw70/helpdata/EN/4c/7862a6642eab40ac7abf34e9048c93/frameset.htm in order to adjust the outbound queue. Unfortunately there are many users involved and this procedure requires losing something like 1 hour with each in order to do the required renitializations.
    Any more ideas?
    Best regards,
    Daniel Garrido

  • R2_AQ_JMS deployment Error--Urgent, please help!!

    Deploy a simple MDB to Oracle9iASR2, follow the steps:
    1. Define the MDB in ejb-jar.xml
         <message-driven>
              <description>MDB Queue Listener</description>
              <display-name>QueueListener Message Driven Bean</display-name>
              <ejb-name>QueueListenerMDB</ejb-name>
              <ejb-class>mdb.QueueListenerMDB</ejb-class>
              <transaction-type>Container</transaction-type>
         <message-driven-destination>
         <jms-destination-type>javax.jms.Topic</jms-destination-type>     
         </message-driven-destination>          
         </message-driven>     
    2. Modify the orion-ejb-jar.xml
    <message-driven-deployment
    name="QueueListenerMDB"
    destination-location="jms/SalesTopic"
    connection-factory-location="jms/theTopicConnectionFactory"
    subscription-name="MDBSUB"
    >
    </message-driven-deployment>
    3. define the resource-provider in application.xml
    <resource-provider class="oracle.jms.OjmsContext" name="SalesJMS">
    <description> OJMS/AQ </description>
         <property name="url" value="jdbc:oracle:thin:@dell2400:1521:mydb"></property>
         <property name="username" value="user"></property>
         <property name="password" value="pssword"></property>
    </resource-provider>
    4. Deploy the ear file and got the following error:
    java.lang.NullPointerException
    at com.evermind.server.ejb.MessageDrivenHome.<init>(MessageDrivenHome.java:280)
    at com.evermind.server.ejb.EJBPackageDeployment.bindHomes(EJBPackageDeployment.java:239
    at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:589)
    at com.evermind.server.Application.postInit(Application.java:420)
    at com.evermind.server.administration.ServerApplicationInstallation.finish(ServerApplic
    ationInstallation.java:491)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:80)
    at com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java:64)
    Any idea on what's the cause of this. It seems that the Oracle 9i's support of MDB differs significantly from R1. The demo sample that works for R1 no longer work for R2. For example, the following DD doesn't seem to work with R2.
    <resource-ref>
    <res-ref-name>jms/Queue/senderQueueConnectionFactory</res-ref-name>
    <res-type>javax.jms.QueueConnectionFactory</res-type>
    <res-auth>Container</res-auth>
    <res-sharing-scope>Shareable</res-sharing-scope>
    </resource-ref>
    <resource-env-ref>
    <resource-env-ref-name>jms/Queue/senderQueue</resource-env-ref-name>
    <resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
    </resource-env-ref>
    <resource-ref>
    <res-ref-name>jms/Topic/senderTopicConnectionFactory</res-ref-name>
    <res-type>javax.jms.TopicConnectionFactory</res-type>
    <res-auth>Container</res-auth>
    <res-sharing-scope>Shareable</res-sharing-scope>
    </resource-ref>
    Please help!! This is very urgent! Thanks in advance!

    Chunming -- There was a change from v1022x to v902. This was required per the changes in the EJB specification as it was finalized. The tag <jms-destination-type> was changed to <destination-type>. If you make this change in your ejb-jar.xml that should work.
    Thanks -- Jeff

  • After starting up the listener the server consuming 100% CPU

    Hi,
    when i startup the database tier (EBS 12.1.3 and DB 11.2.0.2) its stared well and the CPU usage is normal.But when i start the listener the server (RHEL 5.8) start consuming 100% CPU.
    alert.log details
    in file /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/trace/UAT_j000_7601.trc:
    ORA-00600: internal error code, arguments: [13011], [262414], [1644193998], [33], [1644194002], [0], [], [], [], [], [], []
    ORA-06512: at "APPS.WF_BES_CLEANUP", line 488
    ORA-06512: at line 1
    Wed Dec 12 10:11:33 2012
    Sweep [inc][480592]: completed
    Wed Dec 12 10:13:17 2012
    Errors in file /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/trace/UAT_j001_7624.trc (incident=480612):
    ORA-00600: internal error code, arguments: [13011], [262414], [1644193998], [33], [1644194002], [0], [], [], [], [], [], []
    Use ADRCI or Support Workbench to package the incident.
    See Note 411.1 at My Oracle Support for error and packaging details.
    Errors in file /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/trace/UAT_j001_7624.trc:
    ORA-00600: internal error code, arguments: [13011], [262414], [1644193998], [33], [1644194002], [0], [], [], [], [], [], []
    ORA-06512: at "APPS.WF_BES_CLEANUP", line 488
    ORA-06512: at line 1
    Wed Dec 12 10:13:18 2012
    Sweep [inc][480612]: completed
    Wed Dec 12 10:14:18 2012
    Errors in file /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/trace/UAT_ora_7814.trc (incident=481092):
    ORA-00600: internal error code, arguments: [kdsgrp1], [], [], [], [], [], [], [], [], [], [], []
    Incident details in: /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/incident/incdir_481092/UAT_ora_7814_i481092.trc
    Wed Dec 12 10:14:23 2012
    Dumping diagnostic data in directory=[cdmp_20121212101423], requested by (instance=1, osid=7814), summary=[incident=481092].
    Use ADRCI or Support Workbench to package the incident.
    See Note 411.1 at My Oracle Support for error and packaging details.
    Wed Dec 12 10:14:24 2012
    Sweep [inc][481092]: completed
    Sweep [inc2][481092]: completed
    Wed Dec 12 10:16:50 2012
    Errors in file /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/trace/UAT_j001_8058.trc (incident=481492):
    ORA-00600: internal error code, arguments: [13011], [262414], [1644193998], [33], [1644194002], [0], [], [], [], [], [], []
    Use ADRCI or Support Workbench to package the incident.
    See Note 411.1 at My Oracle Support for error and packaging details.
    Errors in file /ebs/UAT/bin/db/tech_st/11.2.0/admin/UAT_dcvlodbdev/diag/rdbms/uat/UAT/trace/UAT_j001_8058.trc:
    ORA-00600: internal error code, arguments: [13011], [262414], [1644193998], [33], [1644194002], [0], [], [], [], [], [], []
    ORA-06512: at "APPS.WF_BES_CLEANUP", line 488
    ORA-06512: at line 1
    Wed Dec 12 10:19:04 2012
    Incremental checkpoint up to RBA [0xf.ac257.0], current log tail at RBA [0xf.c3691.0]
    Wed Dec 12 10:20:56 2012
    Active Session History (ASH) performed an emergency flush. This may mean that ASH is undersized. If emergency flushes are a recurring issue, you may consider increasing ASH size by setting the value of ASHSIZE to a sufficiently large value. Currently, ASH size is 2097152 bytes. Both ASH size and the total number of emergency flushes since instance startup can be monitored by running the following query:
    select total_size,awr_flush_emergency_count from v$ash_info;
    Wed Dec 12 10:21:26 2012
    Sweep [inc][481492]: completed

    Please see these docs.
    ORA-600/ORA-7445/ORA-700 Error Look-up Tool [ID 153788.1]
    ORA-600 [13011] "Problem occurred when trying to delete a row" [ID 28184.1]
    Workflow Control Queue Clean Up Program Fails With ORA-25226 [ID 334237.1]
    Thanks,
    Hussein

  • Error deserializing object

    Hi all,
    I am posting a serializable object as message to MDB Queue and trying to deserialize it in onMessage() method. But, getting below error
    "Exception in onMessage weblogic.jms.common.JMSException: Error deserializing object"
    Here is my onMessage method. Please help me !!!
    public void onMessage(Message msg) {
         ProcessQuery prQuery = null;          
         try {
              ObjectMessage message = (ObjectMessage) msg;
              ProcessQuery pQ = (ProcessQuery) message.getObject();
              prQuery = pQ.execute();
         catch(JMSException ex) {
              System.out.println("Exception in onMessage " + ex);
              ex.printStackTrace();
    ProcessQuery is a serializable object.
    Thanks in advance,
    Anitha

    Hi all,
    I am posting a serializable object as message to MDB Queue and trying to deserialize it in onMessage() method. But, getting below error
    "Exception in onMessage weblogic.jms.common.JMSException: Error deserializing object"
    Here is my onMessage method. Please help me !!!
    public void onMessage(Message msg) {
         ProcessQuery prQuery = null;          
         try {
              ObjectMessage message = (ObjectMessage) msg;
              ProcessQuery pQ = (ProcessQuery) message.getObject();
              prQuery = pQ.execute();
         catch(JMSException ex) {
              System.out.println("Exception in onMessage " + ex);
              ex.printStackTrace();
    ProcessQuery is a serializable object.
    Thanks in advance,
    Anitha

  • Immediate JRockit Dump WebLogic 8.1

     

    I would suggest you grab the 8.1sp3 version of JRockit available at:
    http://commerce.bea.com/showproduct.jsp?family=WLJR&major=JR142SDK&minor=0
    Regards,
    /Staffan
    sree bodapati wrote:
    you should post this to jrockit.developer.interest.general.
    I am cc'ing that group here for you.
    "Jeremy Whitlock" <[email protected]> wrote in message
    news:40e329a0$1@mktnews1...
    I am trying to launch WebLogic 8.1 inside of Eclipse via the WebLogicplugin.
    With WebLogic 7.0 and JRockit 7.0 SP4, it worked like a charm but now I amusing
    WebLogic 8.l and JRockit 8.1 SP2 and I get an immediate JRockit Dump whenstarted
    WebLogic inside of Eclipse. Here is the dump:
    <Jun 30, 2004 2:01:19 PM MDT> <Info> <WebLogicServer> <BEA-000377><Starting WebLogic
    Server with BEA WebLogic JRockit(R) Virtual Machine Version8.1sp2-1.4.1_05-Load10-viking-win32-sthqa29-20031105-1554
    from BEA Systems, Inc.>
    <Jun 30, 2004 2:01:21 PM MDT> <Info> <Configuration Management><BEA-150016> <This
    server is being started as the administration server.>
    <Jun 30, 2004 2:01:21 PM MDT> <Info> <Management> <BEA-141107> <Version:WebLogic
    XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284 >
    <Jun 30, 2004 2:01:22 PM MDT> <Notice> <Management> <BEA-140005> <Loadingdomain
    configuration from configuration repository atC:\bea\firms\wlsutestdev411\.\config.xml.>
    <Jun 30, 2004 2:01:29 PM MDT> <Notice> <Log Management> <BEA-170019> <Theserver
    log file C:\bea\firms\wlsutestdev411\logs\UTEST\UTEST.log is opened. Allserver
    side log events will be written to this file.>
    <Jun 30, 2004 2:01:34 PM MDT> <Notice> <Security> <BEA-090082> <Securityinitializing
    using security realm CompatibilityRealm.>
    <Jun 30, 2004 2:01:35 PM MDT> <Notice> <WebLogicServer> <BEA-000327><Starting
    WebLogic Admin Server "UTEST" for domain "wlsutestdev411">
    ********* POSSE LogListener Starting *********
    The Bulk Reporting Queue Cleaner has started
    Cleanup Interval: 3600000
    Time To Live: 604800000
    ********* Initializing PosseErrors *********
    ===== BEGIN DUMP=============================================================
    JRockit context dump produced on Wed Jun 30 14:02:08 2004
    If you see this dump, please send it, along with as much
    information as you can on your system setup and the program
    you were running, to [email protected]. Please include the
    file jrockit.3048.dump and jrockit.3048.mdmp from the current
    directory in the bug report. Thank you.
    Version : 8.1sp2-1.4.1_05-Load10-viking-win32-sthqa29-20031105-1554
    Threads / GC : Native Threads, Generational Copying Garbage Collector
    Number CPUs : 1
    Tot Phys Mem : 535838720
    OS version : Microsoft Windows 2000 Service Pack 2 (Build 2195)
    State : JVM is running
    Command Line: -Djava.class.path=. -Xms64m -Xmx128m -Dweblogic.Domain=wlsutestdev411
    -Dweblogic.ProductionModeEnabled=false -Dweblogic.Name=UTEST -Dbea.home=C:\bea
    -Djava.security.policy=C:\bea\firms\wlsutestdev411\weblogic.policy -Dweblogic.management.password=password
    -Dweblogic.management.username=system -Dschemas=true -Dposse.firm=UTEST -Dweblogic.Name=UTEST
    -Dbea.home=C:\bea -Dweblogic.management.username=system -Dweblogic.management.password=password
    -Djava.class.path=C:\bea\weblogic81\server\bin;C:\bea\weblogic81\server\lib;C:\bea\weblogic81\server\lib\xmlx.jar;C:\bea\weblogic81\server\lib\joltwls
    .jar;C:\bea\weblogic81\server\lib\joltjse.jar;C:\bea\weblogic81\server\lib\j
    olt.jar;C:\bea\weblogic81\server\lib\weblogic.jar;C:\bea\jrockit81sp2_141_05
    \lib\tools.jar;C:\bea\weblogic81\server\lib\weblogic_sp.jar;C:\bea\weblogic8
    1\server\lib\weblogic.jar;C:\bea\weblogic81\server\bin;C:\bea\weblogic81\ser
    ver\lib;C:\bea\firms\wlsutestdev411;C:\bea\posse_4_11_1\classes\pubsub_clien
    t_4_11_1.jar;C:\bea\posse_4_11_1\classes\startup_4_11_1.jar;C:\bea\posse_4_1
    1_1\classes\castor-0.9.5.3.jar;C:\bea\posse_4_11_1\classes\castor-0.9.5.3-xm
    l.jar;C:\bea\posse_4_11_1\classes\xerces.jar;C:\bea\weblogic700\classes\adap
    terSupport_4_8_1.jar;C:\bea\posse_4_11_1\javachart\adpsis-kavachart.jar;C:\b
    ea\posse_4_11_1\fop\lib\avalon-framework-cvs-20020806.jar;C:\bea\posse_4_11_
    1\fop\lib\batik.jar;C:\bea\posse_4_11_1\fop\lib\xalan-2.4.1.jar;C:\bea\posse
    _4_11_1\fop\lib\xercesImpl-2.2.1.jar;C:\bea\posse_4_11_1\fop\fop.jar
    -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,suspend=y,address=localhost:1848
    -Dsun.java.command=weblogic.Server
    Environment : JAVA_HOME=C:\j2sdk1.4.2_04,java.home=C:\bea\jrockit81sp2_141_05\jre,
    java.class.path=C:\bea\weblogic81\server\bin;C:\bea\weblogic81\server\lib;C:
    \bea\weblogic81\server\lib\xmlx.jar;C:\bea\weblogic81\server\lib\joltwls.jar
    ;C:\bea\weblogic81\server\lib\joltjse.jar;C:\bea\weblogic81\server\lib\jolt.
    jar;C:\bea\weblogic81\server\lib\weblogic.jar;C:\bea\jrockit81sp2_141_05\lib
    \tools.jar;C:\bea\weblogic81\server\lib\weblogic_sp.jar;C:\bea\weblogic81\se
    rver\lib\weblogic.jar;C:\bea\weblogic81\server\bin;C:\bea\weblogic81\server\
    lib;C:\bea\firms\wlsutestdev411;C:\bea\posse_4_11_1\classes\pubsub_client_4_
    11_1.jar;C:\bea\posse_4_11_1\classes\startup_4_11_1.jar;C:\bea\posse_4_11_1\
    classes\castor-0.9.5.3.jar;C:\bea\posse_4_11_1\classes\castor-0.9.5.3-xml.ja
    r;C:\bea\posse_4_11_1\classes\xerces.jar;C:\bea\weblogic700\classes\adapterS
    upport_4_8_1.jar;C:\bea\posse_4_11_1\javachart\adpsis-kavachart.jar;C:\bea\p
    osse_4_11_1\fop\lib\avalon-framework-cvs-20020806.jar;C:\bea\posse_4_11_1\fo
    p\lib\batik.jar;C:\bea\posse_4_11_1\fop\lib\xalan-2.4.1.jar;C:\bea\posse_4_1
    1_1\fop\lib\xercesImpl-2.2.1.jar;C:\bea\posse_4_11_1\fop\fop.jar,
    java.library.path=C:\bea\jrockit81sp2_141_05\jre\bin;C:\WINNT\System32;C:\WI
    NNT;C:\j2sdk1.4.2_04\bin;c:\bea\weblogic81\server\bin;c:\bea\weblogic700\ser
    ver\bin;C:\Sybase\ASEP_Win32;C:\Sybase\OCS-12_5\dll;C:\Sybase\OCS-12_5\lib3p
    ;C:\Sybase\OCS-12_5\bin;C:\PROGRA~1\PVCS\VM\win32\bin;C:\WINNT\SYSTEM32;C:\W
    INNT;C:\WINNT\SYSTEM32\WBEM;C:\DMI\WIN32\BIN;C:\jakarta-ant-1.5.1\bin;C:\Syb
    ase\DLL;C:\Sybase\BIN;
    Registers:
    Converted EIP: 004d506e
    EAX = 1f3d8744 EBX = 12e8b1a4
    ECX = 089ae090 EDX = 00000000
    ESI = 00000000 EDI = 1f3d8744
    EIP = 0081506e ESP = 7fe50c50
    EBP = 7fe50c88 EFL = 00010202
    CS = 001b DS = 0023 ES = 0023
    SS = 0023 FS = 0038 GS = 0000
    Stack:
    7fe50c50 :1f3d8744 00000000 12e8b1a4 00000001 009a2398 009a2380
    7fe50c68 :7fe50cc0 0081473e 009a09e0 6d27f307 6d27f766 1f3d8744
    7fe50c80 :7fe50c84 12e703a8 7fe50cc0 6d274913 1f3d8744 7fe50cd0
    7fe50c98 :7fe50e70 10a25201 08a377c4 12e703a8 12e70338 12e8b1a0
    7fe50cb0 :00001015 00000000 00001019 12e8f1f4 7fe50e70 6d276be8
    7fe50cc8 :00000001 7fe50cdc 6d183010 00000001 10a25208 7fe50d04
    7fe50ce0 :0000012c 7fe50cf8 00000000 00070000 00000476 00000080
    7fe50cf8 :00000000 7fe50d04 00000000 00000000 00000001 00000000
    7fe50d10 :0000005d 61657206 66202764 7120726f 65756575 7727203a
    7fe50d28 :6f6c6265 2e636967 6b636f73 4d2e7465 72657875 65752727
    7fe50d40 :6e616c27 65722f67 65522f66 65726566 3b65636e 0a010000
    7fe50d58 :3825bc10 15000000 72617473 66655274 6e657265 61486563
    7fe50d70 :656c646e 00000072 56292803 0a000000 b828bc10 0a000000
    7fe50d88 :65636361 30247373 00003030 29281b00 76616a4c 616c2f61
    7fe50da0 :722f676e 522f6665 72656665 65636e65 0000003b 27bc1008
    7fe50db8 :000000b8 6e693c06 003e7469 28150000 76616a4c 616c2f61
    7fe50dd0 :4f2f676e 63656a62 56293b74 00000000 3828bc10 06000000
    7fe50de8 :696e693c 00003e74 4c283300 6176616a 6e616c2f 624f2f67
    7fe50e00 :7463656a 616a4c3b 6c2f6176 2f676e61 2f666572 65666552
    7fe50e18 :636e6572 65755165 293b6575 00000056 27bc1000 00000038
    7fe50e30 :12e37078 12e701bf 00000000 00000000 00000000 00000476
    7fe50e48 :00020100 00000017 12e701a8 00000000 12e60798 00000476
    7fe50e60 :00020100 00000017 12e701a8 00000000 08a37740 6d27e0ec
    7fe50e78 :00000000 08a377c4 6d27e162 6d183010 00834af2 6d183010
    7fe50e90 :10a25208 12cdbb03 10a25208 6d27e159 6d183010 10d4a288
    7fe50ea8 :00a5d770 6d27e159 08a605c8 12cdbb5c 08a605c8 08a605c8
    7fe50ec0 :172cffa4 12cdb3c6 00000000 00000000 08a605c8 10c252a0
    7fe50ed8 :08a37740 08a37740 00000000 00000000 00000000 08a37740
    7fe50ef0 :10c25026 00000000 08a37740 00000000 00000000 00000000
    7fe50f08 :00000000 00000000 00000000 7fe50f58 0083b6cc 00000000
    7fe50f20 :172cffa4 10c20e60 7fe50f38 10c24fd0 08a37740 172cffa0
    7fe50f38 :172cffb4 0083a84f 08a37740 10c24fd0 10c10044 007ae3f3
    7fe50f50 :0084776c 08a37740 10c24fd0 08a37740 00000000 00000000
    7fe50f68 :00000000 00000000 00000000 00000000 00000000 00000000
    7fe50f80 :00000000 00000000 00000000 00000000 00000000 00000000
    7fe50f98 :00000000 00000000 00000000 00000000 00000000 00000000
    7fe50fb0 :00000000 00000000 00000000 00000000 00000000 00000000
    7fe50fc8 :00000000 00000000 00000000 00000000 00000000 00000000
    7fe50fe0 :00000000 00000000 00000000 00000000 00000000 00000000
    Code:
    00814f6e :04c483ff 04c2c033 83d0ff00 04c204c4 cccc9000 cccccccc
    00814f86 :cccccccc cccccccc 448bcccc 55530424 57088b56 1824548b
    00814f9e :5220798b 8b0c6f8b 468d0c75 50529903 f3e6e5e8 85d88bff
    00814fb6 :8b3375db 8b182444 ff83247f 7c008b01 03ff8313 00c60e74
    00814fce :04c6404c 5c883b30 04eb0130 003004c6 56004d8b 37e85051
    00814fe6 :83000000 5e5f0cc4 5b5dc38b 900008c2 90909090 90909090
    00814ffe :cccc9090 cccccccc cccccccc cccccccc cccccccc cccccccc
    00815016 :cccccccc cccccccc 4c8bcccc c9850c24 448b217e 548b0424
    0081502e :2b560824 8af18bd0 f980020c c605752e 02eb2f00 4e400888
    00815046 :c35eed75 90909090 cccc9090 cccccccc cccccccc cccccccc
    0081505e :448bcccc ec830424 56088b20 20718b57 8b0c568b 7c685002
    00815076 :e800891c ffffd242 10244c8d 00b0be8d 57510000 f3c8cce8
    0081508e :1c468bff 4010c483 7704f883 8524ff07 008150f0 0824548d
    008150a6 :4de85752 8dfff3d4 50102444 4c8bd5eb 01c73024 00000003
    008150be :548b16eb 02c73024 00000006 448b0aeb 00c73024 00000008
    008150d6 :08244c8d cfe85751 83fff3c3 c03308c4 c4835e5f 0008c220
    008150ee :50ccff8b 50b40081 50b40081 50c00081 50cc0081 90900081
    00815106 :90909090 90909090 cccc9090 cccccccc cccccccc cccccccc
    0081511e :cccccccc cccccccc cccccccc cccccccc cccccccc cccccccc
    00815136 :cccccccc cccccccc 448bcccc 088b0424 5020418b f3cc26e8
    0081514e :04c483ff 1174c085 0824548b dfe85052 83000035 08c208c4
    00815166 :0065b800 08c20000 cccc9000 cccccccc cccccccc cccccccc
    Loaded modules:
    (* denotes the module causing the exception)
    0x77f80000-0x77ffafff C:\WINNT\System32\ntdll.dll
    0x77db0000-0x77e0bfff C:\WINNT\system32\ADVAPI32.dll
    0x77e80000-0x77f34fff C:\WINNT\system32\KERNEL32.DLL
    0x77d40000-0x77dacfff C:\WINNT\system32\RPCRT4.DLL
    0x77e10000-0x77e73fff C:\WINNT\system32\USER32.dll
    0x77f40000-0x77f7bfff C:\WINNT\system32\GDI32.DLL
    0x78000000-0x78045fff C:\WINNT\system32\MSVCRT.dll
    0x00750000-0x008cffff* C:\bea\jrockit81sp2_141_05\jre\bin\jrockit\jvm.dll
    0x77570000-0x7759ffff C:\WINNT\System32\WINMM.dll
    0x75030000-0x75042fff C:\WINNT\System32\WS2_32.dll
    0x75020000-0x75027fff C:\WINNT\System32\WS2HELP.DLL
    0x6d270000-0x6d28bfff C:\bea\jrockit81sp2_141_05\jre\bin\jdwp.dll
    0x6d180000-0x6d184fff C:\bea\jrockit81sp2_141_05\jre\bin\dt_socket.dll
    0x785c0000-0x785cbfff C:\WINNT\System32\rnr20.dll
    0x77980000-0x779a3fff C:\WINNT\System32\DNSAPI.DLL
    0x75050000-0x75057fff C:\WINNT\System32\WSOCK32.DLL
    0x77340000-0x77352fff C:\WINNT\System32\iphlpapi.dll
    0x77520000-0x77524fff C:\WINNT\System32\ICMP.DLL
    0x77320000-0x77336fff C:\WINNT\System32\MPRAPI.DLL
    0x75150000-0x7515ffff C:\WINNT\System32\SAMLIB.DLL
    0x75170000-0x751befff C:\WINNT\System32\NETAPI32.DLL
    0x77be0000-0x77beefff C:\WINNT\System32\SECUR32.DLL
    0x751c0000-0x751c5fff C:\WINNT\System32\NETRAP.DLL
    0x77950000-0x77979fff C:\WINNT\system32\WLDAP32.DLL
    0x77a50000-0x77b39fff C:\WINNT\system32\OLE32.DLL
    0x779b0000-0x77a4afff C:\WINNT\system32\OLEAUT32.DLL
    0x773b0000-0x773ddfff C:\WINNT\System32\ACTIVEDS.DLL
    0x77380000-0x773a1fff C:\WINNT\System32\ADSLDPC.DLL
    0x77830000-0x7783dfff C:\WINNT\System32\RTUTILS.DLL
    0x77880000-0x7790cfff C:\WINNT\System32\SETUPAPI.DLL
    0x77c10000-0x77c6dfff C:\WINNT\System32\USERENV.DLL
    0x774e0000-0x77511fff C:\WINNT\System32\RASAPI32.DLL
    0x774c0000-0x774d0fff C:\WINNT\System32\RASMAN.DLL
    0x77530000-0x77551fff C:\WINNT\System32\TAPI32.DLL
    0x71780000-0x71809fff C:\WINNT\system32\COMCTL32.DLL
    0x70bd0000-0x70c33fff C:\WINNT\system32\SHLWAPI.DLL
    0x77360000-0x77378fff C:\WINNT\System32\DHCPCSVC.DLL
    0x775a0000-0x77624fff C:\WINNT\System32\CLBCATQ.DLL
    0x777e0000-0x777e7fff C:\WINNT\System32\winrnr.dll
    0x777f0000-0x777f4fff C:\WINNT\System32\rasadhlp.dll
    0x74fd0000-0x74feefff C:\WINNT\system32\msafd.dll
    0x75010000-0x75016fff C:\WINNT\System32\wshtcpip.dll
    0x6d200000-0x6d205fff C:\bea\jrockit81sp2_141_05\jre\bin\ioser12.dll
    0x22500000-0x22504fff C:\bea\weblogic81\server\bin\wlntio.dll
    0x24130000-0x241f0fff C:\bea\jrockit81sp2_141_05\jre\bin\dbghelp.dll
    0x77820000-0x77826fff C:\WINNT\system32\VERSION.dll
    0x759b0000-0x759b5fff C:\WINNT\system32\LZ32.DLL
    0x690a0000-0x690aafff C:\WINNT\System32\psapi.dll
    Java Thread ID = 0x00000400, Name = JDWP Transport Listener: dt_socket
    Thread Stack Trace:
    at _jvmdiGetClassStatus@8+14 ()@0081506E
    at JVMOnLoad@12+3080 ()@6D276BE8
    at JVMOnLoad@12+33036 ()@6D27E0EC
    at COM.jrockit.vm.JVMDIBootstrapper.run0(Native Method)@12CDBAE8
    at COM.jrockit.vm.JVMDIBootstrapper.run(Unknown Source)@12CDBB5C
    at java.lang.Thread.run(Unknown Source)@10C252A0
    at java.lang.Thread.startThreadFromVM(Unknown Source)@10C25026
    --- End of stack trace
    ===== END DUMP===============================================================

  • JPA: skipped updates

    Hello!
    I have an issue and I don’t understand the reasons of it.
    In my system I have a stateless session bean that every N seconds retrieves entity list from persistence context:
    @PersistenceContext 
    private EntityManager em; 
    public List<Item> getItemsToProcess() { 
            String sql = "select t " + 
                    "from Item t join ...."; 
            return em.createQuery(sql).getResultList(); 
    }Then all items are updated to “Busy” state and sent to MDB queue for processing. After all processing is done MDB updates item’s state back to “Normal”.
    businessBean.setInProcess(itemPK, true); // busy (called from session bean)
    businessBean.setInProcess(itemPK, false); // normal (called from MDB)
    public void setInProcess(ItemPK itemPK, Boolean value) {
            Item item = em.find(Item.class, itemPK);
            item.setInProcess(value); // field is mapped to DB column
            em.merge(item); 
            //em.flush(); // does not helps
    }So far everything is working, but when I increase load to system (decrease N period) then some items (randomly) are not updated back to “Normal” state. All beans are deployed as single EJB module on the same server, using same persistence context (as I think :). No special transactions are used (only default CMP).
    I have done trace over called methods and found out, that there is (!) a call of function to set “Normal” state, but somehow it does not reach database (SQL logs does not show any update). I mean I set entity field to correct value, and merge it to persistence context, but context does not forwards it to database.
    Is it possible that while MDB tries to update item’s state first select … statement is run and it somehow locks that record? That SQL returns only items with “Normal” state.
    Thanks!

    I have found temporal solution for this issue. I rewrote function for setting items state like this:
    public void setInProcess(ItemPK itemPK, Boolean value) {
            String sql = "update Item t " +
                    "set inProcess = …”;
            Query q = em.createQuery(sql);
            q.setParameter(…);
            q.executeUpdate();
    }{code}
    Now there are no skipped items, but sometimes I receive “java.sql.SQLException: Some non-transactional changed tables couldn't be rolled back”. This exception is specific for MySQL database (MyISAM), but I use InnoDB storage engine for tables, that supports transactions.
    But anyway I do not understand why em.merge() skips updates, but JPQL queries not.
    Any ideas?                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Evictor/UtilizationProfile locking - severe performance problem

    I have a database with 2.5 million entries, 10 - 20 bytes keys and 40kb values (about 200 GB overall).
    je.properties:
    je.maxMemory=419430400
    je.evictor.lruOnly=false
    je.env.isTransactional=false
    je.cleaner.threads=40
    je.evictor.nodesPerScan=100
    I know I can't fit the data in the cache, but the tree should fit. The access pattern is random.
    The situation is this:
    Every get or put is causing an eviction. To do this the PrivateEvictor must be locked:
    "NioProcessor-1" prio=3 tid=0x08d91c00 nid=0x47 waiting for monitor entry [0x70fcb000..0x70fcb970]
    java.lang.Thread.State: BLOCKED (on object monitor)
         at com.sleepycat.je.evictor.Evictor.doEvict(Evictor.java:228)
         - waiting to lock <0x7f157c68> (a com.sleepycat.je.evictor.PrivateEvictor)
         at com.sleepycat.je.evictor.Evictor.doCriticalEviction(Evictor.java:269)
    at com.sleepycat.je.dbi.CursorImpl.close(CursorImpl.java:711)
         at com.sleepycat.je.Cursor.close(Cursor.java:326)
    Once it has a lock on the evictor it seems to need to lock the UtilizationProfile:
    "NioProcessor-25" prio=3 tid=0x08ee4800 nid=0x5f waiting for monitor entry [0x70833000..0x70833970]
    java.lang.Thread.State: BLOCKED (on object monitor)
         at com.sleepycat.je.cleaner.UtilizationProfile.putFileSummary(UtilizationProfile.java:787)
         - waiting to lock <0x7f55bf70> (a com.sleepycat.je.cleaner.UtilizationProfile)
         at com.sleepycat.je.cleaner.UtilizationProfile.flushFileSummary(UtilizationProfile.java:776)
         at com.sleepycat.je.cleaner.UtilizationTracker.evictMemory(UtilizationTracker.java:100)
         at com.sleepycat.je.evictor.PrivateEvictor.startBatch(PrivateEvictor.java:109)
         at com.sleepycat.je.evictor.Evictor.evictBatch(Evictor.java:302)
         at com.sleepycat.je.evictor.Evictor.doEvict(Evictor.java:244)
         - locked <0x7f157c68> (a com.sleepycat.je.evictor.PrivateEvictor)
         at com.sleepycat.je.evictor.Evictor.doCriticalEviction(Evictor.java:269)
    But that is locked by a cleaner thread which holds onto the lock the whole time that it is deciding which file to delete:
    "Cleaner-19" daemon prio=3 tid=0x08d35800 nid=0x2f runnable [0x71763000..0x71763970]
    java.lang.Thread.State: RUNNABLE
         at java.util.TreeMap.successor(Unknown Source)
         at java.util.TreeMap$PrivateEntryIterator.nextEntry(Unknown Source)
         at java.util.TreeMap$EntryIterator.next(Unknown Source)
         at java.util.TreeMap$EntryIterator.next(Unknown Source)
         at com.sleepycat.je.cleaner.UtilizationProfile.getBestFileForCleaning(UtilizationProfile.java:344)
         - locked <0x7f55bf70> (a com.sleepycat.je.cleaner.UtilizationProfile)
         at com.sleepycat.je.cleaner.FileSelector.selectFileForCleaning(FileSelector.java:187)
         at com.sleepycat.je.cleaner.FileProcessor.doClean(FileProcessor.java:197)
         - locked <0x7f153340> (a com.sleepycat.je.cleaner.FileProcessor)
         at com.sleepycat.je.cleaner.FileProcessor.onWakeup(FileProcessor.java:138)
         at com.sleepycat.je.utilint.DaemonThread.run(DaemonThread.java:141)
         at java.lang.Thread.run(Unknown Source)
    This seems to take quite a while.
    So basically I have about worker 50 threads all waiting to lock the evictor and horrible throughput and response times.
    Problems that I see:
    1. If an eviction is in progress having other threads waiting to try to evict more stuff seems pointless.
    2. It is impossible for evictions to happen in parallel.
    3. The locking on UtilizationProfile to way too coarse: cleaner threads shouldn't be able to block evictions for long periods of time.
    4. getBestFileForCleaning doesn't seem very efficient. Big TreeMaps are getting copied around and iterated over. If the data was kept in a priority queue cleaner threads might be able to quickly take the best file of the queue.
    5. Ideally nothing would be being added to or evicted from the cache all the time. Because of my data access patterns I know that having the values in the cache is pointless, and get and puts could bypass the cache completely.

    Hello Cormac,
    If you're a customer, please contact me via email to take this offline (charles.lamb @ o.com).
    Here are some suggestions, questions, and comments:
    . Do you see this particular thread dump all the time or just occasionally? In other words, is it always the same or just certain parts of it? I know you're seeing the eviction part all the time, but what about the Cleaner Thread?
    . One workaround you can try is to increase the amount of cache for the Utilization tracker. You can do this by changing the EnvironmentConfig.CLEANER_DETAIL_MAX_MEMORY_PERCENTAGE. It defaults to 2% so moving it to 5% might have a big impact.
    . Your cache size is << your database size. Have you run DbCacheSize to see if you have sized your cache large enough to fit all of the internal tree nodes in memory? In general, you don't have a lot of cache so an increase in cache size may yield a significant increase in performance.
    . You can look at the stats and if there is no cleaner backlog, you can reduce the number of cleaner threads from 40.
    . You can try increasing the log file size from the default of 10MB to (say) 50 or 100MB.
    Charles Lamb

  • Queues - 1 MDB or many?

    I need an opinion - how well would a system with a single MDB that handles multiple message types (e.g. xml messages, with tags to indicate the type of message) vs having multiple MDB's per topic. I guess I'm looking at a "best practice" pattern. I've been thinking of this and realized that if you have a single MDB with multiple message types, then this could mean that if there were a message type that sees a high volume vs another that sees a lower volume, the lower volume message processing of the messages would be delayed.
    From what I've read, the container is supposed to compensate for a high volume of messages through creating more instances, but this still doesn't stop the fact that the messages are processed FIFO, so having multiple topics would be a far more better way to go.
    The hope here however was to have a model where we would only have two types of messages initially processed asynchronously, while the others were processed synchronously through regular session beans, but additional message types may be turned on later to run asynchronously without having to create new MDB's for each additional topic. But I think this could just mean creating unnecessary delays for other types of messages.
    (reposted from AQ forum...figured this may be a better forum for this)
    Any thoughts?
    Thanks

    Jason -- One important point is that the EJB specification (specifically MDBs) does not guarantee FIFO processing. Here is the quote from section 15.4.6 of the spec:
    A container allows many instances of a message-driven bean class to be executing concurrently, thus allowing for the concurrent processing of a stream of messages. No guarantees are made as to the exact order in which messages are delivered to the instances of the message-driven bean class, although the container should attempt to deliver messages in order when it does not impair the concurrency of message processing. Message-driven beans should therefore be prepared to handle messages that are out of sequence: for example, the message to cancel a reservation may be delivered before the message to make the reservation.
    That said, I have seen queuing systems that have used both types of arrangements you describe (although none were using JMS.) For the generic case, there were problems if the queue was backed up so you might consider multiple queues with different priorities, each of which has a generic payload. This helps starvation of time critical messages.
    If you do establish different topics, then you will have more work to do in terms of deployment and management of the topics, but the messages will be cleanly separated and you may be able to make some optimizaitons of message processing since they can be created in a form that best mathces their use.
    Overall, my experiences with generic queues, once we established multiple queues with different priorities, was good. Just be ready for the additional overhead of processing XML messages.
    Thanks -- Jeff

  • How do I use same MDB for multiple Queues? Deployment ?

              Here is what I am trying to do
              I have written one MDB that I want to use for multiple queues. I have seen posting
              mentioning that code a new weblogic-ejb-jar.xml to define other queues as the
              solution.
              Is there any other work around?
              I want to add queues in future as and when needed. I don't want to modify the
              already deployed jar to replace it with new weblogic-ejb-jar.xml everytime I have
              to add another queue for the message-driven-bean. Is is possible to use some kind
              of reference tag and just put weblogic-ejb-jar.xml in a new jar file and deply
              that every time I have a new queue to use for this MDB ( I don't think so, but
              again ???).
              Any help would be greatly appreciated.
              Chris
              

    Sorry -- that's the only solution for now.
              greg
              "Chris" <[email protected]> wrote in message
              news:[email protected]..
              >
              > Here is what I am trying to do
              >
              > I have written one MDB that I want to use for multiple queues. I have seen
              posting
              > mentioning that code a new weblogic-ejb-jar.xml to define other queues as
              the
              > solution.
              >
              > Is there any other work around?
              >
              > I want to add queues in future as and when needed. I don't want to modify
              the
              > already deployed jar to replace it with new weblogic-ejb-jar.xml everytime
              I have
              > to add another queue for the message-driven-bean. Is is possible to use
              some kind
              > of reference tag and just put weblogic-ejb-jar.xml in a new jar file and
              deply
              > that every time I have a new queue to use for this MDB ( I don't think so,
              but
              > again ???).
              >
              > Any help would be greatly appreciated.
              >
              > Chris
              

Maybe you are looking for

  • Illustrator CS6 crashes every time I move an object

    Every time I have tried to use illustrator in the past hour or so, it will quit when I try to use the selection tool to move an object or type. This is also going on in InDesign, but it doesn't crash. Both programs were working fine this morning when

  • Acrobat crashes during VB Script when workstation is locked

    Very strange problem, maybe only related to my particular configuration but was hoping someone had some ideas. I've been working this issue for months and haven't been able to figure it out. I have an outlook macro that processes emails, downloads PD

  • Dynamical declaration of SELECT-OPTIONS / RANGE possible

    Hi fellow programmers, does anybody know whether there is a way to declare a SELECT-OPTION respectively a RANGE dynamically during runtime? I have both the name of the range to be created and the DDIC-referencefield stored in variables. Thanks in adv

  • Logic 8 crashing when Initializing Core Audio

    Does anybody have an answer for this? I am trying to launch Logic 8 on my G5 and every time it gets to initializing Core Audio it crashes unexpectedly. I tried launching it by disabling the core audio driver as the Apple site suggest and it works fin

  • Error running setupvirtualdirectories.bat during install

    Hello Everyone, I am trying to install an addtional copy of Agile PLM for Process 6.1 for testing. When I get to the point of creating the virtual directories through the command line I get several errors. Errnumber: -2147221020 <0x800401E4> Error Ac