Check in Commerce instance ProfiledMessageSource is available in DynamoMessagingSystem.xml or not if yes then you need to remove the ProfiledMessageSource from CSC instance by overriding DynamoMessagingSystem.xml in CSC layer by adding xml-combine="remove" tag for ProfiledMessageSource.
Thanks for the reply.
My issue is fixed now. It is JBOSS configuration issue. Sessions are not maintained properly that's why we are getting NULL profile in the session. Our application has multiple WARs so we fixed it by setting emptySessionPath to TRUE. If emptySessionPath attribute in server.xml is false, then each WAR will have its own jsessionid cookie.
I did not touch ProfiledMessageSource as its required for session triggering.