• Post Reply Bookmark Topic Watch Topic
  • New Topic

Dynamic Deployment Of Beans

 
ravi subbiah
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am working with Weblogic 6.0.I would like to dynamically update changes in the deployed bean without stopping the server or undeploying the bean!
will some one help me?
Thanx in advance
Ravi Subbiah
------------------
 
Joe McGuire
Ranch Hand
Posts: 293
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Unlike version 5 and earlier, WebLogic 6.0/6.1 supports dynamic deployment (so long as you haven't changed the default option from within the administration console). Just copy you're new jar file into the application directory (or your expanded files). The classloader will see the change and implement it automatically.
 
ravi subbiah
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Joe
Thanx for the reply.well I did not change any default options in the administration console.
I did copy the updated jar file into the application directory .And i checked the server ,it
said..,
" Undeploying EJB Component Migrate "
and when I invoked the bean thro the servlet ,it threw the following exception
exeception thrown by the the servlet =>javax.naming.NameNotFoundException: Unable to resolve Migrate. Resolved: '' Unresolved:'Migrate' ; remaining name ''
javax.naming.NameNotFoundException: Unable to resolve Migrate. Resolved: '' Unresolved:'Migrate' ; remaining name ''
<<no stack trace available>>
I again invoked the servlet ....it did the same
exeception thrown by the the servlet==>javax.naming.NameNotFoundException: Unable to resolve Migrate. Resolved: '' Unresolved:'Migrate' ; remaining name ''
javax.naming.NameNotFoundException: Unable to resolve Migrate. Resolved: '' Unresolved:'Migrate' ; remaining name ''
<<no stack trace available>>
And for the 3rd invoke ....the bean was called ...and I got the result....
"message from bean in regid chk==>Regid already used!"
And the subsequent calls were successfull.
Again I made a small change in the bean ,copied the jar file into the application dir.And this time the
exception was thrown only once. And subsequent calls were successful.
what I understand is that the class loader is taking some time to load the jar file.
Is there any way out to optimize the time taken by the class loader?
Kindly help me out!
Ravi Subbiah
 
Joe McGuire
Ranch Hand
Posts: 293
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
WebLogic Server checks the contents of your $/bea/wlserver6.0/config/examples/applications directory every ten seconds to determine whether an EJB deployment has changed. It's probably possible to change this time interval (though off the top of my head I don't know how); However, you probably don't want to do so because of the performance hit you'll take by constantly polling the directory for changes at smaller intervals.
 
ravi subbiah
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanx a lot Joe.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!