Weblogic server is being shutdown frequently

Hi ,
In our project we are being used weblogic 8.1 sp5 in production envirionment. However since last month one of the cluster server is being shutdown for every 3 days (NOTE: there are 2 servers in cluster). We got 3 different log messages for the last 3 times server was shutdown, which are mentioned in Log1,Log2 and Log3 below. Moreover we are unable to find the exactly root cause for such case. PFB the envirionments which we are using. For LOG2 case we communicated with our network team they said that there was no problem in network at that time.
O/S: SOLARIS
SERVER: WEBLOGIC 8.1 SP5
Technologies used : J2EE(EJB,JMS,MDB,JDBC AND JAVAMAIL)
DATABASE:ORACLE 10g
Log1:
####<Mar 24, 2009 5:06:05 PM GMT> <Error> <WebLogicServer> <dys143a001> <managed3_mogiapp01> <weblogic.health.CoreHealthMonitor> <<WLS Kernel>> <> <BEA-000337> <ExecuteThread: '35' for queue: 'weblogic.kernel.Default' has been busy for "906" seconds working on the request "weblogic.jms.dispatcher.DispatcherImpl", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
Log2:
####<Mar 18, 2009 4:25:56 AM GMT> <Error> <Cluster> <dys143a001> <managed2_mogiapp01> <ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-000141> <TCP/IP socket failure occurred while fetching statedump over HTTP from 1385344116515976978S:147.149.132.159:[61004,61004,-1,-1,61004,-1,-1,0,0]:147.149.132.159:61003,147.149.132.159:61004:mogiapp01:managed3_mogiapp01.
java.io.IOException: Failed to get OK response
     at weblogic.cluster.HTTPExecuteRequest.execute(HTTPExecuteRequest.java:123)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
>
Log 3:
####<Mar 18, 2009 12:00:00 AM GMT> <Info> <Log Management> <dys143a001> <managed3_mogiapp01> <ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-170018> <The log file has been rotated to managed3_mogiapp01.log00690. Log messages will continue to be logged in /wls_domains/mogiapp01/logs/bea/managed3_mogiapp01.log.>
####<Mar 18, 2009 12:00:00 AM GMT> <Info> <null> <unknown> <unknown> <ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <null> <null> <000000> <LogRotation trigger for logfile /wls_domains/mogiapp01/logs/bea/managed3_mogiapp01.log>
####<Mar 18, 2009 4:07:20 AM GMT> <Info> <HTTP> <dys143a001> <managed3_mogiapp01> <ExecuteThread: '0' for queue: 'weblogic.kernel.Non-Blocking'> <<anonymous>> <> <BEA-101047> <[ServletContext(id=20794441,name=bea_wls_internal,context-path=/bea_wls_internal)] /psquare/*: init>
####<Mar 18, 2009 4:23:13 AM GMT> <Error> <HTTP> <dys143a001> <managed3_mogiapp01> <ExecuteThread: '52' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-101083> <Connection failure.
java.lang.OutOfMemoryError
>
####<Mar 18, 2009 4:25:56 AM GMT> <Error> <WebLogicServer> <dys143a001> <managed3_mogiapp01> <weblogic.health.CoreHealthMonitor> <<WLS Kernel>> <> <BEA-000337> <ExecuteThread: '68' for queue: 'weblogic.kernel.Default' has been busy for "754" seconds working on the request "weblogic.jms.dispatcher.DispatcherImpl", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
####<Mar 18, 2009 4:25:56 AM GMT> <Warning> <RMI> <dys143a001> <managed3_mogiapp01> <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-080004> <An error was thrown by rmi server: weblogic.management.internal.MBeanHomeImpl.getMBeanServer()
java.lang.OutOfMemoryError.
java.lang.OutOfMemoryError
>
####<Mar 18, 2009 4:25:56 AM GMT> <Error> <Kernel> <dys143a001> <managed3_mogiapp01> <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-000802> <ExecuteRequest failed
java.lang.OutOfMemoryError.
java.lang.OutOfMemoryError
>
Regards
Vinod
Edited by: [email protected] on Mar 30, 2009 6:27 AM

[att1.html]

Similar Messages

Can't start weblogic Server -The server will force shutdown now

Hello Community ; ) , I hope i post this on the right topic if not pls advise me.
I'm working as a trainee by a company which wants to establish OIBEE.
I'm really new to this topic and hope i can get some help with my problems . Cause i stuck in many ways .
I installed Oracle OBIEE 11g and the latest Patch 11.1.1.7.1.
After changing the Oracle Logo in Oracle Home I restarted the Services, using Oracle WebLogic Server Administration Console.But it cant restart and stuck!
So i stopped all manual using commands like "./stopWebLogic.sh ". As I wanted to start it again i get some error messages. Can somebody advise me how to handle this problem ? I would be very grateful.
<Oct 29, 2013 12:09:31 PM CET> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in /app/oracle/product/OBIEE11.1.1.7/oracle_common/atgpf/modules/oracle.applcore.model_11.1.1/oracle.applcore.model.stub.ear/META-INF/application.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
<Oct 29, 2013 12:09:32 PM CET> <Warning> <Security> <BEA-090668> <Ignored deployment of role "Admin" for resource "type=<url>, application=DMS Application#11.1.1.1.0, contextPath=/dms, uri=/">
<Oct 29, 2013 12:09:35 PM CET> <Warning> <Connector> <BEA-190155> <Compliance checking/validation of the resource adapter /app/oracle/product/OBIEE11.1.1.7/user_projects/domains/bifoundation_domain/servers/AdminServer/tmp/_WL_user/ESSAPP/z68zjr/stub-ess-ra.rar resulted in the following warnings:
The ra.xml <resourceadapter-class> class 'oracle.as.scheduler.adapter.ra.RAImpl' should implement java.io.Serializable but does not.>
<Oct 29, 2013 12:24:25 PM CET> <Notice> <WebLogicServer> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
<Oct 29, 2013 12:24:25 PM CET> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
<Oct 29, 2013 12:24:25 PM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

Hi VG,
thank u a lot for ur answer. But there are no files at the Admin Server boot.properties path.
and at the BI Server boot.properties path there is no security folder. Do u have any idea why i cant found anything at this directions ? Also I tried again the command "./startWeblogic.sh " and get a new error message which I post below. I am rlly worry about this. Is there maybe a way to reset the OBIEE and undo all changes ?
<Oct 30, 2013 10:00:47 AM CET> <Warning> <EJB> <BEA-010001> <While deploying EJB 'AsyncAdminService_AsyncRequestProcessorMDB', class oracle.j2ee.ws.server.jaxws.AsyncRequestProcessorMDB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Oct 30, 2013 10:00:47 AM CET> <Warning> <EJB> <BEA-010001> <While deploying EJB 'AsyncAdminService_AsyncResponseProcessorMDB', class oracle.j2ee.ws.server.jaxws.AsyncResponseProcessorMDB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
<Oct 30, 2013 10:00:48 AM CET> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application em is not versioned.>
^C<Oct 30, 2013 10:39:50 AM CET> <Notice> <WebLogicServer> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
<Oct 30, 2013 10:39:50 AM CET> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
<Oct 30, 2013 10:39:50 AM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

How do shutdown the weblogic server from the command line prompt using web logic 8.1

I%u2019m currently using weblogic 6.1, but I will upgrade to weblogic 8.1. In weblogic 6.1, the following statements will shutdown the weblogic instance from the command line:
java weblogic.Admin -url t3://hostname:port -username system -password abc SHUTDOWN
How do I shutdown the weblogic server from the command line prompt using web logic 8.1.
Any help will be greatly appreciated.
Maria

Maria <[email protected]> wrote:
How do I shutdown the weblogic server from the
command line prompt using weblogic 8.1?Greetings Maria! Use this document, located here:
http://edocs.bea.com/wls/docs81/admin_ref/cli.html#1131733
Hope this helps...
Brian J. Mitchell
Systems Administrator, TRX
email: [email protected]
office: +1 404 327 7238
mobile: +1 678 283 6530

Weblogic server shutdown error

I am using the following script to shutpdown weblogic server
# Set the server classpath
WEBLOGICCLASSPATH=/weblogic/lib/weblogic510sp4.jar:/weblogic/license:/weblgi
c/classes:/weblogic/lib/weblogicaux.jar
# Java 2
JAVACLASSPATH=/weblogic/classes/boot
java -classpath $JAVACLASSPATH -Dweblogic.class.path=$WEBLOGICCLASSPATH
weblogic.Admin www.kubrick.com SHUTDOWN system 12345678
It dives class not def found error for weblogic.Admin. Any solution ?

Since WLS doesn't need to load anything from weblogic classpath, you can put all
classes in java
classpath . Try this
java -classpath $WL_HOME/classes:$WL_HOME/lib/weblogicaux.jar weblogic.Admin
<url> SHUTDOWN system password.
Kumar
Rakesh Gupta wrote:
I am using the following script to shutpdown weblogic server
# Set the server classpath
WEBLOGICCLASSPATH=/weblogic/lib/weblogic510sp4.jar:/weblogic/license:/weblgi
c/classes:/weblogic/lib/weblogicaux.jar
# Java 2
JAVACLASSPATH=/weblogic/classes/boot
java -classpath $JAVACLASSPATH -Dweblogic.class.path=$WEBLOGICCLASSPATH
weblogic.Admin www.kubrick.com SHUTDOWN system 12345678
It dives class not def found error for weblogic.Admin. Any solution ?

Does BEAs WebLogic Server 8.x support EJB 2.1?

Does BEAs WebLogic Server 8.x support EJB 2.1? When it is Support?

I know weblogic 8.1 is EJB 2.0
"John Naranjo" <[email protected]> wrote:
>
Does BEAs WebLogic Server 8.x support EJB 2.1? When it is Support?

Weblogic server and managed servers sudden shutdown

Hi,
when trying to restart both the admin and managed osb servers. after some time the admin and managed servers are getting shut down. This is what the information i got from logs. Appreciate your help in this regard
####<Aug 18, 2011 12:51:44 PM EDT> <Info> <Health> <weblogic.GCMonitor> <<anonymous>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000011> <1313686304697> <BEA-310002> <38% of the total memory in the server is free>
####<Aug 18, 2011 12:52:06 PM EDT> <Error> <JDBC> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000109> <1313686326579> <BEA-001112> <Test "SELECT 1 FROM DUAL" set up for pool "GLTOdatasource" failed with exception: "oracle.jdbc.xa.OracleXAException".>
####<Aug 18, 2011 12:52:06 PM EDT> <Info> <JDBC> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000109> <1313686326580> <BEA-001128> <Connection for pool "GLTOdatasource" closed.>
####<Aug 18, 2011 12:52:44 PM EDT> <Info> <Health> <weblogic.GCMonitor> <<anonymous>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000011> <1313686364766> <BEA-310002> <61% of the total memory in the server is free>
####<Aug 18, 2011 12:56:45 PM EDT> <Info> <Health> <weblogic.GCMonitor> <<anonymous>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000011> <1313686605051> <BEA-310002> <44% of the total memory in the server is free>
####<Aug 18, 2011 12:58:18 PM EDT> <Info> <Security> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000111> <1313686698580> <BEA-090516> <The CredentialMapper provider has preexisting LDAP data.>
####<Aug 18, 2011 1:02:23 PM EDT> <Notice> <WebLogicServer> <Thread-1> <<WLS Kernel>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000117> <1313686943979> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
####<Aug 18, 2011 1:02:23 PM EDT> <Alert> <gifosb_admin> <Thread-1> <<WLS Kernel>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000117> <1313686943996> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
####<Aug 18, 2011 1:02:24 PM EDT> <Notice> <WebLogicServer> <Thread-1> <<WLS Kernel>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000117> <1313686944005> <BEA-000365> <Server state changed to FORCE_SUSPENDING>
Thanks,
Bharath

<JVM called WLS shutdown hook. The server will force shutdown now>This is your JVM process which is getting killed and hence server is forced to shutdown. On which OS, servers are running? How are you starting the server? If you are on windows, DO NOT close the command prompt through which you started the server.
Regards,
Anuj

How to speed up frequent undeploy and deploy on weblogic server ?

We have one web application deployed on a Weblogic Server (10.3).
We use ANT and the wldeploy task ( http://download.oracle.com/docs/cd/E13222_01/wls/docs90/programming/wldeploy.html ) to UNDEPLOY and DEPLOY (frequently) the webapp.
It seems to us that the entire process (RECOMPILE -> make WAR -> UNDEPLOY -> DEPLOY) , which is completely automatic (made by ANT), is too slow (about 1 minute) , especially the step of DEPLOY.
Do exist some tricks to speed up the entire process ?
We have 4/5 notebook (the developers PCs) and 1 remote Weblogic Server .
(SORRY, some admin can move this thread on weblogic server forum ? Thanks)
Edited by: user3873926 on 29-ott-2009 9.21

Just a suggestion: Try using iWS6.0SP2, it has some performance improvements.

Does BEAs WebLogic Server 8.x support JavaServer Faces?

Does BEAs WebLogic Server 8.x support JavaServer Faces?

I know weblogic 8.1 is EJB 2.0
"John Naranjo" <[email protected]> wrote:
>
Does BEAs WebLogic Server 8.x support EJB 2.1? When it is Support?

Weblogic Server 9.2 - JMS File Store not working as expected.

Hi,
I am facing a problem at the server startup possibly due to huge size of the JMS File Store created.
My question is that our application receives messages via MDB (container managed),
Even after successfully processing the message, the message which is logged in the File Store is not deleted.
How can i make sure that a message which is successfully processed is not logged in the file store?
(considering container managed transactions do not require acknowledgement-mode set in the descriptor, altough i have it specified)
Find the the stack trace on the server log below:
####<Dec 10, 2008 11:45:30 AM CST> <Error> <JMS> <xlqwls01> <ACSServer1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tu
ning)'> <<WLS Kernel>> <> <> <1228931130485> <BEA-040123> <Failed to start JMS Server "SDBJMSServer1" due to weblogic.jms.common.JMSException: web
logic.messaging.kernel.KernelException: Unexpected store exception in messaging kernel recovery.
weblogic.jms.common.JMSException: weblogic.messaging.kernel.KernelException: Unexpected store exception in messaging kernel recovery
at weblogic.jms.backend.BackEnd.open(BackEnd.java:963)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:180)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:589)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:450)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:430)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:100)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
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:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
weblogic.messaging.kernel.KernelException: Unexpected store exception in messaging kernel recovery
at weblogic.messaging.kernel.internal.PersistenceImpl.recover(PersistenceImpl.java:839)
at weblogic.messaging.kernel.internal.KernelImpl.open(KernelImpl.java:235)
at weblogic.jms.backend.BackEnd.open(BackEnd.java:961)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:180)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:589)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:450)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:430)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:100)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
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:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
weblogic.store.PersistentStoreException: [Store:280020]There was an error while reading from the log file
at weblogic.store.io.file.Heap.read(Heap.java:648)
at weblogic.store.io.file.FileStoreIO.readInternal(FileStoreIO.java:224)
at weblogic.store.io.file.FileStoreIO.access$000(FileStoreIO.java:31)
at weblogic.store.io.file.FileStoreIO$Cursor.nextInternal(FileStoreIO.java:573)
at weblogic.store.io.file.FileStoreIO$Cursor.next(FileStoreIO.java:547)
at weblogic.store.internal.PersistentStoreConnectionImpl$CursorImpl.next(PersistentStoreConnectionImpl.java:266)
at weblogic.messaging.kernel.internal.PersistenceImpl.recoverHeaders(PersistenceImpl.java:1148)
at weblogic.messaging.kernel.internal.PersistenceImpl.recover(PersistenceImpl.java:814)
at weblogic.messaging.kernel.internal.KernelImpl.open(KernelImpl.java:235)
at weblogic.jms.backend.BackEnd.open(BackEnd.java:961)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:180)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:589)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:450)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:430)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:100)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
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:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
java.io.IOException: Error reading from file, No such file or directory, errno=2
at weblogic.store.io.file.direct.DirectIONative.read(Native Method)
at weblogic.store.io.file.direct.DirectFileChannel.read(DirectFileChannel.java:133)
at weblogic.store.io.file.StoreFile.read(StoreFile.java:281)
at weblogic.store.io.file.Heap.read(Heap.java:646)
at weblogic.store.io.file.FileStoreIO.readInternal(FileStoreIO.java:224)
at weblogic.store.io.file.FileStoreIO.access$000(FileStoreIO.java:31)
at weblogic.store.io.file.FileStoreIO$Cursor.nextInternal(FileStoreIO.java:573)
at weblogic.store.io.file.FileStoreIO$Cursor.next(FileStoreIO.java:547)
at weblogic.store.internal.PersistentStoreConnectionImpl$CursorImpl.next(PersistentStoreConnectionImpl.java:266)
at weblogic.messaging.kernel.internal.PersistenceImpl.recoverHeaders(PersistenceImpl.java:1148)
at weblogic.messaging.kernel.internal.PersistenceImpl.recover(PersistenceImpl.java:814)
at weblogic.messaging.kernel.internal.KernelImpl.open(KernelImpl.java:235)
at weblogic.jms.backend.BackEnd.open(BackEnd.java:961)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:180)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:589)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:450)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:430)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:100)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
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:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Edited by: user5823244 on Dec 14, 2008 2:59 AM

Hi,
It seems there are two problems going on here:
(1) Forceful shutdowns should not (must not) normally corrupt the file store. There may be a bug in WL, or it may be the admin is arbitrarily deleting some file store files while leaving others in place (not supported).
(2) "Even after successfully processing the message, the message which is logged in the File Store is not deleted."
This is a strong indicator that there's an application error and the message is not actually getting deleted. The file store size is proportional to the number of current messages (successfully processing/acknowledging/committing a received message frees space for new messages), and is not proportional to the number of successfully processed messages.
I think it's likely that the application isn't actually successfully processing the message but is instead receiving a message somehow and is either:
(A) throwing an exception from within an XA-or-non-XA-MDB or auto-ack-onMessage() and somehow forcing the message into a state where its not being redelivered for reprocessing
(B) specifying a transacted session and failing to call session.commit()
(C) specifying an XA transaction capable receive and failing to call commit
(D) specifying a "client acknowledge" mode and failing to call acknowledge .
For evidence, check the console statistics for the destination after "successfully processing" all sent messages: the value of "current" + "pending" should be zero once all processing completes, the value of "received (aka total)" should match the sent message count. If the "current" + "pending" value is non-zero, then this is an indication there are messages that were not successfully processed.
Tom Barnes
WebLogic Server Messaging Developer Team

Problem in starting weblogic server as proxy

I am using weblogic server as Proxy to forward the requests to weblogic cluster.
When i bring up the proxy, it works fine, but when i try to access the application deployed in cluster through Proxy, the proxy server crashes with the follwoing error.
I am Pasting my complete logs below.
Setting JVM memory params for server IRISProxy
Using server IRISProxy-specfic java memory arguments: -Xms32m -Xmx200m -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=80 -XX:MaxPermSize=128m -XX:+DisableExplicitGC -XX:NewRatio=4
WLS Production Mode=true
./startWebLogic.sh[68]: B: not found.
maxfiles=8192
CLASSPATH=/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/CR211812_81sp4.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/CR235145_81sp4.jar:/home/weblogic/bea_wli/weblogic81/common/lib/CR224719_81sp2.jar:/home/weblogic/bea_wli/weblogic81/common/lib/CR137449_81sp2.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic_knex_patch.jar:/home/weblogic/bea_wli/weblogic81/common/lib/log4j.jar:/home/weblogic/bea_wli/weblogic81/server/lib/debugging.jar:/home/weblogic/bea_wli/weblogic81/server/lib/knex.jar:/home/weblogic/bea_wli/weblogic81/javelin/lib/javelin.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wlw-lang.jar:/home/weblogic/bea_wli/jdk141_05/lib/tools.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic_sp.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic.jar:/home/weblogic/bea_wli/weblogic81/server/lib/ojdbc14.jar:/home/weblogic/bea_wli/weblogic81/server/lib/ant/ant.jar:/home/weblogic/bea_wli/jdk141_05/jre/lib/rt.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/agent_tools_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-Admin:/opt/jes/policy_agent/IdentityServer/j2ee_agents/locale:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_agent_sdk_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_agent_filter_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_sdk.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_services.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_sso_provider.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_logging.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_wl70_agent_2_1.jar:::::/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/SecurityClient-v1.0.7.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/Log4JInitServlet.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/log4j_IRIS-1.2.4.jar:::/home/weblogic/bea_wli/weblogic81/server/lib/webserviceclient.jar:/home/weblogic/bea_wli/weblogic81/server/lib/webserviceclient+ssl.jar:/home/weblogic/bea_wli/weblogic81/server/lib/xbean.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wlxbean.jar:/home/weblogic/bea_wli/weblogic81/server/lib/xqrl.jar:/home/weblogic/bea_wli/weblogic81/server/lib/netui/netui-compiler.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wli.jar:/home/weblogic/bea_wli/weblogic81/server/lib/fop.jar:/home/weblogic/bea_wli/weblogic81/integration/adapters/sample/lib/sample-eis.jar:
PATH=/home/weblogic/bea_wli/weblogic81/server/bin:/home/weblogic/bea_wli/weblogic81/server/bin:/home/weblogic/bea_wli/jdk141_05/jre/bin:/home/weblogic/bea_wli/jdk141_05/bin:/usr/sbin:/usr/bin:/usr/ccs/bin:/usr/contrib/bin:/usr/local/bin:/opt/hparray/bin:/opt/nettladm/bin:/opt/upgrade/bin:/opt/fcms/bin:/opt/pd/bin:/usr/bin/X11:/usr/contrib/bin/X11:/opt/resmon/bin:/opt/perf/bin:/opt/prm/bin:/opt/mx/bin:/opt/gnome/bin:/opt/wbem/bin:/opt/wbem/sbin:/opt/ignite/bin:/opt/graphics/common/bin:/usr/sbin/diag/contrib:/opt/sec_mgmt/spc/bin:/opt/networker/bin:/opt/sec_mgmt/bastille/bin:/opt/hpnpl//bin:/opt/mozilla:/opt/OV/bin/OpC:/opt/OV/bin:/sbin:/home/root:/util:/home/weblogic/bea_wli/jdk141_05/jre/bin:/usr/local/bin:/usr/local/sbin:.
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
java version "1.4.1.05"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1.05-030910-01:23)
Java HotSpot(TM) Server VM (build 1.4.1 1.4.1.05-030910-02:49-PA_RISC2.0 PA2.0, mixed mode)
Starting WLS with line:
/home/weblogic/bea_wli/jdk141_05/bin/java -server -Xms32m -Xmx200m -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=80 -XX:MaxPermSize=128m -XX:+DisableExplicitGC -XX:NewRatio=4 -Dweblogic.security.SSL.trustedCAKeyStore=/home/weblogic/bea_wli/weblogic81/server/lib/cacerts -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dapp.config.dir=/home/weblogic/upload/appsvcdomain/IRIS/config -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dapp.config.dir=/home/weblogic/upload/appsvcdomain/IRIS/config -da -Dplatform.home=/home/weblogic/bea_wli/weblogic81 -Dwls.home=/home/weblogic/bea_wli/weblogic81/server -Dwli.home=/home/weblogic/bea_wli/weblogic81/integration -Dlog4j.configuration=file:/home/weblogic/bea_wli/weblogic81/common/lib/workshopLogCfg.xml -Dweblogic.management.discover=false -Dweblogic.management.server=t3://170.63.142.14:8100 -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=true -Dweblogic.security.SSL.trustedCAKeyStore=/home/weblogic/bea_wli/weblogic81/server/lib/cacerts -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dweblogic.Name=IRISProxy -Dweblogic.ProductionModeEnabled=true -Djava.security.policy=/home/weblogic/bea_wli/weblogic81/server/lib/weblogic.policy weblogic.Server
Bad level value for property: com.iplanet.services.debug.level
Bad level value for property: com.sun.identity.agents.logging.level
Bad level value for property: com.sun.am.policy.amFilter.audit.level
<Mar 15, 2006 3:40:33 PM EST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.4.1 1.4.1.05-030910-02:49-PA_RISC2.0 PA2.0 from Hewlett-Packard Company>
<Mar 15, 2006 3:40:34 PM EST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://170.63.142.14:8100 to check if there exists a running admin server at this URL.>
<Mar 15, 2006 3:40:34 PM EST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Mar 15, 2006 3:40:35 PM EST> <Warning> <Configuration Management> <BEA-150033> <The managed server should not be started in development mode.>
<Mar 15, 2006 3:40:35 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Temporary Patch for CR211812 01/23/2005 22:15:39
WebLogic Temporary Patch for CR235145 08/16/2005 11:44:59
WebLogic Temporary Patch for CR224719 04/29/2005 16:40:35
WebLogic Temporary Patch for CR137449 02/24/2004 10:48:06
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Integration 8.1 SP2 Thu Dec 11 22:07:14 PST 2003 148883>
<Mar 15, 2006 3:40:35 PM EST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://170.63.142.14:8100 to retrieve the initial configuration.>
<Mar 15, 2006 3:40:46 PM EST> <Notice> <Log Management> <BEA-170019> <The server log file /home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/IRISProxy/IRISProxy.log is opened. All server side log events will be written to this file.>
<Mar 15, 2006 3:41:29 PM EST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Mar 15, 2006 3:41:29 PM EST> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "IRISProxy" for domain "AppSvcDomain">
<Mar 15, 2006 3:41:57 PM EST> <Warning> <HTTP> <BEA-101299> <The servlet-mapping for servlet-name "HttpClusterServlet" will override the default mapping for *.jsp. This can lead to a show code vulnerability.>
<Mar 15, 2006 3:42:06 PM EST> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias irisqa from the jks keystore file /home/weblogic/bea_wli/weblogic81/server/lib/trustIdentityKeys/iris_qa.jks.>
<Mar 15, 2006 3:42:06 PM EST> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias irisqa from the jks keystore file /home/weblogic/bea_wli/weblogic81/server/lib/trustIdentityKeys/iris_qa.jks.>
<Mar 15, 2006 3:42:08 PM EST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /home/weblogic/bea_wli/jdk141_05/jre/lib/security/cacerts.>
<Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "IRISProxy" for domain "AppSvcDomain" running in Production Mode>
<Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 7001, ip address 170.63.142.29>
<Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000355> <Thread "SSLListenThread.Default" listening on port 443, ip address 170.63.142.29>
<Mar 15, 2006 5:02:26 PM EST> <Emergency> <WebLogicServer> <BEA-000209> <ListenThread.run() failed: java.lang.NoSuchMethodError: com.certicom.tls.interfaceimpl.TLSSystem.createServer(Ljavax/net/ssl/SSLSocket;Ljava/io/InputStream;Ljava/io/OutputStream;Ljava/io/Serializable;)Lcom/certicom/tls/TLSConnection;
java.lang.NoSuchMethodError: com.certicom.tls.interfaceimpl.TLSSystem.createServer(Ljavax/net/ssl/SSLSocket;Ljava/io/InputStream;Ljava/io/OutputStream;Ljava/io/Serializable;)Lcom/certicom/tls/TLSConnection;
     at javax.net.ssl.impl.SSLSocketImpl.resetConnection(Unknown Source)
     at javax.net.ssl.impl.SSLServerSocketImpl.accept(Unknown Source)
     at weblogic.t3.srvr.ListenThread.accept(ListenThread.java:739)
     at weblogic.t3.srvr.ListenThread.run(ListenThread.java:292)
>
<Mar 15, 2006 5:02:26 PM EST> <Emergency> <WebLogicServer> <BEA-000210> <The WebLogic Server is no longer listening for connections.>
<Mar 15, 2006 5:02:26 PM EST> <Alert> <WebLogicServer> <BEA-000218> <Server shutdown has been requested by <WLS Kernel>>
<Mar 15, 2006 5:02:26 PM EST> <Notice> <WebLogicServer> <BEA-000353> <Thread "ListenThread.Default" stopped listening on port 7001, ip address 170.63.142.29>
<Mar 15, 2006 5:02:26 PM EST> <Notice> <WebLogicServer> <BEA-000353> <Thread "SSLListenThread.Default" stopped listening on port 443, ip address 170.63.142.29>
<Mar 15, 2006 5:02:26 PM EST> <Alert> <WebLogicServer> <BEA-000219> <The shutdown sequence has been initiated.>
Can someone help me in solving this problem
Thanks
Kris

I solved this problem by commenting the 8.1 SP4 patches i applied in 8.1 SP2
WebLogic Temporary Patch for CR211812
WebLogic Temporary Patch for CR235145
Once i commented the above patches in the CLASSPATH.
The issue is resolved.

WebLogic hangs around after shutdown process appears to complete - Message Driven Bean related

On my current project we have some Ant scripts that automatically
start and stop WebLogic. The stop script equates to (not exactly but
close enough):
java weblogic.Admin -url localhost:8001 -password password -username
username SHUTDOWN
WebLogic is start and shutdown for each system module. All modules
use the exact same script for these two actions. Some of the modules
use Message Driven Beans and consequently, since these use JMS, a
JMSxxx.dat file is generated in the jms_store directory. As part of
the cleanup process the jms_store directory and all files in it are to
be deleted AFTER WebLogic shuts down.
The shutdown process works fine in all cases where JMS is not used and
in all cases where JMS IS used but there are NO message driven beans.
However, when there is a message driven bean the server does not shut
down in a timely manner, sometimes not at all (no error messages are
produced), and the JMSxx.dat file
remains locked. Consequently, all of the tests run via the ant script
for modules come to a grinding halt (i.e. environment could not be
cleaned so further tests would be skewed).
Can anyone shed some light on a definitive order of events during
WebLogic's shutdown process? What is the best way to test for the
server being up? I know there is a ping utility for weblogic - should
this be used or should a connection to a JNDI or JMS listening port do
the trick? Any other ideas would be welcome.
Thanks in advance,
Mark

On my current project we have some Ant scripts that automatically
start and stop WebLogic. The stop script equates to (not exactly but
close enough):
java weblogic.Admin -url localhost:8001 -password password -username
username SHUTDOWN
WebLogic is start and shutdown for each system module. All modules
use the exact same script for these two actions. Some of the modules
use Message Driven Beans and consequently, since these use JMS, a
JMSxxx.dat file is generated in the jms_store directory. As part of
the cleanup process the jms_store directory and all files in it are to
be deleted AFTER WebLogic shuts down.
The shutdown process works fine in all cases where JMS is not used and
in all cases where JMS IS used but there are NO message driven beans.
However, when there is a message driven bean the server does not shut
down in a timely manner, sometimes not at all (no error messages are
produced), and the JMSxx.dat file
remains locked. Consequently, all of the tests run via the ant script
for modules come to a grinding halt (i.e. environment could not be
cleaned so further tests would be skewed).
Can anyone shed some light on a definitive order of events during
WebLogic's shutdown process? What is the best way to test for the
server being up? I know there is a ping utility for weblogic - should
this be used or should a connection to a JNDI or JMS listening port do
the trick? Any other ideas would be welcome.
Thanks in advance,
Mark

Deployment Manager Error with Oracle Weblogic Server

Hi,
Every time i try to open nexaweb client for Import/Export. I get the following error:-
"Either your session timed out or you are trying to access a page without logging in." .
Are there any other permission I'm suppose to grant nexaweb through Welogic admin control?

I still had no luck with neither
* Weblogic 10.3 (the import applet doesn't match the authentication in the web application, no matter which JDK 5/6 I set in the browser or if I use IE instead of FireFox)
* OC4J (downloaded from the oracle.com): the install_server.sh script complains about the server not being running (while I can shutdown it by RMI console with no problem using the same username/password/RMI port).
Instead I tried JBoss 4.2.3 (downloaded from jboss.com) and unzipped it:install_server.sh works without problem just saying
You must copy the .xldatabasekey file from the \xellerate\config\ directory of the original installation to the \xellerate\config\ directory of the current installation.
+.xldatabasekeyThe Oracle Identity Manager installation log file is located at /opt/oracle/app/middleware/oim/xellerate/logs.+
Which is due to the fact that i previously configured weblogic: so I copied it from my OIM Weblogic installation:
cp ./oim.weblogic/xellerate/config/.xldatabasekey oim/xellerate/config/
Run the OIM-ized JBoss instance and, voila'!, the import applet now perfectly recognizes my logged in user and I can now proceed with my real work ... just thinking that I lost 4 days around configuring the OIM server with Weblogic ...

Weblogic server 5.1 restarted automatically

Hi,
I am using weblogic 5.1 with SP 13. While accessing the pages, frequently
it is throwing
HTTP> Connection failure
java.net.SocketException: Connection reset by peer
     at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java,
Compiled Code)
     at java.lang.Exception.<init>(Exception.java, Compiled Code)
     at java.io.IOException.<init>(IOException.java, Compiled Code)
     at java.net.SocketException.<init>(SocketException.java, Compiled
Code)
     at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java,
Compiled Code)
     at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
Code)
And in a very rare cases, the weblogic server system shutsdown and starts immediately.
What is the cause to make the system shutdown? Thanks in advance.

Hi,
I am using weblogic 5.1 with SP 13. While accessing the pages, frequently
it is throwing
HTTP> Connection failure
java.net.SocketException: Connection reset by peer
     at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java,
Compiled Code)
     at java.lang.Exception.<init>(Exception.java, Compiled Code)
     at java.io.IOException.<init>(IOException.java, Compiled Code)
     at java.net.SocketException.<init>(SocketException.java, Compiled
Code)
     at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java,
Compiled Code)
     at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
Code)
And in a very rare cases, the weblogic server system shutsdown and starts immediately.
What is the cause to make the system shutdown? Thanks in advance.

How to delete the deployed composite in weblogic server 11g

Can someone tell me how to delete the deployed composite in weblogic server 11g ?I'm facing an issue where the weblogic server is getting started and immediately after sometime the server changes to "Force shutdown"..When i checked the logs,there is an error in one of the composite i deployed..So now i wanted to delete the deployed composite?Please help ....
Thanks

Hi
1. Deleting a domain will not hold any references. But make sure that under your user_projects/applications also remove the folder that matches with your domain. Basically under user_projects folder you will see 2 folders named applications and domains. When you create a domain say mySoaDomain, it will crate a folder with the same name under applications folder also with few files like em.ear. If you do this, then you can crate a new soa domain and use the same old name.
2. NOW comes the most important thing. If you create a new SOADomain, at one point, you had to give details for soainfra and mds schemas. If you give your current existing db details (that was used for your old deleted domain), then you may still have the issues. Because the soainfra db may still have the instances for your old process.
3. If you really want to have a full clean soa domain, here is what you do:
a) Run rcu and drop the existing schemas for soainfra and mds.
b) Run rcu again and create above schemas again.
c) Now create SOADomain using config wizard and refer above clean rcu db and you are all set.
3. Under your domain root folder, just searh for files named with your workflow and you should see the .jar location.
Thanks
Ravi Jegga

Error when starting Weblogic server with Coherence

We want to use Coherence 3.6 with Weblogic Server 10.3. During server startup, we get the following error. My understanding is the cluster should be started automatically based on the configuration listed below the error. Appreciate any pointers.
<Dec 15, 2011 3:20:11 PM PST> <Error> <Coherence> <BEA-000000> <2011-12-15 15:20:11.920/67.311 Oracle Coherence SE 3.6.0.4 <Error> (thread=Cluster, member=n/a): This member could not join the cluster because of a configuration mismatch between this member and the configuration being used by the rest of the cluster. This member specified a cluster name of "EPCIS" which did not match the name of the running cluster. This indicates that there are multiple clusters on this network attempting to use overlapping network configurations. Rejected by Member(Id=9, Timestamp=2011-11-16 13:58:42.941, Address=10.229.189.30:8088, MachineId=21022, Location=site:us.oracle.com,machine:adc2101177,process:30667, Role=WeblogicServer).>
<Dec 15, 2011 3:20:11 PM PST> <Error> <oracle.apps.pas.epc.framework.db.Cache> <BEA-000000> <java.lang.RuntimeException: Failed to start Service "Cluster" (ServiceState=SERVICE_STOPPED, STATE_JOINING)>
<Dec 15, 2011 3:20:11 PM PST> <Error> <Coherence> <BEA-000000> <2011-12-15 15:20:11.957/67.349 Oracle Coherence SE 3.6.0.4 <Error> (thread=[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)', member=n/a): Error while starting cluster: java.lang.RuntimeException: Failed to start Service "Cluster" (ServiceState=SERVICE_STOPPED, STATE_JOINING)
CONFIGURATION:
We have the following descriptor (epcis-coherence-cache-config.xml) in $DOMAIN_HOME/epc-config:
<?xml version="1.0"?>
<!DOCTYPE cache-config SYSTEM "cache-config.dtd">
<cache-config>
<caching-scheme-mapping>
<cache-mapping>
<cache-name>*</cache-name>
<scheme-name>distributed</scheme-name>
</cache-mapping>
</caching-scheme-mapping>
<caching-schemes>
<distributed-scheme>
<scheme-name>distributed</scheme-name>
<service-name>DistributedCache</service-name>
<backing-map-scheme>
<local-scheme></local-scheme>
</backing-map-scheme>
<autostart>true</autostart>
</distributed-scheme>
</caching-schemes>
</cache-config>
We also have tangosol-coherence-override.xml in the same dir:
<coherence>
<cluster-config>
<member-identity>
<cluster-name system-property="tangosol.coherence.clustername">EPCIS</cluster-name>
</member-identity>
</cluster-config>
<configurable-cache-factory-config>
<class-name>com.tangosol.net.DefaultConfigurableCacheFactory</class-name>
<init-params>
<init-param>
<param-type>java.lang.String</param-type>
<param-value>epcis-coherence-cache-config.xml</param-value>
</init-param>
</init-params>
</configurable-cache-factory-config>
<license-config>
<edition-name system-property="tangosol.coherence.edition">SE</edition-name>
<license-mode system-property="tangosol.coherence.mode">dev</license-mode>
</license-config>
</coherence>
We have modified startWebLogic.sh by adding:
PRE_CLASSPATH="/slot/xyz/oracle/mwhome/oracle_common/modules/oracle.coherence_3.6/coherence.jar:${DOMAIN_HOME}/epc-config/:${PRE_CLASSPATH}"

As the error message says, your WebLogic server is trying to join a cluster that has a different cluster name.
This bit in your tangosol-coherence-override.xml file or the tangosol.coherence.clustername system property must be the same in all members of the cluster
<cluster-name system-property="tangosol.coherence.clustername">EPCIS</cluster-name>JK

Weblogic server is being shutdown frequently

Similar Messages

Maybe you are looking for