In 188.8.131.52, we migrated the code without any change and while testing, we are getting the following error,How did you migrate the code? Ideally no changes in the code should be required for an upgrade.
As a work around, i tried using a AQ adapter to fetch the message from IP_IN_QUEUE. But no luck, getting the following error,Seems like a grant issue. Make sure that your data-source is configured with SOAINFRA user of B2B.
We imported the .jws file into our 184.108.40.206 jdev. Prompt for migration is successful in jdev.Then ideally underlying code must not have changed.
what kind of access has to be given?If data-source being used for composite is also configured with PROD_SOAINFRA user then no additional grants are required.
When i checked the IP_IN_QUEUE, there are two entries (2 rows) for the same transaction. What could be the reason?Either transaction would have been resubmitted manually or partner would have sent it twice. Check the B2B report to see if there is a row for each transaction in IP_IN_QUEUE.
When TP sends Successful ack, its getting stagnated in the queue, my response consumer (b2buser) is not picking it up.Because your B2B adapter might not have been configured for fetching "Receipt Acknowledgment". Please cross-check the B2B adapter configuration in your composite.
In B2B reports i see only one response (either exception/ack) from TP for a transaction.It's working as expected. The exceptions raised by B2B are not displayed in reports.