Connecting a Java Client with a VB Server (problem in recieving messages)

Hi all, i have a VB based Server through which i am trying to connect a VB Server through Sockets
The Connection is Successfull but the problem i am unable to recieve all the messages from VB Server,
but all the messages on the Server Side is coming properly, i want to know do we have a secure connection between Vb and Java

Your answer is here.

Similar Messages

  • Unable to connect the crm client with the IPC server

    Hi,
    I am unable to connect with one CRM client with the IPC server.
    my Dispatcher and all the IPC servers are working all.
    Plz helpme out.
    With thanks and Regards,
    Yusuf.

    Hi Muhammed,
    Check in the file dispatcher.properties if the RFC names are correctly maintained.
    Regards,
    Patricia
    PS Your post was in the wrong forum. I moved it to the correct one where the chance of an answer is much higher.
    Hope you understand and good luck.
    Regards,
    Patricia
    SDN Moderator

  • Interoperability: WSDL-based Java client with MS SOAP server

    Does anybody have the experience with a Java client communicating with Microsoft
    SOAP server based on the WSDL protocol? My initial experiece shows a lot of problems.
    Any information in this regard is appreciated.
    Thanks

    I'm experiencing the same sort of problem too.
    I downloaded Bea Web Service Broker in order to test some MS Soap-based web services
    before developing some Weblogic EJBs which are to use them, since both of them
    (WS Broker and Weblogic EJBs) are said to use the same underlying package of Java
    classes to access any web service.
    Most of the MS web services won't work with this tool. I have problems with remote
    methods that have one or more parameters (the remote methods seem not to get them)
    and also with some web services that raise FileNotFoundExceptions from URLs (rather
    odd to me) on the Broker, despite the fact those URLs are valid.
    Any hint or suggestion will be very appreciated.

  • How to connect Lync 2013 client with OCS 2007 R2 Edge server

    Hi,
    We have OCS 2007 R2 Edge server for external & OCS 2007 R2 FE Server for internal access in our environment.
    We able to access internally Lync2013 clients with OCS 2007R2 server, however from external we cannot access Lync2013 client with OCS2007 R2 server.
    Is there any patch or registry key trick to access OCS from lync2013 client externally? We cannot immediately migrate to Lync2013 server from OCS.
    Any help
    MD

    Hi,
    I suggest you still use OCS 2007 R2 client to login OCS 2007 R2 Server untill finishing migration to Lync Server 2013, as using Lync client with OCS 2007 R2 Server will offer a pretty limited experience.
    Here is a great blog about Lync 2010 Client unsupported with OCS, it is for Lync 2010 client but similar for Lync 2013 client:
    http://blog.schertz.name/2010/09/lync-client-unsupported-ocs/
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there.
    Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • Probelm client auth from jsse client with open ssl server

    I tried to connect jsse client with a openssl server.. with clientAuth
    This is what i did ..
    Using openssl req comand i created a X509 certificate for server and imported the same to java keystore..
    The communication works fine without client authentication.
    To enable client auth i create client private/public key pair using keytool and exported the public key to a file client.public. and used it in open ssl server .
    This is how i invoke the client ..
    java
    -Djavax.net.debug=all
    -Djavax.net.ssl.trustStore=cacerts
    -Djavax.net.ssl.trustStorePassword=changeit
    -Djavax.net.private -Djavax.net.ssl.keyStorePassword=password EchoClient
    After which i get following error in server
    SSL3 alert write:fatal:handshake failure
    SSL_accept:error in SSLv3 read client certificate B
    SSL_accept:error in SSLv3 read client certificate B
    ERROR
    17246:error:140890C7:SSL routines:SSL3_GET_CLIENT_CERTIFICATE:peer did not return a certificate:s3_srvr.c:1666:
    shutting down SSL
    CONNECTION CLOSED
    The client debug says it is recieving a certificate request.. what could be the problem.. can anybody help...

    i also have that problem. I was trying to configure SSL in apache in Win XP machine, but this error occurs. Is there anyone, who can help on it?

  • Anyone successfully set up connection pool in s1as with ms sql server 2000?

    As subject. Since I have seen a lot of posts about the NoSuchMethodException issue with various dbms providers, and the only "official information" I found thru different forums, google, different sun/javasoft sites and forums are this:
    http://sunsolve.sun.com/pub-cgi/retrieve.pl?doc=fsunone%2F8172&zone_32=NoSuchMethodException&wholewords=on
    Which is wonderfully vague and provide not-so-much useful information...
    As for the information and suggestion posted by other forum members, most or all of them have experience with setting up Oracle, DB2, mySQL, etc., not aimed for MS SQL Server 2000 (you may think, I am just asking for it running MS SQL server with Java... oh well, not my choice)
    I still haven't seen any positive feedbacks on how this exception was caused and how to resolve it. I have literally exhausted all leads on how to fix this issue, so right now I'm only interested to know whether anyone in the forum actually have a successful connection pool set up with MS SQL server 2000.
    My platform:
    w2k sp3
    SunOne app server, update1, JDK 1.4.1
    latest MS SQL 2000 JDBC driver
    This fails with the NoSuchMethodException error:
    try {
    InitialContext ic = new InitialContext();
    DataSource ds = (DataSource) ic.lookup("test_db");
    con = ds.getConnection();
    System.out.println( "con is created -> " + con );
    } catch (Exception ex) {
    System.out.println( "failed -> " + ex.getMessage() );
    This works just fine:
    try {
    Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
    con = DriverManager.getConnection("jdbc:microsoft:sqlserver://xxx.xxx.xxx.xxx:1433;DatabaseName=testdb;SelectMethod=cursor", "username", "password");
    System.out.println( "con is created -> " + con );
    } catch (Exception ex) {
    System.out.println( "failed is fucked -> " + ex.getMessage() );
    thanks,
    --kuan

    Hi,
    Thanks for pointing out that article, I did not find it previously. After following the directions in the artile and your advise, now dbping seems to be able to connect to SQL server.
    Thank you very much.
    --kuan                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • Connect webdynpro callable object with ms sql server 2000

    Hi all
    how connect webdynpro callable object with ms sql server 2000?
    How can I register on the portal as an additional connection?
    thank you very much!

    Thanks for your answers, Now I have the following problem, to develop this code:
    try {
              InitialContext iC = new InitialContext();
              DataSource dataSource = (DataSource)iC.lookup("jdbc/ConnectionAlias");
              Connection con = dataSource.getConnection();
              java.sql.Statement stmt = con.createStatement();
              ResultSet rs = stmt.executeQuery("select * from ejemplo");
              while (rs.next()){
                   com.sap.test.sql.testsql.wdp.IPrivateTestIViewView.IDatosElement
                                                             DatosElement =
                                                             wdContext.nodeDatos()
                                                             .createDatosElement();
                   DatosElement.setId(rs.getString("id"));
                   DatosElement.setNom(rs.getString("nom"));
                   DatosElement.setNum(rs.getInt("num"));
         }catch (SQLException e) {
              wdContext.currentContextElement().setB(e.getMessage());
         }catch (Exception e){
              wdContext.currentContextElement().setB(e.getMessage());
    and shows me the following exception
    ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException thrown by the physical connection: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
    the data that you place in the visual administrator were:
    Drivers: com.sap.aii.af.jmsproviderlib (msutil.jar , mssqlserver.jar , msbase.jar)
    DataSources: sap.com/JDBCConnector_MyDatasource.xml
                   Name: MyDatasource
                   Alias: ConnectionAlias
                   DriverName: com.sap.aii.af.jmsproviderlib
                   JDBC Version: 1.x
                   Driver Class: com.microsoft.jdbc.sqlserver.SQLServerDriver
                   Database URL: jdbc:microsoft:sqlserver://181.42.101.219:1433;DatabaseName=test
                   User: sa
                   Password: abcd1234
    did not know the cause of the problem
    thanks!

  • Connect one Business system with two Integration Server

    Hello,
    Can we able to connect one Business System with two Integration Server?
    I have one Business system (ECC 6.0 with the client 900) and it is already connected with PI 7.0 system.Can I able to connect the same sytem (with same client) with PI7.1?
    I want to do the HTTP Connection for ABAP Proxy for this two XI system with one business Sytem ?
    Is this possible ?Is there any work around solution there?
    Thanks.

    Hello ,
    This document describes about connecting with Two PI7.1 system using Application Server 7.1 and Application Server 7.0 SP14  .
    I want to connect same ECC system via abap proxy with two different PI system .One is PI7.0 and another one is PI7.1 system.
    Is this possible if i use Application Server 7.1 or Application Server 7.0 SP14  ?
    Thanks.
    Lakshmi
    Edited by: Muthulakshmi Pandi on Apr 16, 2009 11:48 PM
    Edited by: Muthulakshmi Pandi on Apr 17, 2009 12:21 AM

  • JMX Connectivity has been discontinued with the managed server

    Dear all,
    I am getting following msg in my weblogic 11g manage server and admin server.
    Namage Server Log
    ####<Nov 22, 2010 2:15:39 PM IST> <Warning> <Log Management> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290415539687> <BEA-170011> <The LogBroadcaster on this server failed to broadcast log messages to the admin server. The Admin server may not be running. Message broadcasts to the admin server will be disabled.>
    Admin Server Log
    ####<Nov 22, 2010 2:13:35 PM IST> <Info> <JMX> <NewTradeServer> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290415415015> <BEA-149507> <JMX Connectivity has been discontinued with the managed server NewTradeServer.>
    ####<Nov 22, 2010 2:13:35 PM IST> <Info> <Server> <NewTradeServer> <AdminServer> <[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290415415015> <BEA-002634> <The server "NewTradeServer" disconnected from this server.>
    ####<Nov 22, 2010 2:51:32 PM IST> <Info> <Server> <NewTradeServer> <AdminServer> <[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417692374> <BEA-002635> <The server "NewTradeServer" connected to this server.>
    During this time my admin server in running, i can able to loggin to admin server console,
    Problem which i am faceing is that, i am not able to see the server status of that particular
    manage server, i am not able to see the any sub tabs statistic in Monitoring TAB of manage server, and after 1/2 and hours the manage server stop responding, then i restart the manage server and after that every thing work fine..
    any one have the solution for this error????///
    Regds
    Amar Shaw

    Kindly fing the log for the server problem time.
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 122.177.97.179:21,557 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 117.206.128.110:1,069 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 203.123.173.169:50,920 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 59.180.84.228:50,902 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 120.61.132.164:1,297 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 122.166.48.41:21,631 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 125.22.34.38:39,481 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 113.193.25.104:52,294 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 172.17.1.122:18,934 during the configured idle timeout of 5 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 115.241.80.244:24,575 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 196.15.16.20:38,791 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 202.65.136.252:4,055 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 80.239.242.168:46,777 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 110.227.109.138:64,362 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 59.93.223.187:1,046 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 114.30.77.228:50,110 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 122.164.238.6:1,935 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 192.20.251.68:41,430 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 195.189.142.85:51,932 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 180.150.250.17:3,974 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 82.178.3.115:11,545 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 125.21.153.192:7,902 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 59.177.2.33:50,437 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 117.201.90.244:5,725 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 220.227.95.145:17,067 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 115.248.137.70:33,786 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 172.17.1.121:6,260 during the configured idle timeout of 5 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 59.93.55.98:6,387 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 122.162.145.253:1,603 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 80.239.242.168:46,443 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 120.61.132.164:1,298 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:09 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417549593> <BEA-000449> <Closing socket as no data read from it on 121.243.135.163:2,342 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 117.202.130.167:1,451 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 204.194.141.28:15,387 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 180.215.198.169:2,108 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 180.150.250.17:40,204 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.93.168.80:1,044 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 117.241.82.55:50,090 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.93.134.134:1,079 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 122.162.69.77:4,185 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 155.56.68.217:60,708 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 121.245.188.43:1,262 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 125.17.188.19:45,490 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 122.165.58.249:49,239 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 61.17.215.126:4,085 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 124.125.27.11:2,992 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 172.17.1.121:7,639 during the configured idle timeout of 5 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 61.246.47.199:2,426 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 122.169.70.18:14,392 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.144.98.242:42,408 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 117.197.237.98:51,852 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.163.89.69:64,984 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 192.20.246.168:13,547 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.144.98.242:37,198 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.144.98.242:39,842 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 117.202.130.167:1,450 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.90.72.203:3,972 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 155.56.68.217:58,671 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 59.93.168.80:1,043 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 122.163.163.25:1,957 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 115.240.50.203:1,059 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 203.197.42.2:34,187 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 203.124.135.246:21,650 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 93.186.23.240:11,235 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 172.17.1.133:4,215 during the configured idle timeout of 5 secs>
    ####<Nov 22, 2010 2:49:14 PM IST> <Warning> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '91' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417554593> <BEA-000449> <Closing socket as no data read from it on 122.161.99.67:20,466 during the configured idle timeout of 25 secs>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <WebLogicServer> <NewTradeServer> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1290417576578> <BEA-000000> <WebLogic Server "NewTradeServer" version:
    WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 Copyright (c) 1995, 2009, Oracle and/or its affiliates. All rights reserved.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Notice> <Log Management> <NewTradeServer> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1290417576703> <BEA-170019> <The server log file D:\BEA11G\user_projects\domains\IndiabullsWLS\servers\NewTradeServer\logs\NewTrade_%yyyy%_%MM%_%dd%_%hh%_%mm%.log is opened. All server side log events will be written to this file.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Log Management> <NewTradeServer> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1290417576718> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Diagnostics> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576812> <BEA-320001> <The ServerDebug service initialized successfully.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "t3" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "t3s" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "http" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "https" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "iiop" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "iiops" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "ldap" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576906> <BEA-002622> <The protocol "ldaps" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576921> <BEA-002622> <The protocol "cluster" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576921> <BEA-002622> <The protocol "clusters" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576921> <BEA-002622> <The protocol "snmp" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576921> <BEA-002622> <The protocol "admin" is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576921> <BEA-002624> <The administration protocol is "t3s" and is now configured.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <RJVM> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576937> <BEA-000570> <Network Configuration for Channel "NewTradeServer"
    Listen Address          172.17.1.134:80
    Public Address          N/A
    Http Enabled          true
    Tunneling Enabled     false
    Outbound Enabled     false
    Admin Traffic Enabled     true>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <RJVM> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576937> <BEA-000570> <Network Configuration for Channel "NewTradeServer"
    Listen Address          172.17.1.134:443 (SSL)
    Public Address          N/A
    Http Enabled          true
    Tunneling Enabled     false
    Outbound Enabled     false
    Admin Traffic Enabled     true>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Server> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576968> <BEA-002609> <Channel Service initialized.>
    ####<Nov 22, 2010 2:49:36 PM IST> <Info> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417576999> <BEA-000406> <NTSocketMuxer was built on Jan 24 2006 20:40:35
    >
    ####<Nov 22, 2010 2:49:37 PM IST> <Info> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417577078> <BEA-000436> <Allocating 4 reader threads.>
    ####<Nov 22, 2010 2:49:37 PM IST> <Info> <Socket> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417577078> <BEA-000446> <Native IO Enabled.>
    ####<Nov 22, 2010 2:49:37 PM IST> <Info> <IIOP> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417577281> <BEA-002014> <IIOP subsystem enabled.>
    ####<Nov 22, 2010 2:49:38 PM IST> <Info> <Security> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417578718> <BEA-000000> <Starting OpenJPA 1.1.1-SNAPSHOT>
    ####<Nov 22, 2010 2:49:38 PM IST> <Info> <Security> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417578796> <BEA-000000> <StoreServiceImpl.initJDO - StoreService is initialized with Id = ldap_KNcrxQIcWPsGUMqWWNL3mWV+Tkc=>
    ####<Nov 22, 2010 2:49:39 PM IST> <Info> <Security> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417579203> <BEA-090516> <The Authorizer provider has preexisting LDAP data.>
    ####<Nov 22, 2010 2:49:39 PM IST> <Info> <Security> <NewTradeServer> <NewTradeServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290417579390> <BEA-000000> <Parsing class "com.bea.common.security.store.data.Top".>
    ####<Nov 22, 2010 2:49:39 PM IST> <Info> <Securit

  • Advantages and Disadvantages of Using Oracle 7 Client with Oracle 9 Server

    Hello,
    I was wondering what are the advanatges of using Oracle 7 client with Oracle 9 Server versus using Oracle 9 Client with Oracle 9 server.

    Some years ago I used 7.3 Client with 9i DB, and I don't remember of particular problems, but I'm speaking of Sql*Plus only. Are there specific problems ?
    Of course the best thing is to install one 9i Client (did you already do it ?) : if there are same problems, then that's not compatibility issue.
    And what are advantages of using 9 Client with 9 server other than 7 is no longer supported.You're sure you won't have compatibility problems.
    If you have access to Metalink have a look at [url http://metalink.oracle.com/metalink/plsql/ml2_documents.showFrameDocument?p_database_id=NOTE&p_id=207303.1]Note 207303.1

  • Managing 10.4 clients with 10.5 Server

    Before I jump in....any feedback on managing 10.4 clients with 10.5 server (will post the vice-versa in the 10.4 server forum) from those who are doing it currently?
    Thanks,
    k

    I checked out the link you mentioned. It's really dealing w/ managing the client. I'm have weird issues w/ clients logging in. Today I had a grade level try to log in. Ten of the computers would let that grade level in, two would not. Of the Ten computers approx 5 wouldn't let them log in the first time, but once they were restarted they were able to log in. All of the computers are on a wired network as well as a wireless backup. Of the two that would not let them login I had just restored one and set the settings up the same as the others.
    I'll be damned, this is the weirdest I have had with Apple client management.

  • Syclo : Error in connecting Work Manager Client with Agentry Server

    Hi,
    Can somebody please shed some light on work manager client-server connections? I have downloaded the "SAP_WORK_MANAGER_BY_SYCLO_5.2" package from market place and set up the Work Manager server. It can successfully connect to the SAP back-end. Environment variables are correctly set too. However, I'm failing to connect to the Work Manager server from the Work Manager clients. I have tried from the Win32 & Android clients both.
    For Win32 client, the error I'm getting is:
    For Android, I can't even see the server instance, although it's running (it shows up while attempting to connect from Win32). Error:
    When I attempt to connect from Work Manager client to the server, it asks for username/password and for Android client it asks for Agentry user id and password. Aren't these username/password of the server where my Work Manager (Agentry) server is installed?
    Also, the "Agentry Development Server" which has been set to run as a service runs with Administrative privileges.
    I followed this: http://wiki.scn.sap.com/wiki/display/SAPMOB/Agentry+error+Client+Receiving+RFC+ERROR+LOGON+FAILURE+incomplete+logon+Data+when+connecting+to+server
    It didn't help. Please let me know where I'm going wrong?
    Tags edited by: Michael Appleby

    Hi Michael,
    I can login to SAP backend using the credentials mentioned in JavaBE.ini file.
    Please take a look at the JavaBE.ini:
    [HOST]
    server=<SAP server host name>
    ;  mobile application name configured in sap like SMART_WORK_MANAGER_51, SMART_CUSTOMER_SERVICE_10, SMART_ISU_WORK_MANAGER_10...etc
    APPNAME=SMART_WORK_MANAGER_52
    [CONFIG]
    ;  Used to get the SAP Configutaions from SAP if source=SAP or from JavaBE ini file
    ;  SAP Configurations are [ENABLE_TABLE], [TABLE_CHECK], [TABLE_REFRESH], [BAPI_WRAPPER],
    ;  [SAPOBJECT], [CT_SAPOBJECT], [CT_BAPI_WRAPPER], [CT_RETURN_TABLE], [CT_DELETE_TABLE].....etc
    source=SAP
    [TEST_LOGON]
    UID=
    UPASSWORD=
    UGUID=
    SERVERSERIALNUM=
    ;  Service login user is used to get the SAP Configutaions from SAP if source=SAP
    ;  Set ENABLED=true if source=SAP or ENABLED=false if source=INI
    ;  If ENABLED=true, set the UID, UPASSWORD and SERVERSERIALNUM
    ;  SERVERSERIALNUM is the Agentry server serial number
    [SERVICE_LOGON]
    ENABLED=true
    UID=<SAP backend username>
    UPASSWORD=<SAP backend password>
    UPASSWORDENCODED=false
    SERVERSERIALNUM=AVKNN@NILKGGBTLD
    [PUSH_LOGON]
    ENABLED=false
    UID=
    UPASSWORD=
    UPASSWORDENCODED=false
    SHAREDCONNECTION=10
    [CLIENT_NUM]
    CLIENT=720
    ;CLIENT=010
    [SYSTEM_NUM]
    ;SYSNUM=33
    SYSNUM=00
    [LANGUAGE]
    LANG=EN
    [LOGGING]
    ;1=Fatal, 2=Error, 3=Warning, 4=Info, 5=debug, 6=trace
    Level=4
    [LOGON_METHOD]
    ;  USER_AUTH if standard UID/Password authentication is used
    ;  USER_AUTH_GLOBAL if pooled connections using single UID/Password is used
    ;  USER_AUTH_GROUP if UID/Password authentication with SAP Message Server
    ;   (load balancing) is used
    LOGON_METHOD=USER_AUTH
    [GLOBAL_LOGON]
    ;  referenced when LOGON_METHOD=USER_AUTH_GLOBAL
    ;  uses a pool of connections to the SAP backend all utilizing a single
    ;    UID/password
    UID=
    UPASSWORD=
    SHAREDCONNECTION=100
    [GROUP_LOGON]
    ;  referenced when LOGON_METHOD=USER_AUTH_GROUP
    ;  individual user authentication using an SAP Message Server which distributes
    ;  client connections among a "group" of SAP application servers based on load
    ;  balancing criteria
    ;  host name or IP address of SAP Message Server
    MESSAGE_SERVER=
    GROUP_NAME=
    SYSTEM_ID=
    CLIENT=
    [REQUIRED_BAPI_WRAPPER]
    com.syclo.sap.bapi.LoginCheckBAPI=/SYCLO/CORE_SUSR_LOGIN_CHECK
    com.syclo.sap.bapi.RemoteUserCreateBAPI=/SYCLO/CORE_MDW_SESSION1_CRT
    com.syclo.sap.bapi.RemoteParameterGetBAPI=/SYCLO/CORE_MDW_PARAMETER_GET
    com.syclo.sap.bapi.SystemInfoBAPI=/SYCLO/CORE_SYSTINFO_GET
    com.syclo.sap.bapi.ChangePasswordBAPI=/SYCLO/CORE_SUSR_CHANGE_PASSWD
    com.syclo.sap.bapi.CTConfirmationBAPI=/SYCLO/CORE_OUTB_MSG_STAT_UPD
    com.syclo.sap.bapi.DTBAPI=/SYCLO/CORE_DT_GET
    com.syclo.sap.bapi.GetEmployeeDataBAPI=/SYCLO/HR_EMPLOYEE_DATA_GET
    com.syclo.sap.bapi.GetUserDetailBAPI=/SYCLO/CORE_USER_GET_DETAIL
    com.syclo.sap.bapi.GetUserProfileDataBAPI=/SYCLO/CORE_USER_PROFILE_GET
    com.syclo.sap.bapi.PushStatusUpdateBAPI=/SYCLO/CORE_PUSH_STAT_UPD
    com.syclo.sap.bapi.RemoteObjectCreateBAPI=/SYCLO/CORE_MDW_USR_OBJ_CRT
    com.syclo.sap.bapi.RemoteObjectDeleteBAPI=/SYCLO/CORE_MDW_USR_OBJ_DEL
    com.syclo.sap.bapi.RemoteObjectGetBAPI=/SYCLO/CORE_MDW_SESSION_GET
    com.syclo.sap.bapi.RemoteObjectUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD
    com.syclo.sap.bapi.RemoteReferenceCreateBAPI=/SYCLO/CORE_MDW_USR_KEYMAP_CRT
    com.syclo.sap.bapi.RemoteReferenceDeleteBAPI=/SYCLO/CORE_MDW_USR_KEYMAP_DEL
    com.syclo.sap.bapi.RemoteReferenceGetBAPI=/SYCLO/CORE_MDW_SESSION_GET
    com.syclo.sap.bapi.RemoteReferenceUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD
    com.syclo.sap.bapi.RemoteSessionDeleteBAPI=/SYCLO/CORE_MDW_SESSION1_DEL
    com.syclo.sap.bapi.RemoteUserDeleteBAPI=/SYCLO/CORE_MDW_SESSION1_DEL
    com.syclo.sap.bapi.RemoteUserUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD
    com.syclo.sap.bapi.TransactionCommitBAPI=WFD_TRANSACTION_COMMIT
    com.syclo.sap.bapi.SignatureCaptureBAPI=/SYCLO/CS_DOBDSDOCUMENT_CRT
    I haven't yet installed ATE and tested out any application. I just want my connections to be perfect, first.
    I have a question. Are the credentials used to connect Work Manager client to the server, same as the SAP backend credentials or are they the credentials of the host on which the Work Manager server is installed?
    I have tried logging in using the SAP credentials also. But that results in error too.
    These credentials are valid for SAP backend and successfully logs onto it and also responds correctly to connectTest.bat. However, I think this error is logical because these are the credentials for SAP backend and not the server where Work Manager server is hosted.

  • How to use standalone java client with an enterprise bean in J2EE 1.4

    Hi All,
    I am have deployed a stateless session bean in Sun's J2EE 1.4 Application Server. i am trying to call the bean using a standalone java client. but the client cannot access the bean.
    The error coming is:
    Jan 21, 2004 7:48:27 PM com.sun.corba.ee.impl.legacy.connection.SocketFactoryCo
    nectionImpl <init>
    WARNING: ORBUTIL.connectFailure
    org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
    at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(
    RBUtilSystemException.java:1739)
    at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(
    RBUtilSystemException.java:1757)
    at com.sun.corba.ee.impl.legacy.connection.SocketFactoryConnectionImpl.
    init>(SocketFactoryConnectionImpl.java:74)
    at com.sun.corba.ee.impl.legacy.connection.SocketFactoryContactInfoImpl
    createConnection(SocketFactoryContactInfoImpl.java:88)
    at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.begi
    Request(CorbaClientRequestDispatcherImpl.java:146)
    at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(Corba
    lientDelegateImpl.java:121)
    at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaCli
    ntDelegateImpl.java:212)
    at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
    at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.jav
    :69)
    at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.ja
    a:58)
    at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:12
    at javax.naming.InitialContext.lookup(InitialContext.java:347)
    at StatelessSessionClient.main(StatelessSessionClient.java:17)
    Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection re
    used: connect
    at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSoc
    etFactory.java:390)
    at com.sun.corba.ee.impl.legacy.connection.SocketFactoryConnectionImpl.
    init>(SocketFactoryConnectionImpl.java:58)
    ... 10 more
    Caused by: java.net.ConnectException: Connection refused: connect
    at sun.nio.ch.Net.connect(Native Method)
    at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:457)
    at java.nio.channels.SocketChannel.open(SocketChannel.java:146)
    at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSoc
    etFactory.java:381)
    ... 11 more
    javax.naming.CommunicationException: Can't find SerialContextProvider
    at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.ja
    a:66)
    at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:12
    at javax.naming.InitialContext.lookup(InitialContext.java:347)
    at StatelessSessionClient.main(StatelessSessionClient.java:17)
    Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed
    No
    at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(
    RBUtilSystemException.java:1739)
    at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(
    RBUtilSystemException.java:1757)
    at com.sun.corba.ee.impl.legacy.connection.SocketFactoryConnectionImpl.
    init>(SocketFactoryConnectionImpl.java:74)
    at com.sun.corba.ee.impl.legacy.connection.SocketFactoryContactInfoImpl
    createConnection(SocketFactoryContactInfoImpl.java:88)
    at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.begi
    Request(CorbaClientRequestDispatcherImpl.java:146)
    at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(Corba
    lientDelegateImpl.java:121)
    at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaCli
    ntDelegateImpl.java:212)
    at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
    at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.jav
    :69)
    at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.ja
    a:58)
    ... 3 more
    Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection re
    used: connect
    at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSoc
    etFactory.java:390)
    at com.sun.corba.ee.impl.legacy.connection.SocketFactoryConnectionImpl.
    init>(SocketFactoryConnectionImpl.java:58)
    ... 10 more
    Caused by: java.net.ConnectException: Connection refused: connect
    at sun.nio.ch.Net.connect(Native Method)
    at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:457)
    at java.nio.channels.SocketChannel.open(SocketChannel.java:146)
    at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSoc
    etFactory.java:381)
    ... 11 more
    My java client uses the following code to access the bean:
    Hashtable props = new Hashtable();
    String URL="iiop://localhost:3700";
    props.put("java.naming.factory.initial","com.sun.jndi.cosnaming.CNCtxFactory");
    props.put("java.naming.provider.url", URL) ;
    InitialContext ctx = new InitialContext();
    Object ref = ctx.lookup("ejb/StatelessSessionHome");
    StatelessSessionHome home = (StatelessSessionHome)PortableRemoteObject.narrow(ref,StatelessSessionHome.class);
    StatelessSessionRemote statelessSession = home.create();
    plz help me to locate the error.
    Regards,
    Mohit

    Hi Amol,
    thanks for your suggestion.
    i have deployed the converter application in J2EE1.4 tutorial in Sun AppServer J2EE1.4. the deployment process works smoothly. but accessing the deployed converter bean using standalone client as given in the tutorial gives the following error.
    Caught an unexpected exception!
    javax.naming.NoInitialContextException: Need to specify class name in environmen
    t or system property, or as an applet parameter, or in an application resource f
    ile: java.naming.factory.initial
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
    40)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243
    at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.jav
    a:280)
    at javax.naming.InitialContext.lookup(InitialContext.java:347)
    at ConverterClient.main(ConverterClient.java:14)
    I have set the InitialHost and InitialPort as suggested by you in the client code. the client gets successfully compiled but gives error when executed.
    The client code is:
    import javax.naming.Context;
    import javax.naming.InitialContext;
    import javax.rmi.PortableRemoteObject;
    import java.math.BigDecimal;
    public class ConverterClient {
    public static void main(String[] args) {
    System.setProperty("org.omg.CORBA.ORBInitialHost","localhost");
    System.setProperty("org.omg.CORBA.ORBInitialPort","3700");          
    try {
    Context initial = new InitialContext();
    Object objref = initial.lookup
    ("java:comp/env/ejb/SimpleConverter");
    ConverterHome home =
    (ConverterHome)PortableRemoteObject.narrow(objref,
    ConverterHome.class);
    Converter currencyConverter = home.create();
    BigDecimal param = new BigDecimal ("100.00");
    BigDecimal amount =
    currencyConverter.dollarToYen(param);
    System.out.println(amount);
    amount = currencyConverter.yenToEuro(param);
    System.out.println(amount);
    System.exit(0);
    } catch (Exception ex) {
    System.err.println("Caught an unexpected exception!");
    ex.printStackTrace();
    Please suggest so that i can run the standalone client successfully.
    Regards,
    Mohit Kapoor

  • Oracle 8i client with oracle 9i server

    hi friends..
    i have oracle 8i server and clients..my oracle 8i server crashed.
    so i am planning to install oracle 9i server.
    will i be able to connect oracle 8i clients on to oracle 9i server? is there any procedure for getting this connection.?
    Please help

    Look up the documentation for questions like this, under 'backwards compatibility'
    You can't configure a client to work with a higher release, it works or it doesn't work.
    This one will work.
    Sybrand Bakker
    Senior Oracle DBA
    Experts: those who wave their head at newbies not reading anything and yet continue to use desupported trash.

  • Connect Oracle 9 client from windows 2012 server to 9.0 oracle database

    I have windows 2012 64 bit with installed oracle 9.0 32 bit client
    and i want to connect to oracle 9.0 64 bit server installed on windows 2003 R2 64 bit
    Is it possible to make this connection because when i have tried to connect received this error ORA-06413 connection is not open

    942609 wrote:
    I know that oracle client 9.2.0 is too old but company about i work have tests which run on this systemIf you are stuck using antiquated versions of software, the company really ought to stick to antiquated versions of the operating system as well. Trying to combine versions of the Oracle client that weren't even certified on Windows 2003 with a bleeding edge Windows 2012 system is a recipe for pain and suffering. Even if you appear to get things working, there are any number of bugs that will likely crop up over time due to the massive version incompatibility.
    If i understood right i can't make connection between oracle 9.2.0 32 bit client installed on windows 2012 to connect to oracle server 10 i?As others have pointed out, you probably can though you'll need to change the firewall rules. As others have stated, the firewall changes you'll need to make should probably be the same for a 9.2 client and a 10.2 client. But if you're determined to work with highly unsupported combinations of software, you're likely to have to embrace the idea that you're going to be blazing some new trails and that you'll have to spend a decent amount of time debugging issues that arise from your very unique combination.
    Justin

Maybe you are looking for

  • MBP Unibody and Mini DisplayPort to S-video adapter

    Why is the Mini DisplayPort-to-s-Video Adapter the only adapter that Apple can't seem to make? My late model PowerBook G4 came with its own S-Video out, which was perfect for running video to the dual overhead projectors in my Sunday School class. Bu

  • Bluetooth not working in Windows 7 x64

    Hi, My MBP is primarily used as a Windows 7 x64 box. Up until a couple of days ago, I've been using a bluetooth Logitech mouse and pairing with my iPhone without any problems. Two days ago, the mouse simply stopped working and I now cannot detect any

  • Problems in SQL Connection from Java program to Oracle 8.1.7

    Hi, I am java program that connects to Oracle 8.1.7 . Client: java code on Windows 2000 Server: oracle 8.1.7 on Solaris Java code uses two types of Connection Pools. One Pool uses "thin" connections and other pool uses "OracleConnectionPoolDataSource

  • Call function destination XI exception

    Hello, in R3 i call to function in XI, it's follow: call function 'XXX' --destination 'XI' --exporting AA = aa --importing BB = bb --exceptions system_failure = 1 communication_failure = 2 other = 3 when this call produce a exception, why sometimes I

  • Time Machine will not back up after updating from 10.2 to 10.3

    This just started yesterday so it has to be due to the update. The following error message is given in the Time Machine settings: The backup disk needs 257.55 GB for the backup but only 234.84 GB are available. Select a larger backup disk or make the