SQLException - Connection Reset (OLAP JAVA API)

hi,
when trying to get the rootschema of the MetaDataProvider I receive this error:
java.sql.SQLException: Connection reset at
MdmMetadataProvider.getRootSchema();
Can anybody help me?
thanks

Akram,
Basically you need to set up death detection for the JDBC drivers. Please post this on the JDBC forum.
Deepak

Similar Messages

OLAP JAVA API - JDev

hi all!
i want to develop an olap application with JDeveloper and i´ve followed the steps of the tutorials on bibeans tech site (create and format bi objects). Now i´ve got a graph and a crosstab formatted etc. which i can show in JDeveloper.
My question: is it possible to produce the crosstab and graph with the java graph api on my own or to get the java-code behind the produced crosstab/graph? First of all is there a java code behind?
I´ve recognized the oracle.dss.* package but i can´t find a api guide or sth. like that on the oracle site...
Can anyone help me?
greetz pm

As far as I know there isn't any detailed guid or help doc. The best you can get is the help doc inside JDeveloper.
To answer your question, yes its possible to create presentations using java api.
There are some code fragments inside of the help doc - but its very minimal - you have to find your way through it!!
For a web app - you could use a combination of bi bean tags (for std. features ) & java API ( for any customaization if neded) .
EG: Use the presentation tag to build the presentation in a JSP
And then add some custom java code inside if needed for any customization...
<%
Presentation crossTab = (Presentation)pageContext.findAttribute("MyWorkspace_pres1");
ThinCrosstab thinCrosstab = (ThinCrosstab)crossTab.getView();
DataDirector dd = thinCrosstab.getModel().getDataDirector();
DataAccess da = thinCrosstab.getModel().getDataAccess();
%>
Good Luck!

How do I resolve connection error with Java API listener?

I have created a listener using the new Java API (see How do I implement a listener using new MDM Java API? for background). When I run it, I get this error message
Mar 19, 2008 3:57:58 PM com.sap.mdm.internal.net.ConnectionImpl finalize
INFO: Disconnect was not called. Cleaning up connection in finalize.
This message is triggered whenever I generate a data event that I would otherwise expect to be captured and handled by the listener. I have tried a number of things, including setting the connection to NO_TIMEOUT and trying SimpleConnection versus ConnectionPool, but always with the same result.
Here is some sample code for the listener:
public class DataListenerImpl implements DataListener {
     public void recordAdded(RecordEvent evt) {
          System.out.println("===> Record Added Event");
          System.out.println(evt.getServerName());
     public void recordCheckedIn(RecordEvent evt) {
          System.out.println("===> Record Checked In Event");
          System.out.println(evt.getServerName());
     public void recordCheckedOut(RecordEvent evt) {
          System.out.println("===> Record Checked Out Event");
          System.out.println(evt.getServerName());
     public void recordModified(RecordEvent evt) {
          System.out.println("===> Record Modified Event");
          System.out.println(evt.getServerName());
And here is the code for the Event Dispatcher:
public void execute(Repository repository) {
     DataListener listener = new DataListenerImpl();
     try {
          EventDispatcherManager edm = EventDispatcherManager.getInstance();
          EventDispatcher ed = edm.getEventDispatcher(repository.getServer().getName());
          ed.addListener(listener);
          ed.registerDataNotifications(SystemProperties.getUserName(), SystemProperties.getPassword(),
                    repository.getIdentifier(), repository.getLoginRegion());
          ed.registerRepositoryNotifications(SystemProperties.getUserName(), SystemProperties.getPassword(),
                    repository.getIdentifier());
          ed.registerGlobalNotifications();
          while (true) {
               Thread.yield();
               try {
                    Thread.sleep(1500);
               } catch (InterruptedException ex) {
                    System.out.println("Interrupted Exception: " + ex.getMessage());
     } catch (ConnectionException e) {
          e.printStackTrace();
     } catch (CommandException e) {
          e.printStackTrace();
Has anyone else encountered this message? Could it be related to a TCP configuration on the server? Or is this a bug in the Java API?
As I mentioned in the forum posting linked to above, I have not encountered this problem with the MDM4J API.
Any help is greatly appreciated.

I resolved it. We are switching over to SP6, Patch 1 and the listener code works fine with this version of the Java API.
Just one thing to note, though: make sure that you register data notifications through MetadataManager in your initialization code:
metadataManager.registerDataNotifications(userSessionContext, repositoryPassword);
For information on the changes to the SP6 Java API, especially with regard to connecting to MDM with the UserSessionContext, please review Richard LeBlanc's [presentation|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/20073a91-3e8b-2a10-52ae-e1b4a10add1c].

OLAP Java API: NullPointerException at MdmMetadataProvider. init

Hi there,
I'm using a Oracle9i R2 (9.2.x) db server with OLAP extension and like to write a client application with the OLAPI. When following the programming instruction from the API guide and running a simple program, a connection can be established, but a NullPointerException occured when calling ExpressDataProvider.getDefaultMetadataProvider.
Does anybody know more about this?
By the way: Don't exist there any OLAP services with Release 2 anymore? I couldn't find any hint... Possibly, they are included in the db services?

I am too having the same problem. Please, does anyone has a solution?? Here is my stack trace (well the important part of it anyways):
Cannot create the MDM metadata provider. oracle.express.ExpressServerExceptionError class: Unknown Error
Server error descriptions:
INI: A system failure occurred., Generic at TxsOqConnection::getDefaultDatabase
oracle.express.ExpressServerExceptionError class: Unknown Error
Server error descriptions:
INI: A system failure occurred., Generic at TxsOqConnection::getDefaultDatabase
     at oracle.express.olapi.data.full.ExpressDataProvider.getMetadataProviderInterface(ExpressDataProvider.java:1164)
     at oracle.olapi.metadata.MetadataFetcher.initialize(MetadataFetcher.java:79)
     at oracle.olapi.metadata.MetadataFetcher.<init>(MetadataFetcher.java:51)
     at oracle.olapi.metadata.BaseMetadataProvider.<init>(BaseMetadataProvider.java:59)
     at oracle.olapi.metadata.mdm.MdmMetadataProvider.<init>(MdmMetadataProvider.java:144)
     at oracle.express.olapi.data.full.ExpressDataProvider.getDefaultMetadataProvider(ExpressDataProvider.java:1125)

Java.sql.SQLException: I/O Error: Connection reset on MS-SQL Server 2000

Anybody able to help me with this Java-JDBC Problem?
I'm creating a ResultSet and execute a query which approximatelly delivers me 11.000 rows.
With the given ResultSet i'd like to move through the records forward only.
In my while loop I'm able to reach ~9700 rows and then unexpectedly i get the error:
java.sql.SQLException: I/O Error: Connection reset
at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2277)
at net.sourceforge.jtds.jdbc.TdsCore.getNextRow(TdsCore.java:761)
at net.sourceforge.jtds.jdbc.JtdsResultSet.next(JtdsResultSet.java:593)
at ag.oase.jobs.Datenschaufel.Betriebabgleich(Datenschaufel.java:1629)
at ag.oase.jobs.Datenschaufel.main(Datenschaufel.java:183)
Caused by:
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:197)
at java.io.DataInputStream.readFully(DataInputStream.java:202)
at net.sourceforge.jtds.jdbc.SharedSocket.readPacket(SharedSocket.java:860)
at net.sourceforge.jtds.jdbc.SharedSocket.getNetPacket(SharedSocket.java:707)
at net.sourceforge.jtds.jdbc.ResponseStream.getPacket(ResponseStream.java:466)
at net.sourceforge.jtds.jdbc.ResponseStream.read(ResponseStream.java:103)
at net.sourceforge.jtds.jdbc.ResponseStream.readInt(ResponseStream.java:318)
at net.sourceforge.jtds.jdbc.TdsData.readData(TdsData.java:680)
at net.sourceforge.jtds.jdbc.TdsCore.tdsRowToken(TdsCore.java:2968)
at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2236)
... 4 more
I'm using the jTDS JDBC driver.
I googled a lot but didn't found a solution for this problem?
So please help me!
Thanks in advance
Ren�

...OWB repository cannot be installed into Oracle XE.
Cheers
David

Connection Reset while making http web service call to remote server

Hello guys,
Our environment details are as follows:
WebLogic version: 10.3.3
Cluster: yes
Database: Oracle
Web service server: Remote application
When our WebLogic server makes a http Web service call to another remote application which runs on IIS server for creating a record. The record gets created in remote application but WebLogic server log says java.net.SocketException: Connection reset and the same record doesn't get created in WebLogic application. We have confirmed that remote application is running and it is behaving as expected. Also, we installed web service client on our WebLogic machine just to isolate any network related issues, when we make a same request through this client it works fine and we get answer. At this point in time, it looks like it could be WebLogic or application which is behaving goofy. we are running out of ideas, it would be nice if someone have any thoughts on it like turning on any flags or any other troubleshooting steps. Please, let me know.
Here is the stack trace:
####<Sep 18, 2011 12:31:40 AM MDT> <Info> <com.blah.blah> <server1> <WLSserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Defaul
t (self-tuning)'> <user> <BEA1-69D606DA85BDB1A0A7D5> <> <1316327500388> <BEA-000000> <ERROR com.blah.blah - Error during creating a order remoteappja
va.net.SocketException: Connection reset
com.sun.jersey.api.client.ClientHandlerException: java.net.SocketException: Connection reset
at com.sun.jersey.api.client.Client.handle(Client.java:569)
at com.sun.jersey.api.client.WebResource.handle(WebResource.java:556)
at com.sun.jersey.api.client.WebResource.access$200(WebResource.java:69)
at com.sun.jersey.api.client.WebResource$Builder.get(WebResource.java:451)
Caused by: java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:173)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
at weblogic.net.http.MessageHeader.isHTTP(MessageHeader.java:220)
at weblogic.net.http.MessageHeader.parseHeader(MessageHeader.java:143)
at weblogic.net.http.HttpClient.parseHTTP(HttpClient.java:462)
at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:364)
at weblogic.net.http.SOAPHttpURLConnection.getInputStream(SOAPHttpURLConnection.java:37)
at weblogic.net.http.HttpURLConnection.getResponseCode(HttpURLConnection.java:952)
at com.sun.jersey.client.urlconnection.URLConnectionClientHandler._invoke(URLConnectionClientHandler.java:215)
at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:126)
... 58 more
>
thanks a lot for your help in advance
Regards,

Here's what the issue was for us:
When the web service was initializing, Weblogic? was trying to retrieve the WSDL first before initializing the service.
Though the web service URL was proper, the WSDL itself was unresolvable. This led to this strange connection reset error.
So, if you're experiencing this consistently, check your WSDL URL.
We used "strace" to discover this problem by running it for a brief time while the web service initialization was attempted - and it very clearly showed that the code was attempting to laod something from a bogus address / IP

OVMAPI_6000E Internal Error: Connection reset (VM Manager 3.0.1)

Hi,
I have a problem with connection (http), mention that I can connect with https protocol, to the Oracle VM Manager.
If I use "https://<IP>:7002/ovm/console" it works, and if I use "http://<IP>:7002/ovm/console" I receive the next message: "The connection was reset.."
Below I post the log from the java console when I try to connect to virtual machine.
Java Web Start 1.6.0_27
Using JRE version 1.6.0_27-b07 Java HotSpot(TM) Client VM
User home directory = C:\Users\Florin
c: clear console window
f: finalize objects on finalization queue
g: garbage collect
h: display this help message
m: print memory usage
o: trigger logging
p: reload proxy configuration
q: hide console
r: reload policy configuration
s: dump system and deployment properties
t: dump thread list
v: dump thread stack
0-5: set trace level to <n>
Aug 29, 2011 4:43:09 PM com.oracle.ovm.ras.proxy.RasProxyApplet main
INFO: Arguments [-server, 192.168.0.220, -service, 003600010004fb0000060000ce5ef321b35efa23]
Aug 29, 2011 4:43:09 PM com.oracle.ovm.ras.proxy.RasProxyApplet main
INFO: Server : 192.168.0.220
Aug 29, 2011 4:43:09 PM com.oracle.ovm.ras.proxy.RasProxyApplet main
INFO: service id : 003600010004fb0000060000ce5ef321b35efa23
Aug 29, 2011 4:43:14 PM com.oracle.ovm.ras.proxy.external.VncViewerLauncherFactory getVncViewerLauncher
INFO: Os is : windows 7
Exception in thread "HandshakeCompletedNotify-Thread" java.util.ConcurrentModificationException
     at java.util.HashMap$HashIterator.nextEntry(Unknown Source)
     at java.util.HashMap$EntryIterator.next(Unknown Source)
     at java.util.HashMap$EntryIterator.next(Unknown Source)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl$NotifyHandshakeThread.run(Unknown Source)
Aug 29, 2011 4:43:23 PM com.oracle.ovm.ras.proxy.ProxyThread run
INFO: Connecting ovm to http://192.168.0.220:7002
Aug 29, 2011 4:43:24 PM com.oracle.ovm.ras.proxy.ProxyThread run
SEVERE: OVMAPI_6000E Internal Error: Connection reset Connection reset
Mon Aug 29 16:43:24 EEST 2011
com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_6000E Internal Error: Connection reset Connection reset
Mon Aug 29 16:43:24 EEST 2011
     at com.oracle.ovm.mgr.api.manager.OvmManagerImpl.open(OvmManagerImpl.java:579)
     at com.oracle.ovm.mgr.api.OvmClient.dynamicConnect(OvmClient.java:123)
     at com.oracle.ovm.ras.proxy.ProxyThread.run(ProxyThread.java:161)
Caused by: java.net.SocketException: Connection reset
     at java.net.SocketInputStream.read(Unknown Source)
     at java.io.BufferedInputStream.fill(Unknown Source)
     at java.io.BufferedInputStream.read1(Unknown Source)
     at java.io.BufferedInputStream.read(Unknown Source)
     at sun.net.www.http.HttpClient.parseHTTPHeader(Unknown Source)
     at sun.net.www.http.HttpClient.parseHTTP(Unknown Source)
     at sun.net.www.http.HttpClient.parseHTTP(Unknown Source)
     at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
     at com.oracle.odof.io.AbstractServlet.receive(AbstractServlet.java:253)
     at com.oracle.odof.OdofExchange.send(OdofExchange.java:466)
     at com.oracle.odof.OdofExchange.newConnection(OdofExchange.java:518)
     at com.oracle.odof.OdofExchange.acquireConnection(OdofExchange.java:308)
     at com.oracle.odof.OdofExchange.connect(OdofExchange.java:243)
     at com.oracle.odof.OdofExchange.connect(OdofExchange.java:120)
     at com.oracle.odof.OdofExchange.connect(OdofExchange.java:96)
     at com.oracle.ovm.mgr.api.manager.OvmManagerImpl.open(OvmManagerImpl.java:570)
     ... 2 more
Edited by: user12123011 on Aug 29, 2011 5:04 PM

user12123011 wrote:
I have a problem with connection (http), mention that I can connect with https protocol, to the Oracle VM Manager.
If I use "https://<IP>:7002/ovm/console" it works, and if I use "http://<IP>:7002/ovm/console" I receive the next message: "The connection was reset.."
http is on port 7001, not 7002.

Connection reset error while calling web service deployed on tomcat

Hello Friends,
I am trying to invoke a web service from web dynpro application. The web service is deployed on tomcat 5.5 server.
I am creating an adaptive web service model using wsdl file. The model gets created without any error.
But when application is deployed and run it is giving following exception:
java.net.SocketException: Connection reset
    at java.net.SocketInputStream.read(SocketInputStream.java:168)
    at java.io.BufferedInputStream.read1(BufferedInputStream.java:254)
    at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
    at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
    at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
    ... 102 more
I tried to call the service from a simple java application. There the service works fine.
Also, in the web services navigator, if I specify the wsdl url for testing it gives the same error of "Connection reset".
I don't think this is a proxy server issue as the tomcat is within the local network.
Can someone please help me with this?
Thanks and regards,
Mayuresh
Edited by: Mayuresh Kanvinde on Mar 27, 2008 7:03 PM

Hi Sumit,
Thanks for the reply.
Here is the stack trace:
com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WSDL URL 'http://<host>:<port>/WebServicesTest/DummyWebService?wsdl' and service factory configuration 'null'
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:422)
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:372)
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:342)
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:326)
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo$Cache.getModelInfo(WSModelInfo.java:199)
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:1035)
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:248)
     at com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.<init>(WSTypedModel.java:41)
     at com.tcs.vis.Vishy.<init>(Vishy.java:73)
     at com.tcs.app.AppView.wdDoInit(AppView.java:101)
     at com.tcs.app.wdp.InternalAppView.wdDoInit(InternalAppView.java:143)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
     at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
     at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:748)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:283)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. Could not load web service model. See nested exception for details.
     at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:150)
     at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.<init>(DGenericServiceImpl.java:50)
     at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:71)
     at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:91)
     at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:420)
     ... 45 more
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Proxy Generator Error. Problem with WSDL file parsing. See nested message.
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:182)
     at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:147)
     ... 49 more
Caused by: com.sap.engine.lib.xml.util.NestedException: IO Exception occurred while parsing file:Connection reset -> java.net.SocketException: Connection reset
     at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1039)
     at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadWSDLDocument(WSDLDOMLoader.java:1126)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:178)
     ... 50 more
Caused by: java.net.SocketException: Connection reset
     at java.net.SocketInputStream.read(SocketInputStream.java:168)
     at java.io.BufferedInputStream.read1(BufferedInputStream.java:220)
     at java.io.BufferedInputStream.read(BufferedInputStream.java:277)
     at java.io.BufferedInputStream.read1(BufferedInputStream.java:220)
     at java.io.BufferedInputStream.read(BufferedInputStream.java:277)
     at com.sap.engine.services.webservices.jaxm.soap.LimitedInputStream.read(LimitedInputStream.java:61)
     at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.readData(EncodedDataReader.java:269)
     at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.fetchData(EncodedDataReader.java:332)
     at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:165)
     at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.read(AdvancedXMLStreamReader.java:143)
     at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.addInputFromInputStream(AdvancedXMLStreamReader.java:292)
     at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:220)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
     at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
     at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
     at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
     at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
     at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
     at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1023)
     ... 52 more
Thanks and regards,
Mayuresh
Edited by: Mayuresh Kanvinde on Mar 28, 2008 1:10 PM

Access to Attribute Type via Java API

Hi,
I'm writing an aplication in Java to access out OLAP schema and display certain DIMENSION/LEVEL and ATTRIBUTE values. This is working out really well but I'm hitting one issue at the moment which has me stumped.
When I display a Dimension value in a table I want to default the attribute we display to a sensible display value. In AWM there is a field "Attribute Type" which offers drop down selections for "User", .... "Member Short Description", "Member Long Description"...
See the General Tab under Attributes for a particular Attribute. Looking at the Help text for the "Member Long Description" I see the following.
"Long descriptive names typically used by Oracle Business Intelligence tools for displaying dimension members in selection lists, crosstabs, and graphs." Looks perfect for what I want. My Dataware house architect already has an Attribute for each hirearchy
marked with this property so in theory I should be able to look for the Attribute in the Dimension with this property and bingo I have my default display Atttribute!
The problem is I seem to be able to find api's to access every aspect of the MdmAttribute object except this particular property.
Here is a snippet from the OLAP api sample code augmented with some println's of my own:
if (mdmAttr.getName().equals(name)) {
     System.out.println("Attribute : " + mdmAttr.getID());
     System.out.println(" name : " + mdmAttr.getName());
     System.out.println(" desc : " + mdmAttr.getDescription());
     System.out.println(" s desc: " + mdmAttr.getShortDescription());
     System.out.println(" type : " + mdmAttr.getType());
     System.out.println(" type id: " + mdmAttr.getType().getID());
return mdmAttr;
None of the avaiable APIs of MdmAttribute seem to fit the bill.
The question is ... is there an API somewhere I can call on the MdmAttribute object or an associated object that will give me back the "Attribute Type" as listed in this dropdown. Note that getType returns DataType!String which denotes the fundemental type of the Attribute (int, String etc) rather than this abstract Attribute Type property we need. Not listed here is the getDataType() api which also returns DataType!String and seems to be equivalent to the getType api.
Regards
Fergal

One small clarification if its not already obvious. We are using the OLAP Java api's directly ... not via BI Beans.
Regards
Fergal

HTTP response error :Connection reset

Hi all,
I am getting following error in log while sending message to the trading partner and the main problem is that once this error comes then after that I am not able to send any more message to any of my Trading Partners. Even if I try to send message to any other Trading Partner, nothing comes in the B2B log and report as well. After restarting the B2B I am able to send message again to other Trading Partners.
Can anyone please tell the reason for getting this error? I also want to know that after getting this error once, why am I not able to send message to any Trading Partner?
2008.12.12 at 06:41:07:647: Thread-13: B2B - (WARNING)
Message Transmission Transport Exception
Transport Error Code is OTA-HTTP-SEND-1006
StackTrace oracle.tip.transport.TransportException: [IPT_HttpSendHttpResponseError] HTTP response error :Connection reset.
at oracle.tip.transport.TransportException.create(TransportException.java:91)
at oracle.tip.transport.basic.HTTPSender.send(HTTPSender.java:627)
at oracle.tip.transport.b2b.B2BTransport.send(B2BTransport.java:311)
at oracle.tip.adapter.b2b.transport.TransportInterface.send(TransportInterface.java:980)
at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1744)
at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:968)
at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1147)
at oracle.tip.adapter.b2b.transport.AppInterfaceListener.onMessage(AppInterfaceListener.java:137)
at oracle.tip.transport.basic.jms.JMSMonitor.processMessages(JMSMonitor.java:610)
at oracle.tip.transport.basic.jms.JMSMonitor.run(JMSMonitor.java:236)
Caused by: java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at com.sun.net.ssl.internal.ssl.InputRecord.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.InputRecord.read(DashoA12275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.HandshakeOutStream.flush(DashoA12275)
at com.sun.net.ssl.internal.ssl.SunJSSE_az.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.SunJSSE_az.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.SunJSSE_ax.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.j(DashoA12275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.AppOutputStream.write(DashoA12275)
at java.io.ByteArrayOutputStream.writeTo(ByteArrayOutputStream.java:112)
at HTTPClient.HTTPConnection.sendRequest(HTTPConnection.java:3018)
at HTTPClient.HTTPConnection.handleRequest(HTTPConnection.java:2843)
at HTTPClient.HTTPConnection.setupRequest(HTTPConnection.java:2635)
at HTTPClient.HTTPConnection.Post(HTTPConnection.java:1107)
at oracle.tip.transport.basic.HTTPSender.send(HTTPSender.java:590)
... 8 more
2008.12.12 at 06:41:07:647: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.TransportInterface:send Error in sending message
2008.12.12 at 06:41:07:648: Thread-13: B2B - (INFORMATION) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequestPostColab Request Message Transmission failed
2008.12.12 at 06:41:07:648: Thread-13: B2B - (DEBUG) DBContext beginTransaction: Enter
2008.12.12 at 06:41:07:648: Thread-13: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
2008.12.12 at 06:41:07:648: Thread-13: B2B - (DEBUG) DBContext beginTransaction: Leave
2008.12.12 at 06:41:07:648: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequestPostColab [IPT_HttpSendHttpResponseError] HTTP response error :Connection reset.
Connection reset
2008.12.12 at 06:41:07:651: Thread-13: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
2008.12.12 at 06:41:07:652: Thread-13: BusinessLogicLayer - (DEBUG) Push Stack: updateBusinessMessage
2008.12.12 at 06:41:07:656: Thread-13: BusinessLogicLayer - (DEBUG) Pop Stack: updateBusinessMessage
2008.12.12 at 06:41:07:656: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:notifyApp retry value <= 0, so sending exception to IP_IN_QUEUE
2008.12.12 at 06:41:07:658: Thread-13: B2B - (DEBUG) Engine:notifyApp Enter
2008.12.12 at 06:41:07:663: Thread-13: B2B - (DEBUG) Enqueue Engine AQJMSCorrelationID = null
2008.12.12 at 06:41:07:663: Thread-13: B2B - (DEBUG) notifyApp:notifyApp Enqueue the ip exception message:
<Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<correlationId>null</correlationId>
<b2bMessageId>0AF77A6111E29ED374E000001BDE3D60</b2bMessageId>
<errorCode>AIP-50079</errorCode>
<errorText>Transport error: [IPT_HttpSendHttpResponseError] HTTP response error :Connection reset.
Connection reset</errorText>
<errorDescription>
<![CDATA[Machine Info: (dys094w004)
Transport error: [IPT_HttpSendHttpResponseError] HTTP response error :Connection reset.
Connection reset ]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
2008.12.12 at 06:41:07:692: Thread-13: B2B - (DEBUG) Engine:notifyApp Exit
2008.12.12 at 06:41:07:693: Thread-13: B2B - (DEBUG) DBContext commit: Enter
2008.12.12 at 06:41:07:696: Thread-13: B2B - (DEBUG) DBContext commit: Transaction.commit()
2008.12.12 at 06:41:07:696: Thread-13: B2B - (DEBUG) DBContext commit: Leave
2008.12.12 at 06:41:07:696: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequest Exit
2008.12.12 at 06:41:07:696: Thread-13: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage:
***** REQUEST MESSAGE *****
Please help.
Thanks & Regards,
Anuj Dwivedi

Hi Sinkar,
Thanks for the reply. I confirmed it with my Trading Partner and their server is not running but still I want to know that why am I not able to send message to any other Trading Partner after getting this error once. And if I restart the server, it again acts normally and I am able to send message to other Trading Partners.
SSL is configured properly because I was able to communicate with this Trading Partner earlier when their server was up.
We are working on 10.1.2.3.0 with 7457066 MLR 5 patch. Please guide if any other patch required.
Thanks for the help.
Warm Regards,
Anuj Dwivedi

Socket Connection reset error

i hava a server serving multiple clients. sometimes while reading data from the client by the thread, it is throwing an exception as follows:
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at java.net.SocketInputStream.read(SocketInputStream.java:90)
at Disex.Thread.clientHandlerThread.run(clientHandlerThread.java:86)
where clientHandlerThread is my thread program to handle clients.
i am in need of help to tackle this
thanks
asan

hi...
I think current description of your problem will not help anyone to see the issue properly. Please if you provide some detail info about your application and also if you paste the code block that is throwing exception. "Connection reset" is not saying much about your addressed issue.
Raheel.

SocketException: Connection reset , using HttpURLConnection

hello everybody, i'm using this to read a xml from internet:
       URL url;
            HttpURLConnection urlcon;
            url = new URL (urlString);
            System.out.print("Connecting ....\t");
            urlcon = (HttpURLConnection)url.openConnection();
            if(!urlcon.getResponseMessage().equals("OK"))
                return -1;
            System.out.println("Done!");it gives me:
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read1(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at sun.net.www.http.HttpClient.parseHTTPHeader(Unknown Source)
at sun.net.www.http.HttpClient.parseHTTP(Unknown Source)
at sun.net.www.http.HttpClient.parseHTTP(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unkno
at java.net.HttpURLConnection.getResponseCode(Unknown Source)
at java.net.HttpURLConnection.getResponseMessage(Unknown Source)
when i do urlcon.getResponseMessage()....
Any ideas why this happens?
PS: when i try the same URL in a browser, it opens the file fine .....

My suggestion is run that with Wireshark (ethereal)
monitoring the data. That way you can see what is
really going on in the traffic and compare that to
the browsers traffic. It's possible that the server
is attempting to block bots, and I think Java tells
the server that it is a JRE connecting and not a
normal browser. There are ways to get around that
though if that is the issue.You were right, the first thing i tried was to set the user-agent property in the request, and that was it, looks like the server was blocking me, thx everybody

Connection reset by peer when I specify port for Callback

I have a successful rmi callback when it uses annoymous port by using UnicastRemoteObject.exportObject(this) from client. But I get the following messages when I tried to specify port by using UnicastRemoteObject.exportObject(this, port) by client. My understanding is this tells the server to callback using the port specify and the connection should be made. Where it fails is when the server tries to call client.notify() where the callback is taking place I get the errors.
Am I missing something? I thought that was all I needed to do to specify a port.
Remote Exception:java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.MarshalException: Error marshaling transport header; nested exception is:
java.net.SocketException: Connection reset by peer: Connection reset by peer
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.MarshalException: Error marshaling transport header; nested exception is:
java.net.SocketException: Connection reset by peer: Connection reset by peer
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
Thanks for the help.

Hi Esmond, My name is Lee and I work with Joon (hellscream) and this RMI callback problem still persists. We appreciate your help and we know about your expertise in this area. (Great products on your web site by the way).
The problem environment currently consists of a Unix Solaris server on the backend and windows XP laptops acting as clients. The callback is from the unix server back to the client.
By looking at the output of netstat -na on the unix server during a normal anonymous port run, we can clearly see that there seem to be 3 sequentially numbered ports involved whenever the anonymous port construct of UnicastRemoteObject is used. This happens with super() or super(0); in our client code. All works very well that way.
The problem arises when we make changes to the client impl file and specify a port with super(65000) for example.
There is no firwall involved right now and UnicastRemoteObject doesn't seem to behave as advertised in the sense that
We can clearly see what's going on with the network using Thread.sleep(10000) within the client app meanwhile executing netstat -na on the unix server and grepping for the client IP address
We can see that the unix server STILL wants to talk to the client on an arbitrary port while the laptop client is listening on the desired port that we chose (65000) in this case.
If we attempt to instantiate a port in the server Impl java file, the results are the same with the exception of the choice of the source port on the unix server. We seem to be able to choose and set that at will. Unfortunately, and from the perspective of a future firewall, the source port is irrelevant and the rules normally apply to destination ports in an outgoing connection.
Anyway, with ports instantiated and everything compiling, the client prints the following stacktrace
Thanks very much in advance for your help
Remote Exception:java.rmi.ServerException: RemoteException occurred in server th
read; nested exception is:
java.rmi.ConnectIOException: error during JRMP connection establishment;
nested exception is:
java.net.SocketException: Connection reset
java.rmi.ServerException: RemoteException occurred in server thread; nested exce
ption is:
java.rmi.ConnectIOException: error during JRMP connection establishment;
nested exception is:
java.net.SocketException: Connection reset
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:292)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:4
60)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport
.java:701)
at java.lang.Thread.run(Thread.java:534)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Stream
RemoteCall.java:247)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:
223)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133)
at ids.rmi.ServerJobImpl_Stub.execute(Unknown Source)
at ids.jobExec.JobThread.run(JobRunner.java:551)
Caused by: java.rmi.ConnectIOException: error during JRMP connection establishme
nt; nested exception is:
java.net.SocketException: Connection reset
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:274
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:101)
at ids.rmi.JobClientImpl_Stub.message(Unknown Source)
at ids.rmi.ServerJobImpl.execute(ServerJobImpl.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:4
60)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport
.java:701)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
at java.io.DataInputStream.readByte(DataInputStream.java:331)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:215
... 15 more
Job finished. Exit status: -1

Getting connection reset.

Hi All,
I am working on a client/server based program.The client is sending messages to server. For some messages it is giving the following
exception but also working fine for same messages sometimes.
java.net.SocketException: Connection reset
        at java.net.SocketInputStream.read(SocketInputStream.java:168)
        at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(StreamDecoder.java:408)
        at sun.nio.cs.StreamDecoder$CharsetSD.implRead(StreamDecoder.java:450)
        at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:182)
        at java.io.InputStreamReader.read(InputStreamReader.java:167)
        at java.io.BufferedReader.fill(BufferedReader.java:136)
        at java.io.BufferedReader.readLine(BufferedReader.java:299)
        at java.io.BufferedReader.readLine(BufferedReader.java:362)some help which i got saying the length of message may be long but its not true in my application. Within our domain it worked fine but over firewalls its giving the exception. Is this due to firewall? If yes how can we solve this?
please help me in solving this issue

hi
Iam getting connection reset during processing a file.
java.net.SocketException: Connection reset
        at java.net.SocketInputStream.read(SocketInputStream.java:168)
        at com.sun.net.ssl.internal.ssl.InputRecord.a(DashoA6275)
        at com.sun.net.ssl.internal.ssl.InputRecord.read(DashoA6275)
        at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA6275)
        at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA6275)
        at com.sun.net.ssl.internal.ssl.AppInputStream.read(DashoA6275)
        at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(StreamDecoder.java:406)
        at sun.nio.cs.StreamDecoder$CharsetSD.implRead(StreamDecoder.java:446)
        at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:180)
        at java.io.InputStreamReader.read(InputStreamReader.java:167)
        at java.io.BufferedReader.fill(BufferedReader.java:136)
        at java.io.BufferedReader.readLine(BufferedReader.java:299)
        at java.io.BufferedReader.readLine(BufferedReader.java:362)
        at EndMonitor.run(ApacheCommunication1.java:1502)
        at java.util.TimerThread.mainLoop(Timer.java:432)
        at java.util.TimerThread.run(Timer.java:382)

Connection reset when obtaining Realms from LDAP provider

Properties props = new Properties();
props.put( "provider", JAZNProvider.Type.LDAP);
props.put( "location", "ldap://<myoidurl>:389");
props.put( "ldap.user", "cn=orcladmin");
props.put( "ldap.password", "!<mypwd>");
JAZNConfig cfg = new JAZNConfig(props);
JAZNProvider prov = cfg.getJAZNProvider();
Set realms = prov.getRealmManager().getRealms(); <---- causes following error
Exception in thread "main" oracle.security.jazn.JAZNNamingException: The system is unable to communicate with the directory or naming service.
     at oracle.security.jazn.spi.ldap.LDAPContext.getSSLDirContext(LDAPContext.java:622)
     at oracle.security.jazn.spi.ldap.LDAPContext.getDirContext(LDAPContext.java:487)
     at oracle.security.jazn.spi.ldap.LDAPContext.getDefaultDirContext(LDAPContext.java:246)
     at oracle.security.jazn.spi.ldap.LDAPContext.getOrclRootCtxDN(LDAPContext.java:187)
     at oracle.security.jazn.spi.ldap.LDAPContext.getSiteJAZNCtxDN(LDAPContext.java:222)
     at oracle.security.jazn.spi.ldap.LDAPRealmManager.searchRealms(LDAPRealmManager.java:1087)
     at oracle.security.jazn.spi.ldap.LDAPRealmManager.getRealms(LDAPRealmManager.java:200)
     at client.JaznTest.<init>(JaznTest.java:41)
     at client.JaznTest.main(JaznTest.java:54)
Caused by: javax.naming.CommunicationException: oidtest.ncdenr.org:389 [Root exception is java.net.SocketException: Connection reset]
     at com.sun.jndi.ldap.Connection.<init>(Connection.java:194)
     at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:118)
     at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1578)
     at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2596)
     at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:283)
     at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
     at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
     at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
     at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
     at javax.naming.InitialContext.init(InitialContext.java:223)
     at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
     at oracle.security.jazn.spi.ldap.LDAPContext.getSSLDirContext(LDAPContext.java:613)
     ... 8 more
Caused by: java.net.SocketException: Connection reset
     at java.net.SocketInputStream.read(SocketInputStream.java:168)
     at com.sun.net.ssl.internal.ssl.InputRecord.readFully(InputRecord.java:284)
     at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:319)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:720)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1025)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1038)
     at oracle.security.jazn.spi.ldap.JAZNSSLSocketFactoryImpl.init(JAZNSSLSocketFactoryImpl.java:228)
     at oracle.security.jazn.spi.ldap.JAZNSSLSocketFactoryImpl.createSocket(JAZNSSLSocketFactoryImpl.java:170)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.sun.jndi.ldap.Connection.createSocket(Connection.java:311)
     at com.sun.jndi.ldap.Connection.<init>(Connection.java:181)
     ... 21 more

The reset seems to happen after 5 minutes. Is there any network device in between 153.88.247.15 and the DPS? It could also be a idle timeout on the box or app on 153.88.247.15

SQLException - Connection Reset (OLAP JAVA API)

Similar Messages

Maybe you are looking for