New Jdevelopper Production version

Hi,
When last preview became a production version ?
Do you have resolve problem of physically delete java file, when a file is removed from a Project ?
Regards
Philippe

In 10.1.3 the way JDeveloper manages the project content has changed.
Details about the new (and improved) way are in this document:
http://www.oracle.com/technology/products/jdev/101/collateral/101/migratingjdeveloperprojectsto1013.pdf
The way to eliminate files from showing up in your project in the developer preview is with the working set feature.
In production we'll make it easier with a button that does this automtaically for you.

Similar Messages

  • Schedules for certifications based on new SAP product versions?

    Are there any schedules available that show when SAP certifications and related curriculum will be updated to newer product versions?
    I also have a current requirement from an end user to find certifications and classes based on Crystal Reports 2013.  Everything I can find is based on the older version 2011.  Is there any schedule for availability based on the newer version?
    Regards,
    Derek Ewell

    Hi Derek,
    I am afraid I could not find any such handy information.
    I would always refer to
    https://training.sap.com
    for any updates and the latest certification / curriculum details.
    Hope this helps.
    Kind Regards,
    Ravi

  • How to add new product version in Mopz?

    Hi,
    Can anyone guide me how to add a new product version in maintenance optimizer?
    I am going to get the stack file of Netweaver gateway 7.4, but without the product version, I could not proceed.
    Thanks in advanced.

    Dear Friend,
    1.    Maintain Solution Manager information in the system’s SLD data supplier. In case of ABAP system using tcode RZ70 and incase of Java system using the Visual Administrator/NWA(for NW 7.3 onwards)àSLD data Supplier.
    2.    Once the data supplier jobs gets executed you system will appear under SMSY under Server, Database and (Technical System in case of Java systems).
    The ‘Data Source’ should be LMDB.Note: Please don’t changes to the system in SMSY
    3)Execute transaction code ‘LMDB’ in your solution manager system.Select Technical system(Give Application server ABAP and SID of the Server)
    4)Click on Edit and select Software
    Click ‘Add’ and it will show Product Version screen  and  search for your installed product.
    5)Select your relevant usage types and once done choose ‘Close’ and save the data.
    6)Assignment of Product System :
    Click ‘Assign to Product System’
    Now Product system does not exist, hence we have to create one. Choose ‘Create’ and confirm
    7)After that complete Landscape Verification check..it should be green.
    8)Go to Solman_setup and complete Managed system configuration.
    after that Create Maintainence transaction and generate stack file.
    Before doing all activities make sure that ST-PI and ST-A/PI Patched should be applied in Managed server(NW 7.4) and run rtcctoll.
    Regards
    Maruthi V

  • No Automatic Dispatching Of Planned Order to new Production Version

    Dear Sir,
    When rescheduling an operation from one line to another, the system
    checks whether a production version exists for the material to be
    produced that contains the new production line as the preferred work
    center. If such a production version is found, this version is taken
    over into the planned order. The planned order is scheduled again based
    on the production version.
    The second function allows you to automatically search for an
    alternative work center in the case of a capacity overload of a work
    center, and to dispatch the operations to it. The predefined
    prioritization of the alternative work centers is considered in this
    case.
    The indicator Reschedule with production version must be set in the
    strategy profile.
    My issue is sytem does not making automatic Dispatch to the second
    Production version for the material at the time of insufficient capacity
    Best Regards
    Rami Abd El Fattah Mohamed,PPQM Functional & Technical Application
    Consultant

    In the dispatching control u can remove operation date check indicator and regarding the termination indicator SAP help says"
    "if you have not set this indicator then dispatching is not terminated but carried out without taking the production version into account. That means that the planned order is scheduled with the old standard values and the formulas from the new work center and dispatched to the new line."
    Please check if it works now.
    thanks

  • Selecting New Production version while Splitting a Production Order

    Hi SAP Gurus,
    Is there any option of selecting a New Production Version for a split Production Order?
    I have a production Order with three operations 10.20 and 30. This production Order is curently using the Production Version 001. Now , i have split the production order at Operation 30 and want to select new production Version 002 for the same.
    Can you please let me know if this is possible?

    Hi Sandeep,
       If you don't mind can you please let me know for what purpose you want to assign a new production version to production order after splitting at operation 30?
       To quickly recap, Production version is used if you have alternative BOM or alternative routings for a material. Based on Production Version that you have assigned in Material Master - MRP screen, your Routing and BOM details are selected.
        So how is this Production Version 002 different from Production Version 001 - is it in terms of routing or bom?
      With Best Regards,
    Srinivas

  • I want to erase the new 8.0 version and go back to the last version so I can have my tabs and google back! HOW!!

    I just downloaded the new 8.0 version of Firefox, but all of my extra tabs, auto fill, Google search tool bar, etc, etc, are gone and I want them back!!
    How do I reverse back to the last version of Firefox?
    I tried "RESTORE" to the day before on my computer, but that did not put everything back.
    How can I get these things back??
    Thanx,
    C.

    Hey,
    There are a lot of benefits to running the latest version of Firefox. You should consider [http://input.mozilla.com/en-US/feedback leaving feedback] for the developers so that they can continue to improve the product. If you are just having trouble finding things, you go to ''Firefox > Options > Menu bar''. This will give you a more familiar feel by enabling all of the menu items you are used to. You should also check out this article on [https://support.mozilla.com/en-US/kb/common-questions-after-upgrading-firefox-36 common questions after upgrading]. It will explain all of the UI changes. Everything is still there, it's just been moved around a bit.
    If you still want to roll back to a previous version of Firefox, just take a look at the Knowledge Base article [[Installing a previous version of Firefox]].
    Hopefully this helps!

  • Which SAP Product version to assign to a Logical Component in SMSY (SOLMAN)

    Dear SAP Colleagues,
    In our SAP environment, we do have 2 versions of ERP systems :
    1. CON - SIF - CDP systems are 'SAP ERP Central Component 5.0' product version.
    2. CDD - CDT - CDP systems are 'SAP ECC 6.0' product version.
    Question :
    When I want to assign these systems to a Z_LOGICAL_COMPONENTS, which product version do I have to choose ?
    Example for CON - SIF - CDP systems :
    1. They are 'SAP ERP Central Component 5.0' product version.
    2. In SMSY in our SOLMAN system, logical component are created using
        'SAP ECC 5.0' product version.
    Example for CDD - CDT - CDP systems :
    1. They are 'SAP ECC 6.0' product version.
    2. In SMSY in our SOLMAN system, logical component are created using
       'SAP ECC 6.0' product version.
    Question :
    What about 'SAP ERP 2004' and 'SAP ERP 6.0' product version ?
    In which case must I use this product version to assign CON-SIF-CPS
    or CDD-CDT-CDP to new Logical components ?
    Are they OSS Note or any matrix which give me the right product version to choose ?
    I have heard that 'SAP ECC x.x' product version should not used any longer ?
    Thanks
    Best regards
    P.C

    Hi,
    Read the following document, the mapping for systems and component versions is described in here:
    https://websmp202.sap-ag.de/~sapdownload/011000358700000074392009E/SP18_SolMan_Setup_Guide_V2.pdf
    For ECC 6.0 you should select ERP 6.0
    regards,
    Jaap

  • Differences between Product Version SAP ERP 2005 and SAP ECC 6.0

    Hello Guys,
    I have to setup an new XI interface between two R/3 system. During Integration Scenario setup you have to select under Application Component Type the Product version for the R/3 systems.
    Now, i am able to select SAP ERP 2005 or SAP ECC 6.0 from menu
    Could someone tell me the differences between SAP ERP 2005 and SAP ECC 6.0. Both are listed as Product Versions.
    Thanks in advance!
    Jochen

    SAP ECC 6.0 is latest version 2005 is last year version . as you are intergatin between 2 . you need select accordingly our source and target.
    let me know you still require any doubt
    Thanks
    Sreeram
    Message was edited by:
            Sreeram Reddy

  • Guys, my browser is going crazy and every website that I am on changes in about 10 seconds to 2 minutes to another webpage. I even downloaded a newer 5.0 version of firefox and I am having the same problem.

    Guys, my browser is going crazy and every website that I am on changes in about 10 seconds to 2 minutes to another webpage. I even downloaded a newer 5.0 version of firefox and I am having the same problem.

    Your System Details are showing Fun Web Products. Suggest you look in Add-ons - Extensions and Plug-ins, and Control Panel>Add/Remove programs or >(newer version) Programs and Features. You could also do a search of your computer.
    Fun Web Products(associated with MyWebSearch) always seems to cause problems, Alexa does, too, but less often - there may be conflicts.
    I'm not an expert on these two products. I'm afraid I can only alert you to the problems. Google will show you plenty of evidence of problems. You might also try the Search Firefox Help box above - a gold mine but it usually requires a lot of digging.
    You can start Firefox in Safe Mode - Hold Shift Key down as you double click on the Firefox icon>ignore the page that opens>Continue. If that improves things you could do a little troubleshooting(Safe Mode, Problematic extensions etc), use default theme, -
    https://support.mozilla.com/en-US/kb/Troubleshooting%20extensions%20and%20themes
    http://support.mozilla.com/en-US/kb/Troubleshooting%20plugins

  • Got to end of trial period for Adobe reader XI and cannot revert back to old version or install another version b/c it says I have a newer more functional version, so now I've got no reader at all and cannot fix. Any ideas how to overcome this?.

    Got to end of trial period for Adobe reader XI and cannot revert back to old version or install another version b/c it says I have a newer more functional version, so now I've got no reader at all and cannot fix. Any ideas how to overcome this?.

    YOu need to be clear about the products you are using, so we can help you. In particular there is no trial of Adobe Reader, it is free and keeps running. Sounds like you are using some versions of Acrobat - which?
    YOu must properly uninstall the trial, don't just delete files or you may get a mess impossible to recover.

  • How to identify Production Version in wwv_usr_menus

    In the Portal application menu wizard, you can 'Edit as New' from the manage menu UI. This creates a new menu version and row for menu_id in wwv_usr_menus$. You can also select which version (from n number of versions) should be current. Question is :
    How do you determine in custom application sql which version is current in wwv_usr_menus$, no 'Active' column, or iscurrent column exists. I've checked following:
    1. FK Constraint to wwv_usr_menus$ table = 0
    2. Trigger on table for seeding surrogate key only
    3. No menu API in PDK documentation, i.e. boolean = iscurrentmenu(menu_id, version);
    4. Update_dt column only updated when version is modified, not re-selected as current active version in Menu Manage UI.
    5. max(version) returns the last version created, not the current active (production) version.
    Code for rendering menu manage page is wrapped, I think the logic is there?
    Must be another table (not RI linked) that has current Menu version information.
    SO!!!!
    64,000 question is 'How do you know (programmatically) which row in portal.wwv_usr_menus$ is current version, or when you click 'Make version 2 as Production Version', what table is updated in portal schema?
    tia

    Hi,
    I think I have already answered this one. You can get the curent version either from wwv_usr_menus$ or wwv_modules$
    select version from wwv_modules$
    where id = <module_id>
    and status = 'PRODUCTION'
    This gives the version of the current production version.
    Thanks
    Sharmila

  • Usually there is a upgrade path for current users of the software at a reduced price. I dont see anything like that for Lightroom 6. Will I have to pay full price just to upgrade to the new LR6 standalone version???

    Usually there is a upgrade path for current users of the software at a reduced price. I dont see anything like that for Lightroom 6. Will I have to pay full price just to upgrade to the new LR6 standalone version???

    The standalone upgrade is 79 US Dollars.
    Go to Products, select Lightroom 6, click on Buy, select Upgrade instead of Full

  • The product version and database version are not compatible

    The following simple program gets an exception {The product version and database version are not compatible} its very hard to proceed from here. Does anybody know what cause this?  
    Best Regards
    Jan Isacsson
    using System.Collections.ObjectModel;
    using Microsoft.MasterDataServices.Deployment;
    using Microsoft.MasterDataServices.Services.DataContracts;
    namespace MdsDeploy
        class Program
            static void Main(string[] args)
                try
                    ModelReader reader = new ModelReader();
                    Collection<Identifier> models = reader.GetModels();
                    foreach (Identifier modelId in models)
                        Console.WriteLine(modelId.Name);
                catch (System.Exception ex)
                    Console.WriteLine("Error: " + ex.Message);
                Console.ReadKey();

    Hi Jan,
    For the error "The product version and database version are not compatible", as Emma said, the version number of the Service does not match the database schema version.
    In your scenario, which version of database are you using? Please note that MDS update required after SQL 2012 SP1 installation, please refer to the links below to see the details.
    http://byobi.com/blog/2012/11/mds-update-required-after-sql-2012-sp1-installation/
    http://msdn.microsoft.com/en-IN/library/gg488708.aspx
    Regards,
    Charlie Liao
    TechNet Community Support

  • REM Product cost collectors and Production version

    Hi All,
    Can some one pls let me know
    What are the product cost collectors in REM and how to create the product cost collectors ?
    What is the production version and the difference between production version and controlling version?
    Thanks & Regards,
    Bujji

    Dear Bujji,
    A product cost collector is a cost object in Product Cost by Period that collects the periodic actual costs incurred in the production of a material. It can be created in txn KKF6N.
    [Product Cosr Collector|http://help.sap.com/saphelp_47x200/helpdata/EN/08/77ba810a1611d3a6b900104b55d538/frameset.htm]
    [Product Cost Collectors: Collective Entry for Repetitive Manufacturing |http://help.sap.com/saphelp_47x200/helpdata/EN/08/77ba810a1611d3a6b900104b55d538/frameset.htm]
    A production version determines the various production techniques that can be used to produce a material. It defines the following information:
    Alternative BOM for a BOM explosion
    Task list type, task list group, and group counter for assignment to task lists
    Lot-size restrictions and period of validity
    A material can have one or more production versions.
    It can be defined in the Material Master (txn MM02) in one of the following views:
    MRP 4
    Work Scheduling
    Costing 1
    The costing version is a different issue. It is a costing parameter and is used to save several cost estimates for the same material, with the same costing variant and the same costing date (e.g. in oder to cost the material several times with minor changes without creating new costing variants).
    BR,
    Antje

  • Problem using production version of SQL Server 2005 JDBC drivers

    A production version of the Microsoft SQL Server 2005 JDBC driver became available on 1/20/06, and we are having some issues getting it to work with WLS 9.1. The non-XA driver works fine, but when we attempt to use the XA version, we see the error below in our logs. (Note that in the text "status:0 msg:null", the "null" is actually an unprintable character that I was not able to copy/paste.)
    We have successfully tested WLS 9.1 with the beta JDBC drivers that were released by Microsoft a number of months ago, so this appears to be a problem with the prod version only (although we had no trouble using the prod drivers with JBoss). We have actually opened a support case for this, but the response we have received thus far has been negligible at best and we really need to get this issue resolved, so I am posting the problem here as well to see if anyone else has encountered it.
    Regards,
    Sabrina
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
    Caused by: ourpackage.OurDBUtil.openConnection(OurDBUtil.java:130)     
         ... 11 more
    Caused by: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XA_OK start() failed on resource 'OurXADataSource': XA_OK
    javax.transaction.xa.XAException: java.sql.SQLException: Failed to create the XA control connection. Error: xp_sqljdbc_xa_init failure, status:0 msg:null.
         at com.microsoft.sqlserver.jdbc.SQLServerXAResource.start(Ljavax.transaction.xa.Xid;I)V(Unknown Source)
         at weblogic.jdbc.jta.DataSource.start(DataSource.java:679)
         at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1160)
         at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1093)
         at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:496)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:428)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1390)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1395)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1327)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)
         ... 12 more

    SabrinaL wrote:
    A production version of the Microsoft SQL Server 2005 JDBC driver became available on 1/20/06, and we are having some issues getting it to work with WLS 9.1. The non-XA driver works fine, but when we attempt to use the XA version, we see the error below in our logs. (Note that in the text "status:0 msg:null", the "null" is actually an unprintable character that I was not able to copy/paste.)
    We have successfully tested WLS 9.1 with the beta JDBC drivers that were released by Microsoft a number of months ago, so this appears to be a problem with the prod version only (although we had no trouble using the prod drivers with JBoss). We have actually opened a support case for this, but the response we have received thus far has been negligible at best and we really need to get this issue resolved, so I am posting the problem here as well to see if anyone else has encountered it.
    Regards,
    SabrinaHi. Have you done all the XA-related install for the new MS driver? (put the XA
    dll in the DBMS environment etc)? Is your DBMS on a 32-bit machine or 64-bit machine?
    Does the driver present a dll for each of those? You can also get good JDBC help
    from MS via their microsoft.public.sqlserver.jdbcdriver newsgroup.
    Joe Weinstein at BEA
    >
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
    Caused by: ourpackage.OurDBUtil.openConnection(OurDBUtil.java:130)     
         ... 11 more
    Caused by: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XA_OK start() failed on resource 'OurXADataSource': XA_OK
    javax.transaction.xa.XAException: java.sql.SQLException: Failed to create the XA control connection. Error: xp_sqljdbc_xa_init failure, status:0 msg:null.
         at com.microsoft.sqlserver.jdbc.SQLServerXAResource.start(Ljavax.transaction.xa.Xid;I)V(Unknown Source)
         at weblogic.jdbc.jta.DataSource.start(DataSource.java:679)
         at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1160)
         at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1093)
         at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:496)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:428)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1390)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1395)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1327)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)
         ... 12 more

Maybe you are looking for