Support Article
com.pega.apache.axis2.AxisFault: Transport error: 303
SA-8046
Summary
User is trying to do a command line deployment for Pega7 by referring to the Product migration command line utility guide but getting the error.
Error Messages
2015-03-24 17:05:36,827 (grate.products.MigrateProducts) ERROR Exception has occured while executing the requested action
com.pega.apache.axis2.AxisFault: Transport error: 303 Error: See Other
at com.pega.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:312)
at com.pega.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:200)
at com.pega.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:76)
at com.pega.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:400)
at com.pega.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:224)
at com.pega.apache.axis2.engine.AxisEngine.send(AxisEngine.java:440)
at com.pega.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:402)
at com.pega.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at com.pega.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at com.pega.pegarules.migrate.products.service.MigrationServiceInvoker.invokeService(MigrationServiceInvoker.java:95)
at com.pega.pegarules.migrate.products.MigrateProducts.handleRequest(MigrateProducts.java:221)
at com.pega.pegarules.migrate.products.MigrateProducts.main(MigrateProducts.java:159)
Steps to Reproduce
execute the script
./productMigration.sh addTarget -url http://<HOST>:<PORT>/prweb/PRServlet -user [email protected] -pwd install -https false -host <HOST>-port <PORT> -context prweb -targUser casysadmin -targPwd install
./productMigration.sh showTargets -url http://<HOST>:<PORT>/prweb/PRServlet -user [email protected] -pwd install
./productMigration.sh showProducts -url http://<HOST>:<PORT>/prweb/PRServlet -user [email protected] -pwd install
Root Cause
The root cause of this problem is an error/omission in product documentation. URL should point to PRSOAPServlet instead of PRServlet
Resolution
The explanation for this behavior is as follows: Change Target URL to point to PRSOAPServlet.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.