Active JMS Connections

Are Active JMS Connections as viewed through the console (by clicking on Monitor all Active JMS Connections... ) really active? These numbers never seem to decrease.
          Thanks,
          John

Which one are you talking about?
 JMSServer->Monitor Active JMS Servers, the connection field does change.
 Server->Monitoring->JMS->Monitor all Active JMS Connections, the table does
 reflect the current connections. This works on 6.1 sp2, I don't have other
 version handy to verify.
 .raja
 "John" <[email protected]> wrote in message
 news:[email protected]..
 > Are Active JMS Connections as viewed through the console (by clicking on
 Monitor all Active JMS Connections... ) really active? These numbers never
 seem to decrease.
 >
 > Thanks,
 > John

Similar Messages

Why do the number of active JMS connections increase?

Problem
- Number of active JMS connections and current JMS messages increases until the Weblogic instances crash with an OutOfMemory exception
Setup
- Weblogic v9.2.3, Cluster with 4 Nodes
- A JMS Message is sent from a MDB in Weblogic to a distributed queue which has a member on each of the 4 Weblogic nodes. The session is created as follows session = connection.createSession(false,Session.AUTO_ACKNOWLEDGE), the message delivery mode is set programmatically to persistent and the delivery mode override of the queue setup is set to persistent too
- Standalone JMS client processes: each one is attached to all 4 nodes. Each one uses a unique JMS message selector so that we have more than one queue consumer for one queue but every message is exactly dedicated to one queue consumer. We us weblogic.jar for the clients.
- Use of Weblogic auto reconnect feature. JMS client code:
Connection connection = this.connectionFactory.createQueueConnection();
final WLConnection wlconnection = (WLConnection)connection;
wlconnection.setReconnectPolicy(JMSConstants.RECONNECT_POLICY_ALL);
wlconnection.setTotalReconnectPeriodMillis(-1);
wlconnection.setReconnectBlockingMillis(-1);
Remarks and Questions
- There are no pending JMS messages which is good
- In our setup, each JMS client is connected to all 4 nodes as the messages are not distributed to all nodes: if a message is put to Queue A but the client is only connected to Queue B, the message is NOT transfered from Queue A to Queue B. We set the parameter "Forward Delay" to 5 seconds with no effects. Is this the normal behavior?
- Not all JMS clients are visible in the Weblogic console under JMS Services -> JMS Servers -> [Server] -> Monitoring -> Active Connections. Which one are visible? Which one are not visible? There are also clients where the number of connections is not zero but stays constant; we know that as several independent clients on different hosts are started and the IP adress is visible in the Weblogic console. Why....?
- What reasons can lead to increasing connections? Is this due to client or server problems? Do we have to acknowledge the message in the onMessage(Message) method of the client JMS consumer? So far as I know, we don't have to.
- Are the increasing number of current messages due to the increasing number of JMS connections?
- May the RECONNECT_POLICY_ALL policy produce this problem?
Any hint is appreciated.
Peter
Edited by: pkeller on 23.10.2008 17:08

To answer the question about the forwarding of messages from one queue to another myself: As mentioned at http://forums.bea.com/thread.jspa?threadID=400000611, the forwarding for queues does only work if all queue consumers are attached to the same queue. This means that our setup is OK.
But the main question is still unanswered: why do the number of active JMS connections increase? I forgot to mention that
- all messages arrive at the clients and that no exceptions are visible in the log
- if you kill the client, the connections are still visible in the Weblogic console!?
Please help as this problem is very urgent.
Peter
Edited by: pkeller on 24.10.2008 09:06
Edited by: pkeller on 24.10.2008 09:10

Why do JMS connections stay connected after Flex clients close?

Hello,
I am using AMF_Polling and the JMS Adapter to receive discardable messages on a topic from Fiorano JMS. It works very well except for one thing. When the Flex client goes away because the browser closed, the JMS connection to FIorano is still there. It seems to stay there for a very long time and may never timeout and go away.
Questions:
1. Is this normal behavior for the JMS adapter?
2. Is there a way to force these unused connections to close between the JMS server and the Flex JMS adapter?
3. Is the JMS adapter continuing to receive messages after the Flex client goes away?
4. If so, are messages stacking up in memory which will eventually fill up and cause problems?
Thanks,
Chris Shafer, George Weiss Associates

To answer the question about the forwarding of messages from one queue to another myself: As mentioned at http://forums.bea.com/thread.jspa?threadID=400000611, the forwarding for queues does only work if all queue consumers are attached to the same queue. This means that our setup is OK.
But the main question is still unanswered: why do the number of active JMS connections increase? I forgot to mention that
- all messages arrive at the clients and that no exceptions are visible in the log
- if you kill the client, the connections are still visible in the Weblogic console!?
Please help as this problem is very urgent.
Peter
Edited by: pkeller on 24.10.2008 09:06
Edited by: pkeller on 24.10.2008 09:10

WLS 8.1SP4 and the ever-increasing number of JMS connections

We are running a CRM application on a BEA WebLogic 8.1SP4 cluster and we are experiencing some regular performance problems.
When looking at the active JMS connections we see that they can increase till 800 current connections until the application slows down. It takes a very long time to generate the active JMS connections overview
The current number of connections is always nearly identical to the connections high value.
Do you maybe recognize this kind of behavior? Your comments, advice or suggestions are very much appreciated.
With kind regards,
Fred

We are running a CRM application on a BEA WebLogic 8.1SP4 cluster and we are experiencing some regular performance problems.
When looking at the active JMS connections we see that they can increase till 800 current connections until the application slows down. It takes a very long time to generate the active JMS connections overview
The current number of connections is always nearly identical to the connections high value.
Do you maybe recognize this kind of behavior? Your comments, advice or suggestions are very much appreciated.
With kind regards,
Fred

Release jms connection doesn?t release.

 Hi All,
 Environment: WLS 7.0sp2, JMS: weblogic JMS JMSJDBCStore, database oracle9
 We invoke the following sendEvent code from a worker thread invoked by a scheduler
 that was started in a servlet init method (this worker thread code is wrapped
 with a user tx).
 The topic’s MDB is getting the message OK, however the number of connection in
 the monitor (mydomain> JMS Servers> NomJMSServer> Active JMS Servers) keep growing.
 As you can see we are releasing the connection in a finally block. Can anybody
 explain it.?
 Second question: Should we cache the jms session? If the answer is yes, can they
 expire (close), how do we check if they are still valid?
 Thanks
 public String sendEvent(SyncOutput event)
 String retval = null;
 try
 init();
 topicPublisher.publish( formatMessage(event) );
 catch (Exception e)
 logger().debug("cannot send event", e);
 }finally{
 release();
 return retval;
 private Message formatMessage(SyncOutput output)
 throws JMSException, IOException
 BytesMessage message = topicSession.createBytesMessage();
 GZIPOutputStream gzip = new GZIPOutputStream(new BytesMessageOutputStream(message));
 output.flush(new OutputStreamWriter(gzip));
 gzip.close();
 return message;
 private void init()
 throws Exception
 InitialContext context = new InitialContext();
 TopicConnectionFactory conFactory =
 (TopicConnectionFactory) context.lookup(JMSConfig.get(JMSConfig.FACTORY));
 topicConnection = conFactory.createTopicConnection();
 topicSession = topicConnection.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
 Topic topic = (Topic) context.lookup( this.jndiName );
 topicPublisher = topicSession.createPublisher(topic);
 topicPublisher.setDeliveryMode( DeliveryMode.PERSISTENT );
 private void release()
 try{
 if (topicPublisher != null){
 topicPublisher.close();
 topicPublisher = null;
 if (topicSession != null){
 topicSession.close();
 topicSession = null;
 if (topicConnection != null) {
 topicConnection.close();
 topicConnection = null;
 System.gc();
 }catch(Exception ignore){
 ignore.printStackTrace();


 We found the problem, it was a bug in our code. Thanks for your help.
 Tom Barnes <[email protected]> wrote:
 >Its possible the monitor has a bug, but in your case, since
 >you now only create one connection how could the
 >connection count keep growing?
 >
 >Perhaps the MDB app or MDB container is failing in some
 >unexpected way and not
 >closing its connection before attempting to create a new one?
 >Check your log for warnings and error messages, and
 >consider encapsulating your onMessage() code with a
 >try { /* all onMessage code */ }
 >catch (Throwable t) { t.printStackTrace(); rethrow}
 >
 >Meir wrote:
 >> Is it possible that the monitor has a bug? I changed my code to cache
 >the topic
 >> session and topic publisher, so I always use the same one (they are
 >static members
 >> of the class) but this didn't change the result that I'm seeing in
 >the monitor
 >> - the number of connections still keep growing.
 >> Could it be TX related weirdness (note we set the factory "User Transactions
 >Enabled"
 >> attribute to true)?
 >>
 >>
 >> "Meir" <[email protected]> wrote:
 >>
 >>>Thanks for your quick response.
 >>>I cahnged the code to catch throwable (both the open and close connection
 >>>are
 >>>in the try/catch block) and I don't see any problems.
 >>>Do you have any other suggestions? Do you need more data?
 >>>
 >>>
 >>>Tom Barnes <[email protected]> wrote:
 >>>
 >>>>
 >>>>Meir wrote:
 >>>>
 >>>>
 >>>>>Hi All,
 >>>>>
 >>>>>Environment: WLS 7.0sp2, JMS: weblogic JMS JMSJDBCStore, database
 >>>>
 >>>>oracle9
 >>>>
 >>>>>We invoke the following sendEvent code from a worker thread invoked
 >>>>
 >>>>by a scheduler
 >>>>
 >>>>>that was started in a servlet init method (this worker thread code
 >>>>
 >>>>is wrapped
 >>>>
 >>>>>with a user tx).
 >>>>>The topic’s MDB is getting the message OK, however the number of
 >connection
 >>>>
 >>>>in
 >>>>
 >>>>>the monitor (mydomain> JMS Servers> NomJMSServer> Active JMS Servers)
 >>>>
 >>>>keep growing.
 >>>>
 >>>>>As you can see we are releasing the connection in a finally block.
 >>>>
 >>>>Can anybody
 >>>>
 >>>>>explain it.?
 >>>>
 >>>>Perhaps you are throwing a RuntimeException or Error without
 >>>>catching it. Put trace statements before the connection
 >>>>create and right before and after the "connection.close()" to
 >>>>verify.
 >>>>
 >>>>Note that since you are closing the connection, there is no need
 >>>>to close the publisher or session.
 >>>>
 >>>>
 >>>>>Second question: Should we cache the jms session?
 >>>>
 >>>>For performance reasons, yes. But if your performance
 >>>>is fine, you don't need to. Since you are doing
 >>>>a "zip" per message, which is expensive in terms of CPU,
 >>>>the overhead of creating a session per
 >>>>message may be negligable in comparison.
 >>>>
 >>>>
 >>>>>If the answer is yes, can they
 >>>>>expire (close),
 >>>>
 >>>>If the host JMS server is adminstratively shutdown
 >>>>or the host JVM for the JMS server crashes...
 >>>>
 >>>>
 >>>>>how do we check if they are still valid?
 >>>>
 >>>>If it fails when you use it, it ain't valid. ;-)
 >>>>
 >>>>You can detect failures pro-actively by registering
 >>>>a connection onException listerner
 >>>>and a session onException listener.
 >>>>
 >>>>Note that WL 8.1 has built in connection/session
 >>>>pooling, and the JMS Performance Guide white-paper's
 >>>>appendix has sample code for writing your own pool for
 >>>>previous WL versions. There is a linke to
 >>>>the white-paper here:
 >>>>
 >>>>http://dev2dev.bea.com/technologies/jms/index.jsp
 >>>>
 >>>>
 >>>>>Thanks
 >>>>>
 >>>>>
 >>>>> public String sendEvent(SyncOutput event)
 >>>>> {
 >>>>> String retval = null;
 >>>>> try
 >>>>> {
 >>>>> init();
 >>>>> topicPublisher.publish( formatMessage(event) );
 >>>>> }
 >>>>> catch (Exception e)
 >>>>> {
 >>>>> logger().debug("cannot send event", e);
 >>>>> }finally{
 >>>>> release();
 >>>>> }
 >>>>> return retval;
 >>>>> }
 >>>>>
 >>>>> private Message formatMessage(SyncOutput output)
 >>>>> throws JMSException, IOException
 >>>>> {
 >>>>> BytesMessage message = topicSession.createBytesMessage();
 >>>>> GZIPOutputStream gzip = new GZIPOutputStream(new BytesMessageOutputStream(message));
 >>>>> output.flush(new OutputStreamWriter(gzip));
 >>>>> gzip.close();
 >>>>> return message;
 >>>>> }
 >>>>>
 >>>>> private void init()
 >>>>> throws Exception
 >>>>> {
 >>>>> InitialContext context = new InitialContext();
 >>>>> TopicConnectionFactory conFactory =
 >>>>> (TopicConnectionFactory) context.lookup(JMSConfig.get(JMSConfig.FACTORY));
 >>>>> topicConnection = conFactory.createTopicConnection();
 >>>>> topicSession = topicConnection.createTopicSession(false,
 >Session.AUTO_ACKNOWLEDGE);
 >>>>>
 >>>>> Topic topic = (Topic) context.lookup( this.jndiName );
 >>>>> topicPublisher = topicSession.createPublisher(topic);
 >>>>> topicPublisher.setDeliveryMode( DeliveryMode.PERSISTENT );
 >>>>> }
 >>>>>
 >>>>> private void release()
 >>>>> {
 >>>>> try{
 >>>>> if (topicPublisher != null){
 >>>>> topicPublisher.close();
 >>>>> topicPublisher = null;
 >>>>> }
 >>>>>
 >>>>> if (topicSession != null){
 >>>>> topicSession.close();
 >>>>> topicSession = null;
 >>>>> }
 >>>>>
 >>>>> if (topicConnection != null) {
 >>>>> topicConnection.close();
 >>>>> topicConnection = null;
 >>>>> }
 >>>>>
 >>>>> System.gc();
 >>>>> }catch(Exception ignore){
 >>>>> ignore.printStackTrace();
 >>>>> }
 >>>>> }
 >>>>>
 >>>>
 >>
 >

JMS Connection Factory jms/QueueConnectionFactory could not be found

Hi,
Previously, i tried to extend weblogic domain "oim_domain" that only configured for OIM, and integrate the OIM with OAM 11g.
The integration was failed, because all users cannot login to OAM login page (using Active Directory authentication), so i rolled back all configuration by copying MW_HOME i've backed-up before extend the weblogic domain.
When i start the OIM after rolled back, i've found an error message as follow :
<May 16, 2013 11:38:15 AM WIT> <Error> <oracle.iam.platform.async> <IAM-0050009> <Async Service initialization failed because JMS Connection Factory jms/Queu
eConnectionFactory could not be found. Please check that a JMS Connection Factory with JNDI Name jms/QueueConnectionFactory is present in the Application Ser
ver.>
<May 16, 2013 11:38:15 AM WIT> <Error> <oracle.iam.platform.async> <IAM-0050010> <Error Trace Follows
javax.naming.NamingException: String index out of range: -1
at weblogic.jndi.Environment.getContext(Environment.java:308)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
and this error message :
<May 16, 2013 11:38:15 AM WIT> <Warning> <oracle.iam.platform.utils> <IAM-0070016> <An error occurred while initializing service : oracle.iam.platform.async.
AsyncService>
<May 16, 2013 11:38:15 AM WIT> <Warning> <oracle.iam.platform.utils> <IAM-0070016> <An error occurred while initializing service : {0}
javax.naming.NamingException: String index out of range: -1
at weblogic.jndi.Environment.getContext(Environment.java:308)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
Please help.
Best Regards,
Heri

I have the same error!!! Do you manage to solve it?

Weblogic jms connection problem

Hi All,
My jms bpel process listening on jms Queue. If I deploy bpel process first time I am not getting any jms connection problem with weblogic , but if redploy I am getting jms conneciton problem. saying
Adapter_start: Jms Adapter started
<2005-12-07 10:19:20,044> <ERROR> <default.collaxa.cube.activation> <JMSAdapter::Inbound> Error whil
e creating managed connection:
<2005-12-07 10:19:20,044> <ERROR> <default.collaxa.cube.activation> <JMSAdapter::Inbound>
ORABPEL-12141
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor BP
ELJMS neither through JNDI nor instantiate it as a Java class
Please examine the log file to determine the problem.
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnection
FactoryFactory.java:156)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getQueueConnectionFactory(JMSConne
ctionFactoryFactory.java:95)
at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:143)
at oracle.tip.adapter.jms.JMS.JMSConnection.<init>(JMSConnection.java:102)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionF
actory.java:355)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createDefaultConnection(JmsManagedConn
ectionFactory.java:346)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionF
actory.java:309)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConn
ectionFactory.java:99)
at com.evermind.server.connector.ApplicationConnectionManager.createManagedConnection(Applic
ationConnectionManager.java:564)
at oracle.j2ee.connector.ConnectionPoolImpl.createManagedConnection(ConnectionPoolImpl.java:
Work around is I need to restart the BPEL server.
Is there any permanant solution for this, Please suggest.
Thanks,
Srini

srini,
see this thread
JMS Connection
thanks,
-Ng.

Problem with transacted JMS connection factory and transaction timeouts

          We encountered an interesting problem using transacted JMS connection factories.
          An EJB starts a container managed transaction and tries to validate a credit card
          before creating some information to a database for the user, in case of success
          an SMS is sent to the user via the transacted JMS queue. If the credit card authentications
          duration is about the same as the transactions timeout (in this case the default
          30 seconds) sometimes the database inserts is committed but the JMS insert is
          rollbacked. How can this be?
          If the authorization duration is much longer than 30 seconds everything works
          fine (both database and JMS inserts rollbacked), the same is true if a rollback
          is insured by calling EJBContext.setRollbackOnly(). The problem thus occurs only
          if the duration is approximately the same as the transaction timeout, it appears
          that the database insert is not timeouted but the JMS insert is. How can this
          be if they are both participating in the same transaction.
          The JMSConnectionFactory used is a Connection factory with XA-enabled. The result
          is the same also with the default "javax.jms.QueueConnectionFactory" and if we
          configure our own factory with user transactions enabled.
          Any help appreciated!


Tomas Granö wrote:
          > We encountered an interesting problem using transacted JMS connection factories.
          > An EJB starts a container managed transaction and tries to validate a credit card
          > before creating some information to a database for the user, in case of success
          > an SMS is sent to the user via the transacted JMS queue. If the credit card authentications
          > duration is about the same as the transactions timeout (in this case the default
          > 30 seconds) sometimes the database inserts is committed but the JMS insert is
          > rollbacked. How can this be?
          It should not be.
          >
          > If the authorization duration is much longer than 30 seconds everything works
          > fine (both database and JMS inserts rollbacked), the same is true if a rollback
          > is insured by calling EJBContext.setRollbackOnly(). The problem thus occurs only
          > if the duration is approximately the same as the transaction timeout, it appears
          > that the database insert is not timeouted but the JMS insert is. How can this
          > be if they are both participating in the same transaction.
          >
          > The JMSConnectionFactory used is a Connection factory with XA-enabled. The result
          > is the same also with the default "javax.jms.QueueConnectionFactory" and if we
          > configure our own factory with user transactions enabled.
          >
          > Any help appreciated!
          Make sure that your session is not "transacted". In other words,
          the first parameter to createSession() must be false. There is an
          unfortunate name re-use here. If a session is "transacted", it
          maintains an independent "inner transaction" independent of the
          outer transaction. From the above description, it seems unlikely
          that your application has this wrong, as you say that
          "setRollbackOnly" works - but please check anyway.
          Make sure that you are using a true XA capable driver and database
          (XA "emulation" may not suffice)
          Beyond the above, I do not see what can be going wrong. You
          may want to try posting to the transactions and jdbc newsgroups. Note
          that JMS is appears to be exhibiting the correct behavior, but the
          JDBC operation is not. The JDBC operation appears to have
          its timeout independent of the transaction monitor's timeout.
          Tom

I am not able to create a JMS connection from a custom component in UCM

I am trying to create a custom component which makes a JMS connection and inserts messages in JMS Queue.
THe JMS server is hosted on Weblogic Application Server.
When the code runs I am getting the factory object and the queue object.
But when I try to get a connection it throws an error as pasted below.
WHen I googled the same error It has shown a simliar problem in TOmcat in sun thread
It said two jar files xerces.jar and xml-apis.jar are obsolete.
I replaced with the new version.
still the same problem occurred
Please help
Pasting the code and exception here
Code __________________________________________
import java.util.Date;
import java.util.Hashtable;
import javax.jms.*;
import javax.naming.*;
import weblogic.jms.client.WLConnectionImpl;
import weblogic.jms.extensions.*;
import javax.rmi.PortableRemoteObject;
public class SimpleProducer {
public static void drive() {
final int NUM_MSGS;
 NUM_MSGS = 93;
Context jndiContext = null;
Hashtable<String, String> ht;
 ht = new Hashtable<String, String>();
 ht.put(Context.INITIAL_CONTEXT_FACTORY,
 "weblogic.jndi.WLInitialContextFactory");
 ht.put(Context.PROVIDER_URL, "t3://punitp52975d:7001");
try {
 jndiContext = new InitialContext(ht);
} catch (NamingException e) {
System.out.println("Could not create JNDI API context: " +
e.toString());
System.exit(1);
ConnectionFactory connectionFactory = null;
Destination dest = null;
try {
 Object home = jndiContext.lookup("CNFT"); // where iiopTestDS is jndi name for my DataSource.
connectionFactory =(ConnectionFactory)PortableRemoteObject.narrow(home , ConnectionFactory.class);
 Object home1 = jndiContext.lookup("QUEUE2"); // where iiopTestDS is jndi name for my DataSource.
dest =(Destination)PortableRemoteObject.narrow(home1 , Destination.class);
 /*connectionFactory = (ConnectionFactory) jndiContext.lookup(
"CNFT");
dest = (Destination) jndiContext.lookup("QUEUE2");
System.out.println("connectionFactory,dest "+connectionFactory+dest);*/
} catch (Exception e) {
System.out.println("JNDI API lookup failed: " + e.toString());
e.printStackTrace();
System.exit(1);
//WLConnectionImpl connection = null;
WLConnection connection = null;
WLMessageProducer producer = null;
try {
 System.out.println("Getting Connection "+(WLConnection) connectionFactory.createConnection());
//connection = (WLConnection) connectionFactory.createConnection();
 System.out.println("Connection created");
WLSession session =
(WLSession) connection.createSession(false, Session.CLIENT_ACKNOWLEDGE);
producer = (WLMessageProducer) session.createProducer(dest);
WLMessage message = (WLMessage) session.createTextMessage();
//TextMessage message = session.createTextMessage();
for (int i = 91; i < NUM_MSGS; i++) {
((TextMessage) message).setText("This is message " + (i + 1));
Long l = new Date().getTime();
message.setLongProperty("ReleasedDate",l );
System.out.println("Sending message: " + ((TextMessage) message).getText());
producer.send(message);
producer.send(session.createMessage());
} catch (Exception e) {
System.out.println("Exception occurred: " + e.toString());
} catch (Throwable et) {
System.out.println("Exception occurred: " + et.toString());
et.printStackTrace();
finally {
if (connection != null) {
try {
connection.close();
} catch (Exception e) {
 System.out.println("*************Instantiating Producer***************");
Exception_________________________________________________________________
Exception occurred: java.lang.NoSuchMethodError: javax.xml.parsers.SAXParserFactory.getSchema()Ljavax/xml/validation/Schema;
java.lang.NoSuchMethodError: javax.xml.parsers.SAXParserFactory.getSchema()Ljavax/xml/validation/Schema;
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.<init>(SAXParserImpl.java:124)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl.newSAXParserImpl(SAXParserFactoryImpl.java:115)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl.setFeature(SAXParserFactoryImpl.java:143)
at weblogic.xml.jaxp.WebLogicSAXParserFactory.<init>(WebLogicSAXParserFactory.java:62)
at weblogic.rmi.internal.wls.WLSRMIEnvironment.getSAXParser(WLSRMIEnvironment.java:136)
at weblogic.rmi.internal.DescriptorManager.getDescriptorAsMap(DescriptorManager.java:170)
at weblogic.rmi.internal.DescriptorManager.getDescriptorAsMap(DescriptorManager.java:159)
at weblogic.rmi.internal.DescriptorManager.createRuntimeDescriptor(DescriptorManager.java:104)
at weblogic.rmi.internal.DescriptorManager.getBasicRuntimeDescriptor(DescriptorManager.java:85)
at weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManager.java:51)
at weblogic.rmi.internal.DescriptorManager.getDescriptor(DescriptorManager.java:37)
at weblogic.rmi.internal.OIDManager.makeServerReference(OIDManager.java:194)
at weblogic.rmi.internal.OIDManager.getReplacement(OIDManager.java:175)
at weblogic.rmi.utils.io.RemoteObjectReplacer.replaceRemote(RemoteObjectReplacer.java:120)
at weblogic.rmi.utils.io.RemoteObjectReplacer.replaceObject(RemoteObjectReplacer.java:103)
at weblogic.rmi.extensions.server.ServerHelper.exportObject(ServerHelper.java:223)
at weblogic.rmi.internal.OIDManager.initializeDGCServer(OIDManager.java:231)
at weblogic.rmi.internal.OIDManager.getReplacement(OIDManager.java:144)
at weblogic.rmi.utils.io.RemoteObjectReplacer.replaceRemote(RemoteObjectReplacer.java:120)
at weblogic.rmi.utils.io.RemoteObjectReplacer.replaceObject(RemoteObjectReplacer.java:103)
at weblogic.rmi.extensions.server.ServerHelper.exportObject(ServerHelper.java:223)
at weblogic.corba.server.naming.ReferenceHelperImpl.exportObject(ReferenceHelperImpl.java:233)
at weblogic.rmi.extensions.PortableRemoteObject.exportObject(PortableRemoteObject.java:34)
at weblogic.messaging.dispatcher.DispatcherImpl.export(DispatcherImpl.java:85)

This is probably related to this other issue http://www.adobeforums.com/webx/.59b7fbab/0.
Jasmin

Error when creating a new JMS connection factory in GlassFish V3 b57

When I use the admin console and try to create a new JMS connection factory in GlassFish V3 b57, the operation fails with the error message
An error has occurred: Can't find ConfigModel.Property for attr -connection-validation-required on interface com.sun.enterprise.config.serverbeans.ConnectorConnectionPool
Should I better report this in the GlassFish news forum (http://forums.java.net/jive/forum.jspa?forumID=56&start=0)?
p.s. I launch the admin console from within NetBeans 6.7.1 (the server started before the IDE). WIth version b 56, creating a JMS connection factory worked fine.
Best regards,
Michael Justin

This bug does not apear in the nightly build (b58) now so everything looks fine again.
Greetings,
Michael

My ipod touch says "activation required, connect to itunes" i restore it on my itunes and it seems to be working, after i tried connecting to my wifi but no luck, i reset it and the same thing happens all over again. Help!

my ipod touch says "activation required, Connect to itunes" i restored it with on my itunes and it seems to be working again, after i tried connecting to my wifi with no luck i reset it, and again it pops back "activation required, connect to itunes" i restored again, its a non ending cycle, and it makes no sense having my ipod and i cannot connect to the internet with it, can someone please help with this issue?

Maybe here:
Restore loop (being prompted to restore again after a restore successfully completes)
Troubleshoot your USB connection. If the issue persists, out-of-date or incorrectly configured third-party security software may be causing this issue. Please follow Troubleshooting security software issues. .
Next would be to make an appointment at the Genius Bar of an Apple store.

How to find out status of JMS Connection ( connected or closed )

Is there a way to find out the status ( connected or closed ) of JMS Connection at any point of time . JMS Connection interface doesn't seem to have any isAlive( ) sort of method ?
I'm using a shared instance JMS Connection and if someone calls connection.close() on this instance the code starts flunking.

Crap isn't it! Would also be useful for creating a JMS connection pool, or for testing connections that stay open for time time and may be closed by network problems etc.
I can think of a couple of options (haven't tested them so may be flawed)
1. Extend your vendors QueueConnectionFactory object to return a decorated Connection, which adds an isAlive() method and records internally whether someone has called .close(); This could be tricky if you use JNDI to retrieve the QCF - you'll have to bind your custom QCF and remove the old one. Much easier if you use a bean factory like Spring.
2. You may be able to do this with the underlying vendor's API. If you choose this option put all the vendor specific code in a separate class and abstract it behind an interface. In future if you change to a JMS provider that does not support this feature, you can always change your isAlive() method return true no matter what;
3. Wrap the JMS sender / receiver in an Adapter class. The adapter delegates send / receive methods to the wrapped class, but if it receives a JMS exception will reconnect and try again. A second JMS Exceptions should be thrown back to the client. All your client code sees is a single send / receive method as if it was using a normal JMS sender / receiver.

Can anyone help me ? my iphone 3gs keeps displaying needs activation and connect to itunes when i do this nothing happens but the phone works fine but as soon as i disconect the phone it displays the same message over again and wont let me go any further

my phone has just suddenly stopped working today was fine this morning then suddenly showed a message saying needs activating and connect to i tunes . i connected it to itunes and nothing happened but phone started to work fine so i disconected it from the laptop it worked fine untill it went to lock then showed the same message again .please can anybody help as i am ready tear my hair out!

In settings>general> cellular do you have it turned ON?

Error in looking up the JMS Connection Factory

 Hi,
 I am using weblogic6.1. I created a JMS Connection factory from administrator
 console with the name QueueConnectionFactory..But when i restart the server and
 try to look up that factory its giving an NameNotFoundException...This is the
 entry of the factory in config.xml
 <JMSConnectionFactory JNDIName="QueueConnectionFactory"
 Name="QueueConnectionFactory" Targets="myserver"/>
 But if i change reapply the target server to myserver from admin console whenever
 restart the server it works fine..
 I dont know where is the problem..Can u please update me on the problem if u people
 have any idea.
 The trace of the exceptions i got is as below:
 java.rmi.RemoteException: javax.naming.NameNotFoundException: Unable to
 resolve QueueConnectionFactory. Resolved
 : '' Unresolved:'QueueConnectionFactory' ; remaining name ''
 java.rmi.RemoteException: javax.naming.NameNotFoundException: Unable to resolve
 QueueConnectionFactory. Resolved: '' Unr
 esolved:'QueueConnectionFactory' ; remaining name ''
 Thanx
 Regards,
 Narayan


 Hi Zach,
 No, I dont think ur interpretation is right..Once the entry corresponding
 to JMS Connection Factory is there in config.xml, the server should automatically
 bind it at the time of booting.. right. Why should this administrator server come
 into the picture.
 Thanx
 "Zach" <[email protected]> wrote:
 >Don't know. Sounds like the admin server is not notifying JMS of the
 >changes under certain situations. You might post in the management.console
 >newsgroup.
 >
 >_sjz.
 >
 >"Narayan" <[email protected]> wrote in message
 >news:[email protected]...
 >>
 >> Hi,
 >> I am using weblogic6.1. I created a JMS Connection factory from
 >administrator
 >> console with the name QueueConnectionFactory..But when i restart the
 >server and
 >> try to look up that factory its giving an NameNotFoundException...This
 >is
 >the
 >> entry of the factory in config.xml
 >>
 >> <JMSConnectionFactory JNDIName="QueueConnectionFactory"
 >> Name="QueueConnectionFactory" Targets="myserver"/>
 >> But if i change reapply the target server to myserver from admin console
 >whenever
 >> restart the server it works fine..
 >> I dont know where is the problem..Can u please update me on the problem
 >if
 >u people
 >> have any idea.
 >> The trace of the exceptions i got is as below:
 >> ****************
 >> java.rmi.RemoteException: javax.naming.NameNotFoundException:
 >Unable to
 >> resolve QueueConnectionFactory. Resolved
 >> : '' Unresolved:'QueueConnectionFactory' ; remaining name ''
 >> java.rmi.RemoteException: javax.naming.NameNotFoundException: Unable
 >to
 >resolve
 >> QueueConnectionFactory. Resolved: '' Unr
 >> esolved:'QueueConnectionFactory' ; remaining name ''
 >>
 >> **********************
 >>
 >> Thanx
 >> Regards,
 >> Narayan
 >>
 >>
 >
 >

JMS Adapter (for DI) does not allow passing username and password to JMS connection

Post Author: PLed76
CA Forum: Data Integration
JMS Adapter (for DI) does not allow passing username and password to JMS connection. It has those fields only for MSMQ. Our Production environment does not allow us to connect to JMS (we use Tibco EMS) anonymously, so it prevents us from use of Data Integrator. Is there any way to pass those params, or obtain the correct version of JMS Adapter, or obtain source codes of the JMS Adapter so we can correct them ourselves (we can send you the corrected sources back) ? Thanks in advance for any help. (PL)ed76 Renaissance Capital

Bump - Were having the same issue.
Has anyone found a way to connect to Tibco with a user/pwd?
Version 14.0.297.

Active JMS Connections

Similar Messages

Maybe you are looking for