INVALID_QUEUE_NAME

[Former Member]

Hi All

I have a JDBC to SAP ECC scenario.

I receive the following error on the Adapter Engine: Transmitting the message to endpoint http://<host>:<port no>/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SCHEDULE_ERROR:.

and: Received XI System Error. ErrorCode: SCHEDULE_ERROR ErrorText: ErrorStack: Error while scheduling message using qRFC (queue name = , exception = INVALID_QUEUE_NAME)

I will really appreciate any help

Thanks

Clinton

[Former Member · Accepted solution]

Hi,

Go to RWB and check whether your adapter engine is with green flag or red flag.

Then check you are using EO or EOIO,becoz when you use EOIO you have to give queue name.

[Former Member · Accepted solution]

Hi

Thanks for the reply's.

I'm using EO, but have changed it to use EOIO and specified a queue name it all else fails I will let it run like that tomorrow.

Also, all the queue's are active and registered.

Also checked the note.

Problem still exists - any other suggestions

Thanks in advance

Clinton

[Former Member · Accepted solution]

Let us know the QUEUE name, if possible.

Do you have the problem with EO also ?

Do you see the message in the SXMB_MONI both with EO and EOIO ?

Can you post the complete error ?

Regards,

Sandro

[Former Member · Accepted solution]

Hi Sandro

I don't see the problem on SXMB_MONI, it is still only on the Adapter Engine in Message Monitoring in RWB.

In the error details from Message Monitoring I cannot see a queue name, is there somewhere I can see this. Could this maybe be a cache problem - if so, what part of the cache should I refresh?

Thanks for the help

Clinton

[Former Member · Accepted solution]

The cache of the adapter is the CPA chache, the link for the refresh is:

http://<server>:<java port>/CPACache/refresh?mode=full

you must to execute this with the user XIDIRUSER (you must to know the password)

Regards,

Sandro

[Former Member · Accepted solution]

Hi Sandro

Thanks for your reply.

I have done the full cache refresh, but no change to the problem.

I yesterday changed it to a EOIO and added a queue name. This morning the Interface ran without a problem..... The error status message from the last couple of days is still a problem.

With the EOIO I could see the queue name - this queue is active and registered, will the XBQO_(my queue name), for the EO then also use XBQO. It seems like with the EO scenario it is not being schedule to a queue? Is this possible?

Thanks for the help this far

Clinton

[Former Member · Accepted solution]

It looks something serious, I suggest you to open an OSS message in the while you continue to investigate on this

Regards,

Sandro

[Former Member · Accepted solution]

Hi Guys

Thanks for all your help. I will logg the call.

Thanks

Clinton

[STALANKI]

Have u registered the queues?If not register them from sxmb_adm.

[Former Member]

Hi,

Have a look at OSS Note: 764176.

Regards,

Venu.

[Former Member]

How long is the queue name you set in the JDBC sender adapter ?

The queue name must to be less than 17 char long.

Regards,

Sandro