Assertion error using weblogic.ejbc20

I'm getting the following error message generating the jar file for my BimPspsAdjApp
WL bean:
[java] weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Couldn't
find a WLBean called "BimPspAdjApp" ]
[java] at weblogic.utils.Debug.assert(Debug.java:84)
[java] at weblogic.ejb20.deployer.CompositeMBeanDescriptor.initialize60(CompositeMBeanDescriptor.java:218)
[java] at weblogic.ejb20.deployer.CompositeMBeanDescriptor.init(CompositeMBeanDescriptor.java:159)
[java] at weblogic.ejb20.deployer.CompositeMBeanDescriptor.<init>(CompositeMBeanDescriptor.java:152)
[java] at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:393)
[java] at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:126)
[java] at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:128)
[java] at weblogic.ejbc20.runBody(ejbc20.java:358)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:79)
[java] at weblogic.ejbc20.main(ejbc20.java:460)
[java] Exception in thread "main" weblogic.utils.AssertionError: ***** ASSERTION
FAILED *****[ Couldn't find a WLBean called "BimPspAdjApp" ]
[java] at weblogic.utils.Debug.assert(Debug.java:84)
[java] at weblogic.ejb20.deployer.CompositeMBeanDescriptor.initialize60(CompositeMBeanDescriptor.java:218)
[java] at weblogic.ejb20.deployer.CompositeMBeanDescriptor.init(CompositeMBeanDescriptor.java:159)
[java] at weblogic.ejb20.deployer.CompositeMBeanDescriptor.<init>(CompositeMBeanDescriptor.java:152)
[java] at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:393)
[java] at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:126)
[java] at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:128)
[java] at weblogic.ejbc20.runBody(ejbc20.java:358)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:79)
[java] at weblogic.ejbc20.main(ejbc20.java:460)
[java] Java Result: 1
My Ant command is:
<target name = "intBimPsp">
     <mkdir dir="${ejbjartmp.dir}/webserviceBim/META-INF"/>
     <mkdir dir="${ejbjartmp.dir}/webserviceBim/fastway/runtime/intBimPsp"/>
     <copy file="${descriptors.dir}/BimPspAdjApp-ejb-jar.xml" tofile="${ejbjartmp.dir}/webserviceBim/META-INF/ejb-jar.xml"/>
     <copy file="${descriptors.dir}/BimPspAdjApp-weblogic-ejb-jar.xml" tofile="${ejbjartmp.dir}/webserviceBim/META-INF/weblogic-ejb-jar.xml"/>
<copy todir="${ejbjartmp.dir}/webserviceBim/fastway/runtime/intBimPsp/">
<fileset dir="${build.dir}/fastway/runtime/intBimPsp/"/>
</copy>
     <jar jarfile="${ejbjartmp.dir}/pre_BimPspAdjApp.jar"
     basedir="${ejbjartmp.dir}/webserviceBim"/>
<java classname="weblogic.ejbc20" fork="yes" dir="${ejbjartmp.dir}">
     <arg line="$pre_BimPspAdjApp.jar $BimPspAdjApp.jar"/>
          <classpath>
               <pathelement location="/apps/bea/wlserver6.1/lib/weblogic.jar"/>
               <pathelement location="${ejbjartmp.dir}/pre_BimPspAdjApp.jar"/>
          </classpath>
     </java>
<delete dir="${ejbjartmp.dir}/webserviceBim/"/>
     <delete file="${ejbjartmp.dir}/pre_BimPspAdjApp.jar"/>
</target>
Why does this assertion error occur?
Thanks

Are you trying to run a EJB 2.0 bean using a EJB 1.1 DTD?
Gabriela Gonzalez wrote:
I'm getting the following error message generating the jar file for my BimPspsAdjApp
WL bean:
[java] weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Couldn't
find a WLBean called "BimPspAdjApp" ]
[java] at weblogic.utils.Debug.assert(Debug.java:84)
[java] at weblogic.ejb20.deployer.CompositeMBeanDescriptor.initialize60(CompositeMBeanDescriptor.java:218)
[java] at weblogic.ejb20.deployer.CompositeMBeanDescriptor.init(CompositeMBeanDescriptor.java:159)
[java] at weblogic.ejb20.deployer.CompositeMBeanDescriptor.<init>(CompositeMBeanDescriptor.java:152)
[java] at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:393)
[java] at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:126)
[java] at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:128)
[java] at weblogic.ejbc20.runBody(ejbc20.java:358)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:79)
[java] at weblogic.ejbc20.main(ejbc20.java:460)
[java] Exception in thread "main" weblogic.utils.AssertionError: ***** ASSERTION
FAILED *****[ Couldn't find a WLBean called "BimPspAdjApp" ]
[java] at weblogic.utils.Debug.assert(Debug.java:84)
[java] at weblogic.ejb20.deployer.CompositeMBeanDescriptor.initialize60(CompositeMBeanDescriptor.java:218)
[java] at weblogic.ejb20.deployer.CompositeMBeanDescriptor.init(CompositeMBeanDescriptor.java:159)
[java] at weblogic.ejb20.deployer.CompositeMBeanDescriptor.<init>(CompositeMBeanDescriptor.java:152)
[java] at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:393)
[java] at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:126)
[java] at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:128)
[java] at weblogic.ejbc20.runBody(ejbc20.java:358)
[java] at weblogic.utils.compiler.Tool.run(Tool.java:79)
[java] at weblogic.ejbc20.main(ejbc20.java:460)
[java] Java Result: 1
My Ant command is:
<target name = "intBimPsp">
<mkdir dir="${ejbjartmp.dir}/webserviceBim/META-INF"/>
<mkdir dir="${ejbjartmp.dir}/webserviceBim/fastway/runtime/intBimPsp"/>
<copy file="${descriptors.dir}/BimPspAdjApp-ejb-jar.xml" tofile="${ejbjartmp.dir}/webserviceBim/META-INF/ejb-jar.xml"/>
<copy file="${descriptors.dir}/BimPspAdjApp-weblogic-ejb-jar.xml" tofile="${ejbjartmp.dir}/webserviceBim/META-INF/weblogic-ejb-jar.xml"/>
<copy todir="${ejbjartmp.dir}/webserviceBim/fastway/runtime/intBimPsp/">
<fileset dir="${build.dir}/fastway/runtime/intBimPsp/"/>
</copy>
<jar jarfile="${ejbjartmp.dir}/pre_BimPspAdjApp.jar"
basedir="${ejbjartmp.dir}/webserviceBim"/>
<java classname="weblogic.ejbc20" fork="yes" dir="${ejbjartmp.dir}">
<arg line="$pre_BimPspAdjApp.jar $BimPspAdjApp.jar"/>
<classpath>
<pathelement location="/apps/bea/wlserver6.1/lib/weblogic.jar"/>
<pathelement location="${ejbjartmp.dir}/pre_BimPspAdjApp.jar"/>
</classpath>
</java>
<delete dir="${ejbjartmp.dir}/webserviceBim/"/>
<delete file="${ejbjartmp.dir}/pre_BimPspAdjApp.jar"/>
</target>
Why does this assertion error occur?
Thanks--
Rajesh Mirchandani
Developer Relations Engineer
BEA Support

Similar Messages

  • Help!.... XA error: using Weblogic 6.1 and Oracle 8.1.6

              Hi,
              I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSource as I wanted
              to use Container Managed Transaction through a Session Bean.
              Connection Pool Settings: -------------------------
              Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
              TXDataSource Settings : -----------------------
              Name - myXADS
              JNDIName - myXADS
              PoolName - myXAPool
              Everything works fine but once in a while I get the following exception:
              java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured
              in the transaction branch start() failed on resource 'myXAPool' Unexpected error
              during start for XAResource 'myXAPool': null
              The connection pool size is 30 and the number connections high reached was 5,
              which means there are enough connections in the pool available at all time.
              It would be really great if you can help me out.
              Thanks in Advance, Sudhir.
              

    Hi Slava,
    Sorry about that Oracle instance I am using is 8.1.7.
    For the XA Driver I am using the one that comes with Weblogic in weblogic.jar.
    And my Weblogic version 6.1 Sp3.
    Thanks,
    Sudhir.
    "Slava Imeshev" <[email protected]> wrote:
    Hi Sudhir,
    Are you using an instance of 8.1.6 or 8.1.7? In the message header you
    say
    8.1.6.
    Regards,
    Slava Imeshev
    "Sudhir Babu" <[email protected]> wrote in message
    news:[email protected]..
    Hi,
    I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSourceas
    I wanted
    to use Container Managed Transaction through a Session Bean.
    Connection Pool Settings: -------------------------
    Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb
    DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
    TXDataSource Settings : -----------------------
    Name - myXADS
    JNDIName - myXADS
    PoolName - myXAPool
    Everything works fine but once in a while I get the following exception:
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager errorhas
    occured
    in the transaction branch start() failed on resource 'myXAPool' Unexpectederror
    during start for XAResource 'myXAPool': null
    The connection pool size is 30 and the number connections high reachedwas
    5,
    which means there are enough connections in the pool available at alltime.
    It would be really great if you can help me out.
    Thanks in Advance, Sudhir.

  • XA error: using Weblogic 6.1 and Oracle 8.1.6

    Hi,
    I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSource as I wanted
    to use Container Managed Transaction through a Session Bean.
    Connection Pool Settings: -------------------------
    Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb
    DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
    TXDataSource Settings : -----------------------
    Name - myXADS
    JNDIName - myXADS
    PoolName - myXAPool
    Everything works fine but once in a while I get the following exception:
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured
    in the transaction branch start() failed on resource 'myXAPool' Unexpected error
    during start for XAResource 'myXAPool': null
    The connection pool size is 30 and the number connections high reached was 5,
    which means there are enough connections in the pool available at all time.
    It would be really great if you can help me out.
    Thanks in Advance, Sudhir.

    Hi Slava,
    Sorry about that Oracle instance I am using is 8.1.7.
    For the XA Driver I am using the one that comes with Weblogic in weblogic.jar.
    And my Weblogic version 6.1 Sp3.
    Thanks,
    Sudhir.
    "Slava Imeshev" <[email protected]> wrote:
    Hi Sudhir,
    Are you using an instance of 8.1.6 or 8.1.7? In the message header you
    say
    8.1.6.
    Regards,
    Slava Imeshev
    "Sudhir Babu" <[email protected]> wrote in message
    news:[email protected]..
    Hi,
    I am using Weblogic 6.1 with Oracle 8.1.7. I configured a TXDataSourceas
    I wanted
    to use Container Managed Transaction through a Session Bean.
    Connection Pool Settings: -------------------------
    Name - myXAPool URL - jdbc:oracle:thin:@myServer:1521:myDb
    DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
    TXDataSource Settings : -----------------------
    Name - myXADS
    JNDIName - myXADS
    PoolName - myXAPool
    Everything works fine but once in a while I get the following exception:
    java.sql.SQLException: XA error: XAER_RMERR : A resource manager errorhas
    occured
    in the transaction branch start() failed on resource 'myXAPool' Unexpectederror
    during start for XAResource 'myXAPool': null
    The connection pool size is 30 and the number connections high reachedwas
    5,
    which means there are enough connections in the pool available at alltime.
    It would be really great if you can help me out.
    Thanks in Advance, Sudhir.

  • Receiving ERRORS using WEBLOGIC.DEPLOY

    Hi everybody,
    I am getting strange errors when using the weblogic.deploy command-line
    function. I am using WL6.0 on W2000.
    Deploy/Update
    command: java weblogic.deploy -port 7001 -host localhost update
    beapasword MyWebApplication stage\MyWebApplication.war
    error: java.lang.NullPointerException
    at
    weblogic.deploy.deployApplication(deploy.java:383)
    at weblogic.deploy.deploy(deploy.java:340)
    at weblogic.deploy.runBody(deploy.java:219)
    at weblogic.utils.compiler.Tool.run(Tool.java:81)
    at weblogic.deploy.main(deploy.java:954)
    Undeploy
    Command: java weblogic.deploy -port 7001 -host localhost undeploy
    beapasword MyWebApplication
    error: giving up after two minutes
    And it looks that just a Update doens't work. I have to undeploy first and
    the do a update to see the changes I've made in my file.
    Any suggestions....
    M-

    Hi.
    WLS version and service pack level? Please post the entire weblogic.deploy command along
    with the exception that follows.
    Thanks,
    Michael
    Harjeet Singh wrote:
    I try to use weblogic.deploy to deploy my EAR file on weblogic server called localhost
    on 7001. When I try to run it gives me following error:
    [java] JNDI naming exception: Naming exception trying to connect to: t3://localhost:7001
    as: system: password
    system password is correct. I have tried http://localhost:7001 to but doesen't seem
    to work.
    Any ideas.
    HS--
    Michael Young
    Developer Relations Engineer
    BEA Support

  • Error Using weblogic.jspc --- java.lang.ExceptionInInitializerError

    Hi,
              I am trying to use the weblogic.jspc compiler to pre-compile my jsp
              files so that I can verify that they compile w/o having to visit the
              page. I am using Weblogic 4.5.1. I am encountering the following
              error:
              java.lang.ExceptionInInitializerError
              at java.lang.Throwable.<init>(Compiled Code)
              at java.lang.Error.<init>(Compiled Code)
              at java.lang.LinkageError.<init>(Compiled Code)
              at java.lang.ExceptionInInitializerError.<init>(Compiled Code)
              at java.beans.Beans.instantiate(Compiled Code)
              at weblogic.servlet.jsp.JspLexer.processBeanTag(Compiled Code)
              at weblogic.servlet.jsp.JspLexer.mXML_OPEN_USEBEAN(Compiled Code)
              at weblogic.servlet.jsp.JspLexer.mXML_THING(Compiled Code)
              at weblogic.servlet.jsp.JspLexer.mTOKEN(Compiled Code)
              at weblogic.servlet.jsp.JspLexer.nextToken(Compiled Code)
              at weblogic.servlet.jsp.JspLexer.parse(Compiled Code)
              at weblogic.servlet.jsp.JspParser.doit(Compiled Code)
              at weblogic.servlet.jsp.JspParser.parse(Compiled Code)
              at weblogic.servlet.jhtmlc.Jhtml2Java$Output.setSourceFile(Compiled
              Code)
              at weblogic.servlet.jhtmlc.Jhtml2Java.outputs(Compiled Code)
              at weblogic.utils.compiler.CodeGenerator.generate(Compiled Code)
              at weblogic.jhtmlc.runBody(Compiled Code)
              at weblogic.jspc.runBody(Compiled Code)
              at weblogic.utils.compiler.Tool.run(Compiled Code)
              at weblogic.jspc.main(Compiled Code)
              Have any of you seen this? Can you tell me what I am doing wrong
              (Classpath, etc.)?
              Any and all help would be greatly appreciated.
              The command line I am using is:
              java -verbose -classpath
              $CLASSPATH:/apps/weblogic/license:/apps/weblogic/classes:/apps/weblogic/lib/weblogicaux.jar
              weblogic.jspc -d $HOME/weblogic/myserver/classfiles/examples
              100-Welcome.jsp
              Regards,
              Richard
              

    Fixed with a patch CR0737797 and CR062538 for the 6.1 sp3 source line
              Prasanna Yalam

  • Errors using weblogic sql driver: "No JDBC connection can be made because the transaction state is marked rollback"

    One of our customers starts to encounter this error message recently.
    We checked our log files. It seems that the error happens when
    to obtain a jdbc connection. Have anyone seen similar problems
    and knows how to fix it? thanks in advance.
    We are using weblogic server 6.1sp2, and weblogic sql type 4 driver.
    The functions that invoke the jdbc calls are stateless session bean
    methods with their transaction attributes marked as Required.
    There is no nested calls of these methods.
    A partial stack trace we obtained is as following:
    java.sql.SQLException: No JDBC connection can be made
    because the transaction state is
    Marked Rollback
         at weblogic.jdbc.jts.Connection.getOrCreateConnection(Connection.java:586)
         at weblogic.jdbc.jts.Connection.prepareStatement(Connection.java:115)
         at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
         at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:76)
    lixin

    Joseph Weinstein <[email protected]> wrote:
    >
    >
    YuanHui Liu wrote:
    Joe,
    We got the exact same error message. The error came after we got theJDBC connection,
    and trying to create statement off it.
    It occurs intermitently when we are running another standalone JAVAapp to do
    some end of day work, which results in the DB Server being very busy(90+%CPU
    usage) for about 5 minutes. We see a surge of requests to the WLSJDBC Connection
    pool. This would sometimes result in all our subsequent DB requeststo fail and
    lead to a crash.
    We are using WLS6.0SP1. I do not think there's a 30 seconds wait leadingto a
    connection timeout that caused this(rather it is the end effect).
    Can you give us a more detailed explanation? Is there a miscommunicationbetween
    our DB(Sybase12) and WLS?Hi. It looks to you like it's after you get the connection, but really
    it's when the server is
    gettng the pool connection. For performance/synchronization reasons we
    do a clever
    delay: When your code asks for a pool connection we quickly give you
    the pool wrapper,
    but we delay actually reserving the real underlying DBMS connection until
    your first
    real need for a connection, at your first JDBC call, such as createStatement()
    etc.
    It is while waiting for a pool connection long enough for the transaction
    coordinator
    to have timed you out before you ever get a chance. It's nothing to do
    with the
    DBMS or even JDBC, I believe. I think the weblogic server either has
    too few execute-threads
    and/or too few CPU cycles to do the work load.
    Okay, so there's a lazy initialization of the connection.
    From reading our log I believe our failur is immediate rather
    than waiting for 30+ seconds(the default setting) from the DB,
    the timeout occurred later as a result. At the time either because the DB Server
    is very busy.
    Since we are running WLS6.0 we have only one connection pool,
    we have defined a max of 150 threads in the pool. While this
    is happening the DB Server is being pinned by an overnight job,
    but the WLS Server is not busy at all. The DB and WLS resides
    on different physical boxes.
    We also have a thread dump from the WLS console when we rebooted the server, it
    showed that we are hanging on to the thread & jdbc
    connections after these exceptions has occurred instead of releasing them, note
    "16083"(~4.5 hours) seconds has passed:
    142 116222 Retry rollback request for tx: 'transaction=(IdHash=2963855,Name =
    [EJB UserManagerBeanImpl.signalICUserServletHeartBeat()],Xid=30643:8f3838f3709bf53d,Status=Rolling
    Back. [Reason = Unknown],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since
    begin=16083,seconds left=10,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=server),SCInfo[server]=(state=active),properties=({weblogic.jdbc=t3://159.55.158.25:8005,
    weblogic.transaction.name=[EJB UserManagerBeanImpl.signalICUserServletHeartBeat()]}))'
    Scheduled Trigger
    So I would argue this problem actually chewed up resources on the WLS server.
    -Yuanhui Liu
    >>
    >>
    Thanks.
    -YuanHui Liu
    Joseph Weinstein <[email protected]> wrote:
    lixin wrote:
    One of our customers starts to encounter this error message recently.
    We checked our log files. It seems that the error happens when
    to obtain a jdbc connection. Have anyone seen similar problems
    and knows how to fix it? thanks in advance.
    We are using weblogic server 6.1sp2, and weblogic sql type 4 driver.
    The functions that invoke the jdbc calls are stateless session bean
    methods with their transaction attributes marked as Required.
    There is no nested calls of these methods.
    A partial stack trace we obtained is as following:
    java.sql.SQLException: No JDBC connection can be made
    because the transaction state is
    Marked Rollback
    at weblogic.jdbc.jts.Connection.getOrCreateConnection(Connection.java:586)Hi. This sounds like a JVM thread starvation issue, and/or a server
    load
    issue. What is
    happening is that the transaction is started, and times out beforethe
    SSB even gets to
    the first JDBC work. I would first verify that the customer is using
    the very latest JVM
    available for the machine.
    Joe Weinstein
    at weblogic.jdbc.jts.Connection.prepareStatement(Connection.java:115)
    at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
    at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:76)
    lixin

  • Error using weblogic.deploy tool, while deploying a war

              Hi all, I'm trying to deploy a war with the follw command:
              java weblogic.deploy -host localhost -port 7001 -component NewScreenWar:BEAserver
              deploy beasystem NewScreenWar d:\newsscreen\weblogic\NewScreenWar.war
              It gives me following error:
              weblogic.j2ee.DeploymentException: Application NewScreenWar does not contain com
              ponent NewScreenWar at weblogic.deploy.deploy(deploy.java:668) at weblogic.deploy.runBody(deploy.java:358)
              at weblogic.utils.compiler.Tool.run(Tool.java:79) at weblogic.deploy.main(deploy.java:1601)
              Application NewScreenWar does not contain component NewScreenWar
              how do I resolve this...??
              thanx --anjaly
              

    Hi,
    For a tutorial with source on how to create and deploy a simple quickstart JEE5 JPA enterprise 3-tier application on your Oracle WebLogic 10.3 server - see the following example that uses the EclipseLink JPA provider. You should be able to transition all of your mapping information (the @ManyToOne and table/column overrides and named queries for example) using either JPA via entity annotations or native extensions if you do not want to implement EJB3.
    see...
    http://wiki.eclipse.org/EclipseLink/Examples/JPA/WebLogic_Web_Tutorial
    We also have a similar version for Tomcat 6 except the JPA entity beans run outside a container-managed JTA transaction on the web container - for reference.
    http://wiki.eclipse.org/EclipseLink/Examples/JPA/Tomcat_Web_Tutorial
    thank you
    /michael
    www.eclipselink.org

  • Hyperion Workspace error , using weblogic as application server.

    HI Experts !
    I have Hyperion 9.3.0 environment and
    I m using web logic 8.1 and facing problem in starting workspace .
    configuration with weblogic is successful but still error while open workspace :
    Error 404--Not Found
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.5 404 Not Found
    The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
    If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
    Please help me..
    Thank you

    Hello,
    Were you able to find any solutions to this problem. We are experiencing the same issue now.
    Thanks
    Srikanth

  • Annoying Assertion errors using the DB2 Driver "com.inet.drda.DRDADriver"

    I am using the "com.inet.drda.DRDADriver" DB2 Driver.
    My query works fine and returns everything ok but I get these annoying Assertion failed errors on the console.
    Any Ideas how to stop these?
    I do not have assert enabled on JBuilder.
    Thanks ... J
    Assertion v1 == 0 failed: s.v1@ca=75
    Assertion v1 == 0 failed: s.v1@fb=250
    Assertion v1 == 0 failed: s.v1@128=75
    and so on

    Prior to using the JDBC:DB2 driver I was using the JDBC:ODBC driver and there were no such errors. So the errors are related to using the db2 driver.
    All that has changed is the lines you see commented out replaced by the new driver class.
    Nothing has changed in my Database interface layer.
        //Set up DB url using a JDBC:DB2 driver and get a connection
        String url = "jdbc:inetdb2:" + host + ":" + port + "?database="+tableOwner;
        String driverClass = "com.inet.drda.DRDADriver";
        //Set up DB url using a JDBC:ODBC driver and get a connection
        //String url = "jdbc:ODBC:"+tableOwner;
        //String driverClass = "sun.jdbc.odbc.JdbcOdbc";
    Connection connection = Tools.setUpConnectionToDB(driverClass, url,username,password);
    List appletsFound = Tools.processStatement(Query, connection);I did have Asserts enabled before this but they are not enabled now because I disabled it after I was happy all my JUnit tests were passing.

  • Serialization error using WebLogic generated stubs.

    I have written a web service using WL Workshop, and it works fine
    in the browser based test environment. When I use the client stubsgenerated by
    WL, I get a serialization error:
    java.rmi.RemoteException: web service invoke failed; nested exception is:
         javax.xml.soap.SOAPException: failed to deserialize xml:weblogic.xml.schema.binding.DeserializationException:
    did not find needed xsi:type attribute on element <anyType>
         at weblogic.jws.proxies.DataFeedSoap_Stub.getSched(DataFeedSoap_Stub.java:36)
         at weblogic.jws.proxies.DataFeedSoap_Stub.getSched(DataFeedSoap_Stub.java:58)
         at datafeed.Client.main(Client.java:19)
    Caused by: javax.xml.soap.SOAPException: failed to deserialize xml:weblogic.xml.schema.binding.DeserializationException:
    did not find needed xsi:type attribute on element <anyType>
         at weblogic.webservice.core.DefaultPart.toJava(DefaultPart.java:296)
         at weblogic.webservice.core.DefaultMessage.toJava(DefaultMessage.java:359)
         at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:465)
         at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:359)
         at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:205)
         at weblogic.jws.proxies.DataFeedSoap_Stub.getSched(DataFeedSoap_Stub.java:33)
         ... 2 more
    Caused by: weblogic.xml.schema.binding.DeserializationException: did not find
    needed xsi:type attribute on element <anyType>
         at weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec.extractType(XSDAnyCodec.java:108)
         at weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec.deserialize(XSDAnyCodec.java:83)
         at weblogic.xml.schema.binding.SequenceCodecBase.deserialize(SequenceCodecBase.java:118)
         at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:310)
         at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:286)
         at weblogic.xml.schema.binding.BeanCodecBase.processElement(BeanCodecBase.java:140)
         at weblogic.xml.schema.binding.BeanCodecBase.processElements(BeanCodecBase.java:125)
         at weblogic.xml.schema.binding.BeanCodecBase.deserialize(BeanCodecBase.java:96)
         at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:310)
         at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:286)
         at weblogic.xml.schema.binding.BeanCodecBase.processElement(BeanCodecBase.java:140)
         at weblogic.xml.schema.binding.BeanCodecBase.processElements(BeanCodecBase.java:125)
         at weblogic.xml.schema.binding.BeanCodecBase.deserialize(BeanCodecBase.java:96)
         at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:310)
         at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:266)
         at weblogic.webservice.core.DefaultPart.toJava(DefaultPart.java:290)
         ... 7 more

    Indeed there is a difference in how WLS and Workshop handle
    xsd:anyType. Our plan at this point is to fix this to return
    javax.xml.soap.SOAPElement when we do not find the xsi:type attribute
    -- probably in the next service pack release. We have entered a
    change request CR082976 that you can reference with support if you
    need a more urgent resolution.
    --Scott
    In article <[email protected]>,
    Neil Hornbeck <[email protected]> wrote:
    >
    I have written a web service using WL Workshop, and it works fine in
    the browser based test environment. When I use the client
    stubsgenerated by WL, I get a serialization error:
    java.rmi.RemoteException: web service invoke failed; nested exception is:
         javax.xml.soap.SOAPException: failed to deserialize xml:weblogic.xml.schema.binding.DeserializationException:
    did not find needed xsi:type attribute on element <anyType>
         at weblogic.jws.proxies.DataFeedSoap_Stub.getSched(DataFeedSoap_Stub.java:36)
         at weblogic.jws.proxies.DataFeedSoap_Stub.getSched(DataFeedSoap_Stub.java:58)
         at datafeed.Client.main(Client.java:19)
    Caused by: javax.xml.soap.SOAPException: failed to deserialize xml:weblogic.xml.schema.binding.DeserializationException:
    did not find needed xsi:type attribute on element <anyType>
         at weblogic.webservice.core.DefaultPart.toJava(DefaultPart.java:296)
         at weblogic.webservice.core.DefaultMessage.toJava(DefaultMessage.java:359)
         at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:465)
         at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:359)
         at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:205)
         at weblogic.jws.proxies.DataFeedSoap_Stub.getSched(DataFeedSoap_Stub.java:33)
         ... 2 more
    Caused by: weblogic.xml.schema.binding.DeserializationException: did not find
    needed xsi:type attribute on element <anyType>
         at weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec.extractType(XSDAnyCodec.java:108)
         at weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec.deserialize(XSDAnyCodec.java:83)
         at weblogic.xml.schema.binding.SequenceCodecBase.deserialize(SequenceCodecBase.java:118)
         at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:310)
         at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:286)
         at weblogic.xml.schema.binding.BeanCodecBase.processElement(BeanCodecBase.java:140)
         at weblogic.xml.schema.binding.BeanCodecBase.processElements(BeanCodecBase.java:125)
         at weblogic.xml.schema.binding.BeanCodecBase.deserialize(BeanCodecBase.java:96)
         at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:310)
         at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:286)
         at weblogic.xml.schema.binding.BeanCodecBase.processElement(BeanCodecBase.java:140)
         at weblogic.xml.schema.binding.BeanCodecBase.processElements(BeanCodecBase.java:125)
         at weblogic.xml.schema.binding.BeanCodecBase.deserialize(BeanCodecBase.java:96)
         at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:310)
         at weblogic.xml.schema.binding.RuntimeUtils.invoke_deserializer(RuntimeUtils.java:266)
         at weblogic.webservice.core.DefaultPart.toJava(DefaultPart.java:290)
         ... 7 more

  • Assertion error using USB midi.

    Hello,
    I am trying the real time java for midi/sound. I am getting the following when I try to open my usb midi keyboard.
    java: ../../../src/rawmidi/rawmidi.c:264: snd_rawmidi_open_conf: Assertion `err >= 0' failed.
    Aborted (core dumped)
    Setup is linux ubuntu 7.10 with the rt kernel
    java version "1.5.0_13"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13_JavaRTS-2.1_EA-nb021_RTSJ-1.0.2)
    Java Real-Time System HotSpot(TM) Client VM (build 1.5.0_13, mixed mode)
    Kernel 2.6.22-14-rt #1 SMP PREEMPT RT Tue Feb 12 03:54:33 UTC 2008 x86_64 GNU/Linux
    Is this a bug ?
    cheers Paul.

    Hi David,
    Thanks for your reply,
    rawmidi.c is part of the alsa-lib .
    I am using the latest alsa-lib-1.0.16 and alsa-driver-1.0.16
    http://alsa.cvs.sourceforge.net/alsa/alsa-lib/src/rawmidi/rawmidi.c?view=markup
    putting strace before the java command gives some more info.
    [snip lots of stuff]
    java: ../../../src/rawmidi/rawmidi.c:264: snd_rawmidi_open_conf: Assertion `err >= 0' failed.
    ) = ? ERESTART_RESTARTBLOCK (To be restarted)
    +++ killed by SIGABRT (core dumped) +++
    It happens when you try to open the midi input device.
    The code works fine with a plain 64bit VM.
    java -version
    java version "1.6.0_03"
    Java(TM) SE Runtime Environment (build 1.6.0_03-b05)
    Java HotSpot(TM) 64-Bit Server VM (build 1.6.0_03-b05, mixed mode)
    The java realtime works great for low latency audio (compared to plain java) it would be great to get my keyboard working!
    cheers Paul.

  • Problem using weblogic.jspc with wls6.1

              I've got this error using weblogic.jspc on jsp that works fine with the compiler
              of 5.1, is this a bug?
              java.lang.NullPointerException
              at weblogic.management.Admin.getServer(Admin.java:1252)
              at weblogic.servlet.internal.dd.ServletEntityResolver.initServerMBean(ServletEntityResolver.java:69)
              at weblogic.servlet.internal.dd.ServletEntityResolver.resolveEntity(ServletEntityResolver.java:94)
              at weblogic.apache.xerces.readers.DefaultEntityHandler.startReadingFromExternalEntity(DefaultEntityHandler.java:749)
              at weblogic.apache.xerces.readers.DefaultEntityHandler.startReadingFromExternalSubset(DefaultEntityHandler.java:566)
              at weblogic.apache.xerces.framework.XMLDTDScanner.scanDoctypeDecl(XMLDTDScanner.java:1139)
              at weblogic.apache.xerces.framework.XMLDocumentScanner.scanDoctypeDecl(XMLDocumentScanner.java:2215)
              at weblogic.apache.xerces.framework.XMLDocumentScanner.access$0(Compiled
              Code)
              at weblogic.apache.xerces.framework.XMLDocumentScanner$PrologDispatcher.dispatch(Compiled
              Code)
              at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(Compiled
              Code)
              at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:967)
              at weblogic.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:175)
              at weblogic.servlet.internal.dd.DescriptorLoader.parse(DescriptorLoader.java:311)
              at weblogic.servlet.internal.dd.DescriptorLoader.initializeWebXml(DescriptorLoader.java:327)
              at weblogic.servlet.internal.dd.DescriptorLoader.initialize(DescriptorLoader.java:242)
              at weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader.java:176)
              at weblogic.servlet.internal.dd.DescriptorLoader.loadDescriptor(DescriptorLoader.java:396)
              at weblogic.jspc.runBodyInternal(Compiled Code)
              at weblogic.jspc.runBody(jspc.java:169)
              at weblogic.utils.compiler.Tool.run(Tool.java:79)
              at weblogic.jspc.main(Compiled Code)
              --------------- nested within: ------------------
              weblogic.utils.AssertionError: ***** ASSERTION FAILED ***** - with nested exception:
              [java.lang.NullPointerException]
              at java.lang.Throwable.fillInStackTrace(Native Method)
              at java.lang.Throwable.fillInStackTrace(Compiled Code)
              at java.lang.Throwable.<init>(Compiled Code)
              at java.lang.Error.<init>(Error.java:50)
              at weblogic.utils.NestedError.<init>(NestedError.java:24)
              

    Please post your full description. I can't see what you're replying to (must
              be too old).
              Alex
              "Gregory Chazalon" <[email protected]> wrote in message
              news:3c7383a8$[email protected]..
              > I've got te same problem (NullPointerException at the same line code in
              the same class). The most disturbing is that the weblogic.jspc works fine
              with wl6.1 SP2 but fails with wl6.1 SP1.
              >
              > Do you have a solution ? Can I download a CRXXXX.jar that fixes it ?
              >
              > I will appreciate any help.
              >
              

  • Assertion Error: Cannot Load Dyamically Generated Stub

    Hi Everyone,
    I am getting an Assertion Error in Weblogic 9.2, the root cause being a ClassNotFoundException for a dynamically-generated WL Stub for an Oracle JDBC wrapper. The partial stacktrace is as follows:
    ASSERTION FAILED *****[Could not find dynamically generated class: 'weblogic.jdbc.rmi.internal.ResultSetImpl_weblogic_jdbc_wrapper_ResultSet_oracle_jdbc_driver_OracleResultSetImpl_920_WLStub']
    Caused by: java.lang.ClassNotFoundException: weblogic.jdbc.rmi.internal.ResultSetImpl_weblogic_jdbc_wrapper_ResultSet_oracle_jdbc_driver_OracleResultSetImpl_920_WLStub
    So...not sure if the RMI stub is never generated because/or there is something dorked up in my classpath re: Oracle. Any insight would be awesome
    Thanks!
    --John                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

    Hi yoster,
    I have the same problem, but I couldn't solve the problem by removing a war file like you did.
    It's nearly the same stacktrace:
    ASSERTION FAILED *****[ Could not find dynamically generated class: 'weblogic.jdbc.rmi.internal.StatementImpl_weblogic_jdbc_wrapper_Statement_oracle_jdbc_driver_T4CStatement_921_WLStub' ].
    java.lang.ClassNotFoundException: weblogic.jdbc.rmi.internal.StatementImpl_weblogic_jdbc_wrapper_Statement_oracle_jdbc_driver_T4CStatement_921_WLStub
    My database is also oracle.
    Do you have other ideas that could sold this ?
    I hope you do, because I'm stuck ... don't know where to look anymore :(
    Toni

  • Troubles using EJBDeployment tool : perpetual assertion errors.

    I'm trying to deploy an EJB using the Weblogic 510 EJBDeployment tool.
    I've got a Remote interface, an EJB class and a home interface in a
    directory called
    d:\EJBDemos.
    The classes are not in packages.
    When I try to create the jar file, no matter where I try to create it, I get
    an assertion error on the console which says something along the lines of:
    File root of D:/EJBDemos is not a prefix for file
    d:/EJBDemos/RoleEJB.class ]
    (in this particular example, I was trying to create a d:\test.jar )
    and then throws a whole bunch of swing exceptions.
    I have also tried this on another Entity bean, and exactly the same thing
    happened.
    I got it to create the jar file the very first time I attempted it, but the
    classes were wrong, so I tried to create a new one and have had this problem
    every time. Any ideas?

    I'm trying to deploy an EJB using the Weblogic 510 EJBDeployment tool.
    I've got a Remote interface, an EJB class and a home interface in a
    directory called
    d:\EJBDemos.
    The classes are not in packages.
    When I try to create the jar file, no matter where I try to create it, I get
    an assertion error on the console which says something along the lines of:
    File root of D:/EJBDemos is not a prefix for file
    d:/EJBDemos/RoleEJB.class ]
    (in this particular example, I was trying to create a d:\test.jar )
    and then throws a whole bunch of swing exceptions.
    I have also tried this on another Entity bean, and exactly the same thing
    happened.
    I got it to create the jar file the very first time I attempted it, but the
    classes were wrong, so I tried to create a new one and have had this problem
    every time. Any ideas?

  • Error in using the JMS Adater using weblogic queue

    I am using weblogic queue in jms adapter to queue the data. i configured the server.xml
         <shared-library name="oracle.weblogic" version="10.1.3">
              <code-source path="D:\product\10.1.3.1\OracleAS_5\jdk\lib\weblogic.jar"/>
         </shared-library>
    I got the following error. Any Suggestions?
    file:/D:/product/10.1.3.1/OracleAS_5/bpel/domains/default/tmp/.bpel_OSM_OrderRequest_2.0_c68a29fd8af11327e1a8892e8de5a6bb.tmp/Sample.wsdl [ Produce_Message_ptt::Produce_Message(orderRequestMessage) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: Could not instantiate InteractionSpec oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec due to:
         Missing class: oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec
         Dependent class: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /D:/product/10.1.3.1/OracleAS_5/bpel/lib/orabpel.jar
         Configuration: <code-source> in /D:/product/10.1.3.1/OracleAS_5/j2ee/oc4j_soa/config/server.xml
    This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.; nested exception is:
         oracle.classloader.util.AnnotatedClassNotFoundException:
         Missing class: oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec
         Dependent class: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /D:/product/10.1.3.1/OracleAS_5/bpel/lib/orabpel.jar
         Configuration: <code-source> in /D:/product/10.1.3.1/OracleAS_5/j2ee/oc4j_soa/config/server.xml
    This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.; nested exception is:
         org.collaxa.thirdparty.apache.wsif.WSIFException: Could not instantiate InteractionSpec oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec due to:
         Missing class: oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec
         Dependent class: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /D:/product/10.1.3.1/OracleAS_5/bpel/lib/orabpel.jar
         Configuration: <code-source> in /D:/product/10.1.3.1/OracleAS_5/j2ee/oc4j_soa/config/server.xml
    This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.; nested exception is:
         oracle.classloader.util.AnnotatedClassNotFoundException:
         Missing class: oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec
         Dependent class: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /D:/product/10.1.3.1/OracleAS_5/bpel/lib/orabpel.jar
         Configuration: <code-source> in /D:/product/10.1.3.1/OracleAS_5/j2ee/oc4j_soa/config/server.xml
    This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.
    </summary>
    </part>
    -<part name="detail">
    <detail>
    org.collaxa.thirdparty.apache.wsif.WSIFException: Could not instantiate InteractionSpec oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec due to:
         Missing class: oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec
         Dependent class: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /D:/product/10.1.3.1/OracleAS_5/bpel/lib/orabpel.jar
         Configuration: <code-source> in /D:/product/10.1.3.1/OracleAS_5/j2ee/oc4j_soa/config/server.xml
    This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.; nested exception is:
         oracle.classloader.util.AnnotatedClassNotFoundException:
         Missing class: oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec
         Dependent class: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /D:/product/10.1.3.1/OracleAS_5/bpel/lib/orabpel.jar
         Configuration: <code-source> in /D:/product/10.1.3.1/OracleAS_5/j2ee/oc4j_soa/config/server.xml
    This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.

    I am able to fix this error by copying "JmsAdapter.jar" to "applib" directory of oc4j_soa.
    I was getting a new error.
    +"Missing class: oracle.tip.adapter.api.TranslationAware+
    +     Dependent class: oracle.tip.adapter.jms.JmsInteractionSpec+
    +     Loader: global.libraries:1.0+
    +     Code-Source: /D:/SOA1013/j2ee/oc4j_soa/applib/JmsAdapter.jar+
    +     Configuration: <code-source> in /D:/SOA1013/j2ee/oc4j_soa/config/server.xml+
    +The missing class is available from the following locations:+
    +     1. Code-Source: /D:/SOA1013/bpel/lib/orabpel.jar (from <code-source> in /D:/SOA1013/j2ee/oc4j_soa/config/server.xml)+
    +     This code-source is available in loader oracle.bpel.common:10.1.3."+
    But managed it to fix it by copying "orabpel.jar" to "applib" directory.
    We need to restart OC4J once we copy the JAR files.
    regards,
    S.Vasanth Kumar.

Maybe you are looking for

  • Please help--I can't take it.

    I apologize for bringing this up again. Many of you gave me very sound advice when I asked about this before. But now, I have additional information (and experience) that is helpful yet confusing. I also apologize for the long post. Should any of you

  • How to create a node in the transaction?

    Hi ! In R/3 , How can i create  a node  underwhich I want to assign my generic datasource? I went to RSA5, there create node is hidden under hierarchy menu item. Waiting for your reply. Regards Durai

  • URxvt and the mouse wheel

    Hi all! I would like to know if it's possible to scroll down in man or less with the mouse will using URxvt. Thank you.

  • 20" G4 dim display

    I have read as much as I can on here but need more info. I have an iMac USB2.0 w/20" that is very dimly lit. When I first got it it was not lit at all. I have tried 2 different inverters thinking maybe the first one was bad. The one that came in it w

  • Which is better for spareparts for a T410: broken T400 or broken T410i ?

    I tried immersing myself in the datasheets for the FRUs for both T410i and T400, to see which of the two has more common or interchangeable spareparts with my T410. I have the opportunity to buy a broken T400 or a broken T410i for spareparts, but am