Problem in JMS congiuration in cluster

Hi,
I am facing a big problem in cluster.
I am using weblogic server8.1 with SP5.
Created a cluster with 2 managed servers. Two JMS servers and deployed them on managed servers i.e. JMSServers1 is deployed on ManagedServer1 (migratable) and JMSServer2 is deployed on ManagedServer2 (migratable). There are 4 distributed JMS Topics are created for each server. My program uses these JMS topics and picks up the data and inserts them into the Database. The problem here is it is inserting 2 times each record. If I use single server without cluster it is inserting one time. Some times it is not JMS clients not at all invoked when even a message is published into the topic.
What might be the problem? I am very new to this clustering. Its very urgent please.

Hi,
thanks a lot for your replies.
our driver settings are correct (as I can see).
I removed value 819 from CCSID, but we have the same effect.
The messages in the local queue manager are TextMessages in XML.
Does anybody know, if we need the standard modules (ConvertJMSMessageToBinary and ConvertBinaryToXMBMessage) in this case?
Is it possible to set the CCSID for the message payload anywhere in the configuration?
The CCSID in the Source tab doesn't have any influence to the encoding of the payload message, only to the header data.
Regards
Thorsten

Similar Messages

Problem with JMS in a Cluster

In summary I am having a problem with my application when it is running on the server that does not contain the JMS.
          Setup:
          2 machines:- Server 1 with the Admin Server and a Managed Server with JMS and a Distributed Queue. Second machine (Server 2) with a managed server. The two managed servers are in a Cluster.
          The connection factory has xa enabled.
          The queue is a distributed queue, with one member queue - on server 1.
          Scenario 1 (works):
          Deploy my application on Server 1 only
          Scenario 2 (works):
          Deploy my application on Server 1 and Server 2
          When the application puts messages on the JMS queue, the messages are processed round robin by the MDB on both Server 1 and Server 2 - as expected.
          Scenario 3 - Does not work
          Deploy my application on Server 2 only
          The application successfully sends a message to the queue - I can see it in queue through the console.
          However the MDB never processes the message. On the queue, I can see 0 consumers.
          Essentially the MDB appears to deploy correctly from the server log but never appears as a consumer on the queue.
          I know the above information is very brief, however I can provide more configuration details and detailed logging if required.

On a further look through the logs, I have found the following Warning message which may point to the reason why my MDB is not receiving messages from JMS:
          <25-Apr-2005 17:26:01 o'clock IST> <Warning> <EJB> <BEA-010220> <The jms destination 'AsyncMessageQueue' is a distributed destination and it has no physical destination(s) on the current weblogic server. As per distributed destination co-location rules, no pool was creted for the MDB 'AsyncMessage(Application: m3-j2ee_Weblogic21apr_2, EJBComponent: ejb_framework.jar)' on this weblogic server. Hence the MDB 'AsyncMessage(Application: m3-j2ee_Weblogic21apr_2, EJBComponent: ejb_framework.jar)' cannot receive any messages on this server.>
          I have created a Destination on the JMS Server ("Replicate JNDI Name In Cluster" is set), and I have created a Distributed Destination, which has as its member the Destination associated with the JMS Server.
          If the JMS is not on the same server as the deployed application, how do I get the MDB to connect to the physical destination?
          Do I always need a Physical Destination on the the same server as my deployed application? If so, how do I create a Physical Destination on the server that does not have the JMS?
          Any help appreciated.

Problems with JMS: Error JMS BEA-040368

Hi,
I have run into a problem using JMS on BEA. It appears to happen when we run huge amounts of messages through the queue (100 000+).
Once this error occurs, we cant get rid of it. Restarting server, re-dployment, nothing works. Every subsequent message sent to the JMS produces this error.
According to the error message, we have exceeded the maximum allowed transactions for the server, but how do we reset the transactions? And what is causing the error to appear in the first place? Somthing I forget to close or flush?
I have QueueConnection, QueueSession and QueueRecevier objects open for all transactions, and close them when the bean is destroyed. Should I rather create and close them for each transaction?
Here is the exception:
<15.jun.2005 kl 14.55 CEST> <Error> <JMS> <BEA-040368> <The following exception has occurred:
java.lang.RuntimeException: [EJB:010166]Error occurred while starting transaction: javax.transaction.SystemException: Exceeded maximum allowed transactions on server 'myserver'.
at weblogic.ejb20.internal.MDListener.perhapsBeginTransaction()V(MDListener.java:325)
at weblogic.ejb20.internal.MDListener.execute(Lweblogic.kernel.ExecuteThread; )V(MDListener.java:339)
at weblogic.ejb20.internal.MDListener.onMessage(Ljavax.jms.Message; )V(MDListener.java:262)
at weblogic.jms.client.JMSSession.onMessage(Ljavax.jms.MessageListener;Lweblogic.jms.common.MessageImpl; )V(JMSSession.java:2678)
at weblogic.jms.client.JMSSession.execute(Lweblogic.kernel.ExecuteThread; )V(JMSSession.java:2598)
at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest; )V(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread; )V(Unknown Source)
>

Developments
It turned out that my "client" used: this.queueSession = queueConnection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
While the "server" used: this.queueSession = queueConnection.createQueueSession(true, Session.AUTO_ACKNOWLEDGE);
Now changing both sessions to use transactions (createQueueSession(true, Session.AUTO_ACKNOWLEDGE)) and fortifying the use of QueueSession.commit() when sending and receiving messages seemed to solve the problem... for a while.
After a few new tests the problem appeared again, this time on the "client" side. It is obvious that transaction are somehow not commited correctly even though Session.commit() is called after each and every message is sent and received.
Btw. To make the app "clean up" hanging transactions faster you can change the value in the console at:
Mydomain --> Services --> JTA --> Abandon Timeout Seconds
weblogic.jms.common.TransactionRolledBackException: Exceeded maximum allowed transactions on server 'myserver':error beginning transacted session's internal transaction
at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:137)
at weblogic.jms.dispatcher.DispatcherImpl_814_WLStub.dispatchSyncNoTranFuture(Unknown Source)
at weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSyncNoTran(DispatcherWrapperState.java:472)
at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:391)
at weblogic.jms.client.JMSProducer.send(JMSProducer.java:186)
at no.nrk.returia.test.TestSMSInAdapter.send(TestSMSInAdapter.java:133)
at no.nrk.returia.test.TestSMSInAdapter.main(TestSMSInAdapter.java:206)

Problem with JMS migration when using Ctrl+C to stop the managed server in cluster

          Hi,
          I am having a clustered weblogic application running on Weblogic 7.0 SP5. My application
          uses JMS as a asynchrous communication. We have MDB which listens to these JMS
          messages.
          If something is being processed on Managed Server 1 and while the request is in
          process, i am stopping the the MAnaged SErver 1 using Ctrl+C.
          After this, i go to admin console and migrate teh JTA and JMS. After this, i am
          expecting other running Managed Server should restart the incomplete transaction.
          But this is not happening. The Managed Serve2 doesn't process the requst.
          But when i restart teh MAnaged SErver 1 again, it takes up the same request and
          processes it.
          Is this a known problem with Weblogic that it doesn't support Ctlr+C case?
          Please note that the same thing is working fine when i stop the server using Admin
          console(Normal shutdown OR forced shutdown).
          Any comments in this regards are apprecciated.
          Thanks,
          Naresh


          Hi,
          I am having a clustered weblogic application running on Weblogic 7.0 SP5. My application
          uses JMS as a asynchrous communication. We have MDB which listens to these JMS
          messages.
          If something is being processed on Managed Server 1 and while the request is in
          process, i am stopping the the MAnaged SErver 1 using Ctrl+C.
          After this, i go to admin console and migrate teh JTA and JMS. After this, i am
          expecting other running Managed Server should restart the incomplete transaction.
          But this is not happening. The Managed Serve2 doesn't process the requst.
          But when i restart teh MAnaged SErver 1 again, it takes up the same request and
          processes it.
          Is this a known problem with Weblogic that it doesn't support Ctlr+C case?
          Please note that the same thing is working fine when i stop the server using Admin
          console(Normal shutdown OR forced shutdown).
          Any comments in this regards are apprecciated.
          Thanks,
          Naresh

Always selecting the local JMS in a cluster, is it possible? (in 6.1)

Hi,
          A 6.1 cluster has a JMS server running on each node. The JMS client
          code has a component to do the fail over "manually": it tries one
          node, if that doesn't work it tries the next and so on. The
          destination names are different (and replicated in the JNDI tree).
          If everything is ok, all requests go the first server (meaning network
          traffic). Is there an elegant way to always try with the local JMS
          server before the remote ones, without minimum configuration
          dependency (i.e. no system properties passed at start-up telling what
          JMS servers to use and so on)
          Perhaps something using JMSDestinationRuntimeMBean and
          JMSServerRuntimeMBean?
          Oh, just noticed JMSRuntimeMBean.html.getJMSServers(), this might do
          it. I'll post it nonetheless in case other people have better ideas.
          Thanks.


Thanks again.
          In fact, if I use the server/queue syntax, I can use the queue name
          (the Name attrribute) not the JNDI name. This in case these names can
          be the same in a cluster deployment (with replicated JNDI names
          different). I'll check soon.
          Regarding the connection factory, I wonder whether WL doesn't do its
          otherwise typical performance improvements and return a local
          connection if there is one (as it already does with remote
          interfaces). I couldn't find a reference to such an optimization in
          the JMS documentation, though.
          On Wed, 17 Apr 2002 09:37:59 -0400, Tom Barnes
          <[email protected]> wrote:
          >email wrote:
          >
          >> Thank you. The second option looks better than the first because it
          >> allows using destinations on other JMS servers (by interrogating an
          >> MBean to get the JMS servers in the cluster).
          >
          >The second option only works if the connection is already connected
          >to the correct server. If you use mbeans, you can glean the URL
          >of the correct server by obtaining the IP and address of the remote
          >server from the ServerMBean - the "target" of the JMSServerMBean.
          >
          >An issue with this feature is the connection factory - which round-robins the
          >location of connection in certain cases. Currently the only way to ensure the
          >connection
          >factory does not do this is to target it at a single server. I suppose one
          >could duplicate the connection factory and target each duplicate at
          >a different server, but that requires giving each one a different name.
          >This may not be an issue with server-side contexts, I will investigate.
          >
          >
          >> It's useful to know
          >> about JNDINameReplicated, but that way accessing a remote destination
          >> will not be possible at all.
          >>
          >
          >I think you could write a small a startup class to look up the queue in the
          >local context and register the queue in a
          >replicated context with a different JNDI name. This way the destination
          >is advertised both ways. Fairly sure this would work.
          >
          >>
          >> BTW, a related question on reliability: accessing a remote destination
          >> if the local is down means there is a local problem with the JMS
          >> server or the queue, but the container is fine. Now, how likely is
          >> this in practice? Having the container up but the JMS subsystem down.
          >>
          >
          >Parts (or all) of JMS can fail due to configuration
          >errors -- commonly JNDI name collisions of destinations and/or factories,
          >failure to set the target, or using the same server name or jms server name
          >on two different servers.
          >
          >If you are using a file-store, boot failures occur with things
          >like file-store not found, or relatively catastrophic failures like
          >out-of-memory.
          >
          >If you are using a JDBC store, there is a dependency on the database being up.
          >
          >
          >>
          >> Indeed, 7.0 would solve it but that's several months ahead if I
          >> understand correctly:)
          >>
          >
          >Not months. Weeks. A very few weeks. I'm not sure what is officially
          >announced
          >so I can't get more specific.
          >
          >>
          >> Thanks again.
          >>
          >> On Tue, 16 Apr 2002 14:48:02 -0400, Tom Barnes
          >> <[email protected]> wrote:
          >>
          >> >Consider the new "JNDINameReplicated" configuration parm on the
          >> >destination. Ensure each server running 6.0SP2 with patch CR061106, or
          >> >6.1SP3 (not out yet) and later, or 7.0. Configure each queue to have the
          >> >same JNDI name, and also take care to set the destination’s new
          >> >“JNDINameReplicated” parameter to false. This turns off name
          >> >replications, so the JNDI name of the dest is only visible on the server
          >> >local to the context.
          >> >
          >> >Consider naming all destinations the same and looking them up the dest via
          >> >session.createQueue("./queuename"), this is a new syntax that restricts
          >> >the lookup to the same server as the one the JMS connection is talking
          >> >to. The normal syntax is "servername/queuename". This feature is
          >> >slated for 6.1SP3, no guarantees, (or try ask customer support to get this
          >> >feature in early as a patch, no guarantees there either), or 7.0.
          >> >
          >> >Consider not rolling your own and using 7.0, which has a rich distributed
          >> >destination feature built in.
          >> >
          >> >Tom
          >> >
          >> >email wrote:
          >> >
          >> >> Hi,
          >> >>
          >> >> A 6.1 cluster has a JMS server running on each node. The JMS client
          >> >> code has a component to do the fail over "manually": it tries one
          >> >> node, if that doesn't work it tries the next and so on. The
          >> >> destination names are different (and replicated in the JNDI tree).
          >> >>
          >> >> If everything is ok, all requests go the first server (meaning network
          >> >> traffic). Is there an elegant way to always try with the local JMS
          >> >> server before the remote ones, without minimum configuration
          >> >> dependency (i.e. no system properties passed at start-up telling what
          >> >> JMS servers to use and so on)
          >> >>
          >> >> Perhaps something using JMSDestinationRuntimeMBean and
          >> >> JMSServerRuntimeMBean?
          >> >>
          >> >> Oh, just noticed JMSRuntimeMBean.html.getJMSServers(), this might do
          >> >> it. I'll post it nonetheless in case other people have better ideas.
          >> >>
          >> >> Thanks.
          >> >
          >

Problem Configuring JMS Error Queue

Domain configuration : one adminServer, One cluster, 2 managedservers in cluster
Two distibuted Queues: InboundQueue, Error Queue
I want to redirect any bad message from InboundQueue to ErrorQueue and discard it.
It worked fine for 4 yrs in Wls 8.1 ( did configured in 8.1)..
now i upgrde to wls 10.1 and i did same configuration but InboundQueue is not redirecting to Errorqueue..
Dont know where i am missing..
here is the config.xml entry and jms/JmModule.xml files..
config.xml entry_
<jms-system-resource>
<name>JmsModule</name>
<target>cluster1</target>
<sub-deployment>
<name>subdeployment1</name>
<target>JmsServer1,JmsServer2</target>
</sub-deployment>
<descriptor-file-name>jms/JmsModule-jms.xml</descriptor-file-name>
</jms-system-resource>
JmsModule.xml_
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-jms xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/920 http://www.bea.com/ns/weblogic/920.xsd">
<uniform-distributed-queue name="ErrorQueue">
<sub-deployment-name>subdeployment1</sub-deployment-name>
<delivery-params-overrides>
<delivery-mode>Non-Persistent</delivery-mode>
<time-to-deliver>-1</time-to-deliver>
<time-to-live>-1</time-to-live>
<priority>-1</priority>
<redelivery-delay>-1</redelivery-delay>
</delivery-params-overrides>
<delivery-failure-params>
<redelivery-limit>0</redelivery-limit>
</delivery-failure-params>
<jndi-name>ErrorQueue</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
<forward-delay>-1</forward-delay>
</uniform-distributed-queue>
<uniform-distributed-queue name="InboundQueue">
<sub-deployment-name>subdeployment1</sub-deployment-name>
<delivery-params-overrides>
<delivery-mode>Persistent</delivery-mode>
<time-to-deliver>10</time-to-deliver>
<time-to-live>10</time-to-live>
<priority>2</priority>
<redelivery-delay>10</redelivery-delay>
</delivery-params-overrides>
<delivery-failure-params>
<error-destination>ErrorQueue</error-destination>
<redelivery-limit>1</redelivery-limit>
<expiration-policy>Redirect</expiration-policy>
</delivery-failure-params>
<jndi-name>InboundQueue</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
<forward-delay>10</forward-delay>
</uniform-distributed-queue>
</weblogic-jms>
Any help
Thanks
ksr

Are you still having a problem? If so, I recommend trying to simplify the reproducer by removing the "time-to-deliver", "redelivery-delay", and "time-to-live" settings.
<time-to-deliver>10</time-to-deliver>
<time-to-live>10</time-to-live>
<redelivery-delay>10</redelivery-delay>
Note that these are all set to a very small value (10 milliseconds), and that the message will expire before it can be delivered or redelivered. The delivery delay is 10 millis, so by the time the delivery delay completes, the time-to-live will have passed -- furthermore, if there was no delivery delay, the redelivery delay is at 10 millis -- so by the time the redel occurs the time-to-live expires).
Tom

Problem with JMS Adapter after upgrade to 7.1

Hi All,
After an upgrade the JMS adapter connecting IBM Websphere MQ gives the following error:
Error connecting due to missing class: com.ibm.mq.jms.MQQueueConnectionFactory. Ensure that all resources required are present in the JMS provider library: aii_af_jmsproviderlib.sda
Since we are now on PI 7.1, the directory the JMS adapter should be looking for the libraries should be com.sap.aii.adapter.lib.sda. Has anyone else come across this problem after an upgrade? Should we remove the old aii_af_jmsproviderlib.sda?
Edited by: Luqman on Oct 31, 2008 5:39 PM

does following JAR files in place in aii_af_jmsproviderlib.sda.
●      com.ibm.mq.jar
●      com.ibm.mqbind.jar
●      com.ibm.mqjms.jar
●      connector.jar (use the JAR file from the J2EE client directory)
can u check n confirm.
i hopw u have followed the proper deployement process.
chirag

Problem creating JMS Error Destination via Ant in WLS 8.1

We've got several JMS queues in our application. We create the server via Ant (using the wlconfig task).
All is well, the queues have been working fine, until we try to add an error destination queue (after several attempts to handle the message, it'll be sent to the error queue for later troubleshooting).
Here's an example of what we've got now:
<create type="JMSQueue" name="batchQueue" property="jmsqueue">
    <set attribute="JNDIName" value="net.nike.cdm.batchQueue"/>
    <set attribute="RedeliveryLimit" value="5"/>
</create>We create another queue to handle the errors, and then add an attribute to the first to point to the second:
<create type="JMSQueue" name="batchErrorQueue" property="batchErrorQueue">
    <set attribute="JNDIName" value="net.nike.cdm.batchErrorQueue"/>
    <set attribute="RedeliveryLimit" value="5"/>
</create>
<create type="JMSQueue" name="batchQueue" property="jmsqueue">
    <set attribute="JNDIName" value="net.nike.cdm.batchQueue"/>
    <set attribute="RedeliveryLimit" value="5"/>
    <set attribute="ErrorDestination" value="${batchErrorQueue}"/>
</create>This seems logical, because if we do this same exact operation via the console, the config.xml goes from this:
<JMSQueue JNDIName="net.nike.cdm.batchQueue"
            Name="batchQueue" RedeliveryLimit="5"/>to this:
<JMSQueue ErrorDestination="batchErrorQueue"
            JNDIName="net.nike.cdm.batchQueue"
            Name="batchQueue" RedeliveryLimit="5"/>
<JMSQueue JNDIName="net.nike.cdm.batchErrorQueue" Name="batchErrorQueue"/>The error we get when trying to do this via Ant is:
[wlconfig] A destination and its ErrorDestination must both be on the same JMS server. (The problematic destination is "batchQueue" on JMS server "cdmdomain"). Also, an ErrorDestination can not be null if the ExpirationPolicy for a destination is "redirect" and a destination can not specify itself as its ErrorDestination.Flipping on -verbose in Ant, the actual exception is:
[wlconfig] SET -mbean cdmdomain:Name=batchQueue,Type=JMSQueue -property ErrorDestination cdmdomain:Name=batchErrorQueue,Type=JMSQue
[wlconfig] A destination and its ErrorDestination must both be on the same JMS server. (The problematic destination is "batchQueue"
s its ErrorDestination.
      [if] Error in class net.sf.antcontrib.logic.IfTask
BUILD FAILED
file:C:/viewstore/CDM_R6.5_Development/B2B_CDM/dev/build.xml:1399: Error invoking MBean command: java.lang.NullPointerException
       at weblogic.ant.taskdefs.management.WLConfig.handleException(WLConfig.java:567)
       at weblogic.ant.taskdefs.management.WLConfig.invokeCommand(WLConfig.java:381)
       at weblogic.ant.taskdefs.management.WLConfig.invokeSetCommand(WLConfig.java:235)
       at weblogic.ant.taskdefs.management.WLConfig.invokeCreateCommand(WLConfig.java:163)
       at weblogic.ant.taskdefs.management.WLConfig.executeCommands(WLConfig.java:106)
       at weblogic.ant.taskdefs.management.WLConfig.invokeCreateCommand(WLConfig.java:167)
       at weblogic.ant.taskdefs.management.WLConfig.executeCommands(WLConfig.java:106)
       at weblogic.ant.taskdefs.management.WLConfig.execute(WLConfig.java:89)
       at org.apache.tools.ant.Task.perform(Task.java:341)
       at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:117)
       at org.apache.tools.ant.Task.perform(Task.java:341)
       at net.sf.antcontrib.logic.IfTask.execute(Unknown Source)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:324)
       at org.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:147)
       at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:193)
       at org.apache.tools.ant.Task.perform(Task.java:341)
       at org.apache.tools.ant.Target.execute(Target.java:309)
       at org.apache.tools.ant.Target.performTasks(Target.java:336)
       at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
       at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
       at org.apache.tools.ant.Main.runBuild(Main.java:609)
       at org.apache.tools.ant.Main.start(Main.java:196)
       at org.apache.tools.ant.Main.main(Main.java:235)So, my question is, what are we doing wrong? What IS the syntax to set an error destination for a JMS queue via Ant for WLS 8.1?
Any help would be greatly appreciated
Thanks,
Douglas Bullard

I get exactly the same problem - was a resolution to this issue found?
Thanks,
Richard Marriott
[email protected]

Management console problem after installing recommended patch cluster

Hello everyone.
I just got a new SUN 440 server, it didn't come with the solaris os installed and so I installed solaris 9 12/03 to it. The installation went fine and I could start the management console with no problems at all. Then I went to sunsolve.sun.com to download the latest recommended patch clusters for solaris 9 (this was yesterday Sept.-06-2006), I downloaded the file, checked it with md5sum, unzipped it, went to single user mode and ran the install_patch script. After the patch cluster finished installing I rebooted the server for the patches to take effect, I logged in, tried to run console management 2.1 and it starts OK but I cannot use any services it offers because it says (in the console events):
"Server Not Running: no solaris management console server was available on the specified server. Please ensure there is a Solaris Management Console server available on the specified host and that it is running"
When I click on "See Exception" I get (for a particular service that is... in this case com.sun.admin.fsmgr.client.VFsMgr - for managing file systems):
java.rmi.RemoteException: Server RMI is null:
at sun.com.management.viperimpl.client.ViperClient.lookupServer(ViperClient.java:376)and so on...
I already checked that the service is running on port 898 and it seems that there is no other app. using that same port. I also restarted the service using /etc/init.d.init stop/status/start but I get the same results.
I don't know solaris very much and don't know what else to do, please help.
Thanks in advance.

Well, I guess what you see isn't what you get.
Guess I'm used to the fact USENET just left things formatted the way they were :-O

Problem starting managed server in Cluster

Hi,
I'm using cluster with 2 managed server. other managed server2 is runing ok in the cluster now when I am starting managed server1 in a cluster this error is coming
The WebLogic Server encountered a critical failure
Reason: Assertion violated
Exception in thread "main" java.lang.NoClassDefFoundError
at weblogic.protocol.ServerIdentityManager.findServerIdentity(ServerIdentityManager.java:65)
at weblogic.protocol.URLManager.findAdministrationURL(URLManager.java:170)
at weblogic.server.ServerLifeCycleRuntime.getLifeCycleOperationsRemote(ServerLifeCycleRuntime.java:677)
at weblogic.t3.srvr.ServerRuntime.sendStateToAdminServer(ServerRuntime.java:406)
at weblogic.t3.srvr.ServerRuntime.updateRunState(ServerRuntime.java:392)
at weblogic.t3.srvr.T3Srvr.setState(T3Srvr.java:172)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:373)
at weblogic.Server.main(Server.java:67)
Could you pl tell the reason of this error?
Thanks in advance
Hi,
Can anybody help?
Edited by: user10680571 on Dec 4, 2008 4:42 AM

Thanks David.
During starting this managed server in cluster when I do tail -f <log_file_name> I can see this error message. But this message I can't see in log however ending log details- Is this something related with CLASSPATH problem?
<04-Dec-2008 10:11:18 o'clock GMT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to t
he end of the classpath:
/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n-schemas.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_c
ommon.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wl
p/netuix_common.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/netuix_schemas.jar:/software/bea/wls/920/weblogic92/pla
tform/lib/wlp/netuix_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/wsrp-common.jar>
<04-Dec-2008 10:11:21 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Serve
r VM Version 1.5.0_07-b03 from Sun Microsystems Inc.>
<04-Dec-2008 10:11:33 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 Fri Jun 23 20:47:26 EDT 20
06 783464 >
<04-Dec-2008 10:12:06 o'clock GMT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /software/bea/wls/920/license.bea>
<04-Dec-2008 10:12:06 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<04-Dec-2008 10:12:06 o'clock GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<04-Dec-2008 12:12:26 o'clock GMT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to t
he end of the classpath:
/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n-schemas.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_c
ommon.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wl
p/netuix_common.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/netuix_schemas.jar:/software/bea/wls/920/weblogic92/pla
tform/lib/wlp/netuix_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/wsrp-common.jar>
<04-Dec-2008 12:12:35 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Serve
r VM Version 1.5.0_07-b03 from Sun Microsystems Inc.>
<04-Dec-2008 12:13:03 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 Fri Jun 23 20:47:26 EDT 20
06 783464 >
<04-Dec-2008 12:13:56 o'clock GMT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /software/bea/wls/920/license.bea>
<04-Dec-2008 12:13:58 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<04-Dec-2008 12:14:00 o'clock GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<05-Dec-2008 06:21:55 o'clock GMT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to t
he end of the classpath:
/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n-schemas.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_c
ommon.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wl
p/netuix_common.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/netuix_schemas.jar:/software/bea/wls/920/weblogic92/pla
tform/lib/wlp/netuix_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/wsrp-common.jar>
<05-Dec-2008 06:21:57 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Serve
r VM Version 1.5.0_07-b03 from Sun Microsystems Inc.>
<05-Dec-2008 06:22:04 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 Fri Jun 23 20:47:26 EDT 20
06 783464 >
<05-Dec-2008 06:22:23 o'clock GMT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /software/bea/wls/920/license.bea>
<05-Dec-2008 06:22:23 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<05-Dec-2008 06:22:23 o'clock GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
Thanks for your help.....

Problem connecting weblogic server to cluster

          Hi,
          I am very new to WL/JMS/JNDI/EJB etc. I downloaded WL6.0, and tried to make a cluster. I started a server on one machine as Administrative server, and created a cluster. Now, I started another server on a different machine, as a managed server by adding the following parameter at startup
          -Dweblogic.admin.host=http://admin-ipaddr:7001....,
          I get the following error
          Starting WebLogic Server ....
          <Thu Oct 19 14:37:37 PDT 2000> <Error> <Configuration Management> <Error connecting to admin server to bootstrap via URL: http://admin-ipaddr:7001/Bootstrap, user: system
          weblogic.management.configuration.ConfigurationException: Connection error: java.lang.SecurityException: Authentication for user system
          denied in realm weblogic
          at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:752)
          at weblogic.management.Admin.initialize(Admin.java:275)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:345)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
          at weblogic.Server.main(Server.java:32)
          >
          <Thu Oct 19 14:37:37 PDT 2000> <Emergency> <Server> <Unable to initialize the server: Fatal initialization exception
          Throwable: weblogic.management.configuration.ConfigurationException: connecting to http://admin-ipaddr:7001/Bootstrap - with nested exception:
          [weblogic.management.configuration.ConfigurationException: Connection error: java.lang.SecurityException: Authentication for user system denied in realm weblogic]
          weblogic.management.configuration.ConfigurationException: connecting to http://admin-ipaddr:7001/Bootstrap - with nested exception:
          [weblogic.management.configuration.ConfigurationException: Connection error: java.lang.SecurityException: Authentication for user syste
          m denied in realm weblogic]
          at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:803)
          at weblogic.management.Admin.initialize(Admin.java:275)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:345)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
          at weblogic.Server.main(Server.java:32)
          >
          I understand that all managed servers are supposed to use the same config file as the Admin server.
          Also, I am not clear about the domain parameter.... what should I pass for -Dweblogic.Domain=mydomain (this is what is there in the batch file that comes). Should I change this parameter for Managed servers, which points to Admin domain? If so, how do I do that?
          I am struck up on this. I'd greatly appreciate it some body could help me out.
          thanks a lot,
          Anil.


-Dweblogic.admin.host=admin-ipaddr:7001, you shouldn't specify protocol. Also please use beta newsgroup for 6.0 related questions.
          anil wrote:
          > Hi,
          > I am very new to WL/JMS/JNDI/EJB etc. I downloaded WL6.0, and tried to make a cluster. I started a server on one machine as Administrative server, and created a cluster. Now, I started another server on a different machine, as a managed server by adding the following parameter at startup
          > -Dweblogic.admin.host=http://admin-ipaddr:7001....,
          >
          > I get the following error
          > Starting WebLogic Server ....
          > <Thu Oct 19 14:37:37 PDT 2000> <Error> <Configuration Management> <Error connecting to admin server to bootstrap via URL: http://admin-ipaddr:7001/Bootstrap, user: system
          > weblogic.management.configuration.ConfigurationException: Connection error: java.lang.SecurityException: Authentication for user system
          > denied in realm weblogic
          > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:752)
          > at weblogic.management.Admin.initialize(Admin.java:275)
          > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:345)
          > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
          > at weblogic.Server.main(Server.java:32)
          > >
          > <Thu Oct 19 14:37:37 PDT 2000> <Emergency> <Server> <Unable to initialize the server: Fatal initialization exception
          > Throwable: weblogic.management.configuration.ConfigurationException: connecting to http://admin-ipaddr:7001/Bootstrap - with nested exception:
          > [weblogic.management.configuration.ConfigurationException: Connection error: java.lang.SecurityException: Authentication for user system denied in realm weblogic]
          > weblogic.management.configuration.ConfigurationException: connecting to http://admin-ipaddr:7001/Bootstrap - with nested exception:
          > [weblogic.management.configuration.ConfigurationException: Connection error: java.lang.SecurityException: Authentication for user syste
          > m denied in realm weblogic]
          > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:803)
          > at weblogic.management.Admin.initialize(Admin.java:275)
          > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:345)
          > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
          > at weblogic.Server.main(Server.java:32)
          > >
          > ***************************************************************************
          > I understand that all managed servers are supposed to use the same config file as the Admin server.
          >
          > Also, I am not clear about the domain parameter.... what should I pass for -Dweblogic.Domain=mydomain (this is what is there in the batch file that comes). Should I change this parameter for Managed servers, which points to Admin domain? If so, how do I do that?
          >
          > I am struck up on this. I'd greatly appreciate it some body could help me out.
          >
          > thanks a lot,
          > Anil.

Problem in JMS-Adapter with CharacterSet Websphere MQ

Hi,
we have the following scenario:
JMS -> PI -> File
We have a local Websphere MQ Queue Manager and the follwoing configuration in our sender adapter:
Transport-Protocol: WebSphere MQ (non JMS)
Message-Protocol: JMS 1.x
ConnectionFactory: com.ibm.mq.jms.MQQueueConnectionFactory
Java-class Queue: com.ibm.mq.jms.MQQueue
CCSID: 819
Transport: TCP/IP
JMS-conform: WebSphere MQ (non JMS)
In the local queue manager the messages (XML-Messages with header <?xml version="1.0" encoding="ISO-8859-1"?>) have characterSet 819 (ISO-8859-1). That's correct. You can open the files with XMLSpy and it works.
When we receive the messages by our JMS Sender Adapter all the character seems to be in UTF-8 and I don't know why. All the special characters are wrong cause the header of the XML-message shows ISO-8859-1 but all the signs are decoded in UTF-8.
In the other direction (JMS Receiver adapter, File -> PI - JMS) we have the same problem.
We create a ISO-8859-1 message in mapping (and it is really ISO-8859-1) and send it via JMS Receiver Adapter to the local message queue. But there the message arrives in UTF-8 encoding. I don't understand this.
Does anybody know what could be the cause for this?
Does the JMS adapter convert the messages from ISO-8859-1 into UTF-8?
Are there any parameters we have to set?
I hope anybody has an idea what's wrong.
Regards
Thorsten
Edited by: Thorsten Hautz on Oct 12, 2010 5:42 PM

Hi,
thanks a lot for your replies.
our driver settings are correct (as I can see).
I removed value 819 from CCSID, but we have the same effect.
The messages in the local queue manager are TextMessages in XML.
Does anybody know, if we need the standard modules (ConvertJMSMessageToBinary and ConvertBinaryToXMBMessage) in this case?
Is it possible to set the CCSID for the message payload anywhere in the configuration?
The CCSID in the Source tab doesn't have any influence to the encoding of the payload message, only to the header data.
Regards
Thorsten

About BEA WebLogic JMS on the cluster

Hi,
I have 3 files which together build in 1 EAR, then deploy on the cluster. I can see my message publish to the distributed topic successfully, but the listener process is not work. Could anyone give me a little clue.
// this one publish msg to the distributed topic.
import javax.naming.*;
import javax.jms.*;
import javax.rmi.PortableRemoteObject ;
import java.util.*;
public class PublishTopic {
public final static String JNDI_FACTORY = "weblogic.jndi.WLInitialContextFactory" ;
public final static String JMS_FACTORY = "weblogic.jws.jms.QueueConnectionFactory" ;
public final static String URL = "t3://localhost:7003,localhost:7005" ;
public final static String DIST_TOPIC = "dist_topic" ;
public String publishMsg(String s) throws Exception {
InitialContext ic = getInitialContext();
TopicConnectionFactory tcf = (TopicConnectionFactory) PortableRemoteObject.narrow
(ic.lookup(JMS_FACTORY),TopicConnectionFactory.class);
TopicConnection tc = tcf.createTopicConnection();
TopicSession ts = tc.createTopicSession(false,Session.AUTO_ACKNOWLEDGE);
Topic t = ts.createTopic(DIST_TOPIC);
TopicPublisher tpub = ts.createPublisher(t);
TextMessage msg = ts.createTextMessage(s);
tc.start();
tpub.publish(msg);
tc.close();
return "publish - : " + msg.getText();
public static InitialContext getInitialContext()throws NamingException {
Hashtable ht = new Hashtable();
ht.put(Context.INITIAL_CONTEXT_FACTORY, JNDI_FACTORY);
ht.put(Context.PROVIDER_URL,URL);
return new InitialContext(ht);
=================================================
// the listener one.
import javax.rmi.PortableRemoteObject ;
import java.util.HashMap;
import java.util.Date;
import javax.naming.*;
import javax.jms.*;
import java.io.*;
public class ListenMsg implements MessageListener {
private static HashMap hm ;
private static TopicConnection tcon ;
static {
// the coding inside static will process once every time
// class load. The code inside here should be
// 1. subscrib to the distributed topic
// 2. refresh the static var.
ListenMsg lm = new ListenMsg();
lm.retrieveDB();
lm.subscribTopic();
lm = null ;
public void onMessage(Message m) {
try {
PrintWriter p = new PrintWriter(new FileOutputStream
("C:/bea/user_projects/applications/TestJMS/JMSLog.txt",true));
p.println(new Date().toLocaleString());
p.println(((TextMessage)m).getText() + "\n");
// check to see the content of m then decide whether
// to call retrieveDB.
} catch (Exception e) {
} finally {
if (tcon != null)
try {
tcon.close();
} catch (Exception e) {}
private void retrieveDB () {
// connect to DB then select the allow/unallow-list.
private void subscribTopic(){
try {
InitialContext ic = PublishTopic.getInitialContext();
TopicConnectionFactory tcf = (TopicConnectionFactory) PortableRemoteObject.narrow
(ic.lookup(PublishTopic.JMS_FACTORY),TopicConnectionFactory.class);
tcon = tcf.createTopicConnection();
TopicSession tsess = tcon.createTopicSession(false,Session.AUTO_ACKNOWLEDGE);
// crateTopic doesn't actually create a new one but instead
// obtain a reference to the object which given name.
Topic t = tsess.createTopic(PublishTopic.DIST_TOPIC);
TopicSubscriber tsub = tsess.createSubscriber(t);
tsub.setMessageListener(this);
tcon.start();
} catch(JMSException je) {
je.printStackTrace();
} catch (NamingException ne) {
ne.printStackTrace();
} catch (Exception e) {
e.printStackTrace();
public boolean isAuthorized(String username, String servicename) {
// check against hm.
return true ;
===============================================
// the web service file.
public class TestPublish implements com.bea.jws.WebService
static final long serialVersionUID = 1L;
* @common:operation
public String sendMsg(String s) throws Exception {
String r = "";
try {
PublishTopic pt = new PublishTopic();
r = pt.publishMsg(s);
} catch(Exception e) {
e.printStackTrace();
throw e;
return r;
A big thanks in advance.
Tanin

Hi
Please verify that the listener points to the correct JNDI name
Do you see any error in the log ?
Jin

Problem Reading JMS queue

I have written a jms client to read a queue in weblogic. Specifically the wlai
event queue. However, I have tried to read other not-wli specific queues with
the same error. I get an access denied error even trying the system user!
I have even played with the ACL for the queue.
Anyone have any ideas?
Thanks

You need to add a 'browse' permission for your user to the ACL for that queue (or
the weblogic.jms ACL). It worked for me.
If you look in the stack, it mentions that your user was denied for the action
'browse'.
"Ryan Richards" <[email protected]> wrote:
>
Thanks for the help. I am not dequeueing any messages when I read them.
I have
also verified that there are messages on the queue. Here is the access
denied
message I am receiving.
Start server side stack trace: weblogic.jms.common.JMSSecurityException:
Access
denied to resource: type=<jms>, application=, destinationType=queue,
resource=RyanTestQueue,
action=browse at weblogic.jms.JMSService.checkPermission(JMSService.java:1065)
at weblogic.jms.JMSService.checkBrowsePermission(JMSService.java:1081)
at weblogic.jms.frontend.FESession.browserCreate(FESession.java:1100)
at weblogic.jms.frontend.FESession.invoke(FESession.java:2254) at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:602)
at weblogic.jms.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:152)
at weblogic.jms.dispatcher.DispatcherImpl.dispatchSyncFuture(DispatcherImpl.java:303)
at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:821)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:308)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
End server side stack trace
at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:109)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:127)
at weblogic.jms.dispatcher.DispatcherImpl_WLStub.dispatchSyncFuture(Unknown
Source) at weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSync(DispatcherWrapperState.java:282)
at weblogic.jms.client.JMSSession.createBackEndBrowser(JMSSession.java:1749)
at
weblogic.jms.client.JMSQueueBrowser.<init>(JMSQueueBrowser.java:46) at
weblogic.jms.client.JMSSession.createBrowser(JMSSession.java:1344)
at weblogic.jms.client.JMSSession.createBrowser(JMSSession.java:1324)
at Test.init(Test.java:41)
at Test.main(Test.java:115) Exception in thread "main"
Thanks for any help Ryan
"Karthik V" <[email protected]> wrote:
Check if you have selected the running server as target for your connection
factory and JMS server config (from admin console).
If still problem exists, can you post the exception and portion of your
client code causing the problem?
Remember one thing when trying to listen on any wli specific queues:
there
might be MDBs that consumes the message before your client code canread
from the queue. So avoid creating listeners on wli specific queues.(topic
is not a problem)
/k
"Ryan Richards" <[email protected]> wrote in message
news:[email protected]...
I have written a jms client to read a queue in weblogic. Specificallythe
wlai
event queue. However, I have tried to read other not-wli specific
queues
with
the same error. I get an access denied error even trying the systemuser!
I have even played with the ACL for the queue.
Anyone have any ideas?
Thanks

Problem instaling Subscriber in netware cluster

Hello.
I am using ZSM 7.0.1 installation program and trying to install only
subscriber functinality on a cluster OES Netware with Sp5.
The installation says it goes successful in the 2 logfiles that comes up
after the installation but when I try to offline and then online the
cluster-volume with the ZSM7 installed on it it goes into comatose because
the zfs.ncf is missing in the zenworks folder on the volume. I can not find
the file on any other volume on the server. I also have the ZDM701 installed
on the server before I install ZSM701 on it. The ZDM701 install was totaly
fine and it works great. The only ZDM701 services installed on the server on
the same volume is WOL, Import and Removal.
So my question is, how am I supose to get the right files and folders into
the cluster and to get it work. It should not be a problem.
Does anyone no what to do.
Thanks
Best regards Jonas Rydstrom

ZSM is supported on a cluster, you have to choose though to have either a
single cluster resource installed with ZSM or installing in on the
individual nodes. In this case it looks like Jonas installed ZSM on a
cluster resource, that's supposed to work, not sure why zfs.ncf isn't there.
Ron
"Jared Jennings" <[email protected]> wrote in message
news:Jv_4i.5587$[email protected]..
> Jonas Rydstrm,
>
>>OK, can you be more specific about what is not supported. I was succesful
>>installing both ZDM701 and ZSM701 Distributor, Subscriber and database on
>>a
>>single server to specific zenworks volume and the services on that server
>>seems to run fine.
>
> It is not supported to run individual subscriber objects on cluster nodes.
> The only portion of ZFS that is supported in a cluster environment is the
> distributor object.
>
> So, you are correct in that you can run ZFS, ZFD, and the database on a
> non-clustered server.
>
> You can also run ZFD on a clustered resource. The ZFD 7.0 with SP1 install
> correctly installed all the files to the clustered volume so that the
> services could load and fail-over with the information being consistent.
> All ZFD services load from \\clusteredvolume\public or
> \\clusteredvolume\system etc.
>
> ZFS supports clustered environments, but the clustered resource that loads
> the distributor code, cannot send distributions to subscriber objects
> representing nodes in the cluster, nor can it send to the clustered
> subscriber object that does exist and represents the clustered zfs
> resource.
>
> --
> Jared Jennings - Data Technique, Inc.
> Novell Support Forums Sysop
> My Blog and Wiki with Tips, Tricks, and Tutorials
> http://jaredjennings.org

Problem in JMS congiuration in cluster

Similar Messages

Maybe you are looking for