I am having exactly the same problem in IS. I concur that everything in the pipeline is being passed to the procedure, hence why I get the following error:
com.wm.app.b2b.server.ServiceException: [B2BSERV.0026.9103] No parameter named deDupeOrSort
(where deDupeOrSort is a parameter in my pipeline!)
The interesting thing is that if I put a Map step immediately before the “call” step to the Stored Procedure to DROP everything except $dbAlias and $dbConnection, I get the same error refering to a different pipeline variable (rowCount):
com.wm.app.b2b.server.ServiceException: [B2BSERV.0026.9103] No parameter named rowCount
However, rowCount was one of the variables I dropped in the “drop” Map step.
This is definately a bug!
Sorry that doesn’t help anyone but hopefully it reaffirms the original observation.
#webMethods#Integration-Server-and-ESB#webMethods-General