Error when calling rollback on connection object

Hi,
I am using 10g client connecting to 9i database on Linux RHEL 3.0 with gcc 3.2.3
When I call connection->rollback(), (where connection is of type Connection), my application core dumps with the following error : "pure virtual method called"
I looked in occiControl.h and the method is pure virtual. However, so is the terminateStatement, but i don't have any trouble when i call that.
Any ideas?
Other api's for Connection object such as createStatement and terminateStatement work fine.
Thanks much,
Nilofer

Want to correct my previous post. Problem was not with the connection being passed as a pointer (pointers and references work the same way as far as virtual calls are concerned. Both are valid.).
Problem was with the connection object. Under certain conditions, it would get released somewhere before the call to rollback.
Thanks,
Nilofer

Similar Messages

  • Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679

    Hi,
    We update the BW landscape for version 7.4 suppport package 4 (whitout HANA).
    We use a external system connection to extract data from a SQLServer database (Microsoft Connector 1.1 for SAP/BW)
    In the previous version (BW 7.0.1 SP 10) run correctly, but now is in error.
    Below the  BW error log:
    Error: COMMUNICATION_FAILURE with function RSB_API_OHS_3RDPARTY_NOTIFY and target system SQLIS.
    Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679 Transaction program not regist).
    Error log of Integrations Services
    [SAP BI Destination 1 [476]] Error: Microsoft.SqlServer.Dts.SapBw.Connectivity.ERPException: An error occurred during the dispatch of the incoming function. The last return code was "RFC_FAILURE".
    em Microsoft.SqlServer.Dts.SapBw.Components.SapBwSourceBWLoader.ProcessInput(Int32 inputID, PipelineBuffer buffer)
    em Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostProcessInput(IDTSManagedComponentWrapper100 wrapper, Int32 inputID, IDTSBuffer100 pDTSBuffer, IntPtr bufferWirePacket)
    [SSIS.Pipeline] Error: SSIS Error Code DTS_E_PROCESSINPUTFAILED.  The ProcessInput method on component "SAP BI Destination 1" (476) failed with error code 0x80131500 while processing input "SAP BI Destination Input" (491). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running.  There may be error messages posted before this with more information about the failure.
    I checked the topic and notes below, but without success
    CPIC Return Code 679 - Transaction Program not Registered - ABAP Connectivity - SCN Wiki
    Note 1480644 - gw/acl_mode versus gw/reg_no_conn_info.
    Note 353597 - Registering RFC server programs
    Regards,
    Bruno

    Hi Bruno,
    We were able to resolve the issue. SAP RDS is assisting us with our upgrade and one of their consultants gave us this fix/workaround.
    Edit and add an entry into P:\usr\sap\<SID>\DVEBMGS00\data\reginfo.dat on your BW host server.
    Below is the entry I added.
    P TP=<NAME OF PROGRAM ID> HOST=<remote hostname where you creating the RFC to> CANCEL=<remote hostname> ACCESS=*
    P TP=CTSAPNPSCI_PORTAL_FPS HOST=ctsapnpsci CANCEL=ctsapnpsci ACCESS=*
    Then in BW system goto smgw > goto > Expert Funtions > External Security > ReRead ACL (N) & Globally
    I hope that this works for you.
    Regards
    James 

  • Error When Calling Up IGS (Error opening an RFC connection.)

    hi experts,
    i am getting error Error When Calling Up IGS (Error opening an RFC connection.)
    when i excute in wad, i checked in forums regarding this issue ,it is suggested that in check in se38--> se38->GRAPHICS_IGS_ADMIN(execute)->then it opens one more window (IGS_RFC_DEST)execute(could not reach to IGS)
    in RSRT if i execute IGS test button it is showing page cannot be displayed
    can anybody give answer for this what to do
    thanks
    venu

    Hi Venu,
    I would suggest that you contact your basis team and ask them to check the entry for the IGS in SM59.

  • RFC call failed : Error when opening an RFC connection

    Hi,
    As a result of "Start Data Collection" operation in the t-code RZ70, I have got this error.
    "RFC call failed : Error when opening an RFC connection"
    Others things are with success message.
    Regards,
    Bala Raja

    hi
    check this links
    http://help.sap.com/saphelp_nw04s/helpdata/en/9b/da0f41026df223e10000000a155106/frameset.htm
    http://help.sap.com/saphelp_nw04s/helpdata/en/9b/da0f41026df223e10000000a155106/frameset.htm
    also check Tcode: SLDAPICUST.
    run tcode SLDCHECK? any error?
    Thanks
    Rodrigo
    PS: If useful reward points

  • Error when calling getLocalSocketAddress() on for a newly created socket

    Hello,
    I have an issue when using JVM 1.5.0.12 on HP-UX (IA64N):
    java.lang.Error: java.net.SocketException: Bad file number (errno:9)
         at sun.nio.ch.Net.localAddress(Net.java:123)
         at sun.nio.ch.SocketChannelImpl.localAddress(SocketChannelImpl.java:394)
         at sun.nio.ch.SocketAdaptor.getLocalAddress(SocketAdaptor.java:147)
         at java.net.Socket.getLocalSocketAddress(Socket.java:708)
    I get this error when I accept a connection from a remote peer and I try to call getLocalSocketAddress() method on the new accepted socket connection object.
    Does anyone have an idea about the cause for this error?
    I also get 2 other errors but in different places in the code:
    1/ java.io.IOException: No buffer space available (errno:233)
         at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
         at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:145)
    This one I get when my server socket accepts a connection. But even if the connection is accepted succesfully, I might get the "java.lang.Error: java.net.SocketException: Bad file number (errno:9)" when trying to call getLocalSocketAddress()
    2/ Once I accept the new connection I call "socketChannel.socket().setTcpNoDelay(true)" but sometimes this fails with a SocketException: Invalid argument (errno:22).
    Al the 3 errors are manifesting sporadically and I cannot find the cause.

    Hello,
    Thanks for your quick response!
    We actually do something like this:
    // NIO engine build around a Selector for asynchronous IO developpement.
    public class NIOCore implements Runnable {
    private final Selector selector;
    private final Set<SelectableChannelListener> channels = new HashSet<SelectableChannelListener>();
    public void run() {
    for (final Iterator<SelectionKey> i = selector.selectedKeys().iterator(); i.hasNext();) {
    final SelectionKey selectionKey = i.next();
    i.remove();
    final SelectableChannelListener selectableChannelListener = (SelectableChannelListener) selectionKey.attachment();
    if (!selectionKey.isValid()) {
    continue;
    // Check what event is available and deal with it
    if (selectionKey.isAcceptable()) {
    if (log.isTraceEnabled()) {
    log.debug("Processing ACCEPT event for listener: " + selectableChannelListener);
    try {
    selectableChannelListener.acceptEvent();
    } catch (final Throwable t) {
    log.error("Error on ACCEPT event for listener " + selectableChannelListener, t);
    selectableChannelListener.close();
    As you ca see, we use to do a callback on our SelectableChannelListener objects. In our case the SelectableChannelListener object that actually propagates the JVM Error is this one:
    public final class Acceptor extends SelectableChannelListener {
    protected NIOCore core;
    public void acceptEvent() {
    SocketChannel socketChannel = serverSocketChannel.accept();
    if (socketChannel == null) {
    throw new NIOCoreException("No incoming connection to accept");
    // Socket options
    if (params.getSocketBufferSize() > 0) {
    socketChannel.socket().setSendBufferSize(params.getSocketBufferSize());
    try {
    socketChannel.socket().setTcpNoDelay(true);
    } catch (SocketException ex) {
    if (log.isDebugEnabled() || log.isTraceEnabled())
    log.warn(logPrefix + "could not set TCP_NODELAY socket option.You may experience performance loss", ex);
    else
    log.warn(logPrefix + "could not set TCP_NODELAY socket option. You may experience performance loss. Cause : " + ex.getMessage());
    // later if the connection is accepted succesfully this line is executed
    SocketAddress localAddress = socketChannel.socket().getLocalSocketAddress();
    @Override
    public void close() {
    core.unregister(this);
    try {
    selectableChannel.close();
    } catch (final IOException e) {
    // Ignore
    NIOPortManager.getInstance().setListenBindSapState(getBoundSAP(), true);
    So bassically when we call selectableChannelListener.close() we indeed close the ServerSocketChannel channel, but we also unregister the Acceptor observer object from NIOCore in order to free memory and set the SAP as available.
    The problem is that we cannot reproduce this issue (it reproduces only on our customers environment) and I consider rather risky to remove the selectableChannelListener.close() call.
    Actually I would catch the Error and package it in an internal runtime exception:
    SocketAddress localAddress = null;
    try {
    localAddress = socketChannel.socket().getLocalSocketAddress();
    catch (Throwable t) {
    throw new MyRunntimeException(t);
    And then to catch this new runtime exception in NIOCore class when this call is made:
    try {
    selectableChannelListener.acceptEvent();
    } catch (final MyRunntimeException e) {
    log.debug("JVM error occured!");
    } catch (final Throwable t) {
    log.error("Error on ACCEPT event for listener " + selectableChannelListener, t);
    selectableChannelListener.close();
    I know this is silly but at least we can use it as a temporary workaround until these JVM issues are fixed.
    Also since socketChannel.socket().getLocalSocketAddress() API call only throws that specific error from time to time, we could implement a retry mechanism. What I mean is to call getLocalSocketAddress() in a while loop and if the call fails with Error just continue to retry...we could provide 3 retries for example. If on the 3 ^rd^ retry the call also fails, just let it be failed and treat it in normal way.
    Best regards,
    Alex

  • Error when call RFC Function module in R/3

    Dear All,
    We are trying to call RFC function module CBIF_GLM1_PROCESS_ORDER_READ (This is not a BAPI and also not released ) in R/3 from XI system.
    we are facing the error "Error while lookup Exception during processing the payload. Error when calling an adapter by using the communication channel CC_PPPI_MES_RFC_Rcvr (Party: , Service: WCD_320, Object ID: 16563889b449328eac76caa6a3bc592e) XI AF API call failed. Module exception: 'error while processing the request to rfc-client: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: failed to parse BAPI response due to: com.sap.aii.adapter.rfc.util.bapi.BapiException: Parameter with name RETURN not found.'. Cause Exception: 'com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: failed to parse BAPI response due to: com.sap.aii.adapter.rfc.util.bapi.BapiException: Parameter with name RETURN not found.'."
    This is the first time we are doing this configuration.
    Could you please let me know what woulbe the reason.

    read the original message
    We are trying to call RFC function module CBIF_GLM1_PROCESS_ORDER_READ (This is not a BAPI and also not released ) in R/3 from XI system.
    I am talking about the above Receiver RFC channel which you guys are using to call R/3 from XI. That where you need to change the commit parameter

  • ORA-28868 error when calling Web service over HTTPS from PL/SQL utl_http

    I am getting error message ORA-28868 error when calling Web service over HTTPS from PL/SQL utl_http PL/SQL package,
    when browsed through some of the messages they point to setting Oracle Wallet Manager.
    I am trying to connect
    Any idea on how to resolve this issue ?
    your input is appreciated.
    Thanks
    Ravi

    Duplicate post ... please ignore.

  • Error when determining a number from object BI_TSDTEL and number 01

    Hi BW Experts,
    After Transporting Infosources (Master & Transaction) to BW QA, the transfer rules were not getting activated in QA. The following error message was diaplyed.
    "Error when determining a number from object BI_TSDTEL and number 01
    Object name can only contain characters from syntactical character set
    Object name can only contain characters from syntactical character set
    Data element for InfoObject KOKRS 0CO_AREA could not be created
    Data element for InfoObject KOKRS 0CO_AREA could not be created
    Transfer structure 0IM_FA_IQ_2_SB activated under the name 0IM_FA_IQ_2_SA
    It is not necessary to copy dependent objects for transfer structure 0IM_FA_IQ_2_SA
    Transfer structure 0IM_FA_IQ_2_SA does not exist
    Error RSAR 440 when handling objects with type R3TR ISTS."
    I have gone through the Note: 674818.
    Could someone clear me about BI_TSDTEl, By using this do we need to maintain object intervals manually in all the systems like BW ( Dev & QA ), R/3 (Dev & QA).
    Because  I have not seen the Intervals in R/3 ( Dev & QA) systems.
    please could someone provide Inputs for this.
    Thanks in Advance
    Regards
    SK

    Hi,
    Try to see that transfer structure is existing in the sytem which is connecting in
    the BW quality.
    You need the same to be transported from the development server of R/3 to quality server of R/3.
    Just check if this helps.
    Regards
    Rahul Bindroo

  • Error when opening an RFC connection (LB : Hostname or service of the messa

    Hi All,
    Im trying to transport datasources in BW, they are 7.x  RSDS datasources. but we did not change the source system, it was existing and we are using the same source for older BW version. we now installing new BW 7.x system.
    These  transports went fine in BQ system but failing in BP system with the below error :
    Error when opening an RFC connection (LB : Hostname or service of the message ser
    Error when activating DataSource 2LIS_17_I0NOTIF RP1CLT100
    Error when opening an RFC connection (LB : Hostname or service of the message ser
    Error when resetting DataSource 2LIS_17_I0NOTIF RP1CLT100 to the active version
    the datasource 2LIS_17_I0NOTIF is active in RP1CLT100 system. when this transport goes to prod it tries to overwrite the existing one, as there are no changes to the datasource the structure will be the same.
    but after that it cant able to activate that datasource.
    so my question is can we able to activate this datasource in RP rather than doing transport again from R/3 Dev---R/3 PRD.
    i tried RSDS_DATASOURCE_ACTIVATE_ALL but it doesn't help.
    another question is when we migrate from 3.x datasource to 7.x, does this change any metadata in R/3 system as well.
    Best Regards
    Robyn.

    Hi Rizwan,
    Looking at the error message it seems like there is some issue with RFC connection and whatever objects you are trying to move are not reaching to target system. Just have a check with basis team.
    Once you migrate DS from 3.x to 7.0 yes there will be some meta data changes e.g. the DS type will be changed from ISFS to RSDS. You will have to send the migration along with current data source.
    Regards,
    Durgesh.

  • Error when opening an RFC connection in IDT

    Hi Experts,
    I m trying to create a relational connection (JCO) from IDT to BW 7.4, and I m getting the following error:
    Error when opening an RFC connection (CPIC-CALL: ' ThSAPOCMINIT', communication
    I searched this error in Internet and I found many discussions about it ...And I think it's about autorizations in BW system that by default dosen't allow external servers to connect to it.
    So, I changed the values for the following parameters in RZ11 t-code:
    gw/acl_mode = 0
    gw/reg_no_conn_info = 0
    But I still get the same error ...When I checked the SM59 t-code I found that IDT create an entry in TCP/Ip connections ...
    Can you guide me to solve this issue...
    BW server is 7.4 version on AIX OS
    BO server is 4.1 SP05 on windows system
    Thank's a lot for your help.
    Abdess,

    Hi,
    test the RFC connection in sm59.If it is sussecfull then try to create conneciton otherwise see the error message.
    Amit

  • Error in Local Message System: Error when opening an RFC connection Message

    Hi Gurus,
    We are not able to create support messages in our ECC production system but it can created in Development and Quality. Support message created appears in solution manager system. ECC System displays error message as
    Error in Local Message System: Error when opening
    an RFC connection Message was Not Created
    I have checked RFC connection between ECC and Solution Manager which displays following message
    Logon     Connection Error
    Error Details     Error when opening an RFC connection
    Error Details     ERROR: partner "local:sapgw00' not reached
    Error Details     LOCATION: SAP-Gateway on host local / sapgw05
    Error Details     DETAIL: NiPConnect2
    Error Details     CALL: connect
    Error Details     COMPONENT: NI (network interface)
    Error Details     COUNTER: 40142
    Error Details     ERROR NUMBER: 10060
    Error Details     ERROR TEXT: WSAETIMEDOUT: Connection timed out
    Error Details     MODULE: nixxi.cpp
    Error Details     LINE: 2835
    Error Details     RETURN CODE: -10
    Error Details     SUBRC: 0
    Error Details     RELEASE: 701
    Error Details     TIME: Wed Jan 11 23:26:54 2012
    Error Details     VERSION: 38
    Kindly Help.....

    Hi
    Based on the instance number of the servers, you can determine the gateway to be used.
    IF your ECC instance number is , 01 then gateway would be , sapgw01 (in ECC system)
    So check and change the settings accordingly, in the RFC connection. Also check, if this entry sapgw01 is made in /etc/service file. Also check, in transaction smgw for gateway parameters.
    Hope this info helps,
    ~ Raj

  • JMS sender cc error: Error while calling operation 'setChannel' for object

    Hi guys,
    I'm getting following error in my sender JMS adapter which tries to connect to Websphere MQ:
    Error while calling operation 'setChannel' for object '|   com.ibm.mq.jms.MQQueueConnectionFactory
    it is then followed by connection and system parameters.
    Any idea, what could be wrong?
    I also doubt about cc's connection parameters:
    - transport network protocol: should I use TCP/IP or WebsphereMQ?
    - JMS compliant: non-JMS or JMS compliant?
    thanks for your help,
    olian

    Hi Olian,
    the configuration of a JMS adapter requires close working with the MQ team. they are best people to tell  you what is the correct parameter value.
    depending on the "transport protocol" he will be able to help you complete the configuration.
    if you have chosen "websphere MQ (non-jms)", the transport/network protocol and Jms-compliance depends on the configuration made on the network and MQ.
    Raghu

  • An error occured while opening the connection: Object reference not set to

    After I uninstalled Oracle Developer Tools for Visual Studio .NET 10.1.0.4 and installed Oracle Developer Tools for Visual Studio .NET with Oracle10g Release 2 ODAC 10.2.0.2.21 I got the error message below when I want to connect to my 10g database using Oracle Explorer.
    Error:
    An error occured while opening the connection: Object reference not set to an instance of an object
    I use OracleConnection to open also cannot be done. But I use Oracle SQL Developer I can connect to orcl that I cannot connect using ODAC 10.2.0.2.21 in my laptop.
    Please help me.
    Ming Man

    Sorry my mistake, I double checked, the one I uninstalled is ODAC 10.2.0.2.20 and not ODAC 10.1.0.4.
    But I have that error.
    Ming Man

  • 500 Internal Server Error - When calling LOV's

    I receiving the following error when calling a LOV.
    Both date LOV's and LOV's based on a foreign key fail.
    500 Internal Server Error
    OracleJSP: oracle.jsp.provider.JspCompileException:
    Errors compiling:D:\Oracle\oc4j\j2ee\home\application-deployments\ois\web\persistence\_pages\_jheadstart\_lovFrame.java
    error: Invalid class file format in C:\Program Files\Java\j2re1.4.0\lib\rt.jar(java/lang/Object.class). The major.minor version '48.0' is too recent for this tool to understand.
    D:\Oracle\oc4j\j2ee\home\application-deployments\ois\web\persistence\_pages\_jheadstart\_lovFrame.java:0: Class java.lang.Object not found in class com.orionserver.http.OrionHttpJspPage.
    package _jheadstart;
    ^
    2 errors

    Marcel,
    JDeveloper will not run out of the box with JDK 1.4. There is a help topic 'Configuring Support for JDK 1.4.0.01 in JDeveloper' that gives you some information.
    But you also need to verify the compatability of all the frameworks you use with JKD 1.4, including BC4J, MVC and UIX. E.g. the classes12.jar we normally use for a JHeadstart application only works with JKD 1.2/1.3.
    Having found out which versions of the frameworks you need, the next step is to validate whether the JHeadstart runtime classes will work with these versions. We have no experience ourself in this respect.
    If it is an option for you, you might consider to downgrade to JKD 1.3.
    Jan Kettenis

  • STMS: RFC error: Error when opening an RFC connection

    Hello ,
    I was wondering if you could help me with this TMS issue.
    The transport system is not working properly.
    The fallowing error is shown:
    Could not start transport control program tp
    RFC error: Error when opening an RFC connection
    There was an attempt to start the transport control program tp using the local RFC interface. An error occurred here.
      Error code: 3
      RFC error text: Error when opening an RFC connection
    Meaning of the error codes:
      03  RFC system failure
      04  RFC communication failure
    System Response
    The function terminates. Details about the error can be found in the trace file of the Gateway Monitor (SMGW).
    Procedure
    Contact your system administrator or use report RSTPTEST to localize the error. You can then execute the command again.
    When I test the tp tools:
    tp Call and RFC Ping: Error when opening an RFC connection
    Another thing would be that when testing the RFC connection CALLTP_Linux I have the error:
    ERROR: user XXX  is not authorized to start TP /usr/sap/SID/DVEBMGS53/exe
    And I have to say that the user has maximum authorizations.
    I also checked the permissions of the tp at OS level but everything seems to be ok.
    Can you help me with this?
    BR,
    Manoliv

    Dear Manoliv,
    Firstly please check if you have enough space in /usr/sap/trans file system.
    If OK, please run RSTPTEST report from SE38 and check the log file in SMGW => Goto => Trace => Gateways => Display file
    and paste the log here.
    Also, I assume filesystem permissions are OK.
    Regards,
    Sujit.

Maybe you are looking for