Weblogic 10 Ant task, JMS Module & Foreign JMS Destinations

Any body knows how to configure JMS System Modules (which got introduced in WL ver. 9) and other JMS MBeans such as JMS Destinations and ConnectionFactories under the newly created JMS Module, using ant task for Weblogic 10.3 ?
Also, when I create the ForeignJMSServer and the child MBeans such as Foreign Destinations and ConnectionFactories using ant task, it just creates the ForeignJMSServer and not creating the child MBeans. The problem is with WL 10. In WL 8.1, it works fine.
In Weblogic 8.1, þe ant target for this job is as follows.
===========================================================================
     <target name="prepareForeignJMSServer">
<wlconfig url="t3://localhost:7001" username="weblogic"
password="weblogic" failonerror="false">
<create type="ForeignJMSServer" name="myForeignJMSServer" property="temp-jms-server">
<set attribute="InitialContextFactory" value="weblogic.jndi.WLInitialContextFactory"/>
<set attribute="ConnectionURL" value="t3://192.168.0.23:7001"/>
<set attribute="Targets" value="mydomain:Name=myserver,Type=Server"/>
<create type="ForeignJMSConnectionFactory" name="MyRemoteCF">
<set attribute="LocalJNDIName" value="MyLocalCFJNDI"/>
<set attribute="RemoteJNDIName" value="MyRemoteCFJNDI"/>
<set attribute="Username" value="weblogic-remote"/>
<set attribute="Password" value="weblogic-remote"/>
</create>
<create type="ForeignJMSDestination" Name="MyRemoteQueue1">
<set attribute="LocalJNDIName" value="MyLocalQueue1JNDI"/>
<set attribute="RemoteJNDIName" value="MyRemoteQueue1JNDI"/>
</create>
     </create>
          </wlconfig>
     </target>
=====================================================================
This target runs without error in WL 10, but does not create the ForeignJMSConnectionFactory and ForeignJMSDestination.
If some one knows the solution, please give me advice.
Thanks,

Maybe this is of some help: http://www.bea-weblogic.com/namenotfoundexception-when-configuring-foreign-jms-server.html

Similar Messages

  • JMS Module, Foreign Server: Destination unreachable

    Hi,
    In our OSB setup we have 2 weblogic domains (on RHEL5), one for hosting the OSB services and one that is used solely for the purpose of JMS messsaging.
    Therefore we have configured a Foreign Server in our JMS Module on the OSB Domain with following config:
    * JNDI Initial Context Factory: weblogic.jndi.WLInitialContextFactory
    * JNDI Connection URL: t3://fsb-jms1-dev:7901,fsb-jms2-dev:7901
    After deploying an EJB that makes use of this module we see following error in our log files every time when starting a Managed Server:
    ####<Jun 8, 2011 11:36:48 AM CEST> <Warning> <EJB> <esddev148> <osbms1> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <11d1def534ea1be0:-27013fcb:1306e9a12ac:-8000-0000000000000016> <13075
    25808959> <BEA-010061> <The Message-Driven EJB: MessageLogWriter is unable to connect to the JMS destination: fsb.jms.MessageLoggingQueue. The Error was:
    javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Could not establish a connection with 3499163233583403748S:fsb-jms1-dev:[7901,-1,-1,-1,-1,-1,-1]:fsb-jms1-dev:7901,fsb-jms2-dev:7901:jmsdevdomain:jmsms1, java
    .rmi.ConnectException: Destination unreachable; nested exception is:
    java.io.IOException: Empty server reply; No available router to destination; nested exception is:
    java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.io.IOException: Empty server reply; No available router to destination]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:64)
    at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:470)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:426)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
    at javax.naming.InitialContext.lookup(InitialContext.java:392)
    at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:221)
    at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
    at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
    at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
    at javax.naming.InitialContext.lookup(InitialContext.java:392)
    at weblogic.jms.common.CDS$2.run(CDS.java:486)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:131)
    at weblogic.jms.common.CDS.lookupDestination(CDS.java:480)
    at weblogic.jms.common.CDS.lookupDDAndCalloutListener(CDS.java:345)
    at weblogic.jms.common.CDS.access$100(CDS.java:41)
    at weblogic.jms.common.CDS$DDListenerRegistrationTimerListener.timerExpired(CDS.java:193)
    at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    Caused by: java.rmi.ConnectException: Could not establish a connection with 3499163233583403748S:fsb-jms1-dev:[7901,-1,-1,-1,-1,-1,-1]:fsb-jms1-dev:7901,fsb-jms2-dev:7901:jmsdevdomain:jmsms1, java.rmi.ConnectException: Destination unreachab
    le; nested exception is:
    java.io.IOException: Empty server reply; No available router to destination; nested exception is:
    java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.io.IOException: Empty server reply; No available router to destination
    at weblogic.rjvm.RJVMImpl.getOutputStream(RJVMImpl.java:352)
    at weblogic.rjvm.RJVMImpl.getRequestStreamInternal(RJVMImpl.java:612)
    at weblogic.rjvm.RJVMImpl.getRequestStream(RJVMImpl.java:563)
    at weblogic.rjvm.RJVMImpl.getOutboundRequest(RJVMImpl.java:789)
    at weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:159)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:341)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
    at weblogic.jndi.internal.ServerNamingNode_1034_WLStub.lookup(Unknown Source)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:423)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:412)
    at javax.naming.InitialContext.lookup(InitialContext.java:392)
    at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:221)
    at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
    at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
    at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:412)
    at javax.naming.InitialContext.lookup(InitialContext.java:392)
    at weblogic.jms.common.CDS$2.run(CDS.java:486)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:131)
    at weblogic.jms.common.CDS.lookupDestination(CDS.java:480)
    at weblogic.jms.common.CDS.lookupDDAndCalloutListener(CDS.java:345)
    at weblogic.jms.common.CDS.access$100(CDS.java:41)
    at weblogic.jms.common.CDS$DDListenerRegistrationTimerListener.timerExpired(CDS.java:194)
    ... 4 more
    Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.io.IOException: Empty server reply; No available router to destination
    at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:470)
    at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:402)
    at weblogic.rjvm.RJVMImpl.ensureConnectionEstablished(RJVMImpl.java:306)
    at weblogic.rjvm.RJVMImpl.getOutputStream(RJVMImpl.java:350)
    at weblogic.rjvm.RJVMImpl.getRequestStreamInternal(RJVMImpl.java:613)
    ... 30 more
    >
    I've allready ensured that the managed servers of the jms cluster are reachable by issuing a connect command from WLST (although making the connection can be time consuming)
    wls:/offline> connect('weblogic','******','t3://fsb-jms1-dev:7901')
    Connecting to t3://fsb-jms1-dev:7901 with userid weblogic ...
    Successfully connected to managed Server 'jmsms1' that belongs to domain 'jmsdevdomain'.
    Warning: An insecure protocol was used to connect to the
    server. To ensure on-the-wire security, the SSL port or
    Admin port should be used instead.
    wls:/jmsdevdomain/serverConfig> disconnect()
    Disconnected from weblogic server: jmsms1
    wls:/offline> connect('weblogic','******','t3://fsb-jms2-dev:7901')
    Connecting to t3://fsb-jms2-dev:7901 with userid weblogic ...
    Successfully connected to managed Server 'jmsms2' that belongs to domain 'jmsdevdomain'.
    Warning: An insecure protocol was used to connect to the
    server. To ensure on-the-wire security, the SSL port or
    Admin port should be used instead.
    In my search for a solution I've also read that this could be caused by a bad configured DNS server. Therefore I configured my /etc/nsswitch.conf file to contain only the property files under the parameter hosts.
    Following is an extraction of my /etc/hosts file:
    10.16.85.50 fsb-jms1-dev.localdomain fsb-jms1-dev
    10.16.85.51 fsb-jms2-dev.localdomain fsb-jms2-dev
    10.16.85.52 fsb-osb1-dev.localdomain fsb-osb1-dev
    10.16.85.53 fsb-osb2-dev.localdomain fsb-osb2-dev
    Does anybody have an idea how I can further debug this problem?
    Kind Regards,
    Davy

    Maybe this is of some help: http://www.bea-weblogic.com/namenotfoundexception-when-configuring-foreign-jms-server.html

  • Eclipse and WebLogic Ant Tasks

    In WL_HOME/server/lib/ant/ is an ant.jar. It has a "defaults.properties" containing all of the ant taskdefs. I tried to extract that so that my build.xml could use them but it keeps complaining about weblogic.ant.taskdefs.perforce.P4Changes cannot be found. The reason why is that it's under the wrong package. How does one run the weblogic ant tasks outside of the weblogic ant installation? Thanks, Jeremy

    bengali.Hi,
    you also have to include a <taskdef> for the servicegen task of >weblogicThat's why I did but I still have a problem with the source2wsdd
    ant task ( the other tasks run correctly within Eclipse).
    I get a :
    [source2wsdd] source2wsdd: Cannot find doclet class weblogic.webservice.tools.ddgen.ServiceGen
    [source2wsdd] 1 error
    BUILD FAILED: build.xml:324: javadoc execution failed
    Total time: 3 seconds
    The problem is that my source2wsdd has been defined with a well suited classpath
    and is also called with the right classpath.
    The problem only happens with this task !
    Bengali

  • Weblogic ant tasks integration in Eclipse

    Hi,
    I would like to make Weblogic ant tasks ( web services one) work in Eclipse 3.0
    . Someone on this newsgroup suggested to just add weblogic.jar and webservices.jar
    to the built-in ant classpath of Eclipse. The problem is that it doesn't work
    for me. The tasks don't run because ant doesn't recognize the tasks.
    What should I do ? If anyone has already managed to do it, please let me know.
    bengali.

    bengali.Hi,
    you also have to include a <taskdef> for the servicegen task of >weblogicThat's why I did but I still have a problem with the source2wsdd
    ant task ( the other tasks run correctly within Eclipse).
    I get a :
    [source2wsdd] source2wsdd: Cannot find doclet class weblogic.webservice.tools.ddgen.ServiceGen
    [source2wsdd] 1 error
    BUILD FAILED: build.xml:324: javadoc execution failed
    Total time: 3 seconds
    The problem is that my source2wsdd has been defined with a well suited classpath
    and is also called with the right classpath.
    The problem only happens with this task !
    Bengali

  • Weblogic ant task

    Hi all,
    I'm trying to write a build script for starting the Weblogic server, stopping it, deploy applications and delete them from server. Till now it has been done manually, like clicking the startCmd.bat for the corresponding server domain. I have specifically mentioned some memory properties in MEM_ARGS (-Xms256m -Xmx512m -XX:MaxPermSize=128m). How can one specify the same memory arguments in Weblogic Ant task (wlserver). Thanks in advance.

    Hi all,
    I'm trying to write a build script for starting the Weblogic server, stopping it, deploy applications and delete them from server. Till now it has been done manually, like clicking the startCmd.bat for the corresponding server domain. I have specifically mentioned some memory properties in MEM_ARGS (-Xms256m -Xmx512m -XX:MaxPermSize=128m). How can one specify the same memory arguments in Weblogic Ant task (wlserver). Thanks in advance.

  • Weblogic ant task wsdl2service - truncating soapaction

    Hi all,
    I'm using the weblogic ant utility "wsdl2service" to deploy my webservice. Here is the ant snippet of my script.
    <taskdef name="wsdl2service" classname="weblogic.ant.taskdefs.webservices.wsdl2service.WSDL2Service"/>
    <wsdl2service wsdl="${dev.dir}/wsdl/${myService}.wsdl" destDir="${build.dir}/wsjar"
         typeMappingFile="AutoType/in_types.xml" packageName="${in_class_packagename}" generateImpl="True">
    <classpath>
         <pathelement path="${lib3}"/>
         <pathelement path="${lib1}"/>
    <pathelement path="${lib2}"/>
         <pathelement path="AutoType/inventoryNotificationType.jar"/>
    </classpath>     
    </wsdl2service>
    It compiles properly and prepares the build. But after deploying the build, when i try to browse the wsdl thru internet browser, it is not populating the SOAPACTION attribute of SOAP:OPERATION element of my wsdl. So in the internetbroser the SOAPAction attribute is having empty value though it is present in the wsdl.
    Can some one tell why the WSDL2SERVICE tool is not populating the SOAPACTION attribute?

    Hi Jay,
    Thanks for your help.
    I am using weblogic 8.1 and Apache Ant version 1.5.3
    Jay I do not have client source code. When I am generating client using clientgen ant task, it gives me only a .jar file with .class files in it.
    I added .jar file generated by clientgen task in 'run' but now I am getting another error.
    <target name="run">
    <java classname="clientpkg.MathFace_Stub" fork="true" >
    <arg value="http://localhost:${port}/WebServices/MyFirstService?WSDL"/>
    <arg value="10"/>
    <arg value="17"/>
    <classpath>
    <pathelement location="staging"/>
    <pathelement location="${wl.home}/server/lib/weblogic.jar"/>
    <pathelement location="staging/MyFirstService_client.jar"/>
    <pathelement location="/ffdt01/resmgt/kul/ws"/>
    <pathelement path="staging"/>
    </classpath>
    </java>
    </target>
    --- This is giving below error:
    cu dmwls(162)$ ant run
    Buildfile: build.xml
    run:
    +[java] Exception in thread "main" j*ava.lang.NoSuchMethodError:* main+
    +[java] Java Result: 1+
    BUILD SUCCESSFUL
    Total time: 1 second
    Edited by: [email protected] on Feb 19, 2010 1:53 PM

  • A Tip for using EJB 3.0 with WebLogic Ant Tasks

    I started out writing this up as a problem, but then I found the answer so I'm, posting a tip instead.
    When I tried to write an EJB [stateless] using EJB 3.0 in my legacy Weblogic ear project I started getting this error:
    <pre>
    No EJBs found in the ejb-jar file 'test'. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at least one class annotated with the @Stateless, @Stateful or @MessageDriven EJB annotation.
    </pre>
    This is why: wlcompile will put the class files in the App-Inf/classes directory unless it finds an ejb-jar.xml file in the META-INF directory for the module it is working on. With EJB 3.0, I wasn't using an ejb-jar.xml file because it was unnecessary. Later, Appc runs and it complains <b>because there are no classes module directory, they went into the shared ear folder instead.</b>
    Here's I how it working again: Use javac [not wlcompile] to compile the EJB 3.0 module and make sure that the class files go into the correct module directory. Then you can use wlappc to generate all the associated files for the EJB. I have sucessfully deployed an ear file that uses both EJB 2.x and EJB 3.0 with this approach.
    I wish Weblogic's own ejb3.0 sample application used their split directory deployment.
    Good Luck.
    John Aronson

    Hi John,
    I am working on development an enterprise application using EJB 3.0 on Weblogic 10.
    While developing, I am keeping all my classes (from ejb's as well as web) into APP-INF/classes directory. It is working fine for Web and ejb 2.0 packages, but ejb 3.0 packages, I get the following error when I keep my ejb 3.0 beans classes in APP-INF/classes directory.
    No EJBs found in the ejb-jar file 'customer'. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at least one class annotated with the @Stateless, @Stateful or @MessageDriven EJB annotation.
    One solution is to keep the classes under customer ejb directory, but I wan tto keep all the classes in APP-INF/classes directory so that when using Eclipse IDE I can output all compiled sources into APP-INF/classes directory.
    Has anyone faced this situation? Any suggestions to fix this issue?

  • Setting up the environment for a WebLogic Ant task

    The documentations always starts:
    1.. On Windows NT, execute the setWLSEnv.cmd command, located in the
    directory WL_HOME\server\bin, where WL_HOME is the top-level directory of
    your WebLogic Server installation.
    2.. On UNIX, execute the setWLSEnv.sh command, located in the directory
    WL_HOME/server/bin, where WL_HOME is the top-level directory of your
    WebLogic Server installation.
    How much of what's in those bat files (or sh files on UNIX) do I actually
    need? Can I set the environment in Ant without calling the batch files --
    i.e. no system environment variables?
    TIA,
    Robert Snyder
    [email protected]

    Being a JBoss geek I cannot let it pass to recommend to at least investigate JBoss 7.1 as a possible alternative to Glassfish :)
    Also MySQL works fine and is very common and thus very much documented, which is a big plus. But I would not pass up the chance to look into PostgreSQL as well. To me that is basically the perfect balance between the simplicity of MySQL and the power of an Oracle DBMS.
    It depends on what you want to do with it of course, a simple web application works perfectly fine on MySQL, but then you probably also don't need the horsepower of a full enterprise container. You can also just use Tomcat 7 which is fast, easy to setup, well documented and doesn't use up so many resources either.

  • What is the association between JMS Server and JMS Module in weblogic 10?

    Hi,
    I have a created a ConnectionFactory, Queue, Topic under JMS Modules in Weblogic Server 10 using admin console.
    And I have created a JMS Server and Targetted to the current running server (Admin Server).
    But when I run the Queue Sender program it is unable to LookUP the jndi which I gave for Queue.
    queue = (Queue) initialContext.lookup("jndi_queue");
    Exception:
    javax.naming.NameNotFoundException: Unable to resolve 'jndi_queue'.
    But I configured this jndi name when I create the Queue in JMS Module in Weblogic Server 10.
    How JMS Module and JMS server are associated.
    My Doubt is if i have several JMS Modules and only one JMS Server created then how does the JMS Server identifies which Queue/Topic belongs to which JMS Module????
    Please advice.
    Thanks....

    Hi,
    Once you have JMS servers configured:
    Step 1: Target the JMS configuration module to the cluster that will host the destination, or, if not using clustering, target the module to the individual WL server that will host the JMS server.
    Step 2: Configure a "subdeployment" for the module and set it to reference the exact JMS server(s) that will host the destination. If you're using a distributed desitnation, you can specify multiple JMS servers, if you're using a regular destination, only specify a single destination.
    Step 3: Create a destination resource in the module, and set its subdeployment to the subdeployment you specified in step 1 (the console calls this "advanced targeting"). As a best practice avoid the "default targeting" option for the resource - always choose subdeployment (advanced) targeting.
    For more information, reference the "best practices" chapter of the JMS configuration guide:
    http://download.oracle.com/docs/cd/E14571_01/web.1111/e13738/best_practice.htm#CACJCGHG
    I also I highly recommend the JMS chapter of the book "Professional Oracle WebLogic".
    Hope this helps,
    Tom

  • Properties file not found by classloader when using wlappc ant task

    I have encountered a problem with the WebLogic Ant task "wlappc". When this task compiles a webmodule that uses the struts 1.1 framework I get the below error. This struts based web module deploys and runs fine on BEA Weblogic 8.1 SP2 as an exploded EAR structure. But when I attempt to precompile all the J2EE modules the struts web module will not compile with wlappc. The project is strutured correctly in a split directory structure. The problem area seems to be that we are using the struts-el (struts-el.jar) classes which need the properties files located in the struts.jar. The classloader seems to space out when running via the wlappc ant task. I tried adjusting the classpath via the "classpath" wlappc ant task attribute - but no success. Has anyone had this or a similiar problem?
    Any suggestions would be greatly appreciated!
    Thanks in advance,
    Scott
    Error from ant task is as such:
    compile:
    [javac] Compiling 256 source files to C:\My Builds\WWL\build\wwlentityejb
    [javac] Compiling 4 source files to C:\My Builds\WWL\build\wwlsessejb
    [javac] Compiling 91 source files to C:\My Builds\WWL\build\wwlweb\WEB-INF\classes
    appc:
    [wlappc] [appc] Compiling EAR module 'wwltestweb'
    [wlappc] [JspcInvoker]Checking web app for compliance.
    [wlappc] <Jul 28, 2004 4:38:47 PM GMT-05:00> <Info> <HTTP> <BEA-101047> <[ComplianceChecker] Validating the servlet element with servlet-name named "JUnitEETestServlet".>
    [wlappc] <Jul 28, 2004 4:38:48 PM GMT-05:00> <Info> <HTTP> <BEA-101047> <[ComplianceChecker] Checking servlet-mapping for servlet name : "JUnitEETestServlet".>
    [wlappc] [appc] Compiling EAR module 'wwlweb'
    [wlappc] [JspcInvoker]Checking web app for compliance.
    [wlappc] <Jul 28, 2004 4:38:48 PM GMT-05:00> <Info> <HTTP> <BEA-101047> <[ComplianceChecker] Validating the servlet element with servlet-name named "wwlActionServlet".>
    [wlappc] <Jul 28, 2004 4:38:48 PM GMT-05:00> <Info> <HTTP> <BEA-101047> <[ComplianceChecker] Checking servlet-mapping for servlet name : "wwlActionServlet".>
    [wlappc] <Jul 28, 2004 4:38:48 PM GMT-05:00> <Info> <HTTP> <BEA-101047> <[ComplianceChecker] Checking filter-mapping with filter-name "I18NFilter".>
    [wlappc] <Jul 28, 2004 4:38:48 PM GMT-05:00> <Info> <HTTP> <BEA-101047> <[ComplianceChecker] Checking filter-mapping with filter-name "Security Filter".>
    [wlappc] [jspc] parsing /admin/jsps/menu.jsp:
    [wlappc] Jul 28, 2004 4:38:50 PM org.apache.struts.util.MessageResourcesFactory createFactory
    [wlappc] SEVERE: MessageResourcesFactory.createFactory
    [wlappc] java.lang.ClassNotFoundException: org.apache.struts.util.PropertyMessageResourcesFactory
    [wlappc] at java.net.URLClassLoader$1.run(URLClassLoader.java:198)
    [wlappc] at java.security.AccessController.doPrivileged(Native Method)
    [wlappc] at java.net.URLClassLoader.findClass(URLClassLoader.java:186)
    [wlappc] at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
    [wlappc] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:272)
    [wlappc] at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
    [wlappc] at org.apache.struts.util.RequestUtils.applicationClass(RequestUtils.java:207)
    [wlappc] at org.apache.struts.util.MessageResourcesFactory.createFactory(MessageResourcesFactory.java:192)
    [wlappc] at org.apache.struts.util.MessageResources.getMessageResources(MessageResources.java:576)
    [wlappc] at org.apache.struts.util.RequestUtils.<clinit>(RequestUtils.java:134)
    [wlappc] at org.apache.struts.util.MessageResourcesFactory.createFactory(MessageResourcesFactory.java:192)
    [wlappc] at org.apache.struts.util.MessageResources.getMessageResources(MessageResources.java:576)
    [wlappc] at org.apache.struts.taglib.html.BaseTag.<clinit>(BaseTag.java:94)
    [wlappc] at java.lang.Class.forName0(Native Method)
    [wlappc] at java.lang.Class.forName(Class.java:140)
    [wlappc] at org.apache.strutsel.taglib.html.ELBaseTagBeanInfo.class$(ELBaseTagBeanInfo.java:81)
    [wlappc] at org.apache.strutsel.taglib.html.ELBaseTagBeanInfo.getPropertyDescriptors(ELBaseTagBeanInfo.java:81)
    [wlappc] at java.beans.Introspector.getTargetPropertyInfo(Introspector.java:436)
    [wlappc] at java.beans.Introspector.getBeanInfo(Introspector.java:372)
    [wlappc] at java.beans.Introspector.getBeanInfo(Introspector.java:207)
    [wlappc] at java.beans.Introspector.getBeanInfo(Introspector.java:193)
    [wlappc] at weblogic.servlet.jsp.StandardTagLib.parseTagDD(StandardTagLib.java:1323)
    [wlappc] at weblogic.servlet.jsp.StandardTagLib.parseDD(StandardTagLib.java:1261)
    [wlappc] at weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:292)
    [wlappc] at weblogic.servlet.jsp.TagLibHelper.loadTagLib(TagLibHelper.java:314)
    [wlappc] at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:145)
    [wlappc] at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:5015)
    [wlappc] at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:4853)
    [wlappc] at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:4699)
    [wlappc] at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:2094)
    [wlappc] at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1880)
    [wlappc] at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1753)
    [wlappc] at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:963)
    [wlappc] at weblogic.servlet.jsp.JspParser.doit(JspParser.java:106)
    [wlappc] at weblogic.servlet.jsp.JspParser.parse(JspParser.java:230)
    [wlappc] at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:125)
    [wlappc] at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258)
    [wlappc] at weblogic.jspc.runJspc(jspc.java:550)
    [wlappc] at weblogic.jspc.runJspc(jspc.java:437)
    [wlappc] at weblogic.servlet.jsp.JspcInvoker.compile(JspcInvoker.java:163)
    [wlappc] at weblogic.appc.compileWAR(appc.java:859)
    [wlappc] at weblogic.appc.compileModules(appc.java:650)
    [wlappc] at weblogic.appc.compileEAR(appc.java:733)
    [wlappc] at weblogic.appc.compileInput(appc.java:458)
    [wlappc] at weblogic.appc.runBody(appc.java:184)
    [wlappc] at weblogic.utils.compiler.Tool.run(Tool.java:146)
    [wlappc] at weblogic.utils.compiler.Tool.run(Tool.java:103)
    [wlappc] at weblogic.appc.main(appc.java:1028)
    [wlappc] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [wlappc] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [wlappc] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [wlappc] at java.lang.reflect.Method.invoke(Method.java:324)
    [wlappc] at weblogic.ant.taskdefs.j2ee.CompilerTask.invokeMain(CompilerTask.java:278)
    [wlappc] at weblogic.ant.taskdefs.j2ee.Appc.execute(Appc.java:179)
    [wlappc] at org.apache.tools.ant.Task.perform(Task.java:341)
    [wlappc] at org.apache.tools.ant.Target.execute(Target.java:309)
    [wlappc] at org.apache.tools.ant.Target.performTasks(Target.java:336)
    [wlappc] at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
    [wlappc] at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
    [wlappc] at org.apache.tools.ant.Main.runBuild(Main.java:609)
    [wlappc] at org.apache.tools.ant.Main.start(Main.java:196)
    [wlappc] at org.apache.tools.ant.Main.main(Main.java:235)
    [wlappc] Jul 28, 2004 4:38:50 PM org.apache.struts.util.MessageResourcesFactory createFactory
    [wlappc] SEVERE: MessageResourcesFactory.createFactory
    [wlappc] java.lang.ExceptionInInitializerError
    [wlappc] at org.apache.struts.util.MessageResourcesFactory.createFactory(MessageResourcesFactory.java:192)
    [wlappc] at org.apache.struts.util.MessageResources.getMessageResources(MessageResources.java:576)
    [wlappc] at org.apache.struts.taglib.html.BaseTag.<clinit>(BaseTag.java:94)
    [wlappc] at java.lang.Class.forName0(Native Method)
    [wlappc] at java.lang.Class.forName(Class.java:140)
    [wlappc] at org.apache.strutsel.taglib.html.ELBaseTagBeanInfo.class$(ELBaseTagBeanInfo.java:81)
    [wlappc] at org.apache.strutsel.taglib.html.ELBaseTagBeanInfo.getPropertyDescriptors(ELBaseTagBeanInfo.java:81)
    [wlappc] at java.beans.Introspector.getTargetPropertyInfo(Introspector.java:436)
    [wlappc] at java.beans.Introspector.getBeanInfo(Introspector.java:372)
    [wlappc] at java.beans.Introspector.getBeanInfo(Introspector.java:207)
    [wlappc] at java.beans.Introspector.getBeanInfo(Introspector.java:193)
    [wlappc] at weblogic.servlet.jsp.StandardTagLib.parseTagDD(StandardTagLib.java:1323)
    [wlappc] at weblogic.servlet.jsp.StandardTagLib.parseDD(StandardTagLib.java:1261)
    [wlappc] at weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:292)
    [wlappc] at weblogic.servlet.jsp.TagLibHelper.loadTagLib(TagLibHelper.java:314)
    [wlappc] at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:145)
    [wlappc] at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:5015)
    [wlappc] at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:4853)
    [wlappc] at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:4699)
    [wlappc] at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:2094)
    [wlappc] at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1880)
    [wlappc] at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1753)
    [wlappc] at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:963)
    [wlappc] at weblogic.servlet.jsp.JspParser.doit(JspParser.java:106)
    [wlappc] at weblogic.servlet.jsp.JspParser.parse(JspParser.java:230)
    [wlappc] at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:125)
    [wlappc] at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258)
    [wlappc] at weblogic.jspc.runJspc(jspc.java:550)
    [wlappc] at weblogic.jspc.runJspc(jspc.java:437)
    [wlappc] at weblogic.servlet.jsp.JspcInvoker.compile(JspcInvoker.java:163)
    [wlappc] at weblogic.appc.compileWAR(appc.java:859)
    [wlappc] at weblogic.appc.compileModules(appc.java:650)
    [wlappc] at weblogic.appc.compileEAR(appc.java:733)
    [wlappc] at weblogic.appc.compileInput(appc.java:458)
    [wlappc] at weblogic.appc.runBody(appc.java:184)
    [wlappc] at weblogic.utils.compiler.Tool.run(Tool.java:146)
    [wlappc] at weblogic.utils.compiler.Tool.run(Tool.java:103)
    [wlappc] at weblogic.appc.main(appc.java:1028)
    [wlappc] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [wlappc] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [wlappc] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [wlappc] at java.lang.reflect.Method.invoke(Method.java:324)
    [wlappc] at weblogic.ant.taskdefs.j2ee.CompilerTask.invokeMain(CompilerTask.java:278)
    [wlappc] at weblogic.ant.taskdefs.j2ee.Appc.execute(Appc.java:179)
    [wlappc] at org.apache.tools.ant.Task.perform(Task.java:341)
    [wlappc] at org.apache.tools.ant.Target.execute(Target.java:309)
    [wlappc] at org.apache.tools.ant.Target.performTasks(Target.java:336)
    [wlappc] at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
    [wlappc] at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
    [wlappc] at org.apache.tools.ant.Main.runBuild(Main.java:609)
    [wlappc] at org.apache.tools.ant.Main.start(Main.java:196)
    [wlappc] at org.apache.tools.ant.Main.main(Main.java:235)
    [wlappc] Caused by: java.lang.NullPointerException
    [wlappc] at org.apache.struts.util.MessageResources.getMessageResources(MessageResources.java:577)
    [wlappc] at org.apache.struts.util.RequestUtils.<clinit>(RequestUtils.java:134)
    [wlappc] ... 52 more
    BUILD FAILED
    file:C:/My Sources/WWLEar/wwlear/build.xml:128: weblogic.utils.compiler.ToolFailureException: [J2EE:160119]Appc is unable to process the file 'C:\My Builds\WWL\build'. The following error occurred:
    java.lang.ExceptionInInitializerError
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:140)
    at org.apache.strutsel.taglib.html.ELBaseTagBeanInfo.class$(ELBaseTagBeanInfo.java:81)
    at org.apache.strutsel.taglib.html.ELBaseTagBeanInfo.getPropertyDescriptors(ELBaseTagBeanInfo.java:81)
    at java.beans.Introspector.getTargetPropertyInfo(Introspector.java:436)
    at java.beans.Introspector.getBeanInfo(Introspector.java:372)
    at java.beans.Introspector.getBeanInfo(Introspector.java:207)
    at java.beans.Introspector.getBeanInfo(Introspector.java:193)
    at weblogic.servlet.jsp.StandardTagLib.parseTagDD(StandardTagLib.java:1323)
    at weblogic.servlet.jsp.StandardTagLib.parseDD(StandardTagLib.java:1261)
    at weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:292)
    at weblogic.servlet.jsp.TagLibHelper.loadTagLib(TagLibHelper.java:314)
    at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:145)
    at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:5015)
    at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:4853)
    at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:4699)
    at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:2094)
    at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1880)
    at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1753)
    at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:963)
    at weblogic.servlet.jsp.JspParser.doit(JspParser.java:106)
    at weblogic.servlet.jsp.JspParser.parse(JspParser.java:230)
    at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:125)
    at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258)
    at weblogic.jspc.runJspc(jspc.java:550)
    at weblogic.jspc.runJspc(jspc.java:437)
    at weblogic.servlet.jsp.JspcInvoker.compile(JspcInvoker.java:163)
    at weblogic.appc.compileWAR(appc.java:859)
    at weblogic.appc.compileModules(appc.java:650)
    at weblogic.appc.compileEAR(appc.java:733)
    at weblogic.appc.compileInput(appc.java:458)
    at weblogic.appc.runBody(appc.java:184)
    at weblogic.utils.compiler.Tool.run(Tool.java:146)
    at weblogic.utils.compiler.Tool.run(Tool.java:103)
    at weblogic.appc.main(appc.java:1028)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at weblogic.ant.taskdefs.j2ee.CompilerTask.invokeMain(CompilerTask.java:278)
    at weblogic.ant.taskdefs.j2ee.Appc.execute(Appc.java:179)
    at org.apache.tools.ant.Task.perform(Task.java:341)
    at org.apache.tools.ant.Target.execute(Target.java:309)
    at org.apache.tools.ant.Target.performTasks(Target.java:336)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
    at org.apache.tools.ant.Main.runBuild(Main.java:609)
    at org.apache.tools.ant.Main.start(Main.java:196)
    at org.apache.tools.ant.Main.main(Main.java:235)
    Caused by: java.lang.NullPointerException
    at org.apache.struts.util.MessageResources.getMessageResources(MessageResources.java:577)
    at org.apache.struts.taglib.html.BaseTag.<clinit>(BaseTag.java:94)
    ... 49 more
    - with nested exception:
    [java.lang.ExceptionInInitializerError]
    Total time: 42 seconds

    Hi Rob,
    I also gets this error when I deploy my application using struts 1.2.2 with struts-el.jar also.
    The error is thrown when the server comile the jsp's :
    <BEA-101047>[ServletContext(id=20164970,name=tracer,context-path=/tracer)] classfile up-to-date for JSP /webdatagrid/layouts/default/customize.jsp>
    ####<Sep 2, 2004 2:05:26 PM EDT> <Info> <HTTP> <nyeqshu2> <sit1tracerweb> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <>
    <BEA-101047> <[ServletContext(id=20164970,name=tracer,context-path=/tracer)] checking /webdatagrid/layouts/default/exceldownload.jsp:>
    ####<Sep 2, 2004 2:05:30 PM EDT> <Error> <Deployer> <nyeqshu2> <sit1tracerweb> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>>
    <>
    <BEA-149201> <Failed to complete the deployment task with ID 0 for the application tracer-webapp-application-uncontrolled.
    java.lang.NullPointerException
    at org.apache.struts.util.MessageResources.getMessageResources(MessageResources.java:577)
    at org.apache.struts.taglib.html.BaseTag.<clinit>(BaseTag.java:94)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:140)
    at org.apache.strutsel.taglib.html.ELBaseTagBeanInfo.class$(ELBaseTagBeanInfo.java:81)
    at org.apache.strutsel.taglib.html.ELBaseTagBeanInfo.getPropertyDescriptors(ELBaseTagBeanInfo.java:81)
    at java.beans.Introspector.getTargetPropertyInfo(Introspector.java:436)
    at java.beans.Introspector.getBeanInfo(Introspector.java:372)
    at java.beans.Introspector.getBeanInfo(Introspector.java:207)
    at java.beans.Introspector.getBeanInfo(Introspector.java:193)
    at weblogic.servlet.jsp.StandardTagLib.parseTagDD(StandardTagLib.java:1323)
    at weblogic.servlet.jsp.StandardTagLib.parseDD(StandardTagLib.java:1261)
    at weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:292)
    at weblogic.servlet.jsp.TagLibHelper.loadTagLib(TagLibHelper.java:314)
    at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:145)
    at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:5015)
    at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:4853)
    at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:4699)
    at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:2094)
    at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1880)
    at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1753)
    at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:963)
    at weblogic.servlet.jsp.JspParser.doit(JspParser.java:106)
    at weblogic.servlet.jsp.JspParser.parse(JspParser.java:230)
    at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:125)
    at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258)
    at weblogic.servlet.jsp.Precompiler.compileOne(Precompiler.java:191)
    at weblogic.servlet.jsp.Precompiler.compile(Precompiler.java:71)
    at weblogic.servlet.jsp.Precompiler.compile(Precompiler.java:82)
    at weblogic.servlet.internal.WebAppServletContext.precompileJSPs(WebAppServletContext.java:4908)
    at weblogic.servlet.internal.WebAppServletContext.precompileJSPs(WebAppServletContext.java:4886)
    at weblogic.servlet.internal.WebAppServletContext.prepareFromDescriptors(WebAppServletContext.java:2342)
    at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:565)
    at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:493)
    at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:628)
    at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:626)
    at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3011)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1532)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
    at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2602)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2552)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2474)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    --------------- nested within: ------------------
    weblogic.management.ManagementException: - with nested exception:
    [java.lang.NullPointerException]
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2491)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    >
    ####<Sep 2, 2004 2:37:29 PM EDT> <Info> <Deployer> <nyeqshu2> <sit1tracerweb> <ExecuteThread: '2' for queue: 'weblogic.kernel.System'> <<WLS Kernel>>
    <>
    <BEA-149059> <Module tracer of application tracer-webapp-application-1_6_3_510 is transitioning from unprepared to prepared on server sit1tracerweb
    .>
    ####<Sep 2, 2004 2:37:39 PM EDT> <Debug> <HTTP> <nyeqshu2> <sit1tracerweb> <ExecuteThread: '2' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <>
    ####<Sep 2, 2004 2:37:39 PM EDT> <Debug> <HTTP> <nyeqshu2> <sit1tracerweb> <ExecuteThread: '2' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <>
    <BEA-101211> <tracer-webapp-application-1_6_3_510:tracer Precompiling JSPs at startup with JSP config [JspConfig: verbose=true,packagePrefix=jsp_servl
    et,-compiler=javac,compileFlags=,workingDir=./applications/tracer/WEB-INF/classes,pageCheckSeconds=5,superclass=weblogic.servlet.jsp.JspBase,keepgener
    ated=true,precompileContinue=false,compilerSupportsEncoding=true,encoding=null,defaultfilename=index.jsp,compilerclass=null,noTryBlocks=true,debugEnab
    led=false,printNulls=true,jspServlet=null].>
    I've looked at the source code ant it is actually using the current thread's classloader.
    The fact is that it works fine when deployed to tomcat 4.1.30, but it fails when deploying on our weblogic managed servers.
    Thanks
    Julien De Santis
    CGI Group

  • Using wsdlc Ant task and Eclipse

    Hi all,
    I'm using the WebLogic Ant Task wsdlc to generate a default implementation of a java web service based on an existing WSDL.
    Everythign generates just fine. I have one little problem though: the classes that represent some of the complex types defined in the WSDL are generated in the compiled WSDL file (the JAR file that wsdlc creates). If I open the java source file for the web service (also created by the wsdlc task, but NOT in the compiled wsdl jar) with Eclipse, Eclipse cannot find the source code for those complex types, and therefore underlines the data types in red to indicate an error.
    My question is this: is there a way to tell Eclipse to look for additional source files inside of the compiled wsdl.jar file?
    Many thanks in advance!
    Jeff

    I got around this by unjaring the generated source jar into a "generated/src" directory and put that directory on the build path.
    Andy O

  • Problem with WebLogic- Oracle AQ Foreign JMS server.

    I'm trying to create a JMS module in WebLogic pointing at an Oracle AQ queue in another database.  I've got a datasource, module, and queue according to the documentation (I believe). 
    I followed: http://docs.oracle.com/cd/E24329_01/web.1211/e24385/aq_jms.htm#CJAECHCC
    although, I did fix the syntax errors in the SQL, and I used smf instead of jmsuser.
    However, when I deploy a MDB that uses the queue, I get the following exception:
    weblogic.jms.common.InvalidDestinationException: [JMSClientExceptions:055142]Foreign destination, SMF.USERQUEUE
      at weblogic.jms.common.Destination.checkDestinationType(Destination.java:105)
      at weblogic.jms.client.JMSSession.setupConsumer(JMSSession.java:2720)
      at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:2691)
      at weblogic.jms.client.JMSSession.createReceiver(JMSSession.java:2596)
      at weblogic.ejb.container.internal.JMSConnectionPoller.setUpQueueSessionAt(JMSConnectionPoller.java:1791)
      at weblogic.ejb.container.internal.JMSConnectionPoller.setUpQueueSessions(JMSConnectionPoller.java:1618)
      at weblogic.ejb.container.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:2298)
      at weblogic.ejb.container.internal.JMSConnectionPoller.connect(JMSConnectionPoller.java:808)
      at weblogic.ejb.container.internal.MDConnectionManager.timerExpired(MDConnectionManager.java:177)
      at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:293)
      at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    The JDBC data source is connected properly.
    JNDI IC: oracle.jms.AQjmsInitialContextFactory
    ConnectionFactory Local: aqjms/XAQueueConnectionFactory Remote: QueueConnectionFactory
    Destination Local: aqjms/sdcCompilerQueue Remote: Queues/USERQUEUE
    Data Source: jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=SMF)(INSTANCE_NAME=SMF)))
    Supports Global Transactions - DISABLED.
    Data Source Test: SQL SELECT count(*) FROM myqueuetable  -- validates that the queue table exists.
    Oracle WebLogic 12c, Oracle EE 11gR2 on OEL 6.4.
    Any ideas?  We're stumped here.
    Thank you

    The problem was that the MDB wasn't specifying the connection factory.  It needed some more annotations:
    @MessageDriven(name = "MDBName",
            mappedName = "aqjms/mdbQueue",
            activationConfig = {
                    @ActivationConfigProperty(propertyName="connectionFactoryJndiName",
                            propertyValue="aqjms/QueueConnectionFactory"

  • Edit of Foreign JMS module in admin console causes redeployment error

    A JMS module (-jms.xml) for a foreign JMSServer specifies the url of the real JMS server. I am trying to use a deployment plan to make this url a deployment property.
    Following the instructions in "Configuring and Managing Weblogic JMS" and "Deploying Applications to Weblogic Server", I have deployed the module with a fixed URL, and then attempt to edit the url in the admin console. The admin console correctly creates a deployment plan to hold modified value, but then can't redeploy the module due to errors during deployment.
    I experience these errors with the module deployed stand-alone, or when bundled with my enterprise application. I also get the same error if I produce the deployment plan using the PlanGenerator.
    The error seems to be a bug in the deployment plan machinery, since the xpath it produces for the variable-application does not match the xml schema for <weblogic-jms>. The plan.xml refers to "/weblogic-jms/foreign-server[name="IQN_OLTP_FOREIGN_JMS_Server"]/connectionurl" while the schema defines "/weblogic-jms/foreign-server/connection-url".
    Any advice would be welcome.
    We are running 9.2 SP3.
    The messages in the admin console logs are:
    ####<Jan 22, 2009 12:07:02 PM MST> <Info> <J2EE> <truman> <IQN_ADMIN_SERVER> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (
    self-tuning)'> <system> <> <> <1232651222010> <BEA-160166> <References were found in deployment plan for module 'IQN_JMS_OLTP_FOREIGN-jms.xml'
    with uri, '.'. The plan was merged.>
    ####<Jan 22, 2009 12:07:02 PM MST> <Error> <J2EE> <truman> <IQN_ADMIN_SERVER> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default
    (self-tuning)'> <system> <> <> <1232651222024> <BEA-160197> <Unable to load descriptor weblogic.deploy.api.spi.config.DescriptorParser$1@1c7654
    8 finder: weblogic.utils.classloaders.CodeGenClassFinder@1ca6109 annotation: /. of module IQN_JMS_OLTP_FOREIGN-jms.xml. The error is weblogic.d
    escriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
    problem: cvc-complex-type.2.4a: Expected elements 'jndi-properties-credential-encrypted@http://www.bea.com/ns/weblogic/90 jndi-property@http:
    //www.bea.com/ns/weblogic/90' instead of 'default-targeting-enabled@http://www.bea.com/ns/weblogic/90' here in element foreign-server@http://ww
    w.bea.com/ns/weblogic/90:<null>
    problem: cvc-complex-type.2.4a: Expected elements 'jndi-properties-credential-encrypted@http://www.bea.com/ns/weblogic/90 jndi-property@http:
    //www.bea.com/ns/weblogic/90' instead of 'foreign-destination@http://www.bea.com/ns/weblogic/90' here in element foreign-server@http://www.bea.
    com/ns/weblogic/90:<null>
    problem: cvc-complex-type.2.4a: Expected elements 'jndi-properties-credential-encrypted@http://www.bea.com/ns/weblogic/90 jndi-property@http:
    //www.bea.com/ns/weblogic/90' instead of 'foreign-destination@http://www.bea.com/ns/weblogic/90' here in element foreign-server@http://www.bea.
    com/ns/weblogic/90:<null>
    problem: cvc-complex-type.2.4a: Expected elements 'jndi-properties-credential-encrypted@http://www.bea.com/ns/weblogic/90 jndi-property@http:
    //www.bea.com/ns/weblogic/90' instead of 'foreign-connection-factory@http://www.bea.com/ns/weblogic/90' here in element foreign-server@http://w
    ww.bea.com/ns/weblogic/90:<null>
    problem: cvc-complex-type.2.4a: Expected elements 'jndi-properties-credential-encrypted@http://www.bea.com/ns/weblogic/90 jndi-property@http:
    //www.bea.com/ns/weblogic/90' instead of 'foreign-connection-factory@http://www.bea.com/ns/weblogic/90' here in element foreign-server@http://w
    ww.bea.com/ns/weblogic/90:<null>
    /home/jbullock/development/patch841/domains/IQN/nullplan.xml:0: problem: cvc-complex-type.2.4a: Expected elements 'jndi-properties-credential
    -encrypted@http://www.bea.com/ns/weblogic/90 jndi-property@http://www.bea.com/ns/weblogic/90' instead of 'connectionurl@http://www.bea.com/ns/w
    eblogic/90' here in element foreign-server@http://www.bea.com/ns/weblogic/90:<nullplan.xml>

    I also tried this, without success. Changing the deployment plan to use the element name "connection-url" leads to a different error during deployment:
    <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, IQN_JMS_OLTP_FOREIGN [archive: ../../package/jms/IQN_JMS_OLTP_FOREIGN-jms.xml], to IQN_BATCH IQN_OLTP1 .>
    plan xpath defines an element [connection-url] that is not valid!(There is also a subtle variation in the xpath used in the deployment plan: It isn't clear whether the deployer expects /weblogic-jms/foreign-server/[name="IQN_OLTP_FOREIGN_JMS_Server"]/connection-url or /weblogic-jms/foreign-server[name="IQN_OLTP_FOREIGN_JMS_Server"]/connectionurl. The former, although not really correct XPath syntax, seems to be required for other elements, but in this case, the PlanGenerator emits latter, which is correct XPath, but has the wrong element name.)
    Edited by: John Bullock on Jan 26, 2009 11:59 AM

  • MDB not connecting to Foreign JMS destination

    I'm running WL 9.2 MP3 on Windows machine. I'm deploying a rudimentary MDB congured against as Foreign Service JMS provider against MQ V6.0 with local queue running on the same local machine.
              I'm using Maven2 to build all the sub-projects - including my ejb project and enterprise application project. The EAR file deploys successfully without any errors (one minor warning about lack of explicity transactionsi in onMessage() method...). I don't see any errors but my MDB Connection Status is "disconnected" - I've enabled Debug for key sections under default and weblogic sections - still not errors of any kind but it does not connect! What can I do to find the problem?!
              Here is my EJB definition:
              public class AnotherBean extends GenericMessageDrivenBean implements
                        MessageDrivenBean, MessageListener {
                   private static final long serialVersionUID = 1L;
                   /* When the bean is activated, this method will be invoked
                   * @see javax.jms.MessageListener#onMessage(javax.jms.Message)
                   public void onMessage(Message msg) {
                        System.out.println("\n=========================================");
                        System.out.println("=> Message received!");
                        if (msg instanceof TextMessage) {
                             try {
                                  System.out.println("=> Message: "
                                            + ((TextMessage) msg).getText());
                             } catch (JMSException e) {
                                  e.printStackTrace();
                        // Place the message on to the reply queue (WLReplyQueue)
                        System.out.println("=========================================");
              Here is my ejb-jar.xml:
              <ejb-jar
              xmlns="http://java.sun.com/xml/ns/j2ee"
              xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
              xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd"
              version="2.1">
              <enterprise-beans>
              <message-driven>
              <ejb-name>AnotherBean</ejb-name>
              <ejb-class>com.ibm.myclient.gems.ejb.AnotherBean</ejb-class>
              <transaction-type>Container</transaction-type>
              <activation-config>
              <activation-config-property>
              <activation-config-property-name>destinationType</activation-config-property-name>
              <activation-config-property-value>javax.jms.Queue</activation-config-property-value>
              </activation-config-property>
              </activation-config>
              </message-driven>
              </enterprise-beans>
              </ejb-jar>
              Here is my weblogic-ejb-jar.xml:
              <weblogic-ejb-jar
              xmlns="http://www.bea.com/ns/weblogic/90" xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd">
              <weblogic-enterprise-bean>
              <ejb-name>AnotherBean</ejb-name>
              <message-driven-descriptor>
              <destination-jndi-name>jms/WLReceiverQueue</destination-jndi-name>
              <connection-factory-jndi-name>jms/WLReceiverQCF</connection-factory-jndi-name>
              </message-driven-descriptor>
              </weblogic-enterprise-bean>
              </weblogic-ejb-jar>
              WL JMS module is setup like this:
              <weblogic-jms xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schema
              Location="http://www.bea.com/ns/weblogic/920 http://www.bea.com/ns/weblogic/920.xsd">
              <foreign-server name="MQTestForeignServer">
              <default-targeting-enabled>true</default-targeting-enabled>
              <foreign-destination name="ReceiverDetails">
              <local-jndi-name>jms/WLReceiverQueue</local-jndi-name>
              <remote-jndi-name>MQSenderQueue</remote-jndi-name>
              </foreign-destination>
              <foreign-destination name="ReplyDetails">
              <local-jndi-name>jms/WLReplyQueue</local-jndi-name>
              <remote-jndi-name>MQReceiverQueue</remote-jndi-name>
              </foreign-destination>
              <foreign-connection-factory name="ReceiverCF">
              <local-jndi-name>jms/WLReceiverQCF</local-jndi-name>
              <remote-jndi-name>MQSenderQCF</remote-jndi-name>
              </foreign-connection-factory>
              <foreign-connection-factory name="ReplyCF">
              <local-jndi-name>jms/WLReplyQCF</local-jndi-name>
              <remote-jndi-name>MQReceiverQCF</remote-jndi-name>
              </foreign-connection-factory>
              <initial-context-factory>com.sun.jndi.fscontext.RefFSContextFactory</initial-context-factory>
              <connection-url>file:/ C:/JNDI-Directory</connection-url>
              </foreign-server>
              </weblogic-jms>

    Thanks for the tips - I solved the problem. I first recreated my .bindinds file making sure that both QCF objects are in there (it turned out that only ONE of them was there and not the other). Next, I also removed an extra space " " from the URL reference in the Foreign JMS service setup in the console:
              was like this initially:
              <connection-url>file:/ C:/JNDI-Directory</connection-url>
              and I changed it to this - removing single space after first "/":
              <connection-url>file:/C:/JNDI-Directory</connection-url>
              Restarted the whole thing and it worked! Thanks again.

  • Setting up Foreign JMS Dest. to MQ: JMS Destination not found

    I'm trying to set up a foreign JMS destination to an MQ queue. There are several steps you have to get right for this to work. I thought I did them all correctly, but when I deploy the app with an MDB that references the JNDI name, it says (in the console) that the destination with the particular JNDI name could not be found.
              I first used JMSAdmin to create the JNDI data in the provider URL file location. I created the qcf and the queue. I've displayed my results that I set with that, and it all looks fine. One thing that I'm unsure about with this, however, is that the document on using JMSAdmin doesn't make it clear exactly which field in the "queue" definition is the JNDI name, and which is the MQ queue name. My guess is that the value of the "q" field is the JNDI name, and the value of the "queue" field is the MQ queue name. I'm not certain.
              I then created the foreign JMS info in the WebLogic console. I first created the foreign JMS server, using the "RefFSContextFactory" class, and my file location for the provider URL.
              I then created the foreign JMS ConnectionFactory, specifying my JNDI name in both the "local" and "remote" fields. I don't know what the difference is between those two. I did NOT enter a value in the "User Name" or "Password" fields. I don't know whether that's an issue.
              I then created the foreign JMS destination. I set the "local" and "remote" JNDI values to the JNDI value I set in the "q" field in JMSAdmin.
              I then defined an app using an MDB, with the "destination-jndi-name" set to the same value I set in the "q" field.
              When I deployed the app, I saw an error message on the console saying that when deploying the EJB module, the JNDI name (that I had specified in the "q" field) could not be found.

    David,
              first you should check, whether the JNDI-Entry is deployed. You can
              check this by displaying the jndi-tree on the weblogic console. to do
              this, right click on the server entry and select "view jndi tree".
              the point with the jndi-tree you entered as "local jndi destination"
              should be violet.
              in the definitions of foreign jms-destinations and connection factories
              you always set:
              remote jndi name: the entry which you made in JMSADMIN
              local jndi name: the jndi entry you want to use inside weblogic.
              hope this helps,
              Klaas
              David Karr schrieb:
              > I'm trying to set up a foreign JMS destination to an MQ queue. There are several steps you have to get right for this to work. I thought I did them all correctly, but when I deploy the app with an MDB that references the JNDI name, it says (in the console) that the destination with the particular JNDI name could not be found.
              >
              > I first used JMSAdmin to create the JNDI data in the provider URL file location. I created the qcf and the queue. I've displayed my results that I set with that, and it all looks fine. One thing that I'm unsure about with this, however, is that the document on using JMSAdmin doesn't make it clear exactly which field in the "queue" definition is the JNDI name, and which is the MQ queue name. My guess is that the value of the "q" field is the JNDI name, and the value of the "queue" field is the MQ queue
              > name. I'm not certain.
              >
              > I then created the foreign JMS info in the WebLogic console. I first created the foreign JMS server, using the "RefFSContextFactory" class, and my file location for the provider URL.
              >
              > I then created the foreign JMS ConnectionFactory, specifying my JNDI name in both the "local" and "remote" fields. I don't know what the difference is between those two. I did NOT enter a value in the "User Name" or "Password" fields. I don't know whether that's an issue.
              >
              > I then created the foreign JMS destination. I set the "local" and "remote" JNDI values to the JNDI value I set in the "q" field in JMSAdmin.
              >
              > I then defined an app using an MDB, with the "destination-jndi-name" set to the same value I set in the "q" field.
              >
              > When I deployed the app, I saw an error message on the console saying that when deploying the EJB module, the JNDI name (that I had specified in the "q" field) could not be found.

Maybe you are looking for