.ear re-deploy problem

I am using WL 7. I have deployed my message driven bean in an ear file. However,
when I made changes in the bean (adding some debug statements) and redeploy the
.ear file with my mdb's newest jar, weblogic still uses the old version of the
mdb jar. I tried undeploy/redeploying the .ear file, it did not help. I restarted
the server, that did not help either. Is there some where in WL 7, that sometimes
the classes/jars gets cached? Any suggestions?

I suspect you have an older version of this class in the $CLASSPATH.
-- Rob
Pokharel wrote:
I tried, but this still does not work. And I can not tell where weblogic is finding
the old classes from. To be safe, can I delete any other directories that would
clear the problem?
Thanks
Rob Woollen <[email protected]> wrote:
That shouldn't happen.
How are you deploying the application? via the applications directory?
A quick fix might be to shutdown the server, remove teh contents of the
..wlnotdelete directory and then proceed.
If that doesn't work, then I suspect that you have an older copy of the
changed class in the classpath.
-- Rob
Pokharel wrote:
I am using WL 7. I have deployed my message driven bean in an ear file.However,
when I made changes in the bean (adding some debug statements) andredeploy the
ear file with my mdb's newest jar, weblogic still uses the old versionof the
mdb jar. I tried undeploy/redeploying the .ear file, it did not help.I restarted
the server, that did not help either. Is there some where in WL 7,that sometimes
the classes/jars gets cached? Any suggestions?

Similar Messages

  • Wl 8.1 sp1 .ear file deployment problems

    I am Unable to deploy ear file in WL8.1 SP1. See the error below..
    This ear fie is successfully deployed on WL6.1 SP3
    IF i remove the componenet on which this error is thrown, the same error appears
    on other componenet...
    Can somebody explain what would cause this?
    Exception thrown is:-->
    Exception:weblogic.management.ApplicationException: prepare failed for MorningMDB.jar104
    Module: MorningMDB.jar104 Error: Exception preparing module: EJBModule(MorningMDB.jar104,status=NEW)
    Unable to deploy EJB: MorningMDB from MorningMDB.jar: [EJB:011026]The EJB container
    failed while creating the java:/comp/env namespace for this EJB deployment. javax.naming.NameAlreadyBoundException:
    UserTransaction is already bound; remaining name 'app/ejb/MorningMDB/jar#MorningMDB/comp'
    at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:333) at
    weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:291) at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:298)
    at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:359) at weblogic.ejb20.deployer.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:619)
    at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentContext(EJBDeployer.java:385)
    at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentFor(EJBDeployer.java:1110)
    at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:922) at
    weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1283) at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:477)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2847)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1534)
    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:2634)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2584)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2506)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:833)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:542)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
    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)
    5. The LOg of Activities:-->
    [Deployer:149033]preparing application lpapp on wls1
    [Deployer:149033]failed application lpapp on wls1
    [Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application
    lpapp on wls1.:
    Exception:weblogic.management.ApplicationException: prepare failed for MorningMDB.jar104
    Module: MorningMDB.jar104 Error: Exception preparing module: EJBModule(MorningMDB.jar104,status=NEW)
    Unable to deploy EJB: MorningMDB from MorningMDB.jar:
    [EJB:011026]The EJB container failed while creating the java:/comp/env namespace
    for this EJB deployment.
    javax.naming.NameAlreadyBoundException: UserTransaction is already bound; remaining
    name 'app/ejb/MorningMDB/jar#MorningMDB/comp'
    at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:333)
    at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:291)
    at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:298)
    at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:359)
    at weblogic.ejb20.deployer.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:619)
    at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentContext(EJBDeployer.java:385)
    at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentFor(EJBDeployer.java:1110)
    at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:922)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1283)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:477)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2847)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1534)
    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:2634)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2584)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2506)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:833)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:542)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
    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)

    I can give you the skeleton..
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EE Application
    1.2//EN' 'http://java.sun.com/j2ee/dtds/application_1_2.dtd'>
    <application>
    <display-name>Application</display-name>
    <description>Application description</description>          
    <module>
         <web>
              <web-uri>mywar.war</web-uri>
              <context-root>mywar</context-root>
              </web>
    </module>
         <module>
              <ejb>myejbs.jar</ejb>
    </module>
    </application>
    "skv" <[email protected]> wrote:
    >
    Unfortunately I can't.
    But I can answer your questions. I have also open a case with bea and
    so far no
    luck.
    Also the ear file take an awful lot of time to deploy. THe ear file
    I have currently
    contains 106 jar file (ejb's) and the deployment continues forever (>
    than 25
    minutes) and the status in console Shows 'In progress'
    Rob Woollen <[email protected]> wrote:
    Strange. Can you show me the contents of your EAR file (ie the file
    layout) and your application.xml?
    -- Rob
    skv wrote:
    I am Unable to deploy ear file in WL8.1 SP1. See the error below..
    This ear fie is successfully deployed on WL6.1 SP3
    IF i remove the componenet on which this error is thrown, the sameerror appears
    on other componenet...
    Can somebody explain what would cause this?
    Exception thrown is:-->
    Exception:weblogic.management.ApplicationException: prepare failedfor MorningMDB.jar104
    Module: MorningMDB.jar104 Error: Exception preparing module: EJBModule(MorningMDB.jar104,status=NEW)
    Unable to deploy EJB: MorningMDB from MorningMDB.jar: [EJB:011026]TheEJB container
    failed while creating the java:/comp/env namespace for this EJB deployment.javax.naming.NameAlreadyBoundException:
    UserTransaction is already bound; remaining name 'app/ejb/MorningMDB/jar#MorningMDB/comp'
    at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:333)at
    weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:291)at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:298)
    at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:359)at weblogic.ejb20.deployer.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:619)
    at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentContext(EJBDeployer.java:385)
    at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentFor(EJBDeployer.java:1110)
    at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:922)at
    weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1283)at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:477)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2847)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1534)
    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:2634)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2584)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2506)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:833)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:542)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) atweblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    5. The LOg of Activities:-->
    [Deployer:149033]preparing application lpapp on wls1
    [Deployer:149033]failed application lpapp on wls1
    [Deployer:149034]An exception occurred for task [Deployer:149026]Deployapplication
    lpapp on wls1.:
    Exception:weblogic.management.ApplicationException: prepare failedfor MorningMDB.jar104
    Module: MorningMDB.jar104 Error: Exception preparing module: EJBModule(MorningMDB.jar104,status=NEW)
    Unable to deploy EJB: MorningMDB from MorningMDB.jar:
    [EJB:011026]The EJB container failed while creating the java:/comp/envnamespace
    for this EJB deployment.
    javax.naming.NameAlreadyBoundException: UserTransaction is alreadybound; remaining
    name 'app/ejb/MorningMDB/jar#MorningMDB/comp'
    at weblogic.jndi.internal.BasicNamingNode.bindHere(BasicNamingNode.java:333)
    at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:291)
    at weblogic.jndi.internal.BasicNamingNode.bind(BasicNamingNode.java:298)
    at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:359)
    at weblogic.ejb20.deployer.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:619)
    at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentContext(EJBDeployer.java:385)
    at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentFor(EJBDeployer.java:1110)
    at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:922)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1283)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:477)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2847)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1534)
    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:2634)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2584)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2506)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:833)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:542)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
    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)

  • War an ear deployment problem

    hi,
    I got a war and ear that share common classes. I would like to deploy both of them on the same application server.
    I started with weblogic and it worked fine.
    Now I am running it on Websphere - the problem is the ear application failed to start - it cant find one of it's property files even though it is in the class path.
    I see that the jar containing all the properties is in the class path - the application can access all other properties files except this one.
    The problematic properties file is my.commons.logging.properties which is a refactoring to the common.logging jar.
    I also see that if the war is not deployed - the ear is deployed without a problem.
    the war contains commons.logging.properties and because Websphere also had it's own common.logging i had to use "parent last" for the war deployment.
    If i change the load order of the applications(the ear is loaded first) - the properties file is found.
    I will be happy to hear any idea you got about this.
    I don�t understand how two different applications affect each other that way.
    Thanks!!!

    Sounds like a bug. You can report it to [email protected]
    -- Rob

  • Deployment problems EAR & WAR

    I have serious problems deploying an EAR, containing 25 ejb-jars and 3 wars.
    The history of the project is that it was first developed on WLS 4.5 & 5.1. We
    have later moved to Orion were the actual development takes place. Now we can
    run the application on Orion and WLS 5.1. We now want to deploy the application
    on WLS 6.1 sp 2. We have setup the whole application to be deployed as one EAR,
    this works fine with Orion. The whole building is made in Ant.
    I'm new on WLS 6.1 but have worked a lot on WLS 5.1 and 4.5 (I think it was).
    I might have missed something but the documentation on EAR is very short.
    When I first deploy the EAR, it seemed to work fine according to the console,
    however when I tried to access servlets or JSPs, they simply weren't there (Error
    404--Not Found). When I deployed the EAR from the console I got a number of zipexceptions.
    After asking around, I was recommended to remove the compression in the jar,war
    & earfiles. When I did that I got a number of errors in static initializers in
    EJBs, which indicated that the EJBs actually were deployed. I fixed those and
    the application was deployed without errors (when I start WLS and the EAR is deployed
    by being in the config.xml file). Still when I deploy it from the console it still
    throws ZipExceptions.
    Anyway now I can access one of the war files but the other is not there. The deployed
    war file is a lot smaller than the one not being deployed.
    I think that all settings in application.xml, web.xml etc is correct. I'm also
    confident that modules are correct, it does work in Orion, which has similar classloading.
    From other developers, I have heard that I need to use WLS 6.1 sp 2, no compression
    and that I have to break up large EARs in smaller (my EAR is 6,5 MB) files.
    What really annoys me that I do not seem to get any errors, logs or anything.
    The console indicates that everything is deployed even if apparently is not.
    And I can deploy PerStore and everything works. If I deploy the wars, and ejbs
    from the console (one at a time), it works.
    I would appreciate any help on this subject any workarounds etc. I think that
    I have to skip my first intent and deploy an exploded EAR instead of having (almost)
    the same deployement as in Orion, which kind of pisses me of. I am also disappointed
    that BEA has apperantly skipped java-modules all together. It is after all in
    the specification.
    I have talked to a number of people and they say that the whole EAR deployment
    in WLS is very shaky. Is this true?
    Thanks in advance,
    Erik Romson

    EAR deployment works fine from my own experience. Use JAR and turn off
    compression for the WARs and JARs and the EAR itself, although I've never
    seen a ZIP exception and I use JAR and ZIP and Winzip and whatever else I
    can grab to muck with the files. 6.5MB is not tiny, but it isn't very large
    either -- WL can handle much bigger EARs. Normally we don't suggest having
    so many JARs and WARs in the EAR, but that is more preference ... are you
    using manifest class path? ... are you referring to any of the files in the
    WARs from any of the classes in the JARs?
    Peace,
    Cameron Purdy
    Tangosol, Inc.
    Clustering Weblogic? You're either using Coherence, or you should be!
    Download a Tangosol Coherence eval today at http://www.tangosol.com/
    "Erik Romson" <[email protected]> wrote in message
    news:[email protected]...
    >
    I have serious problems deploying an EAR, containing 25 ejb-jars and 3wars.
    The history of the project is that it was first developed on WLS 4.5 &5.1. We
    have later moved to Orion were the actual development takes place. Now wecan
    run the application on Orion and WLS 5.1. We now want to deploy theapplication
    on WLS 6.1 sp 2. We have setup the whole application to be deployed as oneEAR,
    this works fine with Orion. The whole building is made in Ant.
    I'm new on WLS 6.1 but have worked a lot on WLS 5.1 and 4.5 (I think itwas).
    I might have missed something but the documentation on EAR is very short.
    When I first deploy the EAR, it seemed to work fine according to theconsole,
    however when I tried to access servlets or JSPs, they simply weren't there(Error
    404--Not Found). When I deployed the EAR from the console I got a numberof zipexceptions.
    After asking around, I was recommended to remove the compression in thejar,war
    & earfiles. When I did that I got a number of errors in staticinitializers in
    EJBs, which indicated that the EJBs actually were deployed. I fixed thoseand
    the application was deployed without errors (when I start WLS and the EARis deployed
    by being in the config.xml file). Still when I deploy it from the consoleit still
    throws ZipExceptions.
    Anyway now I can access one of the war files but the other is not there.The deployed
    war file is a lot smaller than the one not being deployed.
    I think that all settings in application.xml, web.xml etc is correct. I'malso
    confident that modules are correct, it does work in Orion, which hassimilar classloading.
    >
    From other developers, I have heard that I need to use WLS 6.1 sp 2, nocompression
    and that I have to break up large EARs in smaller (my EAR is 6,5 MB)files.
    >
    What really annoys me that I do not seem to get any errors, logs oranything.
    The console indicates that everything is deployed even if apparently isnot.
    >
    And I can deploy PerStore and everything works. If I deploy the wars, andejbs
    from the console (one at a time), it works.
    I would appreciate any help on this subject any workarounds etc. I thinkthat
    I have to skip my first intent and deploy an exploded EAR instead ofhaving (almost)
    the same deployement as in Orion, which kind of pisses me of. I am alsodisappointed
    that BEA has apperantly skipped java-modules all together. It is after allin
    the specification.
    I have talked to a number of people and they say that the whole EARdeployment
    in WLS is very shaky. Is this true?
    Thanks in advance,
    Erik Romson

  • RE: [iPlanet-JATO] Re: Deployment problem

    Chidu,
    I think that you are mired in the very common confusion of the default
    behavior of the ApplicationServletBase.parsePathInfo() which will determine
    the controlling/handling ViewBean via a URL design pattern. Lets take a look
    at the URL
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp
    is decomposed as follows:
    /NASApp -> well, this is long story but is absolutely necessary, welcome to
    iAS
    /MigtoolboxSampleAppWar -> is the web application name, taken as the name of
    the WAR file when there is no EAR file (this allows the Servlet/JSP
    container to deferences the web application root under
    <ias>/APPS/modules/MigtoolboxSampleAppWar) I think this part of the URL is
    called th Context Path
    /MigtoolboxSample -> is the Servlet Path, and will either directly reference
    or match a Servlet Mapping
    for instance
    <servlet-mapping>
    <servlet-name>MigtoolboxSampleServlet</servlet-name>
    <url-pattern>/MigtoolboxSample/*</url-pattern>
    </servlet-mapping>
    tells the Servlet Container that the Servlet Path
    /MigtoolboxSample
    maps to the Module Servlet MigtoolboxSampleServlet
    This is how EVERY request makes its way to the "front controller" pattern in
    JATO. It is fundamental to JATO Applicatioan that every request pass
    through the ModuleServlet.
    every else on the URL past the Servlet Path is the PATH INFO. Based on this
    understanding, you will see why the
    ApplicationServletBase.parsePathInfo()
    is so important. In parsePathInfo() the PATH INFO is compared to the design
    pattern
    /VIEWBEANNAME*
    to determine the handling ViewBean from the first String Token in the path
    info. For instance, the starting URL of the Sample Application is
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage
    The PATH INFO is [IndexPage]
    and IndexPage[ViewBean] is the handling ViewBean. Therefore, any simiarl
    URL like
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.matt
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.mike
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.chidu
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.XXX
    will all result in the same handling View Bean
    IndexPageViewBean
    It is very important to understand that you CANNOT hit the JATO JSPs
    directly. You must hit the "front controller" ModuleServlet which will
    always delegate control to the handling ViewBean (a la, the "service to
    workers" pattern)
    You can attempt to hit the JSP directly but you need the right J2EE URL
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSampleApp/MigtoolboxSample/IndexPag
    e.jsp
    this URL will directly hit the JSP. However, you will recieve an error
    because the JATO framework quickly determines that there is no
    RequestContext in the HttpRequest attributes and assumes that the "front
    controller" was bypassed. Try it. You will get ERROR.
    Lets go back to what you are trying to do, place Models and Viewbeans in
    separate directories. I recommend that you move the Models. Models are
    ONLY referenced by TYPE via the ModelManager, the compiler will ensure that
    your code is correct and matches the packages, file locations, import
    statements, etc. ViewBeans, on the other hand are related to the
    ModuleServlet their are contained in and are loaded via type names according
    to a design pattern.
    if you want to separate models and Viewbean then simply move the Model and
    make sure everything compiles.
    you cannot move the ViewBeans
    if you do want to move the JSP peers of the Viewbeans, then you can put them
    anywhere in the web application doc root. When you do, update the
    DEFAULT_DISPLAY_URL as Mike suggested
    matt
    -----Original Message-----
    From: Mike Frisino [mailto:<a href="/group/SunONE-JATO/post?protectID=174176219122158198138082063148231088239026066196217193234150166091061">Michael.Frisino@S...</a>]
    Sent: Thursday, July 26, 2001 10:48 PM
    Subject: Re: [iPlanet-JATO] Re: Deployment problem
    Chidu,
    Did you have it running fine in the original default configuration, before
    you started changing things around? The URL should not access the .jsp
    directly. The URL should look more like this
    "/NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage", without the
    .jsp.
    Also, please read the "Migration Tech Notes" document that is
    linked to the
    main doc index page. There is some information in there related
    to trying to
    run the sample application under iAS (see Tech Note 4 in
    particular, "Note
    on running the iMT "MigtoolboxSample" in iPlanet Application Server )
    ----- Original Message -----
    From: <<a href="/group/SunONE-JATO/post?protectID=219015020150194233215218164140244063078048234051197">chidusv@y...</a>>
    Sent: Thursday, July 26, 2001 7:27 PM
    Subject: [iPlanet-JATO] Re: Deployment problem
    Hi Mike,
    I tried changing the url in all the viewbeans to reflect the new sub-
    directory for the viewbeans(I have placed the jsps and viewbeans in
    a sub-directory under MigtoolboxSampleApp/MigtoolboxSample). But I'm
    still not able to get access to the jsps. I basically see the
    message "GX Error Socket Error Code missing!!" error on the browser
    thrown by iPlanet, but the log doesn't tell me anything. Does the url
    which I give to access the jsp change accordingly, i.e., should I
    give something other
    than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp.
    If I try to use any other url other
    than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp, I
    see the FileNotFoundException in the log.
    I guess I'm still missing something.
    Thanks for your help.
    --Chidu.
    --- In <a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166136158139046209">iPlanet-JATO@y...</a>, "Mike Frisino" <<a href="/group/SunONE-JATO/post?protectID=174176219122158198138082063148231088239026066196217130152150">Michael.Frisino@S...</a>> wrote:
    Chidu.
    Did you also adjust the following member in each of the ViewBeans?
    public static final String DEFAULT_DISPLAY_URL=
    "/jatosample/module1/Index.jsp";
    Try adjusting this to be consistent with your new hierarchy.
    Also, if you still have problems, send us the error message thatyou recieve
    when you try to access the page. That would help.
    ----- Original Message -----
    From: <<a href="/group/SunONE-JATO/post?protectID=219015020150194233215218164036129208">chidusv@y...</a>>
    Sent: Thursday, July 26, 2001 4:48 PM
    Subject: [iPlanet-JATO] Deployment problem
    Hi,
    We have a requirement to seperate the models and viewbeans and
    keep
    them in seperate directories. Is it possible to seperate the
    viewbeans and models not be in the same directory?
    I tried seperating the two in the MigtoolboxSampleApp application
    provided by JATO. I changed the package and import statements
    accordingly in the viewbeans, jsps and the models. But when I
    deployed the application, I'm not able to access the Index page or
    any of the jsps. Does the ApplicationServletBase always look forthe
    viewbean in the same path as that of the module servlet?
    Any help will be appreciated.
    Thanks,
    Chidu.
    <a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166215146166214017110250006230056039126077176105140127082088124241215002153">[email protected]</a>
    <a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166215146166214017110250006230056039126077176105140127082088124241215002153">[email protected]</a>
    <a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166215146166214017110250006230056039126077176105140127082088124241215002153">[email protected]</a>

    Hi Mike,
    I tried changing the url in all the viewbeans to reflect the new sub-
    directory for the viewbeans(I have placed the jsps and viewbeans in
    a sub-directory under MigtoolboxSampleApp/MigtoolboxSample). But I'm
    still not able to get access to the jsps. I basically see the
    message "GX Error Socket Error Code missing!!" error on the browser
    thrown by iPlanet, but the log doesn't tell me anything. Does the url
    which I give to access the jsp change accordingly, i.e., should I
    give something other
    than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp.
    If I try to use any other url other
    than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp, I
    see the FileNotFoundException in the log.
    I guess I'm still missing something.
    Thanks for your help.
    --Chidu.
    --- In iPlanet-JATO@y..., "Mike Frisino" <Michael.Frisino@S...> wrote:
    >
    Chidu.
    Did you also adjust the following member in each of the ViewBeans?
    public static final String DEFAULT_DISPLAY_URL=
    "/jatosample/module1/Index.jsp";
    Try adjusting this to be consistent with your new hierarchy.
    Also, if you still have problems, send us the error message that you recieve
    when you try to access the page. That would help.
    ----- Original Message -----
    From: <chidusv@y...>
    Sent: Thursday, July 26, 2001 4:48 PM
    Subject: [iPlanet-JATO] Deployment problem
    Hi,
    We have a requirement to seperate the models and viewbeans and
    keep
    them in seperate directories. Is it possible to seperate the
    viewbeans and models not be in the same directory?
    I tried seperating the two in the MigtoolboxSampleApp application
    provided by JATO. I changed the package and import statements
    accordingly in the viewbeans, jsps and the models. But when I
    deployed the application, I'm not able to access the Index page or
    any of the jsps. Does the ApplicationServletBase always look for the
    viewbean in the same path as that of the module servlet?
    Any help will be appreciated.
    Thanks,
    Chidu.
    [email protected]

  • Deployment Problems of Enterprise Application in NWDS 7.1

    Hello Everyone,<br>
    <br>
    I am having a problem when trying to deploy an application I made to the server. The project consists of two DCs, one which is an Enterprise Application and the other is a Web Module. I have configured the web module to be a dependency of the Enterprise application, so that the .war file generated from the Web Module DC is contained within the .ear file created when the Enterprise Application DC is built. The only dependency that the Web Module DC has is "engine.jee5.facade," which is there by default when it is created. I have not added any code to either DC, because I was just trying to test if I could deploy something to the server before I got into that. When I build the Enterprise Application DC, both DCs build successfully (because of the dependency). When I deploy the Enterprise Application DC, I get an "[ERROR CODE DPL.DC.5089]" error message. When I checked the SDN for what that error code means, I get sent to <a href="http://wiki.sdn.sap.com/wiki/display/JSTSG/(JSTSG)(Deploy)Problems-P58">http://wiki.sdn.sap.com/wiki/display/JSTSG/(JSTSG)(Deploy)Problems-P58</a>, which is pretty vague.
    I did try to see if I could deploy the .ear by itself, without the war file within it (by removing the dependency on the Enterprise Application DC) and that seemed to work ok. Its just seems to be when the Web Module is a dependency of the Enterprise Application is when it fails. I have included the error message I get from NWDS below. Thanks in advance for any help you can offer.                                                                                <br>                                                                                <br>                                                                                SUMMARY<br>                
    ~~~~~~~~~~~~~~~~~~~<br>
    Successfully deployed:           0<br>
    Deployed with warnings:           0<br>
    Failed deployments:                1<br>
    ~~~~~~~~~~~~~~~~~~~<br>
    ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
    ; nested exception is:
         com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
    sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
    version status: [HIGHER]
    deployment status: [Admitted]
    description: []
    ]. Cannot update it. <br>
    <br>
    1. File:C:\Develop\workspace.jdi\2\DCs\sap.com\test\sgj_ent_app_test_three\_comp\gen\default\deploy\sap.comtestsgj_ent_app_test_three.ear<br>
         Name:test~sgj_ent_app_test_three<br>
         Vendor:sap.com<br>
         Location:PDI_J2EETST1_D<br>
         Version:20100716152020<br>
         Deploy status:Aborted<br>
         Version:HIGHER<br>
    <br>
         Description:<br>
              1. [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container.<br>
    <br>
    Exception:<br>
    com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
    Reason: ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
    ; nested exception is:
         com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
    sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
    version status: [HIGHER]
    deployment status: [Admitted]
    description: []
    ]. Cannot update it.
         at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:715)
         at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:226)
         at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:112)
         at com.sap.ide.eclipse.j2ee.engine.deploy.view.deploy.action.DeployAction$DeployActionJob.run(DeployAction.java:222)
         at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
    ; nested exception is:
         com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
    sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
    version status: [HIGHER]
    deployment status: [Admitted]
    description: []
    ]. Cannot update it.
         at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:188)
         at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:57)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:229)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:91)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:34)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
    sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
    version status: [HIGHER]
    deployment status: [Admitted]
    description: []
    ]. Cannot update it.
         at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:81)
         at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:110)
         at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:51)
         at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:163)
         ... 8 more
    Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: [ERROR CODE DPL.DS.6193] Error while ; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:4712)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:426)
         at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:67)
         ... 11 more
    Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container.
         at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:496)
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:249)
         at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:197)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2534)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:525)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:424)
         ... 12 more
    Caused by: java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException:
         at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:73)
         at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:54)
         at com.sap.engine.services.security.server.AuthenticationContextImpl.setProperty(AuthenticationContextImpl.java:533)
         at com.sap.engine.services.servlets_jsp.server.deploy.util.SecurityUtils.initSecurityConfiguration(SecurityUtils.java:722)
         at com.sap.engine.services.servlets_jsp.server.deploy.util.SecurityUtils.createSecurityResources(SecurityUtils.java:143)
         at com.sap.engine.services.servlets_jsp.server.deploy.DeployAction.initXmls(DeployAction.java:778)
         at com.sap.engine.services.servlets_jsp.server.deploy.DeployAction.deploy(DeployAction.java:301)
         at com.sap.engine.services.servlets_jsp.server.deploy.UpdateAction.makeUpdate(UpdateAction.java:340)
         at com.sap.engine.services.servlets_jsp.server.deploy.WebContainer.makeUpdate(WebContainer.java:341)
         at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.makeUpdate(ContainerWrapper.java:279)
         at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:490)
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:249)
         at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:197)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2534)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:525)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:424)
         at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:67)
         at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:110)
         at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:51)
         at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:163)
         at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:57)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:229)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:91)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:34)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Edited by: Savin on Aug 5, 2010 10:25 PM
    Edited by: Savin on Aug 5, 2010 10:26 PM
    Edited by: Savin on Aug 5, 2010 10:31 PM
    Edited by: Savin on Aug 5, 2010 5:27 PM
    Edited by: Savin on Aug 5, 2010 5:38 PM
    Edited by: Savin on Aug 5, 2010 5:44 PM

    Hi Veera/Abhi
    I have installed MinDB and all the required files on the PDA. It is synchronizing with the middleware.
    On my NWDS PDA  Simulator , the application is appearing but when i click on the application there is no data and it is giving exception
    2009-02-11 13:02:40 ...  (com.sap.tc.mobile.cfs.pers.PersistenceManager:release resultset) Thread: Finalizer Error: java.sql.SQLException: Result set is closed
    Madhu--
    Please find my ans to the following points mentioned by you
    1) BASIS SWCV must be assigned in the Distribution Model Software Component Version tab of the device.
    It is assigned
    2) Activate the "DISTRIBUTE_USER_DETAILS" Rule in the admin.
    Rule is activated
    3) Activate the "DISTRIBUTE_USER_AUTHORIZATIONS" Rule in the admin.
    Rule is activated
    4) Make sure that you have installed the following components in the following sequence in the PDA
    - Creme
    - MinDB/DB2e
    - PDA_eswt_container
    - PDA Runtime.
    Client is  installed in this sequence only. I referrred to help.sap.com while installing
    the application should atleast work in the NWDS PDA simulator. My basic problem is it is not picking  up the data. giving the above mentioned error.
    Regards
    Priya

  • Deploying problem of web dynpro java application

    Hi,
    I have a web dynpro java application with no problem about deploying.
    I copied this application with another name.
    I tryed new application to deploy but sdm aborted with error.
    Error
    19.Tem.2011 10:22:25 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [001]Deployment aborted
    Settings
    SDM host : vserver0202
    SDM port : 52018
    URL to deploy : file:/C:/Users/CEMIL~1.BOZ/AppData/Local/Temp/temp27456HF_PERS_RAPOR_BUTCE.ear
    Result
    => deployment aborted : file:/C:/Users/CEMIL~1.BOZ/AppData/Local/Temp/temp27456HF_PERS_RAPOR_BUTCE.ear
    Aborted: development component 'HF_PERS_RAPOR_BUTCE'/'local'/'LOKAL'/'0.2011.07.19.10.22.15'/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application local/HF_PERS_RAPOR_BUTCE.. Reason: Clusterwide exception: Failed to deploy application local/HF_PERS_RAPOR_BUTCE. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:      com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application local/HF_PERS_RAPOR_BUTCE. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment exception : The deployment of at least one item aborted

    Hi,
    Since the exception says "Are all referenced components deployed and available on the engine?"
    Check wether any DC is used as a used DC in the webdynpro component which you are deploying.
    If any used DC is available try to deploy that DC in the server and then deploy ur webdynpro application.
    If all reference DC's are avialable in server, still if you get this error try to rename the component and reload+rebuild the project and deploy it.
    Hope this helps you...
    Regards,
    Saleem Mohammad.

  • Error when stating weblogic server after EAR (packed) deploy

    Hii!
    I am having a deploy problem, after i have packed my application with the ant task
    <taskdef name="pack-ear" classname="atg.appassembly.ant.PackEarFileTask" classpathref="ant.dynamo.classpath"/>
    i cannot access my application, it throws an exception (below). Nonetheless, when i deploy with an exploded ear using:
    <taskdef name="assemble-jar" classname="atg.appassembly.ant.CreateUnpackedEarTask" classpathref="ant.dynamo.classpath" onerror="ignore"/>
    It works finely.
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools --- CONTAINER:atg.repository.RepositoryException; SOURCE:CONTAINER:atg.service.idgen.IdGeneratorException; SOURCE:java.lang.NullPointerException
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.adapter.gsa.GSAItemDescriptor.getNewId(GSAItemDescriptor.java:6946)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.adapter.gsa.GSARepository.createItem(GSARepository.java:718)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.userprofiling.ProfileTools.createNewUser(ProfileTools.java:521)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.userprofiling.ProfileTools.createNewUser(ProfileTools.java:501)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.userprofiling.ProfileRequestServlet.initializeNewProfile(ProfileRequestServlet.java:1079)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.userprofiling.ProfileRequestServlet.initializeProfile(ProfileRequestServlet.java:693)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.userprofiling.ProfileRequestServlet.serviceProfilingRequest(ProfileRequestServlet.java:604)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.userprofiling.ProfileRequestServlet.service(ProfileRequestServlet.java:450)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.DynamoPipelineServlet.service(DynamoPipelineServlet.java:491)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.URLArgumentPipelineServlet.service(URLArgumentPipelineServlet.java:303)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PathAuthenticationPipelineServlet.service(PathAuthenticationPipelineServlet.java:392)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.security.ThreadUserBinderServlet.service(ThreadUserBinderServlet.java:113)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.dtm.TransactionPipelineServlet.service(TransactionPipelineServlet.java:235)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.SecurityServlet.service(SecurityServlet.java:192)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.multisite.SiteContextPipelineServlet.service(SiteContextPipelineServlet.java:371)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.HeadPipelineServlet.passRequest(HeadPipelineServlet.java:1273)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.HeadPipelineServlet.service(HeadPipelineServlet.java:952)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.service(PipelineableServletImpl.java:272)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.filter.dspjsp.PageFilter.innerDoFilter(PageFilter.java:349)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.filter.dspjsp.PageFilter.doFilter(PageFilter.java:208)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools Caused by :CONTAINER:atg.service.idgen.IdGeneratorException; SOURCE:java.lang.NullPointerException
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.service.idgen.PersistentIdGenerator.initialize(PersistentIdGenerator.java:389)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.service.idgen.PersistentIdGenerator.addIdSpace(PersistentIdGenerator.java:475)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.service.idgen.AbstractSequentialIdGenerator.generateStringId(AbstractSequentialIdGenerator.java:331)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.adapter.gsa.GSAItemDescriptor.getNewId(GSAItemDescriptor.java:6922)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.adapter.gsa.GSARepository.createItem(GSARepository.java:718)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.userprofiling.ProfileTools.createNewUser(ProfileTools.java:521)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.userprofiling.ProfileTools.createNewUser(ProfileTools.java:501)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.userprofiling.ProfileRequestServlet.initializeNewProfile(ProfileRequestServlet.java:1079)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.userprofiling.ProfileRequestServlet.initializeProfile(ProfileRequestServlet.java:693)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.userprofiling.ProfileRequestServlet.serviceProfilingRequest(ProfileRequestServlet.java:604)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.userprofiling.ProfileRequestServlet.service(ProfileRequestServlet.java:450)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.DynamoPipelineServlet.service(DynamoPipelineServlet.java:491)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.URLArgumentPipelineServlet.service(URLArgumentPipelineServlet.java:302)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PathAuthenticationPipelineServlet.service(PathAuthenticationPipelineServlet.java:392)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.security.ThreadUserBinderServlet.service(ThreadUserBinderServlet.java:113)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.dtm.TransactionPipelineServlet.service(TransactionPipelineServlet.java:234)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.SecurityServlet.service(SecurityServlet.java:191)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.multisite.SiteContextPipelineServlet.service(SiteContextPipelineServlet.java:370)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.HeadPipelineServlet.passRequest(HeadPipelineServlet.java:1271)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.HeadPipelineServlet.service(HeadPipelineServlet.java:952)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.service(PipelineableServletImpl.java:272)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.filter.dspjsp.PageFilter.innerDoFilter(PageFilter.java:349)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.filter.dspjsp.PageFilter.doFilter(PageFilter.java:208)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools Caused by (#2):java.lang.NullPointerException
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.service.jdbc.WatcherDataSource.getConnection(WatcherDataSource.java:845)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.service.jdbc.WatcherDataSource.getConnection(WatcherDataSource.java:825)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.service.idgen.SQLIdGenerator.getConnection(SQLIdGenerator.java:633)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.service.idgen.SQLIdGenerator.initializeIdSpaces(SQLIdGenerator.java:833)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.service.idgen.PersistentIdGenerator.initialize(PersistentIdGenerator.java:327)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.service.idgen.PersistentIdGenerator.addIdSpace(PersistentIdGenerator.java:475)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.service.idgen.AbstractSequentialIdGenerator.generateStringId(AbstractSequentialIdGenerator.java:331)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.adapter.gsa.GSAItemDescriptor.getNewId(GSAItemDescriptor.java:6922)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.adapter.gsa.GSARepository.createItem(GSARepository.java:718)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.userprofiling.ProfileTools.createNewUser(ProfileTools.java:521)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.userprofiling.ProfileTools.createNewUser(ProfileTools.java:501)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.userprofiling.ProfileRequestServlet.initializeNewProfile(ProfileRequestServlet.java:1079)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.userprofiling.ProfileRequestServlet.initializeProfile(ProfileRequestServlet.java:693)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.userprofiling.ProfileRequestServlet.serviceProfilingRequest(ProfileRequestServlet.java:604)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.userprofiling.ProfileRequestServlet.service(ProfileRequestServlet.java:450)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.DynamoPipelineServlet.service(DynamoPipelineServlet.java:491)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.URLArgumentPipelineServlet.service(URLArgumentPipelineServlet.java:302)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PathAuthenticationPipelineServlet.service(PathAuthenticationPipelineServlet.java:392)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.security.ThreadUserBinderServlet.service(ThreadUserBinderServlet.java:113)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.dtm.TransactionPipelineServlet.service(TransactionPipelineServlet.java:234)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.SecurityServlet.service(SecurityServlet.java:191)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.multisite.SiteContextPipelineServlet.service(SiteContextPipelineServlet.java:370)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.HeadPipelineServlet.passRequest(HeadPipelineServlet.java:1271)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.HeadPipelineServlet.service(HeadPipelineServlet.java:952)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.servlet.pipeline.PipelineableServletImpl.service(PipelineableServletImpl.java:272)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.filter.dspjsp.PageFilter.innerDoFilter(PageFilter.java:349)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at atg.filter.dspjsp.PageFilter.doFilter(PageFilter.java:208)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    **** Error Ter Nov 12 14:02:53 BRST 2013 1384272173984 /atg/userprofiling/ProfileTools
    <12/11/2013 14h02min54s BRST> <Error> <HTTP> <BEA-101020> <[ServletContext@284990416[app:Production module:LojaAtgEndeca path:/LojaAtgEndeca spec-version:2.5]] Servlet failed with Exception
    java.lang.NullPointerException
      at atg.userprofiling.ProfilePropertyServlet.service(ProfilePropertyServlet.java:197)
      at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
      at atg.userprofiling.ProfileRequestServlet.service(ProfileRequestServlet.java:460)
      at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:157)
      at atg.servlet.pipeline.DynamoPipelineServlet.service(DynamoPipelineServlet.java:491)
      Truncated. see log file for complete stacktrace
    >

    Ian,
    Thanks for your response.  I have the following in my application.properties file:
    plugin.libraries=com.oracle.determinations.web.siebel.SiebelDataAdapter;com.oracle.determinations.web.siebel.PreseedOnSessionCreatedHandler;com.sample.userplugins.automation.SessionSubmitTrigger
    Additionally, I have placed the SessionSubmitTrigger class within a JAR in the plugins directory within the war.  I am using Oracle WebLogic 10.3 as the app server to deploy the war within the AdminServer. And I am using OPA 10.4.3.
    I should mention that the first two entries in the plugin.libraries property were there already as part of the Siebel Connector install.  I just added the third one for OnInvestigationEndedEventHandler implementation.
    I don't understand why Weblogic complains about not finding the Plugins directory. it is in my war. And despite the warning, I can access and navigate through my rulebase.  It just doesn't seem to handle the OnInvestigationEndedEvent.
    Thanks.
    Sam

  • Programmatically gettiing which AppServer the EAR is deployed under

    Within a Servlet or JSP, I'm trying to programmatically get the name of the JVM (AppServer) where the code (war or ear) is deployed and running under.
    (This is like getting "server1" when using WSAD).
    I tried the System, Runtime and Thread approaches with no luck.. any ideas??
    Thanks.
    Example:
    If I have 2 AppServers created: Server1 and Server2
    The ear could be deployed to either, but I want to show to the user if he/she is pointing to Server1 or Server2.

    Thanks.
    I got it using an IBM API:
    AdminServiceFactory.getAdminService().getProcessName();
    I was hoping that I would get it without vendor-specific API. Unfortunately there is no way to do it now with J2EE1.3 specs.
    The good news is that J2EE 1.4 will include JSR-88 (if I'm not mistaken) and this will have a standard deployment interfaces so this problem will be fixed.
    Thanks for your reply anyway..
    -George

  • Deployment Problem in SDM

    while deploying using SDM i am getting this error...can u please give me a solution...i am just learning to use portal
    (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [005]Deployment aborted
    Settings
    SDM host : HDCHARTOMR372
    SDM port : 50018
    URL to deploy : file:/C:/DOCUME1/MOHAMM1.HCL/LOCALS~1/Temp/temp26654TestAppEAR.ear
    Result
    => deployment aborted : file:/C:/DOCUME1/MOHAMM1.HCL/LOCALS~1/Temp/temp26654TestAppEAR.ear
    Aborted: development component 'TestAppEAR'/'sap.com'/'localhost'/'2007.06.28.15.05.59':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment exception : The deployment of at least one item aborted

    Hi Mohammed,
    from your portal User Admin -> Groups page - search for the group named Administrators. Then add the user id 'admin' into that Administrators group and save it. Then try redeploying the application. Normally the SDM is accessed by the 'admin' user - and that user has to be part of the Administrators group to access SDM. I guess your problem would be resolved by this change.
    Or you can do the same thing from accessing the User Admin page in http://host:port/useradmin URL also. There also you have to add this user in the group I mentioned above.
    Regards,
    Shubhadip
    Message was edited by:
            Shubhadip Ghosh

  • EM website (ssl-enabled) deployment problem

    Hi,
    I download and installed the Oracle 9iAS release 3 for Linux. OS: SLES 7 (certified platform).
    Tested the out-of-the-box configuration of the EM web site and everything works (at least nog visable problems). Tried to deploy a web-application (ear-file) --> no problem.
    Now I enabled ssl for the EM web site (as described in doc id 201387.1 on Metalink). If I now try to deploy a web-application I get an error after step 2 of the ear-deployment wizard. The error I get is the following:
    Internal Error The J2EE application (.ear) file needs to be specified and read before the deploy process can proceed. Go back to the Deploy Application Introduction page.
    What might be the problem? As stated it works without ssl.
    Guido

    I have JDK 1.6.0_20-b02 on redhat linx, but still having the issue
    <Jul 31, 2012 9:58:57 AM MDT> <Error> <oracle.as.management.mbeans.opmn> <BEA-000000> <OPMN mbeanstart failed with the following exception
    oracle.as.management.opmn.optic.OpticBadConnectException: Error flushing write connection to OPMN
    at oracle.as.management.opmn.optic.OpmnPhone.sendRequest(OpmnPhone.java:739)
    at oracle.as.management.opmn.optic.OpmnPhone.makePhoneCall(OpmnPhone.java:330)
    at oracle.as.management.opmn.optic.OpmnPhone.request(OpmnPhone.java:270)
    at oracle.as.management.opmn.optic.OpmnQuery.getBuf(OpmnQuery.java:462)
    at oracle.as.management.mbeans.opmn.Opmn.manageProcess(Opmn.java:238)
    at oracle.as.management.mbeans.opmn.Opmn.startProcess(Opmn.java:102)
    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:597)
    at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.doInvoke(OracleStand

  • Message Driven Bean deployment problem in SAILFIN b12

    Hi,
    I am a fresh learner in EJB technology and have been experiencing a deployment problem while attempting to deploy a very simple message driven bean, that does nothing basically, to a SAILFIN (b12) application server instance. I am using NetBeans 5.5.1 to form the message driven bean but I deploy the bean manually on a Linux terminal. The following is the code of the bean:
    package trial.mdb;
    import javax.annotation.Resource;
    import javax.ejb.ActivationConfigProperty;
    import javax.ejb.MessageDriven;
    import javax.jms.Message;
    import javax.jms.MessageListener;
    @MessageDriven(mappedName = "jms/MDB1", activationConfig = {
    @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"),
    @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")
    public class MDB1 implements MessageListener {
    /** Creates a new instance of MDB1 */
    public MDB1() {
    public void onMessage(Message message) {
    I got the following message after deployment attempt:
    "Command deploy executed successfully with following warning messages: Error occurred during application loading phase. The application will not run properly. Please fix your application and redeploy.
    WARNING: com.sun.enterprise.deployment.backend.IASDeploymentException: Error while loading EJB module [TrialMDB]. Please refer to the server log for more details."
    The verifier does not give any error, warning or failure message and it states "com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1;" in the server log. Below, I have stated the content of the server log. I am novice in EJB technology particularly in message driven beans so any help will be appreciated. Thanks a lot in advance.
    --faydemir
    The content of the server log:
    [#|2008-01-02T16:25:11.106+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.avk.tools.verifier|_ThreadID=23;_ThreadName=Thread-41;|Verifying: [ _home_efikayd_SAILFINB12_sailfin_domains_domain1_applications_j2ee-modules_TrialMDB ]|#]
    [#|2008-01-02T16:25:11.286+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.tools.avk.tools.verifier|_ThreadID=23;_ThreadName=Thread-41;_RequestID=c8eac819-597f-454b-b189-1ad5a88770ac;|
    STATIC VERIFICATION RESULTS
    NUMBER OF FAILURES/WARNINGS/ERRORS
    # of Failures : 0
    # of Warnings : 0
    # of Errors : 0
    END OF STATIC VERIFICATION RESULTS
    |#]
    [#|2008-01-02T16:25:11.286+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.avk.tools.verifier|_ThreadID=23;_ThreadName=Thread-41;|No errors found in the archive.|#]
    [#|2008-01-02T16:25:11.367+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=23;_ThreadName=Thread-41;|deployed with moduleid = TrialMDB|#]
    [#|2008-01-02T16:25:11.441+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb.mdb|_ThreadID=24;_ThreadName=Thread-40;MDB1;com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|MDB00017: [MDB1]: Exception in creating message-driven bean container: [com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1]|#]
    [#|2008-01-02T16:25:11.441+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb.mdb|_ThreadID=24;_ThreadName=Thread-40;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|com.sun.enterprise.connectors.ConnectorRuntimeException
    com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1
    at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:1528)
    at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:1379)
    at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:170)
    at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:209)
    at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:280)
    at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:537)
    at com.sun.enterprise.server.EJBModuleLoader.doLoad(EJBModuleLoader.java:171)
    at com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:245)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:233)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:188)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:420)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:1004)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:991)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:470)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:182)
    at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
    at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:230)
    at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
    at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
    at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:920)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:591)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:635)
    at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:773)
    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:597)
    at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:381)
    at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:364)
    at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:470)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
    at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
    at $Proxy1.invoke(Unknown Source)
    at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
    at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
    at com.sun.enterprise.deployment.client.DeploymentClientUtils.startApplication(DeploymentClientUtils.java:154)
    at com.sun.enterprise.deployment.client.DeployAction.run(DeployAction.java:535)
    at java.lang.Thread.run(Thread.java:619)
    |#]
    [#|2008-01-02T16:25:11.443+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=24;_ThreadName=Thread-40;com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|EJB5090: Exception in creating EJB container [com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1]|#]
    [#|2008-01-02T16:25:11.443+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=24;_ThreadName=Thread-40;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|appId=TrialMDB moduleName=_home_efikayd_SAILFINB12_sailfin_domains_domain1_applications_j2ee-modules_TrialMDB ejbName=MDB1|#]
    [#|2008-01-02T16:25:11.443+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.core.classloading|_ThreadID=24;_ThreadName=Thread-40;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|LDR5004: UnExpected error occured while creating ejb container
    com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1
    at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:1528)
    at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:1379)
    at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:170)
    at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:209)
    at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:280)
    at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:537)
    at com.sun.enterprise.server.EJBModuleLoader.doLoad(EJBModuleLoader.java:171)
    at com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:245)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:233)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:188)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:420)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:1004)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:991)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:470)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:182)
    at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
    at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:230)
    at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
    at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
    at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:920)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:591)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:635)
    at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:773)
    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:597)
    at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:381)
    at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:364)
    at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:470)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
    at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
    at $Proxy1.invoke(Unknown Source)
    at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
    at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
    at com.sun.enterprise.deployment.client.DeploymentClientUtils.startApplication(DeploymentClientUtils.java:154)
    at com.sun.enterprise.deployment.client.DeployAction.run(DeployAction.java:535)
    at java.lang.Thread.run(Thread.java:619)
    |#]
    [#|2008-01-02T16:25:11.445+0100|WARNING|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=24;_ThreadName=Thread-40;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|CORE5020: Error while loading ejb module|#]
    [#|2008-01-02T16:25:11.446+0100|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=24;_ThreadName=Thread-40;Error while loading EJB module [TrialMDB]. Please refer to the server log for more details. ;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|ADM1075:Error on listening event:[Error while loading EJB module [TrialMDB]. Please refer to the server log for more details. ]|#]

    Hi thank you for your answer. I did not create any jms resource in the application server because my message driven bean was not implementing the MessageListener interface. Since it did not work in that way, I added the MessageListenerInterface to the bean and formed the necessary jms resources usuing the admin console of the SAILFIN but it keeps giving the same message both on the linux terminal and the server log.
    Let me explain my situation in a more detailed way. I am developing a JCA based resource adapter (i.e.) connector. The inbound module of the connector listens on a specific port for incoming messages from a server (EIS). The port property is defined in the connector's deployment descriptor. When a message reaches, the connector delivers it to the a message driven bean whose code is indicated in the following:
    package com....;
    import com....ra.facade.InboundListener;
    import javax.ejb.ActivationConfigProperty;
    import javax.ejb.MessageDriven;
    import javax.jms.Message;
    import javax.jms.MessageListener;
    import java.util.logging.*;
    * Entity class InboundMessageReceiverMDB
    * @author efikayd
    @MessageDriven(
    mappedName = "InboundMessageReceiverMDB",
    messageListenerInterface = com......ra.facade.InboundListener.class,
    activationConfig = {
    @ActivationConfigProperty(
    propertyName = "listenerPort", propertyValue = "12345"),
    @ActivationConfigProperty(
    propertyName="ConnectionFactoryJndiName", propertyValue="RAjms/MyQCF"),
    @ActivationConfigProperty(
    propertyName="DestinationName", propertyValue="MyQueue"),
    @ActivationConfigProperty(
    propertyName="DestinationType", propertyValue="javax.jms.Queue")
    public class InboundMessageReceiverMDB implements InboundListener, MessageListener {
    private static final Logger logger = Logger.getLogger("com.xyz.inbound.InboundMessageReceiverMDB");
    /** Creates a new instance of InboundMessageReceiverMDB */
    public InboundMessageReceiverMDB() {
    public void onMessage(Message message) {
    public void receiveMessage(String message) {
    logger.log(Level.SEVERE, "CLASS: " + getClass().getName() + "METHOD: receiveMessage() ==> Message received...: " + message);
    The listener interface is the following:
    package com...ra.facade;
    public interface InboundListener{
    public void receiveMessage(String message);
    I have set the JMS resource and the destination resource properties on the admin console in the following manner:
    ConnectionFactory:
    JNDI Name: RAjms/MyQCF
    Pool Name: RAjms/MyQCF
    Type: javax.jms.ConnectionFactory
    Status: enabled
    Property1 ==> Name: DestinationType Value: javax.jms.Queue
    Property2 ==> Name: DestinationName Value: MyQueue
    Destination (i.e. queue):
    JNDIName: MyQueue
    Physical Destination Name: MyQueue
    status: enabled
    Property1 ==> Name: DestinationType Value:javax.jms.Queue
    Property2 ==> Name: DestinationName Value:MyQueue
    Although I created the JMS resources as above I am getting the same problems.Do you think the above configuration is fine and appropriate to the activation configuration definitions in my message driven bean code? Am I missing something on this configuration? Below, I have indicated the message that I got on the linux terminal when I attempt to deploy the message driven bean and the related server log. They are same as what I posted before (i.e. JMS resource cannot be created...). Thank you very much in advance for your help.
    Kind regards,
    faydemir
    PS: The 'restart' command in the following linux terminal outcome basically makes a call to a bash script which deploys the message driven bean to the SAILFIN application server. The resource adapter instance is already deployed on the application server before attempting to deploy the message driven bean.
    WHILE DEPLOYING:
    ws2089 [11:29am] [home/efikayd/bin] -> ./restart
    Command deploy executed successfully with following warning messages: Error occurred during application loading phase. The application will not run properly. Please fix your application and redeploy.
    WARNING: com.sun.enterprise.deployment.backend.IASDeploymentException: Error while loading EJB module [InboundReceiverMDBModule]. Please refer to the server log for more details.
    ws2089 [11:29am] [home/efikayd/bin] ->
    SERVER LOG:
    [#|2008-01-03T11:29:00.542+0100|INFO|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Application server startup complete.|#]
    [#|2008-01-03T11:29:09.482+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;/tmp/s1astempdomain1server-1825660455/InboundReceiverMDBModule.jar;|ADM1006:Uploading the file to:[/tmp/s1astempdomain1server-1825660455/InboundReceiverMDBModule.jar]|#]
    [#|2008-01-03T11:29:12.399+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=18;_ThreadName=Thread-32;|deployed with moduleid = InboundReceiverMDBModule|#]
    [#|2008-01-03T11:29:12.739+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb.mdb|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;InboundMessageReceiverMDB;com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|MDB00017: [InboundMessageReceiverMDB]: Exception in creating message-driven bean container: [com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB]|#]
    [#|2008-01-03T11:29:12.739+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb.mdb|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|com.sun.enterprise.connectors.ConnectorRuntimeException
    com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB
         at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:1528)
         at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:1379)
         at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:170)
         at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:209)
         at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:280)
         at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:537)
         at com.sun.enterprise.server.EJBModuleLoader.doLoad(EJBModuleLoader.java:171)
         at com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:245)
         at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:233)
         at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:188)
         at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:420)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:1004)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:991)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:470)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:182)
         at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
         at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:230)
         at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
         at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
         at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:920)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:591)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:635)
         at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:773)
         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:597)
         at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:381)
         at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:364)
         at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:470)
         at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
         at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
         at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
         at $Proxy1.invoke(Unknown Source)
         at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
         at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
         at com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:69)
         at com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandler.java:155)
         at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.processRequest(RemoteJmxConnectorServlet.java:122)
         at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.doPost(RemoteJmxConnectorServlet.java:193)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
         at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:290)
         at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
         at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
         at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:271)
         at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
         at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
         at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
         at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:339)
         at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:261)
         at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:212)
         at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
         at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)
    |#]
    [#|2008-01-03T11:29:12.742+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|EJB5090: Exception in creating EJB container [com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB]|#]
    [#|2008-01-03T11:29:12.742+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|appId=InboundReceiverMDBModule moduleName=_home_efikayd_SAILFINB12_sailfin_domains_domain1_applications_j2ee-modules_InboundReceiverMDBModule ejbName=InboundMessageReceiverMDB|#]
    [#|2008-01-03T11:29:12.742+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.core.classloading|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|LDR5004: UnExpected error occured while creating ejb container
    com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB
         at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:1528)
         at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:1379)
         at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:170)
         at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:209)
         at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:280)
         at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:537)
         at com.sun.enterprise.server.EJBModuleLoader.doLoad(EJBModuleLoader.java:171)
         at com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:245)
         at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:233)
         at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:188)
         at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:420)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:1004)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:991)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:470)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:182)
         at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
         at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:230)
         at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
         at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
         at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:920)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:591)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:635)
         at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:773)
         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:597)
         at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:381)
         at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:364)
         at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:470)
         at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
         at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
         at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
         at $Proxy1.invoke(Unknown Source)
         at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
         at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
         at com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:69)
         at com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandler.java:155)
         at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.processRequest(RemoteJmxConnectorServlet.java:122)
         at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.doPost(RemoteJmxConnectorServlet.java:193)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
         at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:290)
         at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
         at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
         at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:271)
         at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
         at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
         at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
         at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:339)
         at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:261)
         at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:212)
         at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
         at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)
    |#]
    [#|2008-01-03T11:29:12.745+0100|WARNING|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|CORE5020: Error while loading ejb module|#]
    [#|2008-01-03T11:29:12.747+0100|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;Error while loading EJB module [InboundReceiverMDBModule]. Please refer to the server log for more details. ;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|ADM1075:Error on listening event:[Error while loading EJB module [InboundReceiverMDBModule]. Please refer to the server log for more details. ]|#]

  • Terracotta: application deploy problem (WLP 9.2)

    hi,
    when i try to deploy a Portal application on a bea weblogic server (9.2.1), that is enabled for terracotta (added the java startup arguments to the bea server and the client is visible in the Terracotta Administrator Console), the deployment fails and a lot of compile errors are shown concerning bea classes (from netuix.jar and content.jar, see bottom for snippet). for some reason bea wants to compile these classes on deployment.
    has anybody seen this same problem and does anybody have a solution or workaround for this problem? must the classes be compiled on the fly during development?
    regards,
    erik
    log snippet:
    ####<Oct 4, 2007 6:48:49 PM CEST> <Error> <Deployer> <opteron-w2k3> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1191516529616> <BEA-149205> <Failed to initialize the application 'ps' due to error weblogic.application.ModuleException: Exception preparing module: EJBModule(netuix.jar)
    Unable to deploy EJB: netuix.jar from netuix.jar:
    There are 1 nested errors:
    java.io.IOException: Compiler failed executable.exec:
    D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\wsrp\services\persistence\internal\ProducerPersistenceManager_7vyoe8_Impl.java:11: com.bea.wsrp.services.persistence.internal.ProducerPersistenceManager_7vyoe8_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.wsrp.services.persistence.internal.ProducerPersistenceManager_7vyoe8_Intf
    public final class ProducerPersistenceManager_7vyoe8_Impl
    ^
    D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\BookDefinitionManager_1xzrxc_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.BookDefinitionManager_1xzrxc_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.BookDefinitionManager_1xzrxc_Intf
    public final class BookDefinitionManager_1xzrxc_Impl
    ^
    D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\PortletCategoryManager_uhkdka_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.PortletCategoryManager_uhkdka_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.PortletCategoryManager_uhkdka_Intf
    public final class PortletCategoryManager_uhkdka_Impl
    [MORE CLASSES HERE]
    D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\PortalDefinitionManager_d875a8_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.PortalDefinitionManager_d875a8_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.PortalDefinitionManager_d875a8_Intf
    public final class PortalDefinitionManager_d875a8_Impl
    ^
    D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\PageDefinitionManager_c4el9c_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.PageDefinitionManager_c4el9c_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.PageDefinitionManager_c4el9c_Intf
    public final class PageDefinitionManager_c4el9c_Impl
    ^
    Note: Some input files use or override a deprecated API.
    Note: Recompile with -Xlint:deprecation for details.
    Note: Some input files use unchecked or unsafe operations.
    Note: Recompile with -Xlint:unchecked for details.
    25 errors
         at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:435)
         at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:295)
         at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:303)
         at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
         at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
         at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
         at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:430)
         at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:752)
         at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:655)
         at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1199)
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:354)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
         at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:137)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:38)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

    the deployment problem is solved by putting the bea packages in the exclude section of the Terracotta configuration file.

  • Webdynpro application deployment problem

    Hi, I am tring to deploy webdynpro application using netweaver studio 2004 version, and using ep6.
    when I deploy and run application , I get following error:-
    URL to deploy : file:/C:/DOCUME1/PROCES1/LOCALS~1/Temp/temp32470a.ear
    Result
    => deployment aborted : file:/C:/DOCUME1/PROCES1/LOCALS~1/Temp/temp32470a.ear
    Aborted: development component 'a'/'local'/'LOKAL'/'0.2006.09.28.23.40.19':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Only Administrators have the right to perform this operation.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    1.
    why does it say only administrator can deploy? I am uing login which has admin rights.
    2. is there any other way to deploy ear file? using some SDM  or other way? How?

    I tried using SDM, same error message: only adminsitrators have rights to perform this action.
    I think, I am not able to access J2EE engine.
    How to get J2EE engine access?
    Message was edited by: Ankit

  • Does the final Release 5.1 Support ear type deployment in Weblogic

    I down loaded final Release 5.1 and trying to find deploying different
    modules using using ear (Enterprise Archieve), I can not find
    any documents.
    Does the final Release support ear type deploying or not.
    Regards
    Krishna

    No, it supports war and jar deployments only.
    -- Rob
    Krishna Chaganti wrote:
    I down loaded final Release 5.1 and trying to find deploying different
    modules using using ear (Enterprise Archieve), I can not find
    any documents.
    Does the final Release support ear type deploying or not.
    Regards
    Krishna

Maybe you are looking for

  • Moving data from pc to mac with external hard drive

    I moved my tunes and pictures from my pc to ext hd. Found hd on my mac, but nothing shows up in the hard drive folder on my mac... how come? what did i do wrong? Thanks, M

  • PDF Exaprom, problem with multitext in one header

    Problem is,that according to my simply thiking when I connect two elements Append Text HF one by one serialy with some text in header, and in their properties I set alligment both of them at left- MIDDLE in my opinion it suppose to overwrite one text

  • Any issues connecting the new MacBook to LCD projector with VGA adapter?

    I do presentations on the road using my old MacBook with whatever LCD I find when I get there. I run Keynote with lots of video clips in my presentations. I carry a Mini-DVI to VGA adapter. Most often it works fine. I was hoping to update to the new

  • Settlement Through WBS element in CJ88

    Dear Expert, When I going settle one asse through WBS element P05/00204/CB, I got the follwing problem in SAP Down payment to recipient 802000000006 0 area 01 amount 5,142.74 not cleared Message no. AW605 Diagnosis All downpayments were not cleared f

  • My iWeb's main blog page has photos of entries all mixed up

    My site is egsilberman.com and all but the main blog page is functioning.  The index.html looks perfect, the page listing all the blog pages using the index.html in the browser looks as it should. But after uploading the site to my FTP - using iWeb S