GetCollectionMetaData method is not supported by OracleXMLDataSetGenJDBC

Hi,
We are in the process of migrating our Web Application from Oracle 9i to Oracle 10.1.0.5. Our Web Application runs under WebLogic 9.1 Server and uses Oracle XSQL APIs to store CLOB Data in Database. We are using ojdbc14.jar as well as xsu12.jar and other required Oracle XSQL Libraries.
We observed the following error
===============================
ORA-29532: Java call terminated by uncaught Java exception: oracle.xml.sql.OracleXMLSQLException: Invalid context handle specified. ORA-06512: at XSU.DBMS_XMLQUERY , line 178 ORA-06512: at XSU.XSU$XML_XCHANGE , line 293 ORA-29532: Java call terminated by uncaught Java exception: oracle.xml.sql.OracleXMLSQLException: getCollectionMetaData: this method is not supported by OracleXMLDataSetGenJdbc class. Please use OracleXMLDataSetExtJdbc instead. ORA-06512: at line 1
===============================
When we printed the underlying connection object class name, it appeared as "oracle.jdbc.driver.T4CConnection".
What is the cause of this issue? How to resolve this issue?

One import piece of info: This OracleXMLQuery works against a standard table. The query that fail goes against the following view and uses nested tables(object lists).
SELECT v.name as PACKAGE,
u.name,
u.version,
u.iteration,
u.summary,
u.events_basic,
u.author,
u.rev_date,
u.ext_points,
u.assumptions,
u.preconditions,
u.revision_notes,
u.trigger_event,
u.package as PUID,
u.ALTERNATE_PATHS AS ALTERNATE_PATHS_LIST,
u.EXCEPTION_PATHS AS EXCEPTION_PATHS_LIST,
u.BUSINESS_RULES AS BUSINESS_RULE_LIST
FROM USECASE u, DESIGN_PACKAGE v
WHERE u.package=v.puid
AND EXISTS(SELECT 'X'
     FROM DESIGN_CUR_VER d
     WHERE d.name = u.name
     AND d.version = u.version
     AND d.design_date = u.rev_date)
AND EXISTS (SELECT 'X'
     FROM USECASE_AUDIT a
     WHERE a.package = u.package
     AND a.name = u.name
     AND a.version = u.version
     AND a.timestamp = u.rev_date
     AND a.status_code IN('created','modified','rejected'))
ORDER BY v.name, u.name

Similar Messages

  • GetCollectionMetaData:  this method is not supported by 'OracleXMLDataSetGenJdbc' cla

    The following Java code:
    // Create an OracleOCIConnectionPool instance with default configuration
    OracleOCIConnectionPool cpool = new OracleOCIConnectionPool("appserver", "9ias", url, null);
    // Print out the default configuration for the OracleOCIConnectionPool
    System.out.println ("-- The default configuration for the OracleOCIConnectionPool --");
    displayPoolConfig(cpool);
    // Get a connection from the pool
    OracleOCIConnection conn1 = (OracleOCIConnection) cpool.getConnection("usecase", "uml");
    // Create a Statement
    Statement stmt = conn1.createStatement ();
    // Select the ENAME column from the EMP table
    ResultSet rset = stmt.executeQuery ("select * from usecases_ov");
    OracleXMLQuery q = new OracleXMLQuery(conn1,"select * from usecases_ov");
    System.out.println(q.getXMLString());
    Produces:
    -- The default configuration for the OracleOCIConnectionPool --
    Min poolsize Limit: 1
    Max poolsize Limit: 1
    Connection Increment: 0
    NoWait: false
    Timeout: 0
    PoolSize: 1
    ActiveSize: 0
    <?xml version = '1.0'?>
    <ERROR>oracle.xml.sql.OracleXMLSQLException: getCollectionMetaData: this method is not supported by 'OracleXMLDataSetGenJdbc' class. Please use 'OracleXMLDataSetExtJdbc' instead.</ERROR>
    Any Suggestions?

    One import piece of info: This OracleXMLQuery works against a standard table. The query that fail goes against the following view and uses nested tables(object lists).
    SELECT v.name as PACKAGE,
    u.name,
    u.version,
    u.iteration,
    u.summary,
    u.events_basic,
    u.author,
    u.rev_date,
    u.ext_points,
    u.assumptions,
    u.preconditions,
    u.revision_notes,
    u.trigger_event,
    u.package as PUID,
    u.ALTERNATE_PATHS AS ALTERNATE_PATHS_LIST,
    u.EXCEPTION_PATHS AS EXCEPTION_PATHS_LIST,
    u.BUSINESS_RULES AS BUSINESS_RULE_LIST
    FROM USECASE u, DESIGN_PACKAGE v
    WHERE u.package=v.puid
    AND EXISTS(SELECT 'X'
         FROM DESIGN_CUR_VER d
         WHERE d.name = u.name
         AND d.version = u.version
         AND d.design_date = u.rev_date)
    AND EXISTS (SELECT 'X'
         FROM USECASE_AUDIT a
         WHERE a.package = u.package
         AND a.name = u.name
         AND a.version = u.version
         AND a.timestamp = u.rev_date
         AND a.status_code IN('created','modified','rejected'))
    ORDER BY v.name, u.name

  • Java.lang.Error: JAX-RPC 1.1 method is not supported in WLS 8.1 clients.

    We have some web services that run under OC4J 10.1.3.4. We have various JEE 'client' apps (JSF, servlets etc.) that use these web services. These JEE apps also run under OC4J.
    We started a migration project from oc4j to weblogic 10.3.2. In phase 1 we want to move these JEE 'client' apps to weblogic. In phase 2 we want to move the web services themselves to weblogic with adjustments to the JEE 'client' apps as needed.
    However we ran into an issue during this phase 1. Deploying these JEE 'client' apps to weblogic results in an error like this:
    java.lang.Error: JAX-RPC 1.1 method is not supported in WLS 8.1 clients. If you are attempting to run an OC4J 10.1.3 JAX-RPC client in WLS, please see the Web Service Migration Guide for instructions.
    We are including Oracle web services client libraries (http://download.oracle.com/otn/java/oc4j/1013/wsclient_extended.zip) in these JEE 'client' apps's war files because weblogic does not have them.
    What part of Web Service Migration Guide is the above error message talking about? Do we have to re-generate the client side proxies for all these web services using weblogic's clientgen task in 'JAXRPC' mode? Many of these web services are doc/literal jax-rpc web services. Or does the migration guide recommend we migrate the web services first to weblogic? Any other specific information on working around this error message would be greatly appreciated.

    Hi,
    I had the same issue but I just managed to fix it. You must upgrade and/or regenerate you proxy. This creates new classes (possibily in a new package) that you must use in your code. I had this error because the classes directory was not clean after the rebuild and the old classes (in the old package) were still present, so the compilation was successful with the old classes. So clean your classes directories, regenerate your proxy and use the new classes in your code.
    Regards,
    Sylvain

  • Web Deploy error - "This method is not supported by this class"

    I have an MVC project which I am trying to deploy to one of our internally-hosted web front end servers via a TFS build process. Our server hosts the MS Deploy service, and other solutions deploy without problems to the same box. The parameters for the build
    process are as follows:
    /p:DeployOnBuild=True /p:DeployTarget=MsDeployPublish /p:MSDeployPublishMethod=WMSVC /p:MsDeployServiceUrl=https://<server>:8172/msdeploy.axd /p:DeployIISAppPath="<internal.site.com>" /p:username=<username> /p:password=<password>
    /p:IncludeIisSettingsOnPublish=false /p:AllowUntrustedCertificate=True /p:OutputPath=bin\ /p:SkipExtraFilesOnServer=True /p:VisualStudioVersion=11.0
    The error message I receive at the point the build reaches the deployment activity is:
    Web deployment task failed. (Could not complete the request to remote agent URL 'https://<server>:8172/msdeploy.axd?site=<internal.site.com>'.)
    Could not complete the request to remote agent URL 'https://<server>:8172/msdeploy.axd?site=<internal.site.com>'.
    The request was aborted: The request was canceled.
    This method is not supported by this class.
    We've found
    this StackOverflow post which describes the same error we're experiencing, however the suggested solution is something we already do in our server configuration, so this doesn't resolve the issue for us.
    Has anyone seen this error before, or is able to make any suggestions why it is happening?

    Hi Matt,
    You have to have a look in the build log then copy the command that is under Run MSBuild node and executed it on the build agent.
    You should find something like below:
    C:\Program Files (x86)\MSBuild\12.0\bin\amd64\MSBuild.exe /nologo /noconsolelogger "C:\Builds\....sln" /nr:False /fl /flp:"logfile=C:\Builds\...log;encoding=Unicode;verbosity=normal" /p:SkipInvalidConfigurations=true /p:CreatePackageOnPublish=true /p:DeployOnBuild=true /p:SkipExtraFilesOnServer=True /m /p:OutDir="C:\Builds\...\bin\\" /p:Configuration="DEV" /p:Platform="Any CPU" /p:VCBuildOverride="C:\Builds\....sln.Any CPU.DEV.vsprops" /dl:WorkflowCentralLogger,"C:\Program Files\Microsoft Team Foundation Server 12.0\Tools\Microsoft.TeamFoundation.Build.Server.Logger.dll";"Verbosity=Normal;BuildUri=vstfs:///Build/Build/31630;IgnoreDuplicateProjects=False;InformationNodeId=14;TargetsNotLogged=GetNativeManifest,GetCopyToOutputDirectoryItems,GetTargetPath;LogProjectNodes=True;LogWarnings=True;TFSUrl=http://...-tfs:8080/tfs/...;"*WorkflowForwardingLogger,"C:\Program Files\Microsoft Team Foundation Server 12.0\Tools\Microsoft.TeamFoundation.Build.Server.Logger.dll";"Verbosity=Normal;" /p:BuildId="aa2d3857-27e9-4854-b44f-4ca625ccd786,vstfs:///Build/Build/31630" /p:BuildLabel="..._2015.02.27.2" /p:BuildTimestamp="Fri, 27 Feb 2015 11:16:41 GMT" /p:BuildDefinition="..."
    Daniel

  • Jdeveloper 11g - JAX-RPC 1.1 method is not supported in WLS 8.1 clients.

    Hi,
    I am using Jdeveloper 11g and migrating a web Service Proxy created using jdeveloper 10g.
    I imported all the proxy classes and when I try to run web service client In Jdeveloper 11g I get the following error
    "JAX-RPC 1.1 method is not supported in WLS 8.1 clients. If you are attempting to run an OC4J 10.1.3 JAX-RPC client in WLS, please see the Web Service Migration Guide for instructions."
    Please advise on how to solve this?
    which is the offending jar/library file in Jdeveloper 11g which is causing the above error?.
    Is the above problem there in the WebLogic Server Runtime also?
    Please let me know.
    2) I cannot generate web server proxies also with jdev11g because the wsdl has overloaded methods omitting the name property within the input and output message, ie, they have a null name. therefore Jdeveloper 11g is using the library which
    when called with an overloaded operation that contains null input/output message names, a duplicate error occurs because it sees other operations with the same name. so it is effectively not allowing to create the web service proxies.
    Thanks,
    Appreciate your quick response to the above

    Have you checked the 'Web Service Migration Guide' mentioned in the error message?
    Timo

  • HTTP Method Post not supported by this URL

    We are running WL6.0sp1 on Win2000. When we try to open a JSP page which calls
    a servlet we get a "HTTP Method Post not supported by this URL". This same setup
    (WL 6.0sp1 on Win2000) on another machine works absolutely fine running from the
    same client. Is there any setup that needs to be done in Weblogic for this? Any
    pointers on this would be appreciated.
    Rgds

    Normally when you get this error, your username/password is not correct.
    It's not a clean way of errorhandling. I have had the same issue and after a while i noticed the password i entered was not correct.

  • The :pserver: access method is not supported by this port of CVS

    i receive the following error when trying to connect to cvs
    the :pserver: access method is not supported by this port of CVS

    i receive the following error when trying to connect to cvs
    the :pserver: access method is not supported by this port of CVS Use the CVS 1.11.2 from http://www.cvshome.org, sounds like you are using a version of cvs which (is maybe CVSNT) doesn't support pserver.
    Rob

  • Last() method  was not supported by "resultset type of TYPE_FORWARD_ONLY "

    Hi all,
    I got this exception
    java.sql.SQLException: JZ0BT: The last() method is not supported for ResultSets of type TYPE_FORWARD_ONLY.
    but while creating statement object i am dong like this
    stmt = con.prepareCall(sql.toString(),ResultSet.TYPE_SCROLL_INSENSITIVE,
    ResultSet.CONCUR_READ_ONLY);
    then also it is giving the same exception.
    my bean code is like this,
    try {
    //Dynamically get the row size for the o/p dataset
    from result set
    rs.last();
    System.out.println(rs);
    int numrows =rs.getRow();
    can anyone help me out to get the total number of rows in Resultset
    Thanks in advance
    Ravi

    There's no easy way to do it that I know of. All you can do is iterate through and count. - MOD

  • BIweb service proxy JAX-RPC 1.1 method is not supported in WLS 8.1 clients

    Hello
    I have an application in oracle Application server and I'm migrating to weblogic 11g .
    I have used web service proxy for BIPublisher 10.1.3.4 , careated by jdeveloper web service proxy wizard , when I want using it in weblogic , In corresponding form that uses BI Publisher web service proxy , I encounter following error :
    "JAX-RPC 1.1 method is not supported in WLS 8.1 clients , if you attempting to run oc4j 10.1.3 JAX-RPC client in WLS,please see Web service Migration Guide for Instructions"
    What should I do?
    Regards
    Mehdi

    Spoke to dev and there was a bug logged, it seems to be down to Weblogic's implementation.
    +This is pure WLS issue. The root cause of this problem is that Weblogic's
    SAAJ implementation. No codechange on BIP server side
    WLS 10 ships with two SAAJ implementations. By default the buggy 9.x
    implementation is used (which lives in the package
    weblogic.webservice.core.soap), but there is a new implementation, which
    supports SAAJ 1.3 (which lives in the package weblogic.xml.saaj). I also
    checked in a debugging jsp page, which could help looking at the DEBUG
    logging to see which SAAJ implementation is used.
    JSP testpage xmlponline/wwwroot/wsclient/soapclient-wls-8270711.jsp
    To use this new version, you have to make sure setting the
    -Djavax.xml.soap.MessageFactory=weblogic.xml.saaj.MessageFactoryImpl
    in startWebLogic script. +
    Please give the solution a try and let me know if it works.
    Regards
    tim

  • Pop3 sasl AUTH PLAIN not supported over TLS?

    Hi,
    Thunberbird does not work with Mac OS X server 10.5.5 POP3 because SASL AUTH PLAIN method is not supported when TLS or SSL is used.
    According to RFC5034:
    "To ensure interoperability, client and server implementations of this extension MUST implement the PLAIN SASL mechanism [RFC4616] running over TLS [RFC2595]."
    I have looked throught Cyrus documentation but I cannot find a find to enable AUTH PLAIN over TLS.
    Any clue how to make the server RFC compliant?
    Best regards,
    Nicolas.

    Really? Well I'd really like to dig through this. Could you post more info about your setup so that we can compare and check where the problem is on my side?
    My setup: Mac OS X Server 10.5.5 running Cyrus POP3 v2.3.8-OS X Server 10.5. SSL and TLS are enabled but not required. Port 995 is only port open for outside clients.
    Thunberbird version 2.0.0.18 and 3 beta 1 cannot connect to POP over SSL or TLS. The error I get is: 'authentication failure'.
    Non encrypted connection works (Thunberbird will issue a USER/PASS and will not use the AUTH PLAIN method).
    SASL and Kerberos are enabled on the server.
    If I connect with openssl on command line to port 995, then issue a CAPA command here is the result:
    CAPA
    +OK List of capabilities follows
    SASL GSSAPI
    EXPIRE NEVER
    LOGIN-DELAY 0
    TOP
    UIDL
    PIPELINING
    RESP-CODES
    AUTH-RESP-CODE
    USER
    Could you please post the result of the same test?
    ('openssl> s_client -connect 10.1.1.1:995', then type 'CAPA').
    Thanks to help on this,
    Nicolas.

  • How to Overcome DomainOperationEntry overloads are not supported in C#

      Hi Team ,
    I have a assigmmnet to finsh . requerment is
    1) I have to Comboboxes one is cmbDomain , second one is cmbSubDoamin
      based on selected value in cmbDoman , cmbSubDoamin has to fill.
     for this  I  am  using WCFRIA Serivice
    In sercive I have two methods like bellow.
    //for Domain
    public IQueryable<DomainGroup> GetDomainGroups()
    return this.ObjectContext.DomainGroups;
    // for SubDoamin
    public IQueryable<Domain> GetDomains()
    return this.ObjectContext.Domains;
    //for subdomain based on selected value in Domain
    public IQueryable<Domain> GetDomains(string selectedDomain)
    return this.ObjectContext.Domains.Where(x => x.Title.ToUpper() == selectedDomain.ToUpper());
    in Silverlight i implimented bellow code
    <riaControls:DomainDataSource x:Name="source" QueryName="GetDomainGroups" AutoLoad="True"> <riaControls:DomainDataSource.DomainContext>
    <domain:DomainService1/> </riaControls:DomainDataSource.DomainContext>
    </riaControls:DomainDataSource>
    <riaControls:DomainDataSource x:Name="SubDomainSource" QueryName="GetDomains" AutoLoad="True">
    <riaControls:DomainDataSource.DomainContext>
    <domain:DomainService1/> </riaControls:DomainDataSource.DomainContext>
    <riaControls:DomainDataSource.QueryParameters>
    <riaControls:Parameter ParameterName="selectedDomain" Value="{Binding Path=SelectedValue,ElementName=cmbDomain}"/> </riaControls:DomainDataSource.QueryParameters>
    </riaControls:DomainDataSource>
    <StackPanel Orientation="Vertical">
    <!--<sdk:DataGrid x:Name="domainGrid" ItemsSource="{Binding Data, ElementName=source}" Height="200" Width="200"/>-->
    <sdk:Label Content="Domain"/>
    <ComboBox x:Name="cmbDomain" ItemsSource="{Binding Data,ElementName=source}" DisplayMemberPath="Title" Height="50" Width="100"></ComboBox>
    <sdk:Label Content="Sub Domain"/>
    <ComboBox x:Name="cmbSubDomain" ItemsSource="{Binding Data,ElementName=SubDomainSource}" DisplayMemberPath="Title" Height="50" Width="100"></ComboBox>
    </StackPanel>
     if any one help it could be a great support for me .
    Srilatha

    You can't use overloads.
    You need to rename one of your GetDomains:
    public IQueryable<Domain> GetDomains()
    return this.ObjectContext.Domains;
    //for subdomain based on selected value in Domain
    public IQueryable<Domain> GetDomains(string selectedDomain)
    return this.ObjectContext.Domains.Where(x => x.Title.ToUpper() == selectedDomain.ToUpper());
    from
    https://msdn.microsoft.com/en-us/library/ee707366%28v=vs.91%29.aspx?f=255&MSPPError=-2147217396
    General Rules for using Inheritance            
    The following rules apply to using inheritance with RIA Services.
    Inheritance is supported only for entity types. Non-entity types are treated as the type specified in the domain service operation signature.
    Interface types are not supported for return values or parameters in domain service operations.
    The set of types in an inheritance hierarchy must be known at the time of code generation. The behavior for returning a type not specified at the time of code generation is unspecified and implementation-dependent.
    The virtual modifier on public properties and fields for an entity type is permitted but ignored when generating the corresponding entity type on the client.
    Method overloads for domain service operations are not permitted.
    The new (C#) and Shadows (Visual Basic) keywords on public properties are not allowed on entity types and will result in an error when client code is generated.
    LINQ query capabilities related to inheritance cannot be translated for execution of domain service methods. Specifically,
    OfType<T>, is,
    as, and GetType() operators and methods are not supported.  However, these operators may be used directly against
    EntitySet or
    EntityCollection<TEntity> in LINQ to Objects queries.
    Hope that helps.
    Technet articles: Uneventful MVVM;
    All my Technet Articles

  • Function overloading not supported by RMI-IIOP?

    Hi, I am successfully connecting to a stateful session EJB running under
    WebLogic 5.1, sp5 as an RMI-IIOP client. Here's the problem. If I try to
    invoke an overloaded public method on my bean I get the following error:
    Remote Error: CORBA UNKNOWN 0 Maybe; nested exception is:
    org.omg.CORBA.UNKNOWN: minor code: 0 completed: Maybe
    If I comment out all versions but one of the overloaded method and rebuild,
    everything's peachy, I can call the method.
    Is method overloading not supported by RMI-IIOP? Each version of the
    overloaded method does get added to the weblogic.ejbc generated IDL file,
    but again if there are multiple overloaded versions it doesn't work.
    Thx,
    Sandy Barletta

    Eduardo, have you had a chance to test this yet?
    Thx,
    Sandy
    "Eduardo Ceballos" <[email protected]> wrote in message
    news:[email protected]..
    This is a bug, I suspect. This should of course work. I'll look into it.
    Sandy Barletta wrote:
    Hi, I am successfully connecting to a stateful session EJB running under
    WebLogic 5.1, sp5 as an RMI-IIOP client. Here's the problem. If I try to
    invoke an overloaded public method on my bean I get the following error:
    Remote Error: CORBA UNKNOWN 0 Maybe; nested exception is:
    org.omg.CORBA.UNKNOWN: minor code: 0 completed: Maybe
    If I comment out all versions but one of the overloaded method and
    rebuild,
    everything's peachy, I can call the method.
    Is method overloading not supported by RMI-IIOP? Each version of the
    overloaded method does get added to the weblogic.ejbc generated IDLfile,
    but again if there are multiple overloaded versions it doesn't work.
    Thx,
    Sandy Barletta

  • Strange IE ExternalInterface Bug: "Object does not support this property or method"

    We have an application on a relatively slow server (I mention
    the speed because it may be relevant).
    The app is flash 8 and uses ExternalInterface to call a
    javascript function in its parent page. It also used the
    ExternalInterface to receive a call from another function. These
    calls happens separately (the outbound one calls up a list view of
    items, clicking on an item calls up the details in the flash
    movie). In between the calls, the flash movie is hidden by moving
    it off screen using absolute positioning.
    On my local development box (Windows XPSP2) this works fine
    in both directions.
    On our production server (LAMP) this works fine in both
    directions in Firefox 1.5 and 2.0
    BUT while the outbound call from Flash to the page works fine
    in Internet Explorer 6 or 7, the call back from the page to the
    flash movie fails with the error messgage "Object does not support
    this method or property"
    We've tried not hiding the flash so it is always present on
    the page and still the browser > flash communication breaks in
    ie.
    We've tried using both the Adobe active content script and
    swfobject to embed the flash in the page with no difference in the
    resultset. In truth we've given up and gone to a two-page solution,
    reloading the flash from the start each time but I wondered if
    anyone had encountered a similar issue? Can't see why it would work
    perfectly in FF but not in IE.

    Not sure if this is your problem, but you do reference the
    Flash object
    differently, depending on the browser. In a video player we
    made, that uses
    JS to communicate back to Flash, I use a function like this
    to modify the
    variable depending on the browser:
    function changeVideo(xname){
    //ff
    if(window.vplayer){
    window.document["vplayer"].SetVariable("theXML", xname);
    window.document["vplayer"].GotoFrame(2);
    window.document["vplayer"].Play();
    //ie
    if(document.vplayer){
    document.vplayer.SetVariable("theXML", xname);
    document.vplayer.GotoFrame(2);
    document.vplayer.Play();
    The Flash is in a <div> named 'vplayer'
    Dave -
    Head Developer
    http://www.blurredistinction.com
    Adobe Community Expert
    http://www.adobe.com/communities/experts/

  • GRMG RFC Configuration "HTTP method GET is not supported by this URL"

    Hi All,
    when i create the RFC Destinaton for SLD  with regards to GRMG Configuration and test the rfc i get the Reason code 400 with error "HTTP method GET is not supported by this URL".
    Even if i call  http://hostname:port/sld/rtc in the browser i get the same error.
    RFC Details:
    Target machine:Host
    Service No: port no
    path prefix: /sld/rtc
    My other RFC destinations for rwb,IR,ID,Adapter Engine works well.
    I would appreciate your suggestions on this
    Aravind

    Hi David,
    I feel sorry to wake this thread up after long time.
    It's the same situation, connection testing for SLD returns 400 "HTTP method GET is not supported by this URL".
    However, CCMS hearbeat seems to work fine with SLD. It returns green.
    I have a question here. Is it OK if we leave it that way without changing GRMG?
    Is there any potential problem, or side effect when the RFC destination returns 400?
    Thank you very much,
    Teyun

  • JDBC 2.0 method not supported Error occuring in WL 6.1 sp1

    Hi ,
    When I connect to a mssqlserver 2000 using a session bean and execute the following
    statement
    "stmDataAccess=conDataAccess.createStatement(ResultSet.CONCUR_UPDATABLE,ResultSet.TYPE_SCROLL_INSENSITIVE);"
    i get the following error at the client and server side
    what can be wrong?.Support for Jdbc 2.0 is inherent in WL 6.1 isn't it?
    java.rmi.RemoteException: EJB Exception:; nested exception is:
    javax.ejb.EJBException
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented]
    Start server side stack trace:
    java.rmi.RemoteException: EJB Exception:; nested exception is:
    javax.ejb.EJBException
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented]
    java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
    at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    javax.ejb.EJBException
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented]
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:271)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    ; nested exception is:
    javax.ejb.EJBException:
    Start server side stack trace:
    java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
    at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    javax.ejb.EJBException
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented]
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:271)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
    Start server side stack trace:
    java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
            at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
            at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
            at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
            at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
            at java.lang.reflect.Method.invoke(Native Method)
            at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
            at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
            at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
            at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
            at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
            at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
            at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
            at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
            at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
            at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
            at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End  server side stack trace
    java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
    Start server side stack trace:
    java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
    at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    <<no stack trace available>>
    --------------- nested within: ------------------
    javax.ejb.EJBException:
    Start server side stack trace:
    java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
    at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    javax.ejb.EJBException
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented]
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:271)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
    Start server side stack trace:
    java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method is not implemented
            at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
            at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
            at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
            at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
            at java.lang.reflect.Method.invoke(Native Method)
            at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
            at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
            at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
            at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
            at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
            at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
            at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
            at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
            at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
            at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
            at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End  server side stack trace
    <<no stack trace available>>

    Hi
    As I know, not all mehtods are supported by WebLogic. For Example for Oracle only
    a SubSet of the JDBC methods are supported (see the link http://e-docs.bea.com/wls/docs61///////oracle/API_joci.html#1070961).
    I can imagine that for Microsoft Products this is even worse.
    Regards Patrick
    "Thomas" <[email protected]> wrote:
    >
    Hi,
    I'm using the driver that comes along with the application server ie
    weblogic.jdbc.mssqlserver4.Driver.If
    this driver doesn't support JDBC 2.0 where can i find a suitable driver
    as my
    app needs updatable recordsets with updateXXX methods and absolute moves?
    Thanks in advance
    "noone_home" <[email protected]> wrote:
    Hi,
    It looks like your JDBC driver does not support JDBC 2.0. I believethe
    the JDBC
    driver for SQL Server that came with WLS 6.x supports only JDBC 1.1.
    I'm making
    the assumption that that is the driver which you are using.
    hth.
    "Thomas" <[email protected]> wrote:
    Hi ,
    When I connect to a mssqlserver 2000 using a session bean and execute
    the following
    statement
    "stmDataAccess=conDataAccess.createStatement(ResultSet.CONCUR_UPDATABLE,ResultSet.TYPE_SCROLL_INSENSITIVE);"
    i get the following error at the client and server side
    what can be wrong?.Support for Jdbc 2.0 is inherent in WL 6.1 isn't
    it?
    java.rmi.RemoteException: EJB Exception:; nested exception is:
    javax.ejb.EJBException
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
    is>>>not implemented
    Start server side stack trace:
    java.rmi.RemoteException: EJB Exception:; nested exception is:
    javax.ejb.EJBException
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
    is>>>not implemented
    java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
    is
    not implemented
    at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    javax.ejb.EJBException
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
    is>>>not implemented
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:271)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    ; nested exception is:
    javax.ejb.EJBException:
    Start server side stack trace:
    java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 methodis
    not implemented
    at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    javax.ejb.EJBException
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
    is>>>not implemented
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:271)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
    is>>>not implemented>>> >>>Start server side stack trace:>>>java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method>is>>>not implemented>>>        at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)>>>        at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)>>>        at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)>>>        at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)>>>        at java.lang.reflect.Method.invoke(Native Method)>>>        at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)>>>        at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)>>>        at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)>>>        at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)>>>        at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown>>>Source)>>>        at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)>>>        at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)>>>        at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)>>>        at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)>>>        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)>>>        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)>>>End  server side stack trace>>>
    java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 methodis
    not implemented
    Start server side stack trace:
    java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 methodis
    not implemented
    at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    <<no stack trace available>>
    --------------- nested within: ------------------
    javax.ejb.EJBException:
    Start server side stack trace:
    java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 methodis
    not implemented
    at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    javax.ejb.EJBException
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
    is>>>not implemented
    at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:271)
    at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)
    at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)
    at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)
    at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    End server side stack trace
    - with nested exception:
    [java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
    is>>>not implemented>>> >>>Start server side stack trace:>>>java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method>is>>>not implemented>>>        at weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)>>>        at packbss.javatranslator.dataaccess.ComDataBean.subLoadResultset(ComDataBean.java:264)>>>        at packbss.javatranslator.dataaccess.ComDataBean.ejbCreate(ComDataBean.java:50)>>>        at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_Impl.ejbCreate(ComDataBean_vzmqkb_Impl.java:112)>>>        at java.lang.reflect.Method.invoke(Native Method)>>>        at weblogic.ejb20.manager.StatefulSessionManager.create(StatefulSessionManager.java:657)>>>        at weblogic.ejb20.manager.StatefulSessionManager.remoteCreate(StatefulSessionManager.java:705)>>>        at weblogic.ejb20.internal.StatefulEJBHome.create(StatefulEJBHome.java:142)>>>        at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl.create(ComDataBean_vzmqkb_HomeImpl.java:80)>>>        at packbss.javatranslator.dataaccess.ComDataBean_vzmqkb_HomeImpl_WLSkel.invoke(Unknown>>>Source)>>>        at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)>>>        at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)>>>        at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)>>>        at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)>>>        at weblogic.kernel.ExecuteThread.execute>>(ExecuteThread.java:139)>>>        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)>>>End  server side stack trace>>>
    <<no stack trace available>>

Maybe you are looking for

  • Tools not working in Photoshop Elements 8

    I just got PSE 8 and I've been playing around with it. I've noticed that occasionally, when I open a picture to edit and try toselect a tool from the left side, the tool graphic tself presses, but my cursor is just the little clenched hand and the to

  • Vendor balance transfors

    HI friend i have doubht ,in vendor balances updations, while tranforing vendor balances from 2009 to 2010, through f.07. some vendors are already showing some opening balance, how that vendor swill be transfor, weather we will transfor vendor balance

  • How to edit PPD List Illustrator CS3?

    Hi all, Recently updated a printer driver, which has resulted in a really long PPD list through which I have to scroll when I send something
 to print. I know in Quark there's a way that one can edit the list by turning off unwanted PPDs. Is this pos

  • Oracle Management Server logs

    Hello All, Can someone point me to where the log(s) may be?

  • HOME HUB 2 PROBLEM

    Hello All.New poster here.Am suffering HH2 wireless problems which seem to be common knowledge on these forums.My question is because ihave BTV and am considering you view do i need to replace the hub with another BT one ie HH3 or can purchase my own