cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

error for email notification job

Former Member

on ‎10-15-2014 3:13 AM

0 Kudos

HI

I would to ask if anyone familiar with the below error which i encounter for one my job parameter. The way i setting this paramet is as below .

JCS-122021: Could not evaluate default value for parameter: Parameter waitEvents for job

JCS-122021: Could not evaluate default value for parameter: Parameter waitEvents for job 3365869

at com.redwood.scheduler.model.method.impl.JobParameterMethodImpl.evaluateDefaultValueInt(JobParameterMethodImpl.java:658)

at com.redwood.scheduler.model.method.impl.JobParameterMethodImpl.setInValueToDefault(JobParameterMethodImpl.java:141)

at com.redwood.scheduler.model.method.impl.JobParameterMethodImpl.prepareInt(JobParameterMethodImpl.java:93)

at com.redwood.scheduler.model.JobParameterImpl.prepareInt(JobParameterImpl.java:1129)

at com.redwood.scheduler.model.method.impl.JobMethodImpl.initializeParameters(JobMethodImpl.java:3384)

at com.redwood.scheduler.model.method.impl.JobMethodImpl.initializeNonStepJob(JobMethodImpl.java:3334)

at com.redwood.scheduler.model.method.impl.JobDefinitionMethodImpl.performPrepare(JobDefinitionMethodImpl.java:932)

at com.redwood.scheduler.model.method.impl.JobDefinitionMethodImpl.prepareInt(JobDefinitionMethodImpl.java:856)

at com.redwood.scheduler.model.JobDefinitionImpl.prepareInt(JobDefinitionImpl.java:2593)

at com.redwood.scheduler.model.method.impl.JobDefinitionMethodImpl.prepareInt(JobDefinitionMethodImpl.java:851)

at com.redwood.scheduler.model.method.impl.JobDefinitionMethodImpl.prepareInt(JobDefinitionMethodImpl.java:833)

at com.redwood.scheduler.model.JobDefinitionImpl.prepare(JobDefinitionImpl.java:2577)

at com.redwood.scheduler.ui.submit.MetaSubmitPage.submitJobDefinition(MetaSubmitPage.java:743)

at com.redwood.scheduler.ui.meta.actions.MetaJobDefinitionSubmitAction.performModelAction(MetaJobDefinitionSubmitAction.java:112)

at com.redwood.scheduler.ui.meta.MetaModelAction.performModelAction(MetaModelAction.java:207)

at com.redwood.scheduler.ui.meta.actions.MetaMultiAction$MultiAction.performModelAction(MetaMultiAction.java:92)

at com.redwood.scheduler.ui.model.impl.FormImpl.modelActions(FormImpl.java:748)

at com.redwood.scheduler.ui.model.impl.LifeCycle.run(LifeCycle.java:226)

at com.redwood.scheduler.ui.servlet.Servlet.handleRequest(Servlet.java:98)

at com.redwood.scheduler.ui.servlet.Servlet.doPost(Servlet.java:54)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)

at com.redwood.scheduler.module.impl.ModuleFilter.doFilter(ModuleFilter.java:157)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)

at com.redwood.scheduler.security.filter.SecurityFilter.doFilter(SecurityFilter.java:708)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)

at com.redwood.scheduler.servlet.RequestCharsetFilter.doFilter(RequestCharsetFilter.java:197)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:432)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)

at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)

at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)

at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)

at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

Caused by: com.redwood.scheduler.script.api.ScriptEngineEvaluationException: Invalid identifier: waitEvents.EVT_EDI_ITSD_MAIL.raiserComment

at com.redwood.scheduler.script.rel.impl.RELScript.evaluate(RELScript.java:67)

at com.redwood.scheduler.apiint.model.script.ScriptRunner.runScript(ScriptRunner.java:32)

at com.redwood.scheduler.apiint.model.script.ScriptRunner.runREL(ScriptRunner.java:41)

at com.redwood.scheduler.model.method.impl.JobParameterMethodImpl.evaluateDefaultValue(JobParameterMethodImpl.java:701)

at com.redwood.scheduler.model.method.impl.JobParameterMethodImpl.evaluateDefaultValueInt(JobParameterMethodImpl.java:654)

... 66 more

Caused by: com.redwood.scheduler.script.rel.parser.RELException: Invalid identifier: waitEvents.EVT_EDI_ITSD_MAIL.raiserComment

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.visit(RELEvaluateVisitor.java:183)

at com.redwood.scheduler.script.rel.parser.ASTIdentifier.jjtAccept(ASTIdentifier.java:22)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.visitChildren(RELEvaluateVisitor.java:136)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.visit(RELEvaluateVisitor.java:395)

at com.redwood.scheduler.script.rel.parser.ASTPrimaryExpression.jjtAccept(ASTPrimaryExpression.java:14)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.evaluateUnary(RELEvaluateVisitor.java:246)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.visit(RELEvaluateVisitor.java:353)

at com.redwood.scheduler.script.rel.parser.ASTUnaryExpression.jjtAccept(ASTUnaryExpression.java:14)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.evaluateBinary(RELEvaluateVisitor.java:196)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.visit(RELEvaluateVisitor.java:346)

at com.redwood.scheduler.script.rel.parser.ASTMultiplicativeExpression.jjtAccept(ASTMultiplicativeExpression.java:14)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.evaluateBinary(RELEvaluateVisitor.java:196)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.visit(RELEvaluateVisitor.java:339)

at com.redwood.scheduler.script.rel.parser.ASTAdditiveExpression.jjtAccept(ASTAdditiveExpression.java:14)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.evaluateBinary(RELEvaluateVisitor.java:196)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.visit(RELEvaluateVisitor.java:332)

at com.redwood.scheduler.script.rel.parser.ASTRelationalExpression.jjtAccept(ASTRelationalExpression.java:14)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.evaluateBinary(RELEvaluateVisitor.java:196)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.visit(RELEvaluateVisitor.java:325)

at com.redwood.scheduler.script.rel.parser.ASTEqualityExpression.jjtAccept(ASTEqualityExpression.java:14)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.evaluateLogical(RELEvaluateVisitor.java:209)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.visit(RELEvaluateVisitor.java:318)

at com.redwood.scheduler.script.rel.parser.ASTLogicalANDExpression.jjtAccept(ASTLogicalANDExpression.java:14)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.evaluateLogical(RELEvaluateVisitor.java:209)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.visit(RELEvaluateVisitor.java:311)

at com.redwood.scheduler.script.rel.parser.ASTLogicalORExpression.jjtAccept(ASTLogicalORExpression.java:14)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.visitChildren(RELEvaluateVisitor.java:136)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.visit(RELEvaluateVisitor.java:304)

at com.redwood.scheduler.script.rel.impl.RELScript.evaluate(RELScript.java:59)

... 70 more

Caused by: com.redwood.scheduler.api.scripting.NoSuchIdentifierException: No such identifier :: raiserComment :: Event is not raised

at com.redwood.scheduler.apiint.model.script.JobWaitEventScriptObjectImpl.getMember(JobWaitEventScriptObjectImpl.java:24)

at com.redwood.scheduler.apiint.model.script.JobWaitEventsScriptObjectImpl.getMember(JobWaitEventsScriptObjectImpl.java:12)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.valueOf(RELEvaluateVisitor.java:483)

at com.redwood.scheduler.script.rel.impl.RELEvaluateVisitor.visit(RELEvaluateVisitor.java:179)

Show replies
Show replies
Answer

Accepted Solutions (0)

Answers (7)

Answers (7)

former_member256534
Explorer
‎04-21-2016 12:06 PM
0 Kudos

Hi Chris,

Has there been any solution to this issue?

Show replies
Show replies
h_carpenter
Active Contributor
‎04-21-2016 7:27 PM
0 Kudos

Hi Mikael,

Actually, looking at the previous two, these were different issues ...

I think Chris Wong had not set the parameter 'runtime', so his problem was then fixed - I can only assume so, because he did not come back :-(.

Hariharan Palanisamy had a problem where he was trying to access the event info from the job definition, not the chain. If you put a WaitEvent on the chain, then I think you need to reference the

wait event in the parameter mapping (chain editor), not as default value on the job definition/process definition that the chain calls. That is what I think was going on, here ... not sure, though.

What is your precise problem, you might want to open a new thread on the subject ... it is better than hijacking threads like this, we have had two different (but similar) issues here already ;-).

What would help is a few screenshots and the full error stack ... make a small test case where you reproduce the problem, try to keep it as simple as possible, and use non-identifiable values (no company/customer details).

Best regards,

HP

Message was edited by: h. Carpenter "It works for me, but then again, I am lucky!"

former_member256534
Explorer
‎04-22-2016 7:52 AM
0 Kudos

Thanks for your answer HP.

I have the same issue as Chris, I try to use the chain parameter =waitEvents.<event name>.raiserComment and yes my parameter is also set to Display but I'm not able to find where to change to runtime in BPA version 9.0.15.1

h_carpenter
Active Contributor
‎04-22-2016 2:46 PM
0 Kudos

Hi Mikael,

In 9.0.15, go to "Definitions > Processes" (for process definitions) or "Definitions > Chains" (for chains), select "edit" from the context menu of "Monitoring_Batch_Runtime_FABD". On the "Parameters" tab, locate and select the parameter "ZJOB_NAME", in the lower pane, right at the end, you have the "Parameter Options" field, there you have "Runtime".

Note that it is not necessary for the parameter to be Display, it "has to" be Runtime, though.

Regards,

HP

Message was edited by: h. Carpenter Added instructions for chains, as I noticed you mentioned chain parameter. Basically, you just edit the chain or process definition, on the parameters tab, you have the all the parameter properties.

former_member256534
Explorer
‎04-25-2016 8:38 AM
0 Kudos

Thanks for the education! I use the parameter in a chain to fetch the job name where the max runtime event was triggered from. Now I only see the job id and not the name.

Maximum runtime limit Maximum of 0:00:01.000 for process 3859889 reached. Raised event for process 3859889.

I'm sure I have been able to add the job name to the text before.

Former Member
‎12-16-2015 10:40 PM
0 Kudos

Nanda,

I set the parameter to optional but no luck. Still getting the same error.

Show replies
Show replies
h_carpenter
Active Contributor
‎12-17-2015 8:01 AM
0 Kudos

Hi Hariharan Palanisamy,

Could you please provide a screenshot of the 'Wait Events' tab, are we sure the name of the event is correct ?

Regards,

HP

Former Member
‎12-17-2015 11:27 AM
0 Kudos

HP,

i am not logged in right now so will provide the screenshot later. But I can assure that the event name is correct.

FYI,

When I define the event wait to the JD and run only the JD it works fine but when I try to define the event to the job chain i get this error.

Former Member
‎12-17-2015 4:35 PM
0 Kudos

PFB the screenshot for the event definition and wait event.

nanda_kumar21
Active Contributor
‎12-17-2015 6:25 PM
0 Kudos

I see that in your parameter configuration, you have multiple references to event attributes.

Are they all pointing to the same event? Can you past the error stack?

It is possible some other parameter mapping is causing the error?

thanks

Nanda

Former Member
‎12-17-2015 7:59 PM
0 Kudos

Yes Nanda.. They all pointing to the same event.

Here is the error:

Error.txt.zip
Former Member
‎12-16-2015 10:19 PM
0 Kudos

Hi Nanda,

PFB the screenshot.

I haven't set it as optional. I can set it and try once again.

Show replies
Show replies
Former Member
‎12-16-2015 9:24 PM
0 Kudos

I have defined the default raiser comment and defined the parameter to "Runtime" as well. But still getting the same error.

Show replies
Show replies
nanda_kumar21
Active Contributor
‎12-16-2015 10:11 PM
0 Kudos

can you please share the screenshot of the parameter config?

Also can you choose the option "optional" for the parameter?

thanks

Nanda

Former Member
‎12-16-2015 9:22 PM
0 Kudos

Could anyone please provide the solution for this issue?

I am also facing the same issue.

Show replies
Show replies
gmblom
Active Contributor
‎10-15-2014 7:45 AM
0 Kudos

Hi Chris,

Since the event information is not there when the event is not raised (yet) it makes sense to make the parameter 'Runtime' as it will read the event information when the job starts (and the event is raised).

Regards Gerben

Show replies
Show replies
nanda_kumar21
Active Contributor
‎10-15-2014 3:46 AM
0 Kudos

Does the Event have default raise comment defined?

If not can you please define it and try again?

Thanks

Nanda

Show replies
Show replies
Ask a Question