JMS- Iplanet 6.0 connection.

Hi,
I'm running iPlanet 6.0 WebServer and SwiftMQ router for JMS connectivity. Both the versions are running on JDK1.3.1, now when the JDK version is changed in iPlanet to JDK1.4.2, the webserver & Messaging router are unable to communicate. I'm unable to guess anything with the error messages thrown.
Kindly help. The swiftMQ Router needs to be in JDK1.3.1, since it requires a license purchase in the later versions.
Thanks in advance.

Hi,
I found the issue. The code was having traces of JVM Timestamp. Hence I changed them to System Timestamp.
Thanks

Similar Messages

  • JMS Exception - unable to connect to the JMS destination

    Hi,
    I've configured WebLogic10R3 Cluster with one Admin Server and 2 Managed Servers.
    I deployed the application to the Cluster. (Ie. both Managed 1 and Managed Server 2.)
    I am geeting the following JMS destination not found exception while starting the Second Managed Server.
    There are no errors occurred in the First Managed Server.
    {color:#ff0000}<Warning> <EJB> <BEA-010061>
    <The Message-Driven EJB: SysAuditLogger is unable to connect to the JMS destination: topic/efpAuditTopic.
    The Error was: weblogic.jms.common.JMSException: could not find Server efpserver_man2
    Nested exception: weblogic.jms.common.JMSException: could not find Server efpserver_man2
    Nested exception: weblogic.jms.common.JMSException: could not find Server efpserver_man2
    Nested exception: weblogic.jms.common.JMSException: could not find Server efpserver_man2
    Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server efpserver_man2
    Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:efpserver_man2.
    Resolved 'weblogic .messaging.dispatcher'; remaining name 'S:efpserver_man2>{color}
    Configuration Details:
    ##config.xml:
    <?xml version='1.0' encoding='UTF-8'?>
    <domain xmlns="http://www.bea.com/ns/weblogic/920/domain" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90/security/wls [http://www.bea.com/ns/weblogic/90/security/wls.xsd] [http://www.bea.com/ns/weblogic/920/domain] [http://www.bea.com/ns/weblogic/920/domain.xsd] [http://www.bea.com/ns/weblogic/90/security/xacml] [http://www.bea.com/ns/weblogic/90/security/xacml.xsd] [http://www.bea.com/ns/weblogic/90/security] [http://www.bea.com/ns/weblogic/90/security.xsd]">
    <name>efpdomain</name>
    <domain-version>10.3.0.0</domain-version>
    <security-configuration>
    <name>efpdomain</name>
    <realm>
    <sec:authentication-provider xsi:type="wls:default-authenticatorType"></sec:authentication-provider>
    <sec:authentication-provider xsi:type="wls:default-identity-asserterType">
    <sec:active-type>AuthenticatedUser</sec:active-type>
    </sec:authentication-provider>
    <sec:role-mapper xmlns:xac="http://www.bea.com/ns/weblogic/90/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
    <sec:authorizer xmlns:xac="http://www.bea.com/ns/weblogic/90/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
    <sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
    <sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
    <sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
    <sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
    <sec:name>myrealm</sec:name>
    </realm>
    <default-realm>myrealm</default-realm>
    <credential-encrypted>{3DES}hcdd+yZGXk5DHgRKqCM7E86l4+VxPcZ9Ut7rB6WaXqMyvbtDjDUKNCKbMQdCN/BEYCv5E0N4Hms9kntfqhaduDO1WGMtbmJL</credential-encrypted>
    <node-manager-username>weblogic</node-manager-username>
    <node-manager-password-encrypted>{3DES}Q2xO0EiChbay/HkRiorTjg==</node-manager-password-encrypted>
    </security-configuration>
    <server>
    <name>AdminServer</name>
    <listen-address>192.168.12.240</listen-address>
    </server>
    <server>
    <name>efpserver_man1</name>
    <listen-port>8011</listen-port>
    <cluster>efpcluster</cluster>
    <listen-address>192.168.12.240</listen-address>
    <xml-registry>XMLEFP</xml-registry>
    <jta-migratable-target>
    <user-preferred-server>efpserver_man1</user-preferred-server>
    <cluster>efpcluster</cluster>
    </jta-migratable-target>
    </server>
    <server>
    <name>efpserver_man2</name>
    <listen-port>8012</listen-port>
    <cluster>efpcluster</cluster>
    <listen-address>192.168.12.240</listen-address>
    <xml-registry>XMLEFP</xml-registry>
    <jta-migratable-target>
    <user-preferred-server>efpserver_man2</user-preferred-server>
    <cluster>efpcluster</cluster>
    </jta-migratable-target>
    </server>
    <cluster>
    <name>efpcluster</name>
    <cluster-address>192.168.12.240:8011,192.168.12.240:8012</cluster-address>
    <multicast-address>239.192.0.0</multicast-address>
    </cluster>
    <embedded-ldap>
    <name>efpdomain</name>
    <credential-encrypted>{3DES}q/XQGirHcAcgi4iwPiXIkRHP8xte4xVBgJwjM+qMwbk=</credential-encrypted>
    </embedded-ldap>
    <configuration-version>10.3.0.0</configuration-version>
    <app-deployment>
    <name>efp</name>
    <target>efpcluster</target>
    <module-type>ear</module-type>
    <source-path>applications\efp.ear</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    </app-deployment>
    <xml-registry>
    <name>XMLEFP</name>
    <document-builder-factory>weblogic.apache.xerces.jaxp.DocumentBuilderFactoryImpl</document-builder-factory>
    <sax-parser-factory>weblogic.apache.xerces.jaxp.SAXParserFactoryImpl</sax-parser-factory>
    <transformer-factory>weblogic.apache.xalan.processor.TransformerFactoryImpl</transformer-factory>
    </xml-registry>
    <jms-server>
    <name>eFpJMSServer</name>
    <target>efpserver_man1 (migratable)</target>
    <persistent-store>eFpJMSJDBCStore</persistent-store>
    </jms-server>
    <jms-server>
    <name>eFpJMSServer2</name>
    <target>efpserver_man2 (migratable)</target>
    <persistent-store>eFpJMSJDBCStore2</persistent-store>
    </jms-server>
    <migratable-target>
    <name>efpserver_man1 (migratable)</name>
    <notes>繧ｷ繧ｹ繝・Β逕滓・縺ｫ繧医ｋ繝・ヵ繧ｩ繝ｫ繝医・繧ｵ繝ｼ繝千畑遘ｻ陦悟庄閭ｽ蟇ｾ雎｡縺ｧ縺吶€よ焔蜍輔〒蜑企勁縺励↑縺・〒縺上□縺輔＞縲・/notes>
    <user-preferred-server>efpserver_man1</user-preferred-server>
    <cluster>efpcluster</cluster>
    </migratable-target>
    <migratable-target>
    <name>efpserver_man2 (migratable)</name>
    <notes>繧ｷ繧ｹ繝・Β逕滓・縺ｫ繧医ｋ繝・ヵ繧ｩ繝ｫ繝医・繧ｵ繝ｼ繝千畑遘ｻ陦悟庄閭ｽ蟇ｾ雎｡縺ｧ縺吶€よ焔蜍輔〒蜑企勁縺励↑縺・〒縺上□縺輔＞縲・/notes>
    <user-preferred-server>efpserver_man2</user-preferred-server>
    <cluster>efpcluster</cluster>
    </migratable-target>
    <jdbc-store>
    <name>eFpJMSJDBCStore</name>
    <prefix-name>WLJMS_</prefix-name>
    <data-source>eFpNonXADataSource</data-source>
    <target>efpserver_man1 (migratable)</target>
    </jdbc-store>
    <jdbc-store>
    <name>eFpJMSJDBCStore2</name>
    <prefix-name>WLJMS2_</prefix-name>
    <data-source>eFpNonXADataSource</data-source>
    <target>efpserver_man2 (migratable)</target>
    </jdbc-store>
    <jms-system-resource>
    <name>eFPJMS</name>
    <target>efpcluster</target>
    <sub-deployment>
    <name>eFPServer</name>
    <target>eFpJMSServer</target>
    </sub-deployment>
    <sub-deployment>
    <name>eFPServer2</name>
    <target>eFpJMSServer2</target>
    </sub-deployment>
    <descriptor-file-name>jms/efpjms-jms.xml\JMS Description-jms.xml</descriptor-file-name>
    </jms-system-resource>
    <admin-server-name>AdminServer</admin-server-name>
    <jdbc-system-resource>
    <name>eFpDataSource</name>
    <target>efpcluster</target>
    <descriptor-file-name>jdbc/eFpDataSource-2004-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    <jdbc-system-resource>
    <name>eFpNonXADataSource</name>
    <target>efpcluster</target>
    <descriptor-file-name>jdbc/eFpNonXADataSource-6172-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    </domain>
    ##JMS Description-jms.xml
    <?xml version='1.0' encoding='UTF-8'?>
    <weblogic-jms xmlns="http://www.bea.com/ns/weblogic/weblogic-jms" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-jms [http://www.bea.com/ns/weblogic/weblogic-jms/1.0/weblogic-jms.xsd]">
    <connection-factory name="ConnectionFactory">
    <default-targeting-enabled>true</default-targeting-enabled>
    <jndi-name>jms/ConnectionFactory</jndi-name>
    <security-params>
    <attach-jmsx-user-id>false</attach-jmsx-user-id>
    </security-params>
    </connection-factory>
    <connection-factory name="XAConnectionFactory">
    <default-targeting-enabled>true</default-targeting-enabled>
    <jndi-name>jms/XAConnectionFactory</jndi-name>
    <transaction-params>
    <transaction-timeout>3600</transaction-timeout>
    <xa-connection-factory-enabled>true</xa-connection-factory-enabled>
    </transaction-params>
    <security-params>
    <attach-jmsx-user-id>false</attach-jmsx-user-id>
    </security-params>
    </connection-factory>
    <uniform-distributed-queue name="ActiveActivityQueue">
    <default-targeting-enabled>true</default-targeting-enabled>
    <jndi-name>queue/efpActiveActivityQueue</jndi-name>
    <load-balancing-policy>Round-Robin</load-balancing-policy>
    <forward-delay>-1</forward-delay>
    <reset-delivery-count-on-forward>true</reset-delivery-count-on-forward>
    </uniform-distributed-queue>
    <uniform-distributed-topic name="AdminTopic">
    <default-targeting-enabled>true</default-targeting-enabled>
    <jndi-name>topic/efpAdminTopic</jndi-name>
    <load-balancing-policy>Round-Robin</load-balancing-policy>
    </uniform-distributed-topic>
    <uniform-distributed-topic name="AuditTopic">
    <default-targeting-enabled>true</default-targeting-enabled>
    <jndi-name>topic/efpAuditTopic</jndi-name>
    <load-balancing-policy>Round-Robin</load-balancing-policy>
    </uniform-distributed-topic>
    <uniform-distributed-topic name="ErrorTopic">
    <default-targeting-enabled>true</default-targeting-enabled>
    <jndi-name>topic/efpErrorTopic</jndi-name>
    <load-balancing-policy>Round-Robin</load-balancing-policy>
    </uniform-distributed-topic>
    <uniform-distributed-topic name="FreeTextTopic">
    <default-targeting-enabled>true</default-targeting-enabled>
    <jndi-name>topic/efpFreeTextTopic</jndi-name>
    <load-balancing-policy>Round-Robin</load-balancing-policy>
    </uniform-distributed-topic>
    <uniform-distributed-topic name="ReportingTopic">
    <default-targeting-enabled>true</default-targeting-enabled>
    <jndi-name>topic/efpReportingTopic</jndi-name>
    <load-balancing-policy>Round-Robin</load-balancing-policy>
    </uniform-distributed-topic>
    </weblogic-jms>
    -----

    Getting the following exception while trying to connect the JMS destination I am using weblogic 10.3.3 connecting to oracle AQ. The config has been done as per the 'Interoperating with Oracle AQ JMS' document from oracle. I could see that while deploying the application the number of connections in the database increasing to 15 and getting the following error message.
    <Jun 15, 2011 4:14:29 PM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven E
    JB: SampleEJBBean is unable to connect to the JMS destination: jms/propQueue. Th
    e Error was:
    oracle.jms.AQjmsException: Internal error: Cannot obtain XAConnection weblogic.c
    ommon.resourcepool.ResourceLimitException: No resources currently available in p
    ool TestDataSource to allocate to applications, please increase the size of the
    pool and retry..
    at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal
    (ResourcePoolImpl.java:555)
    at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(Resourc
    ePoolImpl.java:332)
    at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(Resourc
    ePoolImpl.java:322)
    at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.j
    ava:438)
    at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.j
    ava:317)
    at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(Connectio
    nPoolManager.java:93)
    at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(Connectio
    nPoolManager.java:61)
    at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:
    1670)
    at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1
    468)
    at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:439)
    at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
    at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSour
    ce.java:355)
    at oracle.jms.AQjmsDBConnMgr.getConnection(AQjmsDBConnMgr.java:566)
    at oracle.jms.AQjmsXAConnection.createXAQueueSession(AQjmsXAConnection.j
    ava:214)
    at weblogic.ejb.container.internal.JMSConnectionPoller.setUpQueueSession
    s(JMSConnectionPoller.java:1545)
    at weblogic.ejb.container.internal.JMSConnectionPoller.createJMSConnecti
    on(JMSConnectionPoller.java:2047)
    at weblogic.ejb.container.internal.JMSConnectionPoller.connect(JMSConnec
    tionPoller.java:787)
    at weblogic.ejb.container.internal.MDConnectionManager.startConnectionPo
    lling(MDConnectionManager.java:244)
    at weblogic.ejb.container.manager.MessageDrivenManager.start(MessageDriv
    enManager.java:584)
    at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.mdManagerSt
    art(MessageDrivenBeanInfoImpl.java:1334)
    at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.deployMessa
    geDrivenBeans(MessageDrivenBeanInfoImpl.java:1314)
    at weblogic.ejb.container.deployer.EJBDeployer.deployMessageDrivenBeans(
    EJBDeployer.java:1669)
    at weblogic.ejb.container.deployer.EJBDeployer.start(EJBDeployer.java:14
    93)
    at weblogic.ejb.container.deployer.EJBModule.start(EJBModule.java:614)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(Module
    ListenerInvoker.java:249)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleSta
    teDriver.java:427)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
    river.java:43)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStat
    eDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartMod
    ulesFlow.java:28)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.ja
    va:1269)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
    river.java:43)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.
    java:409)
    at weblogic.application.internal.SingleModuleDeployment.activate(SingleM
    oduleDeployment.java:43)
    at weblogic.application.internal.DeploymentStateChecker.activate(Deploym
    entStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(Ap
    pContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.ac
    tivate(AbstractOperation.java:569)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.ac
    tivateDeployment(ActivateOperation.java:150)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.do
    Commit(ActivateOperation.java:116)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.co
    mmit(AbstractOperation.java:323)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploym
    entCommit(DeploymentManager.java:844)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeplo
    ymentList(DeploymentManager.java:1253)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(
    DeploymentManager.java:440)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.com
    mit(DeploymentServiceDispatcher.java:164)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
    ackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
    ackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
    ackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:69)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin
    gWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

  • Qualys vulnerability Scanner caused JMS Server to reset connection

    Hi
    Our customer is doing vulnerability scanning for our product. We are using Oracle AS 10.1.2.0.2.
    When customer ran Qualys vulnerability scanner, our application stopped working. While debugging we found that Oracle JMS server closed its connections.
    We got following error in jms.log under OC4J
    java.net.SocketException: Connection reset
    at java.net.SocketInputStream.read(SocketInputStream.java:173)
    at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
    at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
    at java.io.DataInputStream.readInt(DataInputStream.java:443)
    at com.evermind.server.jms.JMSRequestHandler.readCheck(JMSRequestHandler.java:269)
    at com.evermind.server.jms.JMSRequestHandler.protocol(JMSRequestHandler.java:282)
    at com.evermind.server.jms.JMSRequestHandler.run(JMSRequestHandler.java:124)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
    at java.lang.Thread.run(Thread.java:534)
    09/09/08 02:08:16 protocol
    javax.jms.JMSException: [PROTOCOL ERROR] JMSRequestHandler[2:10.129.246.48:33729]: "JMS protocol" error, expected "-559,038,735", got "1,735,489,335".
    at com.evermind.server.jms.JMSUtils.toJMSException(JMSUtils.java:1854)
    at com.evermind.server.jms.JMSRequestHandler.readCheck(JMSRequestHandler.java:272)
    at com.evermind.server.jms.JMSRequestHandler.protocol(JMSRequestHandler.java:282)
    at com.evermind.server.jms.JMSRequestHandler.run(JMSRequestHandler.java:124)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
    This shows that JMS server is prone to denial of service problem. Can any one have any idea, is this is some known issue. Or how to debug the issue.

    HI,
    Have a look into SAP Notes – 804124, 807000
    Check the JMS drivers are installed or not?
    Thnx
    Chirag Gohil

  • JMS proxy and XA connection factory

    Hi all,
    I would like to ask you what is the best practice to adopt about the scenario described below.
    A JMS proxy retrieves a message and processes it.
    Any error could occurr during processing it and, in case of errors, the JMS proxy error handler publishes the message on ad hoc recovery destination D.
    (later another app will check failed messages for fixing & republishing them into ALSB).
    In that scenario we have the JMS proxy and the jms business service that, in case of errors, publishes on destination D.
    Should the JMS proxy and the business service use both a XA connection factory in order to perform all the above steps in one transaction ?
    Otherwise if the business service itself fails publishing on destination D, the message retrieved by the JMS proxy is lost and not re-delivered to the JMS proxy.
    Or XA connection factory is not needed and could I use
    Routing Options with exactly once or both are needed ?
    Thanks
    ferp

    Hi all,
    I did some tests and follow what I've achieved.
    Scenario 1.
    - Precondition
    -- A JMS proxy with XA factory + Error Destination (MyRecoveryQueue)
    -- A business service BS with XA factory that publishes into MyOutboundQueue
    -- No "exactly once" routing option used calling BS
    -- an error is forced in the pipeline
    - Flow
    -- proxy retrieves a message and try to publish it using BS
    -- an error is forced in the pipeline:
    --- transaction is rolled back, message redelivered to proxy
    --- the message is posted to the error destination after all the retries failed
    Scenario 2.
    - Precondition
    -- As 1. but no error is forced in the pipeline
    -- the MyOutboundQueue destination queue is paused
    - Flow
    -- proxy retrieves a message and try to publish it using BS
    -- BS fails to publish it on MyOutboundQueue (because it is paused)
    --- transaction is rolled back, message redelivered to proxy
    --- the message is posted to the error destination after all the retries failed
    Scenario 2A.
    - Precondition
    -- As 2. with MyOutboundQueue paused and resumed
    - Flow:
    -- proxy retrieves a message and try to publish it using BS
    -- BS fails to publish it on MyOutboundQueue (because it is paused)
    --- transaction is rolled back, message redelivered to proxy
    --- before all the retries failed the queue is resumed
    --- BS succeeds to publish the message
    Scenario 3.
    - Precondition
    -- A JMS proxy with NO XA factory + Error Destination
    -- A business service BS with NO XA factory
    -- No "exactly once" routing option used calling BS
    -- an error is forced in the pipeline
    - Flow
    -- proxy retrieves a message and try to publish it using BS
    -- an error is forced in the pipeline:
    --- transaction is NOT rolled back, message NOT redelivered to proxy
    -- so
    --- no message delivered to MyOutboundQueue2 destination
    --- no message delivered to MyRecoveryQueue2 destination
    --- message consumed from MyQueue2 and now is lost!
    To publish message into MyRecoveryQueue2 a proxy error handler has to be added and here added explicit publish to MyRecoveryQueue2.
    But naturally in that case if in the proxy error handler, the explicit publish fails or any error occurrs no message is delivered to recovery queue.
    So if I'm not using an XAFactory the message is auto-acknowledged as soon as it is read and I've to use XA factory if I want the message to be put back in the queue in case of errors and the retry to happen.
    So both my proxy service and business service use an XA factory.
    Regards
    ferp

  • IPlanet- WebLogic Proxy Connection Pools

    In the NSAPI weblogic plugin doco it says that the wlproxy plugin pools connections. How do you control the size of the connection pool. I don't see a min/max paramater. All I see is KeepAlive, ConnectTimeoutSecs and a few other related but nothing related to connection pool size. Any help would be appreciated.
    Jack

    Hi.
    You might try posting this in the plug-in newsgroup.
    Regards,
    Michael
    Jack wrote:
    In the NSAPI weblogic plugin doco it says that the wlproxy plugin pools connections. How do you control the size of the connection pool. I don't see a min/max paramater. All I see is KeepAlive, ConnectTimeoutSecs and a few other related but nothing related to connection pool size. Any help would be appreciated.
    Jack--
    Michael Young
    Developer Relations Engineer
    BEA Support

  • Iplanet 6.0  connection queue question

    ConnectionQueue:
    Current/Peak/Limit Queue Length 0/25/4096
    Total Connections Queued 933189
    Average Queueing Delay 0.66 milliseconds
    What is an acceptable average queueing delay? Not sure when I should really worry about it or what can be done (more acceptor threads?)

    How does one go about tuning the queing delay ? Ours seems pretty high by comparision. Maybe it has something to do with the high number of images in our document pages (over 100, thank the developers for that one) or our web application performance.
    webservd pid: 7069
    Sun ONE Web Server 6.1 B08/22/2003 12:37 (SunOS DOMESTIC)
    Server started Wed Jan 21 11:32:24 2004
    Process 7069 started Wed Jan 21 11:32:24 2004
    ConnectionQueue:
    Current/Peak/Limit Queue Length 0/30/4096
    Total Connections Queued 3498501
    Average Queueing Delay 196.97 milliseconds
    ListenSocket ls1:
    Address http://aaa.bbb.ccc.ddd:80
    Acceptor Threads 1
    Default Virtual Server https-ourcompany.com
    ListenSocket ls2:
    Address https://aaa.bbb.ccc.ddd:443
    Acceptor Threads 1
    Default Virtual Server https-ourcompany.com
    KeepAliveInfo:
    KeepAliveCount 5/256
    KeepAliveHits 2253199
    KeepAliveFlushes 0
    KeepAliveRefusals 0
    KeepAliveTimeouts 18852
    KeepAliveTimeout 60 seconds
    SessionCreationInfo:
    Active Sessions 1
    Total Sessions Created 128/256
    CacheInfo:
    enabled yes
    CacheEntries 1024/1024
    Hit Ratio 8881467/9097232 ( 97.63%)
    Maximum Age 300
    Native pools:
    NativePool:
    Idle/Peak/Limit 1/1/128
    Work Queue Length/Peak/Limit 0/0/0
    Server DNS cache disabled
    Async DNS disabled
    Performance Counters:
    Average Total Percent
    Total number of requests: 2988117
    Request processing time: 0.1857 554994.5000
    default-bucket (Default bucket)
    Number of Requests: 2988117 (100.00%)
    Number of Invocations: 46667042 (100.00%)
    Latency: 0.0002 685.7922 ( 0.12%)
    Function Processing Time: 0.1855 554308.6875 ( 99.88%)
    Total Response Time: 0.1857 554994.5000 (100.00%)
    Sessions:
    Process Status Function
    7069 response service-dump

  • Connecting to a Remote JMS provider from MDB in jboss-4.0

    Hi,
    I am using Tibco as a remote JMS Provider. When the Tibco server is running on the same machine as JBoss-4.0, the Message Driven Bean deployed in Jboss is able to get the messages from the queue on Tibco server.
    I have added the following configuration to jms-ds.xml file
    <!-- The JMS provider loader -->
    <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
    name="jboss.mq:service=JMSProviderLoader,name=JMSProvider">
    <attribute name="ProviderName">TIBCOJMSProvider</attribute>
    <attribute name="ProviderAdapterClass">
    org.jboss.jms.jndi.JNDIProviderAdapter
    </attribute>
    <!-- The combined connection factory -->
    <!--attribute name="FactoryRef">XAConnectionFactory</attribute-->
    <!-- The queue connection factory -->
    <attribute name="QueueFactoryRef">XAQueueConnectionFactory</attribute>
    <!-- The topic factory -->
    <attribute name="TopicFactoryRef">XATopicConnectionFactory</attribute>
    <attribute name="Properties">
    java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory
    java.naming.factory.url.pkgs=com.tibco.tibjms.naming
    java.naming.provider.url=tibjmsnaming://TibcoHost:7222
    </attribute>
    </mbean>
    Also following invoker proxy binding is added to standardjboss.xml & it is used in MDB's jboss.xml
    <invoker-proxy-binding>
    <name>my-mdb-invoker</name>
    <invoker-mbean>does-not-matter</invoker-mbean>
    <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
    <proxy-factory-config>
    <JMSProviderAdapterJNDI>TIBCOJMSProvider</JMSProviderAdapterJNDI>
    <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
    <MinimumSize>1</MinimumSize>
    <KeepAliveMillis>30000</KeepAliveMillis>
    <MaximumSize>15</MaximumSize>
    <MaxMessages>1</MaxMessages>
    <MDBConfig>
    <ReconnectIntervalSec>10</ReconnectIntervalSec>
    <DLQConfig>
    <DestinationQueue>queue/DLQ</DestinationQueue>
    <MaxTimesRedelivered>10</MaxTimesRedelivered>
    <TimeToLive>0</TimeToLive>
    </DLQConfig>
    </MDBConfig>
    </proxy-factory-config>
    </invoker-proxy-binding>
    But When I try to use Tibco server on some other machine it throws following exception. It actually tryies to connect to Tibco server on same machine.
    javax.jms.JMSException: Failed to connect to the server at tcp://localhost:7222
    at com.tibco.tibjms.TibjmsxLinkTcp._createSocket(TibjmsxLinkTcp.java:748)
    at com.tibco.tibjms.TibjmsxLinkTcp.connect(TibjmsxLinkTcp.java:857)
    at com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:611)
    at com.tibco.tibjms.TibjmsConnection.<init>(TibjmsConnection.java:1769)
    at com.tibco.tibjms.TibjmsQueueConnection.<init>(TibjmsQueueConnection.java:35)
    at com.tibco.tibjms.TibjmsxCFImpl._createImpl(TibjmsxCFImpl.java:90)
    at com.tibco.tibjms.TibjmsxCFImpl._createConnection(TibjmsxCFImpl.java:151)
    at com.tibco.tibjms.TibjmsXAQueueConnectionFactory.createQueueConnection(TibjmsXAQueueConnectionFactory.java:140
    at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:152)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:237)
    at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:164)
    at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:545)
    at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:767)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
    at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
    at $Proxy45.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:416)
    at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
    at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:170)
    at org.jboss.ejb.MessageDrivenContainer.startService(MessageDrivenContainer.java:262)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
    at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:416)
    at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
    at $Proxy43.start(Unknown Source)
    at org.jboss.ejb.EjbModule.startService(EjbModule.java:394)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
    at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:416)
    at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
    at $Proxy19.start(Unknown Source)
    at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:605)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:935)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:746)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:709)
    at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:119)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
    at $Proxy8.deploy(Unknown Source)

    Hi,
    I am using Tibco as a remote JMS Provider. When the Tibco server is running on the same machine as JBoss-4.0, the Message Driven Bean deployed in Jboss is able to get the messages from the queue on Tibco server.
    I have added the following configuration to jms-ds.xml file
    <!-- The JMS provider loader -->
    <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
    name="jboss.mq:service=JMSProviderLoader,name=JMSProvider">
    <attribute name="ProviderName">TIBCOJMSProvider</attribute>
    <attribute name="ProviderAdapterClass">
    org.jboss.jms.jndi.JNDIProviderAdapter
    </attribute>
    <!-- The combined connection factory -->
    <!--attribute name="FactoryRef">XAConnectionFactory</attribute-->
    <!-- The queue connection factory -->
    <attribute name="QueueFactoryRef">XAQueueConnectionFactory</attribute>
    <!-- The topic factory -->
    <attribute name="TopicFactoryRef">XATopicConnectionFactory</attribute>
    <attribute name="Properties">
    java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory
    java.naming.factory.url.pkgs=com.tibco.tibjms.naming
    java.naming.provider.url=tibjmsnaming://TibcoHost:7222
    </attribute>
    </mbean>
    Also following invoker proxy binding is added to standardjboss.xml & it is used in MDB's jboss.xml
    <invoker-proxy-binding>
    <name>my-mdb-invoker</name>
    <invoker-mbean>does-not-matter</invoker-mbean>
    <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
    <proxy-factory-config>
    <JMSProviderAdapterJNDI>TIBCOJMSProvider</JMSProviderAdapterJNDI>
    <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
    <MinimumSize>1</MinimumSize>
    <KeepAliveMillis>30000</KeepAliveMillis>
    <MaximumSize>15</MaximumSize>
    <MaxMessages>1</MaxMessages>
    <MDBConfig>
    <ReconnectIntervalSec>10</ReconnectIntervalSec>
    <DLQConfig>
    <DestinationQueue>queue/DLQ</DestinationQueue>
    <MaxTimesRedelivered>10</MaxTimesRedelivered>
    <TimeToLive>0</TimeToLive>
    </DLQConfig>
    </MDBConfig>
    </proxy-factory-config>
    </invoker-proxy-binding>
    But When I try to use Tibco server on some other machine it throws following exception. It actually tryies to connect to Tibco server on same machine.
    javax.jms.JMSException: Failed to connect to the server at tcp://localhost:7222
    at com.tibco.tibjms.TibjmsxLinkTcp._createSocket(TibjmsxLinkTcp.java:748)
    at com.tibco.tibjms.TibjmsxLinkTcp.connect(TibjmsxLinkTcp.java:857)
    at com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:611)
    at com.tibco.tibjms.TibjmsConnection.<init>(TibjmsConnection.java:1769)
    at com.tibco.tibjms.TibjmsQueueConnection.<init>(TibjmsQueueConnection.java:35)
    at com.tibco.tibjms.TibjmsxCFImpl._createImpl(TibjmsxCFImpl.java:90)
    at com.tibco.tibjms.TibjmsxCFImpl._createConnection(TibjmsxCFImpl.java:151)
    at com.tibco.tibjms.TibjmsXAQueueConnectionFactory.createQueueConnection(TibjmsXAQueueConnectionFactory.java:140
    at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:152)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:237)
    at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:164)
    at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:545)
    at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:767)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
    at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
    at $Proxy45.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:416)
    at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
    at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:170)
    at org.jboss.ejb.MessageDrivenContainer.startService(MessageDrivenContainer.java:262)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
    at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:416)
    at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
    at $Proxy43.start(Unknown Source)
    at org.jboss.ejb.EjbModule.startService(EjbModule.java:394)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
    at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:416)
    at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
    at $Proxy19.start(Unknown Source)
    at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:605)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:935)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:746)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:709)
    at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:119)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
    at $Proxy8.deploy(Unknown Source)

  • Error with the Receiver JMS Adapter (Connection On-Demand feature)

    Hi,
    In high volume we are experiencing errors with the Receiver JMS Adapter and the connection On-demand feature:
    Adapter Framework caught exception: while trying to invoke the method com.sap.aii.adapter.jms.api.connector.DisconnectorListener.notifyEvent(java.lang.String) of an object loaded from local variable 'listener'
    Delivering the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: while trying to invoke the method com.sap.aii.adapter.jms.api.connector.DisconnectorListener.notifyEvent(java.lang.String) of an object loaded from local variable 'listener'.
    The message status was set to WAIT.
    Looks like the message is successfuly reprocess after the wait period but the ALEAUD/Akcnowledgment are not successful in the sender ECC system. (SAP -> PI - > JMS)
    Any idea?
    PI 7.1 EHP1
    Thanks,
    Martin
    /people/sunil.ojha5/blog/2010/08/31/review-of-sap-pi-jms-adapter-on-demand-connection-feature
    Edited by: Martin Lavoie Rousseau on Jun 3, 2011 3:21 PM

    Please ensure to have specified an User and password to connect to JMS server (don't leave the fields empty).

  • Error of Foreign JMS server connecting to durable subscriber topic

    Weblogic server domain is trying to connect to the durable topic configured on the other weblogic domain. (Both domain are running on weblogic 9.2 platform)
    WLI 9.2 Event generator is TestPinFJ is the MDB which is trying to listen message from Foreign JMS.
    Following error we have got when I did following configuration for connecting to durable topic using foreign JMS.
    <EJB> <BEA-010061> <The Message-Driven EJB: TestPinFJ is unable to connect to the JMS destination: TestQueue. The Error was:
    java.lang.IllegalArgumentException: port out of range:-16>
    Detail configuration is as follows:
    Foreign JMS : TestFS
    General:
    JNDI Connection URL: t3://10.20.65.95:9004 TestClient123 (where TestClient123 is the client id for durable subscriber topic )
    Destinations:
    Local JNDI Name: TestQueue
    Remote JNDI Name: TestTopic
    Connection Factories :
    Local JNDI Name: TestQCF
    Remote JNDI Name: TestTCF
    My suspect is the JNDI connection URL is incorrect. Please advice how to configure JNDI conn url while connecting to durable topic with client id?

    hi Hussain,
    I am the collegue of the person created this thread.
    Thaks for the input. can u please suggest me how do we configure connectionfactory and JSM topic to durable subscription with ClientID.Shoudl th eClientID be same for JMSTopic and ConectionFactory?
    In Domain "A" I have created JMS topic with durable subscriber wioth client ID "TestClient123" and created a conenctionfacory with same client ID "TestClient123" .
    In Domain "B" i created a foreign JMS connecting to topic in Domain A using connection facatory created in Domain "A" configured as as remoteConnectionFActory.
    Also the JNDI Connection URL is : t3://10.20.65.95:9004
    "weblogic.jms.common.InvalidClientIDException: Client id, Testclient1, is in use. The reason for rejection is "The JNDI name weblogic.jms.connection.clientid.TestClient123was found, and was bound to an object of type weblogic.jms.frontend.FEClientIDSingularAggregatable : FEClientIDSingularAggregatable(SingularAggregatable(<9222810352589496374.1>:1):TestClient123)"
    Nested exception: weblogic.jms.common.InvalidClientIDException: Client id, EAIEXTTestClient123, is in use. The reason for rejection is "The JNDI name weblogic.jms.connection.clientid.TestClient123 was found, and was bound to an object of type weblogic.jms.frontend.FEClientIDSingularAggregatable : FEClientIDSingularAggregatable(SingularAggregatable(<9222810352589496374.1>:1):TestClient123)".
    weblogic.jms.common.InvalidClientIDException: Client id, EAIEXTTestClient123, is in use. The reason for rejection is "The JNDI name weblogic.jms.connection.clientid.TestClient123 was found, and was bound to an object of type weblogic.jms.frontend.FEClientIDSingularAggregatable : FEClientIDSingularAggregatable(SingularAggregatable(<9222810352589496374.1>:1):TestClient123)"
    at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:211)"
    IS there any chnage i need to make to get this connectivity between Domain A and B working?
    Appreciate your help on this.

  • Unable to connect to JMSServer - JMS Exception

    Hi
    When reading a message from topic i get the folowing exception
    Exception occurred: javax.jms.JMSException: Unable to connect to JMSServer (NOAH
    /192.168.0.131:9127): Option unsupported by protocol: no further information
    javax.jms.JMSException: Unable to connect to JMSServer (NOAH/192.168.0.131:9127)
    : Option unsupported by protocol: no further information
    at com.evermind._hrb._mu(.:136)
    at com.evermind._hrb.start(.:33)
    at Tester.main(Tester.java:91)
    I have noticed that this occours if the JMS server is running on JRE 1.4 and the client on JRE1.3
    If the JMS server is runnning on JRE 1.3 , clients with either JRE 1.3 or 1.4 can connect ot it.
    What could be the reason? and is there any solution to this?
    The code i am using in the client is given below
    topicConnection = topicConnectionFactory.createTopicConnection();
    topicSession = topicConnection.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
    topicSubscriber = topicSession.createSubscriber(topic);
    topicListener = new TextListener();
    topicSubscriber.setMessageListener(topicListener);
    topicConnection.start();
    Renjith

    Hi, raeeskader !
    I just want to thank you.
    We encountered the same problem:
      java.net.SocketException: Option unsupported by protocol: connect wrapped in a JMSException when trying to connect to a JMS server
    and changing JVM used to run the server, as you suggested, from 1.4.0 to 1.3.1 solved the problem.

  • Connection Problem To "JMS Queue XML"

    Hi.
    I can't connect to the JMS Queue XML.While Creating Data Server using the JMS XML Queue Technology pointing to WLS and the XML document type definition (dtd ) file books.dtd is provided from the local(C:\Documents and Settings\348773\Desktop\XML FILES) directory. The connection details are as below:-
    Definition Tab:
    Connection:
    User: userXXX
    Password: passYYY
    These are user name and password for the application server
    JNDI tab:
    JNDI Authorization: None
    JNDI User/password (same as above)
    JNDI Protocol: Undefined
    JNDI Driver: weblogic.jndi.WLInitialContextFactory
    JNDI URL: http://172.18.41.47:7001?d=C:\Documents and Settings\348773\Desktop\XML FILES\books.dtd&JMS_DESTINATION=jms/demoQueue
    JNDI Resource:eis/ConnFact/Queue
    FYI:-I h'v just copy and pasted the value of JNDI Driver(weblogic.jndi.WLInitialContextFactory) from a document because I don't know how to find the JNDI drivers name for WLS.I think it is a default name.If I'm wrong then Please tell me how to find it.when I test the connection it shows an error like this:-
    java.sql.SQLException: Cannot load connection class because of underlying exception: 'java.sql.SQLException: Cannot load connection class because of underlying exception: 'javax.jms.JMSException: ODI-40201: Cannot create the initial JNDI context)'.'.
         at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.doGetConnection(LoginTimeoutDatasourceAdapter.java:133)
         at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.getConnection(LoginTimeoutDatasourceAdapter.java:62)
         at com.sunopsis.sql.SnpsConnection.testConnection(SnpsConnection.java:1118)
         at com.sunopsis.graphical.dialog.SnpsDialogTestConnet.getLocalConnect(SnpsDialogTestConnet.java:420)
         at com.sunopsis.graphical.dialog.SnpsDialogTestConnet.localConnect(SnpsDialogTestConnet.java:860)
         at com.sunopsis.graphical.dialog.SnpsDialogTestConnet.jButtonTest_ActionPerformed(SnpsDialogTestConnet.java:806)
         at com.sunopsis.graphical.dialog.SnpsDialogTestConnet.connEtoC1(SnpsDialogTestConnet.java:165)
         at com.sunopsis.graphical.dialog.SnpsDialogTestConnet.access$1(SnpsDialogTestConnet.java:161)
         at com.sunopsis.graphical.dialog.SnpsDialogTestConnet$IvjEventHandler.actionPerformed(SnpsDialogTestConnet.java:111)
         at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
         at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2319)
         at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
         at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
         at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
         at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:272)
         at java.awt.Component.processMouseEvent(Component.java:6289)
         at javax.swing.JComponent.processMouseEvent(JComponent.java:3268)
         at java.awt.Component.processEvent(Component.java:6054)
         at java.awt.Container.processEvent(Container.java:2042)
         at java.awt.Component.dispatchEventImpl(Component.java:4652)
         at java.awt.Container.dispatchEventImpl(Container.java:2101)
         at java.awt.Component.dispatchEvent(Component.java:4483)
         at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4577)
         at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4238)
         at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168)
         at java.awt.Container.dispatchEventImpl(Container.java:2085)
         at java.awt.Window.dispatchEventImpl(Window.java:2479)
         at java.awt.Component.dispatchEvent(Component.java:4483)
         at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:644)
         at java.awt.EventQueue.access$000(EventQueue.java:85)
         at java.awt.EventQueue$1.run(EventQueue.java:604)
         at java.awt.EventQueue$1.run(EventQueue.java:601)
         at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
         at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:98)
         at java.awt.EventQueue$2.run(EventQueue.java:618)
         at java.awt.EventQueue$2.run(EventQueue.java:615)
         at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:614)
         at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
         at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:175)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:170)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:162)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
    Caused by: java.sql.SQLException: Cannot load connection class because of underlying exception: 'java.sql.SQLException: Cannot load connection class because of underlying exception: 'javax.jms.JMSException: ODI-40201: Cannot create the initial JNDI context)'.'.
         at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.doGetConnection(LoginTimeoutDatasourceAdapter.java:133)
         at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter.getConnection(LoginTimeoutDatasourceAdapter.java:62)
         at oracle.odi.core.datasource.dwgobject.support.OnConnectOnDisconnectDataSourceAdapter.getConnection(OnConnectOnDisconnectDataSourceAdapter.java:74)
         at oracle.odi.jdbc.datasource.LoginTimeoutDatasourceAdapter$ConnectionProcessor.run(LoginTimeoutDatasourceAdapter.java:217)
         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
         at java.util.concurrent.FutureTask.run(FutureTask.java:139)
         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:909)
         at java.lang.Thread.run(Thread.java:662)
    Caused by: java.sql.SQLException: Cannot load connection class because of underlying exception: 'java.sql.SQLException: Cannot load connection class because of underlying exception: 'javax.jms.JMSException: ODI-40201: Cannot create the initial JNDI context)'.'.
         at com.sunopsis.jdbc.driver.JMSXMLDriver.connect(JMSXMLDriver.java:113)
         at oracle.odi.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriver(DriverManagerDataSource.java:409)
         at oracle.odi.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriver(DriverManagerDataSource.java:385)
         at oracle.odi.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriver(DriverManagerDataSource.java:352)
         at oracle.odi.jdbc.datasource.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:331)
         ... 7 more
    Caused by: java.sql.SQLException: Cannot load connection class because of underlying exception: 'javax.jms.JMSException: ODI-40201: Cannot create the initial JNDI context)'.
         at com.sunopsis.jdbc.driver.JMSXMLConnection.<init>(JMSXMLConnection.java:295)
         at com.sunopsis.jdbc.driver.JMSXMLDriver.connect(JMSXMLDriver.java:99)
         ... 11 more
    So,
    please advise
    Thanks
    Anindya

    Hi,
    Hope till now you might have solved this problem.
    If not lets do  this below workout , we had same kind of problem.
    in JNDI tab , you have JNDI authentication, this authentication is for JNDI resources, I am sure you might be using weblogic credentials.
    Steps :
    1. Clear JNDI User : Blank (No value)
    2. Clear Password : Blank (No Value)
    3. set JNDI Authentication as None, regenerate the scenario and check
    For accessing JNDI responses , JMS XML Queue uses Connection parameters from Definition tab.
    Hope this helps

  • Iplanet connect exception when usig non acc client

    I am trying to connect a non acc client to my appserver. I have everything set up according to the sample program provided by sun. When i execute the client it "hangs" at the contect initialization line (Context initial = new InitialContext(env).
    when I check the log for the appserver it has the following error:
    com.iplanet.ias.cis.connection.ConnectException: com.iplanet.ias.cis.channel.tcp.TCPNativeException: -5973:EndPoint.JNI_getValidAddressNative: PR_GetHostByAddr() Failed
    at com.iplanet.ias.cis.connection.Connection.<init>(Connection.java:205)
    at com.iplanet.ias.cis.connection.ServerConnection.accept(ServerConnection.java:251)
    at com.sun.corba.ee.internal.iiop.ListenerThread.run(ListenerThread.java:77)
    Caused by: com.iplanet.ias.cis.channel.tcp.TCPNativeException: -5973:EndPoint.JNI_getValidAddressNative: PR_GetHostByAddr() Failed
    at com.iplanet.ias.cis.connection.EndPoint.getValidAddressNative(Native Method)
    at com.iplanet.ias.cis.connection.EndPoint.getValidAddress(EndPoint.java:239)
    at com.iplanet.ias.cis.connection.EndPoint.<init>(EndPoint.java:101)
    at com.iplanet.ias.cis.connection.EndPoint.getEndPoint(EndPoint.java:73)
    at com.iplanet.ias.cis.connection.EndPoint.getEndPoint(EndPoint.java:78)
    at com.iplanet.ias.cis.channel.tcp.TCPChannel.getLocalEndPoint(TCPChannel.java:68)
    at com.iplanet.ias.cis.connection.Connection.<init>(Connection.java:202)
    ... 2 more
    any idea what I am doing wrong?

    Were you ever able to resolve this problem? If so, please let me know how at [email protected]
    thanks
    suneet

  • JMS Default connection factories

              Hi
              I have a evaluation version of Weblogic Server 7. When I start the examples server
              there are no default connection factories under JMS. The default connection factory
              is enabled. How can I view the default connection factory to use with the given
              examples?
              Thanks
              

              Hi
              You can look them up in the server's JNDI tree.
              In console, you can goto server (myserver) and click on the "View JNDI tree"
              link at the bottom, to get the JNDI tree, where you can find the default connection
              factories.
              Kats
              BEA
              "diptiman" <[email protected]> wrote:
              >
              >Hi
              >I have a evaluation version of Weblogic Server 7. When I start the examples
              >server
              >there are no default connection factories under JMS. The default connection
              >factory
              >is enabled. How can I view the default connection factory to use with
              >the given
              >examples?
              >
              >Thanks
              

  • Connecting to remote JMS server

    I am running Flex2/FDS using Tomcat, and want to create a
    Producer/Consumer to message via a JMS application (Sonic ESB) on a
    different host. We have successfully done this with Flex 1.5 using
    a java servlet, but I cannot get it to work via Flex2/FDS
    messaging.
    Here are (I think) the essentials:
    We have the sonic jars on the server available to FDS, I also
    put them in tomcat's common/lib directory
    in mxml, I have:
    <Producer id="p" destination="sonicDestination" />
    in messaging-config.xml I have (relevant part):
    <destination id="sonicDestination" >
    <adapter ref="jms"/>
    <channels>
    <channel ref="my-rtmp">
    </channel>
    <properties>
    <jms>
    <destination-type>Queue</destination-type>
    <message-type>javax.jms.TextMessage</message-type>
    <connection-factory>java:comp/env/jms/connectionFactory</connection-factory>
    <destination-jndi-name>java:comp/env/sonicDestination</destination-jndi-name>
    <destination-name>targetSonicQueue</destination-name>
    <delivery-mode>NON-PERSISTENT</delivery-mode>
    <acknowledge-mode>AUTO_ACKNOWLEDGE</acknowledge-mode>
    <transacted-sessions>false</transacted-sessions>
    </jms>
    </properties>
    </destination>
    in web-xml I have:
    <resource-ref>
    <res-ref-name>jms/connectionFactory</res-ref-name>
    <res-type>javax.jms.ConnectionFactory</res-type>
    <res-auth>Container</res-auth>
    <res-sharing-scope>Shareable</res-sharing-scope>
    </resource-ref>
    <resource-ref>
    <res-ref-name>sonicDestination</res-ref-name>
    <res-type>javax.jms.Destination</res-type>
    <res-auth>Container</res-auth>
    <res-sharing-scope>Shareable</res-sharing-scope>
    </resource-ref>
    AND in context.xml I have:
    <Resource name="jms/connectionFactory" auth="container"
    type="progress.message.jclient.ConnectionFactory"
    brokerURL="tcp:_ipaddress_:2506"
    username="_username_" password="_password_"
    defaultUser="_username_" defaultPassword="_password_"
    />
    <Resource name="sonicDestination" auth="container"
    type="progress.message.jclient.Queue"
    queueName="targetSonicQueue" />
    ... this all seems to deploy OK... in the mxml... when I
    create a message and try to have the producer send it...
    I get an error on the server (which is passed back as an
    exception to the client)... the relevant part of all that is:
    javax.naming.NamingException: Cannot create resource instance
    at
    org.apache.naming.factory.ResourceFactory.getObjectInstance()
    at javax.naming.spi.NamingManager.getObjectInstance()
    at org.apache.naming.NamingContext.lookup()
    _several layers of calling NamingContext_
    at javax.naming.InitialContext.lookup()
    at
    flex.messaging.services.messaging.adapters.JMSProxy.getDestination()
    at
    flex.messaging.services.messaging.adapters.JMSQueueProducer.start()
    ..._more
    It looks to me like it is finding Tomcat's JNDI service and
    getting to the point where its trying to instantiate the
    connectionFactory or the sonicDestination...
    and that's failing...
    do you have or know of someone who knows how to connect to
    from Flex 2.0.1 / FDS via Tomcat to a Sonic MQ (7.0) server on
    another host ?
    Thanx much

    My current code is:
    env.setProperty(Context.PROVIDER_URL, "iiop://localhost:2809");
    env.setProperty(Context.INITIAL_CONTEXT_FACTORY, "com.ibm.websphere.naming.WsnInitialContextFactory");
    InitialContext initCtx = new InitialContext(env);
    System.out.println("Getting connection factory....");
    // Finding the WAS QueueConnectionFactory
    javax.jms.ConnectionFactory qcf = (javax.jms.ConnectionFactory) initCtx.lookup(JMSCF_JNDI_NAME);
    System.out.println("qcf="+qcf);
    // Finding the Queue Destination
    Destination q = (Destination) initCtx.lookup(JMSQ_JNDI_NAME);
    I am getting exception as:
    Oct 26, 2005 4:10:11 PM com.ibm.ws.naming.java.javaURLContextFactory
    SEVERE: javaAccessorNotSet
    javax.naming.ConfigurationException: Name space accessor for the java: name space has not been set. Possible cause is that the user is specifying a java: URL name in a JNDI Context method call but is not running in a J2EE client or server environment.
    at com.ibm.ws.naming.java.javaURLContextFactory.isNameSpaceAccessable(javaURLContextFactory.java:98)
    at com.ibm.ws.naming.urlbase.UrlContextFactory.getObjectInstance(UrlContextFactory.java:73)
    at javax.naming.spi.NamingManager.getURLObject(NamingManager.java:579)
    at javax.naming.spi.NamingManager.getURLContext(NamingManager.java:528)
    at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:275)
    at javax.naming.InitialContext.lookup(InitialContext.java:347)
    at sender.Main.main(Main.java:29)

  • JMS Server active connections keep incrementing when calling jms webservice

    I was doing performance and resources consumption analysis of the CGBU Activation product and noticed that when interacting with jms transport web service the number of active connections (JMS Servers/Monitoring/Active Connections in Admin Console) keeps incrementing at the rate of invoking methods on the web service. The number of active connections, when disconnecting the client from the server, doesn't change.
    I've stripped down the web service so it doesn't do anything at all and connect to it via a web service client. When, through admin console, I check the number of active connection in the jms server, it goes up by the number of calls to the jms web service.
    Can anyone tell if this is a known issue in WebLogic jms transport implementation for web services?
    my WSDL
    <?xml version='1.0' encoding='UTF-8'?>
    <s0:definitions name="MslvAsapWsDefinitions" targetNamespace="tns" xmlns="" xmlns:s0="http://schemas.xmlsoap.org/wsdl/" xmlns:s1="tns" xmlns:s2="java:com.mslv.asap.ws.impl" xmlns:s3="http://schemas.xmlsoap.org/wsdl/soap/">
    <s0:types>
    <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="tns" xmlns:xs="http://www.w3.org/2001/XMLSchema">
    <xs:import namespace="http://com.bea/wls92/com/bea/staxb/buildtime/internal/bts"/>
    <xs:element name="suspendOrderByKey">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="suspendOrderByKeyResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="resumeOrderByKey">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="resumeOrderByKeyResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="createOrderByValue">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="createOrderByValueResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="getServiceTypes">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="getServiceTypesResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="removeOrderByKey">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="removeOrderByKeyResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="getOrderByKey">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="getOrderByKeyResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="jsrpGateway">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="jsrpGatewayResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="abortOrderByKey">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="abortOrderByKeyResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="getOrderTypes">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="getOrderTypesResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="queryOrders">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="queryOrdersResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="setOrderByValue">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="setOrderByValueResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="startOrderByKey">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="startOrderByKeyResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:schema>
    <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="java:com.mslv.asap.ws.impl" xmlns:xs="http://www.w3.org/2001/XMLSchema">
    <xs:complexType name="MslvAsapWsSessionException">
    <xs:sequence>
    <xs:element minOccurs="1" name="Arg0" nillable="true" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    <xs:element name="MslvAsapWsSessionException" type="java:MslvAsapWsSessionException" xmlns:java="java:com.mslv.asap.ws.impl"/>
    </xs:schema>
    </s0:types>
    <s0:message name="suspendOrderByKey">
    <s0:part element="s1:suspendOrderByKey" name="parameters"/>
    </s0:message>
    <s0:message name="suspendOrderByKeyResponse">
    <s0:part element="s1:suspendOrderByKeyResponse" name="parameters"/>
    </s0:message>
    <s0:message name="MslvAsapWsSessionException">
    <s0:part element="s2:MslvAsapWsSessionException" name="MslvAsapWsSessionException"/>
    </s0:message>
    <s0:message name="resumeOrderByKey">
    <s0:part element="s1:resumeOrderByKey" name="parameters"/>
    </s0:message>
    <s0:message name="resumeOrderByKeyResponse">
    <s0:part element="s1:resumeOrderByKeyResponse" name="parameters"/>
    </s0:message>
    <s0:message name="createOrderByValue">
    <s0:part element="s1:createOrderByValue" name="parameters"/>
    </s0:message>
    <s0:message name="createOrderByValueResponse">
    <s0:part element="s1:createOrderByValueResponse" name="parameters"/>
    </s0:message>
    <s0:message name="getServiceTypes">
    <s0:part element="s1:getServiceTypes" name="parameters"/>
    </s0:message>
    <s0:message name="getServiceTypesResponse">
    <s0:part element="s1:getServiceTypesResponse" name="parameters"/>
    </s0:message>
    <s0:message name="removeOrderByKey">
    <s0:part element="s1:removeOrderByKey" name="parameters"/>
    </s0:message>
    <s0:message name="removeOrderByKeyResponse">
    <s0:part element="s1:removeOrderByKeyResponse" name="parameters"/>
    </s0:message>
    <s0:message name="getOrderByKey">
    <s0:part element="s1:getOrderByKey" name="parameters"/>
    </s0:message>
    <s0:message name="getOrderByKeyResponse">
    <s0:part element="s1:getOrderByKeyResponse" name="parameters"/>
    </s0:message>
    <s0:message name="jsrpGateway">
    <s0:part element="s1:jsrpGateway" name="parameters"/>
    </s0:message>
    <s0:message name="jsrpGatewayResponse">
    <s0:part element="s1:jsrpGatewayResponse" name="parameters"/>
    </s0:message>
    <s0:message name="abortOrderByKey">
    <s0:part element="s1:abortOrderByKey" name="parameters"/>
    </s0:message>
    <s0:message name="abortOrderByKeyResponse">
    <s0:part element="s1:abortOrderByKeyResponse" name="parameters"/>
    </s0:message>
    <s0:message name="getOrderTypes">
    <s0:part element="s1:getOrderTypes" name="parameters"/>
    </s0:message>
    <s0:message name="getOrderTypesResponse">
    <s0:part element="s1:getOrderTypesResponse" name="parameters"/>
    </s0:message>
    <s0:message name="queryOrders">
    <s0:part element="s1:queryOrders" name="parameters"/>
    </s0:message>
    <s0:message name="queryOrdersResponse">
    <s0:part element="s1:queryOrdersResponse" name="parameters"/>
    </s0:message>
    <s0:message name="setOrderByValue">
    <s0:part element="s1:setOrderByValue" name="parameters"/>
    </s0:message>
    <s0:message name="setOrderByValueResponse">
    <s0:part element="s1:setOrderByValueResponse" name="parameters"/>
    </s0:message>
    <s0:message name="startOrderByKey">
    <s0:part element="s1:startOrderByKey" name="parameters"/>
    </s0:message>
    <s0:message name="startOrderByKeyResponse">
    <s0:part element="s1:startOrderByKeyResponse" name="parameters"/>
    </s0:message>
    <s0:portType name="MslvAsapWsServiceImpl">
    <s0:operation name="suspendOrderByKey" parameterOrder="parameters">
    <s0:input message="s1:suspendOrderByKey"/>
    <s0:output message="s1:suspendOrderByKeyResponse"/>
    <s0:fault message="s1:MslvAsapWsSessionException" name="MslvAsapWsSessionException"/>
    </s0:operation>
    <s0:operation name="resumeOrderByKey" parameterOrder="parameters">
    <s0:input message="s1:resumeOrderByKey"/>
    <s0:output message="s1:resumeOrderByKeyResponse"/>
    <s0:fault message="s1:MslvAsapWsSessionException" name="MslvAsapWsSessionException"/>
    </s0:operation>
    <s0:operation name="createOrderByValue" parameterOrder="parameters">
    <s0:input message="s1:createOrderByValue"/>
    <s0:output message="s1:createOrderByValueResponse"/>
    <s0:fault message="s1:MslvAsapWsSessionException" name="MslvAsapWsSessionException"/>
    </s0:operation>
    <s0:operation name="getServiceTypes" parameterOrder="parameters">
    <s0:input message="s1:getServiceTypes"/>
    <s0:output message="s1:getServiceTypesResponse"/>
    <s0:fault message="s1:MslvAsapWsSessionException" name="MslvAsapWsSessionException"/>
    </s0:operation>
    <s0:operation name="removeOrderByKey" parameterOrder="parameters">
    <s0:input message="s1:removeOrderByKey"/>
    <s0:output message="s1:removeOrderByKeyResponse"/>
    <s0:fault message="s1:MslvAsapWsSessionException" name="MslvAsapWsSessionException"/>
    </s0:operation>
    <s0:operation name="getOrderByKey" parameterOrder="parameters">
    <s0:input message="s1:getOrderByKey"/>
    <s0:output message="s1:getOrderByKeyResponse"/>
    <s0:fault message="s1:MslvAsapWsSessionException" name="MslvAsapWsSessionException"/>
    </s0:operation>
    <s0:operation name="jsrpGateway" parameterOrder="parameters">
    <s0:input message="s1:jsrpGateway"/>
    <s0:output message="s1:jsrpGatewayResponse"/>
    <s0:fault message="s1:MslvAsapWsSessionException" name="MslvAsapWsSessionException"/>
    </s0:operation>
    <s0:operation name="abortOrderByKey" parameterOrder="parameters">
    <s0:input message="s1:abortOrderByKey"/>
    <s0:output message="s1:abortOrderByKeyResponse"/>
    <s0:fault message="s1:MslvAsapWsSessionException" name="MslvAsapWsSessionException"/>
    </s0:operation>
    <s0:operation name="getOrderTypes" parameterOrder="parameters">
    <s0:input message="s1:getOrderTypes"/>
    <s0:output message="s1:getOrderTypesResponse"/>
    <s0:fault message="s1:MslvAsapWsSessionException" name="MslvAsapWsSessionException"/>
    </s0:operation>
    <s0:operation name="queryOrders" parameterOrder="parameters">
    <s0:input message="s1:queryOrders"/>
    <s0:output message="s1:queryOrdersResponse"/>
    <s0:fault message="s1:MslvAsapWsSessionException" name="MslvAsapWsSessionException"/>
    </s0:operation>
    <s0:operation name="setOrderByValue" parameterOrder="parameters">
    <s0:input message="s1:setOrderByValue"/>
    <s0:output message="s1:setOrderByValueResponse"/>
    <s0:fault message="s1:MslvAsapWsSessionException" name="MslvAsapWsSessionException"/>
    </s0:operation>
    <s0:operation name="startOrderByKey" parameterOrder="parameters">
    <s0:input message="s1:startOrderByKey"/>
    <s0:output message="s1:startOrderByKeyResponse"/>
    <s0:fault message="s1:MslvAsapWsSessionException" name="MslvAsapWsSessionException"/>
    </s0:operation>
    </s0:portType>
    <s0:binding name="MslvAsapWsSoapBinding" type="s1:MslvAsapWsServiceImpl">
    <s3:binding style="document" transport="http://www.openuri.org/2002/04/soap/jms/"/>
    <s0:operation name="suspendOrderByKey">
    <s3:operation soapAction="tns/suspendOrderByKey" style="document"/>
    <s0:input>
    <s3:body parts="parameters" use="literal"/>
    </s0:input>
    <s0:output>
    <s3:body parts="parameters" use="literal"/>
    </s0:output>
    <s0:fault name="MslvAsapWsSessionException">
    <s3:fault name="MslvAsapWsSessionException" use="literal"/>
    </s0:fault>
    </s0:operation>
    <s0:operation name="resumeOrderByKey">
    <s3:operation soapAction="tns/resumeOrderByKey" style="document"/>
    <s0:input>
    <s3:body parts="parameters" use="literal"/>
    </s0:input>
    <s0:output>
    <s3:body parts="parameters" use="literal"/>
    </s0:output>
    <s0:fault name="MslvAsapWsSessionException">
    <s3:fault name="MslvAsapWsSessionException" use="literal"/>
    </s0:fault>
    </s0:operation>
    <s0:operation name="createOrderByValue">
    <s3:operation soapAction="tns/createOrderByValue" style="document"/>
    <s0:input>
    <s3:body parts="parameters" use="literal"/>
    </s0:input>
    <s0:output>
    <s3:body parts="parameters" use="literal"/>
    </s0:output>
    <s0:fault name="MslvAsapWsSessionException">
    <s3:fault name="MslvAsapWsSessionException" use="literal"/>
    </s0:fault>
    </s0:operation>
    <s0:operation name="getServiceTypes">
    <s3:operation soapAction="tns/getServiceTypes" style="document"/>
    <s0:input>
    <s3:body parts="parameters" use="literal"/>
    </s0:input>
    <s0:output>
    <s3:body parts="parameters" use="literal"/>
    </s0:output>
    <s0:fault name="MslvAsapWsSessionException">
    <s3:fault name="MslvAsapWsSessionException" use="literal"/>
    </s0:fault>
    </s0:operation>
    <s0:operation name="removeOrderByKey">
    <s3:operation soapAction="tns/removeOrderByKey" style="document"/>
    <s0:input>
    <s3:body parts="parameters" use="literal"/>
    </s0:input>
    <s0:output>
    <s3:body parts="parameters" use="literal"/>
    </s0:output>
    <s0:fault name="MslvAsapWsSessionException">
    <s3:fault name="MslvAsapWsSessionException" use="literal"/>
    </s0:fault>
    </s0:operation>
    <s0:operation name="getOrderByKey">
    <s3:operation soapAction="tns/getOrderByKey" style="document"/>
    <s0:input>
    <s3:body parts="parameters" use="literal"/>
    </s0:input>
    <s0:output>
    <s3:body parts="parameters" use="literal"/>
    </s0:output>
    <s0:fault name="MslvAsapWsSessionException">
    <s3:fault name="MslvAsapWsSessionException" use="literal"/>
    </s0:fault>
    </s0:operation>
    <s0:operation name="jsrpGateway">
    <s3:operation soapAction="tns/jsrpGateway" style="document"/>
    <s0:input>
    <s3:body parts="parameters" use="literal"/>
    </s0:input>
    <s0:output>
    <s3:body parts="parameters" use="literal"/>
    </s0:output>
    <s0:fault name="MslvAsapWsSessionException">
    <s3:fault name="MslvAsapWsSessionException" use="literal"/>
    </s0:fault>
    </s0:operation>
    <s0:operation name="abortOrderByKey">
    <s3:operation soapAction="tns/abortOrderByKey" style="document"/>
    <s0:input>
    <s3:body parts="parameters" use="literal"/>
    </s0:input>
    <s0:output>
    <s3:body parts="parameters" use="literal"/>
    </s0:output>
    <s0:fault name="MslvAsapWsSessionException">
    <s3:fault name="MslvAsapWsSessionException" use="literal"/>
    </s0:fault>
    </s0:operation>
    <s0:operation name="getOrderTypes">
    <s3:operation soapAction="tns/getOrderTypes" style="document"/>
    <s0:input>
    <s3:body parts="parameters" use="literal"/>
    </s0:input>
    <s0:output>
    <s3:body parts="parameters" use="literal"/>
    </s0:output>
    <s0:fault name="MslvAsapWsSessionException">
    <s3:fault name="MslvAsapWsSessionException" use="literal"/>
    </s0:fault>
    </s0:operation>
    <s0:operation name="queryOrders">
    <s3:operation soapAction="tns/queryOrders" style="document"/>
    <s0:input>
    <s3:body parts="parameters" use="literal"/>
    </s0:input>
    <s0:output>
    <s3:body parts="parameters" use="literal"/>
    </s0:output>
    <s0:fault name="MslvAsapWsSessionException">
    <s3:fault name="MslvAsapWsSessionException" use="literal"/>
    </s0:fault>
    </s0:operation>
    <s0:operation name="setOrderByValue">
    <s3:operation soapAction="tns/setOrderByValue" style="document"/>
    <s0:input>
    <s3:body parts="parameters" use="literal"/>
    </s0:input>
    <s0:output>
    <s3:body parts="parameters" use="literal"/>
    </s0:output>
    <s0:fault name="MslvAsapWsSessionException">
    <s3:fault name="MslvAsapWsSessionException" use="literal"/>
    </s0:fault>
    </s0:operation>
    <s0:operation name="startOrderByKey">
    <s3:operation soapAction="tns/startOrderByKey" style="document"/>
    <s0:input>
    <s3:body parts="parameters" use="literal"/>
    </s0:input>
    <s0:output>
    <s3:body parts="parameters" use="literal"/>
    </s0:output>
    <s0:fault name="MslvAsapWsSessionException">
    <s3:fault name="MslvAsapWsSessionException" use="literal"/>
    </s0:fault>
    </s0:operation>
    </s0:binding>
    <s0:service name="MslvAsapWs">
    <s0:port binding="s1:MslvAsapWsSoapBinding" name="JmsSessionPort">
    <s3:address location="jms:///SAAS-1/Oracle/CGBU/Mslv/Asap/Ws?URI=SAAS-1.WebServiceQueue"/>
    </s0:port>
    </s0:service>
    </s0:definitions>

    I was doing performance and resources consumption analysis of the CGBU Activation product and noticed that when interacting with jms transport web service the number of active connections (JMS Servers/Monitoring/Active Connections in Admin Console) keeps incrementing at the rate of invoking methods on the web service. The number of active connections, when disconnecting the client from the server, doesn't change.
    I've stripped down the web service so it doesn't do anything at all and connect to it via a web service client. When, through admin console, I check the number of active connection in the jms server, it goes up by the number of calls to the jms web service.
    Can anyone tell if this is a known issue in WebLogic jms transport implementation for web services?
    my WSDL
    <?xml version='1.0' encoding='UTF-8'?>
    <s0:definitions name="MslvAsapWsDefinitions" targetNamespace="tns" xmlns="" xmlns:s0="http://schemas.xmlsoap.org/wsdl/" xmlns:s1="tns" xmlns:s2="java:com.mslv.asap.ws.impl" xmlns:s3="http://schemas.xmlsoap.org/wsdl/soap/">
    <s0:types>
    <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="tns" xmlns:xs="http://www.w3.org/2001/XMLSchema">
    <xs:import namespace="http://com.bea/wls92/com/bea/staxb/buildtime/internal/bts"/>
    <xs:element name="suspendOrderByKey">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="suspendOrderByKeyResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="resumeOrderByKey">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="resumeOrderByKeyResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="createOrderByValue">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="createOrderByValueResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="getServiceTypes">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="getServiceTypesResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="removeOrderByKey">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="removeOrderByKeyResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="getOrderByKey">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="getOrderByKeyResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="jsrpGateway">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="jsrpGatewayResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="abortOrderByKey">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="abortOrderByKeyResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="getOrderTypes">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="getOrderTypesResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="queryOrders">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="queryOrdersResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="setOrderByValue">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="setOrderByValueResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="startOrderByKey">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="startOrderByKeyResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:any/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:schema>
    <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="java:com.mslv.asap.ws.impl" xmlns:xs="http://www.w3.org/2001/XMLSchema">
    <xs:complexType name="MslvAsapWsSessionException">
    <xs:sequence>
    <xs:element minOccurs="1" name="Arg0" nillable="true" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    <xs:element name="MslvAsapWsSessionException" type="java:MslvAsapWsSessionException" xmlns:java="java:com.mslv.asap.ws.impl"/>
    </xs:schema>
    </s0:types>
    <s0:message name="suspendOrderByKey">
    <s0:part element="s1:suspendOrderByKey" name="parameters"/>
    </s0:message>
    <s0:message name="suspendOrderByKeyResponse">
    <s0:part element="s1:suspendOrderByKeyResponse" name="parameters"/>
    </s0:message>
    <s0:message name="MslvAsapWsSessionException">
    <s0:part element="s2:MslvAsapWsSessionException" name="MslvAsapWsSessionException"/>
    </s0:message>
    <s0:message name="resumeOrderByKey">
    <s0:part element="s1:resumeOrderByKey" name="parameters"/>
    </s0:message>
    <s0:message name="resumeOrderByKeyResponse">
    <s0:part element="s1:resumeOrderByKeyResponse" name="parameters"/>
    </s0:message>
    <s0:message name="createOrderByValue">
    <s0:part element="s1:createOrderByValue" name="parameters"/>
    </s0:message>
    <s0:message name="createOrderByValueResponse">
    <s0:part element="s1:createOrderByValueResponse" name="parameters"/>
    </s0:message>
    <s0:message name="getServiceTypes">
    <s0:part element="s1:getServiceTypes" name="parameters"/>
    </s0:message>
    <s0:message name="getServiceTypesResponse">
    <s0:part element="s1:getServiceTypesResponse" name="parameters"/>
    </s0:message>
    <s0:message name="removeOrderByKey">
    <s0:part element="s1:removeOrderByKey" name="parameters"/>
    </s0:message>
    <s0:message name="removeOrderByKeyResponse">
    <s0:part element="s1:removeOrderByKeyResponse" name="parameters"/>
    </s0:message>
    <s0:message name="getOrderByKey">
    <s0:part element="s1:getOrderByKey" name="parameters"/>
    </s0:message>
    <s0:message name="getOrderByKeyResponse">
    <s0:part element="s1:getOrderByKeyResponse" name="parameters"/>
    </s0:message>
    <s0:message name="jsrpGateway">
    <s0:part element="s1:jsrpGateway" name="parameters"/>
    </s0:message>
    <s0:message name="jsrpGatewayResponse">
    <s0:part element="s1:jsrpGatewayResponse" name="parameters"/>
    </s0:message>
    <s0:message name="abortOrderByKey">
    <s0:part element="s1:abortOrderByKey" name="parameters"/>
    </s0:message>
    <s0:message name="abortOrderByKeyResponse">
    <s0:part element="s1:abortOrderByKeyResponse" name="parameters"/>
    </s0:message>
    <s0:message name="getOrderTypes">
    <s0:part element="s1:getOrderTypes" name="parameters"/>
    </s0:message>
    <s0:message name="getOrderTypesResponse">
    <s0:part element="s1:getOrderTypesResponse" name="parameters"/>
    </s0:message>
    <s0:message name="queryOrders">
    <s0:part element="s1:queryOrders" name="parameters"/>
    </s0:message>
    <s0:message name="queryOrdersResponse">
    <s0:part element="s1:queryOrdersResponse" name="parameters"/>
    </s0:message>
    <s0:message name="setOrderByValue">
    <s0:part element="s1:setOrderByValue" name="parameters"/>
    </s0:message>
    <s0:message name="setOrderByValueResponse">
    <s0:part element="s1:setOrderByValueResponse" name="parameters"/>
    </s0:message>
    <s0:message name="startOrderByKey">
    <s0:part element="s1:startOrderByKey" name="parameters"/>
    </s0:message>
    <s0:message name="startOrderByKeyResponse">
    <s0:part element="s1:startOrderByKeyResponse" name="parameters"/>
    </s0:message>
    <s0:portType name="MslvAsapWsServiceImpl">
    <s0:operation name="suspendOrderByKey" parameterOrder="parameters">
    <s0:input message="s1:suspendOrderByKey"/>
    <s0:output message="s1:suspendOrderByKeyResponse"/>
    <s0:fault message="s1:MslvAsapWsSessionException" name="MslvAsapWsSessionException"/>
    </s0:operation>
    <s0:operation name="resumeOrderByKey" parameterOrder="parameters">
    <s0:input message="s1:resumeOrderByKey"/>
    <s0:output message="s1:resumeOrderByKeyResponse"/>
    <s0:fault message="s1:MslvAsapWsSessionException" name="MslvAsapWsSessionException"/>
    </s0:operation>
    <s0:operation name="createOrderByValue" parameterOrder="parameters">
    <s0:input message="s1:createOrderByValue"/>
    <s0:output message="s1:createOrderByValueResponse"/>
    <s0:fault message="s1:MslvAsapWsSessionException" name="MslvAsapWsSessionException"/>
    </s0:operation>
    <s0:operation name="getServiceTypes" parameterOrder="parameters">
    <s0:input message="s1:getServiceTypes"/>
    <s0:output message="s1:getServiceTypesResponse"/>
    <s0:fault message="s1:MslvAsapWsSessionException" name="MslvAsapWsSessionException"/>
    </s0:operation>
    <s0:operation name="removeOrderByKey" parameterOrder="parameters">
    <s0:input message="s1:removeOrderByKey"/>
    <s0:output message="s1:removeOrderByKeyResponse"/>
    <s0:fault message="s1:MslvAsapWsSessionException" name="MslvAsapWsSessionException"/>
    </s0:operation>
    <s0:operation name="getOrderByKey" parameterOrder="parameters">
    <s0:input message="s1:getOrderByKey"/>
    <s0:output message="s1:getOrderByKeyResponse"/>
    <s0:fault message="s1:MslvAsapWsSessionException" name="MslvAsapWsSessionException"/>
    </s0:operation>
    <s0:operation name="jsrpGateway" parameterOrder="parameters">
    <s0:input message="s1:jsrpGateway"/>
    <s0:output message="s1:jsrpGatewayResponse"/>
    <s0:fault message="s1:MslvAsapWsSessionException" name="MslvAsapWsSessionException"/>
    </s0:operation>
    <s0:operation name="abortOrderByKey" parameterOrder="parameters">
    <s0:input message="s1:abortOrderByKey"/>
    <s0:output message="s1:abortOrderByKeyResponse"/>
    <s0:fault message="s1:MslvAsapWsSessionException" name="MslvAsapWsSessionException"/>
    </s0:operation>
    <s0:operation name="getOrderTypes" parameterOrder="parameters">
    <s0:input message="s1:getOrderTypes"/>
    <s0:output message="s1:getOrderTypesResponse"/>
    <s0:fault message="s1:MslvAsapWsSessionException" name="MslvAsapWsSessionException"/>
    </s0:operation>
    <s0:operation name="queryOrders" parameterOrder="parameters">
    <s0:input message="s1:queryOrders"/>
    <s0:output message="s1:queryOrdersResponse"/>
    <s0:fault message="s1:MslvAsapWsSessionException" name="MslvAsapWsSessionException"/>
    </s0:operation>
    <s0:operation name="setOrderByValue" parameterOrder="parameters">
    <s0:input message="s1:setOrderByValue"/>
    <s0:output message="s1:setOrderByValueResponse"/>
    <s0:fault message="s1:MslvAsapWsSessionException" name="MslvAsapWsSessionException"/>
    </s0:operation>
    <s0:operation name="startOrderByKey" parameterOrder="parameters">
    <s0:input message="s1:startOrderByKey"/>
    <s0:output message="s1:startOrderByKeyResponse"/>
    <s0:fault message="s1:MslvAsapWsSessionException" name="MslvAsapWsSessionException"/>
    </s0:operation>
    </s0:portType>
    <s0:binding name="MslvAsapWsSoapBinding" type="s1:MslvAsapWsServiceImpl">
    <s3:binding style="document" transport="http://www.openuri.org/2002/04/soap/jms/"/>
    <s0:operation name="suspendOrderByKey">
    <s3:operation soapAction="tns/suspendOrderByKey" style="document"/>
    <s0:input>
    <s3:body parts="parameters" use="literal"/>
    </s0:input>
    <s0:output>
    <s3:body parts="parameters" use="literal"/>
    </s0:output>
    <s0:fault name="MslvAsapWsSessionException">
    <s3:fault name="MslvAsapWsSessionException" use="literal"/>
    </s0:fault>
    </s0:operation>
    <s0:operation name="resumeOrderByKey">
    <s3:operation soapAction="tns/resumeOrderByKey" style="document"/>
    <s0:input>
    <s3:body parts="parameters" use="literal"/>
    </s0:input>
    <s0:output>
    <s3:body parts="parameters" use="literal"/>
    </s0:output>
    <s0:fault name="MslvAsapWsSessionException">
    <s3:fault name="MslvAsapWsSessionException" use="literal"/>
    </s0:fault>
    </s0:operation>
    <s0:operation name="createOrderByValue">
    <s3:operation soapAction="tns/createOrderByValue" style="document"/>
    <s0:input>
    <s3:body parts="parameters" use="literal"/>
    </s0:input>
    <s0:output>
    <s3:body parts="parameters" use="literal"/>
    </s0:output>
    <s0:fault name="MslvAsapWsSessionException">
    <s3:fault name="MslvAsapWsSessionException" use="literal"/>
    </s0:fault>
    </s0:operation>
    <s0:operation name="getServiceTypes">
    <s3:operation soapAction="tns/getServiceTypes" style="document"/>
    <s0:input>
    <s3:body parts="parameters" use="literal"/>
    </s0:input>
    <s0:output>
    <s3:body parts="parameters" use="literal"/>
    </s0:output>
    <s0:fault name="MslvAsapWsSessionException">
    <s3:fault name="MslvAsapWsSessionException" use="literal"/>
    </s0:fault>
    </s0:operation>
    <s0:operation name="removeOrderByKey">
    <s3:operation soapAction="tns/removeOrderByKey" style="document"/>
    <s0:input>
    <s3:body parts="parameters" use="literal"/>
    </s0:input>
    <s0:output>
    <s3:body parts="parameters" use="literal"/>
    </s0:output>
    <s0:fault name="MslvAsapWsSessionException">
    <s3:fault name="MslvAsapWsSessionException" use="literal"/>
    </s0:fault>
    </s0:operation>
    <s0:operation name="getOrderByKey">
    <s3:operation soapAction="tns/getOrderByKey" style="document"/>
    <s0:input>
    <s3:body parts="parameters" use="literal"/>
    </s0:input>
    <s0:output>
    <s3:body parts="parameters" use="literal"/>
    </s0:output>
    <s0:fault name="MslvAsapWsSessionException">
    <s3:fault name="MslvAsapWsSessionException" use="literal"/>
    </s0:fault>
    </s0:operation>
    <s0:operation name="jsrpGateway">
    <s3:operation soapAction="tns/jsrpGateway" style="document"/>
    <s0:input>
    <s3:body parts="parameters" use="literal"/>
    </s0:input>
    <s0:output>
    <s3:body parts="parameters" use="literal"/>
    </s0:output>
    <s0:fault name="MslvAsapWsSessionException">
    <s3:fault name="MslvAsapWsSessionException" use="literal"/>
    </s0:fault>
    </s0:operation>
    <s0:operation name="abortOrderByKey">
    <s3:operation soapAction="tns/abortOrderByKey" style="document"/>
    <s0:input>
    <s3:body parts="parameters" use="literal"/>
    </s0:input>
    <s0:output>
    <s3:body parts="parameters" use="literal"/>
    </s0:output>
    <s0:fault name="MslvAsapWsSessionException">
    <s3:fault name="MslvAsapWsSessionException" use="literal"/>
    </s0:fault>
    </s0:operation>
    <s0:operation name="getOrderTypes">
    <s3:operation soapAction="tns/getOrderTypes" style="document"/>
    <s0:input>
    <s3:body parts="parameters" use="literal"/>
    </s0:input>
    <s0:output>
    <s3:body parts="parameters" use="literal"/>
    </s0:output>
    <s0:fault name="MslvAsapWsSessionException">
    <s3:fault name="MslvAsapWsSessionException" use="literal"/>
    </s0:fault>
    </s0:operation>
    <s0:operation name="queryOrders">
    <s3:operation soapAction="tns/queryOrders" style="document"/>
    <s0:input>
    <s3:body parts="parameters" use="literal"/>
    </s0:input>
    <s0:output>
    <s3:body parts="parameters" use="literal"/>
    </s0:output>
    <s0:fault name="MslvAsapWsSessionException">
    <s3:fault name="MslvAsapWsSessionException" use="literal"/>
    </s0:fault>
    </s0:operation>
    <s0:operation name="setOrderByValue">
    <s3:operation soapAction="tns/setOrderByValue" style="document"/>
    <s0:input>
    <s3:body parts="parameters" use="literal"/>
    </s0:input>
    <s0:output>
    <s3:body parts="parameters" use="literal"/>
    </s0:output>
    <s0:fault name="MslvAsapWsSessionException">
    <s3:fault name="MslvAsapWsSessionException" use="literal"/>
    </s0:fault>
    </s0:operation>
    <s0:operation name="startOrderByKey">
    <s3:operation soapAction="tns/startOrderByKey" style="document"/>
    <s0:input>
    <s3:body parts="parameters" use="literal"/>
    </s0:input>
    <s0:output>
    <s3:body parts="parameters" use="literal"/>
    </s0:output>
    <s0:fault name="MslvAsapWsSessionException">
    <s3:fault name="MslvAsapWsSessionException" use="literal"/>
    </s0:fault>
    </s0:operation>
    </s0:binding>
    <s0:service name="MslvAsapWs">
    <s0:port binding="s1:MslvAsapWsSoapBinding" name="JmsSessionPort">
    <s3:address location="jms:///SAAS-1/Oracle/CGBU/Mslv/Asap/Ws?URI=SAAS-1.WebServiceQueue"/>
    </s0:port>
    </s0:service>
    </s0:definitions>

Maybe you are looking for

  • Compile REP file from RDF in the command line

    Is it possible to compile the REP file from an RDF in the command line? If so, do you have a simple example?

  • Deploying Web Application

    Hi I downloaded the Free JSP Editor version of Workshop, I really like it. However, is there a way to deploy the webapplication to the server from Eclipse for a project created using this version of the Workshop. thanks Anand

  • Java.exe CPU %

    Hi, We are running Resin Servlet runner on our web server. Our web site mostly serves out .XML documents using XSLT. The problem we periodically have is java.exe consumes 100% of the CPU until the web server stop responding. Restarting the servlet ru

  • Flex live Video Encoding

    Hai. I am developing a video chat application in flex. Can anbody help me in the video encoding part? I need the video to be encoded using ON2VP6 or H264 to get a better quality. How it can be done live using flex? Thanks, VivekVijayan

  • Transfering game on my i-mac to my notebook i-book g-4

    i have some games i would like to move to my i-book from my i-mac how do i do it and what cables do i need etc........