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.

Tags: Java

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

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

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

  • 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) {}
            }
        }
    }
    
  • Deployment using ant script is a failure

    Hey guys,.

    Having a problem when im trying to deploy my bpel process using ant scripts, was got the error below, I have not even looked at the file they specified on the server, but it was not where they said that it is. someone knows how to solve this problem. When I tried to deployment using jdeveloper, I got this error, but after I cleared the cache wsdl, this error disappeared and it worked very well, but I need to use Ant scripts to deploy and this error occurs, I tried to clear the cache wsdl as well but no luck, any help on this is REALLY appreciated

    Thank you
    Krishil


    [deployProcess] Deployment of process C:\buildroot_0\build\CashRegister\CashRegisterService\output\bpel_CashRegisterService_1.1.jar

    BUILD FAILED
    C:\buildroot_0\build.XML:92: The following error occurred during the execution of this line:
    C:\buildroot_0\build.XML:103: The following error occurred during the execution of this line:
    C:\buildroot_0\build\CashRegister\build\build-ABC.XML:14: The following error occurred during the execution of this line:
    C:\buildroot_0\build\CashRegister\CashRegisterService\build.XML:77: There was a problem connecting to the server "soadv.up.ac.za" using the port '80': bpel_CashRegisterService_1.1.jar failed to deploy. Ex
    exception message is: ORABPEL-05215
    Error loading process.
    The field of process encountered the following errors when loading the "CashRegisterService" ("1.1" review) process: BPEL validation failed.
    Source BPEL validation failed, the errors are:
    [Error ORABPEL-10000]: typelienpartenaire unresolved
    [Description]: 59 online to ' / home/oracle/product/10.1.3/OracleAS_C1/bpel/domains/default/tmp/.bpel_CashRegisterService_1.1_7fe4cbb7aa31f89de5cfc208dc3326d3.tmp/CashRegisterService.bpel ', partnerLink
    Type "{http://oracle.com/esb/namespaces/DefaultSystem} execute_pptLT" of partnerLink 'CashRegisterESBRouting' is not defined.
    [Potential fix]: ensure that typelienpartenaire ' {http://oracle.com/esb/namespaces/DefaultSystem} execute_pptLT ' is defined in the process WSDL file or the WSDL file that is referenced by the property
    ySet 'CashRegisterESBRouting' in the deployment descriptor.
    [Error ORABPEL-10007]: messageType unresolved
    [Description]: line 95 of "/ home/oracle/product/10.1.3/OracleAS_C1/bpel/domains/default/tmp/.bpel_CashRegisterService_1.1_7fe4cbb7aa31f89de5cfc208dc3326d3.tmp/CashRegisterService.bpel", WSDL messages
    eType '{http://oracle.com/esb/namespaces/DefaultSystem} DebtorInfo_request' variable 'callbackClient_execute_InputVariable' is not defined in the WSDL files.
    [Potential fix]: make sure the messageType "{http://oracle.com/esb/namespaces/DefaultSystem} DebtorInfo_request" WSDL is defined in one of the files referenced by the deployment descriptor WSDL.
    [Error ORABPEL-10000]: typelienpartenaire unresolved
    [Description]: line 743 of "/ home/oracle/product/10.1.3/OracleAS_C1/bpel/domains/default/tmp/.bpel_CashRegisterService_1.1_7fe4cbb7aa31f89de5cfc208dc3326d3.tmp/CashRegisterService.bpel", partnerLin
    kType ' {http://oracle.com/esb/namespaces/DefaultSystem} execute_pptLT "of partnerLink 'CashRegisterESBRouting' is not defined.
    [Potential fix]: ensure that typelienpartenaire ' {http://oracle.com/esb/namespaces/DefaultSystem} execute_pptLT ' is defined in the process WSDL file or the WSDL file that is referenced by the property
    ySet 'CashRegisterESBRouting' in the deployment descriptor.
    [ORABPEL-10016 error]: portType unresolved
    "[Description]: line 743 of ' / home/oracle/product/10.1.3/OracleAS_C1/bpel/domains/default/tmp/.bpel_CashRegisterService_1.1_7fe4cbb7aa31f89de5cfc208dc3326d3.tmp/CashRegisterService.bpel ', portType"
    "{http://oracle.com/esb/namespaces/DefaultSystem} execute_ppt" < call > is not defined.
    [Potential fix]: make sure the class portType ' {http://oracle.com/esb/namespaces/DefaultSystem} execute_ppt ' is defined in one of the referenced WSDL files.
    .
    .
    If you installed a hotfix on the server, verify that the ownership of the bpelcClasspath domain includes patch classes.
    at com.collaxa.cube.engine.deployment.CubeProcessHolder.bind(CubeProcessHolder.java:286)
    at com.collaxa.cube.engine.deployment.DeploymentManager.deployProcess(DeploymentManager.java:925)
    at com.collaxa.cube.engine.deployment.DeploymentManager.deploySuitcase(DeploymentManager.java:791)
    at com.collaxa.cube.ejb.impl.BPELDomainManagerBean.deploySuitcase(BPELDomainManagerBean.java:448)
    at sun.reflect.GeneratedMethodAccessor96.invoke (unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    to com.evermind.server.ejb.interceptor.system.JAASInterceptor$ 1.run(JAASInterceptor.java:31)
    at com.evermind.server.ThreadState.runAs(ThreadState.java:646)
    at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
    at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
    at DomainManagerBean_RemoteProxy_4bin6i8.deploySuitcase (unknown Source)
    at com.oracle.bpel.client.BPELDomainHandle.deploySuitcase(BPELDomainHandle.java:319)
    at com.oracle.bpel.client.BPELDomainHandle.deployProcess(BPELDomainHandle.java:341)
    at deployHttpClientProcess. jspService(_deployHttpClientProcess.java:376)
    at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
    at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:462)
    at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)
    at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
    to oracle.security.jazn.oc4j.JAZNFilter$ 1.run(JAZNFilter.java:396)
    at java.security.AccessController.doPrivileged (Native Method)
    at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
    at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:410)
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
    at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
    at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
    at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
    at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
    at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
    to oracle.oc4j.network.ServerSocketReadHandler$ SafeRunnable.run (ServerSocketReadHandler.java:260)
    to com.evermind.util.ReleasableResourcePooledExecutor$ MyWorker.run (ReleasableResourcePooledExecutor.java:303)
    at java.lang.Thread.run(Thread.java:595)


    Total duration: 14 seconds
    C:\buildroot_0 >

    Krish,

    I need two clarification

    1. What is the port number of your SOASuite? Manifest error that you want to deploy on port: 80 (makesure there wont be anymismatch)
    2. What is in your deploymentplan?

    When you use the "Ant" command to deploy, it will look for the build.proerties file where your port is defined. change to the right

    Thank you

    Sen

  • A Message in a rectangular box "Messages Agent wants to use the 'Local products' kenchain. appearing on the screen and ask for Keychain password password.  This started after I changed the password of Apple resulting for the purchase of a new iPhone

    A Message in the box 1. "Message agent wants to use the 'Local products' kenchain. "is appearing on the screen and ask for Keychain password password.  This started after I changed the password of Apple resulting for the purchase of a new iPhone.

    My iPhone 5 has been damaged and the screen was not visible.  As a result, I couldn't open the iPhone.  I bought 5 s iPhone and when I got to connect with the iCloud

    I remember the answers to security questions.   The seller must change the password and enter new answers to security questions, I did.  This happened in Bangalore.  When I'm home in Ernakulam, Kochi (India), where I has the Air of Mac, Ipad and my wife had another iPhone and laptop computer Dell, these problems began to come up on the screen and blocks the screen.

    Four Messages are appearing: the first is on the top.

    Other messages are:

    2. ' cloudd wants to use the kenchain 'local products '. '

    appearing on the screen and ask for Keychain password password.

    3. ' com.apple.iCloudHelper.xpc wants to use the kenchain 'local products '. appearing on the screen and ask for Keychain password password.

    4. ' cloudpaired wants to use the kenchain 'local products '. ' is appearing on the screen and ask for Keychain password password.

    It of an upheaval and please suggest how to solve this problem

    Hello remy!

    I see that you are either prompted by iCloud Keychain with various alert messages.  I know it's important to have iCloud Keychain works correctly and I am pleased to offer you an article that should help you.  Please follow the instructions in the following support article:

    If your Mac keeps asking for the password in the keychain

    Thank you for using communities of Apple Support.

    See you soon!

  • the DMP is missing when deploying using DMM

    Hello

    I have a DMM and DMP on my network, for a reason that I put a '.xml' file on my DMP in the contents of the folder (\usb_1\deployment\content\\... http://tmp) and x - tac core folder too.

    the problem is when I deploy a presentation using the dmm to the DMP the xml file I store is MISSING.

    the question is why the xml file? I want this file is still there when I via DMM to the DPM Deployment Package.

    Thanks in advance for any advice you may have.

    Kind regards

    Hi Andrie,

    This folder is reserved for the deployment package, thus, all the files already present will be deleted when you perform a deployment.

    When you deploy a presentation or playlist, the DMM will push all required content for presentation, so, I'm afraid, I can't really point to attempt to download a file manually, but if you really want to do, you can download it after that deployment ended or just put in a different folder.

    Concerning

    Daniel

  • How to use log4j in an EJB Module?

    I've included the log4j.jar in libraries;

    log4j.XML added in the sources folder.

    but I m getting an error:

    < 22 April 2014 11:07:50 PKT > < WARNING > < EJB > < BEA-010065 > < MessageDrivenBean threw an Exception in onMessage(). The exception is:

    java.lang.NoClassDefFoundError: org/apache/log4j/recorder.

    java.lang.NoClassDefFoundError: org/apache/log4j/Logger

    during the tests. MyMessageBean.onMessage (MyMessageBean.java:39)

    at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:575)

    at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:477)

    at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:375)

    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4855)

    Truncated. check the log file full stacktrace

    Kindly guide me how to solve this problem?
    Thank you!

    Here is the Solution:
    NetBeans - how to use log4j in an EJB Module with WebLogic? -Stack overflow

  • Im having problems downloading from my site using ftp hosting

    Im having problems downloading from my site using ftp hosting, I get the following message: the server does not not in time. FTP may not be supported on this server [connection timed out after 15007 milliseconds].

    See this discussion where the issue has been widely debated

    FTP download failed: error 553

  • Why do I get an internal error message when trying to use acrobat reader?

    Why do I get an internal error message when trying to use acrobat reader?

    Hi David,

    Let me know if the problem persists.

    Kind regards

    Nicos

  • When I have videos on my calendar, they do not play in the screen of the monitor. I hear the audio but can't see the image. To test if my new files are somehow the problem, I went back and used video files that I have used successfully a year ago and th

    When I have videos on my calendar, they do not play in the screen of the monitor. I hear the audio but can't see the image. To test if my new files are somehow the problem, I went back and used video files that I have used successfully a year ago, and they no longer play in the monitor window. I hear the sound track, but don't see any video. Have I changed it some setting that controls video playback in the monitor window?

    Randy Ruttger

    Thanks for the follow-up.

    Missing in this equation are the Premiere Elements version you were using and the operating system on which it is running. But...

    The Act is accomplished. But... Up to now, and after that you went ahead and moved to version 12, we now learn what Premiere Elements version you were using. We don't yet know the operating system involved.

    You said first Elements 10. First 10 Elements is affected by a problem serious display known if the computer uses an NVIDIA GeForce video/graphics card card. In this issue, the only cure is to roll back the version of the driver about may 2013. The description of the problem and how to make the rear roller are described in one of the messages at the top of this forum. What video/graphics card your computer use?

    On another front, Adobe will release a new version of Premiere Elements any day now. Not one, but Adobe knows the function defined for the new version. This type of information is announced at the time of the release of the new version.

    So the solution to the problem you presented in this thread could have been...

    1 roll back the version of the NVIDIA GeForce driver for all may 2013 if possible (Windows 8 or 8.1 64 bit, maybe not possible)

    2. move to a different version of Premiere Elements (which you did)

    I offer the foregoing for consideration so that you can review your decisions. We are pleased to learn that the first items 12/12.1 works for you.

    Please do not hesitate to ask questions and seek clarification, but do not forget that the answers are in the details.

    Best wishes

    RTA

  • Using Log4J in JRUN leads to conflict ClassLoader

    Summary:
    Using Log4J in JRUN leads to conflict ClassLoader

    Steps to reproduce:
    I created a java class file that uses Log4J. I've bundled in a jar and place it in the directory "JRun4\servers\cfusion\cfusion-ear\cfusion-war\WEB-INF\lib". When I use the < CFOBJECT > tag to instantiate the class, I get an error message:

    impossible log4j:error to instantiate appender named "adest.
    log4j:error a 'org.apache.log4j.ConsoleAppender' object is not assigned to a variable 'org.apache.log4j.Appender '.
    log4j:error the class 'org.apache.log4j.Appender' has been commissioned by
    log4j:error [sun.misc.Launcher$AppClassLoader@53ba3d] whereas the type object
    log4j:error 'org.apache.log4j.ConsoleAppender' has been charged by [coldfusion.bootstrap.BootstrapClassLoader@4ca6b6].

    Messages appear in the cfusion - err.log. My Appender is called adest, so I know it is to find the class and running. Maybe someone who knows more about the functioning of ColdFusion and JRun classloaders can help me. I checked on similar posts, but nothing is quite like this one.

    My Log4J configuration file is named "x_log4j.properties" and has this entry:
    ...
    log4j. Category.IHF.Logging.IHFAgentLogger = Warn, adest
    !-----------------------------------------------------------------------------!
    ! Declare an output file for the recorder of the IHF Agent Applications!
    !-----------------------------------------------------------------------------!
    log4j.appender.ADEST = org. Apache.log4j.RollingFileAppender
    log4j.appender.ADEST.file=C:\\Work\\agent_applications.log
    log4j.appender.ADEST.layout = org. Apache.log4j.PatternLayout
    log4j.appender.ADEST.layout.ConversionPattern=%p|+|%d{yyyy-mm-dd}|+|%d{hh:mm:SS:SSS}|+|%m| + | %n
    log4j.appender.ADEST.MaxFileSize = 25 KB
    log4j.appender.ADEST.MaxBackupIndex = 5
    log4j. Additivity.IHF.Logging.IHFAgentLogger = false

    ...

    What should have happened? :
    I should have not seen an error and a new logfile specified by my .properties file would be created and receive the output of the ColdFusion call

    Product version: ColdFusion MX7 7,0,0,91690
    Product version: JRun 4 (Build 84683)
    Information of the platform: Windows
    Material:
    OS version: XP
    RAM:
    Color depth:

    I think I myself have solved by moving my jar and application log4j.properties file in a directory that is not in the classpath JRun4. I moved in a directory specified in the ColdFusion administrator, where he says he's looking for COM and Java objects: \JRun4\servers\cfusion\cfusion-ear\cfusion-war\WEB-INF\cfusion\gateway\lib

Maybe you are looking for