Siebel BIP Report Scheduling Fails With "java.net.ConnectException: Connection refused (Connection refused)" Error In BIPublisher.log
(Doc ID 3040529.1)
Last updated on AUGUST 11, 2024
Applies to:
Siebel Reports - Version 17.0 [IP2017] and laterInformation in this document applies to any platform.
Symptoms
When attempting to run reports through the Siebel BIP Reports scheduling, it's failing and the following errors are being captured in the BIPublisher.log
BIPublisher.log:
[2024-07-24T10:31:44.478+03:00] [bi_server1] [NOTIFICATION] [] [oracle.xdo] [tid: 215] [userId: weblogic] [ecid: 0205901f-ad96-4cfc-baaf-95e358f6276d-0000000c,0:604:1:26] [APP: bipublisher] [partition-name: DOMAIN] [tenant-name: GLOBAL] [2024-07-24T10:31:44.478+03:00][dp id:682104377][sch info:JobId:1042[ESS RequestId:null]]javax.xml.soap.SOAPException: Message send failed: Connection refused (Connection refused)[[
at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.post2(HttpSOAPConnection.java:682)
at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection$PrivilegedPost.run(HttpSOAPConnection.java:1533)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.call2(HttpSOAPConnection.java:346)
at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:143)
at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:136)
at oracle.xdo.dataengine.datasource.webservice.WSService.sendMessage(WSService.java:955)
at oracle.xdo.dataengine.datasource.webservice.WSService.execute(WSService.java:410)
at oracle.xdo.dataengine.datasource.webservice.WSSoapRequest.execute(WSSoapRequest.java:61)
at oracle.xdo.dataengine.datasource.webservice.ComplexWSCall.execute(ComplexWSCall.java:210)
at oracle.xdo.dataengine.datasource.XMLStatement.executeWS(XMLStatement.java:572)
at oracle.xdo.dataengine.datasource.ThreadExecutor.process(ThreadExecutor.java:95)
at oracle.xdo.dataengine.datasource.ThreadExecutor.run(ThreadExecutor.java:62)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.post2(HttpSOAPConnection.java:682)
at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection$PrivilegedPost.run(HttpSOAPConnection.java:1533)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.call2(HttpSOAPConnection.java:346)
at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:143)
at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:136)
at oracle.xdo.dataengine.datasource.webservice.WSService.sendMessage(WSService.java:955)
at oracle.xdo.dataengine.datasource.webservice.WSService.execute(WSService.java:410)
at oracle.xdo.dataengine.datasource.webservice.WSSoapRequest.execute(WSSoapRequest.java:61)
at oracle.xdo.dataengine.datasource.webservice.ComplexWSCall.execute(ComplexWSCall.java:210)
at oracle.xdo.dataengine.datasource.XMLStatement.executeWS(XMLStatement.java:572)
at oracle.xdo.dataengine.datasource.ThreadExecutor.process(ThreadExecutor.java:95)
at oracle.xdo.dataengine.datasource.ThreadExecutor.run(ThreadExecutor.java:62)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
The issue can be reproduced at will with the following steps:
1. Setup Siebel 23.6 and Integrate with BIP.
2. Configure Siebel reports and Scheduling functionality.
3. Generate reports through the Siebel BIP Report scheduling.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |