• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Paul Clapham
  • Bear Bibeault
  • Jeanne Boyarsky
Sheriffs:
  • Ron McLeod
  • Tim Cooke
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Jj Roberts
  • Stephan van Hulst
  • Carey Brown
Bartenders:
  • salvin francis
  • Scott Selikoff
  • fred rosenberger

Weblogic and EJB Error

 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am new to weblogic,

I created an ejb for printing "Hello world". I compiled made it a JAR File and Deployed it in Weblogic, It Works fine. Now I changed the Text "Hello World" to "Hello MY Name" and compiled the application made it as JAR file. Then I Removed the first application which display "Hello world" , Cleared Cache temp file etc etc. Stoped the server and restarted the server. And after doing all these things I installed the new JAR file which has to display "Hello MY Name". But when I run this application its Gives me an Output "Hello World"( Output of first application ). Please Please Help me to sort it out. What Could be the Problem. Any help is highly appreciated.

Thanx in advance
Regards
Sinora
 
Ranch Hand
Posts: 775
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Weblogic has a directory where it puts a recompiled and expanded version of the ejb-jars, wars, ears. When you attempt to re-deploy, sometimes that old stuff doesn't get replaced. Might be because of timestamps on files, might be because of security permissions (e.g. deployed the first one as "root" on a Unix box, and the second one as some other user).

Where these temporary directories are depends on your configuration and WebLogic version. For 8.1, look in your domain, in the server directory (probably called "myserver"), and you'll fine a .wlnotdelete directory beneath it. That is where the old stuff will be. The "applications" directory in your domain is another candidate for having a ".wlnotdelete" directory that might have stuff to clean out. Just be careful to ONLY clean out your stuff, not other files (e.g. for the weblogic console). Shut down the server, clear out your stuff from those directories, bring up the server, redeploy, and you should be all set.
 
Sinora Aspin
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
a new instance of wl installation was carried out using a different administrative user; hence, the new installation has nothing to do with the old one (they cannot see each other). once the ejbs are deployed to the new installation, the changes are still not reflected!!
we are suspecting a bug within the ejbc compiler, could this be the reason?




Originally posted by Reid M. Pinchback:
Weblogic has a directory where it puts a recompiled and expanded version of the ejb-jars, wars, ears. When you attempt to re-deploy, sometimes that old stuff doesn't get replaced. Might be because of timestamps on files, might be because of security permissions (e.g. deployed the first one as "root" on a Unix box, and the second one as some other user).

Where these temporary directories are depends on your configuration and WebLogic version. For 8.1, look in your domain, in the server directory (probably called "myserver"), and you'll fine a .wlnotdelete directory beneath it. That is where the old stuff will be. The "applications" directory in your domain is another candidate for having a ".wlnotdelete" directory that might have stuff to clean out. Just be careful to ONLY clean out your stuff, not other files (e.g. for the weblogic console). Shut down the server, clear out your stuff from those directories, bring up the server, redeploy, and you should be all set.



[ February 18, 2006: Message edited by: Sinora Aspin ]
[ February 18, 2006: Message edited by: Sinora Aspin ]
 
Ranch Hand
Posts: 1683
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It will not be a compiler bug.

My suggestion is to delete all the .class files, rebuild and redeploy. All should now be fine.
 
Greenhorn
Posts: 22
Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Sinora,

I have come across similar problem earlier and after I manually deployed the jar file through weblogic console, it worked fine. May be you should try that.

Thanks

Anikanchan
 
Reid M. Pinchback
Ranch Hand
Posts: 775
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Originally posted by Anikanchan Raut:
I have come across similar problem earlier and after I manually deployed the jar file through weblogic console, it worked fine. May be you should try that.



That reminds me of something I saw once before. You have to make sure that the ear/war/jar getting deployed is the one you intended. If you have a copy of the old one in a place that weblogic automatically scans on startup, you may be consistently redeploying the old one, not the new one that was built.
 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have a similar problem - sometimes when I update an application in Unix, the new version doesn't appear to be deployed. Never happens on Windows, though.

Re:

"If you have a copy of the old one in a place that weblogic automatically scans on startup, you may be consistently redeploying the old one, not the new one that was built."

can anyone tell me where this old copy might be?

Thank you in advance.
 
Joel Salatin has signs on his property that say "Trespassers will be Impressed!" Impressive tiny ad:
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
reply
    Bookmark Topic Watch Topic
  • New Topic