JBuilder 3.1 Deployment/JDBC Exception - Exhausted Resultset

I just installed JBuilder 3.1 with Oracle 8i (8.1.6) on NT workstation w/SP5 and am receiving error "java.sql.SQLException: Exhausted Resultset" upon choosing deploy for sample "Auctions" application profile. I have an idea this has to do with the number of rows returned by SQL statement associated with ResultSet rset declaration in method getvalue but don't know for sure. What's happening here?
Thanks in advance for any assistance...
Java/JBuilder neophyte

As far as i know u can encounter an exhausted resultset exception if the JDBC version is prior 2.0 and that , the same resultset is tried to iterate more than once...... coz this was what i have experienced...

Similar Messages

  • [oracle 10g on SDK 1.6SE] Err Msg: Exhausted Resultset

    I am having problem obtaining proper Resultset from a excuteQuery() method.
    i can successfully create a JDBC connection to local oracle database (on my computer) and excute a query on a table named "emp" which contains two records; however when i print out my Resultset using getInt(String coloumName), compiler error says "Exhausted Resultset".
    my source code:
    import java.sql.*;
    import oracle.jdbc.pool.OracleDataSource;
    class GetEmpDetails
    public static void main(String args[])
    try
    // instantiate and initialize OracleDataSource
    OracleDataSource ods = new OracleDataSource();
    ods.setURL("jdbc:oracle:thin:usr/secret@Laptop:1521:oracle"); Connection x = ods.getConnection();
    Statement stmt = x.createStatement();
    ResultSet rset = stmt.executeQuery("select empno, ename, job from emp");
    rset.next();
    System.out.println("My ID is "+ rset.getInt("empno") );
    // System.out.println("My ID is" + rset.getInt(1); returns "invalid coloum index" error
    catch (SQLException e)
    System.err.println ("error message: " + e.getMessage() );
    e.printStackTrace();
    Runtime.getRuntime().exit(1);
    i am able to query my emp table under SQLPlus with the following output:
    EMPNO ENAME JOB
    1 Tim Student
    2 Tom Student
    JAVA compiler compiles upto excuteQuery("select ...") statement and at that point returns an empty Resultset objet (i think)
    i copied this code from an example giving in a programming book using oracle 10g on JDK1.5SE.
    can anyone make some suggestion about how to fix this error?
    ting

    Okay a few points here to clear some things up and move you forward.
    1) What you are getting are not compilation errors. They are runtime errors. You made this mistake at least twice (once in your original post and once in your follow up) and it's worth clarifying because runtime errors and compile time errors are not the same thing. And that's worth knowing if for no other reason then in future if you ask for help with "compilation" errors that are actually runtime errors you may well find that you confuse the heck out of people and can't be helped.
    2) What the good doctor was pointing out is that you should not be throwing away the value of rs.next no matter if you feel the table should have records or not. Your code should look like this
    if(rs.next()){
      // do something
    }else{
      // do something else
    }Because that will handle either way and your program won't come to a screeching halt because you tried to read a value that doesn't exist in the ResultSet.
    So no matter how you get this resolved your code should still end up looking like the above (or similar). At any rate make use of the boolean returned from the next method.
    3) On to your actual problem. Well first you need to cross off any silly mistakes that do happen from time to time. Like are you sure you are talking to the "right" database. Again this may seem silly but it does happen.
    If that checks out then almost certainly yes this is some sort of Oracle permissions related issue. This seems to happen with Oracle more than other databases, I suspect because Oracle more than others associates table statistics with user permissions, but this could be totally unwarranted and simply based on my experience here which is many people having similar types of problems. The best way to resolve this is to make sure that you are logging in with the same credentials as you use in SQLPlus.
    If all else fails talk to your DBA. This is an Oracle related issue of some sort but it's very difficult to diagnose specifically over the internet.

  • Com.sap.db.jdbc.exceptions.JDBCDriverException:user is forced to change password

    Hi all
    I am trying to connect hana using jdbc code
    here is my code
              Class.forName("com.sap.db.jdbc.Driver");
                String url = "jdbc:sap://host:30015/?";
                String user = "Mujadid";
                String password = "Cloud123";
                System.out.println("try to connect to HANA !");
                Connection cn = java.sql.DriverManager.getConnection(url, user, password);
                System.out.println("Connection to HANA successful!");
                ResultSet rs = cn.createStatement().executeQuery("select * from _SYS_STATISTICS.STATISTICS_ALERTS");
                rs.next();
                System.out.println(rs.getString(1));
    I am facing following exception
    com.sap.db.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: [414]: user is forced to change password: alter password required for user MUJADID
      at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:345)
    Any suggestion?

    Hi Mathan!
    now above error is esolved
    But i m facing following error when i try to read connections table from live2 schema
    com.sap.db.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: [259] (at 20): invalid table name:  Could not find table/view CONNECTIONS in schema LIVE2
    and this table exist in LIVE2 schema
    Any suggestion?

  • Deploy JDBC driver for SQL server 2005 on PI 7.1

    How to deploy JDBC driver for SQL server 2005 on PI 7.1
    We are in SAP NetWeaver 7.1 Oracle 10G
    Third party system is  SQL server 2005
    There are different JDBC versions are available to download for SQL server 2005.
    I am not sure about the applicable version for the PI 7.1 SP level. Again JMS Adapter needs to be deploy along with this.
    Please help

    Hi,
    Hope this How to Guide help you.
    How To Install and Configure External Drivers for the JDBC & JMS Adapters from
    www.sdn.sap.com/irj/sdn/howtoguides
    Regards,
    Karthick.
    Edited by: Karthick Srinivasan on Apr 13, 2009 4:07 PM

  • Deploying JDBC driver for SQL Server 2005 on PI 7.1

    How to Deploy JDBC driver for SQL Server 2005 on PI 7.1 on Windows 2003 server
    We are in NW PI 7.1 and third party db is sql server 05.
    Found How-to Guide SAP NetWeaver u201804 but unable to find for NW PI 7.1
    Can any one help me on this? (looking for guide step by step procedure)
    Regards
    Mahesh

    Hi,
    Check these:
    Re: Installing JDBC Drivers for PI 7.1
    how to deploy MS Sql Server 2005 and 2008 jdbc driver
    Mention of a SAP Note in the first link or refer this note [831162|https://service.sap.com/sap/support/notes/831162]
    Regards,
    Abhishek.

  • Deploy JDBC drivers - SAP PI 7.0

    Hi guys,
    I have to deploy JDBC drivers to implement JDBC adapter in SAP PI 7.0. I've found some guides for XI 3.0 or SAP PI 7.1 but not to SAP PI 7.0. Can I apply guide for XI 3.0 or another exists?
    Best regards,
    Pablo

    Hi,
    >>>I've found some guides for XI 3.0 or SAP PI 7.1 but not to SAP PI 7.0. Can I apply guide for XI 3.0 or another exists?
    the one for 3.0 works for 7.0
    Regards,
    Michal Krawczyk

  • Error in deploying JDBC driver

    Hi All
    while deploying JDBC driver i am following tthis guide
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f04ce027-934d-2a10-5a8f-fa0b1ed4d88f
    while i run the command  C:>drivertool add aii_af_jmsproviderlib.sda msbase.jar mssqlserver.jar msutil.jar ojdbc14.jar
    i am getting this error
    ERROR: could not open SDA : INVALID SDA: error while parsing provider.xml: java.io.FileNotFoundException c:library.provider.dtd (system cannot find the file specified)
    can anybody give me the solution where can i find this library.provider.dtd?
    how can i remove this error
    Thanks
    sandeep

    Hi rajeev
    i have put driver tool files and also .sda file and sqljdbc.jar file in c:\drive but still i am getting this error
    C:\>drivertool add aii_af_jmsproviderlib.sda msbase.jar \
    mssqlserver.jar msutil.jar ojdbc14.jar
    SAP XI 3.0 JDBC/JMS Driver Tool. Version 1.0.1615
    Copyright (C) 2005 SAP AG. All rights reserved.
    Adding driver JAR(s) to aii_af_jmsproviderlib.sda:
    msbase.jar - Error: jar file not found
    mssqlserver.jar -  Error: jar file not found
    msutil.jar -  Error: jar file not found
    ojdbc14.jar - OK
    Writing changes to SDA. This may take a while, so please be patient.
    any suggestion?
    Thanks
    sandeep

  • SEVERE: com.mysql.jdbc.exceptions.jdbc4 : Communicat link failure

    Hi,
    I am developing web application using jsf2.0. problem is ,
    when we interact with servlet by single person, It working fine. but when we interact with servlet by more then one person at same time. server throws error
    SEVERE: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure
    Last packet sent to the server was 0 ms ago.
    How to solve the problem.
    server :Glashfish v3
    db :mysql 5.0
    thanks in advance.

    You must use a connection and then immediately close it.

  • Com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException

    Hi All,
    I want to connect to a stored procedure that is on mySQL database via BPEL and Jdeveloper 11.1.1.5
    The version of the MySQL database:
    mysqld Ver 5.1.53
    I am using the following driver :
    mysql-connector-java-5.1.25-bin
    I have pointed my JDeveloper to the new driver
    By doing the following :
    JDeveloper > Tools > Manage Libraries > ...
    When I test the connection it give me a success.
    In creating a new BPEL partnerlink - DatabaseAdapter with the new Connection to the MySQL and it seems to work, when I want to select from a table.
    But when I use the option Call stored procedure or function, using the schema aci. I can see the stored procedure aci_insert but when I want to select it, I am getting the following:
    An Error occured while obtaining arguments/source code for the selected stored procedure. Verify that the database connection is valid.
    Details :
    com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown table 'parameters' in information_schema
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
    at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
    at com.mysql.jdbc.Util.getInstance(Util.java:386)
    I am selecting the aci schema, but do not know why it keep on refering to information_schema

    Seems I miss something.
    IS there only two MySQL schema ?
    One to set up from sql file from Higgins server, the other is
    automatically set up by rpps-axis. I have both schema, maybe the one from
    Higgins is not uptodate (but I think it is). Or maybe I have to set up an
    other table but I didn't read about it.
    PS :
    There is some errors with eclipse componment. It's needed to had in
    rpps-axis/WEB-INF/lib/ the following files :
    org.eclipse.runtime.IExtensionRegistry
    org.eclipse.core.runtime
    org.eclipse.equinox.common
    org.eclipse.osgi
    Don't know if needed to work.

  • RFC JDBC Exception Handling

    Hello,
    i have the following scenario:
    RFC receiver adapter (synchronous) <> XI <> JDBC receiver adapter (to MS SQL-database)
    Is it possible to catch JDBC-exceptions, e.g. "duplicate primary key" and pass it to the calling rfc adapter?
    thanks for your help
    Christian

    Hello,
    still my problem is the exception handling of the synchronous JDBC - call.
    If an error occurs I get the error "no payload found" in sxmb_moni_bpe
    I think this is a problem of where the error occur, in the SOAP header
    In sxmb_moni i get the following Error:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Aufruf eines Adapters
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'KUNDEN' (structure 'STATEMENT_NAME'): com.microsoft.sqlserver.jdbc.SQLServerException: Verletzung der PRIMARY KEY-Einschränkung 'PK_Kunden'. Ein doppelter Schlüssel kann in das 'dbo.KUNDEN'-Objekt nicht eingefügt werden.</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Has anybody got any idea where my mistake is?#
    I´m at loss.
    If you need further information, contact me. I´ll send you the required informations.
    Thanks and regards
    Christian

  • Obtaining the original JDBC exception from an EJBException?

    Hello All,
    I am using EJB3 on Glassfish using the default TopLink persistence manager. Within a Session Bean, when the persistence manager catches a DB exception, it marks the transaction to be rolled back, and throws an EJBException, in turn wrapping a RollbackException. Now I was expecting to be able to get the original jdbc exception out of the caused by exception of one of these exceptions, but it is not.
    It is important that I do retrieve the original exception, as I need to report back to the users what the problem is, and to do this I need to analyse the SQL error codes.
    Note that these are the DB exceptions caught by toplink during managed transactions (e.g. an EJB persist or merge), not exceptions thrown by our code.
    Does anyone know if it is possible to get this information from Toplink?
    Edited by: user11973327 on Oct 4, 2009 7:19 AM

    It is odd that Glassfish would throw an exception on marking the transaction for rollback, and ignore the thrown error. You might wish to check with Glassfish on this. What version of TopLink are you using? A similar issue on WLS was fixed in EclipseLink, you may wish to try the latest EclipseLink release.
    You could also call flush() in your SessionBean to obtain the real database exception.
    James : http://www.eclipselink.org : http://en.wikibooks.org/wiki/Java_Persistence

  • Java.sql.SQLException:Exhausted Resultset

    Hi,
    I am Getting java.sql.SQLException:Exhausted Resultset after filling up the form and clicking submit button so that values inserted in to Database but instead of insertion iam getting this error.
    ThankQ
    Regards
    Saikishore

    You are trying to call a closed resultset.
    check your code. if u don't find then post your relavant code
    (Dhananjay Singh)

  • Javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException

    Hi,
    i'm trying to deploy an J2ee application with adf libraries in a Weblogic Server 9.2 with SOA Suite. My application was developed in JDeveloper 10.1.3.3. in Windows XP. My application server is in Linux RedHat 5 Enterprise. In Jdeveloper, when i tried to deploy my application I got the next log:
    ---- Deployment started. ---- Aug 17, 2009 3:39:17 PM
    Target platform is WebLogic Server 9.x (weblogic).
    Checking weblogic.xml for completeness...
    Wrote WAR file to C:\jd\jdev\mywork\ECSBPM\ViewController\deploy\ECSBPM.war
    Wrote EAR file to C:\jd\jdev\mywork\ECSBPM\ViewController\deploy\ECSBPM.ear
    java -classpath C:\jd\jdev\mywork\weblogic.jar weblogic.Deployer -adminurl http://10.10.1.190:8001 -user weblogic -password **** -debug -verbose -deploy -upload -source C:\jd\jdev\mywork\ECSBPM\ViewController\deploy\ECSBPM.ear -name ECSBPM
    weblogic.Deployer invoked with options: -adminurl http://10.10.1.190:8001 -user weblogic -debug -verbose -deploy -upload -source C:\jd\jdev\mywork\ECSBPM\ViewController\deploy\ECSBPM.ear -name ECSBPM
    [WebLogicDeploymentManagerImpl.<init>():103] : Constructing DeploymentManager for J2EE version V1_4 deployments
    [WebLogicDeploymentManagerImpl.getNewConnection():146] : Connecting to admin server at 10.10.1.190:8001, as user weblogic
    [ServerConnectionImpl.getEnvironment():288] : setting environment
    [ServerConnectionImpl.getEnvironment():291] : getting context using http://10.10.1.190:8001
    [ServerConnectionImpl.close():334] : Closing DM connection
    [ServerConnectionImpl.close():354] : Unregistered all listeners
    weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 'http://10.10.1.190:8001': invalid type code: 31. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.
         at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:314)
         at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:137)
         at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
         at weblogic.utils.compiler.Tool.run(Tool.java:158)
         at weblogic.utils.compiler.Tool.run(Tool.java:115)
         at weblogic.Deployer.run(Deployer.java:70)
         at weblogic.Deployer.main(Deployer.java:54)
    Caused by: javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException
         at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:121)
         at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:84)
         at weblogic.deploy.api.tools.SessionHelper.getRemoteDeploymentManager(SessionHelper.java:482)
         at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:295)
         ... 6 more
    Caused by: weblogic.deploy.api.spi.exceptions.ServerConnectionException
         at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:143)
         at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(WebLogicDeploymentManagerImpl.java:148)
         at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:118)
         ... 9 more
    Caused by: javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalException: failed to unmarshal class weblogic.security.acl.internal.AuthenticatedUser; nested exception is:
         java.io.StreamCorruptedException: invalid type code: 31]
         at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:85)
         at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:41)
         at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:773)
         at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:673)
         at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:466)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:373)
         at weblogic.jndi.Environment.getContext(Environment.java:307)
         at weblogic.jndi.Environment.getContext(Environment.java:277)
         at weblogic.jndi.Environment.createInitialContext(Environment.java:200)
         at weblogic.jndi.Environment.getInitialContext(Environment.java:184)
         at weblogic.jndi.Environment.getInitialContext(Environment.java:162)
         at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getContext(ServerConnectionImpl.java:330)
         at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getEnvironment(ServerConnectionImpl.java:302)
         at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:141)
         ... 11 more
    Caused by: java.rmi.UnmarshalException: failed to unmarshal class weblogic.security.acl.internal.AuthenticatedUser; nested exception is:
         java.io.StreamCorruptedException: invalid type code: 31
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:223)
         at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:224)
         at weblogic.common.internal.RMIBootServiceImpl_923_WLStub.authenticate(Unknown Source)
         at weblogic.security.acl.internal.Security$1.run(Security.java:185)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.security.acl.internal.Security.authenticate(Security.java:181)
         at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRemotely(WLInitialContextFactoryDelegate.java:734)
         at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:667)
         ... 21 more
    Caused by: java.io.StreamCorruptedException: invalid type code: 31
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.readObject(Unknown Source)
         at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:195)
         at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:565)
         at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:191)
         at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:62)
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:221)
         ... 29 more
    **** weblogic.deploy returned with non-zero exit status: 1
    **** weblogic.deploy returned with non-zero exit status: 1
    Elapsed time for deployment: 17 seconds
    #### Deployment incomplete. #### Aug 17, 2009 3:39:34 PM
    ---- Deployment started. ---- Aug 17, 2009 3:39:17 PM
    Target platform is WebLogic Server 9.x (weblogic).
    Checking weblogic.xml for completeness...
    Wrote WAR file to C:\jd\jdev\mywork\ECSBPM\ViewController\deploy\ECSBPM.war
    Wrote EAR file to C:\jd\jdev\mywork\ECSBPM\ViewController\deploy\ECSBPM.ear
    java -classpath C:\jd\jdev\mywork\weblogic.jar weblogic.Deployer -adminurl http://10.10.1.190:8001 -user weblogic -password **** -debug -verbose -deploy -upload -source C:\jd\jdev\mywork\ECSBPM\ViewController\deploy\ECSBPM.ear -name ECSBPM
    weblogic.Deployer invoked with options: -adminurl http://10.10.1.190:8001 -user weblogic -debug -verbose -deploy -upload -source C:\jd\jdev\mywork\ECSBPM\ViewController\deploy\ECSBPM.ear -name ECSBPM
    [WebLogicDeploymentManagerImpl.<init>():103] : Constructing DeploymentManager for J2EE version V1_4 deployments
    [WebLogicDeploymentManagerImpl.getNewConnection():146] : Connecting to admin server at 10.10.1.190:8001, as user weblogic
    [ServerConnectionImpl.getEnvironment():288] : setting environment
    [ServerConnectionImpl.getEnvironment():291] : getting context using http://10.10.1.190:8001
    [ServerConnectionImpl.close():334] : Closing DM connection
    [ServerConnectionImpl.close():354] : Unregistered all listeners
    weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 'http://10.10.1.190:8001': invalid type code: 31. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.
         at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:314)
         at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:137)
         at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
         at weblogic.utils.compiler.Tool.run(Tool.java:158)
         at weblogic.utils.compiler.Tool.run(Tool.java:115)
         at weblogic.Deployer.run(Deployer.java:70)
         at weblogic.Deployer.main(Deployer.java:54)
    Caused by: javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException
         at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:121)
         at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:84)
         at weblogic.deploy.api.tools.SessionHelper.getRemoteDeploymentManager(SessionHelper.java:482)
         at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:295)
         ... 6 more
    Caused by: weblogic.deploy.api.spi.exceptions.ServerConnectionException
         at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:143)
         at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(WebLogicDeploymentManagerImpl.java:148)
         at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:118)
         ... 9 more
    Caused by: javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalException: failed to unmarshal class weblogic.security.acl.internal.AuthenticatedUser; nested exception is:
         java.io.StreamCorruptedException: invalid type code: 31]
         at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:85)
         at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:41)
         at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:773)
         at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:673)
         at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:466)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:373)
         at weblogic.jndi.Environment.getContext(Environment.java:307)
         at weblogic.jndi.Environment.getContext(Environment.java:277)
         at weblogic.jndi.Environment.createInitialContext(Environment.java:200)
         at weblogic.jndi.Environment.getInitialContext(Environment.java:184)
         at weblogic.jndi.Environment.getInitialContext(Environment.java:162)
         at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getContext(ServerConnectionImpl.java:330)
         at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getEnvironment(ServerConnectionImpl.java:302)
         at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:141)
         ... 11 more
    Caused by: java.rmi.UnmarshalException: failed to unmarshal class weblogic.security.acl.internal.AuthenticatedUser; nested exception is:
         java.io.StreamCorruptedException: invalid type code: 31
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:223)
         at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:224)
         at weblogic.common.internal.RMIBootServiceImpl_923_WLStub.authenticate(Unknown Source)
         at weblogic.security.acl.internal.Security$1.run(Security.java:185)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.security.acl.internal.Security.authenticate(Security.java:181)
         at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRemotely(WLInitialContextFactoryDelegate.java:734)
         at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:667)
         ... 21 more
    Caused by: java.io.StreamCorruptedException: invalid type code: 31
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.readObject(Unknown Source)
         at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:195)
         at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:565)
         at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:191)
         at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:62)
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:221)
         ... 29 more
    **** weblogic.deploy returned with non-zero exit status: 1
    **** weblogic.deploy returned with non-zero exit status: 1
    Elapsed time for deployment: 17 seconds
    #### Deployment incomplete. #### Aug 17, 2009 3:39:34 PM
    I verified and my credentials are correct. Please your help.
    Thanks
    Eve

    Hi,
    I hope you are deploying application through build file.
    Can you check build.xml file whether you had given correct Admin url and port number.
    Regards,
    Kal
    Edited by: kalyan Pasupuleti on Sep 12, 2012 1:39 AM

  • Javax.enterprise.deploy.spi.exceptions.InvalidModuleException: [J2EE Deploy

    Hi,
    I'm using Weblogic Server 9.2. I'm having problems to deploy a .ear aplication.?:|
    When I try to install the aplication i get the following error:
    javax.enterprise.deploy.spi.exceptions.InvalidModuleException: [J2EE Deployment SPI:260105]Failed to create DDBeanRoot for application, 'sgi-core-1.0.jar'
    Could anyone say me how can I solve this error?
    The deployment descriptor weblogic-ejb-jar.xml seems to be correct.
    I'm using Andromda to generate the .ear file, so I don't know if it can be causing any problems
    If anyone could help me...
    Thanks in advance

    Hi,
    The J2EE Error code siply suggest that there is something wrong in your Deployment Descriptors...
    Can u please post the XML files available inside your "WEB-INF" directory?
    Thanks
    Jay SenSharma
    http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)

  • Cannot import com.mysql.jdbc.exceptions

    Hi all,
    I have a pretty simple question.
    Why it is not possible to import classes from the package com.mysql.jdbc.exceptions?
    My classpath is set up correctly I can use jdb driver to connect to my db, but if I try to import com.mysql.jdbc.exceptions I receive a compile time error
    package com.mysql.jdbc.exceptions does not exist!
    Anyone could help?
    Thanks for your attention
    By Manio

    Thankfully there is no reason for you to do this so it's really not a problem.
    You should ONLY be importing java.sql.* (and sometimes javax) but not specific driver packages.

Maybe you are looking for