SPD WorkFlow is not able to read all the column values

Question

So quick run through of what is going on so far and the environment set in place.
Number of Environments: 2
Environment Details:
Dev: One front end server, One App Server, One SQL Server,
Production: Two Front End Servers, Two App Servers, One SQL Server,
We have a InfoPath form made in InfoPath 2010.
After making the form, it was published to the dev site with all the needed property promotions in place. It was than attached to a library, and than a workflow was made using SharePoint Designer 2010. When the workflow initiates when CreateBy value is not
empty. The workflow works fine and all the columns promoted from the form are read and placed in the email and set to end user.
when we move the same form to Production side, what happens is that the workflow reads certain properties and skips certain properties. So when the end user receives the email it is missing information that has been filled out in the form.
Just to confirm is all the values were being saved to the library properly, i went to modify view under the library tab at the top of my SharePoint library. Opened the view settings and checked off each of the properties that were promoted from the InfoPath
form (refereed to as site columns on the SharePoint side). All the columns that were filled out show the values that were either chosen or entered by the user (check box, text box, drop down, people picker). But the WorkFlow does not pick up all the values.
lets say we have the following:
We have: TextBox A for First Name
TextBox B for Last Name
TextBox C for Location Name
Dropdown 1 for Division Name
Dropdown 2 for age
People Picker for requester name
What happens is that when the user receives the email it will have the only the first name, last name, have the location missing, the division would there there, but the age would again be missing.
This is really confusing as to why it would be happening. It works fine on the Dev side, but screws up on the Production side.
Below is what the library looks like with the information populated.
same names are referenced in the workflow.

Answer 1

It depends on what you mean by "what messages are available on the topic".
if you want to know what messages would be delivered to a new consumer on the topic, then you can simply create a consumer yourself. Each messages on a topic is delivered to all subscribers, so by creating a consumer yourself you won't be interfering with the delivery of messages to other consumers. (That's not possible with queues which is why the queue browser is provided).
If you want to know what messages are "persisted in the topic" then there's not really such a concept. Messages sent to a topic are only persisted in individual durable subscriptions created for individual clients. If there are no durable subscriptions when messages are not persisted. The JMS APi doesn't provide a way to browse the messages saved in an individual durable subscription. It could, but it doesn't.
Nigel