KRONOS - EJB Job scheduler for Weblogic

Paramus, NJ - February 22, 2002 - Indus Consultancy Services (ICS) today
announced the latest in a series of improvements to Kronos Enterprise
Scheduler, a full-featured job scheduling system written for the
Enterprise Java (J2EE) environment.
This version fixes some minor bugs reported by customers, and adds a new
security feature to control user visibility to jobs, tasks, and
schedules. A new environment setting allows the Kronos Enterprise
Scheduler administrator to restrict users to seeing only those items
which they have created. Administrators still have full visibility to
all items.
ICS is also proud to have Kronos Enterprise Scheduler competing in the
Java Developer's Journal 2002 Readers' Choice Awards. Every year, Java
Developer's Journal holds voting for products in a variety of
categories. This year, Kronos Enterprise Scheduler is nominated in
three of those categories:
· Best Java Application (Standing as of 2/22/02 : 16th out of 69
products with votes.)
· Best Java Component (Standing as of 2/22/02 : 10th out of 26 products
with votes.)
· Most Innovative Java Product (Standing as of 2/22/02 : 21st out of 63
products with votes.)
To vote, visit the Java Developer's Journal website at
<http://www.sys-con.com/java/readerschoice2002>
To find out more about Kronos Enterprise Scheduler, and learn why
companies around globe are selecting this powerful product to handle
their scheduling needs, visit the ICS website at <http://www.indcon.com>
and request a FREE 30-day evaluation.
© 2002 Indus Consultancy Services, Inc. All rights reserved. Java and
all Java-based marks are trademarks or registered trademarks of Sun
Microsystems, Inc. in the U.S. and other countries. All other product
and company names are trademarks of their respective owners.

I would hope that BEA will step up and develop a replacement for their
deprecated APIs. It is unfair to ask their customers to buy something they
got previously for free. I also understand that the future EJB spec will
contain scheduling features.

Similar Messages

  • ANNOUNCE:::::::: EJB job scheduler for Weblogic

    Paramus, NJ - June 26, 2001 - Indus Consultancy Services today announced
    an upgrade release of its Java scheduling product. Kronos Enterprise
    Scheduler is a full-featured job scheduling system written for the
    Enterprise Java (J2EE) environment.
    As a J2EE application, Kronos Enterprise Scheduler is able to achieve a
    high degree of portability, scalability, and reliability, features which
    are critical to an enterprise system.
    Additionally, Kronos Enterprise Scheduler provides a comprehensive set
    of scheduling options, powerful holiday definitions, job dependencies,
    administrative alerts, J2EE security integration, monitoring
    capabilities, Web and "rich client" user interfaces, and an open
    developer API. The combination of these features make Kronos Enterprise
    Scheduler one of the most complete solutions on the market today.
    Version 2.10 contains a number of minor enhancements and bug fixes and
    is a free upgrade for current customers.
    For more information on Kronos, please visit our products page at
    www.indcon.com

    I would hope that BEA will step up and develop a replacement for their
    deprecated APIs. It is unfair to ask their customers to buy something they
    got previously for free. I also understand that the future EJB spec will
    contain scheduling features.

  • KRONOS JOB Scheduler For WEBLOGIC CUSTOMERS

    Paramus, NJ - June 26, 2001 - Indus Consultancy Services today announced
    an upgrade release of its Java scheduling product. Kronos Enterprise
    Scheduler is a full-featured job scheduling system written for the
    Enterprise Java (J2EE) environment.
    As a J2EE application, Kronos Enterprise Scheduler is able to achieve a
    high degree of portability, scalability, and reliability, features which
    are critical to an enterprise system.
    Additionally, Kronos Enterprise Scheduler provides a comprehensive set
    of scheduling options, powerful holiday definitions, job dependencies,
    administrative alerts, J2EE security integration, monitoring
    capabilities, Web and "rich client" user interfaces, and an open
    developer API. The combination of these features make Kronos Enterprise
    Scheduler one of the most complete solutions on the market today.
    Version 2.10 contains a number of minor enhancements and bug fixes and
    is a free upgrade for current customers.
    For more information on Kronos, please visit our products page at
    www.indcon.com

    Paramus, NJ - June 26, 2001 - Indus Consultancy Services today announced
    an upgrade release of its Java scheduling product. Kronos Enterprise
    Scheduler is a full-featured job scheduling system written for the
    Enterprise Java (J2EE) environment.
    As a J2EE application, Kronos Enterprise Scheduler is able to achieve a
    high degree of portability, scalability, and reliability, features which
    are critical to an enterprise system.
    Additionally, Kronos Enterprise Scheduler provides a comprehensive set
    of scheduling options, powerful holiday definitions, job dependencies,
    administrative alerts, J2EE security integration, monitoring
    capabilities, Web and "rich client" user interfaces, and an open
    developer API. The combination of these features make Kronos Enterprise
    Scheduler one of the most complete solutions on the market today.
    Version 2.10 contains a number of minor enhancements and bug fixes and
    is a free upgrade for current customers.
    For more information on Kronos, please visit our products page at
    www.indcon.com

  • Regarding Background Job scheduling for file to file scenario

    Hi Guru's
    Good morining all of u
    I have one doubt on ...
    can we do background job scheduling for file to file scenario?
    Please give me response as early as possible.
    thanks and regards
    sai

    background jobscheduling for file adapter...
    you can schedule the file adapter according to your requirement as follows:
    In the  Communication Channel Monitoring Locate the link Availability Time Planning,  In Availability Time Planning, choose the Availability time as daily and say create, give the time details, select the communication channel in your case file adapter , goto the Communication Channels tab and filter and add the respective channel, save it
    /people/shabarish.vijayakumar/blog/2006/11/26/adapter-scheduling--hail-sp-19-

  • Background job scheduling for report

    Hi can any one explain me how to do background job scheduling for report periodically for every 15 min.

    Hi Rajesh thanks for your brief explanation.
    but I am new to abap so I can't understand exactly will you please make it clear for the below program
    REPORT  zklj.
    data: begin of itab occurs 0,
          partner  type but000-partner,
          type     type but000-type,
          BU_SORT1 type but000-BU_SORT1,
          end of itab.
    select partner type from but000 into table itab.
    CALL FUNCTION 'GUI_DOWNLOAD'
      EXPORTING
      BIN_FILESIZE                    =
        FILENAME                        = 'd:\al1\ahaj.xls'
        FILETYPE                        = 'DAT'
      APPEND                          = ' '
      WRITE_FIELD_SEPARATOR           = ' '
      HEADER                          = '00'
      TRUNC_TRAILING_BLANKS           = ' '
      WRITE_LF                        = 'X'
      COL_SELECT                      = ' '
      COL_SELECT_MASK                 = ' '
      DAT_MODE                        = ' '
      CONFIRM_OVERWRITE               = ' '
      NO_AUTH_CHECK                   = ' '
      CODEPAGE                        = '400'
      IGNORE_CERR                     = ABAP_TRUE
      REPLACEMENT                     = '#'
      WRITE_BOM                       = ' '
      TRUNC_TRAILING_BLANKS_EOL       = 'X'
      WK1_N_FORMAT                    = ' '
      WK1_N_SIZE                      = ' '
      WK1_T_FORMAT                    = ' '
      WK1_T_SIZE                      = ' '
      WRITE_LF_AFTER_LAST_LINE        = ABAP_TRUE
      SHOW_TRANSFER_STATUS            = ABAP_TRUE
    IMPORTING
      FILELENGTH                      =
      TABLES
        DATA_TAB                        = itab.

  • Error occured while posting the job schedule for JDBCAdapter

    Hi Experts,
    In Application Log in Path: "/usr/sap/<SID>/DVExxxx/j2ee/cluster/server1/log", I see the error:
    #/Applications/ExchangeInfrastructure/AdapterFramework/Services/Util
    ##com.sap.aii.af.service.scheduler.SchedulerManagerImpl.postJobScheduleOthers(String, int)
    #J2EE_GUEST#0##n/a##f7956e1f6b4711e0b851001e0b5d3ac8#SAPEngine_Application_Thread[impl:3]_23##0#0
    #Error#1#com.sap.aii.af.service.scheduler.SchedulerManagerImpl#Plain
    ###error occured while posting the job schedule for JDBCAdapter_9f0584b1bcb33b94b67ada456233bcb8 with 2#
    Frequently are created Lock's and I need remove them in Visual Admin.
    Any idea about this error?
    Tks in advance.

    Hi,
    After applying the SP 23 Patch Level 08, LOCK JDBC problems stopped.
    But now when a network error or database error, the JDBC Sender Communication channels that were open to connection, are blocked.
    Even following the instructions in [SAP Note 1083488 - XI FTP_JDBC sender channel stop polling indefinitely (04_04S)|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1083488] the problem continues.
    I've already set the parameter "taskTimeout" and selected the option "Disconnect from Database After Each Message Processing" but not resolved.
    Any ideas?
    Thanks in advance.

  • Re: What is the Job Market for weblogic/soa administrator????

    HI
    what about the job market for weblogic/soa administration?????
    Only weblogic server administration .... ok .....
    what about weblogic with soa ...having some confusions....
    what about the future of weblogic/soa admins?????
    pls help me anyone,.............Give me your valuable suggestions to me please
    this information is useful for so many people...
    Thanks
    ganesh

    Hello,
    SWU_OBUF really should do the same trick as the job. (I neither can remeber the job name.)
    Did you have some transaction(s) open in another session(s), when you executed SWU_OBUF. This might have a really annoying effect: the SWU_OBUF doesn't seem to do its job. For example I once had SE37 open in another session, and SWU_OBUF didn't do the trick (tried many times). After closing SE37, it suddenly worked...
    Regards,
    Karri

  • Oracle job scheduling for 2 different timezones

    I have a procedure which needs to be scheduled for different timezones based on one of the column in the table (ex: region).
    If region is California, it needs to be scheduled at 8:00am, if Newyork at 6:00am.
    Any ideas much appreciated!

    user497841 wrote:
    In my procedure, I populate a snapshot table for all regions.
    The procedure includes different inserts into the table per region.
    But insert for california should be scheduled at 8:00 and insert for newyork should be scheduled at 6:00am.
    Also, the job needs to take care of daylight savings.
    So i got to schedule the same procedure to run at 8:00am and 6:00 am.Assuming that you use DBMS_SCHEDULER then if you take a look at the definition of create schedule (or create job etc) then you will find that the scheduled time is timezone aware. eg
    DBMS_SCHEDULER.CREATE_SCHEDULE (
       schedule_name          IN VARCHAR2,
       start_date             IN TIMESTAMP WITH TIMEZONE DEFAULT NULL,
       repeat_interval        IN VARCHAR2,
       end_date               IN TIMESTAMP WITH TIMEZONE DEFAULT NULL,
       comments               IN VARCHAR2 DEFAULT NULL);This should then make your jobs timezone (and hence dst) aware.
    Niall Litchfield
    http://www.orawin.info/

  • Job scheduling for different slection criteria

    Hi,
    I have a selection screen where user can select eg. say operation 700 or 800 (radiobuttons).
    Now user want to schedule the report as background job.
    Is that I need to create two jobs with two variants ( i.e for two operations 700 & 800)? So that user executes job with respective variant for the operation.
    Pl. clarify whether above steps are of right approach. Also any alternative ways to achieve the same.
    Thanks.
    From
    Reddy

    Hi,
    If user wants to run it as a background job as & when required( The program doesnt have any specific schedule for background execution), then use FM JOB_OPEN, JOB_SUBMIT, JOB_CLOSE to schedule it as a background job.
    If its a periodic job then you will have to create 2 variants & create 2 jobs in SM36.
    Best regards,
    Prashant

  • Disabling Report Job (Scheduling) for User

    Hi all,
    Is it possible to disable the ability to schedule report job for certain user?
    I tried setting the permission on the reports, unchecking the "Schedule Report" option. But the user (under BI Consumer role) are still able to run scheduler for all report.
    Thanks a lot!

    Hi,
    Is this a Z Report that your are using?
    You can setup a background job in SM36 specifying the calendar and variant, you can take help from BASIS in setting up a spool recipient, I.D  This person will get the output in his/her mail.
    Regards
    Shailesh

  • EJB EAR deployment for weblogic 9.2

    Hello!
    I already have the EJB3.0 application which I would like to deploy. After preparing the .ear file I tried to deploy it with the Administration console. I received the error message, and I found a workaround : [url http://forums.bea.com/bea/thread.jspa?threadID=600016992&tstart=0]here (@dev2dev). When I tried the console deployment, I received the following error message:
    <11.12.2006 14.49 Uhr CET> <Error> <Deployer> <BEA-149265> <Failure occured in the execution of deployment request with ID '1165844945693' f
    or task '3'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(app5.jar)
    weblogic.application.ModuleException: Exception preparing module: EJBModule(app5.jar)
            at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:394)
            at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
            at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
            Truncated. see log file for complete stacktrace
    java.lang.IllegalStateException: getLocalName() may only be called on a START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE event, the current st
    ate is [END_DOCUMENT]
            at weblogic.xml.stax.XMLStreamReaderBase.getLocalName(XMLStreamReaderBase.java:524)
            at javax.xml.stream.util.StreamReaderDelegate.getLocalName(StreamReaderDelegate.java:216)
            at javax.xml.stream.util.StreamReaderDelegate.getLocalName(StreamReaderDelegate.java:216)
            at com.bea.xbean.richParser.XMLStreamReaderExtImpl.getLocalName(XMLStreamReaderExtImpl.java:1294)
            at com.bea.staxb.runtime.internal.UnmarshalResult.getLocalName(UnmarshalResult.java:867)
            Truncated. see log file for complete stacktrace
    >
    <11.12.2006 14.49 Uhr CET> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'app5'.
    >
    <11.12.2006 14.49 Uhr CET> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException: Exception preparing module: EJBModule(app5.jar)
            at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:394)
            at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
            at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
            at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
            at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
            Truncated. see log file for complete stacktrace
    java.lang.IllegalStateException: getLocalName() may only be called on a START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE event, the current st
    ate is [END_DOCUMENT]
            at weblogic.xml.stax.XMLStreamReaderBase.getLocalName(XMLStreamReaderBase.java:524)
            at javax.xml.stream.util.StreamReaderDelegate.getLocalName(StreamReaderDelegate.java:216)
            at javax.xml.stream.util.StreamReaderDelegate.getLocalName(StreamReaderDelegate.java:216)
            at com.bea.xbean.richParser.XMLStreamReaderExtImpl.getLocalName(XMLStreamReaderExtImpl.java:1294)
            at com.bea.staxb.runtime.internal.UnmarshalResult.getLocalName(UnmarshalResult.java:867)
            Truncated. see log file for complete stacktrace
    >I would just like to mention, that it is not really self-explaining. Can somebody help me and explain me what does this error mean?
    Also, is there a document describing the complete deployment process for wl9.2?
    Thank you.
    Konstantin

    MIK wrote:
    I have a question about weblogic-ejb-jar.xml file entries.
    weblogic 9.1 server says it is invalid while deploying my file
    my file is as under,
    <?xml version="1.0"?><!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems,
    Inc.//DTD WebLogic 8.1.0 EJB//EN'
    'http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd'>
    <weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/910"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.bea.com/ns/weblogic/910
    http://www.bea.com/ns/weblogic/910/weblogic-ejb-jar.xsd">
    <weblogic-enterprise-bean>
              <ejb-name>MessageAccess</ejb-name>
              <message-driven-descriptor>
    <resource-adapter-jndi-name>SystemModule-test</resource-adapter-jndi-name>
              </message-driven-descriptor>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    can anybody help what is wrong with it?the error I get is this,
    [EJB:011023]An error occurred while reading the deployment descriptor.
    The error was:
    Unmarshaller failed.
    at
    weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:957)
    at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:317)
    at
    weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
    at
    weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
    at
    weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    and XMLSPY also says that weblogic-ejb-jar.xml is invalid and the error
    there is,
    Root element '<weblogic-ejb-jar' not defined in DTD/Schema.

  • Background Job Scheduling for MC.9

    Dear All,
    Transaction : MC.9
    Program Name: RMCB0300
    This transaction is running fine on foreground run but i am not able to schedule a background run for it. It's giving an Error message "No List available" when i try to check the output in SM37 Job Selection transaction. Please help me in this regard.
    Regards,
    Sushant L

    Dear All,
    Transaction : MC.9
    Program Name: RMCB0300
    This transaction is running fine on foreground run but i am not able to schedule a background run for it. It's giving an Error message "No List available" when i try to check the output in SM37 Job Selection transaction. Please help me in this regard.
    Regards,
    Sushant L

  • EJB deployment error for Weblogic server 9.2 mp4

    Hi,
    While trying to deploy a small EJB jar file which uses EJB 2.1 CMP beans with relationships, getting the following error from Weblogic server 9.2 MP4:
    =================================================================================================
    <Error> <EJB> <VinodThinkPad> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1320143988333> <BEA-012036> <Compiling generated EJB classes produced the following Java compiler error message:
    C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
    found : <nulltype>
    required: int
    shipmentId = null;
    ^
    Note: Some input files use unchecked or unsafe operations.
    Note: Recompile with -Xlint:unchecked for details.
    1 error
    >
    ####<Nov 1, 2011 4:09:48 PM IST> <Error> <Deployer> <VinodThinkPad> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1320143988380> <BEA-149265> <Failure occured in the execution of deployment request with ID '1320143984947' for task '1'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(EJBTest)
    Unable to deploy EJB: EJBTest.jar from EJBTest.jar:
    There are 1 nested errors:
    java.io.IOException: Compiler failed executable.exec:
    C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
    found : <nulltype>
    required: int
    shipmentId = null;
    ^
    Note: Some input files use unchecked or unsafe operations.
    Note: Recompile with -Xlint:unchecked for details.
    1 error
         at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
         at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
         at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
         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:432)
         at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:754)
         at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:657)
         at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1201)
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:355)
         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.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
         at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    weblogic.application.ModuleException: Exception preparing module: EJBModule(EJBTest)
    Unable to deploy EJB: EJBTest.jar from EJBTest.jar:
    There are 1 nested errors:
    java.io.IOException: Compiler failed executable.exec:
    C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
    found : <nulltype>
    required: int
    shipmentId = null;
    ^
    Note: Some input files use unchecked or unsafe operations.
    Note: Recompile with -Xlint:unchecked for details.
    1 error
         at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
         at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
         at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
         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:432)
         at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:754)
         at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:657)
         at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1201)
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:355)
         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.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
         at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:382)
         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.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
         at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    java.io.IOException: Compiler failed executable.exec:
    C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
    found : <nulltype>
    required: int
    shipmentId = null;
    ^
    Note: Some input files use unchecked or unsafe operations.
    Note: Recompile with -Xlint:unchecked for details.
    1 error
         at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
         at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
         at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
         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:432)
         at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:754)
         at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:657)
         at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1201)
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:355)
         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.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
         at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    >
    =================================================================================================
    While I'm able to deploy without the CMP 1-1 relationship, the moment I introduce the 1-1 relationship, I get this error. Database used is Oracle 10g XE.
    I have been battling this error for more than a day now. Kindly help me fix this.
    Thanks in advance!
    Regards,
    Vinod

    Hi,
    I was able to figure out the root cause. I was using the primitive data type "int" for primary key and foreign key for one of the beans in the relationship. After I changed it to "Integer" wrapper type, the issue got resolved.
    -Vinod

  • Mail configuration and background job scheduling for ST22 Data

    Experts,
    I want to know how can i schedule a background job in SAP to extract data from ST22 and send a automated mail for the same?
    Any help will be appreciated, Thanks!!!
    Regards,
    Vinit Pagaria

    You don't need to do that, simply configure CCMS (RZ20) to send you an alert via mail when a dump occurs.
    Read,
    http://help.sap.com/saphelp_nw04/helpdata/EN/90/4e313f8815d036e10000000a114084/frameset.htm
    Regards
    Juan

  • Error in Back ground job schedule for call transaction

    Hi Experts ,
    I have a Program which as Three BDC in it . 1 - to create contact person , 2- customer 3-sales order
    Using call transaction if i run with all screens and no screens it's running fine..
    if i schedule it background job
    conact and customer works fine but sales order not works ..
    can anyone give me the solution ?

    Hi Phani and Pavan ,
    It works Fine for Back ground anf fore ground i.e ( N and A )  sales order is created here .
    but Sales order not created when i schedule it in back ground  as
    Program - execute in back ground  .
    sales not created when i schedule it in background job  only using SM36 or Program - execute in back ground  ?
    Edited by: Pradeep Annaiah on Jan 13, 2009 5:29 AM

Maybe you are looking for

  • Transfer an Email from one account to another and ...

    Dear Team, I joined BT recently this month and I have a btinternet Email for more than 5 years when i was living with my brother. Now I want to tranfer my email from my brothers account to my account and make it my primary email. I called 3 times the

  • Illustrator CS6 jpeg file saved looks distorted when uploaded onto internet

    I am helping  a pal of mine on illustrator and I have little knowledge so Im asking here. They made a simple type and shape design with a solid backdrop. When I tried to export via save for web to jpeg with high settings, it came up online with subtl

  • JTabbedPane w/ Accelerator Keys

    I need to add accelerator keys to the tabs of a JTabbedPane, much like the accelerators in a JMenuItem (i.e. under-score for Alt-F, or CTRL-X, etc...). Any suggestions? Thanks!

  • Fetching column data for clicked DataGrid cell

    I am using a DataGrid and the number of columns are based on the data thus dynamic; columns are added at runtime.  I am trying to use the same ItemRenderer for all columns.  The one piece I can not seem to get to work is knowing which datafield to us

  • Issue with PluginProcess, virus or what??

    I log onto two credit card sites, both owned by the same bank, almost every day.  Two days ago, for the first time ever, VirusBarrier which I have on my mac, lit up and said, Virus Barrier detected that the application "PluginProcess" is downloading