WebSphere Message Driven Bean pool lack of warning

Similar Questions

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

  • By using the Service path
  • The hash-based routing using

  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

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

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

• 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) {}
          }
      }
  }
  

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

• my happy (request) message after processing XSLT lack of Landau (string) values comparing to the context of the initial message. I know don't know why

  Hello

  I stuck the Trace of the Invocation of the OSB below: why param values such as: 'F', 'PL' are missing in Message context changes?

  The initial Message context

  $body added

  " < = xmlns:soapenv soapenv:Body ' http://schemas.xmlsoap.org/SOAP/envelope/ "xmlns:sear =" " http://www.Ferrovial.es/XSD/SearchRegionEX_PM "xmlns:arc =" http://www.Ferrovial.es/XSD/architecture "xmlns:sear1 =" http://www.Ferrovial.es/XSD/SearchRegion_CDM "> "

  < sear: SearchRegionEXRequest_PM >

  < arc: HeaderMsgReq >

  <!-in option: - >

  < arc: functionalId >? < / arc: functionalId >

  <!-in option: - >

  < arc: messageId >? < / arc: messageId >

  < arc: timeStamp >? < / arc: timeStamp >

  < arc: consumerApp >? < / arc: consumerApp >

  < arc: consumerUsr >? < / arc: consumerUsr >

  <!-in option: - >

  < arc: language >? < / arc: language >

  < / arc: HeaderMsgReq >

  < sear1:BodyMsgRequest >

  F < sear1:Idiom > < / sear1:Idiom >

  < sear1:IdRegion > PL < / sear1:IdRegion >

  < sear1:IdCountry > PL < / sear1:IdCountry >

  < sear1:applicationCode >? < / sear1:applicationCode >

  < / sear1:BodyMsgRequest >

  < / trigger: SearchRegionEXRequest_PM >

  < / soapenv:Body >

  +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

  Changes of message context

  $body modified

  " < = xmlns:soapenv soapenv:Body ' http://schemas.xmlsoap.org/SOAP/envelope/ "xmlns:sear =" " http://www.Ferrovial.es/XSD/SearchRegionEX_PM "xmlns:arc =" http://www.Ferrovial.es/XSD/architecture "xmlns:sear1 =" http://www.Ferrovial.es/XSD/SearchRegion_CDM "> "

  " < = xmlns:mime tns:ZphoenixZmdRegion01 ' http://schemas.xmlsoap.org/WSDL/MIME/ "xmlns:wsdl =" " http://schemas.xmlsoap.org/wsdl/ "xmlns:soap =" " http://schemas.xmlsoap.org/WSDL/SOAP/ "" "xmlns:n1 =" urn: sap - com:document:sap:rfc:functions ' xmlns:ns3 = ' http://www.Ferrovial.es/XSD/Ferrovial_CDM "xmlns:ns2 =" http://www.Ferrovial.es/XSD/SearchRegion_CDM "xmlns:xsd2 =" http://www.Ferrovial.es/XSD/SearchRegionEX_PM "xmlns:ns1 =" http://www.Ferrovial.es/XSD/architecture "xmlns:wsu =" http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd "xmlns:http =" http://schemas.xmlsoap.org/wsdl/http/ "xmlns:wsoap12 =" http://schemas.xmlsoap.org/wsdl/Soap12/ "xmlns:tns =" "urn: sap - com:document:sap:soap:functions:mc - style" xmlns:wsp =" http://schemas.xmlsoap.org/ws/2004/09/Policy " > "" "" "

  < tns:ILand1 / >

  < tns:ILangu / >

  < tns:IRegio / >

  < / tns:ZphoenixZmdRegion01 >

  < / soapenv:Body >

  ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

  and here is the XSLT:

  <? XML version = "1.0" encoding = "UTF-8"? >

  < xsl: stylesheet version = "1.0".

  ' xmlns:UUIDUserFunction = ' http://www.Oracle.com/xsl/transform/Java/COM.BEA.WLI.SB.stages.functions.UUIDUserFunction "" "

  ' xmlns:IsUserInGroupFunction = ' http://www.Oracle.com/xsl/transform/Java/COM.BEA.WLI.SB.stages.functions.IsUserInGroupFunction "" "

  ' xmlns:IsUserInRoleFunction = ' http://www.Oracle.com/xsl/transform/Java/COM.BEA.WLI.SB.stages.functions.IsUserInRoleFunction "" "

  ' xmlns:ns0 = ' http://www.Ferrovial.es/BO_CONS/PS_SearchRegionEX_HTTP_CORP "" "

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

  ' xmlns:DVMFunctions = ' http://www.Oracle.com/xsl/transform/Java/COM.BEA.WLI.SB.functions.DVM.DVMFunctions "" "

  xmlns:TNS = "" urn: sap - com:document:sap:soap:functions:mc - style ""

  " xmlns:oracle - xsl-Mapper = ' http://www.Oracle.com/xsl/Mapper/schemas "" "

  ' xmlns:oraxsl = ' http://www.Oracle.com/xsl/transform/Java "" "

  ' xmlns:XrefFunctions = ' http://www.Oracle.com/xsl/transform/Java/COM.BEA.WLI.SB.functions.xref.XrefFunctions "" "

  " xmlns: xsi =" http://www.w3.org/2001/XMLSchema-instance "" xmlns: xsl = " " http://www.w3.org/1999/XSL/transform "

  ' xmlns:BasicCredentialsUserFunction = ' http://www.Oracle.com/xsl/transform/Java/COM.BEA.WLI.SB.stages.functions.BasicCredentialsUserFunction "" "

  exclude-result-prefixes = "xsd oracle xsl map xsi xsl tns UUIDUserFunction IsUserInGroupFunction IsUserInRoleFunction DVMFunctions XrefFunctions BasicCredentialsUserFunction oraxsl ns0.

  ' xmlns:ns1 = ' http://www.Ferrovial.es/XSD/architecture "" "

  ' xmlns:xsd2 = ' http://www.Ferrovial.es/XSD/SearchRegionEX_PM "xmlns:wsdl =" http://schemas.xmlsoap.org/wsdl/ ''

  ' xmlns:ns2 = ' http://www.Ferrovial.es/XSD/SearchRegion_CDM "" "

  ' xmlns:ns3 = ' http://www.Ferrovial.es/XSD/Ferrovial_CDM "xmlns:soap =" http://schemas.xmlsoap.org/wsdl/SOAP/ " "

  ' xmlns:wsp = ' http://schemas.xmlsoap.org/ws/2004/09/policy "

  xmlns:N1 = "" urn: sap - com:document:sap:rfc:functions ""

  ' xmlns:wsoap12 = ' http://schemas.xmlsoap.org/wsdl/SOAP12/ "

  ' xmlns:http = ' http://schemas.xmlsoap.org/wsdl/http/ "

  ' xmlns:wsu = ' http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd "

  ' xmlns:mime = ' http://schemas.xmlsoap.org/WSDL/MIME/ ">

  < oracle-xsl-schema Mapper: >

  <! - SPECIFICATION map SOURCES AND TARGETS, DO CHANGE NOT. - >

  < oracle-xsl-Mapper: mapSources >

  < oracle-xsl-type Mapper: source = "WSDL" >

  < oracle-xsl-schema Mapper: location = "SearchRegionEX.wsdl" / >

  < oracle-xsl-Mapper: rootElement name = "SearchRegionEXOperation".

                                         namespace=" http://www.Ferrovial.es/BO_CONS/PS_SearchRegionEX_HTTP_CORP "/ > "

  < / oracle-xsl-Mapper: source >

  < / oracle-xsl-Mapper: mapSources >

  < oracle-xsl-Mapper: mapTargets >

  < oracle-xsl-type Mapper: target = "WSDL" >

  < oracle-xsl-schema Mapper: location = "SAP_SearchRegionEX.wsdl" / >

  < oracle-xsl-Mapper: rootElement name = "ZphoenixZmdRegion01".

  Namespace = "urn: sap - com:document:sap:soap:functions:mc - style" / >

  < / oracle-xsl-Mapper: target >

  < / oracle-xsl-Mapper: mapTargets >

  <! - GENERATED BY ORACLE XSL MAPPER 12.1.3.0.0(XSLT Build 140529.0700.0211) in [Mar 16 June at 14:37:31 CEST 2015]. - >

  < / oracle-xsl-schema Mapper: >

  <! - user edit BELOW this line--DO NOT REMOVE THIS LINE-->

  < xsl: template match = "/" >

  < tns:ZphoenixZmdRegion01 >

  < ILand1 >

  < xsl: value-of select = "/ ns0:SearchRegionEXOperation / xsd2:SearchRegionEXRequest_PM / ns2:BodyMsgRequest / ns2:IdCountry" / >

  < / ILand1 >

  < ILangu >

  < xsl: value-of select = "/ ns0:SearchRegionEXOperation / xsd2:SearchRegionEXRequest_PM / ns2:BodyMsgRequest / ns2:Idiom" / >

  < / ILangu >

  < IRegio >

  < xsl: value-of select = "/ ns0:SearchRegionEXOperation / xsd2:SearchRegionEXRequest_PM / ns2:BodyMsgRequest / ns2:IdRegion" / >

  < / IRegio >

  < / tns:ZphoenixZmdRegion01 >

  < / xsl: template >

  < / xsl: stylesheet >

  Hello

  What I do in this case is to stick the piece of xml code that I want to ask in an ascii Editor. So I replace all tags, content and oblique end etc. with the bar to get an xpath expression. I compare with the xpath expression in the XSLT. Placing them underneath eachother makes it easy to compare. You're example I take:

  //soapenv:Body                             /sear:SearchRegionEXRequest_PM/sear1:BodyMsgRequest/sear1:Idiom
  

  With the XPath of the xlt described with a piece of xml (given the lack of namespace is not the same):

                 /ns0:SearchRegionEXOperation/xsd2:SearchRegionEXRequest_PM/  ns2:BodyMsgRequest/ns2  :Idiom
  

  Then you will see that the root in the xpath expression is "SearchRegionEXOperation", which is not present in the body. Then the XPath apparently follows the body. So, you will need to change the element root in the mapping definition.

  You must also post this xsd2: refers to the same namespace as sear: and ns2: the same thing as sear1: in the xml file (I did not have that).

  Kind regards
  Martian

• Error message HP Photosmart C4580 - 'Lack of cartridges print or not detected'.

  Original title: error HP Photosmart C4580

  My HP Photosmart C4580 gives the following message: "Print Cartridge missing or not detected". I cleaned and reinstalled both cartridges, which has been printing fine until this message appeared suddenly. How can I make them disappear and return the printer mode?
  I'm not in the mood to buy new ink cartridges just to see if that will solve the problem, then waste your time with them I find this is a fatal problem with the printer hardware.

  Hello

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

  2 Windows operating system you are using?

  Method 1:

  See the article and try to run the Troubleshooter:

  Printer in Windows problems

  http://Windows.Microsoft.com/en-us/Windows/help/printer-problems-in-Windows

  Method 2:

  See the article and try to run the HP diagnostic tools:

  Find and fix common printer problems using HP Diagnostic tools

  http://h10025.www1.HP.com/ewfrf/wc/document?DocName=c02073861&cc=us&DLC=en&LC=en

  Method 3:

  See the articles and check if that helps:

  "Cartridge problem" or "Incompatible cartridge" Message "Cartridge missing or damaged" appears on the computer

  http://h10025.www1.HP.com/ewfrf/wc/document?DocName=c01442936&cc=us&DLC=en&LC=en&product=3418707

  Let us know if it helps.

• Using windows XP: whed download afthe the beginning of download Turbo tax program an error message appears saying "user lacks administrative privileges to perform the task"need help"

  I bought a turbo tax download and during the download of the process I ge an error message (1321) saying ' windows install has sufficient privileges to install or change the file. "

  Hello

  1. have you logged as administrator?

  2 are you able to install other programs?

  I suggest to follow the steps in the following article and check if it helps.

  http://TurboTax.Intuit.com/support/IQ/install-product/error-1321--Installer-doesn-t-have-permission/SLN12336.html

  If you are always faced with the question, then I recommend you contact Turbo tax support for more help.

  http://TurboTax.Intuit.com/support/

  Hope this helps

• Startup error message - error in the lack of C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\DLCJtime.dll entry: RunDLLEntry

  I get this message and have no idea what it is or what it touches.

  "Error in entry: RunDLLEntry C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\DLCJtime.dll missing.

  Can anyone offer a solution to get rid of him?

  Hello
  This message refers to Dell printer drivers. You can try simply remove and reinstall the printer drivers relevant to get rid of it.
  If not, visit this link to the Dell website, it can be applied to your system too:
  http://support.Dell.com/support/topics/global.aspx/support/KCS/document?c=JM&l=en&s=Gen&docid=DSN_28E393B4B4A5ADEEE040A68F5B2849AA&isLegacy=true

• "Error message: Verifing DMI pool Data data ', 'Boot from CD' and Vista will not start.

  Vista will not start. Yesterday I had a remote assist of a tech trade SPS who took several Java updates and installed the recommended Java version. Until I left work the day I closed my computer so that he could install the updates from Microsoft. After the updates were finished I he turned and left for the day. When I arrived this morning, I had was a black screen and 2 lines of text following: 'Verifing DMI pool data' and 'Boot from CD' and a cursor flashing beneath them. I downloaded and executed a Western Digital utility that showed no problems with the hard drive, put in on the installation disc repair service is no error. I did a system restore to a point since yesterday morning, and Vista still does not start. Any ideas or suggestions?

  Hi JohnHorky,

  Step 1:

  First check and make sure that all physical connections on the computer are correct.

  Step 2:

  Alternatively, you can try to run a Checkdisk and check.

  a. Insert the installation disc.

  b. restart your computer.

  c. click on the Start button, click the arrow next to the button lock and then click on restart. If you are prompted, press any key to start Windows from the installation disc.

  d. choose your language settings, and then click Next.

  e. in the System Recovery Options menu, click command prompt

  f. at a command prompt, type the following command and press ENTER

  Chkdsk /f /r X: (drive letter)

  Note: When you run the checkdisk, there are risks of data loss you can take a backup before starting the checkdisk.

  g. press y when you are prompted to check the drive the next time the system restarts.

  h. close all applications and restart the computer.

  Note: When you run the disk check, there are chances of losing data if you can take a backup before starting the checkdisk.

  Step 3:

  Check if the automatic hard drive in the BIOS (Basic Input/output System) is enabled and save settings and check if it works. If it doesn't, contact the manufacturer of the system for more support options.

  I also suggest that you install the latest update of the basic system of input/output (BIOS) on the computer by contacting the manufacturer of the computer and check if it helps.

  Important: Change to the BIOS/complementary metal oxide semiconductor (CMOS) settings can cause serious problems that may prevent your computer from starting properly. Microsoft cannot guarantee that problems resulting from the configuration of the BIOS/CMOS settings can be solved. Changes to settings are at your own risk.

  Hope this information is useful.

• Do not consume messages from a durable subscription after reboot MDB

  Hello!
  
  I have two 10.0.1 running Weblogic application server.
  
  Server A has deployed a ConnectionFactory and a subject, including a persistent filestore.
  Just to test the Services, it also has a Message Driven Bean that has a durable subscription in question.
  It saves only incoming messages to a file.
  
  Server B has deployed a similar Message Driven Bean, which has also a durable subscription to this topic on ServerA. The bean uses a different client-id and the name of the subscription.
  
  To post a message, I use a Java application.
  
  First, all works fine. I send a few messages on this subject, and so, the BMD of server A and Server B prints messages as expected.
  
  Then I stop server B. Then I send a few thousand messages to the topic. I see in the Weblogic Server Administration Console, Server A 'Sustainable' subscriber messages are consumed and Server B are available (' Messages current County "). After restarting the server B, I expect that all messages in the 'Sustainable' Subscriber from Server B are consumed. But what happens is, only 34 messages consumed. Others are always available (' Messages current County "). No message is waiting.
  
  What I've observed more, this new send Messages to the topic are actually consumed. But the elders are still "dormant."
  
  I made another observation: when I start several (5) clients, which send messages on this subject, also some old messages are consumed.
  
  Anyone has an explanation for this, or can tell me what I'm doing wrong?
  
  Thanks for your help!

  Hello

  You have described a decidedly strange behavior. Here are some pictures in the dark, you might want to try independently or in combination to see if it changes the result:

  (1) if server A and Server B are in different domains, ensure that server A and Server B have different domain names and the names of different server (WL does not support duplicate domain or names of two servers with the same name in two different areas).

  (2) if the server has and B are members of different groups, making sure that they do not share the same address of multicast cluster...

  Try (3) which makes the transactional MDB if its not already transactional, or who makes the MDB non-transactionnel if it is transactional.

  (4) try to set 'max-beans-in-free-pool' 1.

  (5) check your server logs warning and error messages.

  Kind regards

  Tom

• Stateful session bean store module in EJB?

  Hello
  
  I want to use my EJB Stateful Session Bean (SFSB) module. But it seems that I can't use it because I should not inject my SFSB to a managed bean, or message driven bean (because if I do, the SFSB is communicated to all customers)
  
  I found that the proposed solution is to store SFSB in HttpSession.
  
  I'm doing this way, but I have null pointer exception.
  

  HttpSession session = (HttpSession) facesContext.getExternalContext().getSession(true); 

  So, how can I do this in the EJB module?
  
  Thank you

  Well me: hardly. Generally there is a web layer involved with a perfectly good session (or conversation) in what state can be maintained.

  Alas, you don't want to not seem to really say what is on your mind with or without my eyes so I'll offer just a hunch I have. A stateless bean remains "active" that as long as you keep a connection active IE. the reference that you are looking for or inject into your client code. The 'storage in the session bean' you refer to your first post is the Act of perpetuating the bean; as long as the reference is stored in the session you can continue to use it for the same customer without being cleaned by the container. However: when you are working from a web layer there is not a lot of use for a stateful bean because you can simply use the session itself directly to keep the substance. His personal preference if you use them or not really.

  Where you were going wrong in your initial post, is that you get the the HTTP session object in your EJB code. But you probably already figured out for yourself.

• Distributed theme and messages duplicated clustered BMD

  It's weird, no? I think that it is a distortion of 'Destination topic' purposes.
  
  Documentation WLS:
  
  Deployment on a topic Message-driven beans distributed*.
  
  When an MDB is deployed on a distributed subject and is intended for a WebLogic Server instance in a cluster that hosts two members of the section distributed on a JMS server, the MDB gets deployed to the members of the distributed subject. This happens because the multilateral development banks are pinned to the distributed topic destination name of a member.
  
  + That is why, you will receive [number of sent messages] * [number of members of the distributed subject] more messages by MDB, depending on how may distributed section members are deployed on a WebLogic Server instance. For example, if a JMS server contains two distributed section members, then two multilateral development banks are deployed, one for each Member, so you will receive twice as much messages. +

  There are two cases of very common use for the category multilateral development banks:

  * One-copy-by-server: all servers that hosts the MDB Gets a copy of every message posted. (In fact, each server creates a subscription.)

  * A copy - by Application: exactly a server that hosts the MDB to obtain a copy of any published including message. (Servers share a single subscription somehow, or maybe share more partitioned subscriptions).

  After your comment, I assume you are looking for this last and not the first. It is possible to get a One-copy-by-Application behavior, sometimes using one subscription on a topic that is distributed with a kind of transfer to an interim queue, sometimes via other means.

  If you have the luxury of waiting, there is a set of enhancements to WL JMS and MDB WL in the next 10.3.4 release that are specifically designed to attack one copy - Application use cases. (WL10.3.4 is also known as the 11gR1PS3 name - eg. the next series of patch).

  Tom