WLS 10 and ejb 3 projct deployment problem

hi all, my env. looks like :
vls version : 10
java version : 1.6.0.04
operating system : Solaris SPARC 64-bit.
problem :
when i try to deploy my simplest ejb 3 project i got this error :
weblogic.management.DeploymentException: [Deployer:149189]Attempt to operate 'distribute' on null BasicDeploymentMBean for deployment Test.
at weblogic.deploy.internal.targetserver.DeploymentManager.assertDeploymentMBeanIsNonNull(DeploymentManager.java:1281)
at weblogic.deploy.internal.targetserver.DeploymentManager.findDeploymentMBean(DeploymentManager.java:1322)
at weblogic.deploy.internal.targetserver.DeploymentManager.createOperation(DeploymentManager.java:1022)
at weblogic.deploy.internal.targetserver.DeploymentManager.createOperations(DeploymentManager.java:1368)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleUpdateDeploymentContext(DeploymentManager.java:160)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.updateDeploymentContext(DeploymentServiceDispatcher.java:153)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doUpdateDeploymentContextCallback(DeploymentRe
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.updateDeploymentContext(DeploymentReceiverCall
at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.callDeploymentReceivers(ReceivedPrepare.java:199)
at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.handlePrepare(ReceivedPrepare.java:110)
at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.receivedPrepare(ReceivedPrepare.java:52)
at weblogic.deploy.service.internal.targetserver.TargetRequestImpl.run(TargetRequestImpl.java:211)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$1.run(CommonMessageReceiver.java:408)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
i can't resolve this issues for a week, pls help me.
everything works fine at home on my PC where i have windows XP Professional OS.
any idea will be appreciated.
Regards,
Paata.
Magticom LTD, Georgia.
Edited by paatal at 02/11/2008 5:56 AM
Edited by paatal at 02/11/2008 5:57 AM

Hi, Graeme.
Seems there is an existing CR on something related from v10.0: CR353213
* WLS 10.0 - EJB 3.0 deployment fails when parsing class for Stateless annotation
According to http://edocs.bea.com/wls/docs103/issues/known_resolved.html, this is not addressed in 10.3
Closely review your classpath, and then (assuming you have access to the source) review the body of your ejb. If it is related to this CR, you may be able to workaround the issue by shortening the body and split large methods into more sub-methods.
I hope this helps,
-Adrian

Similar Messages

  • BEA WLS 6.1 SP2: Deploy problems (JDBCConnectionPool/JDBCTxDataSource)

    Hello anybody,
    learnt XA being necessary if more than one sql command in transaction, so I changed
    my entries to the following:
    <JDBCConnectionPool
    DriverName="oracle.jdbc.xa.client.OracleXADataSource"
    Name="OracleDB"
    Password="{3DES}iKOCmvzSc6g="
    Properties="user=osv"
    Targets="osvServer"
    TestConnectionsOnReserve="false"
    URL="jdbc:oracle:thin:@pegnitz:1526:ora1"/>
    <JDBCTxDataSource
    JNDIName="JNDINameOracleOSV-DB"
    Name="OracleDataSource"
    PoolName="OracleDB"
    Targets="osvServer"/>
    We set up on a database ORACLE 8.3.2.
    Now, with the non-XA-driver there was no deployment problem, but now I receive the
    following error message on the server output:
    Unable to deploy EJB: CourseDateEJB from osv.jar:
    The Container-Managed Persistence Entity EJB failed while creating its SQL Type Map.
    The error was:
    XA error: XAER_RMERR : A resource manager error has occured in the transaction branch
    start() failed on resource 'OracleDB' Unexpected error during start for XAResource
    'OracleDB': null
         at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1019)
         at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
         at weblogic.j2ee.Application.deploy(Application.java:247)
         at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:185)
         at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:362)
         at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:296)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1388)
         at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:881)
         at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
         at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
         at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:392)
         at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:298)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
         at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Many thanks if s.b. could help me.
    Klaus

    Hi Klaus,
    if you want to implement a global transaction over two different JDBC Resource Managers
    (update on both + 2PC) they have to be both XA compliant.
    Or you could have only one of them XA compliant(i.e: one 8.1.6 or higher Oracle instance):
    for the other one (i.e.: one 7.3.2 Oracle instance) you could use a non XA-driver
    and configuring a TXDataSource with "enable two-phase commit" = true (but only one
    non-XA JDBC driver at a time can participate in a distributed transaction).
    Well, XA transactions are not a pre-requisite for EJB: you could use simple "local"
    transactions or distributed transactions without XA drivers as well (using a single
    resource manager).
    But if you want to update multiple resource managers in the same transaction using
    EJBs, this is a "global" transaction, and WL server fully supports it.
    But the partecipants must be XA compliant to be able to "talk" to WL coordinator.
    Sergi
    Sergi
    "Klaus Dirlewanger" <[email protected]> wrote:
    >
    Hi Sergi, hello world,
    thanks a lot for this message. So the conclusion is that I hava no chance
    at all
    to use this oracle version (7.3.2) with BEA WLS (or more common EJB), cause
    a prerequisite
    for EJB are XA-transactions.
    Is this conclusion correct.
    Many thanks again
    Klaus
    "Sergi Vaz" <[email protected]> wrote:
    Hi Klaus,
    distributed transaction (XA) features require version
    Oracle8i release 8.1.6 or later of the Oracle server.
    Sergi
    "Klaus Dirlewanger" <[email protected]> wrote:
    Hi Sergi,
    1.) sorry, that was a typing error with the oracle version, I meant 7.3.2.
    2.) I didn´t use a special driver but that that was delivered with thewls
    server
    in the package "weblogic.jar".
    Could I enable you helping me with this information?
    Best wishes
    Klaus
    "Sergi Vaz" <[email protected]> wrote:
    Hi Klaus,
    which
    1) Oracle server version (I don't think it's a 8.3.2.)
    2) Oracle JDBC driver version
    are you you using ?
    Sergi
    "Klaus Dirlewanger" <[email protected]> wrote:
    Hello anybody,
    learnt XA being necessary if more than one sql command in transaction,so
    I changed
    my entries to the following:
    <JDBCConnectionPool
    DriverName="oracle.jdbc.xa.client.OracleXADataSource"
    Name="OracleDB"
    Password="{3DES}iKOCmvzSc6g="
    Properties="user=osv"
    Targets="osvServer"
    TestConnectionsOnReserve="false"
    URL="jdbc:oracle:thin:@pegnitz:1526:ora1"/>
    <JDBCTxDataSource
    JNDIName="JNDINameOracleOSV-DB"
    Name="OracleDataSource"
    PoolName="OracleDB"
    Targets="osvServer"/>
    We set up on a database ORACLE 8.3.2.
    Now, with the non-XA-driver there was no deployment problem, but now
    I
    receive
    the
    following error message on the server output:
    Unable to deploy EJB: CourseDateEJB from osv.jar:
    The Container-Managed Persistence Entity EJB failed while creating itsSQL
    Type Map.
    The error was:
    XA error: XAER_RMERR : A resource manager error has occured in the transaction
    branch
    start() failed on resource 'OracleDB' Unexpected error during start
    for
    XAResource
    'OracleDB': null
         at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1019)
         at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
         at weblogic.j2ee.Application.deploy(Application.java:247)
         at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:185)
         at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:362)
         at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:296)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1388)
         at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:881)
         at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
         at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
         at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:392)
         at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:298)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
         at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown
    Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Many thanks if s.b. could help me.
    Klaus

  • JDBC, JMS and EJB transactions - possible problem?

    Hello,
              I am using Oracle 9, Weblogic 8.1 SP 4, MyEclipse and
              XDoclet.
              In my current project I have the following piece of code
              in one of my message driven beans (code cited as pseudocode
              without unnecessary details):
              * @ejb.bean name="MyMessageProcessor"
              * display-name="Display name for a MyMessageProcessor"
              * jndi-name="ejb/MyMessageProcessor"
              * description="Bean MyMessageProcessor"
              * destination-type="javax.jms.Queue"
              * transaction-type="Container"
              * acknowledge-mode="Auto-acknowledge"
              * subscription-durability="Durable"
              * generate="false"
              * @ejb.transaction type="Required"
              public class MyMessageProcessor implements MessageDrivenBean, MessageListener {
              public void onMessage(Message msg) {
                   try {
                        //obtaining connections to two different databases via JNDi
                        java.sql.Connection connOne =
                        ((DataSource)ctx.lookup("DataSourceOne")).getConnection();          
                        java.sql.Connection connTwo =
                             ((DataSource)ctx.lookup("DataSourceTwo")).getConnection();
                        // performing some UPDATEs and INSERTs on connOne and connTwo
                        // calling some other methods of this bean
                        //creating the reply JMS message and sending it to another JMS queue
                        Message msgTwo = this.createReplyMessage(msg)
                        this.queueSender.send(msgTwo);
                        //commiting everything
                        this.queueSession.commit();          
                   } catch (Exception ex) {
                   try {
                        if (this.queueSession!=null) this.queueSession.rollback();
                   } catch (JMSException JMSEx) {};     
                   this.context.setRollbackOnly();
              Some days ago (before the final remarks from my client) there used to be only one DataSource configurated on the basis of the
              connection pool with non-XA jdbc driver. Everything worked fine
              including the transactions (if anything wrong happend not only wasn't the replymessage sent, but also no changes were written
              to database and the incomming message was thrown back to the my bean's
              queue).
              When I deployed the second DataSource I was informed by an error message, that only one non-transactional resource may
              participate in a global transaction. When I changed both datasources
              to depend on underlying datasources with transatcional (XA) jdbc drivers, everything stopped working. Even if
              EJB transaction was theoretically successfully rolledbacked, the changed were written to the database
              and the JMS message wasn't resent to the JMS queue.
              So here are my questions:
                   1. How to configure connection pools to work in such situations? What JDBC drivers should I choose?
                   Are there any global server configurations, which may influence this situation?
                   2. Which jdbc drivers should I choose so that the container was able to rollback the database transactions
                   (of course, if necessary)?
                   3. Are there any JMS Queue settings, which would disable the container to send message back to the
                   queue in case of setRollbackOnly()? How should be the Queue configurated?
              As I am new to the topic and the deadline for the project seems to be too close I would be grateful
              for any help.
              This message was sent to EJB list and JDBC list.
              Sincerely yours,
              Marcin Zakidalski

    Hi,
              I found these information extremely useful and helpful.
              The seperate transaction for sending messages was, of course, unintentional. Thanks a lot.
              Anyway, I still have some problems. I have made some changes to the
              code cited in my previous mail. These changes included changing QueueSessions
              to non-transactional. I also set the "Honorate global transactions" to true.
              I am using XA JDBC driver. After setting "Enable local transactions" to false
              (I did it, because I assume that JDBC transactions should be part on the global
              EJB transaction) I got the following error:
              java.sql.SQLException: SQL operations are not allowed with no global transaction by default for XA drivers. If the XA
              driver supports performing SQL operations with no global transaction, explicitly allow it by setting
              "SupportsLocalTransaction" JDBC connection pool property to true. In this case, also remember to complete the local
              transaction before using the connection again for global transaction, else a XAER_OUTSIDE XAException may result. To
              complete a local transaction, you can either set auto commit to true or call Connection.commit() or Connection.rollback().
              I have also inspected the calls of methods of bean inside of onMessage() method just to check, whether
              the transactions are correctly initialized (using the weblogic.transaction.Transaction class).
              My questions are as follows:
              1. Any suggestions how to solve it? I have gone through the google answers on that problem and only
              thing I managed to realize that JDBC must start its own transaction. Is there any way to prohibit it
              from doing that? Can using setAutocommit(true/false) change the situation for better?
              2. How to encourage the JDBC driver to be a part of EJB transaction?
              3. As I have noticed each of ejb method has its own transactions (transactions have different
              Xid). Each method of the bean has "required" transaction attribute. Shouldn't it work in such
              way that if already started transaction exists it is used by the called method?
              4. The DataSources are obtained in my application via JNDI and in the destination environment I will have slight
              impact on the configuration of WebLogic. What is least problematic and most common WebLogic configuration which would
              enable JDBC driver to participate in the EJB transaction? Is it the WebLogic configuration problem or can it be
              solved programmically?
              Currently my module works quite fine when "enable local transactions" for DataSources is set to true, but this way
              I am loosing the ability to perform all actions in one transaction.
              Any suggestions / hints are more than welcomed. This message was posted to jdbc list and ejb list.
              Marcin

  • 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

  • Servlet and EJB on different machine: Security propagation

    Hi all,
    I have an application, where my servlets and EJBS are deployed on the same machine.So
    when in my servlet a user need to authenticate himself, security credentials are
    propagated to the EJB automatically.I'd like to know in the case where the components
    are on different machine if I need to put the credential in my InitialContext
    when my servlet calls my EJB or if it is also done automatically.
    Cheers
    romain

    Say your stub is in a jar called stub.jar.
    You need to put that stub somewhere that it can be reached through a protocol for which Java has a URL type - so you can put it on a shared file system and use a file URL or behind an http server and use an http URL.
    Let's use http - put stub.jar at the docroot of a web server.
    Then, when you start your SERVER code, include this VM parameter:
    -Djava.rmi.server.codebase="http://<serveraddress>stub.jar"
    Now your client will be able to use http to load the stub file out of stub.jar through http.
    If you do use a file URL, make sure the shared directory you put your jar in is not on the client's classpath.

  • Ejb and jsproc deployment problems

    Am trying to deploy the java stored procedure (jsp) example
    (jsproc subdirectory in acmevideo directory) and the enterprise
    java bean (ejb) example (ejb subdirectory in acmevideo
    directory). Both use the business and util subdirectries of
    acmevideo directory. These examples are provided with
    JDeveloper.
    In the case of the jsp example, the files compile fine in
    JDeveloper. The deployment profile file is created okay using
    the Stored Procedure Profile Wizard. But when the jsp is
    attempted to be deployed by right clicking the deployment
    profile file menu in JDeveloper, the following errors appear:
    SQL error during creation of acmevideo/util/DataWrapper
    ORA-00922 - missing or invalid option
    SQL error during creation of acmevideo/business/TitleQueries
    ORA-00922 - missing or invalid option
    Is there a corrective action for these errors? Are the details
    recorded in any log so that these errors can be troubleshooted?
    In the case of the jbe example, the files compile fine in
    JDeveloper. The deployment profile file is created okay using
    the EJB Profile Wizard. But when the jsp is attempted to be
    deployed by right clicking the deployment profile file menu in
    JDeveloper, the following happens:
    The message indicating that the deployment will take a few
    minues continues to show forever. There is no completion,
    and one is forced to cancel the process.
    This happens when using the port settings of 1521, 1526 (Oracle
    listener ports) or 2651 (OAS ORB port). Specifying the service
    or omitting it yeilds the same results.
    Is there a corrective action for this? Are the details recorded
    in any log so that these errors can be troubleshooted?
    For both the situations, is the classpath variable need to set
    outside the JDeveloper environment?
    Also am not able to locate the Oracle 8i CORBA and Enterprise
    Java Beans Developer's Guide and the Oracle 8i Java Stored
    Procedure Developer's Guide referenced in Building Java
    Applications for Oracle 8i anywhere.
    Would appreciate any help in this area.
    null

    : Has anyone been able to deploy an ejb from JDeveloper2 (Beta)?
    We have ;) But I guess that doesn't count... Please have a look
    at the online demo for Enterprise JavaBeans on this technet
    website. You can get there through the JDeveloper Tech Info page.
    Please open a new thread if that doesn't help you.
    Thanks,
    -Roel.
    phil gulesian (guest) wrote:
    : mark tomlinson (guest) wrote:
    : : pretty sure the first one is a bug that is fixed in a later
    : : build of JDeveloper (JSP deployment problem).
    : : As for the EJB deployment problem, here is the way to catch
    : what
    : : is really going on (in the Beta build -- this will be done
    much
    : : better in the production build):
    : : -edit the jdeveloper.ini (in the BIN directory), in the
    : : [environment] section add:
    : : LogConsole=1
    : : -edit the jdeveloper.properties file (in the LIB directory)
    : : change the line :
    : : jdeveloper.logOutput=nul
    : : to
    : : jdeveloper.logOutput=-
    : : Now when you run JDeveloper, you will get an output onsole
    : : window for the JVM running JDeveloper. You will be able to
    see
    : : the deployment messages for the EJB wizard being sent to this
    : : console. This will allow you to troubleshoot what is
    happening.
    : I had the same experience as Bansi (above) when I tried to
    deploy
    : a simple ejb. Following your suggestions about looking in the
    : output console window for the JVM, I observed the message
    : "PropertyEditor for borland.sql.dataset.ProcedureDescriptor
    could
    : not be registered ........" A subsequent search found no
    : ProcedureDescriptor in the borland.sql.dataset package.
    : Has anyone been able to deploy an ejb from JDeveloper2 (Beta)?
    null

  • Sequence of startup classes and EJB deployment

    The default sequence when WLS is starting is deploying EJB first and then startUpClasses. Could someone tell me if it's possible to change the sequence.
    Thanks a lot in advance.

    Sure have your startup class do its work and then hot-deploy the EJB.
    -- Rob
    Jack wrote:
    >
    The default sequence when WLS is starting is deploying EJB first and then startUpClasses. Could someone tell me if it's possible to change the sequence.
    Thanks a lot in advance.

  • EJB/8i deployment and SSL

    Hello JDev Team,
    I want to use SSL encryption and authentication in my InfoSwing BC4J Oracle8i application.
    For Local Deployment it's quite transparent you just define appropriate LocalConnection class and SSL works fine.
    But for EJB/8i Deployment it's not that clear. As I understand EjbConnection class can accept user/password authentication only.
    Do I have to extend oracle.dacf.dataset.connections.Connection class and create my own SSL-oriented Connection with my own setConnectionSpecificEnvs method? Is that a possibility?
    Could you please give me some directions on this case?
    Thanks,
    Victor
    null

    Please check the "How to's" in the JDeveloper section of OTN (http://otn.oracle.com). That should shed some light.
    Happy researching,
    Rajesh

  • EJB in WLS - CORBA and EJB on WLE

    I have a client who is looking to attach a C++ client to their WLE
    system, and, since
    they now have WLS and WLE thanks to v. 5.1, they want to start moving
    EJBs to the
    WLS platform. The issue is this.
    What if any are the issues regarding communicating between CORBA objects
    on WLE
    TO EJBs on WLS? I noticed that the illustrations always show the
    communication coming
    from the WLS side to the WLE side, but this client will be connected
    directly to the WLE
    platform, and wanting to access services on WLS.
    Any issues, directions to documentation, or other advice regarding this
    issue?
    Thanks in advance,
    Maffy
    [maffy.vcf]

    can anyone give code example for accessing WLS-EJB from WLE corba client.
    louc wrote:
    Interesting how things can be interpreted. What we need is direct input
    from engineering on this.
    In studying the only direct source of information we have... (the docs...
    and ass-u-me'ing that the docs are correct) it appears that we can have a
    CORBA object in WLE access a EJB in WLS through RMI/IIOP as long as the
    parameter passing is kept to primitive data types. Any attempt to use the
    'Object-by-Value' feature of CORBA 2.3 will result in a error because WLE
    5.1 does not support passing 'Object-by-Value' at this time.
    So to answer Maffy's question... yes a WLE CORBA client can access a WLS EJB
    service through RMI over IIOP.
    -- Lou Caraballo
    Sr. Systems Engineer
    BEA Systems Inc., Denver Telco Group
    719-332-0818 (cell)
    720-528-6073 (denver)
    Robert Patrick <[email protected]> wrote in message
    news:[email protected]...
    The issue is that WLE does not yet support the RMI/IIOP standard (since itdoes not yet support
    Objects by Value) not that the RMI/IIOP support in WLS 5.1 (as of SP3)does not support
    bi-directional communication.
    Papaya Head wrote:
    so, you are saying bi-directional communication is not supported... can
    you tell me what
    rmi/iiop is for?
    Thanks.
    Maffy Finnerty wrote:
    Okay, found a work around thanks to Deepak Sharma (THANK YOU,
    DEEPAK!!) in the BEA
    East office.
    What my customer is going to have to do for now - until, as Will Lyonspointed out, the
    bi-directional
    communication is supported - is to build a Java "client" process onWLE that communicates
    with the
    RMI/EJB/Servlet process on WLS.
    Deepak suggested that the best way, since they are a CORBA shop tryingto move to Java,
    would be to have the C++ client talking to a CORBA/C++ object on WLEthat calls
    a CORBA/Java object on WLE that acts as a client to WLS and accessesthe services of the
    Java object on that server.
    Another option would be to have the CORBA/C++ object on WLE use theJNI API to call a Java
    object
    on WLE that acts as a client to WLS and accesses the Java servicerunning there. There may
    be better
    performance from CORBA/C++ to CORBA/Java, though, so that was Deepak'sfirst choice.
    Maffy
    Papaya Head wrote:
    you can also find an example in the WLS5.1 docs that includes a code
    segment from C++
    client of the RMI-IIOP hello example.
    Will Lyons wrote:
    The example application with C++ CORBA objects calling EJBs on a
    Java Server refers
    to C++ CORBA objects on the WLE T-Engine calling EJBs on the WLET-Engine. That
    interoperability capability is supported, but it is not possibleto call the J-Engine
    from the T-Engine in WLE 5.1. The primary usage model assumed inWLE 5.1 is calling
    the WLE T-Engine from the J-Engine (or from WLS).
    Will
    Papaya Head wrote:
    my understanding of your question is: you want some feature that
    allows CORBA
    objects to talk to EJB objects on WLS.
    WLS5.1 has a new feature: RMI/IIOP, it's probably the featureyou want.
    before WLS5.1, CORBA components couldn't talk to EJB componentsdirectly, but you
    could make it happen by building a bridge from CORBA objects toEJB components on
    WLS. that's probably what the references you read are talkingabout...
    Maffy Finnerty wrote:
    We haven't even gotten that far yet, re: transactions. Right
    now the issue is
    having an
    in-house client (C++) connected to WLE but accessing services(EJBs) on WLS.
    No talk
    of transactions has occurred, yet.
    However, I just found some conflicting information. I found areference to
    building the
    simpapp application to connect C++ objects on a CORBA serverto EJBs on a Java
    Server,
    which, if I'm reading it correctly, translates to WLE to WLS.However, I also
    found a
    reference to bidirectional interoperability that said that,for now, the
    T-Engine could not
    (WLE) could NOT invoke services on the J-Engine (WLS) but thatservices on the
    T-Engine
    (WLE) could BE invoked from requesters on the J-Engine (WLS).So, color me
    confused.
    maffy
    Papaya Head wrote:
    the first question that comes to my mind is:
    can transaction run across components on WLE and components
    on WLS? I don't
    think it can...
    Maffy Finnerty wrote:
    I have a client who is looking to attach a C++ client to
    their WLE
    system, and, since
    they now have WLS and WLE thanks to v. 5.1, they want tostart moving
    EJBs to the
    WLS platform. The issue is this.
    What if any are the issues regarding communicating betweenCORBA objects
    on WLE
    TO EJBs on WLS? I noticed that the illustrations alwaysshow the
    communication coming
    from the WLS side to the WLE side, but this client will beconnected
    directly to the WLE
    platform, and wanting to access services on WLS.
    Any issues, directions to documentation, or other adviceregarding this
    issue?
    Thanks in advance,
    Maffy

  • Starting up j2ee and EJB deployment tool on Windows 98

    I will start off this question with an apology if it is too stupid,
    basic, or placed in the wrong group. I am relatively new to the world
    of Java and even newer to the world of Server-side Java and EJBs.
    However, I am plugging away.
    I am using my trusty 4 year old system with Windows 98 second edition
    to dabble with Server-side Java and EJB applications. I am using
    Tomcat 4.0 as my server. When I try and start the j2ee server or the
    EJB deployment tool I get the following scrolling messages:
    Out of environment space
    Out of environment space
    Out of environment space
    Out of environment space
    Out of environment space
    Out of environment space
    Out of environment space
    Out of environment space
    Out of environment space
    Out of environment space
    Out of environment space
    Out of environment space
    Out of environment space
    Out of environment space
    Syntax error
    Syntax error
    Syntax error
    Out of environment space
    Bad command or file name
    I have tried to adjust the memory settings in the DOS window with no
    success. My question has three parts:
    1) Can these applications be run using Windows 98 and if so what are
    the exact DOS window memory settings for this?
    2) Where exactly can I find the documentation that specifies this?
    (please be specific as possible as I have read the readme.txt files
    supplied with j2ee)
    3) Should this and similar questions be posted in another
    group/section?
    I truly appreciate anyone's help with this.
    Sincerely,
    Tim

    You're going to have a lot of pain unless you upgrade to Windows 2000 or XP.
    In the mean time, set your environment size much larger (google for "Out of
    environment space") and use WinOne from http://www.cia.com.au/luke/ ...
    that's how I scraped by on Windows 98 for a while.
    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/
    "Tim" <[email protected]> wrote in message
    news:[email protected]..
    I will start off this question with an apology if it is too stupid,
    basic, or placed in the wrong group. I am relatively new to the world
    of Java and even newer to the world of Server-side Java and EJBs.
    However, I am plugging away.
    I am using my trusty 4 year old system with Windows 98 second edition
    to dabble with Server-side Java and EJB applications. I am using
    Tomcat 4.0 as my server. When I try and start the j2ee server or the
    EJB deployment tool I get the following scrolling messages:
    Out of environment space
    Out of environment space
    Out of environment space
    Out of environment space
    Out of environment space
    Out of environment space
    Out of environment space
    Out of environment space
    Out of environment space
    Out of environment space
    Out of environment space
    Out of environment space
    Out of environment space
    Out of environment space
    Syntax error
    Syntax error
    Syntax error
    Out of environment space
    Bad command or file name
    I have tried to adjust the memory settings in the DOS window with no
    success. My question has three parts:
    1) Can these applications be run using Windows 98 and if so what are
    the exact DOS window memory settings for this?
    2) Where exactly can I find the documentation that specifies this?
    (please be specific as possible as I have read the readme.txt files
    supplied with j2ee)
    3) Should this and similar questions be posted in another
    group/section?
    I truly appreciate anyone's help with this.
    Sincerely,
    Tim

  • EJB Deployment Problem for Stateless Session with Multiple ejbCreate

    In weblogic server if I use multiple ejbCreate with different parameters it is found
    to raise error with error message :
    <Error deploying application cart:
    Unable to deploy EJB: cart.jar from cart.jar:
         In EJB CartBean, the stateless session bean class must define a single ejbCreate
    method that takes no parameters.
         at weblogic.ejb20.compliance.EJBComplianceChecker.check(EJBComplianceChecker.java:256)
         at weblogic.ejb20.compliance.EJBComplianceChecker.checkDeploymentInfo(EJBComplianceChecker.java:220)
         at weblogic.ejb20.ejbc.EJBCompiler.complianceCheckJar(EJBCompiler.java:453)
         at weblogic.ejb20.ejbc.EJBCompiler.checkCompliance(EJBCompiler.java:410)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:203)
         at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:296)
         at weblogic.ejb20.deployer.Deployer.compileEJB(Deployer.java:676)
         at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:843)
         at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
         at weblogic.j2ee.Application.addComponent(Application.java:160)
         at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
         at ......
    Code example...
    public void ejbCreate() throws CreateException {}
    public void ejbCreate(String person) throws CreateException {
    // code here
    public void ejbCreate(String person, String id) throws CreateException {
    // code here
    the code above is found ok in J2ee Ref. Implementation and able to deploy. Why this
    is not deployable in Weblogic(tried in 6.1).is it a required condition for stateless
    session bean
    to have only single ejbcreate with no parameters ?
    Can somebody explain? and is there a way out to overcome this constraint if so in
    weblogic
    with regards
    Ganeshan Kalembeth

    Stateless session beans may define only a single create() method with no
    suffix
    and no arguments.
    Michael Jouravlev wrote:
    "Ganeshan Kalembeth" <[email protected]> wrote in message
    news:3ce28a88$[email protected]..
    In weblogic server if I use multiple ejbCreate with different parametersit is found
    to raise error with error message :
    <Error deploying application cart:
    Unable to deploy EJB: cart.jar from cart.jar:
    In EJB CartBean, the stateless session bean class must define a singleejbCreate
    method that takes no parameters.
    atweblogic.ejb20.compliance.EJBComplianceChecker.check(EJBComplianceChecker.ja
    va:256)
    atweblogic.ejb20.compliance.EJBComplianceChecker.checkDeploymentInfo(EJBCompli
    anceChecker.java:220)
    atweblogic.ejb20.ejbc.EJBCompiler.complianceCheckJar(EJBCompiler.java:453)
    at weblogic.ejb20.ejbc.EJBCompiler.checkCompliance(EJBCompiler.java:410)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:203)
    at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:296)
    at weblogic.ejb20.deployer.Deployer.compileEJB(Deployer.java:676)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:843)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
    at weblogic.j2ee.Application.addComponent(Application.java:160)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at ......
    Code example...
    public void ejbCreate() throws CreateException {}
    public void ejbCreate(String person) throws CreateException {
    // code here
    public void ejbCreate(String person, String id) throws CreateException {
    // code here
    the code above is found ok in J2ee Ref. Implementation and able to deploy.Why this
    is not deployable in Weblogic(tried in 6.1).is it a required condition forstateless
    session bean
    to have only single ejbcreate with no parameters ?
    Can somebody explain? and is there a way out to overcome this constraintif so in
    weblogic
    with regards
    Ganeshan KalembethRTFM EJB 2.0 Spec, chapter 7.8

  • Deploy PetStore Webapps and EJBs to different tiers

    Hi,
    Basically, the PetStore example deploys JSP/Web/EJBs to one node in one petstore.ear.
    I want to seperate the Web apps and EJBs to different nodes that running Weblogic
    by re-packaging the ear file to get a war file and ejb ear file. I deployed this
    war file to one node and ejb ear to another node. Is this the right approach?
    If so, how the JSP knows that the EJBs are in different node now?
    Thanks,
    Cathy

    Hi,
    Basically, the PetStore example deploys JSP/Web/EJBs to one node in one petstore.ear.
    I want to seperate the Web apps and EJBs to different nodes that running Weblogic
    by re-packaging the ear file to get a war file and ejb ear file. I deployed this
    war file to one node and ejb ear to another node. Is this the right approach?
    If so, how the JSP knows that the EJBs are in different node now?
    Thanks,
    Cathy

  • We want to deploy Servlet/JSP in JServ and call the EJB's deployed in iPlanet App Server 6.0 SP2. How do we make the getInitialContext Call be able to access the EJB's.

    Additionally what configurations do we need to make sure we have on JServ (Third party Servlet container) to make sure that the iPlanet EJB's can be accessed.

    Let me preface my instructions with the comment that this isn't a good idea. Although the J2EE specification allows you seperate your web container from your EJB container, in practical deployments it is a bad idea. The overhead of doing RMI/IIOP calls to an external container as opposed to making inter-JVM calls means that you can expect roughly an order of magnitude less performance than if you colocate your web and EJB containers. (This is why all EJB containers are also web containers, or at least have the provision to install themselves in the same JVM as a web container.)
    That said, if you do not have the option to move the servlets to iAS, you can access EJB's in iAS from JServ the same way that you would from any remote client. Take a look at the following information for more detail:
    Chapter 9 of the developer's guide ( this shows you what changes you need to make to the remote JVM (at JServ) and in the EJB's that you are exposing).
    The RMI/IIOP sample application. This gives you an example of how to access EJB's from outside the container.
    (To answer your direct question, the following code will get the initial context. But if you don't take all of the other configuration steps, this code won't work:
    env.put("java.naming.factory.initial", "com.sun.jndi.cosnaming.CNCtxFactory");
    env.put("java.naming.provider.url", "iiop://" + host + ":"+port);
    Context initial = new InitialContext(env);
    I'd also suggest that you approach the task with the following approach. (Assuming that I haven't managed to convince you that this is a really bad idea.)
    1. Get your EJB's working on iAS. Test them with servlet harnesses running on iAS.
    2. Get your servlets working on JServ, if they aren't already.
    3. Create a simple standalone Java application as a test harness for EJB's. Follow the RMI/IIOP instructions until you get this test harness working.
    4. Create a simple servlet test harness in JServ to access your EJb's. Follow the JVM setup instrucitons until you get this working.
    5. Actually integrate the EJB's with your production application.
    I say this because there are about five trillion things that can go wrong in this process. Although the troubleshooting steps in the docs are helpful, I find that it helps to get one thing working at a time. It's very frustrating to spend a day trying to resolve JNDI issues only to find out that you have your CXS configured improperly.

  • Global transactions in OSB and EJB 2.1

    Hi,
    My team is working in a SOA service based on OSB 11g (11.1.1.5) using DB JCA Adapter and EJB 2.1 over WLS 10g(WLI environment). The logic of the service works in this way:
    1. A table in a database (XE) is polled by the DB Adapter which starts the service (1 row = 1 message).
    2. The message contains a collection of items to be inserted in another Oracle database.
         Once a message/row is picked, and after some steps (logging, validation,etc), there is a for..each action which extracts each item of the collection and executes a service callout action to a business service.
    3. This business service uses EJB protocol to call an EJB (2.1 + WLS Extensions). The EJB is deployed in another domain (WLS 10.3.0/10g and Oracle BEA drivers)  and only executes an store procedure with the parameters based on the message and inserts these values in a table.
    4. Once the for...each finishes, there is a call to another proxy service which marks the message/row as "processed" in the source table. This update is done via DB JCA also.
    5. In case of an error, the error handler of the proxy service calls the proxy service mentioned above to mark the row as "Failed" (in fact there is a retry mechanism, but it's not important for now).
    The service requires to work inside a global transaction. The main requirement is that the collection of items should be processed as "All or None", so basically we're using the options to manage the global transaction. However, the problem is that it's failing to rollback the whole insertion of items when an error is simulated. It only rolls back the last insertion/execution of SP.
    Additionally, the proxy service that should mark the row as FAILED, never updates this one, and the tables stay locked until we modify one of the store procedure in order to avoid the simulated error and commit the transaction.
    The EJB uses WLS extensions with the annotations to "transaction required". The proxy service has the option transaction required also. The database drivers are all XA and we're testing against Oracle11g XE (however, the EJB destiny will be Oracle 8i in production).
    We have tried different alternatives, splitting the logic in different proxies (Proxy services for JCA, Proxy with For Each for EJB, etc), isolating the specific part with the EJB call, without success.
    The security between domains is set as Global Trust.
    Do you have any idea, example or suggestion about this problem? Is EJB really supported in Global Transactions and XA?
    Thanks in advance.

    where do you find the J2EE Connector 1.5 compliant
    Resource Adapter?I wrote the compliant adapter myself. Hey Steve,
    Were you able to find a solution for this problem. I am struggling with the same problem with the RI Beta implementation.
    Sandeep

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

Maybe you are looking for