Error tying to login to CMS as a scheduled task

Rhythmyx Technical Discussion
1

We have a webservice application that creates content items in the Rhythmyx CMS. We would like to setup this module as a scheduled job. I have made all the needed changes/ updates. I have registered the task.
The scheduled task is registered in the admin tab of the CMS. When I run this scheduled task, I am getting exception during the login. However, when I run it as a Java appication thru my eclipse, it works perfectly fine. The exception is as follows:

2012-08-14 16:50:34,306 INFO [STDOUT] Invoking NewsFeed Task…1
2012-08-14 16:50:34,332 INFO [STDOUT] LOGGING IN…
2012-08-14 16:50:34,379 INFO [STDOUT] ABOUT TO LOGGING IN…
2012-08-14 16:50:55,514 ERROR [STDERR] AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.net.ConnectException: Connection timed out: connect
faultActor:
faultNode:
faultDetail:
{WebServices - Axis}stackTrace:java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:153)
at org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:120)
at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:191)
at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:404)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at com.percussion.webservices.security.SecuritySOAPStub.login(Unknown Source)
at com.percussion.webservices.PSWsUtils.login(PSWsUtils.java:329)
at com.owh.healthyday.feed.loader.NewsFeedLoader.login(NewsFeedLoader.java:111)
at com.owh.healthyday.task.ScheduledFeedTask.getArticles(ScheduledFeedTask.java:45)
at com.owh.healthyday.task.ScheduledFeedTask.perform(ScheduledFeedTask.java:29)
at com.percussion.services.schedule.impl.PSTaskAdapter.o00000(Unknown Source)
at com.percussion.services.schedule.impl.PSTaskAdapter.runJob(Unknown Source)
at com.percussion.services.schedule.impl.PSSchedulingService$_b.run(Unknown Source)

Not sure what is the problem. When I googled, it appears that it could be a firewall/ proxy issue. However, what I dont understand is that I am able to work fine outside thru eclipse, but the problem is happening when the code is sitting the Percussion CMS Server itself.

thanks
Manvinder

2

Have you tried a regular wget or telnet from the server to the internet ( I am assuming the feed is external ). If it is windows you may need to test a browser from the box or through remote desktop. I know a lot of times production servers are set up to deny outbound http connections to the outside internet for security, and a specific firewall rule would need to be set up to allow this. As you say it also could be that connection to the outside internet needs a connection through a proxy. There would need to be some configuration in the api calls used in the stack to define what that proxy is, this may require a code change to define these, unfortunately PSWsUtils.login does not currently allow for proxy setup.