Error while looking up EJB

Hello,
I'm trying to develop EJBs 2.0 for my company.
creation and EJB deployment works fine, but when I try to look up my EJB, I get a NamingException.
EAR is deployed on a Websphere Application Server 5.1, and I would like to communicate with my EJB in a portlet. This portlet is deployed on a Websphere portal Server 5.1. WPS ans WAS servers are on the same system.
this is my JSP code :
Context ctx = new InitialContext();
Object obj = ctx.lookup("ejb/fr/test/ejbtest/EJBTest2Home");
EJBTest2Home cacheHome = (EJBTest2Home)javax.rmi.PortableRemoteObject.narrow(obj, EJBTest2Home.class);I think my InitialContext is Websphere Portal Server so it cannot access to my EJB interface deployed on the Websphere Application Server 5.1
Thx for your help !

Hi,
I guess u had made 2 mistakes.
First one as to ur guess, u got the IntialContext wrong and secondly u should lookup the HomeObject using JNDI name instead of the fully qualified classpath.
I am not so sure of websphere5.1, but for most of the servers have diff context for webcontainer and BeanContainer
First u try to get it done changing the code to,
ctx.lookup("ejb/fr/test/ejbtest/EJBTest2Home");
to
ctx.lookup("JNDIName");
if it doesnt workout then do changes to the context as well
Thanks and Regards
Srikanth

Similar Messages

  • RMAN-06010: error while looking up datafile: 82

    Iam building dataguard - Physical Standby database by using the RMAN duplicate command and we are not using the recovery catalog but control file.
    Iam getting the following error while running the duplicate command.
    set newname for datafile 82 to
    "/dflx02/flx/o01flx3rbs/rbs02_02.O01FLX3";
    RMAN-06010: error while looking up datafile: 82
    Actually we dropped the datafile(tablespace) before taken the backup but it is giving error though we are using the latest control file.
    I do not see this file is available in the database as we dropped it successfully.
    Could some one let me know what could be the problem and how to resolve it.
    Your early response is greatly appreciated.
    Note:
    backup script -- It went successfully.
    # Script to be used to backup the production in preparation of creating a DataGuard instance
    YYYY=`date +"%Y"`
    mmdd=`date +"%m%d"`
    hh=`date +"%H"`
    mm=`date +"%M"`
    ss=`date +"%S"`
    hhmmss=${hh}${mm}${ss}
    dt=${YYYY}${mmdd}_${hhmmss}
    echo "Starting backup on O01FLX3"
    $ORACLE_HOME/bin/rman nocatalog <<EOF >> /dflx02/flx/oracle/log/full_backup_run_$dt.log
    connect target /
    configure device type disk clear;
    configure channel device type disk maxpiecesize 4G;
    configure device type disk backup type to compressed backupset parallelism 8;
    run{
    change archivelog all validate;
    backup current controlfile for standby format '/tmp/stby_snapcf_O01FLX3.f';
    backup database format '/dflx02/flx/o01flx3dump/rman/O01FLX3_%s_%p_%T_%t.bak';
    sql 'alter system archive log current';
    backup archivelog all format '/dflx02/flx/o01flx3dump/rman/O01FLX3_%s_%p_%T_%t.arc';
    EXIT
    EOF
    duplicate Script:
    #!/bin/ksh
    # Script to create standby database for production.
    YYYY=`date +"%Y"`
    mmdd=`date +"%m%d"`
    hh=`date +"%H"`
    mm=`date +"%M"`
    ss=`date +"%S"`
    hhmmss=${hh}${mm}${ss}
    dt=${YYYY}${mmdd}_${hhmmss}
    echo "Starting dataguard instance on O01FLX3DR"
    $ORACLE_HOME/bin/rman nocatalog <<EOF >> /dflx02/flx/oracle/log/cr_stdby_O01FLX3$dt.log
    connect target /
    connect auxiliary sys/xxxxxx@O01FLX3DR
    configure channel device type disk maxpiecesize 4G;
    configure device type disk backup type to compressed backupset parallelism 8;
    run {
    set until time "to_date('20080217:19:00', 'YYYYMMDD:HH24:MI')";
    duplicate target database for standby dorecover nofilenamecheck;
    exit;
    EOF
    set newname for datafile 82 to
    "/dflx02/flx/o01flx3rbs/rbs02_02.O01FLX3";

    Thank you for your reply. Actually Iam not renaming the datafile but building the
    dataguard instance and some how control file is looking for old datafile that was deleted.
    Actually both primary and dataguard instances are running on 10.2.0.3 . Oracle control file is listing the datafile 82 as old deleted file, while building the dataguard.
    ---- This file was deleted long time back but still oracle control file is looking for this file while building the dataguard. Iam using the latest control file.
    set newname for datafile 82 to
    "/dflx02/flx/o01flx3rbs/rbs02_02.O01FLX3"
    When I listed the datafile 82, it is showing the correct datafile.
    RMAN> list backup of datafile 82;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    50234 Incr 2 26.93M DISK 00:04:03 18-FEB-08
    BP Key: 101470 Status: AVAILABLE Compressed: YES Tag: DATABASE_BACKUP
    Piece Name: /dflx02/flx/o01flx3dump/rman/O01FLX3_51757_1_20080218_647031779.bak
    List of Datafiles in backup set 50234
    File LV Type Ckp SCN Ckp Time Name
    82 2 Incr 7953177017970 18-FEB-08 /dflx02/flx/o01flx3ndx15/flx_ndx3_18.O01FLX3
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    50334 Incr 2 27.76M DISK 00:04:16 19-FEB-08
    BP Key: 101587 Status: AVAILABLE Compressed: YES Tag: DATABASE_BACKUP
    Piece Name: /dflx02/flx/o01flx3dump/rman/O01FLX3_51857_1_20080219_647119328.bak
    List of Datafiles in backup set 50334
    File LV Type Ckp SCN Ckp Time Name
    82 2 Incr 7953257549488 19-FEB-08 /dflx02/flx/o01flx3ndx15/flx_ndx3_18.O01FLX3
    So Iam thinking that there should be a problem in control file and let me know how to resolve it.
    Please let me know if you have any questions.
    Thanks for your help.
    Suresh.D

  • Error while compiling the ejb java source files.................

    hi,
    i am new to ejb.......
    i have got error while compiling the ejb java source files............
    while compiling..........of this three i ahve got err in ejb home interface....
    ejb remote interface - succeded
    ejb bean class - succeded
    ejb home interface - error
    the error..............is in the return type of the ejb create() method in ejb home interface(which is the type of remote interface).
    the error message is cannot resolve symbol

    Hi,
    thanks for ur reply .....
    i have done enough searching in all sites including sun forum but in vain
    i have pasted my error below...
    can u plz predict anything from it
    D:\>path=%path%;c:\j2sdk1.4.2_12\bin;
    D:\>set classpath=%classpath%;d:\Sun\AppServer\lib\j2ee.jar;
    D:\>javac d:\Librarys\Library.java
    D:\>javac d:\Librarys\LibraryBean.java
    D:\>javac d:\Librarys\LibraryHome.java
    d:\Librarys\LibraryHome.java:8: cannot resolve symbol
    symbol : class Library
    location: interface Librarys.LibraryHome
    public Library create(String id, String name, String address, String phoneNo
    ) throws RemoteException, CreateException;
    ^
    d:\Librarys\LibraryHome.java:9: cannot resolve symbol
    symbol : class Library
    location: interface Librarys.LibraryHome
    public Library findByPrimaryKey(String id) throws FinderException, RemoteExc
    eption;
    ^
    2 errors
    thanks in advance...

  • "Errored while looking up datasource: PWC4216: Name myDB is not bound in th

    hi all,
    am trying to deploy my web application (.war which has a servlet which connects to a db and fetches records and displays in jsp) file in SunOne web server V7 but i cant get past this error :
    [29/Jun/2010:15:14:46] failure (24218): for host 146.171.59.144 trying to POST /BbaMigrationQueryTool/BBAMigrationQuery, service-j2ee reports: NamingExcep
    tion caught: Errored while looking up datasource: PWC4216: Name myDB is not bound in this Context
    my java code to lookup the jndi name :
       1.     //looks up a datasource 
       2.     private static synchronized DataSource getDataSource(String jndiName) throws NamingException { 
       3.  
       4.         DataSource dataSource = null; 
       5.  
       6.         try { 
       7.             Context c = new InitialContext(); 
       8.              Context envContext = (Context) c.lookup("java:comp/env"); 
       9.             Logger.getLogger(DBUtilities.class.getName()).log(Level.INFO, "Found sub context"); 
      10.               dataSource = (DataSource) envContext.lookup(jndiName); 
      11.  
      12.         } catch (NamingException e) { 
      13.             e.printStackTrace(); 
      14.             throw new NamingException("Errored while looking up datasource: " + e.getMessage()); 
      15.         } 
      16.  
      17.         return dataSource; 
      18.     } 
      i call the above method with "jdbc/myDB" and have created a JDBC recourse within the SunOne web server via the admin console.
    my web.xml i have an entry for the resource as follows :
       1.             <resource-ref> 
       2.         <res-ref-name>jdbc/myDB</res-ref-name> 
       3.         <res-type>javax.sql.DataSource</res-type> 
       4.         <res-auth>Container</res-auth> 
       5.         <res-sharing-scope>Shareable</res-sharing-scope> 
       6.     </resource-ref> 
    in my sun-web.xml i have an entry as follows :
       1.     <resource-ref> 
       2.         <res-ref-name>jdbc/myDB</res-ref-name> 
       3.         <jndi-name>jdbc/myDB</jndi-name> 
       4.     </resource-ref> 
    server.xml has this entry in it :
       1.   <jdbc-resource> 
       2.     <jndi-name>jdbc/myDB</jndi-name> 
       3.     <datasource-class>oracle.jdbc.pool.OracleDataSource</datasource-class> 
       4.     <property> 
       5.       <name>password</name> 
       6.       <value>76765</value> 
       7.     </property> 
       8.     <property> 
       9.       <name>user</name> 
      10.       <value>56756</value> 
      11.     </property> 
      12.     <property> 
      13.       <name>url</name> 
      14.       <value>jdbc:oracle:thin:@serveretc etc</value> 
      15.     </property> 
      16.     <description/> 
      17.   </jdbc-resource>
      what could be wrong ??
    thanks in advance.
    Edited by: cesarNZ on Jun 29, 2010 7:58 PM
    Edited by: cesarNZ on Jun 29, 2010 8:00 PM

    try to not split the attributes in server.xml
    use them like
    <Context path="/myPath" docBase="myDocBase" debug="5" reloadable="true" crossContext="true" source="org.eclipse.jst.j2ee.server:myDocBase">
                          <Resource name="jdbc/myDB"
                                                     auth="Container"
                                                     type="javax.sql.DataSource"
                                                     maxActive="100"
                                                     maxIdle="30"
                                                     maxWait="10000"
                                                     username="$$$"
                                                     password="$$$"
                                                     driverClassName="com.mysql.jdbc.Driver"
                                                     url="jdbc:mysql://localhost/myTest" />
                     </Context>and i dont know why you define two resources
    try to look at
    http://forums.sun.com/thread.jspa?messageID=11013089&#11013089

  • Getting error while deploying the ejb in jboss3.2.3

    i m getting following error msg while deploying my ejb in jboss-3.2.3. i m deploying the same code available at
    http://www.ftponline.com/javapro/2003_01/online/j2ee_bkurniawan_01_09_03/
    04:30:48,955 INFO [MainDeployer] Starting deployment of package: file:/home/ami
    tt/jboss-3.2.3/server/default/deploy/StringProcessor.jar
    04:30:48,972 ERROR [MainDeployer] could not create deployment: file:/home/amitt/
    jboss-3.2.3/server/default/deploy/StringProcessor.jar
    org.jboss.deployment.DeploymentException: ejb-jar.xml must define a valid DOCTYP
    E!
    at org.jboss.metadata.ApplicationMetaData.importEjbJarXml(ApplicationMet
    aData.java:206)
    at org.jboss.metadata.XmlFileLoader.load(XmlFileLoader.java:141)
    at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:436)
    at org.jboss.deployment.MainDeployer.create(MainDeployer.java:786)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:641)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605)
    at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea nDispatcher.java:284)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
    at $Proxy6.deploy(Unknown Source)
    at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen tScanner.java:302)
    at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS canner.java:476)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread. doScan(AbstractDeploymentScanner.java:201)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread. loop(AbstractDeploymentScanner.java:212)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread. run(AbstractDeploymentScanner.java:191)
    Please reply me bak the required solution.......

    looks like your xml files are not done.

  • JMS error while looking up from Client

    Hi
    I am looking up a JMS factory though a stand alone client in SAP web as Sp 15. While looking up through JNDI  we are getting a deserialisation error . I have included all the j2ee client jars in the classpath. Any idea do we need to include some other jars also ..
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name jmsFactory/CXLQueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: Cannot lookup ManageConnectionFactory "CXLQueueConnectionFactory". Cannot deserialize object: com.sap.engine.services.jmsconnector.exceptions.BaseClassNotFoundException: Deserialization Error: java.lang.NoClassDefFoundError: com/sap/jms/server/SynchronousNetworkAdapter
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:141)
         at com.sap.engine.services.jndi.persistent.ClientCPOInputStream.resolveClass(ClientCPOInputStream.java:52)
         at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1513)
         at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1435)
         at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1626)
         at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
         at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
         at com.sap.engine.services.jndi.persistent.RemoteSerializator.toObject(RemoteSerializator.java:70)
         at com.sap.engine.services.jndi.implclient.ClientContext.deserializeObject(ClientContext.java:3349)
         at com.sap.engine.services.jndi.implclient.ClientContext.deserializeDirObject(ClientContext.java:3303)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:385)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at com.sap.engine.services.jmsconnector.spi.ManagedConnectionFactoryImpl.readObject(ManagedConnectionFactoryImpl.java:318)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:838)
         at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1746)
         at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
         at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
         at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)
         at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)
         at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
         at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
         at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
         at com.sap.engine.services.jndi.persistent.RemoteSerializator.toObject(RemoteSerializator.java:70)
         at com.sap.engine.services.jndi.implclient.ClientContext.deserializeObject(ClientContext.java:3349)
         at com.sap.engine.services.jndi.implclient.ClientContext.deserializeDirObject(ClientContext.java:3303)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:385)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:165)
         at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:301)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:522)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:204)
         at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:172)
         at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:261)
         at com.sap.engine.services.jmsconnector.spi.ManagedConnectionFactoryImpl.readObject(ManagedConnectionFactoryImpl.java:334)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:838)
         at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1746)
         at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
         at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
         at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)
         at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)
         at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
         at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
         at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
         at com.sap.engine.services.jndi.persistent.RemoteSerializator.toObject(RemoteSerializator.java:70)
         at com.sap.engine.services.jndi.implclient.ClientContext.deserializeObject(ClientContext.java:3349)
         at com.sap.engine.services.jndi.implclient.ClientContext.deserializeDirObject(ClientContext.java:3303)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:385)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:165)
         at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:301)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:522)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:204)
         at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:172)
         at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:261)
    Any help on this will be appreciated.
    regards
    rajesh kr

    Hi Rajesh,
    Please add the jar file "sapjms.jar" to your classpath,
    it is situated at
    \usr\sap\<sid>\<id>\j2ee\cluster\server0\bin\services\jms_provider
    HTH
    Peter

  • Error while Look up session bean (EJB 3.0) in WebDynpro

    hi ,
                 I want to look up session bean inside webdynpro. I hv written following code inside init of component controller. but not able to look up session bean
    try{
                   InitialContext context = new InitialContext();
                   ApplicationFetcherLocal applicationFetcherLocal = null;
                 applicationFetcherLocal = (ApplicationFetcherLocal)context.lookup((ApplicationFetcherLocal.class.getName());
              catch (Exception ex){
                   System.err.println("LookUp Failed\n\n"+ex.getMessage());

    Have you read my latest reply in your other [thread|session bean look up  across DCs in EJB3.0;?
    What's the value of asking the same question again if you don't care about the answer?
    Regards,
    -- Vladimir

  • Error while looking up bean from Eclipse plugin

    Hi all,
       I am developing an Eclipse plugin which calls session bean deployed in some j2ee engine. But I am facing a problem while I try to look up the bean. It gives me an error saying <i>"com.sap.engine.services.jndi.persistent.UnsatisfiedReferenceImpl"</i>.
    I tried print out the UnsatisfiedReferenceImpl stacktrace and it says
    <i>java.lang.ClassNotFoundException: com.sap.engine.services.ejb.session.stateless_sp5.SerializedHomeProxy</i>.
    Does anyone have any idea?
    Regards,
    Satyajit.
    Message was edited by:
            Satyajit Chakraborty

    I have solved the problem. The problem was with an extra classpath entry.
    Regards,
    Satyajit.

  • Error while migrating orion-ejb-jar.xml from OC4J 9.0.4.1

    I am trying to use Toplink migration tool to take our existing orion-ejb-jar.xml file and toplink-ejb-jar.xml file to new 10.1.3 deployment. While running the migration tool I get the following error
    WARNING: Oc4j native CMP setting optimistic-locking on
    entity(TransactionTypeEntityBean) is not migrated and supported.
    java.lang.IllegalArgumentException: MWDatabaseField[9BE2B5]
    (TAX_RULE.TAX_RULE_ID)
    at
    oracle.toplink.workbench.mappingsmodel.desc.relational.MWRelationalPrima
    ryKeyPolicy.addPrimaryKey(MWRelationalPrimaryKeyPolicy.java:99)
    at
    oracle.toplink.tools.migration.RuntimeCMPProjectToMWProjectConverter.con
    vertDescriptor(RuntimeCMPProjectToMWProjectConverter.java:297)
    at
    oracle.toplink.tools.migration.RuntimeCMPProjectToMWProjectConverter.con
    vertDescriptors(RuntimeCMPProjectToMWProjectConverter.java:265)
    at
    oracle.toplink.tools.migration.RuntimeCMPProjectToMWProjectConverter.con
    vertProject(RuntimeCMPProjectToMWProjectConverter.java:144)
    at
    oracle.toplink.tools.migration.MigrationManagerBase.convertAndWriteoutMW
    Project(MigrationManagerBase.java:369)
    at
    oracle.toplink.tools.migration.MigrationManagerBase.migrate(MigrationMan
    agerBase.java:358)
    at
    oracle.toplink.tools.migration.io.MigrationIOManager.buildMigratedJarFil
    e(MigrationIOManager.java:243)
    at
    oracle.toplink.tools.migration.io.MigrationIOManager.operateEarEntry(Mig
    rationIOManager.java:181)
    at
    oracle.toplink.tools.migration.io.MigrationIOManager.operateEar(Migratio
    nIOManager.java:145)
    at
    oracle.toplink.tools.migration.io.MigrationIOManager.operateIO(Migration
    IOManager.java:88)
    at
    oracle.toplink.tools.migration.MigrationManagerBase.startMigration(Migra
    tionManagerBase.java:280)
    at
    oracle.toplink.tools.migration.MigrationManagerBase.run(MigrationManager
    Base.java:121)
    at
    oracle.toplink.tools.migration.MigrationManagerBase.run(MigrationManager
    Base.java:97)
    at
    oracle.toplink.tools.migration.TopLinkCMPMigrator.main(TopLinkCMPMigrato
    r.java:59)

    Hello,
    The warning message looks to be unrelated to the java.lang.IllegalArgumentException error. The warning states that optimistic locking cannot be migrated to the toplink-ejb-jar.xml file; this is stated in chapter 7 of the TopLink developer's guide at
    http://download-west.oracle.com/otn_hosted_doc/toplink/1013/MAIN/_pdf/b13593_v1_01.pdf
    The exception though seems to indicate that your orion-ejb-jar.xml contains EJBs mapped to the same table that are not related through EJB inheritance. I do it all the time with POJOs so this will work in TopLink, but you will need a support case to help get your project migrated if this is the case.
    Best Regards,
    Chris Delahunt

  • RJVM has already been shutdown error while looking upto Foreign Server

    Hi,
    I am trying to set up 2 new servers in a clustered environment. In this I have configured a Foreign Server which is looking up to queues in different server.
    The structure is like this: 1 Foreign Server with 2 Queues and 1 Connection factory with exactly same name as they present on the host server.
    While starting the server, I am getting an exception:
    <Nov 5, 2012 7:39:58 PM EET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: ClonedQueueAnonymousWaiter is unable to connect to the JMS destination: MDB_QUEUE_RESPONSE. The Error was:
    javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalException: RJVM has already been shutdown; nested exception is:
         java.io.IOException: RJVM has already been shutdown]
         at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:74)
         at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:470)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:426)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:221)
         at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
         at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
         at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at weblogic.jms.common.CDS$2.run(CDS.java:486)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:131)
         at weblogic.jms.common.CDS.lookupDestination(CDS.java:480)
         at weblogic.jms.common.CDS.lookupDDAndCalloutListener(CDS.java:345)
         at weblogic.jms.common.CDS.access$100(CDS.java:41)
         at weblogic.jms.common.CDS$DDListenerRegistrationTimerListener.timerExpired(CDS.java:193)
         at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    Caused by: java.rmi.UnmarshalException: RJVM has already been shutdown; nested exception is:
         java.io.IOException: RJVM has already been shutdown
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:360)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
         at weblogic.jndi.internal.ServerNamingNode_1034_WLStub.lookup(Unknown Source)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:423)
         ... 21 more
    Caused by: java.io.IOException: RJVM has already been shutdown
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
         ... 24 more
    Caused by: java.io.IOException: RJVM has already been shutdown
         at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:513)
         at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:900)
         at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
         at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:404)
         at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:109)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:345)
         ... 24 more
    >
    Weblogic is installed in Solaris machine and welogic's version is 10.3.4.0 with Java version 1.6.0 update 33. I have checked the firewall, /etc/hosts but there are no issues with that.
    The JNDI Connection URL is configure like: t3://xx.xxx.x.xx,xx.xxx.x.xx:7001/
    I have tried giving like this also: t3://xx.xxx.x.xx:7001,xx.xxx.x.xx:7001/ or t3://hostname1,hostname2:7001/ or t3://hostname1:7001,hostname2:7001/
    but nothing worked.
    The foreign servers are accessible from my Application Server when I do the telnet on the port. There is no cross domain security required. Funny thing is I have a same set-up in two other application server (in cluster again) and there on configuring the Foreign server to same IPs, I am not facing any issues at all.
    Can anyone please help me with this. Searched all over the place but have no clue regarding this. Many forums mentioned about firewall and etc/hosts but that is also not case it seems.
    Regards,
    Priyam

    809364 wrote:
    You can apply the below debug flags to check t he RJVM Communication in detail and figure out what's going wrong and do apply it at both the side
    -Dweblogic.kernel.debug=true
    -Dweblogic.debug.DebugConnection=true
    -Dweblogic.StdoutDebugEnabled=true
    -Dweblogic.log.LogSeverity=Debug
    -Dweblogic.log.LoggerSeverity=DebugI added the debug as you mentioned and I get the below information there:
    <Nov 6, 2012 11:41:16 AM EET> <Debug> <RJVM> <BEA-000500> <RJVMFinder trying to find rjvm for t3://moon1,moon2:7001->moon1,moon2:[7001, -1, -1, -1, -1, -1, -1]->[]
    Active RJVMs:
    {-8968250770921317063S:10.160.1.115:[7001,-1,-1,-1,-1,-1,-1]:fcdb_domain:AdminServer on [10.160.1.115:7001]=weblogic.rjvm.RJVMImpl@4320d68d - id: '-8968250770921317063S:10.160.1.115:[7001,-1,-1,-1,-1,-1,-1]:fcdb_domain:AdminServer' connect time: 'Tue Nov 06 11:40:26 EET 2012'}
    Synonyms:
    {}>
    <Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Bootstrapping connection to: 'moon1/10.160.1.40:7001' using: 't3'>
    <Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Looking for a new connection for channel Default[t3]:t3(t3):venus1:7001:null:-1 to remote server 0B:10.160.1.40:[7001,-1,-1,-1,-1,-1,-1,-1,-1] active connections: {}>
    <Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <New connection for protocol t3, remote address moon1/10.160.1.40, remote port 7001, over channel Default[t3]>
    <Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Added: 'Default[t3]:t3(t3):venus1:7001:null:-1' connection: 'weblogic.rjvm.t3.MuxableSocketT3$T3MsgAbbrevJVMConnection@7582aacf'. Connections list size 1>
    <Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Bootstrapping using a: 't3', connection to: 'moon1/10.160.1.40' on port: '7001'>
    <Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Created RJVM for: '-3712802650201056847S:10.160.1.40:[7001,-1,-1,-1,-1,-1,-1]:fcj_domain:ManagedServer1 on [10.160.1.40:7001]', Active RJVMs:
    {-8968250770921317063S:10.160.1.115:[7001,-1,-1,-1,-1,-1,-1]:fcdb_domain:AdminServer on [10.160.1.115:7001]=weblogic.rjvm.RJVMImpl@4320d68d - id: '-8968250770921317063S:10.160.1.115:[7001,-1,-1,-1,-1,-1,-1]:fcdb_domain:AdminServer' connect time: 'Tue Nov 06 11:40:26 EET 2012', -3712802650201056847S:10.160.1.40:[7001,-1,-1,-1,-1,-1,-1]:fcj_domain:ManagedServer1 on [10.160.1.40:7001]=weblogic.rjvm.RJVMImpl@7bb8a8c6 - id: '-3712802650201056847S:10.160.1.40:[7001,-1,-1,-1,-1,-1,-1]:fcj_domain:ManagedServer1' connect time: 'Tue Nov 06 11:41:17 EET 2012'}
    Synonyms:
    {}>
    <Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Remote heartbeat: '60000', local heartbeat: '60000'>
    <Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Setting heartbeat for RJVM: '-3712802650201056847S:10.160.1.40:[7001,-1,-1,-1,-1,-1,-1]:fcj_domain:ManagedServer1' to: '60000' milliseconds>
    <Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Added: 'Default[t3]:t3(t3):venus1:7001:null:-1' connection: 'weblogic.rjvm.t3.MuxableSocketT3$T3MsgAbbrevJVMConnection@7582aacf'. Connections list size 1>
    <Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000517> <Error on connection: 'weblogic.rjvm.t3.MuxableSocketT3$T3MsgAbbrevJVMConnection@7582aacf'
    java.io.EOFException
    java.io.EOFException
         at weblogic.rjvm.t3.MuxableSocketT3.endOfStream(MuxableSocketT3.java:345)
         at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:826)
         at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:760)
         at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:941)
         at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:898)
         at weblogic.socket.DevPollSocketMuxer.processSockets(DevPollSocketMuxer.java:126)
         at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
         at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    >
    <Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Signaling peer: '-3712802650201056847S:10.160.1.40:[7001,-1,-1,-1,-1,-1,-1]:fcj_domain:ManagedServer1' gone - weblogic.rjvm.PeerGoneException: ; nested exception is:
         java.io.EOFException>
    <Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Closed and removed: 't3' connection to: '-3712802650201056847S:10.160.1.40:[7001,-1,-1,-1,-1,-1,-1]:fcj_domain:ManagedServer1'. Connections list size 0>
    <Nov 6, 2012 11:41:17 AM EET> <Debug> <RJVM> <BEA-000500> <Closing: '-3712802650201056847S:10.160.1.40:[7001,-1,-1,-1,-1,-1,-1]:fcj_domain:ManagedServer1'>
    <Nov 6, 2012 11:41:17 AM EET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: ClonedQueueAnonymousWaiter is unable to connect to the JMS destination: MDB_QUEUE_RESPONSE. The Error was:
    javax.naming.CommunicationException [Root exception is weblogic.rjvm.PeerGoneException: ; nested exception is:
         java.io.EOFException]
         at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:74)
         at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:470)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:426)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:221)
         at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
         at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
         at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at weblogic.jms.common.CDS$2.run(CDS.java:486)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:131)
         at weblogic.jms.common.CDS.lookupDestination(CDS.java:480)
         at weblogic.jms.common.CDS.lookupDDAndCalloutListener(CDS.java:345)
         at weblogic.jms.common.CDS.access$100(CDS.java:41)
         at weblogic.jms.common.CDS$DDListenerRegistrationTimerListener.timerExpired(CDS.java:193)
         at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    Caused by: weblogic.rjvm.PeerGoneException: ; nested exception is:
         java.io.EOFException
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
         at weblogic.jndi.internal.ServerNamingNode_1034_WLStub.lookup(Unknown Source)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:423)
         ... 21 more
    Caused by: java.io.EOFException
         at weblogic.rjvm.t3.MuxableSocketT3.endOfStream(MuxableSocketT3.java:345)
         at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:826)
         at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:760)
         at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:941)
         at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:898)
         at weblogic.socket.DevPollSocketMuxer.processSockets(DevPollSocketMuxer.java:126)
         at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
         at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    >
    Seems like Peer gone exception is the root cause of this. Any idea for this ?
    Regards,
    Priyam
    Edited by: Priyam Srivastava on Nov 6, 2012 2:49 AM

  • Error While Calling a EJB

    Hai,
            I had created a java class that includes the EJB in it
    The code is given below  :
    Properties props = new Properties();
              try
                   props.put  (Context.INITIAL_CONTEXT_FACTORY,"com.sap.engine.services.jndi.InitialContextFactoryImpl");
                   props.put(Context.PROVIDER_URL, "<server name >:<server port>");
              catch (Exception e1)
                   System.out.println("Exception  1 -
    > "+e1.getMessage());
              try
                Context ctx = new InitialContext(props);
                Object o = ctx.lookup("sap.com/DivEAR/LOCAL/com.sap.sdn.ejb.DivLocalHome");
                System.out.println("Test");
                DivHome  home = (DivHome)PortableRemoteObject.narrow(o,DivHome.class);
                Div  dref  = home.create();
                System.out.println(dref.Divide(20,4));
            catch (Exception e2)
                e2.printStackTrace();
    But it gives the following Error :
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: cannot establish connection with any of the available instances:
    192.168.1.37:50200 Reason: Cannot open connection on host: 192.168.1.37 and port: 50200]
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:455)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
         at javax.naming.InitialContext.init(InitialContext.java:223)
         at javax.naming.InitialContext.<init>(InitialContext.java:197)
         at com.sap.sdn.client.DivisionClient.main(DivisionClient.java:44)
    Caused by: com.sap.engine.interfaces.cross.DestinationException: cannot establish connection with any of the available instances:
    192.168.1.37:50200 Reason: Cannot open connection on host: 192.168.1.37 and port: 50200
         at com.sap.engine.interfaces.cross.Destination.getNextAvailableBroker(Destination.java:53)
         at com.sap.engine.interfaces.cross.Destination.getRemoteBroker(Destination.java:33)
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:340)
         ... 5 more
    Can anyone help me solve the problem.
    Regards,
    R.Jude Silvester.
    Edited by: Jude Silvester on Jan 28, 2009 12:06 PM

    Hai Rajat,
                   I pinged and got replied from Server.
    Now i tried the following Code :
                         try{
                               Properties props=new Properties();
                               props.put(Context.INITIAL_CONTEXT_FACTORY,
              "com.sap.engine.services.jndi.InitialContextFactoryImpl");
              props.put(Context.PROVIDER_URL, "sapsrv02:50200");
              wdContext.currentContextElement().setExc("No Exception : ");
              Context ctx = new InitialContext(props);
                               Object o = ctx.lookup("sap.com/DivEAR/REMOTE/com.sap.sdn.ejb.Div");
         catch (Exception e)
              wdContext.currentContextElement().setExc("Exception : "+e.getMessage());
      got the Error :
       Path to object does not exist at REMOTE, the whole lookup name is sap.com/DivEAR/REMOTE/com.sap.sdn.ejb.Div.
    Can you please help me solve this problem.
    Regards,
    Jude

  • Error while calling for EJB

    I use SunONE app server 7, JDK 1.4.1_01, on Windows 2000 server SP4.
    When EJB client EJB, the followed error message would be occured!
    What's the problem?
    Any clues are welcomed.
    WARNING:
    java.lang.Exception
    at com.sun.corba.ee.internal.iiop.IIOPConnection.cleanUp(IIOPConnection.java:976)
    at com.sun.corba.ee.internal.iiop.ConnectionTable.cleanUp(ConnectionTable.java:370)
    at com.sun.corba.ee.internal.iiop.ConnectionTable.checkConnectionTable(ConnectionTable.java:391)
    at com.sun.corba.ee.internal.iiop.ListenerThread.run(ListenerThread.java:96)

    Hi Patrick,
    This could be due to many reasons:
    1.Server died while you tried to connect
    2.Dispatcher died while you tried to connect
    3. You have only one server node and it is set in debug mode. If this is the case then you will not be able to connect via p4.
    Check also the error in the server log files, maybe there is something that gives a hint.
    I hope this helps.
    Myriana

  • [EJB:015001] error while deploying an ejb on weblogic app server

    Hi,
    I'm trying to deploy an ear which has lot of modules and it is failing for one of the ejb module. The exception is as follows:
    <Mar 22, 2011 7:47:01 PM GMT+05:30> <Error> <Deployer> <WL-149265> <Failure occurred in the execution of deployment request with ID '1300803398704' for task '0'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(triv.product.jar)
    [EJB:011023]An error occurred while reading the deployment descriptor. The error was:
    Error processing annotations: .'
    weblogic.application.ModuleException: Exception preparing module: EJBModule(triv.product.jar)
    [EJB:011023]An error occurred while reading the deployment descriptor. The error was:
    Error processing annotations: .
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:469)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
         Truncated. see log file for complete stacktrace
    Caused By: weblogic.utils.ErrorCollectionException:
    There are 1 nested errors:
    weblogic.j2ee.dd.xml.AnnotationProcessException: [EJB:015001]Unable to link class trivnet.product.services.svams.ProjSVAMServiceBean in Jar D:\ccm_wa\TICP-yogesh_3.4.0\TICP\product\classes : java.lang.NoClassDefFoundError: trivnet/service/svams/SVAMService
         at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addProcessingError(BaseJ2eeAnnotationProcessor.java:1323)
         at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addFatalProcessingError(BaseJ2eeAnnotationProcessor.java:1328)
         at weblogic.ejb.container.dd.xml.EjbAnnotationProcessor.processAnnotations(EjbAnnotationProcessor.java:161)
         at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processStandardAnnotations(EjbDescriptorReaderImpl.java:344)
         at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:204)
         at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:93)
         at weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:1245)
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:397)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
         at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
         at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addProcessingError(BaseJ2eeAnnotationProcessor.java:1322)
         at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addFatalProcessingError(BaseJ2eeAnnotationProcessor.java:1328)
         at weblogic.ejb.container.dd.xml.EjbAnnotationProcessor.processAnnotations(EjbAnnotationProcessor.java:161)
         at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processStandardAnnotations(EjbDescriptorReaderImpl.java:344)
         at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:204)
         Truncated. see log file for complete stacktrace
    >
    <Mar 22, 2011 7:47:01 PM GMT+05:30> <Warning> <Deployer> <WL-149004> <Failures were detected while initiating deploy task for application 'ear'.>
    <Mar 22, 2011 7:47:01 PM GMT+05:30> <Warning> <Deployer> <WL-149078> <Stack trace for message 149004
    weblogic.application.ModuleException: Exception preparing module: EJBModule(triv.product.jar)
    [EJB:011023]An error occurred while reading the deployment descriptor. The error was:
    Error processing annotations: .
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:469)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
         Truncated. see log file for complete stacktrace
    Caused By: weblogic.utils.ErrorCollectionException:
    There are 1 nested errors:
    weblogic.j2ee.dd.xml.AnnotationProcessException: [EJB:015001]Unable to link class trivnet.product.services.svams.ProjSVAMServiceBean in Jar D:\ccm_wa\TICP-yogesh_3.4.0\TICP\product\classes : java.lang.NoClassDefFoundError: trivnet/service/svams/SVAMService
         at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addProcessingError(BaseJ2eeAnnotationProcessor.java:1323)
         at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addFatalProcessingError(BaseJ2eeAnnotationProcessor.java:1328)
         at weblogic.ejb.container.dd.xml.EjbAnnotationProcessor.processAnnotations(EjbAnnotationProcessor.java:161)
         at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processStandardAnnotations(EjbDescriptorReaderImpl.java:344)
         at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:204)
         at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:93)
         at weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:1245)
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:397)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
         at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
         at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addProcessingError(BaseJ2eeAnnotationProcessor.java:1322)
         at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.addFatalProcessingError(BaseJ2eeAnnotationProcessor.java:1328)
         at weblogic.ejb.container.dd.xml.EjbAnnotationProcessor.processAnnotations(EjbAnnotationProcessor.java:161)
         at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processStandardAnnotations(EjbDescriptorReaderImpl.java:344)
         at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:204)
         Truncated. see log file for complete stacktrace
    >
    There are two scenarios one of which is working and the other is not. The details are below:
    Scenario 1: (Working)
    There is an ejb module in the ear (say ModA) which has two session beans (SessionA and SessionB having Remote interfcaes RemoteIntA and RemoteIntB).
    There is another ejb module in the ear (say ModB) which has few more session beans.
    Now I want to add an ejb which will extend from SessionA.
    So, I did following changes:
    i. added a remote interface in ModB - RemoteIntPA implements RemoteIntA
    ii. added session bean SessionPA extends SessionA implements RemoteIntPA
    iii. added ejb related annotations in SessionPA and removed the annotations from SessionA (i.e., SessionA is just a normal class by itself)
    Now in the application.xml I declare both modules (ModA and ModB) as ejb modules.
    I deploy the application everything works fine.
    Scenario 2: (Not Working)
    For some reason, I didn't required SessionB in ModA (which was the only ejb bean left in that module as SessionA was converted to normal java class). So I removed SessionB and RemoteIntB.
    Now as there are no ejb beans in ModA, I cannot define this as ejb module in application.xml and hence I defined it as java module.
    Now if I deploy the same application, I get the exception mentioned above.
    I think it has to do with the classpath issue. But how is that the classpath issue is arising when I declaring a module as java and not when I declare it as ejb. I have this module in classpath of ModB. So it doesn't matter what type of module it is.
    Am I missing something?
    Please help me in this regards.

    java.lang.NoClassDefFoundError: trivnet/service/svams/SVAMService
    The JAR with the class trivnet/service/svams/SVAMService is not in the classpath.

  • Error while deploying the EJB - JPA - Hibernate application

    Hi guys,
    i got following exception while deploying my application into the server. can anyone suggest me.
    Failure occurred in the execution of deployment request with ID '1243505041748' for task '0'. Error is: 'java.lang.ClassNotFoundException: org.jboss.util.file.ArchiveBrowser$Filter' java.lang.ClassNotFoundException: org.jboss.util.file.ArchiveBrowser$Filter at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) at java.net.URLClassLoader.access$000(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:626) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:350) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:126) at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactory(PersistenceUnitInfoImpl.java:330) at weblogic.deployment.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoImpl.java:123) at weblogic.deployment.AbstractPersistenceUnitRegistry.storeDescriptors(AbstractPersistenceUnitRegistry.java:331) at weblogic.deployment.AbstractPersistenceUnitRegistry.loadPersistenceDescriptor(AbstractPersistenceUnitRegistry.java:245) at weblogic.deployment.ModulePersistenceUnitRegistry.<init>(ModulePersistenceUnitRegistry.java:63) at weblogic.ejb.container.deployer.EJBModule.setupPersistenceUnitRegistry(EJBModule.java:209) at weblogic.ejb.container.deployer.EJBModule$1.execute(EJBModule.java:310) at weblogic.deployment.PersistenceUnitRegistryInitializer.setupPersistenceUnitRegistries(PersistenceUnitRegistryInitializer.java:62) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:381) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) java.lang.ClassNotFoundException: org.jboss.util.file.ArchiveBrowser$Filter at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) at java.net.URLClassLoader.access$000(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:626) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:350) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:126) at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactory(PersistenceUnitInfoImpl.java:330) at weblogic.deployment.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoImpl.java:123) at weblogic.deployment.AbstractPersistenceUnitRegistry.storeDescriptors(AbstractPersistenceUnitRegistry.java:331) at weblogic.deployment.AbstractPersistenceUnitRegistry.loadPersistenceDescriptor(AbstractPersistenceUnitRegistry.java:245) at weblogic.deployment.ModulePersistenceUnitRegistry.<init>(ModulePersistenceUnitRegistry.java:63) at weblogic.ejb.container.deployer.EJBModule.setupPersistenceUnitRegistry(EJBModule.java:209) at weblogic.ejb.container.deployer.EJBModule$1.execute(EJBModule.java:310) at weblogic.deployment.PersistenceUnitRegistryInitializer.setupPersistenceUnitRegistries(PersistenceUnitRegistryInitializer.java:62) at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:381) at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:17
    I am using
    Hibernate 3.2
    EJB 3
    WebLogic 10.3
    MyEclipse 6.6

    I think I've seen this before and I believe that it might the way Hibernate 3.2 loads classes. I seem to remember actually patching this myself using a fix someone made at one point and getting it to work, but that used to be documented on a dev2dev blog comment that is no longer around :(
    Here are some hints on similar errors:
    https://jira.jboss.org/jira/browse/EJBTHREE-719
    http://forums.java.net/jive/thread.jspa?threadID=16472
    Some Hibernate issues with ANTLR can be resolved if you can put all of the relevant classes in your web-inf/lib or app-inf/lib and use the appropriate deployment descriptors to "prefer" your classes.
    http://download.oracle.com/docs/cd/E12839_01/wls/docs103/webapp/weblogic_xml.html#wp1059286
    There are other similar errors that you might encounter
    http://maniezhilan.blogspot.com/2008/02/hibernate-antlrjar-with-weblogic-server.html

  • Getting error while doing simple ejb

    gettting error like ....javax.naming.NoInitialContextException: Cannot instantiate class: while try to use simple ejb through cliant application

    Hi!
    Check the following link to see if it solves your problem:
    http://support.microsoft.com/kb/952032
    Best regards
    Andreas Molin
    Andreas Molin | Site: www.guidestomicrosoft.com | Twitter: andreas_molin

Maybe you are looking for

  • Format ICML text placed in InDesign

    Is it possible to format the text of ICMLs placed in an InDesign doc? (see below)

  • Buying the right camcorder

    So...continuing a discussion I posted a couple weeks ago, I've been diligently reading and looking into buying a new camcorder.  I'm currently using a nice Sony Mini-DVD Handycam, but my problem is when I bring content into Premiere Elements I'm havi

  • Incorrect Resolution

    I've seached the internet for this problem, but impossible to search without getting something unneeded long story short, photoshop is not displaying resolution correctly i'll create a file that is 100X100 pxls and it will display at around 500X500 p

  • Maybe there a bug in JDK 1.4 ?

    Hello , I use JBuilder 7 to design my application . When using the default JDK configuration(java 1.3.1-b24) ,my application runs well , but once turned to new JDK edition (java 1.4.0_01-b03),the application can not do any action but just quit ,and a

  • 11g on SLES 10 x86_64 problem

    Hi I'm trying to install Oracle 11g Database (linux.x64_11gR1_database.zip) on SLES 10 x86_64 SP1 (2.6.16.46-0.12-smp) And I've got error while linking: Exception Name: MakefileException Exception String: Error in invoking target 'ioracle client_shar