- 3,708,960 Users
- 2,241,165 Discussions
- 7,840,722 Comments
Forum Stats
Discussions
Categories
- 22 Industry Applications
- 3.2K Intelligent Advisor
- 4 Insurance
- 754 On-Premises Infrastructure
- 253 Analytics Software
- 22 Application Development Software
- 1.7K Cloud Platform
- 700.4K Database Software
- 17.4K Enterprise Manager
- 5 Hardware
- 110 Infrastructure Software
- 70 Integration
- 45 Security Software
b2b-50079 transport error for ACK in oracleb2b

Hi
We are getting b2b-50079 transport error for ACK send to one of our partner via oracle b2b .
Any suggestion on how we can handle this ?
Do you recommend increase the https timeout in WLS will solve this ?
Answers
can you please give more details on what document / transport protocols are you using along with usecase ?
Please paste the error log from the console
Regards,
Dheeraj
it's rosettanet document with https protocol via oracle b2b
can you please paste the error log ( preferrabley in trace:32 mode)
Alternatively, you may want to test with just http
ideally, the outbound ack (not the business Acknowledgment) will be sent back by B2B , to the same URL where the message has come from.
Regards,
Dheeraj
my log configuration as below - do i need to change this to trace:32 mode -Once done - where do we get the oracle b2b logs ?
The error message is given below and doesn't fail/time out for all but few of the ACK fails/timeout .
error message:
Before executing the test change the Oracle.soa.b2b (parent) to Trace:32 and run the test.
You can find the diagnostic log at
$MIDDLEWARE_HOME/user_projects/domains/<domain Name>/servers/soa_server1/logs/soa_server1-diagnostic.log
With the error, it looks like it is not able to connect to the end system. Navigate to the wire message of the particular message and take the URL. Paste the same URL in a browser and see if you are getting the response. also please connect with partner to check the URL, if it is correct or not
Regards,
Dheeraj
There is no issue with Partner URL and it does works - but fails/time out for few
This does not look like an issue with B2B. You may want to check the network, or the reason for intermittent timeout