Mitesh Lashkari

Greenhorn
+ Follow
since Feb 04, 2010
Merit badge: grant badges
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Mitesh Lashkari

Hi,
We are facing issue with Weblogic in Production Environment.
We are using weblogic 10.3.1 and have created two domain servers listening on ports 8001 and 9001.
Both domains are not related to each other and are admin servers.

Issue:
One of these servers i.e. listening on port 8001 got stuck and data was not processed.
When I restarted the server I found that server is not able to connect to JMS modules mounted on the same server due to outOfMemoryError.

Log :
####<Sep 20, 2010 12:30:13 PM IST> <Info> <JMS> <ismart4> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1284966013501> <BEA-040321> <JMSServer "WseeJmsServer" is resuming.>
####<Sep 20, 2010 12:30:13 PM IST> <Info> <Messaging> <ismart4> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1284966013501> <BEA-282003> <The messaging kernel WseeJmsServer will use up to 357,913,941 bytes of memory before paging begins>
####<Sep 20, 2010 12:30:13 PM IST> <Info> <Store> <ismart4> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1284966013517> <BEA-280050> <Persistent store "WseeJmsServer" opened: directory="E:\osb_home1031\user_projects\domains\JCA_Domain\servers\AdminServer\tmp" writePolicy="Non-Durable" blockSize=512 directIO=false driver="wlfileio2">
####<Sep 20, 2010 12:30:13 PM IST> <Info> <Messaging> <ismart4> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1284966013517> <BEA-282001> <The messaging kernel WseeJmsServer is beginning recovery of its persistent state>
####<Sep 20, 2010 12:30:13 PM IST> <Info> <Messaging> <ismart4> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1284966013533> <BEA-282002> <The messaging kernel WseeJmsServer has recovered 0 persistent messages>
####<Sep 20, 2010 12:30:13 PM IST> <Info> <JMS> <ismart4> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1284966013548> <BEA-040321> <JMSServer "wlsbJMSServer" is resuming.>
####<Sep 20, 2010 12:30:13 PM IST> <Info> <Messaging> <ismart4> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1284966013548> <BEA-282003> <The messaging kernel wlsbJMSServer will use up to 357,913,941 bytes of memory before paging begins>
####<Sep 20, 2010 12:30:13 PM IST> <Info> <Store> <ismart4> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1284966013548> <BEA-280050> <Persistent store "wlsbJMSServer" opened: directory="E:\osb_home1031\user_projects\domains\JCA_Domain\servers\AdminServer\tmp" writePolicy="Non-Durable" blockSize=512 directIO=false driver="wlfileio2">
####<Sep 20, 2010 12:30:13 PM IST> <Info> <Messaging> <ismart4> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1284966013548> <BEA-282001> <The messaging kernel wlsbJMSServer is beginning recovery of its persistent state>
####<Sep 20, 2010 12:32:45 PM IST> <Critical> <WorkManager> <ismart4> <AdminServer> <weblogic.timers.TimerThread> <<WLS Kernel>> <> <> <1284966165671> <BEA-002911> <WorkManager weblogic.kernel.Default failed to schedule a request due to java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
>
####<Sep 20, 2010 12:32:45 PM IST> <Error> <JMS> <ismart4> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1284966165671> <BEA-040123> <Failed to start JMS Server "wlsbJMSServer" due to java.lang.OutOfMemoryError.
java.lang.OutOfMemoryError
>
####<Sep 20, 2010 12:32:45 PM IST> <Warning> <Management> <ismart4> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1284966165671> <BEA-141197> <The deployment of wlsbJMSServer failed.
weblogic.management.DeploymentException: Internalrror activating the JMS Server wlsbJMSServer: java.lang.OutOfMemoryError
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:206)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:591)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:452)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:432)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
java.lang.OutOfMemoryError
>
####<Sep 20, 2010 12:32:45 PM IST> <Error> <Kernel> <ismart4> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1284966165687> <BEA-000802> <ExecuteRequest failed
java.lang.OutOfMemoryError: nativeGetNewTLA.
java.lang.OutOfMemoryError: nativeGetNewTLA
at java.util.HashMap.newValueIterator(HashMap.java:971)
at java.util.HashMap$Values.iterator(HashMap.java:1039)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1870)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1517)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:36)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
####<Sep 20, 2010 12:32:45 PM IST> <Info> <WorkManager> <ismart4> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1284966165687> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "WseeJmsModule">
####<Sep 20, 2010 12:32:45 PM IST> <Info> <WorkManager> <ismart4> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1284966165827> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "jmsResources">
####<Sep 20, 2010 12:32:45 PM IST> <Error> <Deployer> <ismart4> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1284966165937> <BEA-149231> <Unable to set the activation state to true for the application 'jmsResources'.
weblogic.application.ModuleException: ERROR: Could not activate jmsResources!wlsb.internal.transport.task.queue.ftp
at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:238)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
at weblogic.jms.module.JMSModule.activate(JMSModule.java:332)
at weblogic.jms.module.ModuleCoordinator.activate(ModuleCoordinator.java:194)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:411)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:74)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:66)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
weblogic.messaging.kernel.KernelException: The Messaging Kernel wlsbJMSServer has not yet been opened
at weblogic.messaging.kernel.internal.KernelImpl.checkOpened(KernelImpl.java:191)
at weblogic.messaging.kernel.internal.DestinationImpl.activate(DestinationImpl.java:280)
at weblogic.messaging.kernel.internal.QueueImpl.activate(QueueImpl.java:1687)
at weblogic.messaging.kernel.internal.DestinationImpl.resume(DestinationImpl.java:264)
at weblogic.messaging.kernel.internal.QueueImpl.resume(QueueImpl.java:1863)
at weblogic.jms.backend.BEDestinationImpl.start(BEDestinationImpl.java:609)
at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:235)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
at weblogic.jms.module.JMSModule.activate(JMSModule.java:332)
at weblogic.jms.module.ModuleCoordinator.activate(ModuleCoordinator.java:194)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:411)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:74)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:66)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)


And then It is showing message that it is unable to connect to JMS modules.

Please help.

Thanks & Regards
Mitesh
12 years ago
Hi,
In Weblogic a thread is treated as 'Stuck' if it is continiously working for a defined time period. Server keeps monitoring each thread and check after a certain period of a time if thread is running and then compare it with "Stuck thread max time" attribute.
This situation can be managed by altering following two attributes
1) Stuck thread max time.
2) Stuck thread time interval.

You can decrease "Stuck thread max time" to reproduce the scenario.

This would help you in generating the scenario but obviously not under exact circumstances which you had earlier.

Hope this would help.

Regards
Mitesh
12 years ago
Hi,
We are implementing Active-Active clustering on Solaris-64 bit
As Oracle doesn't support Active-Passive clustering, this is the only way we can implement clustering.

Could someone throw some light on advantages of A-A over A-P clustering.
Otherwise we need to move to windows with A-P clustering, as client is looking for A-P instead of A-A.
As they have their concerns regarding A-A.

Thanks & Regards
Mitesh
12 years ago
Hi,
I am trying to create a cluster.
For this purpose I have two Physical machines with Solaris platform.

Steps so far-
1) I created domain on one Machine.
2) Started admin server.
3) From admin server console created two Machines named as MachineLocal(same m/c which is used for admin server) and MachineRemote.
4) Created two ManagedServers named as MSLocal and MSRemote and associated with them respective Machines.
5) For Each machine under node manager tab I selected Plain instead of SSL.
6) Then from command prompt started node manager for MachineLocal.

But still the status of NodeManager in MachineLocal is shown as Inactive.
When I investigated I got following exception on node manager command prompt

<Uncaught exception in server handler: javax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer


Could someone suggest?

Regards
Mitesh
12 years ago
I have the execute permission.

I executed it successfully earlier.

Let me share you the full details

On this server I am running Node manager, as it hosts one of the managed servers in cluster.
Admin server is running on some other m/c.

I started Node Manager and its status was inactive.

Then I executed setWLSEnv.sh to set the environment.

And then I tried to start WLST using
java weblogic.WLST

It was throwing an exception "Exception in thread “main” java.lang.NoClassDefFoundError: weblogic/WLST"

So I edited setWLSEnv.sh and tried to execute it again.

Thanks & Regards
Mitesh
12 years ago
Hi Deepak,
Thank you very much for quick response.

I was trying to set the weblogic.jar on classpath, therefore simply edit the class path.

And when I tried to execute the setWLSEnv.sh using ./setWLSEnv.sh
It is saying ./setWLSEnv.sh can not execute.

Later I replaced the modified file with the original one but still facing the same problem.

Note: Is this file server spceific as it resides inside server directory?
Or
I can replace the file with the file on another server, but I am afraid if file's properties are referred/used somewhere else on server.

Thanks.
12 years ago
Hi,
I am trying to configure a cluster on two different hardwares.

I am trying to set the environment for weblogic on remote m/c with the help of setWLSEnv.sh

I made some changes to setWLSEnv.sh and again tried to execute.

It is saying setWLSEnv.sh can not execute

Please help on this issue.
12 years ago
Hi,

I have successfully started the second managed server MS2 on second physical machine.

Note: instead of using ./startManagedWebLogic.sh MS2
we shoud use ./startManagedWeblogic.sh MS2 IP of Adminserver:portno on which admin server is running

But now I need to add Node manager.....
Could you please enlighten on this?

Thanks
12 years ago
Hi,
I am trying to create a cluster with following details

1 managed server + admin server on one machine.
1 managed server on another machine.

First of all I created one domain(Cluster_domain) on First Physical m/c, then with the help of admin server console.

1)Created first m/c M1, then added one managed server MS1 to M1.
2)Created second m/c M2, then added one managed server MS2 to M2.
MS1 is pointing to port 7003 on first physical m/c while MS2 is pointing to port 7005 on second physical m/c

3)Created one Cluster(My_Cluster) and added MS1 and MS2 to that the cluster.

Then I went to second physical m/c created the same domain(Cluster_domain) in the same directory structure.

Then I went to first physical m/c and started the managed server MS1 with the help of managedWebLogic.sh command in bin directory.


Till here it is working fine.

Then I went to second physical m/c and started the managed server MS2 with the help of managedWebLogic.sh command in bin directory.

here I am getting following error....


Feb 4, 2010 1:24:31 PM IST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:

There are 1 nested errors:

weblogic.management.ManagementException: [Management:141223]The server name MS2 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {AdminServer}.
at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:149)
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:39)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:459)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:164)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:711)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:482)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:440)
at weblogic.Server.main(Server.java:67)

>
<Feb 4, 2010 1:24:31 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Feb 4, 2010 1:24:31 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Feb 4, 2010 1:24:31 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>


Thanks in advance for your help.
12 years ago