I am in agreement with Bear, what you are doing is generally not best practice so I hope you don't plan on using something like this in a production capacity. However there is the possibility you are simply doing a learning exercise of some kind so I will do the favor of imparting some knowledge as to why you are having this problem. Eswara has provided a solution which should work but has in effect "given you a fish" without "teaching you how to fish for yourself" so to speak. In other words, I feel he hasn't explained why his solution works. It seems to me that maybe you lack the understanding of the difference between forward and redirect. The underlying mechanisms between the two are very different and this is not the first time I have seen new web developers tripped up by this.
When you send a redirect to a client browser, you are sending a response telling the client browser that the originally requested resource has moved to a new URL. Specifically there is an HTTP response status code 302 which signifies a moved resource. When a redirect is issued the server will actually issue a response to the client that originated the request. The 302 response will contain the new URL for the resource that was moved. In your case "Welcome.jsp". This causes the client browser to issue a NEW REQUEST to the new URL. The request parameters from your original 1st request are lost unless you have taken steps to preserve them and pass them along in the new request such as including them in the URL query string (or have stored them in the session or otherwise persisted them somehow). As you probably realize it must be this way because HTTP is a request/response based protocol. You get 1 response per 1 request.
Forward, on the other hand, does NOT send any response back to the client and therefore no new request is issued. Whatever incoming request parameters were there in the original request will still be available to the servlet/jsp to which you forward. Forward merely takes the original request and response objects from the original request and "forwards" them on, or delegates them if you will, to another servlet/jsp. Any posted data is preserved for the resource to which you are forwarding.
Neither redirect nor forward cause the currently executing servlet/jsp to return. Therefore, IF your jsp includes more reachable code blocks after your redirect or forward call and you don't want them executed,
you should issue a return statement.
There is another key difference between a forward and a redirect as well. A forward can be issued at pretty much any time. A redirect cannot be issued once any response output to the current request has started. If you try you will see errors to the effect of "response already committed" or some such thing.