Skip to Main Content
Forums

Java Programming

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Proxy Error 403 from SAP webservice invocation

User_19BPUNov 16 2019

Hi,

I am connecting to an SAP service from Java application, here the request is send succdessfully from Java application but the response from SAP is not coming back instead we are getting the below error.

      com.sun.xml.ws.client.ClientTransportException: The server sent HTTP status code 403: Proxy Error

       at com.sun.xml.ws.transport.http.client.HttpTransportPipe.checkStatusCode(HttpTransportPipe.java:332)

       at com.sun.xml.ws.transport.http.client.HttpTransportPipe.createResponsePacket(HttpTransportPipe.java:274)

Please let me know what could be the issue here , only from application end we are getting this issue even after enabling the port and firewall to connect to this service/server and the telnet connectivity to the SAP service/server is working fine and also it is working fine when we connect from SOAP UI.

Please let me know what is causing this issue and it is very strange when we invoke this service from application it is not working.

Thanks

Comments

Hello,
You mentioned that the unique constraint is on the doctor_id,name so the update statement might be trying to change the p1_patient_name to a value that was already inserted. During the execution of the update statement try to check what value of p1_patient_name is getting set.

Eslam_Elbyaly

Impossible. The name, doctor_id already exists. It can't exist if there's a similar name, doctor_id

Eslam_Elbyaly

I tried commenting the "IF :P1_PATIENT_ID IS NULL...." part, and the weird part is that the ARP process threw error " ORA-01407 - can not change test.patient_id to null". Which means that it issues update statement with p1_patient_id set to null when it's not. I am sure it's not because I even changed it to a number item instead of a hidden one and it has a value.
If I do not comment the "IF....." part, and disable the unique constraint in patient table, I get a new record inserted, which means that the "IF..." part executes. It's a very weird thing to happen!

Eslam_Elbyaly

The message in Arabic means, p1_patient_id must have a value. See p1_patient_id below has a value!
image.png

Eslam_Elbyaly

I found the culprit and I can assure you it's definitely a bug @john-snyders-oracle. There's a "loseFocus" DA on p1_patient_name with the same code of the "onUpdate" DA(Set value> select statement - I mentioned it in the main question)...
select id from patient where name = :p1_patient_name ;
. I created it because user could write the name instead of choosing it from the lov. In this case, the "onUpdate" DA won't fire.
I am focusing on the first item in the page which is p1_patient_id. The lose focus trigger fires when click SAVE because the cursor is in p1_patient_id then. The weird thing is that, even if it fires, it should set the value of p1_patient_id again not setting it to null. Plus it's not get set to null. I can still see the value in p1_patient_id.
When I set the lose focus DA to Never, the error did not show anymore.
I think this assures it's a very bad bug. The question now is, is there a workaround?
P.S. I don't think this problem exists on APEX 22.1.3 on apex.oracle.com. I tried it but not sure if I mimicked it correctly.

1 - 5

Post Details

Added on Nov 16 2019
0 comments
509 views