Thanks, NAT is not involved in this case & acl's for the needed traffic are already existing.

Aren't the connections being denied by the existing ACLs?

That would explain why you see torn down connections and why there are no connections created in the 'sh conn''

Federico.

Rules are configured for these connections and there were no deny sequence seen for these traffic.

i see following messages when checked:

6|Jun 15 2010 12:05:13|302013: Built inbound TCP connection 12379739847776492194 for FW:10.0.122.8/3397 (10.0.122.8/3397) to WFM:10.51.100.107/443 (10.51.100.107/443)
6|Jun 15 2010 12:05:13|302014: Teardown TCP connection 12379739847776492194 for FW:10.0.122.8/3397 to WFM:10.51.100.107/443 duration 0:00:00 bytes 3715 TCP FINs

tcp FINS are sometimes seen replaced with Reset-0.

Is these kind of built/teardown connection normal with tcp within short timespan.

Thanks for your help!

{EDIT} : So sh conn would only give connections if the rules are configured for the traffic else it wont show . is that correct, just to understand?

Since it is already torn down, you will not see it in connections.

Even if you have allowed for the connection flow, and it is built, but if it is torn down straight away, then it will no longer be in "show connection" output.

You will need to find out why the fin or reset is happening for that specific flow.

What does the configuration look like?

Have you tried packet tracer?

You are doing https traffic. Is the traffic directed to the interface ip address of the firewall, and you have also asdm or webvpn configured for the interface?

Thanks for your help, the problem got resolved lately. It was related to some new process on the server which negated the connections.

Thanks again for ur valuable inputs!