JMS--> DCJMSStringProperty2 and 1 ?

[SD78]

Hello together,

In the log viewer we have after SP 18 this error message:

Cannot read the switch setting for property name DCJMSStringProperty2, switch name dynConfigDCJMSStringProperty2. It is switched off.

Cannot read the switch setting for property name DCJMSStringProperty1, switch name dynConfigDCJMSStringProperty1. It is switched off.

I have checked the jms adapter, but I don’t find this properties.

Have you an idea?

Bye

Stefan

[SD78]

Have somebody an idea?

Stefan

[Former Member]

try to find under adapter specipic attributes

[SD78]

Hi,

There are no settings with this name under adapter specipic attributes.

I have set the trace level com.sap.aii.af.mp.jms to debug.

Date : 11/13/2006

Time : 13:01:02:222

Message : Name DCJMSStringProperty2 is switched off.

Severity : Debug

Category :

Location : com.sap.aii.af.mp.jms.ejb.ConvertBinaryToXMBMessage.fillXMBMessage(ModuleContext moduleContext, Binary payload, XMBMessage xmbMessage, IGUID guid, Channel channel, String jmsmsgid, String jmscorid, String jmsproprefvalue, String jmspropconvvalue)

Application : sap.com/com.sap.aii.adapter.jms.app

Thread : Thread[asyncDelivery0,5,SAPEngine_Application_Thread[impl:3]_Group]

Datasource : 585661350:/usr/sap/XXX/DVEBMGS58/j2ee/cluster/server0/log/defaultTrace.trc

Message ID : 0012799575DE004D00008BDB000014350004221FA7BEEFCC

Source Name : com.sap.aii.af.mp.jms.ejb.ConvertBinaryToXMBMessage

Argument Objs : DCJMSStringProperty2,

Arguments : DCJMSStringProperty2,

Dsr Component :

Dsr Transaction : f80804706fcf11db8c720012799575de

Dsr User :

Indent : 0

Level : 0

Message Code :

Message Type : 1

Relatives :

Resource Bundlename :

Session : 0

Source : com.sap.aii.af.mp.jms.ejb.ConvertBinaryToXMBMessage

ThreadObject : Thread[asyncDelivery0,5,SAPEngine_Application_Thread[impl:3]_Group]

Transaction : SAP J2EE Engine JTA Transaction : [22ffffffe87bffffffa600ffffffc8ffffffc9]

User : J2EE_GUEST

Date : 11/13/2006

Time : 13:01:02:222

Message : Catching com.sap.aii.af.service.cpa.impl.exception.CPAObjectException: Value with name dynConfigDCJMSStringProperty2 not available

at com.sap.aii.af.service.cpa.impl.container.CPAObject.checkNameForValue(CPAObject.java:380)

at com.sap.aii.af.service.cpa.impl.container.CPAObject.getValueAsString(CPAObject.java:562)

at com.sap.aii.af.service.cpa.impl.container.AttributeExtendedCPAObject.getValueAsString(AttributeExtendedCPAObject.java:165)

at com.sap.aii.af.service.jms.Util.shouldPassAsDynamicAttribute(Util.java:405)

at com.sap.aii.af.mp.jms.ejb.ConvertBinaryToXMBMessage.fillXMBMessage(ConvertBinaryToXMBMessage.java:427)

at com.sap.aii.af.mp.jms.ejb.ConvertBinaryToXMBMessage.process(ConvertBinaryToXMBMessage.java:156)

at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl10.process(ModuleLocalLocalObjectImpl10.java:103)

at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:258)

at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)

at com.sap.aii.af.service.jms.WorkerJMSReceiver.onMessage(WorkerJMSReceiver.java:947)

at com.ibm.mq.jms.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:2812)

at com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java:406)

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

Severity : Warning

Category :

Location : com.sap.aii.af.mp.jms.ejb.ConvertBinaryToXMBMessage.fillXMBMessage(ModuleContext moduleContext, Binary payload, XMBMessage xmbMessage, IGUID guid, Channel channel, String jmsmsgid, String jmscorid, String jmsproprefvalue, String jmspropconvvalue)

Application : sap.com/com.sap.aii.adapter.jms.app

Thread : Thread[asyncDelivery0,5,SAPEngine_Application_Thread[impl:3]_Group]

Datasource : 585661350:/usr/sap/XXX/DVEBMGS58/j2ee/cluster/server0/log/defaultTrace.trc

Message ID : 0012799575DE004D00008BD9000014350004221FA7BEEE3D

Source Name : com.sap.aii.af.mp.jms.ejb.ConvertBinaryToXMBMessage

Argument Objs : com.sap.aii.af.service.cpa.impl.exception.CPAObjectException: Value with name dynConfigDCJMSStringProperty2 not available

at com.sap.aii.af.service.cpa.impl.container.CPAObject.checkNameForValue(CPAObject.java:380)

at com.sap.aii.af.service.cpa.impl.container.CPAObject.getValueAsString(CPAObject.java:562)

at com.sap.aii.af.service.cpa.impl.container.AttributeExtendedCPAObject.getValueAsString(AttributeExtendedCPAObject.java:165)

at com.sap.aii.af.service.jms.Util.shouldPassAsDynamicAttribute(Util.java:405)

at com.sap.aii.af.mp.jms.ejb.ConvertBinaryToXMBMessage.fillXMBMessage(ConvertBinaryToXMBMessage.java:427)

at com.sap.aii.af.mp.jms.ejb.ConvertBinaryToXMBMessage.process(ConvertBinaryToXMBMessage.java:156)

at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl10.process(ModuleLocalLocalObjectImpl10.java:103)

at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:258)

at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)

at com.sap.aii.af.service.jms.WorkerJMSReceiver.onMessage(WorkerJMSReceiver.java:947)

at com.ibm.mq.jms.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:2812)

at com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java:406)

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

,

Arguments : com.sap.aii.af.service.cpa.impl.exception.CPAObjectException: Value with name dynConfigDCJMSStringProperty2 not available

at com.sap.aii.af.service.cpa.impl.container.CPAObject.checkNameForValue(CPAObject.java:380)

at com.sap.aii.af.service.cpa.impl.container.CPAObject.getValueAsString(CPAObject.java:562)

at com.sap.aii.af.service.cpa.impl.container.AttributeExtendedCPAObject.getValueAsString(AttributeExtendedCPAObject.java:165)

at com.sap.aii.af.service.jms.Util.shouldPassAsDynamicAttribute(Util.java:405)

at com.sap.aii.af.mp.jms.ejb.ConvertBinaryToXMBMessage.fillXMBMessage(ConvertBinaryToXMBMessage.java:427)

at com.sap.aii.af.mp.jms.ejb.ConvertBinaryToXMBMessage.process(ConvertBinaryToXMBMessage.java:156)

at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl10.process(ModuleLocalLocalObjectImpl10.java:103)

at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:258)

at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)

at com.sap.aii.af.service.jms.WorkerJMSReceiver.onMessage(WorkerJMSReceiver.java:947)

at com.ibm.mq.jms.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:2812)

at com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java:406)

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

,

Dsr Component :

Dsr Transaction : f80804706fcf11db8c720012799575de

Dsr User :

Indent : 0

Level : 0

Message Code :

Message Type : 1

Relatives :

Resource Bundlename :

Session : 0

Source : com.sap.aii.af.mp.jms.ejb.ConvertBinaryToXMBMessage

ThreadObject : Thread[asyncDelivery0,5,SAPEngine_Application_Thread[impl:3]_Group]

Transaction : SAP J2EE Engine JTA Transaction : [22ffffffe87bffffffa600ffffffc8ffffffc9]

User : J2EE_GUEST

It looks like a bug in sap code.

I have created an oss message.

But perhaps you have idea here.

Bye

Stefan

[SD78]

Hi,

I have an answer from the sap.

16.11.2006 - 16:24:18 CET SAP Antwort

Hi Stefan,

(sorry..didn't realize it was a production system)

Both the errors are warnings mentioning that the old channel

configuration (<SP18) is being used with new metadata.

Stefan, the attached screenshots don't show the ASMP (adapter specific

message properties) section. From the trace, I observe that this sectionis switched on. (checkbox 'Set Adapter specific message properties'). Ifthis section is switched on, then the channels would need to be

re-created, if you wish to avoid the warning messages - since there is abreaking change in the ASMP properties from SP17 to SP18.

If you are not using ASMP, then please switch these sections off. You

will only receive once warning at channel initialization mentioning thatthe channel configuration is 'old'. But subsequent message processing

will not throw warnings.

But, these warnings shouldn't cause the channel to stop functioning.

Is your channel functioning fine? Is the status green and are messages

getting successfully processed? Any there any other problems?

Regards,

Tarun

After this we have no error in the visual admin.

Bye

Stefan