Skip to main content
M
mshostak1-Visitor
1-Visitor
March 20, 2017
Question

Axeda - Invoke of class java.io.DataOutputStream#writeBytes not allowed

  • March 20, 2017
  • 1 reply
  • 1527 views

HI All,

         I have an groovy script on an Axeda server calling restful interface on a ThingWorx server. Using a HttpURLConnection and DataOutputStream. It used to work but after some work to our server I'm now getting an exception (below) indicating I am no longer able to write data. Anyone have any ideas what might be causing this?

JEP Expression: Invoke of class java.io.DataOutputStream#writeBytes not allowed: com.singularsys.jep.EvaluationException: Invoke of class java.io.DataOutputStream#writeBytes not allowed

at com.axeda.drm.rules.functions.ExecuteCustomObject.eval(ExecuteCustomObject.java:195)

at com.singularsys.jep.standard.FastEvaluator.visitFun(Unknown Source)

at com.singularsys.jep.standard.FastEvaluator.nodeAccept(Unknown Source)

at com.singularsys.jep.standard.FastEvaluator.evaluate(Unknown Source)

at com.singularsys.jep.Jep.evaluate(Unknown Source)

at com.axeda.drm.rules.engine.JepExpressionParser.evaluate(JepExpressionParser.java:322)

at com.axeda.drm.rules.engine.ExpressionRule.evaluate(ExpressionRule.java:168)

at com.axeda.drm.rules.ExpressionEngineImpl.evaluateExpressionRule(ExpressionEngineImpl.java:424)

at com.axeda.drm.rules.ExpressionEngineImpl.evaluate(ExpressionEngineImpl.java:380)

at com.axeda.drm.rules.ExpressionEngineImpl.evaluate(ExpressionEngineImpl.java:105)

at com.axeda.drm.rules.RulesManagerImpl.evaluate(RulesManagerImpl.java:840)

at com.axeda.drm.rules.RulesExecutorImpl.run(RulesExecutorImpl.java:63)

at com.axeda.drm.rules.ThreadWatcher.runWithDeadline(ThreadWatcher.java:159)

at com.axeda.drm.eda.handler.RulesEventProcessor.processRuleEvent(RulesEventProcessor.java:132)

at com.axeda.drm.eda.handler.RulesEventProcessor.processEvent(RulesEventProcessor.java:88)

at com.axeda.drm.eda.handler.RulesEventProcessor.processEvent(RulesEventProcessor.java:71)

at com.axeda.drm.eda.handler.TriggerableItemEventProcessor.processEvent(TriggerableItemEventProcessor.java:86)

at com.axeda.common.eda.jms.DefaultJMSEventConsumer.onMessage(DefaultJMSEventConsumer.java:239)

at org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:535)

at org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:495)

at org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:467)

at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:325)

at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:263)

at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1058)

at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1050)

at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:947)

at java.lang.Thread.run(Thread.java:745)

Thanks in advance.

    1 reply

    T
    tkawasaki5-Regular Member
    5-Regular Member
    March 22, 2017

    According to the document "Available APIs for Custom Objects", DataOutputStream is not available by default. I assume you used to be able to call it because your Code Access Policy in instance.properties was modified so.

    You might want to compare the current instance.properties with the backup.

    Takaaki

    Terms & ConditionsAccessibility statement