Only 1 thread processes messages from abroad CMT Message Driven Beans?

Hello

I have an MDB configured to use CMT with a transaction REQUIRED attribute. When I deploy this bean, I get this warning: -.
<24-Nov-2010 23:29:18 o'clock GMT> <Warning> <EJB> <BEA-010081> <The message-driven bean 
WLPooledSonicJmsTransactionRequiredMessageDrivenBean was configured to use a JMS Topic, requires container-managed transactions, and uses a foreign JMS provider. Only one thread will be used to receive and process all messages.>
This 1 only average MDB will never be active reading the posts off topic, even if I'm max-beans-in-pool built to a larger number?

All links to documentation on this warning would be much appreciated.

Thank you

Mandy

Published by: MandyWarren on December 1st, 2010 15:18 - fixed tags

Published by: MandyWarren on December 1st, 2010 15:18

Is this a reasonable sentence summary?

Yep!

Tags: Fusion Middleware

Similar Questions

  • WebSphere Message Driven Bean pool lack of warning

    I receive after alarm frequently to an application running on WAS v7.

    Subject: JVMNAME_c1: WebSphere Message Driven Bean pool lack of warning

    Message Driven Bean 'JVMNAME_MDB' in the 'APPLICATIONEAR' application server 'JVM1' has a high percentage of pool narrowly with a percentage of 33% Miss. This exceeds the threshold of 25% warning. Please use the following URL for details of the alarm: https://xxxxxxxxxxx.

    According to the Foglight documents:

    If you experience performance problems, check the following:

    The minimum value of the pool size is set too low, so the container must keep naming new swimming entity bean

    ·         Try increasing the minimum size of pool on your application.

    The maximum value of the pool size is set too low, so any thread tries to get an entity bean from the pool to wait in the queue

    ·         Try to increase the number of maximum pool size on your application. For example, assign something exceeds the maximum number of concurrent users.

    I tried to increase the minimum values and maximum pool one at a time, but it did not help. The pool, I changed values to is the Thread Pool found here:

    Application servers--> "server_name"--> service listening for Message--> thread pool.

    Is this the correct pool, I should be hilarious? OR should I change the found here - QCF connection/session pool resources--> JMS--> factories of connection of the queue--> "QCF_NAME"--> Session/connection pools?

    Thanks in advance.

    You have access to the developer or the person who developed the archive application?

    In general as part of an ear or application jar file there are definitions of the minimum number of Maximum number of EJB and EJB in the pool, I think they are in WebSphere ejb - jar.xml and should look something like this.

    2000

    1000

    I see this in the IBM site on weblogic for websphere migration which can give more info

    http://www.IBM.com/developerWorks/WebSphere/library/techarticles/0706_vines/0706_vines.html#sec4c

    C. max-beans-in-free-pool and initial-beans-in-free-pool

    The element of max-beans-in free-pool sets the maximum size of the EJB free pool for a specific entity bean, bean session without State or message-driven bean. Each bean class can define the size of its own pool for free using this element.

    The element initial-beans on free-pool sets the initial number of instances of bean that will fill the free pool for a specific startup bean class. Filling the free pool with bodies improves initial response times, as initial applications for the bean can be met without generating a new instance.

    In WebLogic, every bean in the application can specify that its initial and maximum pool size and pool size may vary considerably from one Bean to another class.  To determine the specific pool size, see the weblogic-ejb - jar.xml for one of these items:


    To specify the size of the EJB pool in WebSphere Application Server, you can add an argument of the system to the JVM:

    1. In the administration console, select application-online-online Process Definition servername server => Java Virtual Machine.
    2. Add com.ibm.websphere.ejbcontainer.poolSize to the area of Generic JVM arguments, after all the existing JVM arguments. Here is an example that sets the size of the pool maximum and minimum of 1-5 for a bean called RuleEngineEJB:
    -Dcom.ibm.websphere.ejbcontainer.poolSize = myapp #RulesEngine.jar #example. RulesEngineEJB = 1, 5

    For more details, see WebSphere Tuning EJB container .

    Hope this helps

    Golan

  • Message-Driven beans and the order of the messages in the JMS queues.

    Hi all

    We use Weblogic 10.3.6 and we have a cluster with 2 JMS servers. In our project, it is important to process messages in the order when they arrive in the queues.

    Our question is simple enough, the fact that Message-Driven Beans (of the sort that take up messages in parallel) follow the order of the messages? Or do we need to configure something to do this.

    Thank you!

    According to the oracle documentation:

    With the help of unit-of-Order with Destinations spread

    As already mentioned in the Message of treatment according to the specification of JMS, Service of Message in Java specifications (to http://www.oracle.com/technetwork/java/jms/index.html ) doesn't guarantee no message ordered delivery when applications use distributed queues. WebLogic JMS redirects messages with the same disorder unit and have a target distributed to the same distributed destination member. The Member is chosen by unit of the order of the destination configuration:

    You can also

    If you distribute, you can use control unit andmax-beans-in-free-pool:

    http://docs.Oracle.com/CD/E23943_01/Web.1111/e13814/mdbtuning.htm#BABBEFCA

    More information here:

    Using Message unit-of-Order - 11g Release 1 (10.3.6)

    Tuning Message-Driven Beans - 11g Release 1 (10.3.6)

    WebLogic Server (WLS) JMS mapping control unit works with uniform distribution Destinations (Doc ID 1310795.1)

    Best regards

    Luz

  • WebLogic 10 and spring Message Driven Beans

    Hello

    I know there's a similar thread on the use of spring mdb in Weblogic 9 (Re: WebLogic 9.2 and spring Message Driven Beans but I just wanted to check was recommended for use in WebLogic 10?)

    An answer in the above thread stated: -.

    PS. FYI, we hope to improve the AMD spring at some point, but, for various reasons, we generally recommend using WebLogic BMD rather - even when you use the spring for any other purposes. WebLogic BMD include a number of value add capabilities, are very widely tested and adopted and include the ability of transparent works seamlessly with distributed WebLogic destinations.

    Is this still applicable for WebLogic 10?

    FYI, we were planning to use in a cluster environment that mapped MQ Sonic as a foreign JMS provider.

    Thank you very much

    Mandy

    Is this still applicable for WebLogic 10?

    Yes.

    Note that WL now supports EJB 3 annotations, so there is now a standard way of BMD as POJO configuration.

    For most use cases, I recommend using the [EJB 3.0 Wrapper without Injection | http://download.oracle.com/docs/cd/E15523_01/web.1111/e13727/j2ee.htm#CHDIAICD] as a starting point.

  • Problem message driven bean deployment use Log4j

    Hi all.

    Using JDeveloper 11.1.1.0.2, I'm having a problem with a message driven bean, I created and associated to a JMS queue.

    I created a project of EJB Module in my application (in which other projects exist) and created the bean. A simple test of the bean, sending a message through the jms queue and printing on system.out in the mdb onMessage() works beautifully.

    However, when I add a Commons of apache logging to my mdb, things start to go wrong. The project running on the integrated weblogic server 10.3 fails just during the deployment, due to a NoClassDefFoundError on org/apache/log4j/Logger.

    Properties of the project-> libraries and classpath, I added a log4j library (Log4j - 1.2.14.jar) next to Commons Logging 1.0.4 but it does not matter whatever it is.

    My grain of message code:
    @MessageDriven(mappedName = "weblogic.wsee.DefaultQueue")
public class MyMessageBean implements MessageListener {
    
    // logger
    private static Log sLog = LogFactory.getLog(MyMessageBean.class);
    
    public void ejbCreate() {
    }

    public void ejbRemove() {
    }

    public void onMessage(Message message) {
        MapMessage mapmsg = null;
        
        try {
            if (message instanceof MapMessage) {
                mapmsg = (MapMessage)message;

                boolean msgRedelivered = mapmsg.getJMSRedelivered();

                String msgId = mapmsg.getJMSMessageID();

                if (!msgRedelivered) {
                
                    sLog.debug("****** Successfully received message " + msgId);
                } else {

                    sLog.debug("****** Successfully received redelivered message " + msgId);
                }
                
                // Haal de inhoud op:
                int testInt = mapmsg.getInt("TestInt");

                sLog.debug("TestInt:" + testInt);
                
            } else {
                sLog.debug("Message of wrong type: " +
                                   message.getClass().getName());
            }

        } catch (Exception e) {
            sLog.error("Fout in verwerken",e);            
        }
    }
}
    Does anyone have an idea as to what I could do wrong or missing here?

    The full stacktrace:
    5-aug-2009 12:54:44 oracle.adf.share.config.ADFConfigFactory cleanUpApplicationState
INFO: Cleaning up application state
java.lang.ExceptionInInitializerError
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:247)
     at weblogic.ejb.container.dd.xml.EjbAnnotationProcessor.processWLSAnnotations(EjbAnnotationProcessor.java:1705)
     at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processWLSAnnotations(EjbDescriptorReaderImpl.java:346)
     at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:192)
     at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:93)
     at weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:1198)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:380)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
     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)
Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [Ljava.lang.Class;@51b296 for org.apache.commons.logging.impl.Log4JLogger (Caused by java.lang.NoClassDefFoundError: org/apache/log4j/Logger) (Caused by org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [Ljava.lang.Class;@51b296 for org.apache.commons.logging.impl.Log4JLogger (Caused by java.lang.NoClassDefFoundError: org/apache/log4j/Logger))
     at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:543)
     at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235)
     at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209)
     at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
     at nl.justid.dolores.mdb.MyMessageBean.<clinit>(MyMessageBean.java:19)
     ... 32 more
Caused by: org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [Ljava.lang.Class;@51b296 for org.apache.commons.logging.impl.Log4JLogger (Caused by java.lang.NoClassDefFoundError: org/apache/log4j/Logger)
     at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:413)
     at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529)
     ... 36 more
Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
     at java.lang.Class.getDeclaredConstructors0(Native Method)
     at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
     at java.lang.Class.getConstructor0(Class.java:2699)
     at java.lang.Class.getConstructor(Class.java:1657)
     at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:410)
     ... 37 more
Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Logger
     at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
     ... 42 more
<5-aug-2009 12:54:44 uur CEST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1249469684085' for task '14'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(Dolores-MessageBeans-ejb)
[EJB:011023]An error occurred while reading the deployment descriptor. The error was:
 null.'
weblogic.application.ModuleException: Exception preparing module: EJBModule(Dolores-MessageBeans-ejb)
[EJB:011023]An error occurred while reading the deployment descriptor. The error was:
 null.
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
     Truncated. see log file for complete stacktrace
java.lang.ClassNotFoundException: org.apache.log4j.Logger
     at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
     Truncated. see log file for complete stacktrace
>
5-aug-2009 12:54:44 oracle.adf.share.config.ADFConfigFactory cleanUpApplicationState
INFO: Cleaning up application state
<5-aug-2009 12:54:44 uur CEST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'Dolores'.> 
<5-aug-2009 12:54:44 uur CEST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Exception preparing module: EJBModule(Dolores-MessageBeans-ejb)
[EJB:011023]An error occurred while reading the deployment descriptor. The error was:
 null.
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
     Truncated. see log file for complete stacktrace
java.lang.ClassNotFoundException: org.apache.log4j.Logger
     at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
     Truncated. see log file for complete stacktrace
>
[Deployer:149034]An exception occurred for task [Deployer:149026]deploy application Dolores on DefaultServer.: Exception preparing module: EJBModule(Dolores-MessageBeans-ejb)
[EJB:011023]An error occurred while reading the deployment descriptor. The error was:
 null..
weblogic.application.ModuleException: Exception preparing module: EJBModule(Dolores-MessageBeans-ejb)
[EJB:011023]An error occurred while reading the deployment descriptor. The error was:
 null.
####  Deployment incomplete.  ####    Aug 5, 2009 12:54:44 PM
oracle.jdeveloper.deploy.DeployException
     at oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer.doDeploymentAction(Jsr88RemoteDeployer.java:247)
     at oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer.deployImpl(Jsr88RemoteDeployer.java:157)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdeveloper.deploy.common.BatchDeployer.deployImpl(BatchDeployer.java:82)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
     at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
     at oracle.jdevimpl.deploy.fwk.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:436)
     at oracle.jdeveloper.deploy.DeploymentManager.deploy(DeploymentManager.java:209)
     at oracle.jdevimpl.runner.adrs.AdrsStarter$5$1.run(AdrsStarter.java:1365)
Caused by: oracle.jdeveloper.deploy.DeployException
     at oracle.jdevimpl.deploy.common.Jsr88DeploymentHelper.deployApplication(Jsr88DeploymentHelper.java:413)
     at oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer.doDeploymentAction(Jsr88RemoteDeployer.java:238)
     ... 11 more
Caused by: oracle.jdeveloper.deploy.DeployException: Deployment Failed
     at oracle.jdevimpl.deploy.common.Jsr88DeploymentHelper.deployApplication(Jsr88DeploymentHelper.java:395)
     ... 12 more
#### Cannot run application Dolores due to error deploying to DefaultServer.
[Application Dolores stopped and undeployed from Server Instance DefaultServer]
    Thanks in advance!

    Greetings,
    Eelse

    Edited by: Eelse August 5, 2009 13:57

    Edited by: Eelse August 5, 2009 17:39

    Create a new profile of deployment (EAR), including the original deployment (POT) and the libraries needed (in a lib directory) solved the problem.

  • Message-driven bean 'loses' status and icon MDB

    He helps JDev v11.1.1.5.0, when I create an MDB in my project using the wizard, initially is displayed with MDB icon next to it (a small envelope with a trombone). However, about one second later, the icon becomes a normal icon 'Java' (coffee cup). I also noticed that the MDB class does NOT appear in the project properties | EJB module. List of EJB 3.0 Classes annotated. The net result is that when the application is deployed, the MDB is not register to listen to, so it will never receive JMS messages.

    I tried to create a new application from scratch and created the exact same MDB. In this application, the l' icone icon "sticks" and the class is displayed in the list box "Annotated EJB 3.0 Classes" in the project properties dialog box. (And it will record correctly to receive JMS message on deployment).

    So obviously something is different/wrong with my real application that it prevents to recognize that the MDB class is an MDB. But, I don't know what. I have looked at all the settings in the project properties, looked at the real project .jpr file, etc and you don't see anything that would cause an application to fail to recognize the multilateral development banks.

    Anyone have any suggestions on how to understand why my MDB classes are not recognized as such in the Application?

    Here's the class that I am using:

    package com.acme;
import javax.ejb.MessageDriven;
import javax.jms.Message;
import javax.jms.MessageListener;

@MessageDriven(mappedName = "acme.DefaultQueue")
public class MessageEJB implements MessageListener {
    public void onMessage(Message message) {
         // ... code here ...
    }
}

    Thank you

    Karl

    For those who have this problem on the road, here's what I found... It seems that there is a corrupt file "cache" or something in the project. Specifically, I had to delete the files in the -\classes\.data\00000000 folder. Once I deleted these files (especially .jdb) and restart JDeveloper, the correct icon displayed next to my MDB classes, AND they also came properly in the project properties | The Console of the EJB component.

    I'm not sure what are these files, but I guess they are the cache files and automatically get recreated by JDeveloper when necessary. I hope this helps someone else who has the same problem!

  • EJB3 Message-Driven Bean

    I'm developing a simple MDB using ejb3. When I deploy, I get an error to the effect that
    My MDB does not have a configured message destination. This must be defined by using a message-destination-link,
    jndi-destination, destination-resources-link name or a resource-adapter-jndi-name.

    First of all, there are examples of a compatable weblogic EJB3 MDB there? I use the popular
    EJB3 in Action as a reference, but they have nothing in there that seems to work.

    Then, this can be done by dependency injection? I wrote a file of weblogic-ejb - jar.xml and in this, I have included a
    destination-JNDI-name tag. Somehow, it doesn't get picked up?

    Any help would be appreciated!

    Thank you

    John

    BMD is created lazily. Check the status of deployment of MDB in console WLS (deployments-> your mdb-> monitoring). If the State says connected, you can test the mdb with your customer. If not, see the console output or newspapers for what has gone wrong.

    The client that I used for the test looks like this. I built using JDeveloper and modified it a bit:

    package mdb;

import java.util.Date;
import java.util.Properties;

import javax.jms.JMSException;
import javax.jms.Queue;
import javax.jms.QueueConnection;
import javax.jms.QueueConnectionFactory;
import javax.jms.QueueSender;
import javax.jms.QueueSession;
import javax.jms.TextMessage;

import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;

public class MessageDrivenEJBBeanClient {
    public static void main(String [] args) {
        final Properties env = new Properties();
        env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
        env.put(Context.PROVIDER_URL, "t3://localhost:7001");
        env.put(Context.SECURITY_PRINCIPAL, "user");
        env.put(Context.SECURITY_CREDENTIALS, "password");
        final Context ic;
        try {
            ic = new InitialContext(env);
        } catch (NamingException e) {
            throw new RuntimeException("No initial context", e);
        }

        final QueueConnectionFactory qcf;
        final Queue destQueue;
        try {
            qcf = (QueueConnectionFactory)ic.lookup("weblogic.jms.ConnectionFactory");

            // Lookup should specify the queue name that is mentioned as "mappedName" in MessageDriven Bean.
            destQueue = (Queue)ic.lookup("mdbQueue");
        } catch (NamingException e) {
            throw new RuntimeException("No jms object", e);
        } finally {
            try{
                ic.close();
            } catch (NamingException ignored) {}
        }

        final QueueConnection connection;
        try {
            connection = qcf.createQueueConnection();
        } catch (JMSException e) {
            throw new RuntimeException("No jms connection", e);
        }

        try {
            final QueueSession session = connection.createQueueSession(false, 0);
            final QueueSender sender = session.createSender(destQueue);
            final TextMessage msg = session.createTextMessage("Hello World at " + new Date());
            sender.send(msg);
        } catch (JMSException e) {
            throw new RuntimeException("jms send failed", e);
        } finally {
            try {
                connection.close();
            } catch (JMSException ignored) {}
        }
    }
}

  • For the second time in two months, all my messages in the Inbox are not there. Only the SUBJECT and the FROM is left. Tried to 'fix this folder' and lost ALL

    For the second time in two months, all my messages in the Inbox are not there. Only the SUBJECT and the FROM is left.

    Tried to 'fix this folder' and ALL - lost ALL the Inbox.

    The file is still there and works well...

    How can I stop it and what are the causes?

    Thank you all, Gabe

    If you have the file somewhere on your hard drive, export and import tools it will be important back to Thunderbird.

    https://addons.Mozilla.org/en-us/Thunderbird/addon/ImportExportTools/

    Instructions http://chrisramsden.vfast.co.uk/3_How_to_install_Add-ons_in_Thunderbird.html

  • Why there is only a single process RFS in v$ managed_standby?

    We build a backup using Oracle Dataguard 10 g server.
    Steps to start this server are:
    SQL > STARTUP NOMOUNT;
    SQL > ALTER DATABASE MOUNT STANDBY DATABASE;
    SQL > ALTER DATABASE RECOVER MANAGED STANDBY BASE DISCONNECT FROM the SESSION.

    When we show the process using v$ managed_standby
    SQL > SELECT PROCESS, STATUS, THREAD #, SEQUENCE #, BLOCK #, BLOCKS FROM V$ MANAGED_STANDBY;
    the result is

    STATUS OF PROCESS THREAD # SEQUENCE # BLOCK # BLOCKS
    --------- ------------ ---------- ---------- ---------- ----------
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    MRP0 WAIT_FOR_LOG 1 81 0 0
    RFS IDLE 0 0 0 0

    There is only a single process RFS. Whereas, when I read articles on the GDO, they mention that there are two methods of RFS.

    How to create the RFS another process? Should be to identify what are the parameters?

    Thank you very much

    Kind regards
    May


    Notes: init.ora
    SID.__db_cache_size = 2231369728
    * ._B_TREE_BITMAP_PLANS = FALSE
    * ._bloom_filter_enabled = FALSE
    * ._fix_control = 4728348: OFF ',' 5705630: WE '
    * ._IN_MEMORY_UNDO = FALSE
    * ._INDEX_JOIN_ENABLED = FALSE
    * ._OPTIM_PEEK_USER_BINDS = FALSE
    * ._OPTIMIZER_MJC_ENABLED = FALSE
    * ._SORT_ELIMINATION_COST_RATIO = 10
    * ._table_lookup_prefetch_size = 0
    *.background_dump_dest='/Oracle/SID/saptrace/arriere-plan '
    * full = '10.2.0'
    * .control_file_record_keep_time = 30
    *.control_files='/Oracle/SID/origlogA/Cntrl/cntrlSID.dbf','/Oracle/SID/origlogB/Cntrl/cntrlSID.dbf','/Oracle/SID/sapdata1/Cntrl/cntrlSID.dbf '
    *.core_dump_dest='/Oracle/SID/saptrace/arriere-plan '
    * .db_block_size = 8192
    * .db_cache_size = 3383296000
    * .db_files = 354
    * .db_name = "SID".
    * .dml_locks = 4000
    * .event = ' 10027 trace name forever, context level 1', ' 10028 trace the context name forever, level 1', 'trace 10162 name context forever, level 1', ' name of the trace 10183
    context forever, level 1,' 10191 trace the context name forever, level 1', 'trace 10629 name context forever, level 32', ' trace 10891 context name forever, level
    1', 14532 trace context name forever, level 1', 'trace 38068 name context forever, level 100',' 38087 trace context name forever, level 1,' 44951 trace name co
    ntext forever, level 1024'
    *. FILESYSTEMIO_OPTIONS = "setall".
    * .job_queue_processes = 1
    #*.log_archive_dest='/oracle/SID/oraarch/SIDarch '
    * .log_buffer = 1048576
    * .log_checkpoint_interval = 0
    * .log_checkpoints_to_alert = true
    * .max_dump_file_size = "20000".
    * .open_cursors = 800
    * .optimizer_index_cost_adj = 20
    * .parallel_execution_message_size = 16384
    * .parallel_threads_per_cpu = 1
    * .pga_aggregate_target = 3435973837
    * runoff = 160
    * .query_rewrite_enabled = "false".
    * .recyclebin = "off".
    * .remote_login_passwordfile = "exclusive."
    * .remote_os_authent = true
    * .replication_dependency_tracking = false
    * Once = 320
    * .sga_max_size = 5670000000
    * .shared_pool_size = 2228685373
    * .sort_area_retained_size = 0
    * .sort_area_size = 2097152
    * .star_transformation_enabled = 'true '.
    * .undo_management = "AUTO".
    * .undo_retention = 43200
    * .undo_tablespace = "PSAPUNDO".
    *.user_dump_dest='/Oracle/SID/SAPTRACE/usertrace '

    #DATA GUARD STANDBY DATABASE CONFIGURATION
    *. Log_archive_dest_1 = 'LOCATION = / Oracle/sid/oraarch/SIDarch'
    * .log_archive_dest_state_1 = enable
    *.log_archive_format=SIDarch%t_%s_%r.dbf
    *.standby_archive_dest=/Oracle/SID/oraarch/SIDarch
    * .fal_server = prim-server
    * .fal_client = stan-server

    Jin

    The listener on the standby site generates the RFS process depending on connection received. What is the max process archive of the newspaper? This isn't just two RFS process, we can see a lot...

    SQL> SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;

PROCESS   STATUS          THREAD#  SEQUENCE#     BLOCK#     BLOCKS
--------- ------------ ---------- ---------- ---------- ----------
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
MRP0      APPLYING_LOG          2      56362      17111     601526
RFS       IDLE                  0          0          0          0
RFS       IDLE                  0          0          0          0
RFS       IDLE                  0          0          0          0
RFS       IDLE                  0          0          0          0
RFS       IDLE                  1      60056          0          0
RFS       IDLE                  0          0          0          0
RFS       IDLE                  0          0          0          0
RFS       IDLE                  0          0          0          0
RFS       IDLE                  0          0          0          0

12 rows selected.

    Baskar.l

  • Thread of messages with false contacts

    I have a thread of messages which, since the installation of Sierra is showing the wrong contact and the mix of messages from the two contacts.

    It seems that this is because the two contacts work for the same company and have identical entries their: 'work' of phone field. If I remove the scope one of the contacts and Messages to restart, the thread returns to two threads separated by the correct contact.

    The two contacts have iPhones and different MOBILE numbers that show as being related to separate Apple ID I assume that before I upgraded, Contacts, or Messages has been able to use this information to treat them as separate persons. Also, I assume that's the way it should work.

    How do I get things to normal?

    Thank you very much

    Christian

    Hello

    Change/edit the name of the field map to read 1 or something that prevents the binding.

    Report it here http://www.apple.com/feedback/ (there is no one of the separated Contacts).

    22:00 Friday. September 30, 2016

     iMac 2.5 Ghz i5 2011 (El Capitan)
     G4/1GhzDual MDD (Leopard 10.5.8)
     MacBookPro (Snow Leopard 10.6.8) 2 GB
     Mac OS X (10.6.8).
     iPhone and iPad (2)

  • Windows no. disk Exception Processing Message c0000013 parameters 75b6bf7c 4 75b6bf7c 75b6b7c

    I get this message pop up randomly. Any ideas on how to get rid of it, or what to check. I can leave the computer, walk and pop message. Makes me crazy.

    Windows no. disk Exception Processing Message c0000013 parameters 75b6bf7c 4 75b6bf7c 75b6b7c

    I was looking for a solution to this error and found the blog entry from GFF #5 to be the answer.

    http://forums.techarena.in/Windows-Update/1009223.htm

    "The answer lies in the words" Windows: No. disc ', your PC is looking for a USB.
    device - a USB stick or a cell phone, for example - that you recently plugged
    and removed without using the option 'remove hardware safely' in the
    lower right part of your screen. The last USB device you used
    back in the USB port and then use the option 'remove the software safely.

    The pop up message will disappear. »

    In my case, I didn't plug the USB device, I just need to click on the "Remove hardware safely" in the system tray and it say remove the device that is connected is more.

  • After logging in to Windows Gets an error message: Exception Processing Message c0000013 75.

    Original title: no disc dialogue Exception Processing Message c0000013 75...

    When I start Windows XP SP2 the dialog box next No. disc appears from time to time.  This started after I uninstalled the software incompatible with Windows XP.  The 75 begins a series of numbers.  The PC is several years old and did not know this before exception.

    Setting prevents just the pop-up message annoying - if there are some problems with the device, the event will always be recorded in Event Viewer.

    I've never had anyone report problems after you make adjustments - just that they are happy, that they no longer see the message.

  • Exception Processing Message c0000013 parameters 75b6bf7c at startup

    Possibly caused by an update to Windows XP. I get this annoying message whenever I start my computer. It starts with "Windows - no disk". Once I have that then I get the Message of the Exception processing, as shown above.

    How can I solve the problem?

    Hello

    1 have had any changes made on the computer before the show?

    2. have you used any USB (Universal Serial Bus) device on the computer recently?

    I suggest you to see link for a possible solution and check if it helps:

    http://answers.Microsoft.com/en-us/Windows/Forum/windows_xp-system/Windows-no-disk-exception-processing-message/b1a67525-d5e8-46AE-9801-6b169547e656

    Note: using third-party software, including hardware drivers can cause serious problems that may prevent your computer from starting properly. Microsoft cannot guarantee that problems resulting from the use of third-party software can be solved. Software using third party is at your own risk.

  • A message Windows - no disk Exception Processing Message c0000013 parameters 75b6bf9c 4 75b6bf9c

    Hello

    How to solve the problem of my computer with this message Windows - no disk Exception Processing Message c0000013 parameters 75b6bf9c 4 75b6bf9c. It appears everytimes I start running my computer.
    After a few minutes work on my pc that these messages is displayed. clicking on it after about 5 - 6 times makes it disappear for another 2 minutes, until it again...
    Thanks in advance

    Mark

    Hi Mark,

    Did you do any hardware changes or software on your computer before this problem?

    Windows no. disk Exception Processing Message c0000013 parameters 75b6bf7c 4 75b6bf7c 75b6b7c


    Note:     software use of third parties, including hardware drivers can cause serious problems that may prevent your computer from starting properly. Microsoft cannot guarantee that problems resulting from the use of third-party software can be solved. Software using third party is at your own risk.

    Hope the helps of information.

  • Error message, Windows no disk Exception Processing Message c0000013 parameters 75b6bf7c 4 75b6bf7c 75c6bf7c? This error message appears on start up, but will be closs after several attepts.

    Error message, Windows no disk Exception Processing Message c0000013 parameters 75b6bf7c 4 75b6bf7c 75c6bf7c? This error message appears on start up, but will close after several attempts.

    The message above appears on start up. Want to know how to prevent it from happening?

    Hello

    • What were the changes made before the show?
     
    Check to see if the problem exists in Safe Mode, if the computer works as expected in mode without failure, then we can solve the problem in the clean boot state.
    a. refer to the article below for the procedure safe mode in Windows XP
    A description of the options to start in Windows XP Mode
    http://support.Microsoft.com/kb/315222
     
    b. it is a possibility that there is a startup program that is launched with a command line and it appears.
    You need to perform a clean boot to find the program that is causing and then disable or remove.
    How to configure Windows XP to start in a "clean boot" State
    http://support.Microsoft.com/kb/310353/en-us
    Note: When you have finished troubleshooting, proceed as explained in the article to reset the computer to start as usual.
    I hope this helps.

     

Maybe you are looking for