Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Workflows are stalling for some users, but working for others....
dchristie
TS 6.5
Solaris 9
We are running into an issue that has us and Support stumped at the moment. Our workflows run a custom java program to attach a blank DCR as one of the first tasks in the workflow. For some reason, some users are able to run the program just fine, but for others the java app is throwing an error and the worflow stalls. Unix team has investigated permissions and groups, ldap groups, and directory ownership and they look just fine.
The Interwoven API is throwing a Service context has no accessor authentication error.
com.interwoven.api.service.IWService$Context$NoAccessorAuthenticationException: Service context has no accessor authentication.
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:240)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:215)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:117)
at com.interwoven.api.workflow.IWWorkFlowRemoterImpl_Stub.lookupById(Unknown Source)
at com.interwoven.api.workflow.IWWorkFlow.lookupById(IWWorkFlow.java:165)
at iceraj.interwoven.util.Job.init(Job.java:37)
at iceraj.interwoven.util.Job.(Job.java:27)
at iceraj.interwoven.util.ExternalTask.(ExternalTask.java:38)
at com.interwoven.cso.interval.workflow.AttachDCR.(AttachDCR.java:25)
at java.lang.reflect.Constructor.newInstance(Native Method)
at iceraj.interwoven.util.ExternalTask.main(ExternalTask.java:96)
at com.interwoven.cso.interval.workflow.AttachDCR.main(AttachDCR.java:131)
com.interwoven.api.service.IWService$Context$NoAccessorAuthenticationException: Service context has no accessor authentication.
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:240)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:215)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:117)
at com.interwoven.api.workflow.IWTaskRemoterImpl_Stub.lookupById(Unknown Source)
at com.interwoven.api.workflow.IWTask.lookupById(IWTask.java:359)
at iceraj.interwoven.util.Task.init(Task.java:42)
at iceraj.interwoven.util.Task.(Task.java:31)
at iceraj.interwoven.util.ExternalTask.(ExternalTask.java:39)
at com.interwoven.cso.interval.workflow.AttachDCR.(AttachDCR.java:25)
at java.lang.reflect.Constructor.newInstance(Native Method)
at iceraj.interwoven.util.ExternalTask.main(ExternalTask.java:96)
at com.interwoven.cso.interval.workflow.AttachDCR.main(AttachDCR.java:131)
java.lang.NullPointerException
at iceraj.interwoven.util.Job.getVariable(Job.java:43)
at com.interwoven.cso.interval.workflow.AttachDCR.(AttachDCR.java:30)
at java.lang.reflect.Constructor.newInstance(Native Method)
at iceraj.interwoven.util.ExternalTask.main(ExternalTask.java:96)
at com.interwoven.cso.interval.workflow.AttachDCR.main(AttachDCR.java:131)
[VERBOSE:20091008223324] start
java.lang.NullPointerException
at iceraj.interwoven.util.Job.getVariable(Job.java:43)
at com.interwoven.cso.interval.workflow.AttachDCR.run(AttachDCR.java:52)
at iceraj.interwoven.util.ExternalTask.main(ExternalTask.java:97)
at com.interwoven.cso.interval.workflow.AttachDCR.main(AttachDCR.java:131)
java.lang.RuntimeException: task is not external task
at iceraj.interwoven.util.Task.callback(Task.java:148)
at com.interwoven.cso.interval.workflow.AttachDCR.run(AttachDCR.java:84)
at iceraj.interwoven.util.ExternalTask.main(ExternalTask.java:97)
at com.interwoven.cso.interval.workflow.AttachDCR.main(AttachDCR.java:131)
I think it's obvious something must of changed in our environment, but we can't seem to track down what it is. I'd hedge my bets on the LDAP system, but it all checks out for now. Hmm...
Find more posts tagged with
Comments
Adam Stoller
One thing you might check is with regard to logging. If your program logs diagnostic information into a file somewhere - it might be the permissions on
that
directory and/or file that causes problems.
Somehow I don't think this is the actual issue, but it's worth verifying it before ruling it out completely.