Sid varma

Well I thought KILL would terminate the process. But I guess only Kill -9 will truly terminate it, while kill -3 just produces a thread dump

Thanks Cooke !
Sid

Hey All

I have a qucik question about taking thread dumps using KILL -3 PID command. I know that this command generates a thread dump for the given process ID. But why do we have to kill it ? Does Kill-3 actually kill the process or just generate a dump file?/

Thanks!
Sid

Hello Guys

We are running a weblogic domain/server setup locally under eclipse dev environment. The application(using Exploded format.NOT an EAR file) is normally autodeployed in weblogic. I mean the weblogic boots up fine and application runs like it should.
Now I was just curious and deleted the autodeployed application from admin console and also removed the entry from config.xml
And I was trying to deploy it manually by selecting the folder (copied the app folder to a diff location) from the admin console. It just wont work (Getting a bunch of classNotFound exceptions while deploying and the deployment fails). Why does the application work under autodeploy but NOT under normal manual deployment ?? What am I missing here ? What do I need to do for a normal deployment ??

Thanks!
Sid

Faisal,

Thanks for the response.

Yes we upgraded the Weblogic 8 to get to 9.2

Yes, we do have the default security realm. But the authentication is done by the custom realm via Java Class. So without the custom realm, there is no authentication happening.

hello guys,


We are currently planning to upgrade our Application currently running on Weblogic 9.2 to weblogic 10.3.6
The plan is to move the application to the new platform(will be sharing weblogic with other applications), instead of upgrading the domain of the old weblogic. We are running into 2 problems here.

First one is We currently have a RDBMS Custom Realm which we are using in Weblogic 9.2 Server under Compatibility Security. What do you think is the best way to deal with the OLD security realm ? Since we are not upgrading the existing domain's config.xml, there is no way we can get compatibility security in 10.3.6 (Or is there a way ?)
Also the old 9.2 server environment only had a single application deployed, but the new 10.3.6 server environment will be a shared one. So we fear even if we some how use the same compatibility security to support the old RDBMS realms, it might cause issues. Any suggestions on this ?

Second problem is new Weblogic.jar in the version 10.3.6 has been updated by removing deprecated objects – our custom security realm is dependent on those objects/classes which were removed. So we found a workaround by adding the OLD weblogic 9.2's webloigic.jar to the classpath. That by no means should be a solution. What would Oracle suggest about this ? Few of the classes that were removed from 10.3.6 (our RDBMS security realm uses these classes/objects in the code) are,
weblogic.security.acl.User;
weblogic.utils.NestedRuntimeException;
weblogic.security.acl.FlatGroup;
weblogic.security.acl.AbstractListableRealm;
weblogic.security.acl.BasicRealm;
weblogic.security.acl.User

Is the workaround we found good enough ? What would be the right way to deal with this problem ?

Any help/comments will be helpful than you think !

Thanks !!

Its nice to see quick replys to the posts here

Yeah. Thats what i thought. Just wanted to be sure. Thanks again !

Thanks that worked !

Thanks Abhinav ! One more question. Any reason why you applied the patch only to that particular server, instead of the whole cluster ? And how did you do it ? Did you edit the startup script or use the smart update tool ? Any recommendations when doing this ?

Thanks again !

THanks Sandip !

Hello People

How do you check the status of a Managed Server with the WLST or Command Prompt when the Admin Server is completely down ?

Thanks
Sid

any luck on this ?

thanks !

any luck on this ?


Thanks
sid

Hi,

I read from the documentation that Each server instance in a Weblogic cluster must run the same version of WebLogic Server.

But i have also read that You must use multicast if you need to support previous version of WebLogic Server within your cluster.

Aren't they both contradicting statements ? I mean how can you use multicast to support 2 different versions of servers in a cluster when Weblogic doesnt support it ?

Or am i missing something here ? I am confused

Thanks
Sid