I am frequently seeing these messages in the redis logs
1#
602854:M 23 Dec 2022 09:48:54.028 * 10 changes in 300 seconds. Saving...
602854:M 23 Dec 2022 09:48:54.035 * Background saving started by pid 3266364
3266364:C 23 Dec 2022 09:48:55.844 * DB saved on disk
3266364:C 23 Dec 2022 09:48:55.852 * RDB: 12 MB of memory used by copy-on-write
602854:M 23 Dec 2022 09:48:55.938 * Background saving terminated with success
2#
LOADING Redis is loading the dataset in memory
3#
7678:signal-handler (1671738516) Received SIGTERM scheduling shutdown...
7678:M 22 Dec 2022 23:48:36.300 # User requested shutdown...
7678:M 22 Dec 2022 23:48:36.300 # systemd supervision requested, but NOTIFY_SOCKET not found
7678:M 22 Dec 2022 23:48:36.300 * Saving the final RDB snapshot before exiting.
7678:M 22 Dec 2022 23:48:36.300 # systemd supervision requested, but NOTIFY_SOCKET not found
7678:M 22 Dec 2022 23:48:36.720 * DB saved on disk
7678:M 22 Dec 2022 23:48:36.720 * Removing the pid file.
7678:M 22 Dec 2022 23:48:36.720 # Redis is now ready to exit, bye bye...
7901:C 22 Dec 2022 23:48:37.071 # WARNING supervised by systemd - you MUST set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.
7901:C 22 Dec 2022 23:48:37.071 # systemd supervision requested, but NOTIFY_SOCKET not found
7914:C 22 Dec 2022 23:48:37.071 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
7914:C 22 Dec 2022 23:48:37.071 # Redis version=6.0.9, bits=64, commit=00000000, modified=0, pid=7914, just started
7914:C 22 Dec 2022 23:48:37.071 # Configuration loaded
Are these messages concerning?
Let me know if there's any optimization to be carried out in terms of settings.
The first set of informational messages is related to Redis persistence: it appears your Redis node is configured to save the database to disk if 300 seconds elapsed and it surpassed 10 write operations against it. You can change that according to your needs through the Redis configuration file.
The message LOADING Redis is loading the dataset in memory, on the other side, is an error message received while attempting to connect to a Redis instance which is loading its dataset in memory: that occurs during the startup for standalone servers and master nodes or when replicas reconnect and fully resynchronize with master. If you are seeing this error too often and not right after a system restart, I would suggest to check your system log files and learn why your Redis instance is restarting or resynchronizing (depending on your topology).
I have a weblogic server running on AWS. I took a AMI backup of it and created a new instance from the AMI.
In the new instance, when I try to start the weblogic, It stuck at following state.
<Dec 11, 2018 12:00:01 AM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050 >
<Dec 11, 2018 12:00:02 AM IST> <Notice> <WebLogicServer> <BEA-000365>
<Server state changed to STARTING>
<Dec 11, 2018 12:00:02 AM IST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Dec 11, 2018 12:00:02 AM IST> <Notice> <Log Management> <BEA-170019> <The server log file /home/weblogic/Oracle/Middleware/user_projects/domains/ClassicDomain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.
Also see thread dump of the JVM at https://pastebin.com/D9MYSvBj
Any help would highly appreciated.
-- Arun
Issue fixed.
From the thread dump, I found following
"[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=10 tid=0x00007fda6aad4800 nid=0x6a3b runnable [0x00007fda41d5d000]
java.lang.Thread.State: RUNNABLE
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(FileInputStream.java:220)
at sun.security.provider.SeedGenerator$URLSeedGenerator.getSeedBytes(SeedGenerator.java:493)
at sun.security.provider.SeedGenerator.generateSeed(SeedGenerator.java:117)
at sun.security.provider.SecureRandom$SeederHolder.<clinit>(SecureRandom.java:167)
at sun.security.provider.SecureRandom.engineNextBytes(SecureRandom.java:184)
- locked <0x00000000ece53ac0> (a sun.security.provider.SecureRandom)
at java.security.SecureRandom.nextBytes(SecureRandom.java:433)
- locked <0x00000000ece53d60> (a java.security.SecureRandom)
at oracle.ldap.util.guid.GUIDParamGenerator.generateClockSequence(GUIDParamGenerator.java:128)
Did some search in Google and found a solution to change following line in $JAVA_HOME/jre/lib/security/java.security
From
securerandom.source=file:/dev/urandom
To
securerandom.source=file:/dev/./urandom
And restarted weblogic fixed the issue.
Ref : http://ruleoftech.com/2016/avoiding-jvm-delays-caused-by-random-number-generation
Thanks
Arun
We have a JSF application that was on Weblogic 10.3.6 and that we try to deploy on Weblogic 12.2.1.
For information, we succeeded in deploying on Weblogic 12.1.3 without any changes in the project.
We are facing a NullPointerException while deploying on Weblogic 12.2.1 :
.
.
JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000
.
CLASSPATH=C:\tools\java8\JDK18~1.0_1\lib\tools.jar;C:\BEA122~1.1\wlserver\server\lib\weblogic.jar;C:\BEA122~1.1\oracle_common\modules\net.sf.antcontrib_1.1.0.0_1-0b3\lib\ant-contrib.jar;C:\BEA122~1.1\wlserver\modules\features\oracle.wls.common.nodemanager.jar;C:\BEA122~1.1\oracle_common\modules\com.oracle.cie.config-wls-online_8.2.0.0.jar;C:\BEA122~1.1\wlserver\common\derby\lib\derbyclient.jar;C:\BEA122~1.1\wlserver\common\derby\lib\derby.jar;C:\PROGRA~2\INSTAN~1\ojdbc14.jar
.
PATH=C:\BEA122~1.1\USER_P~1\domains\myDomain\bin;;C:\BEA122~1.1\wlserver\server\native\win\x64;C:\BEA122~1.1\wlserver\server\bin;C:\BEA122~1.1\oracle_common\modules\org.apache.ant_1.9.2\bin;C:\tools\java8\JDK18~1.0_1\jre\bin;C:\tools\java8\JDK18~1.0_1\bin;C:\PROGRA~3\Oracle\Java\javapath;C:\Windows\System32;C:\Windows;C:\Windows\System32\wbem;C:\Windows\System32\WINDOW~1\v1.0\;C:\PROGRA~2\QUICKT~1\QTSystem;C:\PROGRA~2\INSTAN~1\;C:\PROGRA~1\TORTOI~1\bin;C:\tools\org\apache\maven\maven\303812~1.3\bin;C:\tools\com\sun\java\jdk\6U23-W~1\bin;C:\PROGRA~2\NETCDF~1;C:\BEA122~1.1\wlserver\server\native\win\x64\oci920_8
.
***************************************************
* 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 WLS with line:
C:\tools\java8\JDK18~1.0_1\bin\java -server -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx512m -XX:CompileThreshold=8000 -Dweblogic.Name=AdminServer -Djava.security.policy=C:\BEA122~1.1\wlserver\server\lib\weblogic.policy -Xverify:none -Djava.system.class.loader=com.oracle.classloader.weblogic.LaunchClassLoader -javaagent:C:\BEA122~1.1\wlserver\server\lib\debugpatch-agent.jar -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dwls.home=C:\BEA122~1.1\wlserver\server -Dweblogic.home=C:\BEA122~1.1\wlserver\server weblogic.Server
Listening for transport dt_socket at address: 8453
<30 déc. 2016 10 h 11 CET> <Info> <Security> <BEA-090905> <Disabling the CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true.>
<30 déc. 2016 10 h 11 CET> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG128 to HMACDRBG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true.>
<30 déc. 2016 10 h 11 CET> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 25.112-b15 from Oracle Corporation.>
<30 déc. 2016 10 h 11 CET> <Info> <RCM> <BEA-2165021> <"ResourceManagement" is not enabled in this JVM. Enable "ResourceManagement" to use the WebLogic Server "Resource Consumption Management" feature. To enable "ResourceManagement", you must specify the following JVM options in the WebLogic Server instance in which the JVM runs: -XX:+UnlockCommercialFeatures -XX:+ResourceManagement.>
<30 déc. 2016 10 h 11 CET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 12.2.1.0.0 Tue Oct 6 10:05:47 PDT 2015 1721936>
<30 déc. 2016 10 h 11 CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING.>
<30 déc. 2016 10 h 11 CET> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool.>
<30 déc. 2016 10 h 11 CET> <Info> <WorkManager> <BEA-002942> <CMM memory level becomes 0. Setting standby thread pool size to 256.>
<30 déc. 2016 10 h 11 CET> <Notice> <Log Management> <BEA-170019> <The server log file weblogic.logging.FileStreamHandler instance=892551724
Current log file=C:\bea12.2.1\user_projects\domains\myDomain\servers\AdminServer\logs\AdminServer.log
Rotation dir=C:\bea12.2.1\user_projects\domains\myDomain\servers\AdminServer\logs
is opened. All server side log events will be written to this file.>
<30 déc. 2016 10 h 11 CET> <Notice> <Security> <BEA-090946> <Security pre-initializing using security realm: myrealm>
<30 déc. 2016 10 h 11 CET> <Notice> <Security> <BEA-090947> <Security post-initializing using security realm: myrealm>
<30 déc. 2016 10 h 11 CET> <Notice> <Security> <BEA-090082> <Security initialized using administrative security realm: myrealm>
<30 déc. 2016 10 h 11 CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY.>
<30 déc. 2016 10 h 11 CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING.>
<30 déc. 2016 10 h 11 CET> <Notice> <Log Management> <BEA-170036> <The Logging monitoring service timer has started to check for logged message counts every 30 seconds.>
<30 déc. 2016 10 h 11 CET> <Notice> <Log Management> <BEA-170027> <The server has successfully established a connection with the Domain level Diagnostic Service.>
<30 déc. 2016 10 h 11 CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN.>
<30 déc. 2016 10 h 11 CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING.>
<30 déc. 2016 10 h 11 CET> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
<30 déc. 2016 10 h 11 CET> <Warning> <Server> <BEA-002611> <The hostname "DSP0761974.atlas.edf.fr", maps to multiple IP addresses: 163.81.65.152, 0:0:0:0:0:0:0:1.>
<30 déc. 2016 10 h 11 CET> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 163.81.65.152:7001 for protocols iiop, t3, ldap, snmp, http.>
<30 déc. 2016 10 h 11 CET> <Notice> <WebLogicServer> <BEA-000331> <Started the WebLogic Server Administration Server "AdminServer" for domain "myDomain" running in development mode.>
<30 déc. 2016 10 h 11 CET> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 0:0:0:0:0:0:0:1:7001 for protocols iiop, t3, ldap, snmp, http.>
<30 déc. 2016 10 h 11 CET> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
<30 déc. 2016 10 h 11 CET> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 163.81.65.152:7001 for protocols iiop, t3, ldap, snmp, http.>
<30 déc. 2016 10 h 11 CET> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 0:0:0:0:0:0:0:1:7001 for protocols iiop, t3, ldap, snmp, http.>
<30 déc. 2016 10 h 11 CET> <Notice> <WebLogicServer> <BEA-000360> <The server started in RUNNING mode.>
<30 déc. 2016 10 h 11 CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING.>
<30 déc. 2016 10 h 12 CET> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID "1668134555370" for task "0" on [partition-name: DOMAIN]. Error is: "weblogic.application.ModuleException: java.lang.NullPointerException"
weblogic.application.ModuleException: java.lang.NullPointerException
at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:114)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:100)
at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:196)
at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:191)
at weblogic.application.utils.StateMachineDriver$ParallelChange.run(StateMachineDriver.java:83)
Truncated. see log file for complete stacktrace
Caused By: java.lang.NullPointerException
at java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1011)
at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006)
at weblogic.spring.monitoring.instrumentation.SpringClassPreprocessor.createSpringInstrumentorEngineIfNecessary(SpringClassPreprocessor.java:67)
at weblogic.spring.monitoring.instrumentation.SpringClassPreprocessor.<init>(SpringClassPreprocessor.java:26)
at weblogic.spring.monitoring.instrumentation.SpringInstrumentationUtils.addSpringInstrumentor(SpringInstrumentationUtils.java:87)
Truncated. see log file for complete stacktrace
>
<30 déc. 2016 10 h 12 CET> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application "MyProject-ear".>
<30 déc. 2016 10 h 12 CET> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: java.lang.NullPointerException
at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:114)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:100)
at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:196)
at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:191)
at weblogic.application.utils.StateMachineDriver$ParallelChange.run(StateMachineDriver.java:83)
Truncated. see log file for complete stacktrace
Caused By: java.lang.NullPointerException
at java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1011)
at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006)
at weblogic.spring.monitoring.instrumentation.SpringClassPreprocessor.createSpringInstrumentorEngineIfNecessary(SpringClassPreprocessor.java:67)
at weblogic.spring.monitoring.instrumentation.SpringClassPreprocessor.<init>(SpringClassPreprocessor.java:26)
at weblogic.spring.monitoring.instrumentation.SpringInstrumentationUtils.addSpringInstrumentor(SpringInstrumentationUtils.java:87)
Truncated. see log file for complete stacktrace
Here is the full stacktrace :
weblogic.application.ModuleException: java.lang.NullPointerException
at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:114)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:100)
at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:196)
at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:191)
at weblogic.application.utils.StateMachineDriver$ParallelChange.run(StateMachineDriver.java:83)
at weblogic.application.utils.StateMachineDriver.nextStateInParallel(StateMachineDriver.java:144)
at weblogic.application.internal.flow.ModuleStateDriver.parallelPrepare(ModuleStateDriver.java:50)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:76)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:730)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:242)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:67)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:158)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:229)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:103)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:237)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:792)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1306)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:264)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:177)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:643)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:348)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:333)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:54)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:617)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:397)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:346)
Caused By: java.lang.NullPointerException
at java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1011)
at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006)
at weblogic.spring.monitoring.instrumentation.SpringClassPreprocessor.createSpringInstrumentorEngineIfNecessary(SpringClassPreprocessor.java:67)
at weblogic.spring.monitoring.instrumentation.SpringClassPreprocessor.<init>(SpringClassPreprocessor.java:26)
at weblogic.spring.monitoring.instrumentation.SpringInstrumentationUtils.addSpringInstrumentor(SpringInstrumentationUtils.java:87)
at weblogic.servlet.internal.WebAppInternalModuleExtension$SpringInstrumentationExtension.doInstrumentation(WebAppInternalModuleExtension.java:113)
at weblogic.servlet.internal.WebAppInternalModuleExtension$SpringInstrumentationExtension.access$400(WebAppInternalModuleExtension.java:102)
at weblogic.servlet.internal.WebAppInternalModuleExtension.prePrepare(WebAppInternalModuleExtension.java:57)
at weblogic.application.internal.ExtensibleModuleWrapper$PrepareStateChange.next(ExtensibleModuleWrapper.java:293)
at weblogic.application.internal.ExtensibleModuleWrapper$PrepareStateChange.next(ExtensibleModuleWrapper.java:285)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
at weblogic.application.internal.ExtensibleModuleWrapper.prepare(ExtensibleModuleWrapper.java:109)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:100)
at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:196)
at weblogic.application.internal.flow.ModuleStateDriver$1.next(ModuleStateDriver.java:191)
at weblogic.application.utils.StateMachineDriver$ParallelChange.run(StateMachineDriver.java:83)
at weblogic.application.utils.StateMachineDriver.nextStateInParallel(StateMachineDriver.java:144)
at weblogic.application.internal.flow.ModuleStateDriver.parallelPrepare(ModuleStateDriver.java:50)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:76)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:730)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:242)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:67)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:158)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:229)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:103)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:237)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:792)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1306)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:264)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:177)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:643)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:348)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:333)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:54)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:617)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:397)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:346)
As you can see in the stacktrace, all classes involved are weblogic's classes and no class from my project.
Does anyone have an idea for this problem ?
Thanks in advance
I finally got the solution from Oracle :
Cause
The InvalidPointcutException was raised because of java.lang.ClassCastException message: "antlr.CommonToken cannot be cast to
antlr.Token".
The reason being the jar antlr-2.7.6.jar packaged with the ear file conflicting with the default class loader
Solution
Add the parameter -DANTLR_USE_DIRECT_CLASS_LOADING=true to last occurence of JAVA_OPTIONS in setDomainEnv.cmd file
Stop all the servers
rename tmp and cache folders under each server directory.
Restart the servers.
Deploy the application
I have an installation of couchdb which has been working well for a few weeks now. Today it started to throw an os_process_error exit status 1 when attempting to look at any view. The documents in the DB are very small and the views a quite simple. Total DB size is 20mb, largest document is 2mb, i have noticed that the ERL process pegs the CPU at 99%.
I've looked at:
CouchDB delay building index (CouchDB 1.5.0 on Windows Server 2008 R2)
Specific couchdb views suddenly start timing out
I've increased my time out to 50000 seconds, then lowered it to 500 to see if i could find the document which was killing everything but nothing shows up. Stale views still work as well.
Below is the debug error:
[Mon, 10 Nov 2014 19:22:19 GMT] [debug] [<0.118.0>] Successful cookie auth as: "sking"
[Mon, 10 Nov 2014 19:22:19 GMT] [info] [<0.118.0>] 192.168.247.158 - - GET /_config/native_query_servers/ 200
[Mon, 10 Nov 2014 19:22:19 GMT] [error] [<0.231.0>] OS Process Error <0.233.0> :: {os_process_error,
{exit_status,1}}
[Mon, 10 Nov 2014 19:22:19 GMT] [error] [emulator] Error in process <0.231.0> with exit value: {{nocatch,{os_process_error,{exit_status,1}}},[{couch_os_process,prompt,2,[{file,"c:/cygwin/relax/APACHE~2.1/src/couchdb/couch_os_process.erl"},{line,57}]},{couch_query_servers,map_doc_raw,2,[{file,"c:/cygwin/relax...
[Mon, 10 Nov 2014 19:22:19 GMT] [debug] [<0.117.0>] Minor error in HTTP request: {os_process_error,
{exit_status,1}}
[Mon, 10 Nov 2014 19:22:19 GMT] [debug] [<0.117.0>] Stacktrace: [{couch_mrview_util,get_view,4,
[{file,
"c:/cygwin/relax/APACHE~2.1/src/COUCH_~3/src/couch_mrview_util.erl"},
{line,49}]},
{couch_mrview,query_view,6,
[{file,
"c:/cygwin/relax/APACHE~2.1/src/COUCH_~3/src/couch_mrview.erl"},
{line,75}]},
{couch_httpd,etag_maybe,2,
[{file,
"c:/cygwin/relax/APACHE~2.1/src/couchdb/couch_httpd.erl"},
{line,610}]},
{couch_mrview_http,design_doc_view,5,
[{file,
"c:/cygwin/relax/APACHE~2.1/src/COUCH_~3/src/couch_mrview_http.erl"},
{line,188}]},
{couch_httpd_db,do_db_req,2,
[{file,
"c:/cygwin/relax/APACHE~2.1/src/couchdb/couch_httpd_db.erl"},
{line,234}]},
{couch_httpd,handle_request_int,5,
[{file,
"c:/cygwin/relax/APACHE~2.1/src/couchdb/couch_httpd.erl"},
{line,318}]},
{mochiweb_http,headers,5,
[{file,
"c:/cygwin/relax/APACHE~2.1/src/mochiweb/mochiweb_http.erl"},
{line,94}]},
{proc_lib,init_p_do_apply,3,
[{file,"proc_lib.erl"},{line,239}]}]
[Mon, 10 Nov 2014 19:22:19 GMT] [info] [<0.117.0>] 192.168.247.158 - - GET /tcs/_design/company/_view/Company_Id?limit=101 500
[Mon, 10 Nov 2014 19:22:19 GMT] [error] [<0.117.0>] httpd 500 error response:
{"error":"os_process_error","reason":"{exit_status,1}"}
I figured this out but I am not sure why it happened. There was a HUGE document 57mb which had been uploaded to the DB but it was not visible in Futon or anywhere else.
I only found it after digging into the debug log further. I could not access the document via a CURL Get. I ended up having to use CURL -X DELETE with the specific revision then a purge to get rid of the document. Soon as the document was deleted everything worked as expected.
When I try to start Apache tomcat 7.0.26 server is not starting. This is first time.
console message as follows :
Mar 7, 2012 12:06:18 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 470 ms
It has been started and the starting process took 470 ms.
That's what the message says.
I have the suspicion that you didn't even bother to check the url of web management to see if Tomcat is up or not.