Message 607

When I attempt to process SFCs down the one of my routes I receive an error message "Message 607" and the SFCs are never started at the operation.

What does Message 607 mean? How do I fix it?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (2)

I recommend that you upgrade to the latest ME service pack (5.2.5 or above). This issue should have been fixed.

If you will still manage to reproduce this issue, then it is a valid case for a bug ticket.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Alli,

Is any event notification set up?

Is there any hooks or activities executed at pre-start?

How you start SFC: Prod Interface XML, WS, POD?

What's the error stack trace from the log?

Regards,

Sergiy

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Is any event notification set up? - No

Is there any hooks or activities executed at pre-start? No

How you start SFC: Prod Interface XML, WS, POD? - POD

What's the error stack trace from the log? I don't have access to view the trace logs

I have verified that the first operation on the route is marked as an entry step and that all operations and routes are marked as releasable. The first operation does not have any activity hooks associated to it.

What does Message 607 mean?

Alli,

What is your ME sp? Is this a custom start?

607 = cannot get connection,error executing SQL or a problem with Dbsequence.

Can you try this with only 1 SFC?

Regards,

German

ME version Base 5.2.4.2, Counter 5

Using the base pod, with no modification. The issue occurs when attempting to start 1 SFC and also when attempting to start multiple

Alli,

I would suggest to log a ticket for this and include the trace file or to paste the error from the trace here in the forum.This is not a common issue (at least for me).

Regards,

German

Alli,

Could you please check if there any issues with JMS on your server. It's a possibility that 607 appears when alarms cannot be sent because of JMS issues.

Thanks,

Bakhtiyar

Hi Bakhtiyar, looks like the issue is because alarms cannot be sent (see the stacktrace below). Is there any temp workaround for it before we can apply the new patch as Mikhail suggested.

(Message 607)

at com.sap.me.alarm.AlarmBOBean.send(AlarmBOBean.java:741)

at com.sap.me.alarm.AlarmBOBean.sendValidated(AlarmBOBean.java:464)

at sun.reflect.GeneratedMethodAccessor12584.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:592)

at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)

at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)

at $Proxy625.sendValidated(Unknown Source)

at com.sap.me.user.CertificationBOBean.sendCertAlarm(CertificationBOBean.java:1094)

at com.sap.me.user.CertificationBOBean.assertCertError(CertificationBOBean.java:1078)

at com.sap.me.user.CertificationBOBean.checkCerts(CertificationBOBean.java:244)

at sun.reflect.GeneratedMethodAccessor12402.invoke(Unknown Source)