We are getting problem in starting weblogic server 10.2 .
We have two machine they switch each other by cluster.
On one machine , Weblogic server does not start when cluster switch to this machine.
When server starts , it hangs. We get following eroor:

Remove the following from the script that is used to start the server.
-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n.
This is used to debug the process and I don't think you may need to start a production system in debug mode.

It seems to me that you have WebLogic Portal instance that is using Autonomy that can not be started. Fail of this Autonomy search engine makes it critical for WLS to start. Autonomy can not bind to IP and port. There are potentially many reasons for that failure:
1. It might be that you have already Autonomy running on this machine
2. It might be that you have more than one instance of WLS (like two managed servers) on the same hardware and both of them are trying to start Autonomy with the same parameters (IP + port)
3. You moved configuration from on hardware to another and forgot to change IP in the configuration of the Autonomy
4. You changed IP address and you did not change IP in the Autonomy settings.

This is interesting that your machine is linux because in the error message it shows that it tries to start "IDOLserver/DiSH/AutonomyDiSH.exe" - so it tries to start Windows executable file that of course does not exist on linux installation. Are these starting / environment scripts original? Or did you modify them?

Check and verify also scripts for starting autonomy - they are placed in the %WL_HOME%\cm\thirdparty\autonomy-wlp10

Chceck on netstat if port 8453 is available and
- if YES than try to remove from starting scripts following flags "-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n"
- if NO modify in starting scripts port 8453 to other one

We observe the server start up log. We did all that you suggested.
Still I am not able to start the production server. As we get very lesser chance to RND on production server.The new problem is now , when we start the server, its hangs, and did not start.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Sever hangs on the line

*/home/bea/bea102/user_projects/domains/tmpasldomain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>*

Hi,
When i was facing this issue, it was due to heap memory...i tuned it according to my RAM and then it worked saw your -Xms256m and -Xmx2048m, try keeping maximum and minimum heap to same figure.may be you JVM is taking too much of time to manage heap; and also try out increasing you -XX:MaxPermSize accordingly.
also,
check your garbage collection data, that will show you what the problem is, check for PermGeneration committed and Used size.If committed size is used completely try increasing MaxPermSize.

Also take thread dump of your running process and analyze those by detecting deadlock and stuck threads.