Tuesday Jan 17, 2012

Exalogic Disaster Recovery White Paper

Lately there have been a lot of questions and requests around Disaster Recovery for Exalogic.
So it's good to keep in mind this link to the Disaster Recovery White Paper for Oracle Exalogic Elastic Cloud, which was published a couple of months ago.

Thursday Sep 01, 2011

The MANIFEST.MF filename... Oh My!

In the last month I worked a Service Request along with my colleague Ernani Mattos, where on WebLogic 10.3.4, when attempting to deploy Coherance*Web, the following error occurs on RedHat, but not on Windows or Debian:
weblogic.application.ModuleException: Missing Coherence jar or WebLogic Coherence Integration jar

The customer was following the Caching Sessions with Coherence and WebLogic Server documentation.

Taking a look at the ModuleException, the coherence.jar is part of the counter.war application, and the Weblogic.coherence.integration.jar is declared with the active-cache-1.0.jar lib which is referenced by the MANIFEST.MF of the counter application.

The entire issue was that MANIFEST.MF on the counter.war was named as "manifest.mf"; Therefore RedHat Linux could not recognize it simply due to the naming issues. So make sure that manifest file name is "MANIFEST.MF" and declares to active-cache-1.0.jar which should be deployed as a lib on the servers.

This was solved by executing the following steps:
1. Explode the counter.war application
2. Goto counter/META-INF/ directory
3. Rename the manifest.mf to MANIFEST.MF
4. Deploy as open directory or compact back to war file and deploy

Monday Aug 08, 2011

Error "java.net.BindException: Address already in use: JVM_Bind" when running Node Manager in Windows

After a brand new install of WebLogic Server, when accessing node manager the following error is thrown:
GRAVE: Fatal error in node manager server java.net.BindException: Address already in use: JVM_Bind at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:365) at java.net.ServerSocket.bind(ServerSocket.java:319) at javax.net.ssl.impl.SSLServerSocketImpl.bind(Unknown Source) at java.net.ServerSocket.(ServerSocket.java:185) at java.net.ServerSocket.(ServerSocket.java:141) at javax.net.ssl.SSLServerSocket.(SSLServerSocket.java:84) at javax.net.ssl.impl.SSLServerSocketImpl.(Unknown Source) at javax.net.ssl.impl.SSLServerSocketFactoryImpl.createServerSocket(Unknown Source) at weblogic.nodemanager.server.SSLListener.init(SSLListener.java:76) at weblogic.nodemanager.server.NMServer.start(NMServer.java:206) at weblogic.nodemanager.server.NMServer.main(NMServer.java:392) at weblogic.NodeManager.main(NodeManager.java:31)



When WebLogic is installed in Windows, the NodeManager is set as a Windows service which is automatically started up and runs on port 5556 (default).



The node manager is already started. It can be shut down in the windows services, and to avoid that it is started up automatically along with Windows, the startup type can be changed.

Thursday May 19, 2011

Beware the JVM arguments!

In the last weeks I have had a bunch of Service Requests where a JVM argument ("-D" or "-X") is set as startup setting of a server on the WebLogic Server Administration Console, then the server is started up through the console (running a shell script) and the specified settings do not take effect.


This is an expected behavior because, according to the WebLogic lifecycle, the arguments set on the administration console (web) work only when the managed server is started up through the console. Arguments set on the shell script work for any way of start up.

So, keep this in mind:
- Set the JVM arguments on the startup script to make sure they will take effect
- Or if you set those parameters through the WebLogic Server Administration Console, then you should start the managed server using the console too instead of the startManagedWebLogic.sh, startManagedWebLogic.cmd or any other script

Monday Oct 25, 2010

Working with Dates in the Model Layer

[Read More]
About


Principal Technical Support Engineer in the Engineered (Systems) Enterprise Support Team - EEST.
Former member of the Coherence and Java Technologies Support Teams.

Search

Archives
« August 2015
SunMonTueWedThuFriSat
      
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
     
Today