HTTP3068: Error receiving request ip_address (Connection refused)

Hi,
I've noticed many failures in my error log. I use SJSWS 6.1u7. Some example are below:
[04/Jul/2007:11:29:11] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
[04/Jul/2007:11:32:40] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
[04/Jul/2007:11:32:40] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
[04/Jul/2007:11:32:41] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
[04/Jul/2007:11:34:53] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
[04/Jul/2007:11:34:53] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
[04/Jul/2007:11:35:45] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
[04/Jul/2007:11:37:21] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)The IP address which is noticed in error line is a router of some NAT in my corporation. I want to tune my webserver and receive all request from this address.
Any idea?
Irek

ireneusz.tarnowski wrote:
Hi,
I've noticed many failures in my error log. I use SJSWS 6.1u7. Some example are below:
[04/Jul/2007:11:29:11] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
[04/Jul/2007:11:32:40] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
[04/Jul/2007:11:32:40] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
[04/Jul/2007:11:32:41] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
[04/Jul/2007:11:34:53] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
[04/Jul/2007:11:34:53] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
[04/Jul/2007:11:35:45] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)
[04/Jul/2007:11:37:21] failure ( 9310): HTTP3068: Error receiving request from 156.17.73.28 (Connection refused)The IP address which is noticed in error line is a router of some NAT in my corporation. I want to tune my webserver and receive all request from this address.
Any idea?
IrekIrek,
Did you ever figure out how to fix this issue with the Sun Webserver 6.1 that you had back in July last year with the "Error receiving request from <ip address> (Connection refused)" messages? We are getting the same errors on our Sun ONE / Sun Java System webserver version 6.1 SP6. Please let me know.
[http://forum.java.sun.com/thread.jspa?messageID=9751068#9751068|http://forum.java.sun.com/thread.jspa?messageID=9751068#9751068]

Similar Messages

HTTP3068: Error receiving request

Hi,
We have a Iplanet Iws 6.0sp1 web server running in DMZ, which forwards request to a SUNONE 7 based application server which is inside intranet.
Now lately we are seeing that the sunone server.log is throwing the following messages
[20/Apr/2006:05:08:09] SEVERE (23451): HTTP3068: Error receiving request from 10.100.10.231 (Not connected)
Can any one help me out to figure out what could be the probably reasons for this messages coming up. Because I have tested the connectivity between the web and the app server and that is alive.
Please let me know if there is any further information needed.
Nikhil

We had a similar problem in April 2007 though we were seeing 'Connection refused' messages associated with the HTTP3068 error and this appeared to be due to our load balancers doing a reset rather than a graceful close (see OSC Case ID 37837095). We have now replaced the load balancers and the problem has gone away...
BTW, we only saw this in Solaris 10 environments and this has been linked to BugID 6263346 (Synopsis: accept() cannot produce ECONNABORTED error so the connection is just dropped). Basically, the web server is reading on the socket waiting for data from the client -- The receive (PR_Recv) has probably returned -1 and there is no data in the client buffer (this is what the Sun Engineer told me) so hence the error message and that it relates to a problem with the Solaris 10 system call itself and not the web server application. Also, Sun Application Server is affected in the same way.
The Solaris bug which is causing the problem has a very low priority according to Sun software engineering and there were no other customers requesting a fix (apart from us) so AFAIK it is still open -- so the option for us was to move back to Solaris 8 or change the load balancers to handle HTTP protocol connections properly.
BTW, we also had similar problems with the Directory Server product and load balancers filling the logs ....
Hope this helps and I am happy to provide more details if needed.

Web Server 6.1 Error failure ( 967): HTTP3068: Error receiving request

Hi I have install Sun web server 6.1 on my T2000 system with solaris 10, the web server run the Siebel CRM application, but it is tooooo slow to bring the first page. Takes about 6.07 sec to bring the login page. The log files of the web server gives me a lot of +"failure ( 967): HTTP3068: Error receiving request"+.
Please I need you help

Hello Dear Friend Urgent Programmer
I'am Alfonso Franco member of Sun Developer
that is requested your questions Look:
1 - Please check out your System is ready to download this iPlanet Web Server 6.1
2- Suppose that you System is ready needs to
configure your setup add/remove program in
you computer that matches with the Web Server
3- if continue the problem error after this
analize very fine the problem and for end
we going to create the exact library and
port in it's Servers with a Java Program Database .
well my friend expect that thoses advice may serve something to solve this
problem for more contact to [email protected] to follow helping sincerely as "Good Programmer "

Executing function module gives error "Portal request failed: Connection fa

Dear Experts,
I have a Function module Z_SAT_CREDITLIMIT_CHANGE which in itself accesses the SAP Update Function module
UPDATE/INSERT of the credit limit(CREDITLIMIT_CHANGE)
and writes the changed data to the Table KNKK(Customer Master Credit Management : Control Area Data).
While executing this fn module Z_SAT_CREDITLIMIT_CHANGE
from VC storyboard i received error "Portal request failed:
Connection failed: Nested Exception: Native Connection to backend system is broken" . Z_SAT_CREDITLIMIT_CHANGE executes fine and updates data in ECC system.
Than i noticed further that while commenting the part of code in Z_SAT_CREDITLIMIT_CHANGEwhere call to fn module CREDITLIMIT_CHANGE is made there's no error recieved and Z_SAT_CREDITLIMIT_CHANGE executes without error but obviously no data is updated.
Appreciate if any one can please explain how can i use CREDITLIMIT_CHANGE in Z_SAT_CREDITLIMIT_CHANGE
without any errors.
Kind Regards,
Robin.

Hi Robin,
Also, check that the user with the one you're accessing to the backend have permissions to execute the Dataservice at the backend system.
You should check the usermapping to know which is the user at backend.
Best Regards,
Luis

LPR Error from LprSendControlFile(): 111 - Connection refused

Hi,
one of our printers produces the error message:
"LPR Error from LprSendControlFile(): 111 - Connection refused".
I can ping the printer.
Used different workstations but no problem of a single workstation.
Restart of the printer has no beneficial impact.
The printer was ok for over six month.
All other printers are ok.
No patches installed within last days.
Server:
- OES2-SP1
- iprintgw PORT=LPR HOSTNAME=xyz.abc.de PRINTERNAME=PASSTHROUGH
- iprint-iprntman: 6.1.20091224
- iprint-management: 6.2.20090924
- iprint-server: 6.1.20091224
Any ideas?
Thanks
Bernhard

Bernhard,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Forums Team
http://forums.novell.com

Before I had Mavericks I was able to print over the network to a Windows PC. Now I receive the message, "connection refused." Any ideas?

Before I upgraded to Mavericks, I was able to print over the network to a printer attached to a Windows PC. Now, I receive the message, "connection refused." any ideas as to why this may be and what I can do about it would be appreciated.

I had reconfigured all of the settings the same as in the previous OS X. The only thing I can think of that may be causing this is that the printer is an older Canon Pixma iP4300 and the Canon site doesn't have a driver for the new OS X. The Canon site said that the new OS X may supply the driver. Is there any one with the same experience as mine?

Error TNS: listener does not curnetly jnow of service requested in connect

hello
i get error TNS: listener does not curnetly jnow of service requested in connect descriptor
when i write tnsping ora920 i get
TNS Ping Utility for 32-bit Windows: Version 10.1.0.2.0 - Production on 02-└┬├.
-2010 23:26:55
Copyright (c) 1997, 2003, Oracle. All rights reserved.
Used parameter files:
C:\oracle\product\10.1.0\Client_1\network\admin\sqlnet.ora
TNS-03505: Failed to resolve name
C:\Users\fg>

784633 wrote:
hello
i get error TNS: listener does not curnetly jnow of service requested in connect descriptor
when i write tnsping ora920 i get
TNS Ping Utility for 32-bit Windows: Version 10.1.0.2.0 - Production on 02-└┬├.
-2010 23:26:55
Copyright (c) 1997, 2003, Oracle. All rights reserved.
Used parameter files:
C:\oracle\product\10.1.0\Client_1\network\admin\sqlnet.ora
TNS-03505: Failed to resolve name
That's not the same error you reported in the thread subject ....
A TNS-03505 is very much like a 12154.
=================================
ORA-12154: TNS:could not resolve the connect identifier specified
This error means one thing, and one thing only. The client could not find the specified entry in the tnsnames.ora file being used.
As a follow-on to that statement, remember that when you use a dblink, the database in which the link is defined is acting as a client to the database that is the target of the link. So in this case, the tnsnames.ora file on the host of your source should have an entry for your target db, as defined in the db_link.
And for the umpteenth time ... this error has NOTHING to do with the status of a listener. The connection request never got far enough to reach a listener. If anyone tells you to check a listener in response to ora-12154, they are not paying attention, or do not understand how TNS works. This error is the equivalent of not being able to place a telephone call because you don't know the number of the party you want to reach. You wouldn't debug that situation by going to the other guy's house and testing his telephone, or by going to the phone company and testing the switchboard. And you don't debug a ORA-12154 by checking the listener. If I had a top ten list of "Incredibly Simple Concepts (tm)" that should be burned into the brain of everyone who claims to be an Oracle DBA, it would include "ORA-12154 Has Nothing To Do With The Listener".
=================================
A couple of important points.
First, the listener is a server side only process. It's entire purpose in life is to receive requests for connections to databases and set up those connections. Once the connection is established, the listener is out of the picture. It creates the connection. It doesn't sustain the connection. One listener, with the default name of LISTENER, running from one oracle home, listening on a single port, will serve multiple database instances of multiple versions running from multiple homes. It is an unnecessary complexity to try to have multiple listeners or to name the listener as if it belongs to a particular database. That would be like the telephone company building a separate switchboard for each customer.
Second, the tnsnames.ora file is a client side issue. It's purpose is for address resolution - the tns equivalent of the 'hosts' file further down the network stack. The only reason it exists on a host machine is because that machine can also run client processes.
Assume you have the following in your tnsnames.ora:
larry =
(DESCRIPTION =
 (ADDRESS_LIST =
 (ADDRESS = (PROTOCOL = TCP)(HOST = myhost)(PORT = 1521))
 (CONNECT_DATA =
 (SERVICE_NAME = curley)
)Now, when you issue a connect, say like this:
$> sqlplus scott/tiger@larrytns will look in your tnsnames.ora for an entry called 'larry'. Next, tns sends a request to (PORT = 1521) on (HOST = myhost) using (PROTOCOL = TCP), asking for a connection to (SERVICE_NAME = curley).
Where is (HOST = myhost) on the network? When the request gets passed from tns to the next layer in the network stack, the name 'myhost' will get resolved to an IP address, either via a local 'hosts' file, via DNS, or possibly other less used mechanisms. You can also hard-code the ip address (HOST = 123.456.789.101) in the tnsnames.ora.
Next, the request arrives at port 1521 on myhost. Hopefully, there is a listener on myhost configured to listen on port 1521, and that listener knows about SERVICE_NAME = curley. If so, you'll be connected.
What can go wrong?
First, there may not be an entry for 'larry' in your tnsnames. In that case you get "ORA-12154: TNS:could not resolve the connect identifier specified" No need to go looking for a problem on the host, with the listener, etc. If you can't place a telephone call because you don't know the number (can't find your telephone directory (tnsnames.ora) or can't find the party you are looking for listed in it (no entry for larry)) you don't look for problems at the telephone switchboard.
Maybe the entry for larry was found, but myhost couldn't be resolved to an IP address (say there was no entry for myhost in the local hosts file). This will result in "ORA-12545: Connect failed because target host or object does not exist"
Maybe there was an entry for myserver in the local hosts file, but it specified a bad IP address. This will result in "ORA-12545: Connect failed because target host or object does not exist"
Maybe the IP was good, but there is no listener running: "ORA-12541: TNS:no listener"
Maybe the IP was good, there is a listener at myhost, but it is listening on a different port. "ORA-12560: TNS:protocol adapter error"
Maybe the IP was good, there is a listener at myhost, it is listening on the specified port, but doesn't know about SERVICE_NAME = curley. "ORA-12514: TNS:listener does not currently know of service requested in connect descriptor"
=====================================
C:\Users\fg>

SOAP Exception, Connection refused error in jdeveloper 11g

Hello,
I am using jdeveloper 11g 11.1.2.3.0.
I have been experiencing the following error everytime I try to run the applicaiton. I use webservices in my applicaiton and recently the webservices url were changed pointing now to dev instead of the lab environment. The code has been migrated to dev environment, I tested the webservices in my browser, they seem to be working fine and are pulling up the required data.
ERROR:
javax.xml.soap.SOAPException: Message send failed: Connection refused: connect
Error
Message send failed: Connection refused: connect
Error
Connection refused: connect
I am not sure what is causing this. Any help would be appreciated.
Thanks in advance,
Sal

Hello Frank,
Thanks for your response. I checked the browser proxy settings in Jdeveloper, nothing is set there right now. Use HTTP Proxy Server is unchecked. What do I need to set this to?
Thanks,
Sal

Jdeveloper 11g TP4: Connection refused error for Embedded Oc4j

Hi,
I am getting following error whenever trying to deploy any application in embedded oc4j or whenever try to connect with embedded server on Resource palette.
Error while getting remote MBeanServer for url: ormi://127.0.0.1:23891/default:
Error reading application-client descriptor: Error communicating with server: Connection refused: connect; nested exception is:
     javax.naming.CommunicationException: Connection refused: connect [Root exception is java.net.ConnectException
I am using Jdeveloper 11g TP 4 on windows XP.
I have checked other links too related to above error and have checked following:
Proper host name entry in host file
No spaces in Jdveleoper installed directory name
Proxy setting in Jdeveloper: excluded localhost and ip address
Will be very thankful if anyone can help me to resolve this issue.
Thanks in advance

Don't spend to much time on this. JDev 11g is production and there will be no OC4J 11g!
--olaf

Error Integrating BOE via KM in Portal : Connection Refused

Hi
I am following the steps outlined on http://wiki.sdn.sap.com/wiki/display/BOBJ/IntegrateBOEXI3.1intoaKMNavigationintoSAPEP+portal in order to integrate BOE content into the portal via KM iViews.
I create the repository, and it shows up in the KM Content area, but as soon as I click on it, I get the following error:
java.net.ConnectException: Connection refused
I check the default trace file from NWA, and there are a bunch of error messages, starting with this one:
com.sapportals.wcm.repository.ResourceException: Invalid root sid. It must be an Integer representing the SI_ID on CMS.
I have used the default ID (23), which corresponds to the ID of the root folder in BOE. I have also tried using the ID of another folder, still with the same error message.
I have checked the security settings on the folder(s), and the user group Everyone has Full Access, so I don't think it is an access problem.
Any ideas on how I can get this working?
Cheers,
Andrew

Hi Andrew
Have you find a solution?
br
Murat

Connection refused error when trying to to lookup EJB in iAS

Hi,
I tried to write a client that uses an EJB in an 9.0.3 iAS running on windows NT SP6, and the JNDI lookup keeps failing with the following error:
javax.naming.NamingException: Lookup error: java.net.ConnectException: Connection refused: connect; nested exception is:
java.net.ConnectException: Connection refused: connect
 java.lang.Object com.evermind.server.rmi.RMIContext.lookup(java.lang.String)
 RMIContext.java:134
 java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
 InitialContext.java:345
 void Samplecom.mind.ejb.stubs.AccountComplexStubClient.main(java.lang.String[])
 AccountComplexStubClient.java:24
I am using the following properties for the lookup:
env.putContext.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
env.put(Context.SECURITY_PRINCIPAL, "ias_admin");
env.put(Context.SECURITY_CREDENTIALS, "ias_admin1");
env.put(Context.PROVIDER_URL, "ormi://localhost:23791/mindejb");
Where:
* 23791 is the port configured in the rmi.xml
* mindejb is the name of the module
* ias_admin1 is the correct password of ias_admin user
Similar properties worked for a stand alone oc4j. What have I done wrong?
Any help will be appreciated.
Thanks,
Avi

Hi -
I can resend what I think I would have said later on. No guarantees though ;-)
What you need to do is to look at the RMI port range allocated in the opmn.xml file for the OC4J instance you are trying to connect to. OPMN basically looks at the first number, and determines if the port is free. If it is, it will use it. If it's not, it will go to the next sequential number and try that, etc.
So if you have a defined port range of 3101-3200 and you only have one process, then it's a pretty safe bet (unless another rogue process has grabbed it) that the port you need will be the first one listed - 3101. If you specified two JVM processes to be started for the instance, then it's likely that 3101 and 3102 will be used.
I think that's what I'd written in the truncated text.
In our forthcoming 904 release, we're providing a port lookup service which will be able to be used by remote clients to discover the RMI ports used for OC4J instances. This will then avoid the client (and admins) needing to know and publish the specific ports used. Since OPMN itself knows which ports have been allocated, it can be queried by remote clients to find out where to connect. I've not seen the final spec, but I think this lookup will be transparent to the client in terms of code and will only require the addition of a prefix to the provider.url property used in jndi.propeties.
It's likely to be of a format such as opmn:lookup:ormi://<known-ias-host-location>.
Sorry about the truncation, it looks like that has now been rectified for the forums.
-steve-

"Connection refused" when using Java client for Web Service

I deployed a web service to Weblogic Server 7.0 running on Windows 2000. I can
use IE browser to see its WSDL perfectly but when I run the Java client, the proxy
method call generates the following error:
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:426)
at java.net.Socket.connect(Socket.java:376)
at java.net.Socket.<init>(Socket.java:291)
at java.net.Socket.<init>(Socket.java:119)
at weblogic.webservice.binding.soap.HttpClientBinding.createSocket(HttpC
lientBinding.java:412)
at weblogic.webservice.binding.soap.HttpClientBinding.createSocket(HttpC
lientBinding.java:390)
at weblogic.webservice.binding.soap.HttpClientBinding.send(HttpClientBin
ding.java:246)
at weblogic.webservice.core.handler.ClientHandler.handleRequest(ClientHa
ndler.java:34)
at weblogic.webservice.core.HandlerChain.handleRequest(HandlerChain.java
:131)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:417)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:359)
at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:225)
at weblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
181)
at weblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
207)
at CenterWSClient.main(CenterWSClient.java:73)
javax.xml.rpc.JAXRPCException: Failed to send request:java.net.ConnectException:
Connection refused: connect
at weblogic.webservice.core.handler.ClientHandler.handleRequest(ClientHa
ndler.java:37)
at weblogic.webservice.core.HandlerChain.handleRequest(HandlerChain.java
:131)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:417)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:359)
at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:225)
at weblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
181)
at weblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
207)
at CenterWSClient.main(CenterWSClient.java:73)
Exception in handler's handleRequest().
java.rmi.RemoteException: SOAP Fault:javax.xml.rpc.soap.SOAPFaultException: Conn
ection refused: connect; nested exception is:
javax.xml.rpc.soap.SOAPFaultException: Connection refused: connect
at weblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
186)
at weblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
207)
at CenterWSClient.main(CenterWSClient.java:73)
Caused by: javax.xml.rpc.soap.SOAPFaultException: Connection refused: connect
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:459)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:359)
at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:225)
at weblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
181)

In your client program, when you do "new XXX_Impl(String wsdlurl)", did you
pass in the wsdl you were hitting with browser?
-Neal
"Ray Yan" <[email protected]> wrote in message
news:[email protected]...
>
I deployed a web service to Weblogic Server 7.0 running on Windows 2000. Ican
use IE browser to see its WSDL perfectly but when I run the Java client,the proxy
method call generates the following error:
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
atjava.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:426)
at java.net.Socket.connect(Socket.java:376)
at java.net.Socket.<init>(Socket.java:291)
at java.net.Socket.<init>(Socket.java:119)
atweblogic.webservice.binding.soap.HttpClientBinding.createSocket(HttpC
lientBinding.java:412)
atweblogic.webservice.binding.soap.HttpClientBinding.createSocket(HttpC
lientBinding.java:390)
atweblogic.webservice.binding.soap.HttpClientBinding.send(HttpClientBin
ding.java:246)
atweblogic.webservice.core.handler.ClientHandler.handleRequest(ClientHa
ndler.java:34)
atweblogic.webservice.core.HandlerChain.handleRequest(HandlerChain.java
:131)
atweblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:417)
atweblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:359)
atweblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:225)
atweblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
181)
atweblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
207)
at CenterWSClient.main(CenterWSClient.java:73)
javax.xml.rpc.JAXRPCException: Failed to sendrequest:java.net.ConnectException:
Connection refused: connect
atweblogic.webservice.core.handler.ClientHandler.handleRequest(ClientHa
ndler.java:37)
atweblogic.webservice.core.HandlerChain.handleRequest(HandlerChain.java
:131)
atweblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:417)
atweblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:359)
atweblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:225)
atweblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
181)
atweblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
207)
at CenterWSClient.main(CenterWSClient.java:73)
Exception in handler's handleRequest().
java.rmi.RemoteException: SOAPFault:javax.xml.rpc.soap.SOAPFaultException: Conn
ection refused: connect; nested exception is:
javax.xml.rpc.soap.SOAPFaultException: Connection refused: connect
atweblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
186)
atweblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
207)
at CenterWSClient.main(CenterWSClient.java:73)
Caused by: javax.xml.rpc.soap.SOAPFaultException: Connection refused:connect
atweblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:459)
atweblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:359)
atweblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:225)
atweblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
181)

TNS:listener does not currently know of service requested in connect

[Oracle 10g 10.1.0.2] TNS:listener does not currently know of service requested in connect
hi,
My system is Windows XP.
Oracle 10g : 10.1.0.2.0
I can connect through sqlplus (and toad) with the following command:
sqlplus scott/tiger /
but I cannot connect with this: sqlplus scott/tiger@localhost:1521:cambridg
I am trying to connect to my database cambridg on my computer (named eclipse).
Where is the problem ? Can anyone help me here ?
This is my tnsnames.ora
# tnsnames.ora Network Configuration File: c:\oracle\product\10.1.0\Db_1\network\admin\tnsnames.ora
# Generated by Oracle configuration tools.
CAMBRIDG =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = ECLIPSE)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = cambridg)
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
And my listener.ora :
# listener.ora Network Configuration File: c:\oracle\product\10.1.0\Db_1\network\admin\listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = c:\oracle\product\10.1.0\Db_1)
(PROGRAM = extproc)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = ECLIPSE)(PORT = 1521))
A tnsping works perfect :
C:\bob>tnsping cambridg
TNS Ping Utility for 32-bit Windows: Version 10.1.0.2.0 - Production on 30-JUIL.
-2005 14:46:11
Copyright (c) 1997, 2003, Oracle. All rights reserved.
Used parameter files:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = ECLIPSE)
(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = cambridg)))
OK (20 msec)
I get the following message:
C:\>sqlplus scott/tiger@localhost:1521:cambridg
SQL*Plus: Release 10.1.0.2.0 - Production on Sam. Juil. 30 15:10:58 2005
Copyright (c) 1982, 2004, Oracle. All rights reserved.
ERROR:
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor
Also, in the services running, I can see that the listener is started and running:
OracleOraDb10g_home1TNSListener
Maybe it has something to do with the other listener, that I cannot start:
OracleOraDb10g_home1TNSListenerSID_LIST_LISTENER
Any help would be much appreciated as I am currently stucked with that.
Thanks a lot

Muhammad Nadeem wrote:
hi all,
I have the following error when try to connect the database thru form developer:
TNS:listener does not currently know of service requested in connect descriptor
any one have the solution?
Regards:
mn=================================
A couple of important points.
First, the listener is a server side only process. It's entire purpose in life is to receive requests for connections to databases and set up those connections. Once the connection is established, the listener is out of the picture. It creates the connection. It doesn't sustain the connection. One listener, with the default name of LISTENER, running from one oracle home, listening on a single port, will serve multiple database instances of multiple versions running from multiple homes. It is an unnecessary complexity to try to have multiple listeners or to name the listener as if it belongs to a particular database. That would be like the telephone company building a separate switchboard for each customer.
Additional notes on the listener: One listener is capable of listening on multiple ports. But please notice that it is the listener using these ports, not the database instance. You can't bind a specific listener port to a specific db instance. Similarly, one listener is capable of listnening on multiple IP addresses (in the case of a server with multiple NICs) But just like the port, you can't bind a specific ip address to a specific db instance.
Second, the tnsnames.ora file is a client side issue. It's purpose is for address resolution - the tns equivalent of the 'hosts' file further down the network stack. The only reason it exists on a host machine is because that machine can also run client processes.
Assume you have the following in your tnsnames.ora:
larry =
(DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = myhost)(PORT = 1521))
    (CONNECT_DATA =
      (SERVICE_NAME = curley)
)Now, when you issue a connect, say like this:
$> sqlplus scott/tiger@larrytns will look in your tnsnames.ora for an entry called 'larry'. Finding it, tns sends a request through the normal network stack to (PORT = 1521) on (HOST = myhost) using (PROTOCOL = TCP), asking for a connection to (SERVICE_NAME = curley).
Where is (HOST = myhost) on the network? When the request gets passed from tns to the next layer in the network stack, the name 'myhost' will get resolved to an IP address, either via a local 'hosts' file, via DNS, or possibly other less used mechanisms. You can also hard-code the ip address (HOST = 123.456.789.101) in the tnsnames.ora.
Next, the standard networking process delivers the message to port 1521 on myhost. Hopefully, there is a listener on myhost configured to listen on port 1521, and that listener knows about SERVICE_NAME = curley. If so, the listener will spawn a server process to act as the intermediary between your client and the database instance. Communication to the server process will be on a randomly selected available port. At that point the listener is out of the process and continues to user port 1521 to await other connection requests.
What can go wrong?
First, there may not be an entry for 'larry' in your tnsnames. In that case you get "ORA-12154: TNS:could not resolve the connect identifier specified" No need to go looking for a problem on the host, with the listener, etc. If you can't place a telephone call because you don't know the number (can't find your telephone directory (tnsnames.ora) or can't find the party you are looking for listed in it (no entry for larry)) you don't look for problems at the telephone switchboard.
Maybe the entry for larry was found, but myhost couldn't be resolved to an IP address (say there was no entry for myhost in the local hosts file). This will result in "ORA-12545: Connect failed because target host or object does not exist"
Maybe there was an entry for myserver in the local hosts file, but it specified a bad IP address. This will result in "ORA-12545: Connect failed because target host or object does not exist"
Maybe the IP was good, but there is no listener running: "ORA-12541: TNS:no listener"
Maybe the IP was good, there is a listener at myhost, but it is listening on a different port. "ORA-12560: TNS:protocol adapter error"
Maybe the IP was good, there is a listener at myhost, it is listening on the specified port, but doesn't know about SERVICE_NAME = curley. "ORA-12514: TNS:listener does not currently know of service requested in connect descriptor"
Third: If the client is on the same machine as the db instance, it is possible to connect without referencing tnsnames and without going through the listener.
Now, when you issue a connect, say like this:
$> sqlplus scott/tigertns will attempt to establish an IPC connection to the db instance. How does it know the name of the instance? It uses the current value of the enviornment variable ORACLE_SID. So...
$> export ORACLE_SID=fred
$> sqlplus scott/tigerIt will attempt to connect to the instance known as "fred". If there is no such instance, it will, of course, fail. Also, if there is no value set for ORACLE_SID, the connect will fail.
check executing instances to get the SID
[oracle@vmlnx01 ~]$ ps -ef|grep pmon|grep -v grep
oracle    4236     1 0 10:30 ?        00:00:00 ora_pmon_vlnxora1set ORACLE_SID appropriately, and connect
[oracle@vmlnx01 ~]$ export ORACLE_SID='vlnxora1
[oracle@vmlnx01 ~]$ sqlplus scott/tiger
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 22 10:42:37 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing optionsNow set ORACLE_SID to a bogus value, and try to connect
SQL> exit
[oracle@vmlnx01 ~]$ export ORACLE_SID=FUBAR
[oracle@vmlnx01 ~]$ sqlplus scott/tiger
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 22 10:42:57 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
ERROR:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux Error: 2: No such file or directory
Enter user-name: Now set ORACLE_SID to null, and try to connect
[oracle@vmlnx01 ~]$ export ORACLE_SID=
[oracle@vmlnx01 ~]$ sqlplus /scott/tiger
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 22 10:43:24 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
ERROR:
ORA-12162: TNS:net service name is incorrectly specifiedOk, that is how we get from the client connection request to the listener. What about the listener's part of all this?
The listener is very simple. It's job is to listen for connection requests and make the connection (server process) between the client and the database instance. Once that connection is made, the listener is out of the picture. If you were to kill the listener, all existing connections would continue. The listener is configured with the listener.ora file, but if that file doesn't exist, the listener is quite capable of starting up with all default values. One common mistake with the listner configuration is to specify "HOST=localhost" or "HOST=127.0.01". This is a NONROUTABLE ip address. LOCALHOST and ip address 127.0.0.1 always mean "this machine on which I am sitting". So, all computers are known as "localhost" or "127.0.0.1". If you specify this address, the listener will only be capable of receiving requests from the machine on which it is running. If you specified that address in your tnsnames file - on a remote client machine - the request would be routed to the machine on which the requesting client resides. Probably not what you want.
=====================================

Javax.mail.MessagingException: Connection refused: connect on localhost

Hello,
I am using Tomcat5.0.28 for a javamail servlet program. I am giving the hostname as localhost. After entering the input details in my html file, i get the error- "javax.mail.MessagingException: Connection refused: connect; nested exception is: java.net.ConnectException: Connection refused: connect " .
can anybody help me regarding in solving error.
Thanks.

First, you're using a very old version of JavaMail. Please upgrade. Some of the properties you're setting aren't supported in that old version.
Second, you don't need the socket factory properties, get rid of them.
Finally, it looks like you're trying to connect on port 143 using SSL. Port 143 is the non-SSL port. That's probably not going to work. Still, it looks like something is refusing to let you connect at all. If you really can telnet from the same machine your program is running on to the same server machine on port 143, then you probably have some sort of firewall that's preventing your program from connecting. Please post the entire debug output if it still fails after correcting the problems above. (Move the setDebug call to before the getStore call.)

Connection Refused: Connect

Hello again,
we installed our Portal with:
Windows 2003 + SQL Server
SAP J2EE PL23
EP6.0 and Patch 2 (us told in docs)
our problem is that when we tried to logon to our portal with sap* user nothing appears !!!!
The inicialization of our system seems to be ok....In the log appears: Portal initialization done.
After that msg appers many with the folow errors:
java.net.ConnectException: Connection refused: connect
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:350)
 at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:137)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:124)
 at java.net.Socket.<init>(Socket.java:268)
 at java.net.Socket.<init>(Socket.java:122)
 at iaik.security.ssl.SSLSocket.<init>(Unknown Source)
 at org.w3c.www.protocol.http.f.a(Unknown Source)
 at org.w3c.www.protocol.http.f.markUsed(Unknown Source)
 at org.w3c.www.protocol.http.HttpBasicServer.getConnection(Unknown Source)
 at org.w3c.www.protocol.http.HttpBasicServer.runRequest(Unknown Source)
 at org.w3c.www.protocol.http.HttpManager.runRequest(Unknown Source)
 at org.w3c.www.protocol.http.HttpURLConnection.connect(Unknown Source)
 at com.sapportals.portal.ivs.http.HttpClient.connect(HttpClient.java:323)
 at com.sapportals.portal.ivs.http.HttpClient.send(HttpClient.java:336)
 at com.sapportals.portal.yahoo.runtime.YahooHbThread.send(YahooHbThread.java:209)
 at com.sapportals.portal.yahoo.runtime.YahooHbThread.run(YahooHbThread.java:95)
java.net.ConnectException: Connection refused: connect
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:350)
 at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:137)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:124)
 at java.net.Socket.<init>(Socket.java:268)
 at java.net.Socket.<init>(Socket.java:122)
 at iaik.security.ssl.SSLSocket.<init>(Unknown Source)
 at org.w3c.www.protocol.http.f.a(Unknown Source)
 at org.w3c.www.protocol.http.f.markUsed(Unknown Source)
 at org.w3c.www.protocol.http.HttpBasicServer.getConnection(Unknown Source)
 at org.w3c.www.protocol.http.HttpBasicServer.runRequest(Unknown Source)
 at org.w3c.www.protocol.http.HttpManager.runRequest(Unknown Source)
 at org.w3c.www.protocol.http.HttpURLConnection.connect(Unknown Source)
 at com.sapportals.portal.ivs.http.HttpClient.connect(HttpClient.java:323)
 at com.sapportals.portal.ivs.http.HttpClient.send(HttpClient.java:336)
 at com.sapportals.portal.yahoo.runtime.YahooHbThread.send(YahooHbThread.java:209)
 at com.sapportals.portal.yahoo.runtime.YahooHbThread.run(YahooHbThread.java:95)
java.net.ConnectException: Connection refused: connect
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:350)
 at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:137)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:124)
 at java.net.Socket.<init>(Socket.java:268)
 at java.net.Socket.<init>(Socket.java:122)
 at iaik.security.ssl.SSLSocket.<init>(Unknown Source)
 at org.w3c.www.protocol.http.f.a(Unknown Source)
 at org.w3c.www.protocol.http.f.markUsed(Unknown Source)
 at org.w3c.www.protocol.http.HttpBasicServer.getConnection(Unknown Source)
 at org.w3c.www.protocol.http.HttpBasicServer.runRequest(Unknown Source)
 at org.w3c.www.protocol.http.HttpManager.runRequest(Unknown Source)
 at org.w3c.www.protocol.http.HttpURLConnection.connect(Unknown Source)
 at com.sapportals.portal.ivs.http.HttpClient.connect(HttpClient.java:323)
 at com.sapportals.portal.ivs.http.HttpClient.send(HttpClient.java:336)
 at com.sapportals.portal.yahoo.runtime.YahooHbThread.send(YahooHbThread.java:209)
 at com.sapportals.portal.yahoo.runtime.YahooHbThread.run(YahooHbThread.java:95)
java.net.ConnectException: Connection refused: connect
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:350)
 at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:137)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:124)
 at java.net.Socket.<init>(Socket.java:268)
 at java.net.Socket.<init>(Socket.java:122)
 at iaik.security.ssl.SSLSocket.<init>(Unknown Source)
 at org.w3c.www.protocol.http.f.a(Unknown Source)
 at org.w3c.www.protocol.http.f.markUsed(Unknown Source)
 at org.w3c.www.protocol.http.HttpBasicServer.getConnection(Unknown Source)
 at org.w3c.www.protocol.http.HttpBasicServer.runRequest(Unknown Source)
 at org.w3c.www.protocol.http.HttpManager.runRequest(Unknown Source)
 at org.w3c.www.protocol.http.HttpURLConnection.connect(Unknown Source)
 at com.sapportals.portal.ivs.http.HttpClient.connect(HttpClient.java:323)
 at com.sapportals.portal.ivs.http.HttpClient.send(HttpClient.java:336)
 at com.sapportals.portal.yahoo.runtime.YahooHbThread.send(YahooHbThread.java:209)
 at com.sapportals.portal.yahoo.runtime.YahooHbThread.run(YahooHbThread.java:95)
java.net.ConnectException: Connection refused: connect
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:350)
 at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:137)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:124)
 at java.net.Socket.<init>(Socket.java:268)
 at java.net.Socket.<init>(Socket.java:122)
 at iaik.security.ssl.SSLSocket.<init>(Unknown Source)
 at org.w3c.www.protocol.http.f.a(Unknown Source)
 at org.w3c.www.protocol.http.f.markUsed(Unknown Source)
 at org.w3c.www.protocol.http.HttpBasicServer.getConnection(Unknown Source)
 at org.w3c.www.protocol.http.HttpBasicServer.runRequest(Unknown Source)
 at org.w3c.www.protocol.http.HttpManager.runRequest(Unknown Source)
 at org.w3c.www.protocol.http.HttpURLConnection.connect(Unknown Source)
 at com.sapportals.portal.ivs.http.HttpClient.connect(HttpClient.java:323)
 at com.sapportals.portal.ivs.http.HttpClient.send(HttpClient.java:336)
 at com.sapportals.portal.yahoo.runtime.YahooHbThread.send(YahooHbThread.java:209)
 at com.sapportals.portal.yahoo.runtime.YahooHbThread.run(YahooHbThread.java:95)
What is this problem ?
Can someone help us ?
Thanks in advanced.

but i am not send to the client when i accept the client connection immediately ,It doesn't matter when you send to the client. The answer is still the same. You send to a client via the socket you accepted from that client. That's what it's for.
for example :
first client_A connect to Server (port 2222) , than Client_B connect to Server (port 2222) , finally Client_C connect to Server (port 2222)You don't need to keep telling me the port number. If the ServerSocket is listening at port 2222 they will all connect via port 2222. They don't have any choice about that.
and all not close the connection, but if I want to send some msg to Client_B from Server, how can i send the msg to client_B ?Via the socket you accepted from client B. I've already answered that.
it's just like you said "you don't have to do anything about that. " ?Is that a question?
You don't seem to have much idea about client-server socket programming. Have you read the Custom Networking tutorial?

HTTP3068: Error receiving request ip_address (Connection refused)

Similar Messages

Maybe you are looking for