Not able to connect

We are not able to connect to http

://xoa.xpedite.co.uk/soap/sync to submit any email job in testign env.

It gives connection timeout error.

The same was being used in 2011 without any issue, We have not chnages any proxy setting or any other things in our application.

Our aplication is live and needtomake some changes in test env

Please update us if any cnages.

My user name is buildToken.easylink.username=

SG/DBAG

Find more posts tagged with

Comments

thuneke

This worked fine for me:

http://xoa.xpedite.co.uk/soap/sync

Sent a test job

- <JobSubmitResult xmlns="http://premconn.premiereconnect.com/2007/02">- <Status> <StatusCode>0</StatusCode> <SubmissionTime>2012-07-16T14:21:20.581Z</SubmissionTime> <CompletionTime>2012-07-16T14:21:20.875Z</CompletionTime> </Status>- <MessageResult>- <Status> <StatusCode>0</StatusCode> <StatusMessage>OK</StatusMessage> <SubmissionTime>2012-07-16T14:21:20.708Z</SubmissionTime> <CompletionTime>2012-07-16T14:21:20.875Z</CompletionTime> </Status> Try typing it again. Click on the above and you should receive a http 500 error. That means it is functioning correctly.

ranjabh

I am sorry by mistake i gace prod link

The following link is not working which is test env

http

//xoa.pt.premiereglobal.com/soap/sync

username=

pt/sg/db

thuneke

The pt system was consolidated to our test2 system. You will need to contact your Sales/PreSales person and have them get you credentials for the test2 system. They will also provide the URL.

ranjabh

So If we start using

https://test2messaging.easylink.com/soap/sync, do we need to chnage the wsdl files as well.

We are using 02.wsdl and 10.wsdl

And URLs as below:

url.jobSubmit=http://premconn.premiereconnect.com/2007/02

url.jobStatus=

http:

//premconn.premiereconnect.com/JobDeliveryStatus/2008/10

Do we need tomake changes in the above details once we migrate to test2 env

skamens

You will not need to change your WSDL's to use the test2messaging.easylink.com URL for submission.

Please make sure that you do not retrieve the WSDL's at runtime, however, as they may not be available from the above URL's. The WSDL should be loaded and retained locally.

ranjabh

I am getting the following Exception. wsdls are being accessed directly from local path

SEVERE: Failed to create WsdlDefinitionFeature for wsdl location: file:/opt/dap/domains/ap0497/int/domain/instance-config/properties/10.wsdl, error: com.sun.xml.ws.wsdl.parser.InaccessibleWSDLException, message: 2 counts of InaccessibleWSDLException.

Jul 19, 2012 6:34:35 PM weblogic.wsee.jaxws.framework.policy.advertisementimpl.AdvertisementHelperImpl registerExtension
WARNING: Registering oracle.j2ee.ws.wsdl.extensions.addressing.AddressingExtensionRegistry extension failed; java.lang.ClassNotFoundException: oracle.j2ee.ws.wsdl.extensions.addressing.AddressingExtensionRegistry
Jul 19, 2012 6:34:35 PM weblogic.wsee.jaxws.spi.WLSServiceDelegate addWsdlDefinitionFeature
SEVERE: Failed to create WsdlDefinitionFeature for wsdl location: file:/opt/dap/domains/ap0497/int/domain/instance-config/properties/10.wsdl, error: com.sun.xml.ws.wsdl.parser.InaccessibleWSDLException, message: 2 counts of InaccessibleWSDLException.

Jul 19, 2012 6:34:36 PM weblogic.wsee.jaxws.framework.policy.advertisementimpl.AdvertisementHelperImpl registerExtension
WARNING: Registering oracle.j2ee.ws.wsdl.extensions.addressing.AddressingExtensionRegistry extension failed; java.lang.ClassNotFoundException: oracle.j2ee.ws.wsdl.extensions.addressing.AddressingExtensionRegistry
Jul 19, 2012 6:34:36 PM weblogic.wsee.jaxws.spi.WLSServiceDelegate addWsdlDefinitionFeature
SEVERE: Failed to create WsdlDefinitionFeature for wsdl location: file:/opt/dap/domains/ap0497/int/domain/instance-config/properties/10.wsdl, error: com.sun.xml.ws.wsdl.parser.InaccessibleWSDLException, message: 2 counts of InaccessibleWSDLException.

thuneke

It looks like the local path may not be right - pointing to a non-existent file maybe or a permissions issue. Is it possible that

"file:/opt/dap/domains/...."

should be

"file:///opt/dap/domains/..." (three slashes)?

ranjabh

There is no issue with local path...so you can ignore theissue with /// slashes...I can confirm that local path is workignfine in prod as well....and its working for last 1 yr...

thuneke

Something has changed in your test environment! The only change you needed to make was the test URL the application was pointing at. Every error is saying it cannot find the WSDL where it is specified. That is not something we can really help with. The WSDL's are not being found.

Just some thoughts. Check the WSDL name, looking for 10.wsdl. Confirm the path. Make sure it is still there.

ranjabh

HI I am not able to get the status of the messages.

Can you please check why i am not able to receive the status for reference:

948070~0ACD321E-1748-120720172126241

skamens

The processing ID shown above (0ACD321E-1748-120720172126241) gives the job submit request, which returned the following JobId:

<JobId>

<XDN>flusme</XDN>

</JobId>

Be sure that you specify the XDN correctly when you query for status. My guess is that you are specfying an XDN of "test2" which is not correct for this type of job.

ranjabh

As per previous communication we were not able to connect to PT system so we are connecting now to test 2 system.

we are still using the old wsdl file to submit teh request and getting the sttaus.

For jobSubmit we are using http://premconn.premiereconnect.com/2007/02 which works fine.

But when we are querying for

Just wondering if any other change s i sreqd other than server details. we have not faced this issues last year and the code also remains same from our side

ranjabh

As per previous communication we were not able to connect to PT system so we are connecting now to test 2 system.

we are still using the old wsdl file to submit teh request and getting the sttaus.

For jobSubmit we are using http://premconn.premiereconnect.com/2007/02 which works fine.

But when we are querying for

Just wondering if any other change s i sreqd other than server details. we have not faced this issues last year and the code also remains same from our side

skamens

Your message appears to be cut off - what are you querying for that you are unable to retrieve?

As indicated previously, you shouldn't have to change anything else but the URL you use to connect and the credentials.

If you are having trouble, please provide more details.

ranjabh

I was asked to use test2 as domain name with the new test server.

When I used flusme as domain name with test server the delivery status worked fine.

thuneke

The correct domain to use when it is needed in a Request is the XDN (domain name) returned in the Submit result along with the MRN (job number) returned.