Escolar Documentos
Profissional Documentos
Cultura Documentos
Problem vs Issue
Problem that happen accidentally due to any reasons, such as network not in sync, Database server might
overloaded or anything. An issue can be transformed into problem when it is not identified in time and not
resolved. A problem that need to fix immediately. The impact of the problem can be Life threatening. To
make more simple, fever is an issue it can be resolved by pills, Heart Attack is a major Life threatening it
is not solved immediately there could be huge loss.
To explore on middleware if you encounter more troubles more you learn. At the same time remember
that your Client always wishes that business will run uninterruptedly. You give the 99.9999%
Bottom line, When the problem is not in Middleware environment then don't play the name blame game.
Try to give your best for support the solution providing team.
Love issues, which make you to learn more about the subject. Enjoy with
issues, troubles, you will be enlighted with your problem skills so..........
dear smart WLA rock with them!!!
1. Port Conflict Issue:
While configuring a new WebLogic instance and starting it, that might be get an issue like : "Port already
in use". There could be many reasons for this one.
1. on the same machine multiple standalone instances might be running one of the instance already used
that port which you have given for new configuration.
2. apache might be running with the same port.
lsof -i tcp:<Port_number>
This Linux command lsof works for that user to where this command is executed by the user.
3. Best way is perl script using a method it will check only standard ports which are used by the system.
getservbyport(int port_number, const char *protocol_name)
Sample perl script goes as follows:
#!/usr/bin/perl
($name, $aliases, $port_number, $protocol_name) = getservbyport(7001,
"tcp");
print "Name = $name\n";
print "Aliases = $aliases\n";
print "Port Number = $port_number\n";
print "Protocol Name = $protocol_name\n";
3. Multicast Failure
while running the managed server on a remote server getting the following exception:
<Jul 31, 2008 4:16:16 AM EDT> <Error> <Cluster> <BEA-000109> <An error
occurred while sending multicast message: java.net.SocketException:
Socket is closed
java.net.SocketException: Socket is closed
at java.net.DatagramSocket.send(DatagramSocket.java:577)
Sol:
1. check for the ping happening between the cluster involved machines.
2. Verify the Multicast IP with the MulticastTest with multiple ips and with ports then use which is
app1
-a 237.0.0.5 -p 9999
WebMachine 2:
$ java utils.MulticastTest -n
app2
-a 237.0.0.5 -p 9999
The messages must exchange between them... otherwise check with Network
team.
3. Multcast heart beat can be visible by the following command line:
java weblogic.cluster.MulticastMonitor <multicastIP> <port> mydomain mycluster
6. Deployment Error
Module Name: apollo, Error: [HTTP:101179][HTTP] Error occurred while parsing descriptor in Web
application "/domainpath/application.war" [Path="/source_code_path", URI="applicaiton.war"
org.xml.sax.SAXParseException: Element type "local-path" must be followed by either attribute
specifications, ">" or "/>".
Sol:
Check the Deployment Descriptors (here weblogic.xml) edit as per the given Line.
7. JNDI Issue
While deploying application which is having multiple JMS Queues getting as:
data couldn't be saved. The exception is : Error while doSenderQueueLookUp for :QUEUEJNDIUnable
to resolve 'QUEUEJNDI' Resolved
Sol:
Please verify the Persistance Store is connected to Connection Pool.
BEA-000117
Received a stale replication request
Whenever you encounter this error code in your logs you need to check following:
1. Network connectivity between the cluster member hosting machines.
2. Check all the member servers are alive in that cluster.
BEA-090870
Security issue while starting Admin Server
Exception:
####<Oct 28, 2010 3:38:41 AM PDT> <Error> <Security> <Unknown> <AdminServer> <[STANDBY]
ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>>
<1288262321492> <BEA-090870> <The realm "myrealm" failed to be loaded:
weblogic.security.service.SecurityServiceException: java.lang.ExceptionInInitializerError.
weblogic.security.service.SecurityServiceException: java.lang.ExceptionInInitializerError
at
weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:342
)
The workaround is suggested as 'Please login to the Database and then run the below SQL file to execute
different queries mentioned in this file:
Suppose Database User Login is weblogic then login to Database with this credential and run the script
under
$BEA_HOME\wlserver_10.3\server\lib\rdbms_security_store_oracle.sql
Yesss!!, it worked...
BEA-000388 JVM called WLS shutdown hook. The server will force shutdown
now
Issue:
The WebLogic server got shutdown with the following error stack found in the server standard out log
files:
####<Sep 7, 2012 3:14:20 PM IST> <Notice> <WebLogicServer> <Ncorp-PLM-08> <Ncorp-PLM-08AgileServer> <Thread-1> <<WLS Kernel>> <> <> <1347011060768> <BEA-000388> <JVM called
WLS shutdown hook. The server will force shutdown now>
####<Sep 7, 2012 3:14:20 PM IST> <Alert> <WebLogicServer> <Ncorp-PLM-08> <Ncorp-PLM-08AgileServer> <Thread-1> <<WLS Kernel>> <> <> <1347011060768> <BEA-000396> <Server
shutdown has been requested by <WLS Kernel>>
####<Sep 7, 2012 3:14:20 PM IST> <Notice> <WebLogicServer> <Ncorp-PLM-08> <Ncorp-PLM-08AgileServer> <Thread-1> <<WLS Kernel>> <> <> <1347011060771> <BEA-000365> <Server state
changed to FORCE_SUSPENDING>
The following could be possible Cause and we have the workaround solution as:
I have the following suggestion for you for the below error:
<Sep 7, 2012 3:14:20 PM IST> <Notice> <WebLogicServer> <Ncorp-PLM-08> <Ncorp-PLM-08AgileServer> <Thread-1> <<WLS Kernel>> <> <> <1347011060768> <BEA-000388> <JVM called
WLS shutdown hook. The server will force shutdown now>
1) It seems like some component is sending the wrong signal to the JVM and this issue is occurring. JVM
monitors and catches OS signals, like: CTRL +C event, Log off event, shutdown event.When JVM
catches one of the stated above signals, it shutdowns all java processes.
BEA-160192
<BEA-160192> <While upgrading weblogic.xml, encountered "max-in-memory-sessions" param
"session-param". This param is unknown and will be removed>
This eror you can see in your weblogic logs, Because the deployment descriptor weblogic.xml is not
updated with the latest DTD defined for weblogic 11g.
To resolve this do setWLSEnv.sh and run the following and it will convert it to compatable to WebLogic
11g. But as this is template the basic xml will need to be amended with the 11g DTD and then build script
creating the correct file out of it java weblogic.DDConverter -d . <<ear/warfile or webapp/ear directory>>