Weblogic Shutdown !
Hi :
I am using Weblogic 5.1 , I frequently get into the below problem and I dont
know how to fix this Any help will be appreciated.
the Actual Error Message that I get, when I give the shutdown command :
Mon Feb 26 10:30:50 PST 2001:<I> <HTTP> Destroying servlets in default
servlet c
ontext.
java.lang.reflect.InvocationTargetException: java.lang.NullPointerException:
at
javax.servlet.GenericServlet.getServletContext(GenericServlet.java:20
5)
at javax.servlet.GenericServlet.log(GenericServlet.java:300)
at javax.servlet.GenericServlet.destroy(GenericServlet.java:122)
at
weblogic.servlet.internal.ServletStubImpl.destroyServlet(ServletStubI
mpl.java:288)
at
weblogic.servlet.internal.ServletContextImpl.destroyServlets(ServletC
ontextImpl.java, Compiled Code)
at weblogic.t3.srvr.HttpServer.destroyServlets(HttpServer.java:766)
at weblogic.t3.srvr.HttpServer.shutdown(HttpServer.java:749)
at weblogic.t3.srvr.T3Srvr.die(T3Srvr.java:2011)
at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java, Compiled Code)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:107)
at weblogic.Server.main(Server.java:65)
at weblogic.Server.main(Server.java:55)
thanks
Balaji.
Try posting in one of the WebLogic server-related newsgroups. Make sure you
install the latest service pack and see if this solves the problem...
Balaji Venkataraman wrote:
Hi :
I am using Weblogic 5.1 , I frequently get into the below problem and I dont
know how to fix this Any help will be appreciated.
the Actual Error Message that I get, when I give the shutdown command :
Mon Feb 26 10:30:50 PST 2001:<I> <HTTP> Destroying servlets in default
servlet c
ontext.
java.lang.reflect.InvocationTargetException: java.lang.NullPointerException:
at
javax.servlet.GenericServlet.getServletContext(GenericServlet.java:20
5)
at javax.servlet.GenericServlet.log(GenericServlet.java:300)
at javax.servlet.GenericServlet.destroy(GenericServlet.java:122)
at
weblogic.servlet.internal.ServletStubImpl.destroyServlet(ServletStubI
mpl.java:288)
at
weblogic.servlet.internal.ServletContextImpl.destroyServlets(ServletC
ontextImpl.java, Compiled Code)
at weblogic.t3.srvr.HttpServer.destroyServlets(HttpServer.java:766)
at weblogic.t3.srvr.HttpServer.shutdown(HttpServer.java:749)
at weblogic.t3.srvr.T3Srvr.die(T3Srvr.java:2011)
at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java, Compiled Code)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:107)
at weblogic.Server.main(Server.java:65)
at weblogic.Server.main(Server.java:55)
thanks
Balaji.
Similar Messages
-
Hi,
I have WAR containing spring (2.5) jobs scheduled using quartz (1.5). This WAR is deployed on weblogic 8.1.
Within the web.xml, I have a listener which reads the Spring configuration file and starts/schedules the spring jobs.
The Spring quartz scheduler bean has a property called "waitForJobsToCompleteOnShutdown" which, if set to TRUE, will allow the currently running jobs to complete before spring context is closed.
The listener has a method "contextDestroyed" which is called when the weblogic graceful shut down is issued. Within this method, I am closing the spring context.
What I am seeing is that if the currently running job goes beyond weblogic shutdown timeout, then they are killed abruptly. Is there any way to allow the jobs to complete even though they go beyond timeout period?
Regards,
JacobHi,
Could you check <session-timeout-seconds> element in deployment descriptors ?
Regards
Anilkumar kari -
Problems during Weblogic Shutdown
Hi :
I am using Weblogic 5.1 SP8 , I frequently get into the below problem and I
dont know how to fix this Any help will be appreciated.
the Actual Error Message that I get, when I give the shutdown command :
Mon Feb 26 10:30:50 PST 2001:<I> <HTTP> Destroying servlets in default
servlet c
ontext.
java.lang.reflect.InvocationTargetException: java.lang.NullPointerException:
at
javax.servlet.GenericServlet.getServletContext(GenericServlet.java:20
5)
at javax.servlet.GenericServlet.log(GenericServlet.java:300)
at javax.servlet.GenericServlet.destroy(GenericServlet.java:122)
at
weblogic.servlet.internal.ServletStubImpl.destroyServlet(ServletStubI
mpl.java:288)
at
weblogic.servlet.internal.ServletContextImpl.destroyServlets(ServletC
ontextImpl.java, Compiled Code)
at weblogic.t3.srvr.HttpServer.destroyServlets(HttpServer.java:766)
at weblogic.t3.srvr.HttpServer.shutdown(HttpServer.java:749)
at weblogic.t3.srvr.T3Srvr.die(T3Srvr.java:2011)
at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java, Compiled Code)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:107)
at weblogic.Server.main(Server.java:65)
at weblogic.Server.main(Server.java:55)
thanks
Balaji.Please verify your path for Context Root:
It shows as null/WEB-INF/classes/log4j.properties
Expectation is that it should show {myContextRoot}/WEB-INF/classes/log4j.properties
Ex:
/rohitApp/WEB-INF/classes/log4j.properties
In case ur unable to build ur ejb via weblogic builder then pls verify the CLASSPATH for log4j jars under menu Tools -> Options ->CLASSPATH.
It should have the entries similar to below :
.../WEB-INF/lib/commons-logging.jar; .../WEB-INF/lib/log4j-1.2.8.jar;
Regards
Rohit -
Needed Message ID for Weblogic SHUTDOWN Status
Hi
We have our OBIEE11g Platform running in Windows platform.
We have the Weblogic Admin & Managed Services as windows Services
My Agenda is to monitor the the Weblogic Admin/managed services startup/stop based on messageID.
Successfully enabled the WL Diagnostics Module(watch/notification) to trigger an email for the Message ID <BEA-000360> "<Server started in RUNNING mode>" ,
but i could not able to find the relevant Message_ID for the SHUTDOWN status or Stopping mode, please let me know what would be the appropriate similar to the above ?
Will this "<BEA-000396> <Server shutdown has been requested by weblogic> can act as the correct messageID for shutdown?
ThanksHi
I reckon a good monitoring would be BEA-000365, then you would be aware of any server's status changes.
Cheers,
Vlad
Give points - it is good etiquette to reward an answerer points (5 - helpful; 10 - correct) for their post if they answer your question. -
Weblogic shutdown with IOException? But...
I have problem with a new fresh installed Weblogic server 7 server, when i completed
installation over a Solaris box, i start the domain, open the web console and
do a server shutdown, it generates me a IOException error. Whats wrong?Wed Apr 11 20:54:35 EDT 2001:<E> <HTTP> Exception flushing HTTP log file
java.io.IOException: Bad file number
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:212)
at weblogic.utils.io.DoubleBufferedOutputStream.flushBuffer(DoubleBufferedOutputStream.java:60)
at weblogic.utils.io.DoubleBufferedOutputStream.flush(DoubleBufferedOutputStream.java:182)
at weblogic.t3.srvr.httplog.LogManagerHttp$FlushLogStreamTrigger.trigger(LogManagerHttp.java:587)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:197)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:191)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:60)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)The exception itself essentially means a file is in use (being written to or some such) and something
attempts
to call destroy() or some such on it without closing it.
Or...you could also just have an open file descriptor that you're attempting to garbage collect without first
closing it.
m. -
Weblogic shutdown and MDB method calls
Hi,
We have message driven beans deployed on Weblogic 7.0.2 server. We have a situation where there are messages pending on the JMS Queue(a persistent store is configured.) and the MDB instances will be processing the meesages from the queue. We need to restart the weblogic server at this point.
My doubt is what happens to the messgaes which were being processed in the onMessage method of the MDB. If the server is shutdown, will these messages that were being processed also be backed up to the persistent store or will these be lost?
There may be additional messages coming in while the server is being shutdown.
What is the best way to shutdown the weblogic server without losing any of the messages?
Any pointers to additional info will be highly appreciated.
Thanks in advance,
Amit<Amit Kulkarni> wrote in message news:[email protected]..
We have message driven beans deployed on Weblogic 7.0.2 server. We have a situation where there are messages pending on the JMSQueue(a persistent store is configured.) and the MDB instances will be processing the meesages from the queue. We need to restart
the weblogic server at this point.
My doubt is what happens to the messgaes which were being processed in the onMessage method of the MDB. If the server is shutdown,will these messages that were being processed also be backed up to the persistent store or will these be lost?
There may be additional messages coming in while the server is being shutdown.
What is the best way to shutdown the weblogic server without losing any of the messages?
Any pointers to additional info will be highly appreciated.Have a standby instance running and switch network to that instance before taking first one down or set up a full-blown cluster.
Regards,
Slava Imeshev -
Weblogic shutdown after a continuous use of approximately 5 hours
Hi,
i am running an application on weblogic server7.0
The problem is, server is shutting down after a continuous use of approxiamtely 5 hours.
please suggest me the possible reasonscheck the logs. maybe your servers are running out of memory.
-
About Weblogic shutdown class.
Hi All,
i would like log an event using my own java class and this java class should fire whenever the weblogic server stops. Is there any possiblity?
Do i need to configure in config.xml?Sounds like you should ask that in a weblogic forum.
-
Hi,
I am looking for weblogic shutdown script?
Can anybody point me to the script if one is available.
Thanks in advance
Subba Reddyjust use the admnin utility from a shell and bat/cmd file. here's the
command:
java weblogic.Admin <url> SHUTDOWN system <password>
you may get the usage by just typing:
java weblogic.Admin
jason
Original Message <<<<<<<<<<<<<<<<<<On 3/10/00, 9:42:47 PM, subba reddy <[email protected]> wrote
regarding shutdown script for Weblogic?:
Hi,
I am looking for weblogic shutdown script?
Can anybody point me to the script if one is available.
Thanks in advance
Subba Reddy -
Unable to start Admin server by using weblogic.admin utility
Hi,
I stoped the admin server by using weblogic.admin utility command as bellow.
java weblogic.Admin -url http://server1:8008 -username adminuser -password weblogic SHUTDOWN myserver
It stopped successfully. But while starting as below i am getting error. Kindly help me out.
java weblogic.Admin -url http://172.27.72.70:8008 -username adminuser -password weblogic START myserver
<Warning> <Net> <BEA-000905> <Could not open connection with host: server1 and port: 8008.>
Failed to connect to http://172.27.72.70:8008: Destination unreachable; nested exception is:
java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: 'star', port: '8008'; No available router to destination
Any suggestion is appreciated.
Thanks,Hi,
Thanks for your reply.
Yes, Node Manager has configured on Managed Server's host machine.
So can't we start admin server by using weblogic.admin utility if admin server is stopped?
Thanks, -
Flushing out remaining contents of a queue after weblogic shuts down
Anyway to tab into Weblogic shutdown event, so I can run some clean up code to
disconnect a persistent connection.. etc.
Gary
"Irwin Yoon" <[email protected]> wrote:
I have a queue which runs as a daemon thread. Every so often the queue
wakes up to empty the queue, then goes back to sleep when it's done,
then
wakes up again, etc. The queue is represented as an array. The queue
is
part of a single instance of a class, similar to a startup class.
This is my question: When the weblogic server is shut down, what is
the
best way for the queue to be able to flush out all the remaining items
in
its queue?
Is a weblogic shutdown class the way to go? If so, how could this be
implemented? Any other suggestions?
Thanks,
Irwin -
Built-in system events for detecting shutdown?
One problem with the WebLogic shutdown process is that there doesn't seem to
be a way to handle shutdown gracefully. Connected clients can't be informed
of an
impending shutdown.
Web clients get notified, I assume, when the server
becomes locked, but that's not really good enough for a distributed
application. For that, you have to be able to "broadcast" a message to
connected clients.
I would expect there to be built-in events that could be listened for. For
example:
weblogic.admin.systemShutdown(parameter gracePeriodMillis)
weblogic.admin.systemShutdownCancelled()
Please tell me I'm missing something. :-)
Tim TaylorThere is a set of Weblogic events that are thrown on shutdown. These should
be documented in the documentation.
As for graceful shutdown (what is called quiescing of servers), we do not
currently handle that as well as we would like for things like HTTP
sessions. We are adding significant functionality in future releases to
make that better. But, with things like clustering, removal of
servers/shutdown should be noncatastrophic because of failover and
redundancy of user data.
Thanks,
Michael
Michael Girdley
Product Manager, WebLogic Server & Express
BEA Systems Inc
Tim Taylor <[email protected]> wrote in message
news:8h3c33$jki$[email protected]..
One problem with the WebLogic shutdown process is that there doesn't seemto
be a way to handle shutdown gracefully. Connected clients can't beinformed
of an
impending shutdown.
Web clients get notified, I assume, when the server
becomes locked, but that's not really good enough for a distributed
application. For that, you have to be able to "broadcast" a message to
connected clients.
I would expect there to be built-in events that could be listened for.For
example:
weblogic.admin.systemShutdown(parameter gracePeriodMillis)
weblogic.admin.systemShutdownCancelled()
Please tell me I'm missing something. :-)
Tim Taylor -
HotSpot Virtual Machine Error, Internal Error ; ID : 4A4156410E43505001E7
Hi,
We're running under Windows 2003 Server.
Application Server :
Weblogic Server 7 SP4.
Used JVM is :
Java VM: Java HotSpot(TM) Server VM (1.4.2_07-b05 mixed mode)
Options givent to the JVM :
-server -ms128m -mx128m -Dos.name=\"windows 2000\"
We're constantly getting this VM internal error at Weblogic shutdown :
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
# Java VM: Java HotSpot(TM) Server VM (1.4.2_07-b05 mixed mode)
# Error ID: 4A4156410E43505001E7
# Problematic Thread: prio=5 tid=0x008729c0 nid=0x9f0 runnable
If what is written here (http://forum.java.sun.com/thread.jspa?threadID=607814&start=0&tstart=135) is true, the error code can be translated to :
4A4156410E43505001E7 --> JAVA_CPP line 147
so the error seems to be caused by java_cpp, line 147.
Here is the heap at VM Abort:
def new generation total 235968K, used 59398K [0x10010000,0x20010000, 0x20010000)
eden space 209792K, 26% used [0x10010000, 0x13585a18, 0x1ccf0000)
from space 26176K, 17% used [0x1ccf0000, 0x1d17c030, 0x1e680000)
to space 26176K, 0% used
Wed Feb 01 09:20:37 2006
ServiceStart done waiting for multiple events. Wait=0 [0x1e680000, 0x1e680000, 0x20010000)
Wed Feb 01 09:20:37 2006 ServiceStart Informing SCM about SERVICE_STOP
I didn't find any relevant information either on google.com or sun.com.
Any idea ?The JNI_CreateJavaVM(..) interface allows an exit_hook function to
be specified. The jvm expected that this function call system exit and
not return. If it did, then the error you saw would occur. The bugfix
added a call to system exit if the exit_hook happens to return. If this
is your problem, finding the exit_hook function and ensuring that it
always call system exit should fix the problem.
The following doc explains the invocation API:
http://java.sun.com/j2se/1.5.0/docs/guide/jni/spec/invocation.html
There was one other issue that this bugfix addressed. To shutdown
the jvm, a shutdown request is sent to the vm thread which is not
supposed to return. Perhaps under some very strange conditions
it might, so another call so system exit was added if the vm shutdown
request returned. -
Client Id in use - WL6.1 sp3 server to server JMS messaging
Any feedback would be greatly appreciated. THANKS!
-Alan May
Scenario:
Two weblogic 6.1 sp3 instances running on two separate Solaris 8 boxes.
Server a - a message producer(client) for a number of topics and queues on b
Server b - hosts JMS services including all the topics and queues, has both
message producers and mdb consumers for a number of topics and queues
What I've set up: a durable connection factory for topics for server a,
topics for server b, queues for server a, and queues for server b (all
targeted to server b)
I have a singleton on each server that has methods to retrieve the queue
connection or topic connection appropriate for that server(a single
connection is
shared for all topic producers and a separate connection is share for all
queue producers for each server)
I have each producer open and close a new session every time. However, the
topic and queue connections are shared for all producers for that JVM. This
seemed to be the approach recommended by the JMS spec, but do you feel this
is the appropriate granularity given the above scenario? I am not currently
closing my jms connection as part of a weblogic shutdown class. Is that
essential in that case? If the server crashes - are there any
recommendations on how to handle(if closing the connection is the issue)?
I've confirmed that my JMS clients running with server b are not using the
connection factories setup for a's use.
Issue:
Everything works on server b as expected.
Server a's connections seemed to be fouled. I was getting that the clientid
was in use(stack trace included below) while trying to fetch the connection.
I stopped server a, removed the fouled connection factories on server
b(dedicated for server a's use), and created new connection factories for
a's use. I stopped server b and deleted everything from the two JMSState
and JMSStore tables, restarted a then b, and tried the test again. This
time the singleton code could fetch the connection without receiving a
JMSException, but I was getting an exception when I tried to open a session
from the connection.
If worst comes to worse, I can stick a stateless session bean on b, to act
as a delegate producer on behalf of server a, but I'd like to avoid it if
possible.
Any recommendations? Please let me know if it would be helpful for me to
clarify any points.
Server a's original error:
weblogic.jms.common.InvalidClientIDException: Client id, Parser.topicPrime,
is in use
Start server side stack trace:
weblogic.jms.common.InvalidClientIDException: Client id, Parser.topicPrime,
is in use
at
weblogic.jms.frontend.FEConnection.setClientId(FEConnection.java:918)
at weblogic.jms.frontend.FEConnection.<init>(FEConnection.java:178)
at
weblogic.jms.frontend.FEConnectionFactory$1.run(FEConnectionFactory.java:319
at weblogic.management.internal.Helper.doLocally(Helper.java:1656)
at
weblogic.jms.frontend.FEConnectionFactory.connectionCreate(FEConnectionFacto
ry.java:316)
at weblogic.jms.frontend.FEConnectionFactory_WLSkel.invoke(Unknown
Source)
at
weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
at
weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
:93)
at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
Hi Alan,
Lots of questions in one message! I'm going to
try and answer them using the shotgun approach -- let
me know if I miss.
(1) It is good practice to close JMS resources when you are done
with them, even if the destination host server crashes. The reason
is that the connection resource may be hosted on a different
WL server than the destination.
(2) Creating a session/producer per message is heavy-weight
in terms of CPU and network - if your app is performance
sensitive is is better to cache these resources for re-use.
See the JMS Performance Guide for details.
(3) From your description I can't tell which two
clients are conflicting. If what I'm writing here
doesn't help, please try to narrow it down and repost.
(4) Make sure that the connection factory does not have
a "client-id" configured for it. Otherwise only one client
can use the connection factory - instead have individual
clients dynamically set their ids.
(5) Note that client-ids are usually only useful for
durable subscriber access, as other types of clients
generally don't need exclusive connections, and therefore
don't need client-ids.
(6) The attached notes, which are for MDBs, may help you
understand durable subscriptions and client-id's better in general.
Tom
Alan May wrote:
> Any feedback would be greatly appreciated. THANKS!
>
> -Alan May
>
>
> Scenario:
>
> Two weblogic 6.1 sp3 instances running on two separate Solaris 8 boxes.
>
> Server a - a message producer(client) for a number of topics and queues on b
>
> Server b - hosts JMS services including all the topics and queues, has both
> message producers and mdb consumers for a number of topics and queues
>
> What I've set up: a durable connection factory for topics for server a,
> topics for server b, queues for server a, and queues for server b (all
> targeted to server b)
>
> I have a singleton on each server that has methods to retrieve the queue
> connection or topic connection appropriate for that server(a single
> connection is
> shared for all topic producers and a separate connection is share for all
> queue producers for each server)
>
> I have each producer open and close a new session every time. However, the
> topic and queue connections are shared for all producers for that JVM. This
> seemed to be the approach recommended by the JMS spec, but do you feel this
> is the appropriate granularity given the above scenario? I am not currently
> closing my jms connection as part of a weblogic shutdown class. Is that
> essential in that case? If the server crashes - are there any
> recommendations on how to handle(if closing the connection is the issue)?
>
> I've confirmed that my JMS clients running with server b are not using the
> connection factories setup for a's use.
>
> Issue:
> ------
> Everything works on server b as expected.
>
> Server a's connections seemed to be fouled. I was getting that the clientid
> was in use(stack trace included below) while trying to fetch the connection.
>
> I stopped server a, removed the fouled connection factories on server
> b(dedicated for server a's use), and created new connection factories for
> a's use. I stopped server b and deleted everything from the two JMSState
> and JMSStore tables, restarted a then b, and tried the test again. This
> time the singleton code could fetch the connection without receiving a
> JMSException, but I was getting an exception when I tried to open a session
> from the connection.
>
> If worst comes to worse, I can stick a stateless session bean on b, to act
> as a delegate producer on behalf of server a, but I'd like to avoid it if
> possible.
>
> Any recommendations? Please let me know if it would be helpful for me to
> clarify any points.
>
>
>
> Server a's original error:
> weblogic.jms.common.InvalidClientIDException: Client id, Parser.topicPrime,
> is in use
>
> Start server side stack trace:
> weblogic.jms.common.InvalidClientIDException: Client id, Parser.topicPrime,
> is in use
> at
> weblogic.jms.frontend.FEConnection.setClientId(FEConnection.java:918)
> at weblogic.jms.frontend.FEConnection.<init>(FEConnection.java:178)
> at
> weblogic.jms.frontend.FEConnectionFactory$1.run(FEConnectionFactory.java:319
> )
> at weblogic.management.internal.Helper.doLocally(Helper.java:1656)
> at
> weblogic.jms.frontend.FEConnectionFactory.connectionCreate(FEConnectionFacto
> ry.java:316)
> at weblogic.jms.frontend.FEConnectionFactory_WLSkel.invoke(Unknown
> Source)
> at
> weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
> at
> weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
> :93)
> at
> weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
> at
> weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
> 2)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
> End server side stack trace
>
>
A durable topic subscriber MDB uses its name to generate its client-id.
Since JMS enforces uniqueness on this client-id, this means that if a durable
subscriber MDB is deployed to multiple servers only one server will be able
to connect. Some applications want a different behavior where
each MDB pool on each server gets its own durable subscription.
The MDB durable subscription id, which must be unique on its topic, comes from:
1) <jms-client-id>MyClientID</jms-client-id>
(the weblogic dtd)
2) if (1) is not set then the client-id
comes from the ejb name.
The durable subscription is uniquely identified within a cluster by a
combination of "connection-id" and "subscription-id". Only one active
connection may use a particular "connection-id" within a WebLogic cluster.
The connection id comes from:
1) The "ClientId" attribute configured on the WebLogic connection factory.
This defaults to null. Note that if the ClientId is set on a connection
factory, only one connection created by the factory
may be active at a time.
2) If (1) is not set, then, as with the subscriber-id,
the connection-id is derived from jms-client-id descriptor attribute:
<jms-client-id>MyClientID</jms-client-id>
(the weblogic dtd)
3) If (1) and (2) are not set, then, as with the subscriber-id,
the connection-id is derived from the ejb name.
Work-around:
A) Create a custom connection-factory for each server:
1) configure "JNDIName" to the same value across all servers
("myMDBCF" in this example)
2) configure "ClientId" to a unique value per server
3) enable "UserTransactionsEnabled"
4) enable "XAConnectionFactoryEnabled"
5) set "AcknowledgePolicy" to "ACKNOWLEDGE_PREVIOUS"
6) target the CF at a single WebLogic server
(Number 5 is required for non-transactional topic MDBs)
B) In the MDB's weblogic-ejb-jar.xml descriptor, set the MDB's connection
factory to the JNDI name of the custom connection factories configured in
(A). Optionally, also specify the subscriber-id via the jms-client-id
attribute.
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>exampleBean</ejb-name>
<message-driven-descriptor>
<connection-factory-jndi-name>myMDBCF</connection-factory-jndi-name>
<jms-client-id>myClientID</jms-client-id>
</message-driven-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
C) Target the application at the same servers that have the custom connection
factories targeted at them.
Notes/Limitations:
1) If the MDB is moved from one server to another, the MDB's corresponding
connection-factory must be moved with it.
2) This work-around will not work if the destination is not in the same
cluster as the MDB. (The MDB can not use the local connection factory, which
contains the connection-id, as connection factories do not work unless they
are in the same cluster as the destination.)
3) This work-around will not work for non-WebLogic JMS topics.
-
Weblogic managed server shutdown immediately after going to STARTING state
Our configuration has 3 managed servers M1, M2, M3. M2 and M3 are in a cluster to share JNDI name for JMS servers. Are M3 server often shutdown on starting up just after the server goes to the STARTING state. I have 2 log traces. The first shows when the server shuts down, the 2nd is when the server initializes correctly. No configuration changes, just a timing race condition. Any help is greatly appreciated.....
Bad startup log trace....
Starting WLS with line:
/Oracle/Middleware/jdk1.6.0_25/bin/java -server -Xms2048m -Xmx2048m -XX:NewSizeThreadIncrease=200 -Dweblogic.ThreadPoolPercentSocketReaders=50 -XX:MaxPermSize=512m -Dweblogic.Name=staAdapter -Djava.security.policy=/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.ProductionModeEnabled=true -Dweblogic.security.SSL.trustedCAKeyStore=/Oracle/Middleware/wlserver_10.3/server/lib/cacerts -da -Dplatform.home=/Oracle/Middleware/wlserver_10.3 -Dwls.home=/Oracle/Middleware/wlserver_10.3/server -Dweblogic.home=/Oracle/Middleware/wlserver_10.3/server -Ddomain.home=/Oracle/Middleware/user_projects/domains/TBI -Dcommon.components.home=/Oracle/Middleware/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=/Oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.domain.config.dir=/Oracle/Middleware/user_projects/domains/TBI/config/fmwconfig -Doracle.server.config.dir=/Oracle/Middleware/user_projects/domains/TBI/config/fmwconfig/servers/staAdapter -Doracle.security.jps.config=/Oracle/Middleware/user_projects/domains/TBI/config/fmwconfig/jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=/Oracle/Middleware/user_projects/domains/TBI/config/fmwconfig/carml -Digf.arisidstack.home=/Oracle/Middleware/user_projects/domains/TBI/config/fmwconfig/arisidprovider -Dweblogic.alternateTypesDirectory=/Oracle/Middleware/oracle_common/modules/oracle.ossoiap_11.1.1,/Oracle/Middleware/oracle_common/modules/oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Dweblogic.management.discover=false -Dweblogic.management.server=t3://localhost:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Duser.timezone=UTC -Xrs -Dweblogic.MaxMessageSize=100000000 -Dweblogic.ext.dirs=/Oracle/Middleware/patch_wls1035/profiles/default/sysext_manifest_classpath:/Oracle/Middleware/patch_jdev1112/profiles/default/sysext_manifest_classpath -Djps.app.credential.overwrite.allowed=true weblogic.Server
<Jan 24, 2013 9:29:16 PM UTC> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Jan 24, 2013 9:29:17 PM UTC> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Jan 24, 2013 9:29:17 PM UTC> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.0-b11 from Sun Microsystems Inc.>
<Jan 24, 2013 9:29:23 PM UTC> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<Jan 24, 2013 9:29:24 PM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Jan 24, 2013 9:29:24 PM UTC> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Jan 24, 2013 9:29:24 PM UTC> <Notice> <Log Management> <BEA-170019> <The server log file /Oracle/Middleware/user_projects/domains/TBI/servers/staAdapter/logs/staAdapter.log is opened. All server side log events will be written to this file.>
<Jan 24, 2013 9:29:25 PM UTC> <Error> <Socket> <BEA-000438> <Unable to load performance pack. Using Java I/O instead. Please ensure that libmuxer library is in :'/Oracle/Middleware/jdk1.6.0_25/jre/lib/amd64/server:/Oracle/Middleware/jdk1.6.0_25/jre/lib/amd64:/Oracle/Middleware/jdk1.6.0_25/jre/../lib/amd64:/Oracle/Middleware/patch_wls1035/profiles/default/native:/Oracle/Middleware/patch_jdev1112/profiles/default/native:/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib'
>
<Jan 24, 2013 9:29:28 PM UTC> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jan 24, 2013 9:29:30 PM UTC> <Warning> <Store> <BEA-280101> <The persistent file store "_WLS_staAdapter" is forced to use buffered I/O and so may have significantly degraded performance. Either the OS/hardware environment does not support the chosen write policy or the native wlfileio library is missing. See store open log messages for the requested and final write policies. See the documentation on store synchronous write policy configuration for advice.>
<Jan 24, 2013 9:29:31 PM UTC> <Warning> <Deployer> <BEA-149617> <Non-critical internal application uddi was not deployed. Error: [Deployer:149158]No application files exist at '/Oracle/Middleware/wlserver_10.3/server/lib/uddi.war'.>
<Jan 24, 2013 9:29:31 PM UTC> <Warning> <Deployer> <BEA-149617> <Non-critical internal application uddiexplorer was not deployed. Error: [Deployer:149158]No application files exist at '/Oracle/Middleware/wlserver_10.3/server/lib/uddiexplorer.war'.>
<Jan 24, 2013 9:29:31 PM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Jan 24, 2013 9:29:31 PM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
*<Jan 24, 2013 9:29:51 PM UTC> <Notice> <WebLogicServer> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>*
*<Jan 24, 2013 9:29:51 PM UTC> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>*
*<Jan 24, 2013 9:29:51 PM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>*
Good startup trace.....
Starting WLS with line:
/Oracle/Middleware/jdk1.6.0_25/bin/java -server -Xms2048m -Xmx2048m -XX:NewSizeThreadIncrease=200 -Dweblogic.ThreadPoolPercentSocketReaders=50 -XX:MaxPermSize=512m -Dweblogic.Name=staAdapter -Djava.security.policy=/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.ProductionModeEnabled=true -Dweblogic.security.SSL.trustedCAKeyStore=/Oracle/Middleware/wlserver_10.3/server/lib/cacerts -da -Dplatform.home=/Oracle/Middleware/wlserver_10.3 -Dwls.home=/Oracle/Middleware/wlserver_10.3/server -Dweblogic.home=/Oracle/Middleware/wlserver_10.3/server -Ddomain.home=/Oracle/Middleware/user_projects/domains/TBI -Dcommon.components.home=/Oracle/Middleware/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=/Oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.domain.config.dir=/Oracle/Middleware/user_projects/domains/TBI/config/fmwconfig -Doracle.server.config.dir=/Oracle/Middleware/user_projects/domains/TBI/config/fmwconfig/servers/staAdapter -Doracle.security.jps.config=/Oracle/Middleware/user_projects/domains/TBI/config/fmwconfig/jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=/Oracle/Middleware/user_projects/domains/TBI/config/fmwconfig/carml -Digf.arisidstack.home=/Oracle/Middleware/user_projects/domains/TBI/config/fmwconfig/arisidprovider -Dweblogic.alternateTypesDirectory=/Oracle/Middleware/oracle_common/modules/oracle.ossoiap_11.1.1,/Oracle/Middleware/oracle_common/modules/oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Dweblogic.management.discover=false -Dweblogic.management.server=t3://localhost:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Duser.timezone=UTC -Xrs -Dweblogic.MaxMessageSize=100000000 -Dweblogic.ext.dirs=/Oracle/Middleware/patch_wls1035/profiles/default/sysext_manifest_classpath:/Oracle/Middleware/patch_jdev1112/profiles/default/sysext_manifest_classpath -Djps.app.credential.overwrite.allowed=true weblogic.Server
<Jan 24, 2013 5:31:06 PM UTC> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Jan 24, 2013 5:31:06 PM UTC> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Jan 24, 2013 5:31:06 PM UTC> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.0-b11 from Sun Microsystems Inc.>
<Jan 24, 2013 5:31:07 PM UTC> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<Jan 24, 2013 5:31:08 PM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Jan 24, 2013 5:31:08 PM UTC> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Jan 24, 2013 5:31:08 PM UTC> <Notice> <Log Management> <BEA-170019> <The server log file /Oracle/Middleware/user_projects/domains/TBI/servers/staAdapter/logs/staAdapter.log is opened. All server side log events will be written to this file.>
<Jan 24, 2013 5:31:09 PM UTC> <Error> <Socket> <BEA-000438> <Unable to load performance pack. Using Java I/O instead. Please ensure that libmuxer library is in :'/Oracle/Middleware/jdk1.6.0_25/jre/lib/amd64/server:/Oracle/Middleware/jdk1.6.0_25/jre/lib/amd64:/Oracle/Middleware/jdk1.6.0_25/jre/../lib/amd64:/Oracle/Middleware/patch_wls1035/profiles/default/native:/Oracle/Middleware/patch_jdev1112/profiles/default/native:/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib'
>
<Jan 24, 2013 5:31:13 PM UTC> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jan 24, 2013 5:31:14 PM UTC> <Warning> <Store> <BEA-280101> <The persistent file store "_WLS_staAdapter" is forced to use buffered I/O and so may have significantly degraded performance. Either the OS/hardware environment does not support the chosen write policy or the native wlfileio library is missing. See store open log messages for the requested and final write policies. See the documentation on store synchronous write policy configuration for advice.>
<Jan 24, 2013 5:31:15 PM UTC> <Warning> <Deployer> <BEA-149617> <Non-critical internal application uddi was not deployed. Error: [Deployer:149158]No application files exist at '/Oracle/Middleware/wlserver_10.3/server/lib/uddi.war'.>
<Jan 24, 2013 5:31:15 PM UTC> <Warning> <Deployer> <BEA-149617> <Non-critical internal application uddiexplorer was not deployed. Error: [Deployer:149158]No application files exist at '/Oracle/Middleware/wlserver_10.3/server/lib/uddiexplorer.war'.>
<Jan 24, 2013 5:31:16 PM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Jan 24, 2013 5:31:16 PM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
**<Jan 24, 2013 5:31:30 PM UTC> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>**
**<Jan 24, 2013 5:31:30 PM UTC> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>**
**<Jan 24, 2013 5:31:30 PM UTC> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of STA_cluster.>**
**<Jan 24, 2013 5:31:38 PM UTC> <Notice> <Cluster> <BEA-000142> <Trying to download cluster JNDI tree from server staEngine.>**
**<Jan 24, 2013 5:31:38 PM UTC> <Notice> <Cluster> <BEA-000164> <Synchronized cluster JNDI tree from server staEngine.>**
**<Jan 24, 2013 5:31:38 PM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>**
**<Jan 24, 2013 5:31:38 PM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>**Thanks. Unfortunately I've already done that and it doesn't work. I've included the -Xrs option in the managed server java command line arguments, see below. However, either it is in the wrong location on the java argument list or something else is going on, because it is not working. See the JVM command line below of the managed server.....
/Oracle/Middleware/jdk1.6.0_25/bin/java -server -Xms2048m -Xmx2048m -XX:NewSizeThreadIncrease=200 -Dweblogic.ThreadPoolPercentSocketReaders=50 -XX:MaxPermSize=512m -Dweblogic.Name=staAdapter -Djava.security.policy=/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.ProductionModeEnabled=true -Dweblogic.security.SSL.trustedCAKeyStore=/Oracle/Middleware/wlserver_10.3/server/lib/cacerts -da -Dplatform.home=/Oracle/Middleware/wlserver_10.3 -Dwls.home=/Oracle/Middleware/wlserver_10.3/server -Dweblogic.home=/Oracle/Middleware/wlserver_10.3/server -Ddomain.home=/Oracle/Middleware/user_projects/domains/TBI -Dcommon.components.home=/Oracle/Middleware/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=/Oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.domain.config.dir=/Oracle/Middleware/user_projects/domains/TBI/config/fmwconfig -Doracle.server.config.dir=/Oracle/Middleware/user_projects/domains/TBI/config/fmwconfig/servers/staAdapter -Doracle.security.jps.config=/Oracle/Middleware/user_projects/domains/TBI/config/fmwconfig/jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=/Oracle/Middleware/user_projects/domains/TBI/config/fmwconfig/carml -Digf.arisidstack.home=/Oracle/Middleware/user_projects/domains/TBI/config/fmwconfig/arisidprovider -Dweblogic.alternateTypesDirectory=/Oracle/Middleware/oracle_common/modules/oracle.ossoiap_11.1.1,/Oracle/Middleware/oracle_common/modules/oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Dweblogic.management.discover=false -Dweblogic.management.server=t3://localhost:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Duser.timezone=UTC -Xrs -Dweblogic.MaxMessageSize=100000000 -Dweblogic.ext.dirs=/Oracle/Middleware/patch_wls1035/profiles/default/sysext_manifest_classpath:/Oracle/Middleware/patch_jdev1112/profiles/default/sysext_manifest_classpath -Djps.app.credential.overwrite.allowed=true weblogic.Serve
Maybe you are looking for
-
Error while moving objects from BMM to Presentation layer: 46036
Hi, I created some aggregate logical columns in a logical fact table in BMM . Next, I created a branch to already existing Dimensional hierarchy and used those aggregate columns in the branch hierarchy. The Original Hierarchy was using columns from 2
-
I recently dropped my 4th gen ipod touch and i want to know how much it will cost to get it replaced by apple. PS i did not buy it from apple i bought it on ebay so it doesnt have a warrenty
-
SELECT statement comparing 2 fields in a table.
Hi, Can someone help me out in making a efficient SELECT statement for the follwing requirement. Say, I want to select all the records from a database table where the field, PLANT is equal to field SALESORG in the table (i.e., when both fields are e
-
I have a little problem with my decimal values while I'm building an app on the iOS 5.1.1 SDK, and I don't know how to fix this. I have a meathod (I'm pretty sure it's declared in my header file under the right class), and this is the meathod: -(IBAc
-
i have tried to update my iphone 3gs and i need to get ios5 and when i click on check for updates it says that itunes can not be contacted and check my internet connection but i have internet? how else can i get ios5 on my phone?