Trimoorthy Kotte

+ Follow
since Mar 31, 2006
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Trimoorthy Kotte

Hope you have created JMS queues in managed servers also. if you have created jms queues on managed servers. Then create a distributed queue with a jndi name say "test.distributed.queue". Then add jms queues (already created) of each managed servers. Then try accessing the distributed queue with the jndi name. Also see that you are using the provider ur� of one of the managed srevers. Then you can see the expected behavior cluster. you can see jms messages distibuted to two jms queue , on each managed servers. Also remeber to configure the connection factory to loadbalance in round robin

Happy New Year...
10 years ago
Hi, Hope you are using MQ binddings file for wrapping up MQ manager as connectionfactory and the MQ manager is on the local machine. the connectionfactory needs to be XA enabled.

In the ejbCreate I found JMS connection is bind to context object something like this.
ctx.bind(jndiName, MQQueueConnectionFactory);
ctx.bind(queueJndiName, Queue);
I gues you are using MQ as foreign JMS server..
Actually the connection is not bound in the context object. The above code just adds the connectionfactory and queue objects into the jndi tree. These objects are just object representation of queue with out actual connection (MQ queue in case your Messaging middleware is IBM MQ) and connectionafactory (MQ queue manager). When MDB gets deployed the bean makes connection to the MQ queue manager.(hope I am reasonably correct here)
Therefore closing of the MQ Conection does not have any relation with the context.
Closing of MQ connection will not remove the jndi bindings for the queue and connectionfactory.
<Mar 1, 2002 11:23:23 AM IST> <Warning> <EJB> <010054> <EJB Deployment: UserProfileEJB has a class com.gmac
.sm.userprofile.ejb.session.UserProfileLocal which is in the classpath. This class should only be located i
n the ejb-jar file.>
Though it not likely, can you check if you have the jar file added to the classpath, if so remove. this

This is the warning I am getting for each and every bean. Even though I am trying to deploy this EJB,
but I am unable to deploy the EJB in WL 7.0, there also i am getting the following the Exceptions,
Are you using WebLogic Server 7.0 or WebLogic Platform 7.0 (WebLogic Integration ). You also specified you are getting this issue with all the EJBs. What kind of EJBs are these.
WebLogic Integration comes with set of Applications (exploded) under which there will be some ejb modules, if you try to deploy ejb under the existing application (thru console), you will find issues.(pls ignore this if you are using WebLogic Server alone) For deploying the EJB under the existing application, you need to add entry in the application.xml. Also you need to copy the ejb jar file to the staging folder of eaching managed server (or delete the managed servers stage folder and strat the servers and then deploy).
Small correction : Generally the startup scripts are not configured to run in background and script runs in same/user (also called current) shell by default
12 years ago

In addition to what Sachin has pointed out, there is one more common mistake in the unix weblogic startup script is thatdevelopers tend to run the script in the background and the server will be running only till you/developer keeps the unix/telnet session active. Once the sessio is inactive and timesout the weblogic server also goes down.

This is due to the java process is atarted in the same shell as the user shell.
12 years ago
When a client reads the message the message will be deleted from the queue. JMS outofMemoryerror occur due to the fact that , JMS server implementation by the app server you are using might be holding all the message in the JVM memory itself (apart from persisting the message to file/database). If you have provision on your JMserver to use paging store configuration, then it will help you solve this problem. (WebLogic supports this)

The solution (xss) you are trying to implement resolves StackOb=verFlow exceptions but not outOfMemory errors.
Apologies, I missed out the text last time I was posting the reply. if you are using WebLogic Aplication server, you can access JMS MBeans through weblogic Mbean API for finding out the JMS queue depth. You might have similar APIs available in other app servers .