How To Solve Autovue startup error: Can’t get JVM library | AutoVue Desktop Deployment

May 212013
 

After installing Desktop Deployment via installer.\

We then copied the oracle\autovue desktop deployment file system to ourapp\autoviewer\autovue desktop deployment and renamed the original directory.

autovue.properties was edited and replaced all c:\oracle(OLD path) with c:\ourapp\autoviewer.

JAVA_HOME was set with c:\ourapp\autoviewer\autovue desktop deployment\jre.

When we tried to run autovue.exe we received the following message…

Autovue Initialization Error

Autovue startup error: Can’t get JVM library
Exiting…
Continue reading “How To Solve Autovue startup error: Can’t get JVM library | AutoVue Desktop Deployment” »

Did Not Find The Exact Solution..? Put A Comment With Your Question TechPaste Support Will Get Back To You!!

Solving libvueserver.so.20.2.1.8280: libbz2.so.1: cannot open shared object file Error | Autovue

May 202013
 

While trying to install AutoVue 20.2.1 on Linux(RedHat 5.5) 64 bit environment we hit following error while starting the Autovue service.

<log4j:event logger=”com.cimmetry.jvueserver.management” timestamp=”1368094054659″ level=”FATAL” thread=”main”>
<log4j:message><![CDATA[Failed to load VueServer library. Aborting.]]></log4j:message>
<log4j:throwable><![CDATA[java.lang.UnsatisfiedLinkError: /opt/autovue/bin/libvueserver.so.20.2.1.8280: libbz2.so.1: cannot open shared object file: No such file or directory
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(Unknown Source)
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.loadLibrary0(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at com.cimmetry.jvueserver.JVueServer.initLibrary(Unknown Source)
at com.cimmetry.jvueserver.JVueServer.start(Unknown Source)
at com.cimmetry.jvueserver.JVueServer.main(Unknown Source)
]]></log4j:throwable>
</log4j:event>
Continue reading “Solving libvueserver.so.20.2.1.8280: libbz2.so.1: cannot open shared object file Error | Autovue” »

Did Not Find The Exact Solution..? Put A Comment With Your Question TechPaste Support Will Get Back To You!!

Insides Of IBM J9 JVM for Java 6 Architecture and Features

May 192013
 

The Java J9 JVM for Java 6 shipped with WAS 7, with other IBM software, and for use on IBM hardware is based on the third generation of the J9 JVM that was introduced with the Java 5 release. The core code is still derived from a licensed Sun JVM implementation that IBM enhances and builds upon for its own products.

For the Java 5 release, the product was rewritten to incorporate features from a traditional optimizing compiler, to support pluggable features and libraries suited to different types of platforms, to have enhanced type safe and generational garbage collection features, and to support class sharing of read-only immutable optimized class information. The Java 6 release essentially tuned the environment more in terms of improved optimization, further garbage collection enhancements, and improved class sharing.
Continue reading “Insides Of IBM J9 JVM for Java 6 Architecture and Features” »

Did Not Find The Exact Solution..? Put A Comment With Your Question TechPaste Support Will Get Back To You!!

Diagnosing java.lang.ClassCastException: weblogic.jms.frontend.FEConnectionFactoryImpl in logs | Weblogic

May 192013
 

If you find below ClassCast error in logs and the server goes down or becomes unresponsive to some modules or on whole you can try below steps to stop the issue from reoccuring.

####<JUn 21, 2012 10:52:51 AM EDT> <Error> <Kernel>
<shheb.local.new.com> <wls-m01> <ACTIVE
ExecuteThread: ’1′ for queue: ‘weblogic.kernel.Default (self-tuning)’>
<<WLS Kernel>> <1367765571206> <BEA-000802> <ExecuteRequest failed
java.lang.ClassCastException: weblogic.jms.frontend.FEConnectionFactoryImpl.
java.lang.ClassCastException: weblogic.jms.frontend.FEConnectionFactoryImpl
at
weblogic.rmi.cluster.BasicReplicaHandler.refreshReplicaList(BasicReplicaHandler.java:519)
at
weblogic.rmi.cluster.BasicReplicaHandler.failOver(BasicReplicaHandler.java:211)
at
weblogic.rmi.cluster.ClusterableRemoteRef.handleException(ClusterableRemoteRef.java:304)
at
weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:275)
at
weblogic.jms.frontend.FEConnectionFactoryImpl_1211_WLStub.connectionCreateRequest(Unknown
Source)
at
weblogic.jms.client.JMSConnectionFactory.setupJMSConnection(JMSConnectionFactory.java:224)
at
weblogic.jms.client.JMSConnection.preCreateReplacement(JMSConnection.java:1736)
at weblogic.jms.client.JMSConnection.reconnect(JMSConnection.java:2515)
at
weblogic.jms.client.WLConnectionImpl.processReconnectTimer(WLConnectionImpl.java:253)
at weblogic.jms.client.JMSConnection.timerExpired(JMSConnection.java:1347)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:293)
at
weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Continue reading “Diagnosing java.lang.ClassCastException: weblogic.jms.frontend.FEConnectionFactoryImpl in logs | Weblogic” »

Did Not Find The Exact Solution..? Put A Comment With Your Question TechPaste Support Will Get Back To You!!

Weblogic Windows Service Fails To Start with SecurityInitializationException incorrect password | Weblogic

May 182013
 

If your windows NT service fails to start with errors like below then please follow the below steps to fix the issue.

ERROR:

<May 8, 2013 8:50:30 AM PDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Server installed as Windows NT service with incorrect password for user admin; The password may have been changed since the server was installed as a Windows NT Service. Contact the Windows NT system administrator.

weblogic.security.SecurityInitializationException: Server installed as Windows NT service with incorrect password for user admin; The password may have been changed since the server was installed as a Windows NT Service. Contact the Windows NT system administrator.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:944)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
at weblogic.security.SecurityService.start(SecurityService.java:141)
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)
Continue reading “Weblogic Windows Service Fails To Start with SecurityInitializationException incorrect password | Weblogic” »

Did Not Find The Exact Solution..? Put A Comment With Your Question TechPaste Support Will Get Back To You!!

Diagnosing Resource Hang Detected For Pool Message in Logs | Weblogic

May 182013
 

While doing a monthly maintenance of weblogic production servers, we went through log files for checking any unusual messages and found below connection pool closed info in logs.

####<Apr 29, 2013 2:00:45 PM EDT> <Info> <JDBC> <seed_datatech> <seed2> <ACTIVE ExecuteThread: ’31′ for queue: ‘weblogic.kernel.Default (self-tuning)’> <<anonymous>> <1367258445862> <BEA-001128>
<Connection for pool “seed_datasource” closed.>
####<Apr 29, 2013 2:00:45 PM EDT> <Info> <Common> <seed_datatech> <seed2> <ACTIVE ExecuteThread: ’29′ for queue: ‘weblogic.kernel.Default (self-tuning)’> <<anonymous>> <1367258445863> <BEA-000634>
<Resource hang detected for pool “seed_datasource”, group “DEFAULT_GROUP_ID”. Waited 20,008 milliseconds where a typical test has been taking 58>
####<Apr 29, 2013 2:00:45 PM EDT> <Info> <JDBC> <seed_datatech> <seed2> <ACTIVE ExecuteThread: ’14′ for queue: ‘weblogic.kernel.Default (self-tuning)’> <<anonymous>> <1367258445863> <BEA-001128>
<Connection for pool “seed_datasource” closed.>
####<Apr 29, 2013 2:00:45 PM EDT> <Info> <JDBC> <seed_datatech> <seed2> <ACTIVE ExecuteThread: ’28′ for queue: ‘weblogic.kernel.Default (self-tuning)’> <<anonymous>> <1367258445864> <BEA-001128>
<Connection for pool “seed_datasource” closed.>
Continue reading “Diagnosing Resource Hang Detected For Pool Message in Logs | Weblogic” »

Did Not Find The Exact Solution..? Put A Comment With Your Question TechPaste Support Will Get Back To You!!

Manage Server Getting Stuck With MaxMessageSizeExceededException Error | Weblogic

May 172013
 

At a customer place we saw the managed server getting stuck and hung with below MaxMessageSizeExceededException errors in logs. So we followed below steps to narrow down the errors and fix it.

Once this error shows up the managed server which is sending this info to admin server usually gets out of sync and the admin server fails to determine the status of the managed server and eventually it looses the connectivity to admin server.

####<May 16, 2013 12:13:11 PM CEST> <Error> <Socket> <kihjja> <prod01_AdminServer> <ExecuteThread: ’2′ for queue:
‘weblogic.socket.Muxer’> <<WLS Kernel>> <fsa322as2a1ad39a:e8f504c:13e8cebfw21:-8000-000000000000038d>
<1368699191244> <BEA-000403> <IOException occurred on socket:Sockethttp://addr=kihjja-ip/11.32.89.30,port=8009,localport=9379
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: ’27002222′ bytes exceeds the configured maximum of: ’25000000′ bytes for protocol: ‘t3′.
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: ’27002222′ bytes exceeds the configured maximum of: ’25000000′ bytes for protocol: ‘t3′
at weblogic.socket.BaseAbstractMuxableSocket.incrementBufferOffset(BaseAbstractMuxableSocket.java:230)
at weblogic.rjvm.t3.MuxableSocketT3.incrementBufferOffset(MuxableSocketT3.java:351)
at weblogic.socket.SocketMuxer.readFromSocket(SocketMuxer.java:991)
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:922)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:899)
at weblogic.socket.EPollSocketMuxer.dataReceived(EPollSocketMuxer.java:215)

 
Continue reading “Manage Server Getting Stuck With MaxMessageSizeExceededException Error | Weblogic” »

Did Not Find The Exact Solution..? Put A Comment With Your Question TechPaste Support Will Get Back To You!!

Page 1 of 65 1 2 3 … 64 65


Stats