When to create a separate JMS Server

Gurus
Please provide/point to guidelines on when to create a separate JMS server within the Weblogic server 11g, the Pros and Cons of doing the same.
From Oracle JMS Guide for Weblogic , the main value add I am able to see is the separate Persistent store and a separate logical container for JMS resources related to my project. These will be important value additions since we will be using a shared environment where artifacts from multiple projects will be deployed.
I researched online , but could not get more inputs. Appreciate any pointers.
regards
Basu

There is a JMS Server and Persistent Store section in the JMS configuration best practices book.
http://docs.oracle.com/cd/E17904_01/web.1111/e13738/best_practice.htm#CACGFHDJ
Hope this is helpful to you.

Similar Messages

  • Exception when trying to Connect to JMS Server Remotely

    Hi,
    I get the following error when i am trying to connect to a JMS server over the network. Please help.
    Aug 7, 2009 12:58:10 PM com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init>
    WARNING: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: localhost; port: 3700"
    org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
    at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2690)
    at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2711)
    at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:261)
    at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:274)
    at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImp
    l.java:130)
    at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl
    .java:192)
    at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:181)
    at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:325)
    at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
    at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69)
    at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:127)
    at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:182)
    at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:339)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)
    at com.splwg.mpl.server.jms.JNDIJMSConnectionFactoryFactory.getConnectionFactory(JNDIJMSConnectionFactoryFactory
    .java:56)
    at com.splwg.mpl.server.jms.JMSUtilImpl.getConnectionFactory(JMSUtilImpl.java:75)
    at com.splwg.mpl.jms.queue.JMSSender.init(JMSSender.java:80)
    at com.splwg.mpl.sending.NewSenderManager.init(NewSenderManager.java:108)
    at com.splwg.mpl.sending.SameThreadSendingManager.initSenderManager(SameThreadSendingManager.java:353)
    at com.splwg.mpl.sending.SameThreadSendingManager.init(SameThreadSendingManager.java:154)
    at com.splwg.mpl.server.async.AsyncServer.init(AsyncServer.java:193)
    at com.splwg.mpl.server.MPLServer.init(MPLServer.java:386)
    at com.splwg.mpl.server.MPLServer.run(MPLServer.java:547)
    at com.splwg.mpl.server.MPLServer.runMPL(MPLServer.java:535)
    at com.splwg.mpl.server.MPLServer.main(MPLServer.java:524)
    Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused: connect
    at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:347)
    at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:244)
    ... 22 more
    Caused by: java.net.ConnectException: Connection refused: connect
    at sun.nio.ch.Net.connect(Native Method)
    at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:464)
    at com.sun.corba.ee.impl.orbutil.ORBUtility.openSocketChannel(ORBUtility.java:105)
    at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:332)
    ... 23 more
    Aug 7, 2009 12:58:16 PM com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init>
    WARNING: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: localhost; port: 3700"
    org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
    at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2690)
    at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2711)
    at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:261)
    at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:274)
    at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImp
    l.java:130)
    at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl
    .java:192)
    at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:181)
    at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:325)
    at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
    at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69)
    at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:127)
    at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:182)
    at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:339)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)
    at com.splwg.mpl.server.jms.JNDIJMSConnectionFactoryFactory.getConnectionFactory(JNDIJMSConnectionFactoryFactory
    .java:56)
    at com.splwg.mpl.server.jms.JMSUtilImpl.getConnectionFactory(JMSUtilImpl.java:75)
    at com.splwg.mpl.jms.queue.JMSSender.init(JMSSender.java:80)
    at com.splwg.mpl.sending.NewSenderManager.init(NewSenderManager.java:108)
    at com.splwg.mpl.sending.SameThreadSendingManager.initSenderManager(SameThreadSendingManager.java:353)
    at com.splwg.mpl.sending.SameThreadSendingManager.init(SameThreadSendingManager.java:154)
    at com.splwg.mpl.server.async.AsyncServer.init(AsyncServer.java:193)
    at com.splwg.mpl.server.MPLServer.init(MPLServer.java:386)
    at com.splwg.mpl.server.MPLServer.run(MPLServer.java:547)
    at com.splwg.mpl.server.MPLServer.runMPL(MPLServer.java:535)
    at com.splwg.mpl.server.MPLServer.main(MPLServer.java:524)
    Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused: connect
    at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:347)
    at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:244)
    ... 22 more
    Caused by: java.net.ConnectException: Connection refused: connect
    at sun.nio.ch.Net.connect(Native Method)
    at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:464)
    at com.sun.corba.ee.impl.orbutil.ORBUtility.openSocketChannel(ORBUtility.java:105)
    at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:332)
    ... 23 more

    The googleapi.jar contains copies of some javamail classes. Here a few I found in my output:
    javax.mail.event.MessageCountListener from googleapi.jar
    javax.mail.Session from googleapi.jar
    javax.mail.MessagingException from googleapi.jar
    javax.mail.NoSuchProviderException from googleapi.jar
    This particular google api is the old SOAP google service that is no longer allowing new registrations, but still has support for existing API key holders, like me :-). Thought this might be a common jar in most libraries, so worth mentioning.
    Don't forget, you can debug your loaded classes with java -verbose MyApp to find those rogue libraries.

  • Integrated ITS in a Separate App Server (DI) for Security and LoadBalancing

    Hi Experts,
    I have a specific requirement for ITS Configuration.
    1. Production Server ( CI + DB ) -> Existing
    [ ERP6.0 ]
    OS : Solaris 10
    DB : oracle 10.2.0.2
    H/W: PRIMEPOWER650
    Unicode Enabled
    2. Application Server ( DI ) --> to be made ( and to be used exclusively for Web users)
    OS : Windows2003 sv
    H/W: RX200 S3
    x64
    MEM: 8GB
    No. 1 is existing Production Server Environment.
    The Customer Requirement.
    The Customer wants to use the ITS . But he doesn't want the existing Production Server to be disturbed for the same for 2 reasons. [ Security and Load Balancing ]
    We are planning to create a Separate Application Server (DI) to work as ITS.
    As the Kernel is 700. The ITS is integrated into the Production Server by Default.
    We have written to SAP and have asked whether the Production Server ITS can be disabled and the Separate DI's ITS be enabled so that the NEW ( No.2 ) Application Server will be used for ITS activities.
    SAP has replied saying the Integrated ITS cannot be disabled at the Production Server. Instead as an alternative we can create a Logon Group (using transaction SMLG) and divert all the Web users to the Separated DI (No.2). We have decided to go according to SAP.
    Now I have the following questions :
    1. The Operating Systems of the Production Server (No.1) and the Separate AP (No. 2)
    are different. ( Are there any complexities involved or must do points to be taken care. )
    2. Brief / MUST DO tasks at the Production Server Environment and Must do tasks at the DI Environment.
    I hope someone has already done some few installations on the above combination, if so, request to please share me your ideas.
    Thanks in anticipation
    Best Regards,
    Paguras
    PS :
    my earlier discussion on the same topic on this community.
    ITS Specific Requirement

    Hi Markus,
    Thanks for the Reply.
    We have the following 2 plans :
    Plan-01.
    As you have advised, we will try to disable ITS of CI and enable ITS of DI.
    Plan-02.
    If Plan-01 could be worked out successfully, well implement as per SAP suggests. Creating a Logon Group and divert all the web users to the DI alone.
    To deactivate ITS on CI, you have mentioned to make sure, that the  system does not listen on the HTTP port (transaction SMICM) on the Servers
    BTW, I have seen a parameter called <b>ITSP/ENABLE</b>. if we deactivate this parameter at CI & DB and then activate the same parameter at DI.
    My questions to you :
    1. Shall we go for Plan-01 ignoring what SAP OSS has said. ?
    2. Disable ITSP/Enable Parameter  -> CI & DB
        Enable ITSP/Enable Parameter   -> DI          has to be implemented .
    Thanks & best Regards,
    Paguras
    PS: Sorry for always pounding you with so many questions on the same topic.
    SAP Help on ITSP / enable parameter
    itsp/enable
    You use this parameter to deactivate (0) or activate (1) the integrated ITS. Even if the integrated ITS is activated, it only accesses system resources when it is actually used. Nevertheless, it can make sense to deactivate it to prevent users from accessing the SAP system with SAP GUI for HTML via special application servers (such as batch or update instances). Since the conversion of SAP screens into HTML pages uses additional CPU time, it makes sense to reserve a number of dedicated application servers to be used with SAP GUI for HTML and to use a special logon group to balance the load between them.

  • Foreign JMS Server Persistance\Retry in case Remote JMS Provider goes down

    Hi All
    I would need more clarity on this. How does the Foreign JMS Server behave in case the remote JMS provider goes down. Does it take the message from the Publishing Proxy Service and retries\persists the JMS Message till the remote provide is up?
    Please let us know. This would effect our design as retrial is very important here. Thanks

    If you want to provide guaranteed delivery with automatic retries when using remote JMS implementations, there are multiple ways to implement it:
    1. While reading from a foreign JMS destination
    Create a Foreign JMS server using transactional drivers (use XA in case of JMS). The messages remain on remote server JMS queue and OSB proxy polls the message directly on remote server. So if Remote Server is down OSB will not be able to read the message. Once remote server is up OSB will pick up the message (as long as foreign JMS server provides persistence and maintains the messages in the queue during a server restart). In case of error in OSB foreign queue can do retry if it provides a retry mechanism.
    2. While writing the message to a foreign JMS destination
    a. Use a foreign JMS server using transactional connection. Put the retry mechanism in OSB Business service which writes to the foreign JMS/MQ queue. In case of failure Business Service can retry based on configuration. If you want to provide guaranteed delivery then create a local JMS queue to store the messages. So when remote destination is down for a long time undelivered messages will be rolled back to the local queue. You can put retry mechanism on the local queue.
    b. Use a messaging bridge which will write the messages to the remote destination. You can configure retry delivery rules in messaging bridge so once busienss service writes the message to the bridge, a SAF agent will ensure the delivery to remote destination whenever it is up.

  • Foreign JMS Server vs Messaging bridge

    Could any body tell me which one is the best Whether Foreign JMS Server or Messaging bridge for connecting Weblogic to IBM MQ Series.I am trying to use foreign jms server but i dont know how to post the message to that queue i created in foreign jms server..

    Hi,
              For sending messages non-transactionally, foreign JMS server is sufficient. For sending messages transactionally using standard JTA transactions, the simplest way is to send them on the server and reference the foreign JMS through an EJB resource reference. See the the following FAQ for a walk-through of the various options, including guidance on when to use a bridge:
              http://e-docs.bea.com/wls/docs81/faq/interop.html
              Tom

  • Do I need a Foreign JMS Server?

              Initially, I had an exploded web application, an ejb jar, a jms server, a connection
              factory and a queue all deployed under one weblogic instance. I am now trying
              to move the jms configuration to another machine running weblogic. However, I
              am unsure whether I need to configure a Foreign JMS Server on the initial weblogic
              instance. I have tried to do so and I cannot successfully start the connection
              from my web/ejb app (i.e., myQueueConnection.start() throws an exception - weblogic.jms.common.JMSException:
              Connection not found).
              I saw a thread here about changing the names of the JMS Servers, so I configured
              my web server with a foreign jms server (ForeignMessageServer) and I configured
              one foreign connection factory and one foreign destination. The local jndi names
              of these are unique and different from the remote jndi name. The remote jndi names
              match the names of the connection/destination on the app server (my 2nd server).
              I am using the url of the web server as my provider url and the foreign connection
              factory local jndi name to look up the connection.
              I have two questions:
              Is it necessary to use a foreign jms server configuration to implement this structure?
              If a foreign jms server configuration is necessary, am I going about this correctly?
              Thanks,
              John
              

    It certainly will work. Basically, all it does is move information like the
              JNDI provider name and URL from your deployment descriptors into config.xml.
              For a lot of applications, that's a big help. You can use the "Foreign JMS
              Provider" support anywhere you want to create a JNDI entry on your local
              server that points to something else. You can even use it to point to a JMS
              queue, topic, or connection factory in the same cluster, or the same WLS
              server if you want. I do this for testing so I don't have to have different
              versions of my EJB for different environments.
              As for the bridge, it depends on whether you need to interact with the JMS
              provider synchronously or asynchronously. When you use the bridge, you first
              put the message on one JMS queue or topic, and the bridge copies it to the
              other. So, if the foreign provider is down, you can still send messages.
              However, using the bridge adds an extra "hop" which will slow performance.
              greg
              <[email protected]> wrote in message news:[email protected]...
              > Hi Tom,
              >
              > If I have 2 WLS servers: server1 and server2 and they are NOT in the same
              > cluster. server1 wants to send a JMS message to server2. I know I can
              > achieve the desired result using your 3 suggestions below but would
              using
              > foreign JMS server works as well? When should I use foreign JMS server
              > instead of a messaging bridge?
              >
              > Thanks,
              >
              > Vincent
              >
              >
              >
              > "Tom Barnes" <[email protected]> wrote in message
              > news:[email protected]...
              > > If both weblogic servers participate in the same cluster
              > > there is no additional configuration needed.
              > > All servers in cluster share the same JNDI
              > > name space. Simply specifying a JNDI name
              > > (as you already must have done) is enough
              > > for any server in the cluster, or any client connected
              > > to the cluster, to find a JNDI resource that is hosted
              > > on any server in the cluster (such as queue).
              > > This location transparency is one of the primary
              > > benefits of using clusters.
              > >
              > > If the MDB is in a different cluster than its
              > > source destination, then you have three choices
              > > (1) Change the MDB weblogic descriptor to specify
              > > a URL that resolves to any one of the
              > > addresses of a WL server in the remote cluster.
              > > I don't recall the name of the URL field,
              > > but it is in the weblogic descriptor, and
              > > is documented in the EJB (MDB) programmer's
              > > guide.
              > > (2) Configure wrappers that refer to the
              > > remote JMS resources in the cluster, and change
              > > the MDB descriptors to point to the jndi
              > > locations you configured for the wrapped
              > > connection factory and wrapped destination.
              > > (3) Configure a messaging bridge that
              > > moves from the remote destination to
              > > a local destination (which, in turn,
              > > the MDB consumes from).
              > >
              > > Tom
              > >
              > > John Owen wrote:
              > >
              > > > Initially, I had an exploded web application, an ejb jar, a jms
              server,
              > a connection
              > > > factory and a queue all deployed under one weblogic instance. I am now
              > trying
              > > > to move the jms configuration to another machine running weblogic.
              > However, I
              > > > am unsure whether I need to configure a Foreign JMS Server on the
              > initial weblogic
              > > > instance. I have tried to do so and I cannot successfully start the
              > connection
              > > > from my web/ejb app (i.e., myQueueConnection.start() throws an
              > exception - weblogic.jms.common.JMSException:
              > > > Connection not found).
              > > >
              > > > I saw a thread here about changing the names of the JMS Servers, so I
              > configured
              > > > my web server with a foreign jms server (ForeignMessageServer) and I
              > configured
              > > > one foreign connection factory and one foreign destination. The local
              > jndi names
              > > > of these are unique and different from the remote jndi name. The
              remote
              > jndi names
              > > > match the names of the connection/destination on the app server (my
              2nd
              > server).
              > > > I am using the url of the web server as my provider url and the
              foreign
              > connection
              > > > factory local jndi name to look up the connection.
              > > >
              > > > I have two questions:
              > > >
              > > > Is it necessary to use a foreign jms server configuration to implement
              > this structure?
              > > > If a foreign jms server configuration is necessary, am I going about
              > this correctly?
              > > >
              > > > Thanks,
              > > > John
              > >
              >
              >
              

  • MDB connecting to Foreign JMS server in WL8.1

    Hello,
              I have this problem that I am hoping someone can help me with. There is a
              MDB deployed in a local WL8.1 that is trying to connect to a Foreign JMS
              Server which is also a WL8.1 running in a remote server. This MDB is
              attempting to subscribe to a topic hosted by that foreign server. In the
              local WL8.1 I created a Foreign JMS Server via the adminconsole and mapped
              the connection factory as well as destinations to the Foreign JMS Server.
              The MDB (via its deployment descriptor) only refers to the local JNDI names
              of the ConnectionFactory and Topic. Here are the scenarios concerning
              security:
              1) When security is turned off (user is in group everyone) everything works
              fine. Messages published to the foreign Topic are received by the MDB in
              the local WL8.1 server and processed.
              2) When a security policy is applied to the Topic (via the remote
              adminconsole), the MDB in the local server gets a 'permission denied'. I
              now have to get around this by defining a principle for the MDB to run as
              and to map the credentials of this principle to that of the user in the
              remote environment with access permissions to the Topic.
              3) When I specify the security identity of my MDB, its JNDI lookup of the
              Topic fails with 'not found'.
              4) Even when the security policy in the remote server is reverted back to
              'everyone' (effectively turning security off) but leaving the MDB running as
              the security principle, it still cannot find the Topic.
              I hope this is something that people have seen and dealt with before.
              Thanks for any and all help anyone can provide. I have also included the
              deployment descriptors for this MDB:
              <ejb-jar>
              <enterprise-beans>
              <message-driven>
              <ejb-name>MDB</ejb-name>
              <ejb-class>sample.class.MDB</ejb-class>
              <transaction-type>Container</transaction-type>
              <message-driven-destination>
              <destination-type>javax.jms.Topic</destination-type>
              </message-driven-destination>
              <security-identity>
              <run-as>
              <role-name>OutsideJMSUser</role-name>
              </run-as>
              </security-identity>
              </message-driven>
              </enterprise-beans>
              <assembly-descriptor>
              <security-role>
              <role-name>OutsideJMSUser</role-name>
              </security-role>
              </assembly-descriptor>
              </ejb-jar>
              <weblogic-ejb-jar>
              <weblogic-enterprise-bean>
              <ejb-name>MDB</ejb-name>
              <message-driven-descriptor>
              <pool>
              <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
              </pool>
              <destination-jndi-name>ForeignTopic</destination-jndi-name>
              <connection-factory-jndi-name>ForeignConnectionFactory</connection-factory-j
              ndi-name>
              </message-driven-descriptor>
              <jndi-name>MDB</jndi-name>
              </weblogic-enterprise-bean>
              <security-role-assignment>
              <role-name>OutsideJMSUser</role-name>
              <principal-name>OutsideJMSUser</principal-name>
              </security-role-assignment>
              </weblogic-ejb-jar>
              

    Thanks for the suggestion Greg. I have enabled trust between the two
              domains and that has certainly cut down the variations of SecurityExceptions
              that I get. Now I am consistently only getting a JMSSecurityException with
              a access denied to the topic. I believe I have the credential mapped
              correctly between the run-as local user and the remote authorized user.
              Unfortunately the exception does not specify what username was rejected, it
              would have been useful in determining the next debugging step to take.
              I think you're right, I should engage the security forum for this. Thanks
              again for the help.
              "Greg Brail" <[email protected]> wrote in message
              news:[email protected]...
              > Hmm. The security people (on weblogic.developer.interest.security) might
              > have to help you here, too. When you set the "runAs" identity for the MDB,
              > it's doing everything, including the JNDI lookup, under that identity. So
              if
              > that identity is one that's recognized by the remote domain, then you
              should
              > be OK. One way to make your local identity recognized by the remote domain
              > is to make your domains trusted, but you may wish not to do that.
              >
              > greg
              >
              > "Steve Chan" <[email protected]> wrote in message
              > news:[email protected]...
              > > Hello,
              > >
              > > I have this problem that I am hoping someone can help me with. There is
              a
              > > MDB deployed in a local WL8.1 that is trying to connect to a Foreign JMS
              > > Server which is also a WL8.1 running in a remote server. This MDB is
              > > attempting to subscribe to a topic hosted by that foreign server. In
              the
              > > local WL8.1 I created a Foreign JMS Server via the adminconsole and
              mapped
              > > the connection factory as well as destinations to the Foreign JMS
              Server.
              > > The MDB (via its deployment descriptor) only refers to the local JNDI
              > names
              > > of the ConnectionFactory and Topic. Here are the scenarios concerning
              > > security:
              > >
              > > 1) When security is turned off (user is in group everyone) everything
              > works
              > > fine. Messages published to the foreign Topic are received by the MDB
              in
              > > the local WL8.1 server and processed.
              > >
              > > 2) When a security policy is applied to the Topic (via the remote
              > > adminconsole), the MDB in the local server gets a 'permission denied'.
              I
              > > now have to get around this by defining a principle for the MDB to run
              as
              > > and to map the credentials of this principle to that of the user in the
              > > remote environment with access permissions to the Topic.
              > >
              > > 3) When I specify the security identity of my MDB, its JNDI lookup of
              the
              > > Topic fails with 'not found'.
              > >
              > > 4) Even when the security policy in the remote server is reverted back
              to
              > > 'everyone' (effectively turning security off) but leaving the MDB
              running
              > as
              > > the security principle, it still cannot find the Topic.
              > >
              > > I hope this is something that people have seen and dealt with before.
              > > Thanks for any and all help anyone can provide. I have also included
              the
              > > deployment descriptors for this MDB:
              > >
              > > <ejb-jar>
              > > <enterprise-beans>
              > > <message-driven>
              > > <ejb-name>MDB</ejb-name>
              > > <ejb-class>sample.class.MDB</ejb-class>
              > > <transaction-type>Container</transaction-type>
              > > <message-driven-destination>
              > > <destination-type>javax.jms.Topic</destination-type>
              > > </message-driven-destination>
              > > <security-identity>
              > > <run-as>
              > > <role-name>OutsideJMSUser</role-name>
              > > </run-as>
              > > </security-identity>
              > > </message-driven>
              > > </enterprise-beans>
              > >
              > > <assembly-descriptor>
              > > <security-role>
              > > <role-name>OutsideJMSUser</role-name>
              > > </security-role>
              > > </assembly-descriptor>
              > >
              > > </ejb-jar>
              > >
              > > <weblogic-ejb-jar>
              > > <weblogic-enterprise-bean>
              > > <ejb-name>MDB</ejb-name>
              > > <message-driven-descriptor>
              > > <pool>
              > > <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
              > > </pool>
              > > <destination-jndi-name>ForeignTopic</destination-jndi-name>
              > >
              > >
              >
              <connection-factory-jndi-name>ForeignConnectionFactory</connection-factory-j
              > > ndi-name>
              > > </message-driven-descriptor>
              > > <jndi-name>MDB</jndi-name>
              > > </weblogic-enterprise-bean>
              > >
              > > <security-role-assignment>
              > > <role-name>OutsideJMSUser</role-name>
              > > <principal-name>OutsideJMSUser</principal-name>
              > > </security-role-assignment>
              > >
              > > </weblogic-ejb-jar>
              > >
              > >
              >
              >
              

  • Problem with SCs that created before the Name Server was configured

    Hello,
    I have created an SC and developed it.
    When I created it, the Name Server wasn't configured and because of that, when I created new DC for this SC I needed to write the vendor manually. Lets assume I wrote example.org.
    Sometime after I did configured the Name Server and I reserved example.org as a namespace prefix.
    When I create new SC and new DCs in it everything is OK: Instead of writing example.org as my vendor I can choose from a combo box between sap.com and my own which is example.org.
    The problem arises with the SC that has been developed before the Name server was configured: If I create new DC for it the vendor is shaded with sap.com inside with no option to change it, even though the previous DCs for this SC were created under the vendor example.org (which I entered manually).
    I assume I can (with a lot of manual work) create new SC and move the DCs (or only their code) to the newly created SC, where I have the option to choose, but I am looking for more simpler solution. For example, changing a certain configuration file at the SC or so.
    Anyone has an idea?
    Thank you in advance,
    Roy

    Anyone...?

  • MDBs failed to connect to remote JMS server

    Hi,
              We currently have 2 clusters: one is a regular cluster (cluster1) and the other is JMS cluster (cluster2). Our JMS server and filestore are targeted to a migratable server in JMS cluster.
              In our weblogic-ejb-jar.xml, we added element <provider-url> to the <message-driven-descriptor> to allow JMS remote connection as follows:
              <weblogic-enterprise-bean>
                   <ejb-name>MyBean</ejb-name>
                   <message-driven-descriptor>
                        <destination-jndi-name>MyTopic</destination-jndi-name>
              <provider-url>t3://myhost:19009,myhost:19011</provider-url>
              <connection-factory-jndi-name>MyConnectionFactory</connection-factory-jn
              di-name>
                   </message-driven-descriptor>
              </weblogic-enterprise-bean>
              When we deployed our application, the Connection Status of MyBean showed "disconnected". I have tried different values (t3://myhost:19009;t3://myhost:19011) and
              (t3://myhost:19009) but got the same result.
              When I re-targeted the JMS server and filestore to a regular server (instead of migratable server), I was able to connect remotely. But because we want to be able to migrate our JMS server (auto and manually), I have to target it to a migratable server.
              I could not figure out why my MDBs failed to connect to a remote JMS server when it is targeted to a migratable server? Is there a restriction that we have to target to a regular server in order to connect remotely or I'm doing something wrong?
              Any help would be greatly appreciated.
              Thanks,
              Thao

    I'm using WL9.2 and my migratable server is actually up and running (is that what you mean about booted?).                    I meant checking your log files to make sure that the JMS server itself actually booted, not checking that the host WL server was up. (For example you should see INFO messages indicating that the JMS server has loaded "X" records from its persistent store).
              >>> Could you elaborate on the known problem?
              9.x MDBs have special code for enhanced handling of remote distributed destinations. I'm guessing that this code is somehow causing problems when the remote JMS server is migratable. I don't have enough information to elaborate further than that.
              >>> What else I can try?
              Beyond contacting customer support, I'm not sure.
              Tom

  • JMS Server Message Buffer Size & Thresholds and Quotas settings

    On WLS10MP1,
    For persistent messages:
    1.Does "JMS Server Message Buffer" setting serve the same purpose as "Bytes Threshold High" under Threshold ?
    2.If no, can someone explain the difference pls.
    Many thanx,

    Message Buffer Size relates to the number of message the JMS server keeps in the memory. The value of this determines when the server should start paging the message out of memory to a persistence store. So this is directly related with the memory/storage issue and the size of messages.
    Bytes Threshold High relates to the performance of the JMS server. When this limit is reached JMS server starts logging the message and may even instruct he producer to slow down the message input.
    So the if you get Bytes Threshold High messages that means you should check on your consumer (MDB who is picking up messages from the que), and try to increase its performance.
    However if your Message Buffer Size is crossing limits then you should think of increasing the momory so that more messages can be kept in memory and disck IO can be reduce.
    Anyone wants to add something more to it?

  • Problem when we created the managed server to configure different ports.

    I am trying to configure different ports for admin console and my communication service as we can’t share admin port to the outside world.
    So that only admin can access admin console using admin port.
    And out side clients can access my webapplication using different port.
    For this i have created the managed server in weblogic.and I deployed the application on managed server.
    Now admin server is running on 8001 port and my Communication Service application is running on 7001 port.
    But when I tried to configure MBeans related to myCommunicationServiceApplication those were disapper on admin console. And the other wlng services are appearing on admin console.
    1. Since my application deployed on managed server MBeans registration happened from myapplication hence it’s disappear on admin console.
    Now If I want to configure Mbeans (related to my communication service) how can I configure it?
    2. My communication service using configurationStore module and other wlng services.
    When I tried to start my application on managed server I got the below error:
    <Apr 28, 2009 12:22:44 PM IST> <Error> <Deployer> <BEA-149231> <dscp11166.TechMahindra.com> <Unable to set the activation state to true for the application 'wlng_nt_qualcomm_active_mediation [Version=1.0]'.
    com.bea.wlcp.wlng.api.storage.configuration.ConfigurationException: Configuration store module is not available.
    3. I tried to target all wlngResources to manged server by editing config.xml file.
    Then all wlng services disappears on admin console. If this is the case how can I configure container/account services on wlng?
    I have created the Basicweblogic domain.
    Below is the config.xml for reference.
    "QualcommServer" is managed server name.
    Can any one please suggest me how to configure this kind of scenarios?
    <server>
    <name>AdminServer</name>
    <machine>new_Machine_1</machine>
    <listen-port>8001</listen-port>
    <default-iiop-user>weblogic</default-iiop-user>
    <default-iiop-password-encrypted>{3DES}W8nBdoJPRZ8TkwcXwAZoxA==</default-iiop-password-encrypted>
    <listen-address>localhost</listen-address>
    </server>
    <server>
    <name>QualcommServer</name>
    <machine>new_Machine_1</machine>
    <listen-address>localhost</listen-address>
    <server-start>
    <java-vendor>Sun</java-vendor>
    <java-home>C:\Program Files\Java\jdk1.6.0</java-home>
    <class-path>C:\bea\wlng400\server\lib\weblogic.jar;C:\bea\wlng_pds400\lib\wlng\wlng.jar</class-path>
    <bea-home>C:\bea</bea-home>
    <username>weblogic</username>
    <password-encrypted>{3DES}W8nBdoJPRZ8TkwcXwAZoxA==</password-encrypted>
    </server-start>
    </server>
    <embedded-ldap>
    <name>managedserver</name>
    <credential-encrypted>{3DES}9q80YuFJueVVJxoWduJA1OGhbqk14EpgQWWyTrzlmxo=</credential-encrypted>
    </embedded-ldap>
    <configuration-version>10.0.1.0</configuration-version>
    <app-deployment>
    <name>wlng_nt_session#4.0</name>
    <target>QualcommServer</target>
    <module-type>ear</module-type>
    <source-path>C:\bea\wlng400/applications/wlng_nt_session.ear</source-path>
    <security-dd-model>CustomRolesAndPolicies</security-dd-model>
    </app-deployment>
    <app-deployment>
    <name>interceptors</name>
    <target>QualcommServer</target>
    <module-type>ear</module-type>
    <source-path>C:\bea\wlng400/applications/interceptors.ear</source-path>
    <security-dd-model>CustomRolesAndPolicies</security-dd-model>
    </app-deployment>
    <app-deployment>
    <name>wlng_prm</name>
    <target>QualcommServer</target>
    <module-type>ear</module-type>
    <source-path>C:\bea\wlng400/applications/wlng_prm.ear</source-path>
    <security-dd-model>CustomRolesAndPolicies</security-dd-model>
    </app-deployment>
    <app-deployment>
    <name>wlng_nt_qualcomm_active_mediation#1.0</name>
    <target>QualcommServer</target>
    <module-type>ear</module-type>
    <source-path>servers\AdminServer\upload\wlng_nt_qualcomm_active_mediation.ear</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    </app-deployment>
    <machine>
    <name>new_Machine_1</name>
    <node-manager>
    <name>new_Machine_1</name>
    <listen-address>localhost</listen-address>
    </node-manager>
    </machine>
    <jms-server>
    <name>JMSServer-AdminServer</name>
    <target>AdminServer</target>
    </jms-server>
    <jms-system-resource>
    <name>WLNGJMSResource</name>
    <target>QualcommServer</target>
    <descriptor-file-name>jms/wlng-jms.xml</descriptor-file-name>
    </jms-system-resource>
    <custom-resource>
    <name>networktier</name>
    <target>AdminServer</target>
    <descriptor-file-name>custom/nt.xml</descriptor-file-name>
    <resource-class>com.bea.wlcp.wlng.management.descriptor.resource.WlngTierResource</resource-class>
    <descriptor-bean-class>com.bea.wlcp.wlng.management.descriptor.bean.WlngTierBean</descriptor-bean-class>
    </custom-resource>
    <custom-resource>
    <name>wlng-edr</name>
    <target>AdminServer</target>
    <descriptor-file-name>custom/wlng-edr.xml</descriptor-file-name>
    <resource-class>com.bea.wlcp.wlng.management.descriptor.resource.WlngEdrResource</resource-class>
    <descriptor-bean-class>com.bea.wlcp.wlng.management.descriptor.bean.WlngEdrBean</descriptor-bean-class>
    </custom-resource>
    <admin-server-name>AdminServer</admin-server-name>
    <jdbc-system-resource>
    <name>wlng.datasource</name>
    <target>QualcommServer</target>
    <descriptor-file-name>jdbc/wlng-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    <jdbc-system-resource>
    <name>wlng.localTX.datasource</name>
    <target>QualcommServer</target>
    <descriptor-file-name>jdbc/wlng-localTX-jdbc.xml</descriptor-file-name>
    </jdbc-system-resource>
    Thanks,
    Srinu Babu P

    Dear Nariharan,
    Today I faced a simlar issue, and this SAP Note helped me fix it: 1966807 - Duplication of AET table records in change processing
    In my case, cardinality of AET table was 1:1, and I was getting duplicate PARENT_ID every time when trying to create a subsequent service request for my activity.
    Regards,
    Andrew

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

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

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

  • JMSHelper throws 'JMS server is not targetted' creating distributed queue

    I am trying to use the 8.1 weblogic.jms.extensions.JMSHelper to create a distributed queue. The target JMS servers are all migratable servers. When calling method createDistributedQueueAsync() I get a JMSException thrown compaining that the [first] JMS server is not targetted. Looking at the code provided in [http://forums.bea.com/bea/thread.jspa?messageID=200023386] which is based on the JMSHelper class source, the exception may be thrown because the target MBean is of class MigratableTargetMBean, whereas the JMSHelper is expecting class TargetMBean. Yet, the 9.0 documentation (which at least documents it) suggests that MigratableTargetMBean is derived from TargetMBean
              Does anyone have experience of this issue or its resolution, short of crafting the code by hand as per the above-referenced reply?

    Hi,
    Just to remember the configuration: 2 managed servers configured as cluster that should be deployed on 2 different machine.
    Following summary of the tests:
         - node manager + admin server + 1 managed server running on the first machine --> server failed to init with error "Server is not in the majority cluster partition"
         - node manager + admin server + 2 managed servers running on the one machine --> servers are running without errors
         - node manager + admin server + 1 managed server running on the first  machine / node manager runs on the second machine --> server on the first machine runs without errors without the famous error ' Server is not in the majority cluster partition'.
    Bottom line, seems that if the node manager is not running on the remote machine, the cluster is not in a stable state and so the single managed server failed to initialize.
    Is it according the documentation / expectations ?
    Thanks,
    Yaakov

  • HT201269 When I try to setup my new iPad air, I go through all the steps for the iCloud sign-in and choosing security questions and what not. But after I hit the agree to the terms and conditions... It says Apple ID could not be created because of a serve

    When I try to setup my new iPad air, I go through all the steps for the iCloud sign-in and choosing security questions and what not. But after I hit the agree to the terms and conditions... It says Apple ID could not be created because of a server error. Have no clue what to do... I've restarted the iPad and get the same message. But my internet works just fine.

    1. Turn router off for 30 seconds and on again
    2. Settings>General>Reset>Reset Network Settings

  • Apple ID couldn't be created because of a server error when i try to restore from a backup

    Apple ID couldn't be created because of a server error when i try to restore from a backup from iCloud?
    Also my mail works fine, and if i bypass everything and sign in tomy apple id in settings it will work!

    I don't know, but it's not working for me.
    I went to Apple ID website and everything is fine there, But I can't restore my phone from iCloud.

Maybe you are looking for