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!

Advertisement

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

Tags: Fusion Middleware

Similar Questions

  • That could limit the number of MDB instances in the JMS queue?

    Hi all, I have an app that publish messages in a JMS queue. In SD in the MDB, I defined the following:

    < wls:ejb - name > VfDataMiner < / wls:ejb - name >
    < wls:message - driven-descriptor >
    < wls:pool >
    < wls:max - beans-in-free-pool > 25 < / wls:max - beans-in-free-pool >
    < wls: initial-beans-in-free-pool > 10 < / wls: initial-beans-in-free-pool >
    < / wls:pool >
    < / wls:message - driven-descriptor >

    My understanding is that this should create up to 25 multilateral development banks to process messages when necessary and that number will fall to 10 if there is no traffic. However, it does not appear so as I saw that 16 consumers at all times.

    At first, I thought it might be that the server is running out of threads to spawn new BMD so I also added the thread pool using the - Dweblogic.threadpool.MinPoolSize = 100 in the start, but it is always showing 16 consumers. I miss any idea what else do you? I use this on WLS 11 g.

    Thanks in advance for the advice/pointers.

    http://download.Oracle.com/docs/CD/E12840_01/WLS/docs103/EJB/message_beans.html

    The number of MDB instances in the free pool is limited by the value of the element of max-beans-in free-pool in memory of weblogic-ejb - jar.xml and available. The value of max-beans-in free-pool is > determined by the following rules, in order of precedence:

    If a custom ExecuteThreadPool is set, the number of threads MDB is identical to the value of ExecuteThreadCount.
    If a WorkManager customized with max-son-constraint is defined, then the number of threads MDB is identical to the value of max-son-stress.
    If the autotune option is disabled, the number of threads MDB is equal to the:
    (ExecuteThreadCount / 2) + 1

    The number of threads MDB is equal to 16 (this is the default).

    If you want more of 16 sons define a handler for a custom job and associate it with the strategy of sending of the mdb.

  • (XML-based) SMS sending to the JMS queue

    Hi gurus,

    How we can publish a text message in the JMS queue using message text option by writing to Java or PL/SQL according to the following XML schema definition:

    <? XML version = "1.0" encoding = "windows-1252"? >

    " < xsd: Schema container = ' http://www.w3.org/2001/XMLSchema "

                xmlns=" http://www.example.org "

    " targetNamespace = ' http://www.example.org "

    elementFormDefault = "qualified" >

    < xsd: element name = "Employee" >

    < xsd: annotation >

    < xsd: documentation >

    An element of the sample

    < / xsd: documentation >

    < / xsd: annotation >

    < xsd: complexType >

    < xsd: SEQUENCE >

    < xsd: element name = "EmpNo" type = "xsd: Decimal" / >

    < xsd: element name = "EmpName" type = "xsd: String" / >

    < xsd: element name = "Salary" type = "xsd: double" / >

    < / xsd: SEQUENCE >

    < / xsd: complexType >

    < / xsd: element >

    < / xsd: Schema >

    My Composite SOA will contain a JMS as a Service exposed adapter.

    Hello

    Please find enclosed the attachment for an example implementation of the Java client code to post the message to a weblogic JMS queue.

    It will be useful.

  • MQ adapter and the error queue

    Hello

    We have a problem where we had an invalid XML message on a MQ. The problem is that the MQ adapter dead before a process has been created.

    This message is now gone. It isn't on the MQ, and it is also not in any BPEL process so it cannot be placed in a hospital error.

    Is there some settings on the MQ or on adapter MQ that is needed to move the message to the workflow queue error what entrance to MQ analysis fails? Please notify.

    Below is an extract from journal:

    < 2010-02-09 13:12:32, 846 > < ERROR > < usu.collaxa.cube.activation > < MQSeries Adapter::Inbound >
    ORABPEL-11211

    DOM Exception analysis to the translator.
    DOM parsing exception in incoming XSD translator during the scan of InputStream.
    Check the error stack and correct the cause of the error. Contact oracle support if the error is not repairable.

    at oracle.tip.pc.services.translation.xlators.xsd.XSDTranslator.translateFromNative(XSDTranslator.java:202)
    at oracle.tip.adapter.mq.inbound.QueueProcessor.translateMessage(QueueProcessor.java:681)
    at oracle.tip.adapter.mq.inbound.QueueProcessor.processIndividualMessage(QueueProcessor.java:407)
    at oracle.tip.adapter.mq.inbound.QueueProcessor.processMessage(QueueProcessor.java:977)
    at oracle.tip.adapter.mq.inbound.QueueProcessor.run(QueueProcessor.java:181)
    at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
    at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:280)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: oracle.xml.parser.v2.XMLParseException: start of the element root waited.
    at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320)
    at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:341)
    at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303)
    at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:291)
    at oracle.tip.pc.services.translation.xlators.xsd.XSDTranslator.translateFromNative(XSDTranslator.java:197)

    In this scenario, the input message should have been dismissed. If you are in 10g or 11g? Research of 10g for the "rejectedMessages" at oracle home folder while 11g search for the folder "rejmsgs". You should see the message rejected in there.

    HTH,
    Sandeep

  • Copy of the JMS queues

    I write Weblogic Integration (WLI) applications. When I deploy these apps I create JMS queues on the server or I get warning messages in the Weblogic console. I have several Weblogic 10.3 servers that I need to deploy these applications WLI too.

    I wonder if there is a way I can copy the contents of the xml files that define the queues JMS from one server to another server? What are the files should be copied? I'm trying to find an easier way to create JMS queues. Create queues in the console can get a lot of time if you have a lot of queues to create.

    Any help is greatly appreciated!

    John

    Hi John,.

    There are several ways to automate the configuration of WebLogic and WebLogic JMS (like all other subsystems WebLogic), can be configured with any of them. Here are a few:

    -Script WLST on-line or off line

    -Program in Java that makes calls to mbean JMX config

    -If the JMS-dest config is absolutely identical, then you can just copy the XML of the JMS module in different areas and then use the console, JMX or WLST to modify the config.xml file to reference it. The module contain config destination, while the config.xml file contains subdeployment, store, and JMS server config.

    When you work with several WebLogic domains, make sure that all domain names are different and all the WebLogic Server names are different (even if the WebLogic servers are in different domains). In addition, in some cases all the JMS server names must be different (even if they are in different domains - apply to the apps feature FAS that use meet cross-domain if I remember correctly).

    Tom

    PS. See also [best practices Configuration JMS | http://download.oracle.com/docs/cd/E15523_01/web.1111/e13738/best_practice.htm#CACJCGHG]

  • Dynamic creation of the JMS queues

    Hello

    I understand that it is possible to define queues (and subjects) in configuration appropriate application jms.xml file. However, I suppose it is also possible to dynamically create JMS queues (i.e. at run time).

    Could someone point me in the right direction for more information on how I can achieve this? I used have a Oracle 10 g and intend to use Oracle AS JMS.

    Thank you very much


    Alistair.

    Hi Alistair,.

    Your options:
    (1) JMX Mbeans [http://download-east.oracle.com/docs/cd/B25221_04/web.1013/b14432/jmxbrowser.htm]
    (2) [http://download.oracle.com/docs/cd/B31017_01/web.1013/b28951/anttasks.htm] ant tasks

  • Consume a Message from a JMS queue on request

    Hello
    I do a few experiments with BPEL and JMS adapter.
    I know how to configure the JMS adapter to subscribe to a queue and begin a BPEL process, but I am trying to achieve a design that is more similar to the following:
    1 BPEL receives a service Web dial with a payload containing MsgID - it's activity "instantiate".
    2 BPEL called JMS adapter with MsgID
    3 JMS adapter removes the message with the given MsgID and returns it to the BPEL (or reports not found)
    4 BPEL process the message
    I have read the documentation on the JMS request/response adapter, but not what I'm looking for. Someone know how I can get this feature?
    I prefer to do it using the JMS adapter, another option could be a custom Java code that uses the JMS API.
    You can also use a JMS queue is maybe the wrong way to achieve this in which case I could code to store messages in a database and retrieve on demand.
    Robert

    I feel that a DB table would provide better support for your case.

    I'm not aware of an API to receive a message based on its JMSMessageId.
    There is a MessageConsumer.receive (), but this does not select messages based on any filter.

    Maybe I'm totally wrong, in this case, I would be happy to learn from my mistakes.

  • publication and the jms Topic subscription

    Hello

    Can someone tell me how to publish and subscribe jms messages in topic using the notion of sustainable text. I use jdeveloper to weblogic 10.3 and 11.1.1.4.0.

    Thanks in advance.

    You create a JMS adapter in the exposed Pan Services. Once you select the topic to subscribe, if you provide a subscription ID sustainable static then the listener adapter will be configured as a sustainable topic Subscriber.
    The publication doesn't have the notion of durable subscription (from which the name).

  • 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.

  • Issue, while reading the file data from a JMS queue

    Hello

    I'm trying a simple case to receive the XML of the JMS queue and inside BPEL use Assign activity to read data in a temporary variable to check the file from the JMS queue. I do the archive file name, CHRAPcXMLInvoices_DUNS_XXXXXXX_datestamp.dat, XXXXXX as the mapping of the identity of the XML from the JMS queue. Some reasons is not mapping... Can someone help me on this please? I stuck here because my final requirement was to insert the data from the XML file in a custom table, but because of this, it fails saying "can not insert a null" which means that some how he does not read the data...

    I enclose the screen... Please help...

    Hello

    I would try to replicate the same at my end, but you can do the following to me.

    You could manually put the message ("but add xmlns ="http://www.example.org" in cXML item payloadID") in the JMS and test it.

    For Ex:

    " xmlns ="http://www.example.org">"

    The XML message is clearly the namespace XSD lacks. The BPEL is looking in the correct namespace (xmlns:ns3 ="http://www.example.org" ") of the XML message, but as space of names are not added to the incoming message sound throw an exception.

    So, try to add the namespace to the XML message and publish manually in the JMS queue to start the process.

  • Problem in the JMS Quota

    Hello

    We got a scenario in which we stop accepting messages from the producer if the JMS queue quota is full. (for example. Configured for the queue quota is 10). While publish us messages from JMS queue in OSB when the quota is full, we need to catch the error of the weblogic and had to turn and must send the response to requests citing that the size of the queue is full.


    Citing the queue of proxy of the OSB and the quota is reached, OSB throws no error even we have set up the mechanism in part necessary exceptions Management error Manager. But when we try to introduce messages directly running the business of producer service (configure JMS) when the quota is full his spear an error response: (the call resulted in an error: weblogic.messaging.kernel.QuotaException: Quota blocking the time limit and no quota available.) But when the call to the proxy service is not to throw any error.


    Thanks in advance

    Can try you a Service call for business, instead of post?

  • WebLogic JMS queue - delayed Messages

    Hi all
    I am using WebLogic Server Version: 10.3.5.0 in a clustered environment.
    I use a uniform distributed queue. I investigated rate messages with a delivery so that they don't not be removed immediately and instead will wait until a specific time before their delivery. In the weblogic console, I see a field delivery time, but on all my posts, the value is (no value specified).
    I use BPEL and the JMS adapter to the queue of messages. Anyone know how I can configure this property to delay the messages?
    Thank you
    Robert

    I know that SOA JMS adapter has added new features to exploit features value-added WLS JMS in recent versions, but I don't think that the delivery time is in the plan.
    Your best bet would be to set the time to deliver on the factory of connections or the destination.

  • Hi, I bought acrobat adobe pro ms with order number: 12287735659 but I have not received the download link and the serial numbers of adobe and had this message there is a problem processing your order, please contact our Service team at the 800 448 custom

    Hi, I bought acrobat adobe pro ms with order number: 12287735659 but I have not received the download link and the serial numbers of adobe and had this message there is a problem processing your order, please contact our Service team customer to 800 448 1642 for assistance. my credit card is already loaded, but not received numbers.please series suggest

    Hi Kunal,

    If the problem still persists, can you please contact the support for this issue through https://helpx.adobe.com/support.html#/top_products.

    Please do not hesitate to me message in person if assistance is needed.

    Concerning

    Stéphane

  • I bought a LR 6 update. I received the order number and the serial number by email from Digital River. However when I try to activate the product I get a message error "we cannot validate this serial number.

    I bought a LR 6 update. I received the order number and the serial number by email from Digital River. However when I try to activate the product I get a message error "we cannot validate this serial number.

    Hi avijitm,

    You are using a Mac or Windows computer?

    Make sure there is no hosts blocking Lightroom entry onto the Adobe servers.

    Follow solution 3 referred to in article Solutions to connect, activation and errors in connection with creative cloud and Creative Suite applications

    See Error failed to validate the serial number | CS6

    Let us know if that helps.

    Kind regards

    Assani

  • 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.

Maybe you are looking for