Deploying JCA with WebLogic 6.1sp3

I am trying to configure kodo-jdo-3.1.2 in WebLogic 6.1sp3 using JCA
method.
But I meet follwing error:
java.lang.Throwable: Couldn't find methods :null or setRestoreMutableValues
with argtype: java.lang.Boolean
at
weblogic.connector.common.internal.ConnectionPool.invokeRemainingSetters(Con
nectionPool.java:536)
at
weblogic.connector.common.internal.ConnectionPool.<init>(ConnectionPool.java
:464)
at
weblogic.connector.common.internal.ConnectionPoolManager.addManagedConnectio
nFactory(ConnectionPoolManager.java:54)
at
weblogic.j2ee.ResourceAdapterComponent.deploy(ResourceAdapterComponent.java:
189)
at weblogic.j2ee.Application.addComponent(Application.java:170)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:360)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
Target.java:285)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
eploymentTarget.java:239)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
entTarget.java:199)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
..java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:360)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy34.updateDeployments(Unknown Source)
at
weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
ServerMBean_CachingStub.java:2977)
at
weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
icationManager.java:372)
at
weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
r.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
..java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:360)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy48.start(Unknown Source)
at
weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
ApplicationManagerMBean_CachingStub.java:480)
at
weblogic.management.Admin.startApplicationManager(Admin.java:1234)
at weblogic.management.Admin.finish(Admin.java:644)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
at weblogic.Server.main(Server.java:35)
java.lang.Throwable: Couldn't find methods :null or setFetchBatchSize with
argtype: java.lang.Integer
at
weblogic.connector.common.internal.ConnectionPool.invokeRemainingSetters(Con
nectionPool.java:536)
at
weblogic.connector.common.internal.ConnectionPool.<init>(ConnectionPool.java
:464)
at
weblogic.connector.common.internal.ConnectionPoolManager.addManagedConnectio
nFactory(ConnectionPoolManager.java:54)
at
weblogic.j2ee.ResourceAdapterComponent.deploy(ResourceAdapterComponent.java:
189)
at weblogic.j2ee.Application.addComponent(Application.java:170)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:360)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
Target.java:285)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
eploymentTarget.java:239)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
entTarget.java:199)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
..java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:360)

While this platform is not officially supported, are you seeing further
problems past these error messages which are usually just warnings?
Leejungryong wrote:
I am trying to configure kodo-jdo-3.1.2 in WebLogic 6.1sp3 using JCA
method.
But I meet follwing error:
java.lang.Throwable: Couldn't find methods :null or setRestoreMutableValues
with argtype: java.lang.Boolean
at
weblogic.connector.common.internal.ConnectionPool.invokeRemainingSetters(Con
nectionPool.java:536)
at
weblogic.connector.common.internal.ConnectionPool.<init>(ConnectionPool.java
:464)
at
weblogic.connector.common.internal.ConnectionPoolManager.addManagedConnectio
nFactory(ConnectionPoolManager.java:54)
at
weblogic.j2ee.ResourceAdapterComponent.deploy(ResourceAdapterComponent.java:
189)
at weblogic.j2ee.Application.addComponent(Application.java:170)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:360)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
Target.java:285)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
eploymentTarget.java:239)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
entTarget.java:199)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:360)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy34.updateDeployments(Unknown Source)
at
weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
ServerMBean_CachingStub.java:2977)
at
weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
icationManager.java:372)
at
weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
r.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:360)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy48.start(Unknown Source)
at
weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
ApplicationManagerMBean_CachingStub.java:480)
at
weblogic.management.Admin.startApplicationManager(Admin.java:1234)
at weblogic.management.Admin.finish(Admin.java:644)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
at weblogic.Server.main(Server.java:35)
java.lang.Throwable: Couldn't find methods :null or setFetchBatchSize with
argtype: java.lang.Integer
at
weblogic.connector.common.internal.ConnectionPool.invokeRemainingSetters(Con
nectionPool.java:536)
at
weblogic.connector.common.internal.ConnectionPool.<init>(ConnectionPool.java
:464)
at
weblogic.connector.common.internal.ConnectionPoolManager.addManagedConnectio
nFactory(ConnectionPoolManager.java:54)
at
weblogic.j2ee.ResourceAdapterComponent.deploy(ResourceAdapterComponent.java:
189)
at weblogic.j2ee.Application.addComponent(Application.java:170)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:360)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
Target.java:285)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
eploymentTarget.java:239)
at
weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
entTarget.java:199)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:360)
Steve Kim
[email protected]
SolarMetric Inc.
http://www.solarmetric.com

Similar Messages

  • EJB 3.0 MDB deployment issue with weblogic 10.0

    Hi there,
    I am new to MDB EJB and right now I am using the EJB 3.0 with weblogic server 10.0. I am using Eclipse 3.4 for development.
    After developing the MDB from eclipse I export the EAR from eclipse and deploy it in weblogic. When I try to start the deployed EAR it gives me following error.
    weblogic.application.ModuleException: Exception preparing module: EJBModule(Message.jar)
    Unable to deploy EJB: MessageBean from Message.jar:
    [EJB:011113]Error: The Message Driven Bean 'MessageBean(Application: MessageEAR, EJBComponent: Message.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:399)
         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)
         Truncated. see log file for complete stacktrace
    [EJB:011113]Error: The Message Driven Bean 'MessageBean(Application: MessageEAR, EJBComponent: Message.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
         at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.ensureMDBHasDestinationConfigured(MessageDrivenBeanInfoImpl.java:1811)
         at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.prepare(MessageDrivenBeanInfoImpl.java:1011)
         at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:997)
         at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1273)
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:372)
         Truncated. see log file for complete stacktrace
    >
    Any help really appreciated. It's too urgent.
    Thanks in advance,
    Piyush

    here is the code for my bean.
    package com.ups;
    import java.util.logging.Logger;
    import javax.ejb.ActivationConfigProperty;
    import javax.ejb.EJBException;
    import javax.ejb.MessageDriven;
    import javax.ejb.MessageDrivenContext;
    import javax.jms.JMSException;
    import javax.jms.Message;
    import javax.jms.MessageListener;
    import javax.jms.TextMessage;
    * Message-Driven Bean implementation class for: MessageBean
    @MessageDriven(
              activationConfig = { @ActivationConfigProperty(
                        propertyName = "destinationType", propertyValue = "javax.jms.Queue"
    public class MessageBean implements MessageListener {
         private MessageDrivenContext mdc;
    * Default constructor.
    public MessageBean() {
    // TODO Auto-generated constructor stub
    * @see MessageListener#onMessage(Message)
    public void onMessage(Message message) {
         TextMessage tmsg = null;
    try {
    tmsg = (TextMessage) message;
    System.out.println("MESSAGE BEAN: Message received: " + tmsg.getText( ));
    System.out.println ("The onMessage() is called");
    } catch (JMSException e) {
    e.printStackTrace( );
    mdc.setRollbackOnly( );
    catch (Throwable th) {
    th.printStackTrace();
    public void ejbRemove( )throws EJBException{
         System.out.println("ejbRemove() is executed >>>>>>>");
    I have configured my JMS Distributed queue in the Weblogic.
    If possible please provide more details so that I can get rid of this error as soon as possible.
    Thanks for reply.
    Piyush

  • Error while deploying application with WebLogic server

    Hi,
    I use Jdeveloper 11g and created and ADF application which i want to deploy with WebLogic Server.But i have an error which is :
    "There was a failure when processing annotations for application C:\...\xxx.war. Please make sure that the annotations are valid. The error is oracle.adf.library.webapp.ResourceServlet "
    Plz help me.
    Thx

    I am receiving same message for simple servlet. Running JDev11g build 5166 and embedded WLS 10.3. Servlet used to deploy to embedded WLS and ran fine. Recently running newly created servlets produces error message as in this thread.
    Investigation turned up the fact that the class file for the servlet was not deployed to the context-root (o.j2ee\drs) on the server. Copying the class file from the mywork project folder to the context-root folder (o.j2ee\drs) permitted the servlet to run.
    Don't know if this is the cause of what you are experiencing but it may assist in your investigation! I have not figured out why the class file for servlets does not deploy to server despite the fact that the log file shows war and ear files were deployed. As it turns out, the war file does not have the class file in it so something is wrong before the war file is created.
    Cheers!

  • Hot deployment problems with weblogic 7.0 sp2

    Hi Guys
    I am trying out hot deplyment of a j2ee application on WebLogic Server 7.0 SP2
    Approach 1
    The application is deployed in exploded ear format from the folder
    d:/work/testbed/ear. The appropriate entry in config.xml looks like this.
    <Application Deployed="true" Name="Testbed"
    Path="D:\tools\bea702\projects\testbed\applications\testbed"
    StagedTargets="" TwoPhase="false">
    <EJBComponent Name="SessionBeans" Targets="myserver" URI="SessionBeans.jar"/>
    </Application>
    Creating or touching the REDEPLOY file in META-INF folder doesnt cause hot
    deployment to occur
    Approach 2
    Copied the ear file to the applications folder. Creating or touching the
    REDEPLOY file in META-INF file caused the application to be redeployed.
    However the weblogic console is constantly spitting out this message.
    Undeploying EJB Component SessionBeans
    <Sep 29, 2003 9:53:46 PM IST> <Notice> <Application Poller> <149400> <Activating application: Testbed>
    <Sep 29, 2003 9:53:46 PM IST> <Notice> <Application Poller> <149404> <Activate application Testbed on myserver - Completed>
    Undeploying EJB Component SessionBeans
    <Sep 29, 2003 9:53:51 PM IST> <Notice> <Application Poller> <149400> <Activating application: Testbed>
    <Sep 29, 2003 9:53:52 PM IST> <Notice> <Application Poller> <149404> <Activate application Testbed on myserver - Completed>
    Undeploying EJB Component SessionBeans
    <Sep 29, 2003 9:53:57 PM IST> <Notice> <Application Poller> <149400> <Activating application: Testbed>
    <Sep 29, 2003 9:53:57 PM IST> <Notice> <Application Poller> <149404> <Activate application Testbed on myserver - Completed>
    It seems that the application is getting undeployed and reactivated every 5
    seconds.
    Questions
    1) Any reasons why approach 1 didnt work
    2) What could be causing this constant undeployment and reactivation
    Thanks for your time
    anand

    I think I figured out what is causing the application to be redployed every 5
    seconds. It seems that if the application is deployed in the weblogic domains
    applications folder you should NOT create a <Application element. Weblogic
    automatically recognizes all applications in this folder and deploys them.
    Removing the application entry (as shown in Approach 1) from the config.xml
    and hot deploying by touching the REDEPLOY file did the trick.
    One question still remains. Is hot deployment only possible when I copy the
    exploded ear to the domain "applications" folder
    Thanks for your time
    anand
    ps : The idea of trying it without the <Application element came from trying
    out hot deployment in Weblogic 8. WLS8 first deploys the application in the
    applications folder, followed by the application configured in the
    <Application element. Since both the applications were essentially the same it
    gave me a JNDIException saying that some entity is already bound with the same
    name. Weblogic 7 however doesnt complain at this point.
    - anand
    In article <[email protected]>, Anand Raman wrote:
    Hi Guys
    I am trying out hot deplyment of a j2ee application on WebLogic Server 7.0 SP2
    Approach 1
    The application is deployed in exploded ear format from the folder
    d:/work/testbed/ear. The appropriate entry in config.xml looks like this.
    <Application Deployed="true" Name="Testbed"
    Path="D:\tools\bea702\projects\testbed\applications\testbed"
    StagedTargets="" TwoPhase="false">
    <EJBComponent Name="SessionBeans" Targets="myserver" URI="SessionBeans.jar"/>
    </Application>
    Creating or touching the REDEPLOY file in META-INF folder doesnt cause hot
    deployment to occur
    Approach 2
    Copied the ear file to the applications folder. Creating or touching the
    REDEPLOY file in META-INF file caused the application to be redeployed.
    However the weblogic console is constantly spitting out this message.
    Undeploying EJB Component SessionBeans
    <Sep 29, 2003 9:53:46 PM IST> <Notice> <Application Poller> <149400> <Activating application: Testbed>
    <Sep 29, 2003 9:53:46 PM IST> <Notice> <Application Poller> <149404> <Activate application Testbed on myserver - Completed>
    Undeploying EJB Component SessionBeans
    <Sep 29, 2003 9:53:51 PM IST> <Notice> <Application Poller> <149400> <Activating application: Testbed>
    <Sep 29, 2003 9:53:52 PM IST> <Notice> <Application Poller> <149404> <Activate application Testbed on myserver - Completed>
    Undeploying EJB Component SessionBeans
    <Sep 29, 2003 9:53:57 PM IST> <Notice> <Application Poller> <149400> <Activating application: Testbed>
    <Sep 29, 2003 9:53:57 PM IST> <Notice> <Application Poller> <149404> <Activate application Testbed on myserver - Completed>
    It seems that the application is getting undeployed and reactivated every 5
    seconds.
    Questions
    1) Any reasons why approach 1 didnt work
    2) What could be causing this constant undeployment and reactivation
    Thanks for your time
    anand

  • HOT deployment problem with WebLogic 5.1sp11

    Hello!
    We trying to deploy our EJB (jar contains 5 EJB's) with WebLogic EJB DeployerTool.
    When we registered our jar in the weblogic.properties file - everything is OK.
    This ejb cotains correct EJB's which are made in EJB 1.1 standard.
    In the WebLogic EJB DeployerTool I attach proper WeaWeblogic application server
    (it works on another computer, but tool found our server confidently. Then I opened
    my jar file. Tool parsed file and found all beans.
    After all I'm trying to run Tools/Deploy and I have the error message showed below.
    If somebody knows how to manage with this problem, help!
    weblogic.ejb.common.DeploymentException: Problem creating deployment ftp://172.16.2.108:21C:/tmp2/StaffShell.jar
    from ftp://172.16.2.108:21C:/tmp2/StaffShell.jar; nested exception is:
         java.lang.NullPointerException:
    Start server side stack trace:
    java.lang.NullPointerException
         at sun.net.www.ParseUtil.decode(ParseUtil.java:27)
         at sun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.java:108)
         at java.net.URL.openStream(URL.java:798)
         at weblogic.ejb.internal.EJBJarDeployment.initializeJarFile(EJBJarDeployment.java:322)
         at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:191)
         at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:166)
         at weblogic.ejb.internal.EJBDeploymentImpl.<init>(EJBDeploymentImpl.java:172)
         at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:100)
         at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:94)
         at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:332)
         at weblogic.ejb.common.EJBManager_WLSkel.invoke(EJBManager_WLSkel.java:144)
         at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
         at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    End server side stack trace
    java.lang.NullPointerException:
    Start server side stack trace:
    java.lang.NullPointerException
         at sun.net.www.ParseUtil.decode(ParseUtil.java:27)
         at sun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.java:108)
         at java.net.URL.openStream(URL.java:798)
         at weblogic.ejb.internal.EJBJarDeployment.initializeJarFile(EJBJarDeployment.java:322)
         at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:191)
         at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:166)
         at weblogic.ejb.internal.EJBDeploymentImpl.<init>(EJBDeploymentImpl.java:172)
         at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:100)
         at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:94)
         at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:332)
         at weblogic.ejb.common.EJBManager_WLSkel.invoke(EJBManager_WLSkel.java:144)
         at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
         at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    End server side stack trace
    Deployment failed.

    Is SP11 jars in the client classpath or not, before launching DeployerTool.
    If yes, then it looks like a bug. You might want to report this problem to
    [email protected]
    Kumar
    "Anton Nazarov" <[email protected]> wrote in message
    news:[email protected]...
    >
    Hello!
    We trying to deploy our EJB (jar contains 5 EJB's) with WebLogic EJBDeployerTool.
    When we registered our jar in the weblogic.properties file - everything isOK.
    This ejb cotains correct EJB's which are made in EJB 1.1 standard.
    In the WebLogic EJB DeployerTool I attach proper WeaWeblogic applicationserver
    (it works on another computer, but tool found our server confidently. ThenI opened
    my jar file. Tool parsed file and found all beans.
    After all I'm trying to run Tools/Deploy and I have the error messageshowed below.
    >
    If somebody knows how to manage with this problem, help!
    weblogic.ejb.common.DeploymentException: Problem creating deploymentftp://172.16.2.108:21C:/tmp2/StaffShell.jar
    from ftp://172.16.2.108:21C:/tmp2/StaffShell.jar; nested exception is:
    java.lang.NullPointerException:
    Start server side stack trace:
    java.lang.NullPointerException
    at sun.net.www.ParseUtil.decode(ParseUtil.java:27)
    atsun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.ja
    va:108)
    >
    at java.net.URL.openStream(URL.java:798)
    atweblogic.ejb.internal.EJBJarDeployment.initializeJarFile(EJBJarDeployment.ja
    va:322)
    >
    at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:191)
    at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:166)
    atweblogic.ejb.internal.EJBDeploymentImpl.<init>(EJBDeploymentImpl.java:172)
    >
    atweblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:100)
    >
    at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:94)
    at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:332)
    atweblogic.ejb.common.EJBManager_WLSkel.invoke(EJBManager_WLSkel.java:144)
    >
    atweblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAda
    pter.java:347)
    >
    atweblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandle
    r.java:96)
    >
    atweblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
    5)
    >
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    End server side stack trace
    java.lang.NullPointerException:
    Start server side stack trace:
    java.lang.NullPointerException
    at sun.net.www.ParseUtil.decode(ParseUtil.java:27)
    atsun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.ja
    va:108)
    >
    at java.net.URL.openStream(URL.java:798)
    atweblogic.ejb.internal.EJBJarDeployment.initializeJarFile(EJBJarDeployment.ja
    va:322)
    >
    at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:191)
    at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:166)
    atweblogic.ejb.internal.EJBDeploymentImpl.<init>(EJBDeploymentImpl.java:172)
    >
    atweblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:100)
    >
    at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:94)
    at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:332)
    atweblogic.ejb.common.EJBManager_WLSkel.invoke(EJBManager_WLSkel.java:144)
    >
    atweblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAda
    pter.java:347)
    >
    atweblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandle
    r.java:96)
    >
    atweblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
    5)
    >
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    End server side stack trace
    Deployment failed.

  • EPMA 11.1.1.3 manual deployment issues with WEBLOGIC in EAS and WEBANALYSIS

    Hi all,
    As we are working on 64 bit machines, we have to deploy hyperion products manually with WEBLOGIC. other than EAS and WEBANALYSIS, all the products are working fine.
    we have followed all the steps related to manual deployment. but still we r getting JAVA related error. so if anything else that we need to perform other than normal manual deployment steps, please let me know.
    NOTE: EASDOCS, HBRLAUNCHER, are working but EAS is not been deployed.
    Regards

    Is your WebLogic 32-bit or 64-bit WebLogic? What specific O/S and version are you using? Some of the products make use of 32-bit native libraries's for JNDI and there are not 64-bit native libraries available unless you are using the AIX or Solaris Platform and even then not all products are supported for 64-bit.
    If you were to use 11.1.2 it supports most of the product suite in 64-bit on most platforms.
    Refer to support matrices at: http://www.oracle.com/technetwork/middleware/bi-foundation/hyperion-supported-platforms-085957.html
    Regards,
    John A. Booth
    http://www.metavero.com

  • Web Module Deployment Problem with Weblogic [Deployer:149026]

    Dear Friends,
    I've been facing a problem during deploying an Web Module on Weblogic 8.1. The name of my webmodule is 'MyOraWebModule'.
    When I first developed, deployed and tested it in Weblogic 8.1, it was deployed and worked fine. But on the next day, when I tried to redeploy it, the deployment failed. This thing not just happens only once.. it is happeing always i.e. if I develop a new webmodule and deploy/redeploy it, it will work fine ONLY ON THE FIRST DAY (i.e. the day when the web module is created), but on the next day, it shows the following error if I try to redeploy it. The error is:
    Task 3 failed: [Deployer:149026]Deploy application MyOraWebModule on myserver.
    Deployment failed on Server myserver
    Exception:weblogic.management.ApplicationException: prepare failed for MyOraWebModule
    Module: MyOraWebModule Error: Context path 'MyOraWebModule' is already in use by the module: MyOraWebModule
    Any suggestion or, guideline from you will be highly appreciated.
    With Thanks,
    ... Chisty

    Not sure if you are still looking for the answer. I have a similar problem, I have a work around on it but still trying to identify what the issue is. I have deployed multiple web application modules on weblogic 8.1 and on the redeploy I was gettig the exception weblogic.management.ApplicationException: prepare failed for USER_DEFINED_MODULE_NAME
    Context path '/' is already in use by the module. when this exception is thrown I observed that the targets attribute of tag WebAppComponent is initialized to the server name. If I stop the server, make the value of the targets attribute to be empty string in config.xml and start the server, the server starts fine. And I could continue. Not sure why this is so since the targets attribute is used to identify on what servers the application needs to be deployed.
    Any input on why the weblogic 8.1 is behaving this way when the targets attribute is defined with a value would of great help.
    thanks,

  • Application deployment order with weblogic-ejb-jar.xml and jndi-name

    I have two applicatation working on Weblogic server v. 10.3.6.
    First of them creating one ejb stateless bean and creates JNDI maping for it (in weblogic-ejb-jar.xml file):
    <weblogic-enterprise-bean>
         <ejb-name>ConfigMenegerBean</ejb-name>
         <stateless-session-descriptor>
         <stateless-session-descriptor>
              <business-interface-jndi-name-map>
              <business-remote>package.ConfigurationSessionRemote</business-remote>
              <jndi-name>ConfigMeneger</jndi-name>
              </business-interface-jndi-name-map>
         </stateless-session-descriptor>
         <enable-call-by-reference>true</enable-call-by-reference>
         <jndi-name>ConfigMeneger</jndi-name>
    </weblogic-enterprise-bean>
    Second appication have to refer for this bean by JNDI using spring been lookup :
    <jee:jndi-lookup id="configManager" jndi-name="ConfigMeneger"/>
    I changed deployment order parameter for both apllication(first=100 and second=500) in order to first app start first and share bean by jndi to another application. Unfortuantelly I got an error :
    javax.naming.NameNotFoundException: Unable to resolve 'ConfigMeneger'. Resolved ''; remaining name 'ConfigMeneger'
    How can I configure deployment order that first application make jndi mapping for bean, before the second application will use it ?

    Ok in a way I have solved my problem (even if I am not completely satisfied by the way on how to proceed...). So thanks to message "JBuilder7.0 and Weblogic6.1" on EJB sun forum :
    http://forum.java.sun.com/thread.jsp?thread=285735&forum=13&message=1255488
    I have tried the following actions (mentionned in the other forum messages):
    - To preserve changes to weblogic*.xml, the safest way is to change the ejb-borland.xml.
    (I am not sure that I have applied this advice correctly, because I suppose that syntax is not similar in weblogic file or borland file).
    And you can MANUALLY update the weblogic file in your JAR archive.
    1. Open the EJB JAR file in Winzip and extract the weblogic-ejb-jar.xml file, so that a copy exists in your
    project directory.
    2. Open this file (in Notepad), add the WebLogic specific information, and then save the file.
    3. Now, when you are finished with the build cycle and are ready to deploy, you may open the EJB jar file
    and swap in the weblogic-ejb-jar.xml file."
    Good Luck.

  • URGENT:  Error while deploying ear with weblogic service control

    We have build an ear within workshop and deployed to another server. When accessing the application we are getting the following error:
    'com.bea.control.ServiceControlException: Could not find service ref in jndi: java:comp/env/service/hhs_wc_controls_SearchServiceControl[javax.naming.NameNotFoundException: While trying to look up comp/env/service/hhs_wc_controls_SearchServiceControl in /app/webapp/WCWeb/5120123.; remaining name 'comp/env/service/hhs_wc_controls_SearchServiceControl'] '
    The service control is connecting a WSDL to consume a web service.
    Does the service control create a JNDI entry or some file is not getting built into the ear?
    We are using WLP 10.3
    Your help is much appreciated.
    Thanks,
    - Shankar
    Edited by: user1269940 on Nov 6, 2009 12:39 PM

    Hi Shankar
    When a WebService Control is created based on .wsdl file, it generates a .JAR file with all jaxb generated classes and .java files with service and port classes. This .jar file will be under web-inf/lib folder. Then I guess you are using this WebService control in your Pageflow and invoke webservice operations. So do you have like a portlet for this pageflow and testing from a portal. I have a similar scenario but I did not get any error that you are seeing. I consume SOA BPEL webservices in one of my pageflows using Service Controls.
    To debug, first test if the wsdl is working by directly invoking the wsdl operations using a utility servlet by name "wls_utc" which you can invoke from any of your wls/wlp domain. Start your domain assuming localhost and port is 7001. The url for testing webservices is:
    http://localhost:7001/wls_utc. This works if domain is in Dev Mode only. This page opens a jsp page, where you can type your wsdl url (http://host:port/context/a/b/xyx?wsdl). This page parses that wsdl and shows all operations and for each operation the fields for input parameters. See if this wsdl works fine.
    As for deployment, there is no additional step required. Just ear your application that has .war file and that has web-inf/lib folder with actual webservice control generate .jar file. I did no tconfigure any additional JNDI lookups like that.
    Thanks
    Ravi Jegga

  • EAR Deployment Problem with weblogic 10.2. Need help.

    Hi,
    I have a EAR file exported from MyEclipse IDE. When i am deploying the EAR file in weblogic 10.2, i am not seeing classess and properties were not exploded under WEB-INF/classes in the web project. I can see the classes folder but it's empty.
    When i opened i can see EJB project JAR file and web project .war file in the EAR file. I checked the .war file content and i can see all the classes and properties available in the .war file.
    Please help me to find, why the classes and properties are not being exploded when i am deploying as package.
    Note: When i am deploying from myeclipse as exploded deployment i was able to run the application but i am failing when i deploy as a package (.ear file).
    Thank you,
    Vijay M

    I found the answer to this. The documentation is not clear enough, LD_LIBRARY_PATH MUST be set and MUST have a pointer to the directory where the SSL .so modules are. I wrote up a blog article explaining the configuration and detailed this issue.
    http://blogs.oracle.com/irm/2010/06/quick_guide_to_oracle_irm_11g_1.html

  • Deploying BRM JCA on Weblogic 10.3

    We are trying to prototype invoking APIs through Webservices exposed by BRM JCA.
    In the Oracle BRM manual it is mentioned that certain Jars need to be present in order for BRM JCA to deploy successfully.
    1. J2EE application server
    classes12.jar, connector15.jar, and jta.jar
    2. Oracle BPEL process
    bpm-infra.jar, orabpel-thirdparty.jar, orabpel.jar, and xmlparserv2.jar
    3. Apache
    xercesImpl.jar
    We have only classes12.jar, jta.jar, xercesImpl.jar.
    My question is whether it is absolutely necessary for these jars to be present, and if so where can I find it.
    Right now we are getting Deployment error when we try to deploy BRM JCA on Weblogic 10.3
    <Dec 10, 2010 2:17:07 PM GMT+05:30> <Warning> <Connector> <BEA-190155> <Compliance checking/validation of the resource a
    dapter E:\BRM74Tools\JCA\jca_adapter\OracleBRMJCA15Adapter.rar resulted in the following warnings:
    The ra.xml <resourceadapter-class> class 'oracle.tip.adapter.brm.BRMResourceAdapter' should implement java.io.Serializab
    le but does not.>
    <Dec 10, 2010 2:17:07 PM GMT+05:30> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment req
    uest with ID '1291970826812' for task '0'. Error is: 'weblogic.application.ModuleException: [1] The ra.xml <connectionfa
    ctory-interface> class 'oracle.tip.adapter.api.OracleConnectionFactory' was not found in the resource adapter archive/ap
    plication.
    [2] The ra.xml <connectionfactory-impl-class> class 'oracle.tip.adapter.brm.BRMConnectionFactory' could not be loaded fr
    om the resource adapter archive/application because of the following error: java.lang.NoClassDefFoundError: oracle/tip/a
    dapter/api/OracleConnectionFactory'
    weblogic.application.ModuleException: [1] The ra.xml <connectionfactory-interface> class 'oracle.tip.adapter.api.OracleC
    onnectionFactory' was not found in the resource adapter archive/application.
    [2] The ra.xml <connectionfactory-impl-class> class 'oracle.tip.adapter.brm.BRMConnectionFactory' could not be loaded fr
    om the resource adapter archive/application because of the following error: java.lang.NoClassDefFoundError: oracle/tip/a
    dapter/api/OracleConnectionFactory
    at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.java:229)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:508)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
    Truncated. see log file for complete stacktrace
    >
    <Dec 10, 2010 2:17:07 PM GMT+05:30> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy ta
    sk for application 'OracleBRMJCA15Adapter'.>
    <Dec 10, 2010 2:17:07 PM GMT+05:30> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException: [1] The ra.xml <connectionfactory-interface> class 'oracle.tip.adapter.api.OracleC
    onnectionFactory' was not found in the resource adapter archive/application.
    [2] The ra.xml <connectionfactory-impl-class> class 'oracle.tip.adapter.brm.BRMConnectionFactory' could not be loaded fr
    om the resource adapter archive/application because of the following error: java.lang.NoClassDefFoundError: oracle/tip/a
    dapter/api/OracleConnectionFactory
    at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.java:229)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:508)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
    Truncated. see log file for complete stacktrace
    >
    <Dec 10, 2010 2:17:07 PM GMT+05:30> <Error> <Console> <BEA-240003> <Console encountered the following error weblogic.app
    lication.ModuleException: [1] The ra.xml <connectionfactory-interface> class 'oracle.tip.adapter.api.OracleConnectionFac
    tory' was not found in the resource adapter archive/application.
    [2] The ra.xml <connectionfactory-impl-class> class 'oracle.tip.adapter.brm.BRMConnectionFactory' could not be loaded fr
    om the resource adapter archive/application because of the following error: java.lang.NoClassDefFoundError: oracle/tip/a
    dapter/api/OracleConnectionFactory
    at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.java:229)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:508)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1223)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
    at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:43)
    at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperatio
    n.java:208)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:749)
    at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:16
    0)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(Deploymen
    tReceiverCallbackDeliverer.java:171)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiv
    erCallbackDeliverer.java:13)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCal
    lbackDeliverer.java:47)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >

    Hi jamavalom,
    I have exactly the same problem with deployment of JCA Adapter, except I collected all requested jar files, and put them in WEBLOGIC_CLASSPATH inside /wlserver_10.3/common/bin/commEnv.sh file, and afterward restarted the WebLogic server. Here are the contents of configuration *.xml files:
    ra.xml:
    <?xml version="1.0" encoding="UTF-8"?>
    <connector xmlns="http://java.sun.com/xml/ns/j2ee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd"
    version="1.5">
    <display-name>Oracle BRM Adapter</display-name>
    <vendor-name>Oracle CGBU</vendor-name>
    <eis-type>Oracle BRM</eis-type>
    <resourceadapter-version>1.0</resourceadapter-version>
    <resourceadapter>
    <resourceadapter-class>oracle.tip.adapter.brm.BRMResourceAdapter</resourceadapter-class>
    <outbound-resourceadapter>
    <connection-definition>
    <managedconnectionfactory-class>
    oracle.tip.adapter.brm.BRMManagedConnectionFactory
    </managedconnectionfactory-class>
    <!-- protocol, hostname and port -->
    <config-property>
    <config-property-name>ConnectionString</config-property-name>
    <config-property-type>java.lang.String</config-property-type>
    <config-property-value>ip hostname 12007</config-property-value>
    </config-property>
    <config-property>
    <config-property-name>PoidID</config-property-name>
    <config-property-type>java.lang.Long</config-property-type>
    <config-property-value>1</config-property-value>
    </config-property>
    <config-property>
    <config-property-name>ServiceType</config-property-name>
    <config-property-type>java.lang.String</config-property-type>
    <config-property-value>/service/pcm_client</config-property-value>
    </config-property>
    <!-- Login type 1 - Authentication by username/password,
    0 - authentication by service and poid id0 -->
    <config-property>
    <config-property-name>LoginType</config-property-name>
    <config-property-type>java.lang.Integer</config-property-type>
    <config-property-value>1</config-property-value>
    </config-property>
         <!-- ConnectionPoolMaxsize - Pool Max size used by pfc.jar -->
    <config-property>
    <config-property-name>ConnectionPoolMaxsize</config-property-name>
    <config-property-type>java.lang.Integer</config-property-type>
    <config-property-value>50</config-property-value>
    </config-property>
         <!-- ConnectionPoolMinsize - Pool Mn size used by pfc.jar -->
    <config-property>
    <config-property-name>ConnectionPoolMinsize</config-property-name>
    <config-property-type>java.lang.Integer</config-property-type>
    <config-property-value>25</config-property-value>
    </config-property>
    <!-- UserName and Password for Login type 1 -->
    <config-property>
    <config-property-name>UserName</config-property-name>
    <config-property-type>java.lang.String</config-property-type>
    <config-property-value>root.0.0.0.1</config-property-value>
    </config-property>
    <config-property>
    <config-property-name>Password</config-property-name>
    <config-property-type>java.lang.String</config-property-type>
    <config-property-value>&amp;aes|08|0D5E11BFDD97D2769D9B0DBFBD1BBF7E5D40C305EDF3D77DF111AAB8F781E92122</config-property-value>
    </config-property>
    <!-- Input and Output schema validation-->
    <config-property>
    <config-property-name>InputValidation</config-property-name>
    <config-property-type>java.lang.Boolean</config-property-type>
    <config-property-value>false</config-property-value>
    </config-property>
    <config-property>
    <config-property-name>OutputValidation</config-property-name>
    <config-property-type>java.lang.Boolean</config-property-type>
    <config-property-value>false</config-property-value>
    </config-property>
         <!-- MultiDB - true - Transaction opened on the incoming database
                   - false- Transaction opened on default DB -->
    <config-property>
    <config-property-name>MultiDB</config-property-name>
    <config-property-type>java.lang.Boolean</config-property-type>
    <config-property-value>false</config-property-value>
    </config-property>
         <!-- AverageOpcodeCount - Determines number of managed connections
                        created on the fly. Its the average number
                        of opcodes executed per thread -->
    <config-property>
    <config-property-name>AverageOpcodeCount</config-property-name>
    <config-property-type>java.lang.Integer</config-property-type>
    <config-property-value>5</config-property-value>
    </config-property>
    <connectionfactory-interface>
    oracle.tip.adapter.api.OracleConnectionFactory
    </connectionfactory-interface>
    <connectionfactory-impl-class>
    oracle.tip.adapter.brm.BRMConnectionFactory
    </connectionfactory-impl-class>
    <connection-interface>
    oracle.tip.adapter.brm.IBRMConnection
    </connection-interface>
    <connection-impl-class>
    oracle.tip.adapter.brm.BRMConnection
    </connection-impl-class>
    </connection-definition>
    <transaction-support>XATransaction</transaction-support>
    <authentication-mechanism>
    <authentication-mechanism-type>
    BasicPassword
    </authentication-mechanism-type>
    <credential-interface>
    javax.resource.spi.security.PasswordCredential
    </credential-interface>
    </authentication-mechanism>
    <reauthentication-support>false</reauthentication-support>
    </outbound-resourceadapter>
    </resourceadapter>
    </connector>
    weblogic-ra.xml:
    <weblogic-connector xmlns="http://www.bea.com/ns/weblogic/weblogic-connector" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-connector http://www.bea.com/ns/weblogic/weblogic-connector/1.0/weblogic-connector.xsd">
    <enable-access-outside-app>true</enable-access-outside-app>
    <enable-global-access-to-classes>true</enable-global-access-to-classes>
    <outbound-resource-adapter>
    <connection-definition-group>
    <connection-factory-interface>oracle.tip.adapter.api.OracleConnectionFactory</connection-factory-interface>
    <connection-instance>
    <jndi-name>eis/BRM</jndi-name>
    <connection-properties>
    <logging>
         <log-filename>eisBRM.log</log-filename>
                                  <logging-enabled>true</logging-enabled>
                                  <rotation-type>bySize</rotation-type>
                                  <number-of-files-limited>true</number-of-files-limited>
                                  <file-count>3</file-count>
                                  <file-size-limit>100</file-size-limit>
                                  <rotate-log-on-startup>true</rotate-log-on-startup>
                                  <log-file-rotation-dir>c:/mylogs</log-file-rotation-dir>
                                  <rotation-time>10:00</rotation-time>
                                  <file-time-span>24</file-time-span>
                             </logging>
                             <properties>
                                  <property>     
                   <name>ConnectionString</name>
                   <value>ip blrhpdv3.idc.oracle.com 12011</value>
                   </property>
                   <!-- Database number, Poid ID0 and Service type -->
                   <property>
                   <name>PoidID</name>
                   <value>1</value>
                   </property>
                   <property>
                   <name>ServiceType</name>
                   <value>/service/pcm_client</value>
                   </property>
                   <!-- Login type 1 - Authentication by username/password,
                   0 - authentication by service and poid id0 -->
                   <property>
                   <name>LoginType</name>
                   <value>1</value>
                   </property>
                   <property>
                   <name>ConnectionPoolMaxsize</name>
                   <value>20</value>
                   </property>
                   <property>
                   <name>ConnectionPoolMinsize</name>
                   <value>10</value>
                   </property>
                   <!-- UserName and Password for Login type 1 -->
                   <property>
                   <name>UserName</name>
                   <value>root.0.0.0.1</value>
                   </property>
                   <property>
                   <name>Password</name>
                   <value>&amp;aes|08|0D5E11BFDD97D2769D9B0DBFBD1BBF7E5D40C305EDF3D77DF111AAB8F781E92122</value>
                   </property>
                   <!-- Input and Output schema validation-->
                   <property>
                   <name>InputValidation</name>
                   <value>false</value>
                   </property>
                   <property>
                   <name>OutputValidation</name>
                   <value>false</value>
                   </property>
                   <property>
                   <name>MultiDB</name>
                   <value>false</value>
                   </property>
                   <!-- The AverageOpcodeCount parameter specifies the number of Opcode calls in a Thread -->
                   <property>
                   <name>AverageOpcodeCount</name>
                   <value>1</value>
                   </property>
                        </properties>
                        </connection-properties>
                        </connection-instance>
                   </connection-definition-group>
              </outbound-resource-adapter>
    </weblogic-connector>
    Thank you in advance for help,
    BR,
    Mario

  • Deploy web application in jbuilder 9 with weblogic 7 problem

    when i create a web application and a servlet, and deploy it in jbuilder 9 with weblogic 7.0 ,jbuilder 9 showed me the error,please tell me why, when i choose "redeploy" ,it can be normally work..
    E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -deploy -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
    WebLogic Application Deployment Utility
    Usage: java weblogic.Deployer [options] [-activate|-deactivate|-remove|-unprepare|-cancel|-list] [files]
    where options include:
    -help Print this help message.
    -version Print version information.
    -adminurl <https://<server>:<port>> The URL of the administration server: default
    http://localhost:7001
    -user <user> A user other than the default of
    "installadministrator"
    -password <password> Specifies the password on the command line.
    If this option is absent the user is
    prompted.
    -verbose Displays additional status during the
    deployment process, including notifications
    when the application is prepared and
    activated on each target.
    -debug Displays debug level messages to the standard
    output.
    -examples Display example usage of this tool.
    -upload Causes the specified source file(s) to be
    transferred to the adminstration server. This
    is used when the Deployer tools is not being
    used on the same machine as the adminstration
    server and the user does not otherwise have
    access to place the targeted files on the
    adminstration server.
    -delete_files Causes the server to remove the files that
    are specified in the file list and leave the
    application activated. This option is valid
    only for unarchived web applications.
    -remote Signals that the tools is not runnning on the
    same machine as the adminstration server and
    that the source path should be made passed
    through unchanged as it represents the path
    on the remote server.
    -nostage Sets the stagingMethod attribute on the
    application mbean when it is created so that
    the application will not be staged and the
    original source is be used.
    -external_stage Sets the stagingMethod attribute on the
    application mbean when it is created so that
    the application will not be staged but the
    value of the staging path will be used when
    preparing the application.
    -stage Sets the stagingMethod staging attribute on
    the application when it is created so that
    the application will always be staged. This
    value will override the stagingMethod
    attribute on any targeted servers.
    -nowait Once the action is initiated the tool will
    print the task id and exit. This is used to
    initiate multiple tasks and then monitor them
    later using the -list action.
    -timeout <seconds> The maximum time in seconds to wait for the
    completion of the deployment task. When the
    time expires the current status is printed
    and the program exits.
    -source <archive file or directory> Location of the file or directory that
    represents the enterprise component or
    application tha is being (re)activated. If
    the source file is relative it is relative to
    the current directory, unless the -remote
    option is used. To specify individual files
    within an application for reployment or
    addition list them at the end of the command
    line.
    -name <application name> The name of the application being deployed.
    -targets <<server 1>,...<component>@<server N>> A comma separated list of the server and/or
    cluster names. Each target may be qualified
    with a J2EE component name. This enables
    different components of the archive to
    deployed on different servers.
    -id <task identifier> Optional client supplied unique identifier
    for the deployment task. The id is first
    specified to -activate, -deactivate,
    -unprepare or -remove. It is then used later
    as an argument to -cancel or -list.
    -activate (Re)activates the <source> application on the
    <targets> with the <name>.
    -deactivate Deactivates the application <name> on the
    <targets> leaving an staged application files
    in a state where the may be quickly
    reactivated.
    -unprepare Deactivates and unloads classes for the
    application <name> on the <targets> leaving
    an staged application files in a state where
    the may be quickly reloaded.
    -remove Deactivates the application <name> on the
    <target> and removes any files that were
    staged for this application. If there are no
    longer any targets for the application, the
    associated configuration is completely
    removed.
    -cancel Atempts to cancel the task <id> if it is has
    not yet completed.
    -list Lists the target status of each task <id>
    -deploy a convenient alias for activate.
    -undeploy a convenient alias for unprepare.
    Optionally a list of the specific files in the archive that are to be
    redeployed may be specified. If a directory is specified the entire subtree is
    redeployed.
    Full documentation on this tool is available at:
    http://edocs.beasys.com/wls/docs70/adminguide/utils.html#1138475
    No actions was specified. Please specify one and only one of:
    -activate, -deactivate, -cancel, -remove, -unprepare, or -list.
    Type java weblogic.Deployer -examples for example usage.

    you use "deploy" under DOS-Mode to deploy your web application?
    i found some differences between "deploy" and "redeploy" function in jbuilder 9.
    when i choose "deploy" ,jbuilder shows me the commond below:
    E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -deploy -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
    WebLogic Application Deployment Utility
    when i choose redeploy,it shows me: (the -deploy parameter has changed to -activate) ,maybe it's a bug.
    E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -activate -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
    WebLogic Application Deployment Utility

  • Re: Error while Deploying OEDQ with a deployement plan on weblogic

    Hi All,
    I am getting this Exception while deployment and look like this is same type of exception
    weblogic.application.ModuleException: Unmarshaller failed
    [fa:deploy] <fusion_domain>: <fusion_domain>: Exception while performing deployJ2EE for application AdvancedPlanningApp : java.lang.Exception: Deployment FAILED:weblogic.application.ModuleException: [HTTP:101064][WebAppModule(AdvancedPlanningApp:advancedPlanning)] Error parsing descriptor in Web appplication "/scratch/software/mw_local/FMWTOOLS_11.1.1.7.0_GENERIC_130327.1838_PATCHES4FA_11.1.1.7.0_PLATFORMS_JDK64/bitukuma/mw_home_standalone/user_projects/domains/fusion_domain/servers/AdminServer/upload/AdvancedPlanningApp/app/AdvancedPlanningApp/EarScmAps.war"
    [fa:deploy] weblogic.application.ModuleException: Unmarshaller failed
    [fa:deploy]     at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1345)
    [fa:deploy]     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:375)
    [fa:deploy]     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180)
    [fa:deploy]     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
    [fa:deploy]     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
    [fa:deploy]     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    [fa:deploy]     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
    [fa:deploy]     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
    [fa:deploy]     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649)
    [fa:deploy]     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    [fa:deploy]     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
    [fa:deploy]     at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:59)
    [fa:deploy]     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
    [fa:deploy]     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
    [fa:deploy]     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:209)
    [fa:deploy]     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
    [fa:deploy]     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    [fa:deploy]     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:749)
    [fa:deploy]     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
    [fa:deploy]     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
    [fa:deploy]     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160)
    [fa:deploy]     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
    [fa:deploy]     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
    [fa:deploy]     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:47)
    [fa:deploy]     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
    [fa:deploy]     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
    [fa:deploy]     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    [fa:deploy] Caused by: weblogic.descriptor.BeanAlreadyExistsException: Bean already exists: "weblogic.j2ee.descriptor.FilterBeanImpl@82a9ceb4(/Filters[ADFLibraryFilter])"
    [fa:deploy]     at weblogic.descriptor.internal.ReferenceManager.registerBean(ReferenceManager.java:231)
    [fa:deploy]     at weblogic.j2ee.descriptor.WebAppBeanImpl.setFilters(WebAppBeanImpl.java:715)
    [fa:deploy]     at sun.reflect.GeneratedMethodAccessor249.invoke(Unknown Source)
    [fa:deploy]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [fa:deploy]     at java.lang.reflect.Method.invoke(Method.java:597)
    [fa:deploy]     at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:48)
    [fa:deploy]     at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.setValue(RuntimeBindingType.java:539)
    [fa:deploy]     at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType$QNameRuntimeProperty.fillCollection(AttributeRuntimeBindingType.java:382)
    [fa:deploy]     at com.bea.staxb.runtime.internal.MultiIntermediary.getFinalValue(MultiIntermediary.java:52)
    [fa:deploy]     at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType.getFinalObjectFromIntermediary(AttributeRuntimeBindingType.java:140)
    [fa:deploy]     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:200)
    [fa:deploy]     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:169)
    [fa:deploy]     at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
    [fa:deploy]     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:150)
    [fa:deploy]     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
    [fa:deploy]     at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
    [fa:deploy]     at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
    [fa:deploy]     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
    [fa:deploy]     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
    [fa:deploy]     at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)
    [fa:deploy]     at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1331)
    Please help me to resolve this error.
    Thanks

    Your error does not appear to be to do with EDQ at all. I do not recognise the name of the war file giving you the error. Which version of EDQ are you deploying?
    Please do not use the public forum if you need support with an internal deployment of a pre-release version.

  • Not able to deploy application with fast-swap enabled - weblogic 10.3

    Hi ,
    When i am trying to deploy my exploded directory by adding      
    <fast-swap>
    <enabled>true</enabled>
    </fast-swap>
    to weblogic.xml , i am getting following error
    ClassLoader [com.bea.wls.redef.RedefiningClassLoader] does NOT provide an 'addTransformer(ClassFileTransformer)' method. Specify a custom LoadTimeWeaver or start your Java virtual machine with Spring's agent
    if remove fast-swap from my weblogic.xml it deploying successfully.

    Full stack trace
    <Apr 27, 2013 10:09:52 PM EDT> <Warning> <HTTP> <BEA-101162> <User defined listener org.springframework.web.context.ContextLoaderListener failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.context.weaving.AspectJWeavingEnabler#0': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'loadTimeWeaver': Initialization of bean failed; nested exception is java.lang.IllegalStateException: ClassLoader [com.bea.wls.redef.RedefiningClassLoader] does NOT provide an 'addTransformer(ClassFileTransformer)' method. Specify a custom LoadTimeWeaver or start your Java virtual machine with Spring's agent: -javaagent:spring-agent.jar.
    org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.context.weaving.AspectJWeavingEnabler#0': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'loadTimeWeaver': Initialization of bean failed; nested exception is java.lang.IllegalStateException: ClassLoader [com.bea.wls.redef.RedefiningClassLoader] does NOT provide an 'addTransformer(ClassFileTransformer)' method. Specify a custom LoadTimeWeaver or start your Java virtual machine with Spring's agent: -javaagent:spring-agent.jar
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:480)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
         at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
         Truncated. see log file for complete stacktrace
    org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'loadTimeWeaver': Initialization of bean failed; nested exception is java.lang.IllegalStateException: ClassLoader [com.bea.wls.redef.RedefiningClassLoader] does NOT provide an 'addTransformer(ClassFileTransformer)' method. Specify a custom LoadTimeWeaver or start your Java virtual machine with Spring's agent: -javaagent:spring-agent.jar
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:480)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
         at java.security.AccessController.doPrivileged(Native Method)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
         at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
         Truncated. see log file for complete stacktrace
    java.lang.IllegalStateException: ClassLoader [com.bea.wls.redef.RedefiningClassLoader] does NOT provide an 'addTransformer(ClassFileTransformer)' method. Specify a custom LoadTimeWeaver or start your Java virtual machine with Spring's agent: -javaagent:spring-agent.jar
         at org.springframework.context.weaving.DefaultContextLoadTimeWeaver.setBeanClassLoader(DefaultContextLoadTimeWeaver.java:82)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1322)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
         at java.security.AccessController.doPrivileged(Native Method)
         Truncated. see log file for complete stacktrace
    >
    <Apr 27, 2013 10:09:52 PM EDT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1367114948992' for task '11'. Error is: 'weblogic.application.ModuleException: '
    weblogic.application.ModuleException:
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1373)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
         Truncated. see log file for complete stacktrace
    java.lang.IllegalStateException: ClassLoader [com.bea.wls.redef.RedefiningClassLoader] does NOT provide an 'addTransformer(ClassFileTransformer)' method. Specify a custom LoadTimeWeaver or start your Java virtual machine with Spring's agent: -javaagent:spring-agent.jar
         at org.springframework.context.weaving.DefaultContextLoadTimeWeaver.setBeanClassLoader(DefaultContextLoadTimeWeaver.java:82)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1322)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
         at java.security.AccessController.doPrivileged(Native Method)
         Truncated. see log file for complete stacktrace
    >
    <Apr 27, 2013 10:09:52 PM EDT> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application 'PDC_1306'.>
    <Apr 27, 2013 10:09:52 PM EDT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'PDC_1306'.>
    <Apr 27, 2013 10:09:52 PM EDT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException:
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1373)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
         Truncated. see log file for complete stacktrace
    java.lang.IllegalStateException: ClassLoader [com.bea.wls.redef.RedefiningClassLoader] does NOT provide an 'addTransformer(ClassFileTransformer)' method. Specify a custom LoadTimeWeaver or start your Java virtual machine with Spring's agent: -javaagent:spring-agent.jar
         at org.springframework.context.weaving.DefaultContextLoadTimeWeaver.setBeanClassLoader(DefaultContextLoadTimeWeaver.java:82)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1322)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
         at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
         at java.security.AccessController.doPrivileged(Native Method)
         Truncated. see log file for complete stacktrace

  • Deploying session beans with weblogic 5.1 in NT

    Hello ,
    I have a problem with deploying session beans in weblogic 5.0. I have
    written the code and compiled it. My Compilation is fine. Cud any one give
    me a step by step of how I should deploy my bean with weblogic 5.0 on
    windows NT.
    Raj Urs

    Hello ,
    I have a problem with deploying session beans in weblogic 5.0. I have
    written the code and compiled it. My Compilation is fine. Cud any one give
    me a step by step of how I should deploy my bean with weblogic 5.0 on
    windows NT.
    Raj Urs

Maybe you are looking for