- This topic has 8 replies, 3 voices, and was last updated 12 years, 10 months ago by
.
-
Posts
-
Im using MyEclipse 10 and configured with Weblogic Server 10.3.3. I was able to successfully deploy my EAR in an exploded format and everything works great. The JSP files automatically picks up the changes once I refresh the page. But when I make any changes to the JAVA class file, I can see that the changes are synced with the deployed location (so autodeploy works) but I was hoping to see in the console that the application being hot deployed. But I don’t see any activity in the console and when I hit the URL I get exception. I had to redeploy the application to actually see the changes.
I have worked with Websphere before without any issues as the app server hot deploys the application if there is any changes to class files.
Is there any additional configuration to be made for Weblogic Server? Any help regarding this will be appreciated.
Thanks,
moutts,
Are you running your application on run mode / debug mode? If you wish to see the changes made to your class file directly on your console, you need to ensure you are running in debug mode.
Hope this helps.I am running my application server in debug mode. I am very much aware of that requirement. So I don’t think that is the problem. Any other recommendations?
moutts,
Thanks for the clarification. You mention
But I don’t see any activity in the console and when I hit the URL I get exception.
Could you attach the issue you are seeing, preferably a screenshot to help me get a visual. Also clear your .log file located at [your workspace dir]/.metadata/.log, replicate the issue and attach file here.
Sorry for the inconvenience.
moutts,
Thanks for the clarification. You mention
But I don’t see any activity in the console and when I hit the URL I get exception.
Could you attach the issue you are seeing, preferably a screenshot to help me get a visual. Also clear your .log file located at [your workspace dir]/.metadata/.log, replicate the issue and attach file here.
Sorry for the inconvenience.
Joy,
Thanks for getting back to me. As per your recommendation I cleared the .log file and started Weblogic in debug mode. I was able to login to my application. Then I modified one of my Java class file. I can see that the the .class file time stamp is modified to the current time (which confirms that the file change is complied and synced) Waited for few minutes and there is no activity in the Console. Now I went back to hit the login page of my application and I get the error. Here is the screen shot of the console with the error message. But when I checked the .log file the file is empty 🙁 Not sure why so I don’t see a reason to attach that file as it is empty.If you need more information, Please let me know.
Thanks,
moutts,
Thank you for the screenshot. You seem to have exceeded the number of open socket connections. Please see this weblink and follow the recommendations http://www.otmfaq.com/forums/f27/solved-weblogic-error-lt-bea-000402-gt-maximum-number-socket-reader-thread-218/
Let me know how this works for you.
Joy,
Thanks for your recommendation. I did follow the recommendations provided as per the link although there is no concept of “ThreadPoolPercentSocketReaders” in Weblogic 10.3.3. Since weblogic 9.2 it has been modified to use self tuning work managers. I configured a Work Manager as per weblogic documentation but I still see the same problem.I feel this has nothing to do with the autodeploy problem I am facing. Once I modify a java class file, I see that the changes is compiled and copied over to the deployed location. But for some reason the weblogic doesn’t seem to hotdeploy the application (which seems to be the problem).
Is there anyone who is running Weblogic 10.3.3 (11g) with MyEclipse 10 with autodeploy feature? If so can you give me the steps involved to configure my environment.
Thanks
moutts,
For hot deploy, it seems as though you have to add a VM parameter. Go to the server connector page for WebLogic 10.x, in the server preferences, then go to the subpage, JDK. After the existing Optional Java VM arguments, add:
-Dweblogic.ProductionModeEnabled=falseI’ve raised a problem report to get this added by default.
So far as the socket threads warning is concerned, I found this thread which contained a possible solution that you might try. In the above preferences page, add this at the end of the arguments:
-Dweblogic.ThreadPoolPercentSocketReaders=50 -Dweblogic.ThreadPoolSize=100 -Dweblogic.SelfTuningThreadPoolSizeMin=100Please let us know if these additions work for you.
