Create a new session bean in a Composite Application DC.

Hi,
I need to create a new Stateless Session Bean in our Composite Application DC which already has some Application services and we need to use these services in the new session bean.
Another requirement is that we need to provide a custom JNDI Name for this Session Bean.
The problem here is that I am not able to see the new session bean in the JNDI browser.
I have tried to provide a JNDI name for the new EJB by adding the <jndi-name> to the ejb-j2ee-engine.xml file in the ejbmodule dc.
Can anyone please provide a resolution for this problem ASAP as I am now stuck up and not able to proceed with my development.
I am working on CE 7.1 SP6 and NWDS 7.1 CE SP 6.
Regards,
Manish

Hi Snehal.
Thanks for your reply!
I need to use this EJB in a seperate Composite DC at runtime and that s why I need a custom JNDI name as there can be any no of implementations for the interface implemented by these EJB's but at runtime we need to pick up a specific implementation for which a Custom JNDI name is alloted.
Can you please provide the steps for including the JNDI name in "ejb-j2ee-engine.xml" as whenever I try to create an entry in the file and deploy the same, its not visible in the JNDI browser.
Please reply ASAP.
Regards,
Manish

Similar Messages

  • Creating multiple stateful session beans from a java client. (EJB 3.0)

    I'm having difficulties with the following:
    To access the ShoppingCartBean, I have to put the following annotation in my standalone java client:
    @EJB
    private static ShoppingCartRemote shoppingCartBean;
    The static must be there, thus only one ShoppingCartBean will exist within my java client. But as the ShoppingCartBean is a stateful session bean, I want to be able to get different beans of the same type.
    What is the correct way to do this in EJB 3.0?

    Great question. Because Home interfaces have been removed for the EJB 3.0 simplified
    API, stateful session bean creation happens as a side-effect of injection. However, the
    same is true of EJB 3.0 business interface lookups. The easiest way to create additional
    stateful session beans is to lookup the same dependency that was declared via your
    @EJB annotation.
    E.g.,
    // Assuming the declaring class is pkg1.ShoppingCartClient.java
    InitialContext ic = new InitialContext();
    ShoppingCartRemote scr1 = (ShoppingCartRemote)
    ic.lookup("java:comp/env/pkg1.ShoppingCartClient/shoppingCartBean");
    Note that the name relative to java:comp/env is the default associated with your
    @EJB annotation since the name() attribute wasn't used. Alternatively, you
    could have used :
    @EJB(name="scb") private static ShoppingCartRemote shoppingCartBean;
    InitialContext ic = new InitialContext();
    ShoppingCartRemote scr1 = (ShoppingCartRemote) ic.lookup("java:comp/env/scb");
    Yet another alternative is to declare the @EJB at the class-level. This just defines
    the dependency without any injection, which is fine if you want to create a bunch of
    them via lookup anyway.
    @EJB(name="scb", beanInterface=ShoppingCartRemote.class)
    public class .... {                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • How to create a new session in JSP file

    Usually a child IE window uses same session with parent window. Dose someone know how to create a new session when creating a new IE window by clicking a URL in parent window? The web page is writen by jsp file.

    I am not sure of your question. Are you wanting to have 2 Session objects (one for the parent window and another for the child)?
    A session is usually created once per client and is stored on the server the session id is carried around in a cookie or a URL rewrite so that everytime the user submits a page you will be able to store/access information.
    // this will create a new session object if one doesn't already exist.
    HttpServletRequest.getSession( true );
    Hope this helps

  • NPE creating a new session on WebLogic Server 9.2

    We're getting the following stack trace from WebLogic Server 9.2 when a page gets hit.
    It appears to be a clustering error when creating a new session.
    When there is only a single server left running, the pages are served correctly.
    Any thoughts appreciated.
    2009-01-27 11:13:47,423 [ExecuteThread: '12' for queue: 'weblogic.kernel.Default'] ERROR com.vignette.portal.website.enduser.filters - java.lang.NullPointerException:
    java.lang.NullPointerException:
    at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:211)
    at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:224)
    at weblogic.cluster.replication.ReplicationManager_922_WLStub.create(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at weblogic.cluster.replication.SecureReplicationInvocationHandler$ReplicationServicesInvocationAction.run(SecureReplicationInvocationHandler.java:184)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.cluster.replication.SecureReplicationInvocationHandler.invoke(SecureReplicationInvocationHandler.java:154)
    at $Proxy46.create(Unknown Source)
    at weblogic.cluster.replication.ReplicationManager.trySecondary(ReplicationManager.java:666)
    at weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java:638)
    at weblogic.cluster.replication.ReplicationManager.add(ReplicationManager.java:359)
    at weblogic.cluster.replication.ReplicationManager.register(ReplicationManager.java:352)
    at weblogic.servlet.internal.session.ReplicatedSessionData.registerOrAdd(ReplicatedSessionData.java:108)
    at weblogic.servlet.internal.session.ReplicatedSessionData.<init>(ReplicatedSessionData.java:78)
    at weblogic.servlet.internal.session.ReplicatedSessionData.<init>(ReplicatedSessionData.java:64)
    at weblogic.servlet.internal.session.ReplicatedSessionContext.getNewSession(ReplicatedSessionContext.java:161)
    at weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getNewSession(ServletRequestImpl.java:2526)
    at weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSessionInternal(ServletRequestImpl.java:2111)
    at weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSession(ServletRequestImpl.java:2075)
    at weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:1207)
    at com.vignette.portal.website.internal.DefaultHttpRequestWrapper.getSession(DefaultHttpRequestWrapper.java:65)
    at com.vignette.portal.website.internal.DefaultHttpRequestWrapper.getSession(DefaultHttpRequestWrapper.java:41)
    at com.epicentric.common.website.InitUtils.initSession(InitUtils.java:73)
    at com.vignette.portal.website.enduser.filters.AuthenticationFilter.initSession(AuthenticationFilter.java:47)
    at com.vignette.portal.website.enduser.filters.AuthenticationFilter.doFilter(AuthenticationFilter.java:41)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
    at com.vignette.portal.website.admin.internal.control.InitFrameworkFilter.httpDoFilter(InitFrameworkFilter.java:35)
    at com.vignette.portal.website.admin.internal.control.AbstractHttpFilter.doFilter(AbstractHttpFilter.java:61)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
    at com.vignette.portal.website.admin.internal.control.MultipartFilter.httpDoFilter(MultipartFilter.java:33)
    at com.vignette.portal.website.admin.internal.control.AbstractHttpFilter.doFilter(AbstractHttpFilter.java:61)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
    at com.vignette.portal.website.internal.StartupProtectionFilter.doFilterSingleInvocation(StartupProtectionFilter.java:100)
    at com.vignette.portal.website.internal.SingleInvocationFilter.doFilter(SingleInvocationFilter.java:52)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
    at com.vignette.portal.website.internal.EnvironmentalWrapperFilter.doFilterSingleInvocation(EnvironmentalWrapperFilter.java:44)
    at com.vignette.portal.website.internal.SingleInvocationFilter.doFilter(SingleInvocationFilter.java:52)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3229)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2002)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1908)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1362)
    at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    Caused by: java.lang.NullPointerException:
    at weblogic.server.channels.ServerChannelImpl.equals(ServerChannelImpl.java:103)
    at weblogic.cluster.replication.ReplicationManagerServerRef.checkPriviledges(ReplicationManagerServerRef.java:102)
    at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:302)
    at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:877)
    at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:1084)
    at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:1001)
    at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:240)
    at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:881)
    at weblogic.rjvm.MsgAbbrevJVMConnection.dispatch(MsgAbbrevJVMConnection.java:446)
    at weblogic.rjvm.t3.MuxableSocketT3.dispatch(MuxableSocketT3.java:368)
    at weblogic.socket.AbstractMuxableSocket.dispatch(AbstractMuxableSocket.java:378)
    at weblogic.socket.SSLFilter.dispatch(SSLFilter.java:258)
    at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:856)
    at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:802)
    at weblogic.socket.EPollSocketMuxer.dataReceived(EPollSocketMuxer.java:192)
    at weblogic.socket.EPollSocketMuxer.processSockets(EPollSocketMuxer.java:174)
    at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
    ... 2 more

    Hi Scott,
    Did you get to the bottom of this?
    We're experiencing exactly the same symptoms, except we're upgrading 8.1 -> 10.3
    App works fine on a single server, as soon as a second server is brought into the cluster we get the same exception.
    I'm checking the configs now for anything suspicious...

  • To create a new session on the clcik of a button in Bsp.

    If have application A.
    On the click of the button i want to create a new session of application B.
    I used the method
    cl_http_ext_webapp=>create_url_for_bsp_application
    for calling the application B.
    but the session is maintained.
    How shall i proceed so that my application creates a new session.

    I am curious.  Both Raja and I suggest the same fix:
    >Now you probably want to add the url parameter sap-sessioncmd. There is the value open that will start a new session
    >'?sap-sessioncmd=open' and use this url for navigating.
    You said that his solution worked and mine did not.  The only difference is that I suggested that you use cl_bsp_runtime=>construct_bsp_url instead of cl_http_ext_webapp=>create_url_for_bsp_application.  This recommendation comes right from the source; cl_bsp_runtime=>construct_bsp_url is the prefered method for constructing URLs.  I am curious the other method somehow produce different results?

  • How can I create a stateful session bean?

    I created a stateless session bean. Now I want to make it be a stateful session bean. How can I do? Where can I find a session bean sample?
    Thanks
    Qing

    Look at this site. The tutorial explains it all.
    Well if you want to convert your stateless EJB to stateful, all you have to do is change the deployment descriptor and re-deploy the ejb. You should be ready to go.
    All the best.

  • Httprequest.getSession(false) creating a NEW Session

    I am working on a web application which uses STRUTS. All the client requests are directed to loginaction class.
    Any resource in the application, is accessed thru the action class.
    Overview: In the action class, i am checking if there is any session associated with the new user using
    session = request.getSession(false);
                      if (session != null) {
          if (session.isNew()) {
          logger.info("New Session Created [" + session.getId() + "]");
          } else {
          logger.info("Session EXIST'S ["+ session.getId()
         + "], Retreiving user from session");
                       }According to the Servlets 2.2 API:
    public HttpSession getSession(boolean create) Returns the current HttpSession associated with this request or, if if there is no current session and create is true, returns a new session.
    If create is false and the request has no valid HttpSession, this method returns null.
    if (session.isNew()) ,
    this if statement should return false and be skipped, as session = request.getSession(false);wont create a new session. When i parse the logs, I see the log statement, "New Session Created ". Which makes me wonder, that a new session is being created
    Problem: When i debug, i see that container is creating a new session if the session doesnt exist. According to API mentioned above, it should not create a new session. It should return null.
    Did anyone had a similar issue? While researching i found this article that using struts, the container creates a default session.
    I found this article: http://www.theserverside.com/discussions/thread.tss?thread_id=21643
    Environment: IDE:WSAD5.1, Appserver:Websphere, Browser:IE 6.0, Struts, JSP, JSTL

    Hi,
    We have two appliactions. Our application say B is uses authentication mechanism provided by say A.
    So the user, is presented a login page by application A. Once they are authenticated, without the knowledge of user, its being forwarded to our application say B.
    Once he is in our application, he can navigate in our application, say,
    he goes from page1 to page2. page1 is the main page. Now browser caching is enabled. When he hits the back button to access page1, browser is sending a new request to our applicaiton insted of furnising form local cache( this is another issue). Even though a new request is sent, all the requests are routed thru a struts controller action class. Now in the action class, we check if its a new session or not.
    request.getSession(false). Since the user is an old user, it shouldnt create any new session.
    As per your suggestion, where should i put the directive in the jsp to not to create a default session?. In page1 which is the main page?.
    How should i implemnt the session listener interface. Do u have any templates or code snippets?.
    Any suggestions?

  • How to create a new session by ABAP?

    Good afternoon everyone:
    This is my first question in the forum, can anybody tell me how to create a new session to display report output in a ALV program? Which function or method can used? I'm freshman.
    Thx.
    Edited by: Joshua Lee on Nov 21, 2008 10:04 AM

    Hi Joshua,
    Welcome To SDN.
    I am not clear about your queestion.
    if u r doing an ALV report if u give selection screen inputs if press execute buttom or F8 u wil get the report.
    if u want the out put in the next screen. you can develop the screen in the module pool
    Regards
    Rasheed
    Edited by: Rasheed salman on Nov 21, 2008 10:25 AM

  • Create a new session when calling a new/different transaction

    Hello Everyone,
    I have a dialog program in which I have a button that calls a different transaction.  I would like for this transaction to open in a new session.  This can be easily done (and there are several posts on this) with FM's TH_CREATE_MODE or ABAP4_CALL_TRANSACTION.  Additionaly it can be done by remote enabling a custom FM and have the transaction call within your custom FM.
    My issue is that I want to pass the transaction a table so that it fills a select-options table at the selection screen.  Then of course I want to skip the selection screen and execute the transaction.  I can pass data if the selection field is a parameter field, but I need to pass the new transaction a table so that a select-options field can be filled.  Does anyone know how to do this and could recommend a proper approach?
    Best Regards,
    Scott

    It seems that you want to start of a new report by calling the ABAP4_CALL_TRANSACTION. There is a parameter USING_TAB which you can use to fill up the data (must be BDC data) to be able to pass to called transaction. Since you are dealing with the select-options this is not a good idea.
    I would suggest:
    From your Module pool,
    Fill the select option table and export it to ABAP memory using EXPORT
    Now,
    1. Create a dummy program ZDUMMY to SUBMIT your report ZREPORT.
    2. IMPORT the exported select option table from memory in ZDUMMY
    3. SUBMIT report ZREPORT with the select option
    4. Attach transaction code say ZDUMMY.
    In your module pool, after exporting the memory call the FM ABAP4_CALL_TRANSACTION with ZDUMMY transaction.
    Regards,
    Naimesh Patel

  • How to prevent Spaces from creating a new session after logging out

    Hi,
    I'm using WebCenter Spaces (11.1.1.4), and I notice that the user is redirected to the landing page after logging out which causes a new HTTP session to be created. I'd like to avoid this behavior, and I was told that this could be done by creating a custom logout page with pure HTML and redirect the user there upon logout. How do I go about doing this? I couldn't find anything related to this in the documentation.
    Thanks,
    Robert

    What's wrong with a new session?
    When you logout, the current session will be destroyed so it's just normal that he creates a new webcenter that does not contain a user credential.

  • Fail Over - Back up, create a new session

              Two WLS 5.1 SP10 clustering, iPlanet4.1 w/wlproxy plugin, Solaris Box. Everything
              works except the following senario:
              1. Two servers up, user browses the site. ok!
              2. shutdown one server, user continues to browse without losing sessions. ok!
              3. down server back up, new session is created in this server and replicated to
              the other server, in the mean time the old session still there. Every click cause
              the session swithing back and forth. WRONG!
              4. close the brower and restart a new session, back to normal. ok!
              Any idea?
              

              Only one cookie is created in the whole process. But in step3, when clicking on
              the browser, plugin directs the request to app1, app2 back and forth for each
              click. I can also see the there are two session ids. one's primary is in app1,
              the other's prirmay is in app2.
              The other interesting thing is the wlproxy.log, where one app server is down (166.200.148.10
              is still up, 166.200.148.11 is down), plugin log shows connecting to 166.200.148.10
              fails and finally throught static list connecting to 166.200.148.11 which is down,
              and in fact, 166.200.148.10 got hit, browser has the display.
              Tue Oct 9 13:40:52 2001 getPref(): primary h=166.200.148.10 p=7008
              Tue Oct 9 13:40:52 2001 ===== New Request [main/formdata.jsp?] ====
              Tue Oct 9 13:40:52 2001 ....relFile.../main/formdata.jsp?...
              Tue Oct 9 13:40:52 2001 trying connect to PRIMARY '166.200.148.10'/7008 at line
              611 for '/main/formdata.jsp?'
              Tue Oct 9 13:40:52 2001 failed to connect to host 166.200.148.10 port 7008
              Tue Oct 9 13:40:52 2001 No good servers left in the general list, reverting back
              to the static list
              Tue Oct 9 13:40:52 2001 Initializing lastIndex=0 for a list of length=2
              Tue Oct 9 13:40:52 2001 general list: trying connect to '166.200.148.10'/7008
              at line 679 for '/main/formdata.jsp?'
              Tue Oct 9 13:40:52 2001 failed to connect to host 166.200.148.10 port 7008
              Tue Oct 9 13:40:52 2001 general list: trying connect to '166.200.148.11'/7008
              at line 679 for '/main/formdata.jsp?'
              Tue Oct 9 13:40:52 2001 Header from client [accept]=[*/*]
              Tue Oct 9 13:40:52 2001 Header from client [accept-language]=[en-us]
              Tue Oct 9 13:40:52 2001 Header from client [accept-encoding]=[gzip, deflate]
              Tue Oct 9 13:40:52 2001 Header from client [user-agent]=[Mozilla/4.0 (compatible;
              MSIE 5.5; Windows NT 4.0)]
              Tue Oct 9 13:40:52 2001 Header from client [host]=[167.206.148.202]
              Tue Oct 9 13:40:52 2001 Header from client [cookie]=[cookieID=4773; bmTzOff=240;
              bmScrRes=1024x768; bmClrDpt=16; bmJava=Yes; WebLo]
              Tue Oct 9 13:40:52 2001 WLS info before parseHeaders : 166.200.148.11:7008
              Tue Oct 9 13:40:52 2001 Sending header to WLS [accept]=[*/*]
              Tue Oct 9 13:40:52 2001 Sending header to WLS [accept-language]=[en-us]
              Tue Oct 9 13:40:52 2001 Sending header to WLS [accept-encoding]=[gzip, deflate]
              Tue Oct 9 13:40:52 2001 Sending header to WLS [user-agent]=[Mozilla/4.0 (compatible;
              MSIE 5.5; Windows NT 4.0)]
              Tue Oct 9 13:40:52 2001 Sending header to WLS [host]=[167.206.148.202]
              Tue Oct 9 13:40:52 2001 Sending header to WLS [cookie]=[cookieID=4773; bmTzOff=240;
              bmScrRes=1024x768; bmClrDpt=16; bmJava=Yes; We]
              Tue Oct 9 13:40:52 2001 Sending header to WLS [X-WebLogic-Force-Cookie]=[true]
              Tue Oct 9 13:40:52 2001 Sending header to WLS [Proxy-Client-IP]=[166.200.148.21]
              Tue Oct 9 13:40:52 2001 Sending header to WLS [X-Forwarded-For]=[166.200.148.21]
              Tue Oct 9 13:40:52 2001 Sending header to WLS [Proxy-Path-Translated]=[opt/netscape/server4/docs/main/formdata.jsp]
              Tue Oct 9 13:40:52 2001 Sending header to WLS [Proxy-Path-Translated-Base]=[opt/netscape/server4/docs]
              Tue Oct 9 13:40:52 2001 Header received from WLS : [HTTP/1.1 200 OK] = []
              Tue Oct 9 13:40:52 2001 Header received from WLS : [Server] = [WebLogic 5.1.0
              Service Pack 10 07/11/2001 21:04:48 #126882]
              Tue Oct 9 13:40:52 2001 Header received from WLS : [Content-Length] = [612]
              Tue Oct 9 13:40:52 2001 Header received from WLS : [Content-Type] = [text/html;
              charset=ISO-8859-1]
              Tue Oct 9 13:40:52 2001 Header received from WLS : [X-WebLogic-Load] = [0]
              Tue Oct 9 13:40:52 2001 Header received from WLS : [X-WebLogic-Cluster-List]
              = [-3524818015807611228/bungan/6/7008/7008/7002/7002]
              Tue Oct 9 13:40:52 2001 Header received from WLS : [X-WebLogic-Cluster-Hash]
              = [a0NT9MOQPES4vbUg1fb3g3C6j7U]
              Tue Oct 9 13:40:52 2001 Header received from WLS : [Connection] = [Close]
              Tue Oct 9 13:40:52 2001 Header to Client [Server]=[WebLogic 5.1.0 Service Pack
              10 07/11/2001 21:04:48 #126882]
              Tue Oct 9 13:40:52 2001 add content-length to srvhdrs, [Content-Length]=[612]
              Tue Oct 9 13:40:52 2001 Header to Client [Content-Length]=[612]
              Tue Oct 9 13:40:52 2001 Header to Client [Content-Type]=[text/html; charset=ISO-8859-1]
              Tue Oct 9 13:40:52 2001 Initializing lastIndex=0 for a list of length=1
              Tue Oct 9 13:40:52 2001 ### Got a new Server List of length 1 ###
              Tue Oct 9 13:40:52 2001 ###Response### : Srvr# [1] = [166.200.148.10:7008]
              Tue Oct 9 13:40:52 2001 request [main/formdata.jsp?] processed ......
              "Mike Reiche" <[email protected]> wrote:
              >
              >
              >A new session should not be created when the down server comes backup.
              >The requests
              >should continue to be sent to the server that was originally the secondary
              >( and
              >now the primary ).
              >
              >In IE, turn on 'prompt for cookies' and note the value of the WebLogicSession
              >cookie whenever one is written to the browser. The number in between
              >the the first
              >and second '/' is the IP address of the WL instance that wlproxy will
              >send the
              >request to. If there is no WL running there, it will round-robin requests
              >to the
              >instances that do exist.
              >
              >You should make sure that both the WebLogic Server and the wlproxy are
              >using the
              >same cookie name. (sounds like they are).
              >
              >
              >Mike
              >
              >
              >"Rong" <[email protected]> wrote:
              >>
              >>Two WLS 5.1 SP10 clustering, iPlanet4.1 w/wlproxy plugin, Solaris Box.
              >> Everything
              >>works except the following senario:
              >>
              >>1. Two servers up, user browses the site. ok!
              >>2. shutdown one server, user continues to browse without losing sessions.
              >>ok!
              >>3. down server back up, new session is created in this server and replicated
              >>to
              >>the other server, in the mean time the old session still there. Every
              >>click cause
              >>the session swithing back and forth. WRONG!
              >>4. close the brower and restart a new session, back to normal. ok!
              >>
              >>Any idea?
              >
              

  • Deploying session bean on sun java application server

    Hi,
    I'm using sun java system application server 8.2.
    I just want to deploy a session bean (stateless) on it.
    Please tell me the procedure.
    Thanks

    problem is coming in Resource Type and Factory class when configuring JNDI.
    what value I should give for the Resource Type and Factory class?
    Please tell me.
    Thanks

  • Hi After being created a new session by our IT department on network Adobe Bridge seem to have lost its link to photoshop in the tool menu. We can't keep on with our usual process to convert picture in Grey ... Could you help us on this ? thanks in advanc

    Hi All,
    I've just been hired in a new editing company where we are producing pictures in black and white to illustrate our book.
    The previous person that was occupying this position could manage the pictures workflow through bridge using a script that was in the Tools menu and use to select several picture and send them to photoshop to apply and converting script (black and white convesion).
    The problem I encounter on my session is that I can't send picture to this photoshop script using Bridge ... Can someone help me on this ?
    Thanks in advance.
    Best regards

    ''the-edmeister [[#answer-666854|said]]''
    <blockquote>
    '''''"I created a second profile called Shopping. I imported the extensions from my default profile into it."'''''
    If you used Sync to do that "import", disable Sync for at least one of those Profiles.
    </blockquote>
    Thank you for your suggestion. I have Sync enabled for all the profiles. To my surprise, however, Sync was of no use in getting Default's extension collection into Shopping. For that I had to resort to the article http://kb.mozillazine.org/Transferring_data_to_a_new_profile_-_Firefox.
    I will try disabling Sync on Shopping.

  • Error when creating a new session manager

    I am an absolute rookie in Java and Object to Persistence, and just need a push in the right direction please?
    Using MyEclipse 5.0 with JBoss 4.0 but just trying a very basic employee mapping with Toplink 10.1.3.1. Standard java application just to read the employee.
    For someone new to Java to figure out what JAR's exactly needs to be included is a nightmare.
    Any help would be much appreciated..
    Here is my code.
    ServerSession aSession = (ServerSession)SessionManager.getManager().getSession("toplinkTest");
              setServerSession(aSession);
    OR      
    SessionManager.getManager().getSession(
              new XMLSessionConfigLoader("sessions.xml"), "toplinkTest", getClass().getClassLoader());
    I am getting the following stack trace for both.
    Exception in thread "main" java.lang.VerifyError: (class: oracle/toplink/tools/sessionconfiguration/TopLinkSessionsFactory, method: buildDatabaseLoginConfig signature: (Loracle/toplink/tools/sessionconfiguration/model/login/DatabaseLoginConfig;)Loracle/toplink/sessions/Login;) Incompatible argument to fun
         at oracle.toplink.tools.sessionconfiguration.XMLSessionConfigLoader.load(XMLSessionConfigLoader.java:103)
         at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(SessionManager.java:367)
         at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(SessionManager.java:184)
         at com.ford.Main.login(Main.java:23)
         at com.ford.Main.main(Main.java:50)
    Message was edited by: Mike
    user548532

    Interesting error. My initial effort would be to ensure that all of my code was rebuilt against the 10.1.3.1 libraries. If the problem continues please open a support request so we can try to reproduce the issue and isolate a solution.
    Doug

  • Dynamically loading new session beans.

    We have an abstract class, say A.
    We then get the information for a new type of "A", call it
    "a1003". We do rigorous in-house coding to implement the
    methods. We finally get the a1003's methods doing exactly what
    we want. We now want to deploy a1003 along with all of the
    container generated code to the server. We will put a1003 in the
    list of "A" for drop-down access and interaction from the client.
    Is this doable on an ad-hoc basis in a production environment?
    How?
    Another option for us is to design all the inputs to any "Type of
    A" and store this in the database, but this may or may not be
    actually achievable, while the first option is achievable, but,
    right now involves a shutdown and restart of the app. The
    current app is an extremely old app where the "a1003" is added to
    an applet which then gets downloaded to the client's workstation.
    We are reengineering to EJB and Oracle and aren't sure how to
    handle this, quite critical, section of enterprise coding.
    Galen Boyer

    On Tue, 19 Nov 2002, [email protected] wrote:
    >
    >
    Galen Boyer wrote:
    We have an abstract class, say A.
    We then get the information for a new type of "A", call it
    "a1003". We do rigorous in-house coding to implement the
    methods. We finally get the a1003's methods doing exactly
    what we want. We now want to deploy a1003 along with all of
    the container generated code to the server. We will put a1003
    in the list of "A" for drop-down access and interaction from
    the client.
    Is this doable on an ad-hoc basis in a production environment?Can you deploy a new EJB in a running, production server? Yes.Actually, we know this. My question was more, is it a
    "productionized" strategy? Is it something people could
    recommend as part of one's production process, not just a hot-fix
    or upgrade, but an everyday, even all-day thing designed into the
    process?
    As for the drop-down box, you'll have to tell me more about how
    you populate that list etc if you want more ideas on how to add
    your new EJB to the list.The drop-down box would be list of all the classes that implement
    "A". The user wants to interact with our implementation of a
    particular class of "A", so he would look for it in the list and
    choose it.
    The client code only needs to call the methods and display the
    results in the same interface for all other "A" type classes.
    But, the "a1003" needs to have very particular implementations of
    the abstract methods.
    So, we wanted to understand if our process that exists today
    would be viable in an EJB environment. Our current process is,
    internally, we recieve the detailed information on the new "A".
    The detailed information is even titled "a1003". We spend time
    internally, implementing the abstract methods that are "modeled"
    after "a1003"'s detailed description, iteratively testing this
    "modeling process". When we deem it worthy of production, we
    would like to make it available to the world.
    The productionizing involves, having "a1003"s container code and
    "a1003"'s business methods code deployed to the server. Then
    putting the string "a1003" in the list of "A"'s (probably a
    drop-down box). Then, without the application having come down,
    the new "A" is available for interaction by the world.
    Does this description make sense?
    Thanks.
    Galen Boyer

Maybe you are looking for