Another error - session replication

Today's is a bad day for me - number of errors I have posted to this group.
Any ideas on this one -
<Feb 10, 2005 12:46:47 PM PST> <Error> <HTTP Session> <BEA-100049> <Error looking up session with id:CLHAml9NLIo15FYPIA7pz1arNCCp2j7WXJdNLkPePDvjiJDg4okz!709225447!-1883813311
java.lang.NullPointerException
     at weblogic.servlet.internal.session.ReplicatedSessionContext.getSessionInternal(ReplicatedSessionContext.java:480)
     at weblogic.servlet.internal.ServletRequestImpl.getValidSession(ServletRequestImpl.java:2489)
     at weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:2153)
     at weblogic.servlet.security.internal.SecurityModule$SessionRetrievalAction.run(SecurityModule.java:637)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
     at weblogic.servlet.security.internal.SecurityModule.getUserSession(SecurityModule.java:612)
     at weblogic.servlet.security.internal.SecurityModule.beginCheck(SecurityModule.java:153)
     at weblogic.servlet.security.internal.BasicSecurityModule.checkA(BasicSecurityModule.java:46)
     at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:145)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3539)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

Similar Messages

Remote handle caching error when using HTTP session replication

          Using WL 7.0 Sp2 on Solaris, deployed apllication on a 2 instance wide cluster.Code
          attached -
          unzip testapp.zip to find a test.jar which is the stateless sesion ejb and test.war
          which is the applicaiton.
          I have this class - TestDelegate that looks up a stateless session EJB(TestEJB),
          and puts the remote handle as a member variable(Test bean).Test.jsp instantiates
          this delegate(TestDelegate ), and then via setAttribute puts the TestDelegate
          in the HTTPSession.Then it calls a couple of methods via the TestDelegate which
          has the remote handle of the TestEJB.
          Scenario 1 : We deploy the WAR on cluster A which is 2 instance wide,we deploy
          the TestEJB on
          cluster B, which is also 2 instance wide. All works fine, the delegate is able
          to lookup EJB and
          can add the remote handle as a member variable.
          Scenario 2: We deploy the WAR on cluster A which is 2 instance wide,we deploy
          the TestEJB on
          cluster B, which is also 2 instance wide. This time we put a weblogic.xml in the
          WAR which has tag for in-memory session replication.This time we get class cast
          exception for the same sequence that we have above.
          <Mar 24, 2003 10:43:28 AM EST> <Error> <kernel> <000802> <ExecuteRequest failed
          java.lang.ClassCastException: Assigning instance of class com.TestEJB_1jsmq_EOImpl_WLStub
          to field com.bean.TestDelegate#bean
          Start server side stack trace:
          java.lang.ClassCastException: Assigning instance of class com.TestEJB_1jsmq_EOImpl_WLStub
          to field com.bean.TestDelegate#bean
          at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2266)
          at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:514)
          at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1407)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:381)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:231)
          at java.util.Hashtable.readObject(Hashtable.java:794)
          at java.lang.reflect.Method.invoke(Native Method)
          at java.io.ObjectInputStream.invokeObjectReader(ObjectInputStream.java:2209)
          at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1406)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:381)
          at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2258)
          at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:514)
          at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1407)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:381)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:231)
          at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:140)
          at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:91)
          at weblogic.cluster.replication.ReplicationManager_WLSkel.invoke(Unknown
          Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
          at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
          at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:821)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:308)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
          End server side stack trace
          [testapp.zip]


To see the list of session IDs in the cache you can iterate over the keys of the cache returned from the following code:
NamedCache cacheCatalog = CacheFactory.getReplicatedCacheService("$FilterService$").ensureCache("CoherenceSession.CATALOG", getClass().getClassLoader());Then to see the contents of a session you can take a look a the cache returned from the following code:
String sId = // keys from cacheCatalog
NamedCache cacheDetails = cacheCatalog.getCacheService().ensureCache(sId, getClass().getClassLoader());Hope this helps.
We have received your request for a development license and we hould have ti out to you today.
Later,
Rob Misek
Tangosol, Inc.
Coherence: Cluster your Work. Work your Cluster.

Strange errors in session replication

          I get following errors in session replication :
          weblogic.utils.NestedError: Tried to update secondary, but it thought
          it was the primary
          - with nested exception:
          [weblogic.cluster.replication.BadStatusException: updateSecondary
          found
              -148099416498695151 but it is not the primary]
          Using Weblogic451, SP7 on Solaris 2.6.
          Any clues ??
          -Kuntal Shah.


Hello,
          > > Alteon is set to use "permanent hashing" to route the client into
          > > the same server in each request.
          >
          > How do you expect the switch to know about the secondary node
          > if the primary fails? This information is stored in the URL and
          > parsed by a proxy.
          It took a couple of days and fair amount of documentation to understand
          the behaviour of the web cluster...;-)
          We changed the configuration to include two proxy servers between the
          Alteon switch and web cluster, but we ended up with a different problem.
          The setup at the moment is:
          - Sun Solaris 2.6, native threads, JDK 1.1.7B_008
          - two WLS 4.51 SP7 running in cluster using in-memory replication
          - only servlets deployed in the servers
          - Two WLS proxies between the webcluster and alteon switch. Both proxies are
          configured to use both of the web servers. they do not belong to the web
          cluster.
          The proxies are configured in the following way:
          weblogic.httpd.session.enable=true
          weblogic.httpd.session.timeoutSecs=1800
          weblogic.httpd.session.invalidationIntervalSecs=600
          weblogic.httpd.session.URLRewriting.enable=true
          weblogic.httpd.session.cookies.enable=true
          weblogic.httpd.session.cookie.maxAgeSecs=-1
          weblogic.httpd.session.cookie.domain=some.domain.name
          weblogic.httpd.register.cluster=weblogic.servlet.internal.HttpClusterServlet
          weblogic.httpd.initArgs.cluster=defaultServers=x.y.z.a1:9001|x.y.z.a2:9001
          weblogic.httpd.defaultServlet=cluster
          weblogic.allow.execute.weblogic.servlet=everyone
          Probably most of the configuration parameters are not necessary, can
          somebody tell me which are
          and which are not?
          The servers in the web cluster are configured in the following way:
          The following parameters are in the start-up script of the servers:
          -Dweblogic.cluster.enable=true \
          -Dweblogic.system.name=somehost \
          -Dweblogic.cluster.name=someclustercluster \
          -Dweblogic.cluster.multicastAddress=237.0.0.1 \
          -Dweblogic.system.bindAddr=x.y.z.a1 \
          -Dweblogic.system.nativeIO.enable=true \
          -Dweblogic.debug.replication=1 \
          And the following are in the cluster-wide properties file:
          weblogic.httpd.clustering.enable=true
          weblogic.httpd.session.persistence=true
          weblogic.httpd.session.persistentStoreType=replicated
          weblogic.httpd.session.enable=true
          weblogic.httpd.session.timeoutSecs=1800
          weblogic.httpd.session.invalidationIntervalSecs=600
          weblogic.httpd.session.URLRewriting.enable=true
          weblogic.httpd.session.cookies.enable=true
          weblogic.httpd.session.cookie.domain=some.domain.name
          The IP-address of the Alteon box in front of the proxies is bound to
          'some.domain.name'.
          The first problem seems to be very poor performance. The overall throughtput
          is vveeeerrryyy slow, comparing
          to the configuration where there is no proxy sitting in front of the
          cluster. Furthermore, at some stage the proxy
          starts to print out error messages: java.lang.InvalidStateException: broken
          pipe [...] . After those exceptions no
          client get any response anymore.
          Could someone give some hints what are the most essential items in the
          weblogic.properties -file for the
          proxy server? Also, if someone has some experience from setting up a
          configuration similar to ours: one hardware
          load-balancer in front of two proxies, and eventually two web servers
          running in a web cluster.
          Cheers,
          Jarno.

Apache + 2 Tomcats session replication problem.

Greetings everyone.
Before stating the problem, let me explain how my environment is set.
I have two machines. One (PC1) running Apache (HTTP server 2.0.58)
and one instance of Tomcat (5.0.28) and another machine (PC2) with
another instance of Tomcat(5.0.28).
The Apache server
It is configured to handle static content, to redirect dynamic content to a
Tomcat instance through AJP 1.3 connector.
This process is done through the mod_jk and the workers.properties
The workers.properties file is configured to have sticky_session = True
so it assigns a SESSION_ID to the same Tomcat it was first assigned.
The workers.properties file is configured to have
sticky_session_force = True so if the Tomcat the SESSION_ID was
assigned is not available, the server answers with a 500 error.
The Tomcat servers
Both have only the AJP 1.3 connector enabled
Both have the Cluster tag from the server.xml file uncommented
and the useDirtyFlag flag set to false, for not to allow SESSION
replication between Tomcats.
The workers.properties file
workers.apache_log=C:/Apache2/logs
workers.tomcat_home=C:/Tomcat5
workers.java_home=C:/j2sdk1.4.2_13
ps=/
#Defining workers -----------------------------
worker.list=balancer,jkstatus
#Defining balancer ---------------------------
worker.balancer.type=lb
worker.balancer.balance_workers=tel1, tel2
worker.balancer.sticky_session=True
worker.balancer.sticky_session_force=True
worker.balancer.method=B
worker.balancer.lock=O
#Defining status -----------------------------
worker.jkstatus.type=status
worker.jkstatus.css=/jk_status/StatusCSS.css
#Workers properties ---------------------------
worker.tel1.type=ajp13
worker.tel1.port=8009
worker.tel1.host=127.0.0.1
worker.tel1.lbfactor=1
worker.tel1.socket_keepalive=False
worker.tel1.socket_timeout=30
worker.tel1.retries=20
worker.tel1.connection_pool_timeout = 20
#worker.tel1.redirect=tel2
worker.tel1.disabled=False
worker.tel2.type=ajp13
worker.tel2.port=8009
worker.tel2.host=199.147.52.181
worker.tel2.lbfactor=1
worker.tel2.socket_keepalive=False
worker.tel2.socket_timeout=30
worker.tel2.retries=20
worker.tel2.connection_pool_timeout = 20
#worker.tel2.redirect=tel1
worker.tel2.disabled=False
THE PROBLEM
I open a browser in the jk-status page to see how the Tomcat instances are
working, and both are working fine: Stat -> OK, now as the
loadbalancing factor is 1 on both Tomcats, an even alternating session
distribution is set.
While this browser is open to keep an eye on the status, I open a new
browser (B1)to connect to my Web Application, Apache answers
correctly and gives me a SESSION_ID for Tomcat instance 1 [both
instances are OK], if I make a simple refresh, my SESSION_ID is still the
same so I'm assigned to Tomcat instance 1 but this time I get an
ERROR 503 - Service unavailable but looking at the status of the
Tomcat instances both instances are still OK, no-one is down. And it
stays throwing this error for as many refreshes i do.
Now, I open a new browser (B2)and do the same process as before,
as expected, Apache now gives me a SESSION_ID for Tomcat instance 2,
repeating the same refreshing process, the error is thrown again, but still at
the jk-status page, both instances are fine.
Without closing these windows, I make a new refresh try on B1 and
even though the jk-status says both Tomcat instances are OK, the error
is still thrown. I open a third one (B3), and Apache again, correctly
gives me a new SESSION_ID for Tomcat instance 1 and answers
correctly on the first call. But once again if i repeat the refreshing process, the
error is thrown again.
Note: Using a different resolution to always keep and eye on the
instances status and using a refresh rate of 1 second for status, both
servers always were OK.
So the main problem is that somehow when the session is replicated
to the same tomcat, Apache confuses and thinks it is not available, when
asking it through the jk-status it tells it is OK
I've been trying different configurations with both Apache and Tomcat,
but there must be something missing since I don't get it to work correctly
Thanks in advance for all your helping comments.
- @alphazygma

Whew... that was quite an answer... definitely is going to help him a lot. Yeah any n00b by now should know how to use google, but that's not the point in this forums, here we are to help each other. and wether you like it or not many of us deploy applications to tomcat and stumble on this. So dont try to be cool posting this kind of answers like google this or google that if you dont have an answer please dont comment you will appear to be more noobish than you aparently are.
Well enough talking.
I found the following useful: (it comes in the server.xml of the tomcat configuration)

Enabling that entry on both machines should be enough.
Aparently the problem is not with apache. is with tomcat since it can't retain the session apache gives.
more information in the Tomcat help at:
http://tomcat.apache.org/tomcat-5.0-doc/balancer-howto.html#Using%20Apache%202%20with%20mod_proxy%20and%20mod_rewrite

CF7 Clustering - session replication broken

Further to my
earlier
thread on CF7 clustering and the "network error",
I think session replication is broken. True, I can't find any
documentation which explains how it is supposed to behave, but this
is what I'm seeing:
If you have a two node cluster, and person A has a session on
node 1 and person B a session on node 2, session variables for each
user DO NOT appear on both nodes
Sessions on one node will only appear on the other when the
first node fails over
Moreover, they will only appear when the user makes another
request
CFLOGIN, when using loginstorage="session" does not replicate.
This means you have to use sticky sessions, and if there is a node
failure, the user will have to login in again. This can be avoided
by using loginstorage = "cookie" but this means the username and
password are stored unencrypted in the cookie.
Problems I have with this:
It's impossible to have a cluster wide view of sessions. E.g.
you can't count how many sessions you have at any one time. Any
code that makes use of being able to dig in to multiple sessions -
made possible by J2EE sessions - will not work reliably.
CFLOGIN is broken. It would be better to not use it for sites
that have to be secure as keeping the unencrypted username and
password in a cookie is very insecure. The only way to protect the
username and password being stored in the cookie is SSL; and that
means that every single item on the site needs to be protected by
SSL to stop the browser from serving up the cookie over an
unprotected connection.
It's not clear what is responsible for replication. If sessions
are only replicated when an instance goes down, rather than
continously, then I assume that the master instance of CF on each
server is responsible for replication. What happens if the server
crashes?

Information about session replication can be found here: http://docs.oracle.com/cd/E21764_01/web.1111/e13709/failover.htm#i1024620
it contains a section 'Requirements for HTTP Session State Replication' that might be helpful to you.
Also important to note is, how the load balancer handles session binding and the WebLogic cookie
http://docs.oracle.com/cd/E21764_01/web.1111/e13709/load_balancing.htm#i1026939

Session Replication and Session Timeout -- Urgent

WLS -4.5.1 SP 11
          OS - both NT and Sol
          HI All
          The session does not seems to timeout when running the Weblogic servers in
          clustered mode with in-memory session replication on.
          This problem seems to be there in version5.1 too , as per another post , it
          seems to be solved in WLS5.1 sp 8
          Could anyone pls confirm in which patch in WLS 4.5.1 is the problem
          addressed . I'm using patch 11 and am getting the problem.
          Thanks in advance..
          -Surya


Try SP13 and if the problem persists, contact [email protected]
          -K
          Surya B Maithani wrote:
          > WLS -4.5.1 SP 11
          > OS - both NT and Sol
          >
          > HI All
          >
          > The session does not seems to timeout when running the Weblogic servers in
          > clustered mode with in-memory session replication on.
          > This problem seems to be there in version5.1 too , as per another post , it
          > seems to be solved in WLS5.1 sp 8
          >
          > Could anyone pls confirm in which patch in WLS 4.5.1 is the problem
          > addressed . I'm using patch 11 and am getting the problem.
          >
          > Thanks in advance..
          >
          > -Surya

Local session bean lookup in another local session bean in EJB 3.0

Hi,
I am doing JNDI lookup of a local session bean in a session bean. ( I do not want to use EJB dependency injection).
Lookup of local interface from session bean is successful. But, when the calling session bean is a local session in another session bean, the lookup fails.
Here is an example:
@Stateless
@EJBs({@EJB(name="EJB2Local", beanInterface=EJB2Local.class),
@EJB(name="EJB3Local", beanInterface=EJB3Local.class)})
public class EJB1 implements EJB1Remote, EJB1Local{
public void findEJB3Local(){
//1. JNDI lookup for EJB3Local ----
//2. EJB3Local.someFunction()
@Stateless
@EJB(name="EJB1Local", beanInterface=EJB1Local.class)
public class EJB2 implements EJB2Remote, EJB2Local{
public void findEJB1Local(){
//1. JNDI lookup EJB1Local
// 2. Call EJB1Local.findEJB1Local method
//THIS METHOD CALL WILL FAIL.
public void findEJB1Remote(){
//1. JNDI lookup EJB1
/ 2. Call EJB1Local.findEJB1 method
@Stateless
public class EJB3 implements EJB3Remote, EJB3Local{
public void someFunction(){}
This setup was working in EJB 2.1, as we had clear ejb-local-ref definitions in our ejb-jar.xml file.
I am suspecting that EJB 3.0 has special annotation to use when lookup is made from another local session bean.
Any comments will be appreciated.
Thanks,
Mohan

From a private component environment perspective, declaring @EJB in a bean class is equivalent
to using ejb-ref or ejb-local-ref for that same bean in ejb-jar.xml. In each case, the EJB dependency
is declared for that bean. Each EJB component has its own private component environment, so
code running within invocations on different EJBs can not see the component environment of the
components that made the invocations.
What exact error are you getting? Please post the stack trace if possible.
--ken

Failover is work, but Session replication doesn't work!

Dear all,
          My Cluster can failover, but can't session replicate....
          I start up the 2 WLS 6.0 and the Web Server, then I visit
          http://web_server_ip/myWebApp/SessionServlet serveral times, then the
          counter variable in the session raise up, then I down the "target" WLS, then
          I try http://web_server_ip/myWebApp/SessionServlet now, I can call but the
          counter restart.... so the session seems not yet replicated. what I can
          do...?!
          My Setup: I setup a Netscape Web Server 3.6.3 as the proxy using libproxy.so
          with the cluster setting, and use 2 WLS 6.0 (both are running in 7001,7002)
          as the Application Server Cluster (WLCluster). one WLS is on Unix Machine
          and the other in on a NT. I set the 2 WLSs: the Primary Group is
          "WL_rep_group1", and set the secondary is "WL_rep_group2".
          Deployment: I deploy the application "myWebApp" (.war) on the servers unix
          and nt, adn also deploy to the cluster WLCluster.
          I deploy the examplesWebApp to my created domain "demo", and modify the
          weblogic.xml:
          <weblogic-web-app>
          <session-descriptor>
          <session-param>
          <param-name>PersistentStoreType</param-name>
          <param-value>replicated</param-value>
          </session-param>
          </session-descriptor>
          <jsp-descriptor>
          <jsp-param>
          <param-name>
          pageCheckSeconds
          </param-name>
          <param-value>
          1
          </param-value>
          </jsp-param>
          <jsp-param>
          <param-name>
          verbose
          </param-name>
          <param-value>
          true
          </param-value>
          </jsp-param>
          </jsp-descriptor>
          </weblogic-web-app>
          so ... anything I did wrong, so the WLS can't do Session replication??!!
          Please Help or Comment!
          Thanks in advance!
          with thanks,
          Alex Wong


Dear Vinod and Kevin,
          Some more information that I think it may help.
          First, I want to correct 1 point in my previous message, the Replication
          Group is "WLRepGroup1" and the Preferred Secondary Group is "WLRepGroup2"
          for the 2 machine WLSs.
          Second, I found that the Multicast Communication is not functioning becoz
          the switch of my office block the 224.0.0.1's communication, so now I added
          a hub for this 2 machine, as a result the multicast is wokring... at least
          pass the java utils.MulticastTest....
          Thrid, after the mutlicast work, I try the SessionServlet, it is working at
          beginning... but after some more clicks, one server will cause the following
          error (this time crash on x.y.z.b--NT machine)....
          -------- (a long list, the IPs are replaced: x.y.z.a UNIX machine, x.y.z.b
          NT machine, x.y.z.c My PC)
          Screen caption on demo>Servers>wlserver2 (monitoring> cluster)
          Unexpected Error
          Connected to x.y.z.a:7001 Active Domain: demo Jun 11, 2001 5:06:23 PM
          GMT+08:00
          An unexpected error was encountered in processing your request.
          Exception
          java.lang.NullPointerException
          <>
          Current Date
          Mon Jun 11 17:06:23 GMT+08:00 2001
          Console Release Build
          6.0 Service Pack 2
          Console Build
          6.0 Service Pack 2 05/24/2001 11:55:28 #117037
          Server Release Build
          6.0 Service Pack 2
          Server Build
          6.0 Service Pack 2 05/24/2001 11:55:28 #117037
          All Server Product Versions
          WebLogic Server Build: 6.0 Service Pack 2 05/24/2001 11:55:28 #117037
          WebLogic XML Module: 6.0 Service Pack 2 05/24/2001 12:34:27 #117037
          Request Info
          Protocol: HTTP/1.1
          ServerName: x.y.z.a
          ServerPort: 7001
          Secure: false
          ContextPath: /console
          ServletPath: /panels/mbean/Server.jsp
          QueryString:
          mbean=demo%3AName%3Dwlserver2%2CType%3DServer
          PathInfo: null
          PathTranslated: null
          RequestURI: /console/panels/mbean/Server.jsp
          AuthType: null
          ContentType: null
          CharacterEncoding: null
          Locale: zh_TW
          Method: GET
          Session:
          weblogic.servlet.internal.session.MemorySessionData@661950
          RequestedSessionId:
          OyQxOz4LG0WnLjufYcZDkIGGXIVAhHNASdBLUs2seZnvoQ4RXekX/console
          RequestedSessionIdFromCookie: true
          RequestedSessionIdFromURL: false
          UserPrincipal: system
          RemoteUser: system
          RemoteAddr: x.y.z.c
          RemoteHost: x.y.z.c
          Parameters
          mbean = demo:Name=wlserver2,Type=Server
          Attributes
          console.original./console/panels/mbean/Server.jsp.ContextPath = /console
          console.original./console/panels/mbean/Server.jsp.Method = GET
          console.original./console/panels/mbean/Server.jsp.QueryString =
          mbean=demo%3AName%3Dwlserver2%2CType%3DServer
          console.original./console/panels/mbean/Server.jsp.RemoteUser = system
          console.original./console/panels/mbean/Server.jsp.RequestURI =
          /console/panels/mbean/Server.jsp
          console.original./console/panels/mbean/Server.jsp.ServletPath =
          /panels/mbean/Server.jsp
          console.preferences.ContextKey =
          /panels/mbean/Server.jsp
          javax.servlet.include.context_path = /console
          javax.servlet.include.request_uri =
          /console/common/requestinfo.jsp
          javax.servlet.include.servlet_path =
          /common/requestinfo.jsp
          javax.servlet.jsp.jspException =
          java.lang.NullPointerException
          weblogic.httpd.user = system
          weblogic.management.console.tags.ContentTag =
          java.lang.Object@545f89
          weblogic.management.console.tags.HeaderTag =
          java.lang.Object@4c5c6c
          weblogic.management.console.tags.TabbedDialogTag =
          java.lang.Object@7eafc
          Headers
          Accept = image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*
          Accept-Encoding = gzip, deflate
          Accept-Language = zh-tw
          Connection = Keep-Alive
          Cookie =
          JSESSIONID=OyQxOz4LG0WnLjufYcZDkIGGXIVAhHNASdBLUs2seZnvoQ4RXekX!143710744761
          7668081!-896735123!7001!7002!NONE
          Host = x.y.z.a:7001
          User-Agent = Mozilla/4.0 (compatible; MSIE 5.01; Windows 98)
          BrowserInfo
          User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows 98)
          IE: true
          Netscape: false
          Supported: true
          JavscriptHrefs: false
          TableCellClick: true
          DocumentReloadedOnResize: false
          DropdownStretchable: true
          CellSpacingBlank: false
          EmptyCellBlank: false
          ImgOnclickSupported: true
          TableBorderFancy: true
          PartialToWideTables: false
          Server System Properties
          bea.home = /u0/weblogic
          file.encoding = ISO8859-1
          file.encoding.pkg = sun.io
          file.separator = /
          java.awt.fonts =
          java.awt.graphicsenv = sun.awt.X11GraphicsEnvironment
          java.awt.printerjob = sun.awt.motif.PSPrinterJob
          java.class.path =
          /u0/weblogic/wlserver6.0:/u0/weblogic/wlserver6.0/lib/weblogic_sp.jar:/u0/we
          blogic/wlserver6.0/lib/weblogic.jar:/opt/oracle/product/8.1.6/jdbc/lib/class
          es12.zip
          java.class.version = 47.0
          java.ext.dirs = /u0/weblogic/jdk130/jre/lib/ext
          java.home = /u0/weblogic/jdk130/jre
          java.io.tmpdir = /var/tmp/
          java.library.path =
          /u0/weblogic/jdk130/jre/bin/../lib/sparc/hotspot:/u0/weblogic/jdk130/jre/bin
          /../lib/sparc::/lib:/usr/local/easysoft/oob/client:/usr/local/easysoft/lib:/
          u0/weblogic/wlserver6.0/lib/solaris:/u0/weblogic/wlserver6.0/lib/solaris/oci
          816_8:/usr/lib
          java.naming.factory.initial =
          weblogic.jndi.WLInitialContextFactory
          java.naming.factory.url.pkgs = weblogic.jndi.factories
          java.protocol.handler.pkgs =
          weblogic.utils|weblogic.utils|weblogic.net|weblogic.management|weblogic.net|
          weblogic.net|weblogic.utils
          java.runtime.name = Java(TM) 2 Runtime Environment,
          Standard Edition
          java.runtime.version = 1.3.0
          java.security.policy =
          =/u0/weblogic/wlserver6.0/lib/weblogic.policy
          java.specification.name = Java Platform API Specification
          java.specification.vendor = Sun Microsystems Inc.
          java.specification.version = 1.3
          java.vendor = Sun Microsystems Inc.
          java.vendor.url = http://java.sun.com/
          java.vendor.url.bug =
          http://java.sun.com/cgi-bin/bugreport.cgi
          java.version = 1.3.0
          java.vm.info = mixed mode
          java.vm.name = Java HotSpot(TM) Client VM
          java.vm.specification.name = Java Virtual Machine
          Specification
          java.vm.specification.vendor = Sun Microsystems Inc.
          java.vm.specification.version = 1.0
          java.vm.vendor = Sun Microsystems Inc.
          java.vm.version = 1.3.0
          javax.rmi.CORBA.PortableRemoteObjectClass =
          weblogic.iiop.PortableRemoteObjectDelegateImpl
          javax.rmi.CORBA.UtilClass = weblogic.iiop.UtilDelegateImpl
          javax.xml.parsers.DocumentBuilderFactory =
          weblogic.xml.jaxp.RegistryDocumentBuilderFactory
          javax.xml.parsers.SAXParserFactory =
          weblogic.xml.jaxp.RegistrySAXParserFactory
          jmx.implementation.name = JMX RI
          jmx.implementation.vendor = Sun Microsystems
          jmx.implementation.version = 1.0
          jmx.specification.name = Java Management Extensions
          jmx.specification.vendor = Sun Microsystems
          jmx.specification.version = 1.0 Final Release
          line.separator =
          os.arch = sparc
          os.name = SunOS
          os.version = 5.6
          path.separator = :
          sun.boot.class.path =
          /u0/weblogic/jdk130/jre/lib/rt.jar:/u0/weblogic/jdk130/jre/lib/i18n.jar:/u0/
          weblogic/jdk130/jre/lib/sunrsasign.jar:/u0/weblogic/jdk130/jre/classes
          sun.boot.library.path =
          /u0/weblogic/jdk130/jre/lib/sparc
          sun.cpu.endian = big
          sun.cpu.isalist = sparcv8plus+vis sparcv8plus
          sparcv8 sparcv8-fsmuld sparcv7 sparc
          sun.io.unicode.encoding = UnicodeBig
          user.dir = /u0/weblogic/wlserver6.0
          user.home = /
          user.language = en
          user.name = root
          user.region = US
          user.timezone = Asia/Hong_Kong
          weblogic.Domain = demo
          weblogic.Name = wlserver1
          weblogic.security.jaas.Configuration =
          weblogic.security.internal.ServerConfig
          weblogic.security.jaas.Policy =
          /u0/weblogic/wlserver6.0/lib/Server.policy
          ---------- End of the message -----------
          any comment?? is that I deploy on wlserver1, wlserver2, WLCluster cause
          error??!! anything I did wrong??!
          please help!! or Comment
          with thanks,
          Alex Wong
          "Alex Wong" <[email protected]> ¼¶¼g©ó¶l¥ó
          news:[email protected]...
          > Hi Vinod and Kevin,
          >
          > Thanks Vinod first, and after I try the session.getClass(), I get the
          > following output
          > class weblogic.servlet.internal.session.ReplicatedSessionData
          > I think that's means I am using "replicated" already, rite?!
          >
          > About the License, I cat the license.bea, there is a license to the
          > "In-memory Replication - Servlet" and "In-memory Replication - EJB",
          however
          > it is a eval license but seems not yet expired, so I don't think that is
          the
          > problem, rite?
          >
          > And a quick question, you tell me "your configuration looks ok" means the
          > H/W configuration, or the WLS configuration??!!
          > Maybe I tell you more about my WLS configuration, so that, you can
          > determinate where I go wrong. (thanks)
          >
          >
          > Vinod and Kevin
          > (Kevin, I am Alex Wong from ASL, if you have any comment, you can simply
          > reply my personal email, thx)
          >
          > Steps I did to create the domain, WLS and Cluster and deploy the .war
          > --- on Unix ---
          > I create a demo domain and wlserver1 using port 7001 and 7002 by the
          > installation program (ip x.y.z.a)
          > --- on NT ---
          > I create a demo domain and wlserver2 using port 7001 and 7002 by the
          > installation program (ip x.y.z.b)
          >
          > --- on Unix ---
          > start the wlserver1 with startWebLogic.sh
          >
          > --- My PC ---
          > go http://x.y.z.a:7001/console
          >
          > create one more server named "wlserver2" using port 7001 and 7002
          > create the cluster named "WLCluster" and fill the the cluster ip
          > "x.y.z.a:7001,x.y.z.b:7001"
          > fill the multi-cast ip 224.0.0.1
          > add the "wlserver1" and "wlserver2" to the "WLCluster"
          > stop the unix WLS
          > start the unix WLS with startWebLogic.sh
          >
          > --- on NT ---
          > start the WLS with startManagedWebLogic.sh wlserver2 http://x.y.z.a:7001
          >
          > --- on Unix ---
          > install the NES 3.6.3 and create a WEB server instance and modify the
          > obj.conf
          >
          > DETAIL
          > ----- start of the obj.conf -----
          > Init fn="load-modules" funcs="wl-proxy,wl-init"
          > shlib="/opt/nes/plugins/weblogic/libproxy.so"
          > Init fn="wl-init"
          > .
          > .
          > .
          > <Object name="weblogic" ppath="*">
          > Service fn=wl-proxy \
          > WebLogicCluster="x.y.z.a:7001,x.y.z.b:7001"
          > </Object>
          >
          > <Object name=default>
          > *NameTrans ...
          > *NameTrans ...
          > *NameTrans ...
          > *NameTrans fn=document-root root="/opt/nes/docs"
          > Service method="(GET|HEAD|POST|PUT)" type=text/jsp fn=wl-proxy \
          > WebLogicCluster="x.y.z.a:7001,x.y.z.b:7001"
          > .
          > .
          > .
          > </Object>
          >
          > <Object name=cgi>
          > .
          > .
          > .
          > </Object>
          > ----- End of the obj.conf ----- (I suppose will redirect all HTTP request
          to
          > WLS from NES)
          >
          > --- My PC ---
          > go http://x.y.z.a:7001/console
          > assign the DefaultWebApp_wlserver1 to wlserver1
          > assign the DefaultWebApp_wlserver2 to wlserver2
          > assign the console the wlserver1 only
          > assign the certificate to wlserver1, wlserver2, WLCluster
          > go SERVER-wlserver1 assign "WLRepGroup1" to Replication Group and
          Preferred
          > Secondary Group
          > go SERVER-wlserver2 assign "WLRepGroup1" to Replication Group and
          Preferred
          > Secondary Group
          >
          > --- on Unix ---
          > go to ./config/examples/applications/examplesWebApp/WEB-INF
          > modify the weblogic.xml
          > go to ./config/examples/applications/examplesWebApp
          > jar cvf myWebApp.war *
          > copy the myWebApp.war to ./config/demo/applications/.
          > and ftp myWebApp.war ro (NT)./config/demo/applicaitons/.
          >
          > --- My PC ---
          > And then now, I can visit http://x.y.z.a:7001/console
          > now I can configuration the myWebApp.
          > assign the myWebApp to wlserver1,wlserver2,WLCluster
          >
          > --- on Unix ---
          > stop the WLS and start with startWebLogic.sh
          >
          > --- on NT ---
          > stop the WLS and start with startManagedWebLogic.sh wlserevr2
          > http://x.y.z.a:7001
          >
          > --- My PC ---
          > visit http://x.y.z.a/myWebApp/SessionServlet (this time no port 7001,
          becoz
          > I want to use the NES web server to proxy the HTTP request)
          >
          > Finally... I can failover the SessionServlet, SnoopServlet and all the
          other
          > html, jsp, servlet, but seems can't load-balancing and Session
          Persistence.
          >
          > Is that anything I did wrong, please comment!
          >
          >
          > with thanks,
          >
          > Alex Wong
          >
          >
          >
          > "Vinod Mehra" <[email protected]> ¼¶¼g©ó¶l¥ó
          > news:[email protected]...
          > > Your configuration looks ok but I guess somehow your clustering is not
          > setup
          > > properly. Check if all the servers are listeniong on the same port and
          > part
          > > of
          > > the same cluster. Also check if you have clustering license.
          > >
          > > Make sure your sessions are of type : "replicated". For that print
          > > the value of session.getClass(), the name will give you an idea. Check
          > > your logs if you got any error message.
          > >
          > > --Vinod.
          > >
          > >
          > > "Alex Wong" <[email protected]> wrote in message
          > > news:[email protected]...
          > > > Dear all,
          > > >
          > > > My Cluster can failover, but can't session replicate....
          > > >
          > > > I start up the 2 WLS 6.0 and the Web Server, then I visit
          > > > http://web_server_ip/myWebApp/SessionServlet serveral times, then the
          > > > counter variable in the session raise up, then I down the "target"
          WLS,
          > > then
          > > > I try http://web_server_ip/myWebApp/SessionServlet now, I can call but
          > the
          > > > counter restart.... so the session seems not yet replicated. what I
          can
          > > > do...?!
          > > >
          > > > My Setup: I setup a Netscape Web Server 3.6.3 as the proxy using
          > > libproxy.so
          > > > with the cluster setting, and use 2 WLS 6.0 (both are running in
          > > 7001,7002)
          > > > as the Application Server Cluster (WLCluster). one WLS is on Unix
          > Machine
          > > > and the other in on a NT. I set the 2 WLSs: the Primary Group is
          > > > "WL_rep_group1", and set the secondary is "WL_rep_group2".
          > > >
          > > > Deployment: I deploy the application "myWebApp" (.war) on the servers
          > unix
          > > > and nt, adn also deploy to the cluster WLCluster.
          > > >
          > > > I deploy the examplesWebApp to my created domain "demo", and modify
          the
          > > > weblogic.xml:
          > > > -------------------
          > > > <weblogic-web-app>
          > > >
          > > > <session-descriptor>
          > > > <session-param>
          > > > <param-name>PersistentStoreType</param-name>
          > > > <param-value>replicated</param-value>
          > > > </session-param>
          > > > </session-descriptor>
          > > >
          > > > <jsp-descriptor>
          > > > <jsp-param>
          > > > <param-name>
          > > > pageCheckSeconds
          > > > </param-name>
          > > > <param-value>
          > > > 1
          > > > </param-value>
          > > > </jsp-param>
          > > > <jsp-param>
          > > > <param-name>
          > > > verbose
          > > > </param-name>
          > > > <param-value>
          > > > true
          > > > </param-value>
          > > > </jsp-param>
          > > > </jsp-descriptor>
          > > >
          > > > </weblogic-web-app>
          > > > ---------------------
          > > >
          > > > so ... anything I did wrong, so the WLS can't do Session
          replication??!!
          > > >
          > > >
          > > > Please Help or Comment!
          > > >
          > > > Thanks in advance!
          > > >
          > > > with thanks,
          > > >
          > > > Alex Wong
          > > >
          > > >
          > > >
          > > >
          > > >
          > > >
          > > >
          > > >
          > > >
          > >
          > >
          >
          >

JNDI lookup of a Stateless Session bean from another stateless session bean

Hi,
   I am working on SAP Netweaver. We have created a stateless session bean which is finally deployed as a webservice. From this stateless session bean we need to call another stateless session bean as a local reference.
    I have done the following.
1. Added JNDI-Name to the ejb-j2ee-engine.xml.
2. My lookup code is as follows
Context context = null;
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sap.engine.services.jndi.InitialContextFactoryImpl");
context = new InitialContext(env);
Object ejbObj =     context.lookup("MyBean");
But i get the NamingException .Here MyBean is the jndi-name provided in the ejb-j2ee-engine.xml.
Can somebody tell me what i am doing wrong.
Thanks
Priya

Hi,
    Thanks for your replies.I did as you had suggested.I added ejb-local-ref to the ejb-jar.xml and i provided ejb-ref as MyBean.
My lookup code uses the string
ctxt.lookup("localejbs\MyBean");
But still i get Naming Exception.
I tried something different yesterday.
I changed the code to use
InitialContext ctxt = new InitialContext();
ctxt.lookup("localejbs/"+ pathfromJNDIRegistry);
and this time i did not get Naming exception but i got RemoteException saying there was error loading the class.
Is there something i need to add somewhere for the classloader to be able to find and load this class in the second scenario.
Please suggest me which method to go for amongst the two and what is the missing information i need to add.
Thanks
Priya

Does replication group have to be set for session replication

I have delployed an servlet based application on a 3 node cluster. I have a simple POJO that I use to carry data in the session from a "confirm?" to "confirmed" page. This object implements serializable and only has String and int members. I put it in session using request.getSession().setAttribute("dto", myobject). For some reason it is not being replicated to the other nodes in the cluster. My weblogic.xml has "PersistentStoreType" set to "replicated_if_clustered". I am not seeing any serialization or other errors in the node logs.
          I have looked at information contained in the link below and I think we are doing everything right. http://support.bea.com/application_content/product_portlets/support_patterns/wls/HTTP_Session_Replication_Failures_Pattern.html
          The only thing that I noticed is that the "Replication Group" is not set for any of the servers in the cluster. Does this need to be set for replication to happen?

Hi,
          Having replication group is optional. It is used only if you are implementing failover in cluster. For session replication one has to generally configure 3 things:
          - in memory replication
          - jdbc replication
          - file sytem replication
          for im memory replication,
          Step 1:
          make sure taht a client is accesing the cluseter using either
          - load balancing hardware
          - web servers with weblogic proxy plugin
          Step 2:
          specify the persistance type in weblogic.xml
          Thanks,
          Sushma

Cluster session replication

Hi,
CFMX 7.01 MULTISERVER:
I am facing a problem, session are not replicating on two CF
instances on same server. Below is Jrun log file error detail
30/05 17:18:10 error Setup of session replication failed.
[1]java.rmi.RemoteException: The web application
'cfusion.ear#cfusion.war' could not be found to accept sessions for
replication.
at
jrun.servlet.session.SessionReplicationService.replicate(SessionReplicationService.java:8 0)
at sun.reflect.GeneratedMethodAccessor51.invoke(Unknown
Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native
Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown
Source)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown
Source)
at java.lang.Thread.run(Unknown Source)
CFMX 7.01 MULTISERVER:
My set-up, installed as multiserver. create new instance from
CF Admin. Cluster them from Jrun Admin. I followed almost all
instructions from live doc, and also help from other blogs.
So far i could not findout why session can not replicate on
same machine.
Is any body have idea about above error.
Thanks for your help in-advance

In my config.xml, I have:
<cluster>
<name>MyCluster</name>
<cluster-address/>
<default-load-algorithm>round-robin</default-load-algorithm>
<cluster-messaging-mode>unicast</cluster-messaging-mode>
<frontend-host>192.168.6.6</frontend-host>
<frontend-http-port>80</frontend-http-port>
<frontend-https-port>443</frontend-https-port>
</cluster>
I already posted my weblogic.xml

Session replication not working with OAM clusters

Hi,
We have a enterprise deployment of OAM 11.1.1.5.0, and we are using a cluster or OAM managed servers. Server#A (fano1) hosts the admin + OAM managed server, server#B (fano2) hosts the second OAM managed server.
What we have noticed in general is that when accessing the OAM admin console (on server#A, fano1), we get prompted to login and then we get a "Error 404--Not Found". It seems that we are getting authenticated against server#B (fano2) and our session is not getting replicated to server#A (fano1). After exactly 60 seconds, if we were to simply reload the URL in the same browser window, we can get in. This is with "database replication of sessions" enabled. If I disable that, then I will never be able to login to the admin console.
The admin server logs contain the error message:
[2011-12-22T16:41:52.471-05:00] [AdminServer] [WARNING] [] [oracle.oam.agent-default] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: f4a544324f1d0f29:2ccc59c7:13467aaf744:-8000-0000000000000182,0] [APP: oam_admin#11.1.1.3.0] OAM Server request failed: OpCode = 19 [GetSessionInfo], Returned Status = Major code: 71(SessionInvalid) Minor code: 2(NoCode)
[2011-12-22T16:41:52.473-05:00] [AdminServer] [WARNING] [OAMAGENT-00406] [oracle.oam.agent-default] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: f4a544324f1d0f29:2ccc59c7:13467aaf744:-8000-0000000000000182,0] [APP: oam_admin#11.1.1.3.0] Invalid authentication token: AccessService INVALID_USER_SESSION
One other point is that we are using virtual IPs and each server (Admin + 2 managed servers) is listening to its own virtual IP.
Does anyone have any suggestions on what this could be. My thinking is that coherence based session replication is not working. However I have no way to say that for sure. Is there any way to enable some more logging from either OAM or Coherence that would help verify if sessions are getting replicated or not? I have tried putting the entire system in TRACE:32 but that generates too much data.
Thanks
Aspi Engineer
Putnam Investments

Did you get solution to this one.
ThanksKrishna

Clustering/Session Replication

Hi,
I know that's a fairly basic question, but I just want to make sure I am not missing anything here.
We have an application which runs on a cluster of WebLogics and the user sometimes is requested to sign in again (it seems like it hit another instance and the session is not there).
The admins from Weblogic say there is NO WAY to disable Session Replication when running Weblogic in a cluster, which makes total sense. They say, however, that if the application doesn't serialize its session, then Weblogic can't handle the serialization. In short, they say it's an application issue.
The developers say the application is written properly, and that the problem is in Weblogic's side.
Although I am still a developer (for my own projects), my role here doesn't allow me to look into the code, how can I show the developers that WebLogic is setup correctly and that they need to fix their code?
Regards

Information about session replication can be found here: http://docs.oracle.com/cd/E21764_01/web.1111/e13709/failover.htm#i1024620
it contains a section 'Requirements for HTTP Session State Replication' that might be helpful to you.
Also important to note is, how the load balancer handles session binding and the WebLogic cookie
http://docs.oracle.com/cd/E21764_01/web.1111/e13709/load_balancing.htm#i1026939

Profile locked by another local session, please retry later

Hi when i ran the "netweaver initial setup" task, this error occurs
"com.sap.rprof.dbprofiles.AccessException: Profile locked by another
local session, please retry later.", i checked in TCODE SM12 and saw an
register "001 PILDUSER 16:57:44 X AII_PROFILES AIICOMMON
exchange_profile.xml 1 0", i saw the sap note 1333205, and update my
Support Packages to Stack 11 of Netweaver 7.1, but not was solved.
Thanks
Josue Neto

Dear all,
we had the same problem on our PI7.0 SP21, that CTS was not working and IntegrationBuilder was not operational, aso...
The lock "AII_TABLES" was visible in SM12 and appeared immediately after restart or manual deletion.
We have opened a very high message to SAP, as the recomm. from SAP Note 1602945 did no help. Once they replied we have additionaly applied SAP_JTECHS PL30 and added parameter "com.sap.aii.ib.remote.exprof.enabled=TRUE" to the exchange profile per each server node.
After these changes and restart, the lock is not active anymore - this was implemented and tested on Dev and Test systems. We will proceed with the Prod later on, we believe it helps.
Regards,
Peter Bajza

Session replication failed

I have multi server environment. Two phisical servers.
Balanced by a hardware load balancer. Each of the server have
multiple instances of ColdFusion. Main instance (cfusion), and
cf_instance_server1_id_1 and cf_instance_server2_2.
CFUSION instance is used as administrative instance only,
other two instances are hosting independent applications.
cf_instance_server1_id_1 is clustered with
cf_instance_server2_id_1, same applies for second instance.
jrun/logs folder is filling up fast with following error
jsession is on.
Please advise

Mikkhait wrote:
> CFUSION instance is used as administrative instance
only, other two instances
> are hosting independent applications.
cf_instance_server1_id_1 is clustered
> with cf_instance_server2_id_1, same applies for second
instance.
> 11/07 10:16:39 error Setup of session replication
failed.
> [1]java.net.ConnectException: Connection refused:
connect
You have a network issue. Make sure there are no firewalls
between both
servers and your routing is set up correctly. If that doesn't
work, we
need a dump of the route table, the interface configuration
and the
overview of instances from the cluster manager.
Jochem
Jochem van Dieten
Adobe Community Expert for ColdFusion

Another error - session replication

Similar Messages

Maybe you are looking for