11 Replies Latest reply on Nov 29, 2000 11:31 PM by 3004

    Problem with javax.mail.Session in cluster

    3004
      Encounter the following exception when running on Solaris cluster. Is
                the exception fatal?
                
                Fri Nov 03 20:04:42 CST 2000:<I> <ListenThread> Listening on port: 7001
                address
                : 192.168.1.239
                Fri Nov 03 20:04:42 CST 2000:<I> <Posix Performance Pack> System has
                file descr
                iptor limits of - soft: '1024', hard: '1024'
                Fri Nov 03 20:04:42 CST 2000:<I> <Posix Performance Pack> Using
                effective filedescriptor limit of: '1024' open sockets/files.
                Fri Nov 03 20:04:42 CST 2000:<I> <Posix Performance Pack> Allocating:
                '3' POSIX
                reader threads
                Fri Nov 03 20:04:42 CST 2000:<E> <MulticastSocket> Error sending blocked
                messag
                e
                java.io.IOException: Class javax.mail.Session with code=-1 does not
                implement S
                erializable, Externalizable or WLSerializable
                at java.lang.Throwable.fillInStackTrace(Native Method)
                at java.lang.Throwable.fillInStackTrace(Compiled Code)
                at java.lang.Throwable.<init>(Compiled Code)
                at java.lang.Exception.<init>(Compiled Code)
                at java.io.IOException.<init>(Compiled Code)
                at
                weblogic.common.internal.WLObjectOutputStreamBase.writeObjectBody(Co
                a:92)
                at
                weblogic.common.internal.WLObjectOutputStreamBase.writePublicSerializable(Compiled
                Code)
                at
                weblogic.common.internal.WLObjectOutputStreamBase.writeObjectBody(Compiled
                Code)
                at
                weblogic.common.internal.WLObjectOutputStreamBase.writeObject(Compiled
                Code)
                at
                weblogic.common.internal.WLObjectOutputStreamBase.writeObjectWL(Compiled
                Code)
                at
                weblogic.common.internal.WLObjectOutputStreamBase.writeArrayList(Compiled
                Code)
                at
                weblogic.cluster.Announcement.writeObject(Announcement.java:75)
                at
                weblogic.common.internal.WLObjectOutputStreamBase.writePublicSerializable(Compiled
                Code)
                at
                weblogic.common.internal.WLObjectOutputStreamBase.writeObjectBody(Compiled
                Code)
                at
                weblogic.common.internal.WLObjectOutputStreamBase.writeObject(Compiled
                Code)
                at
                weblogic.common.internal.WLObjectOutputStreamBase.writeObjectWL(Compiled
                Code)
                at weblogic.cluster.TMSocket.send(Compiled Code)
                at weblogic.cluster.TMSocket.start(Compiled Code)
                at
                weblogic.cluster.ClusterManager.start(ClusterManager.java:166)
                at weblogic.cluster.ClusterMain.start(ClusterMain.java:270)
                at weblogic.t3.srvr.T3Srvr.start(Compiled Code)
                at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:827)
                at java.lang.reflect.Method.invoke(Native Method)
                at weblogic.Server.startServerDynamically(Server.java:99)
                at weblogic.Server.main(Server.java:65)
                at weblogic.Server.main(Server.java:55)
                
                Fri Nov 03 20:04:43 CST 2000:<I> <WebLogicServer> WebLogic Server
                started
                Fri Nov 03 20:05:07 CST 2000:<I> <ServletContext-General> classes: init
                
                
                
                
        • 1. Re: Problem with javax.mail.Session in cluster
          3004
          mail.Session is a final non serializable class and hence you are seeing this
                    exception. Are you by any chance binding this into jndi tree.
                    
                    - Prasad
                    Wong Kok Wai wrote:
                    
                    > Encounter the following exception when running on Solaris cluster. Is
                    > the exception fatal?
                    >
                    > Fri Nov 03 20:04:42 CST 2000:<I> <ListenThread> Listening on port: 7001
                    > address
                    > : 192.168.1.239
                    > Fri Nov 03 20:04:42 CST 2000:<I> <Posix Performance Pack> System has
                    > file descr
                    > iptor limits of - soft: '1024', hard: '1024'
                    > Fri Nov 03 20:04:42 CST 2000:<I> <Posix Performance Pack> Using
                    > effective filedescriptor limit of: '1024' open sockets/files.
                    > Fri Nov 03 20:04:42 CST 2000:<I> <Posix Performance Pack> Allocating:
                    > '3' POSIX
                    > reader threads
                    > Fri Nov 03 20:04:42 CST 2000:<E> <MulticastSocket> Error sending blocked
                    > messag
                    > e
                    > java.io.IOException: Class javax.mail.Session with code=-1 does not
                    > implement S
                    > erializable, Externalizable or WLSerializable
                    > at java.lang.Throwable.fillInStackTrace(Native Method)
                    > at java.lang.Throwable.fillInStackTrace(Compiled Code)
                    > at java.lang.Throwable.<init>(Compiled Code)
                    > at java.lang.Exception.<init>(Compiled Code)
                    > at java.io.IOException.<init>(Compiled Code)
                    > at
                    > weblogic.common.internal.WLObjectOutputStreamBase.writeObjectBody(Co
                    > a:92)
                    > at
                    > weblogic.common.internal.WLObjectOutputStreamBase.writePublicSerializable(Compiled
                    > Code)
                    > at
                    > weblogic.common.internal.WLObjectOutputStreamBase.writeObjectBody(Compiled
                    > Code)
                    > at
                    > weblogic.common.internal.WLObjectOutputStreamBase.writeObject(Compiled
                    > Code)
                    > at
                    > weblogic.common.internal.WLObjectOutputStreamBase.writeObjectWL(Compiled
                    > Code)
                    > at
                    > weblogic.common.internal.WLObjectOutputStreamBase.writeArrayList(Compiled
                    > Code)
                    > at
                    > weblogic.cluster.Announcement.writeObject(Announcement.java:75)
                    > at
                    > weblogic.common.internal.WLObjectOutputStreamBase.writePublicSerializable(Compiled
                    > Code)
                    > at
                    > weblogic.common.internal.WLObjectOutputStreamBase.writeObjectBody(Compiled
                    > Code)
                    > at
                    > weblogic.common.internal.WLObjectOutputStreamBase.writeObject(Compiled
                    > Code)
                    > at
                    > weblogic.common.internal.WLObjectOutputStreamBase.writeObjectWL(Compiled
                    > Code)
                    > at weblogic.cluster.TMSocket.send(Compiled Code)
                    > at weblogic.cluster.TMSocket.start(Compiled Code)
                    > at
                    > weblogic.cluster.ClusterManager.start(ClusterManager.java:166)
                    > at weblogic.cluster.ClusterMain.start(ClusterMain.java:270)
                    > at weblogic.t3.srvr.T3Srvr.start(Compiled Code)
                    > at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:827)
                    > at java.lang.reflect.Method.invoke(Native Method)
                    > at weblogic.Server.startServerDynamically(Server.java:99)
                    > at weblogic.Server.main(Server.java:65)
                    > at weblogic.Server.main(Server.java:55)
                    >
                    > Fri Nov 03 20:04:43 CST 2000:<I> <WebLogicServer> WebLogic Server
                    > started
                    > Fri Nov 03 20:05:07 CST 2000:<I> <ServletContext-General> classes: init
                    
                    
          • 2. Re: Problem with javax.mail.Session in cluster
            3004
            I'm just following the EJB specs and lookup the Session from the JNDI. The session bean
                      works fine in a non-clustered WLS. Initially, I thought it's because I'm using the
                      mail.jar from Sun but the exception still persists when I use SP6.
                      
                      Comments from BEA engineers?
                      
                      Prasad Peddada wrote:
                      
                      > mail.Session is a final non serializable class and hence you are seeing this
                      > exception. Are you by any chance binding this into jndi tree.
                      >
                      > - Prasad
                      > Wong Kok Wai wrote:
                      >
                      > > Encounter the following exception when running on Solaris cluster. Is
                      > > the exception fatal?
                      > >
                      > > Fri Nov 03 20:04:42 CST 2000:<I> <ListenThread> Listening on port: 7001
                      > > address
                      > > : 192.168.1.239
                      > > Fri Nov 03 20:04:42 CST 2000:<I> <Posix Performance Pack> System has
                      > > file descr
                      > > iptor limits of - soft: '1024', hard: '1024'
                      > > Fri Nov 03 20:04:42 CST 2000:<I> <Posix Performance Pack> Using
                      > > effective filedescriptor limit of: '1024' open sockets/files.
                      > > Fri Nov 03 20:04:42 CST 2000:<I> <Posix Performance Pack> Allocating:
                      > > '3' POSIX
                      > > reader threads
                      > > Fri Nov 03 20:04:42 CST 2000:<E> <MulticastSocket> Error sending blocked
                      > > messag
                      > > e
                      > > java.io.IOException: Class javax.mail.Session with code=-1 does not
                      > > implement S
                      > > erializable, Externalizable or WLSerializable
                      > > at java.lang.Throwable.fillInStackTrace(Native Method)
                      > > at java.lang.Throwable.fillInStackTrace(Compiled Code)
                      > > at java.lang.Throwable.<init>(Compiled Code)
                      > > at java.lang.Exception.<init>(Compiled Code)
                      > > at java.io.IOException.<init>(Compiled Code)
                      > > at
                      > > weblogic.common.internal.WLObjectOutputStreamBase.writeObjectBody(Co
                      > > a:92)
                      > > at
                      > > weblogic.common.internal.WLObjectOutputStreamBase.writePublicSerializable(Compiled
                      > > Code)
                      > > at
                      > > weblogic.common.internal.WLObjectOutputStreamBase.writeObjectBody(Compiled
                      > > Code)
                      > > at
                      > > weblogic.common.internal.WLObjectOutputStreamBase.writeObject(Compiled
                      > > Code)
                      > > at
                      > > weblogic.common.internal.WLObjectOutputStreamBase.writeObjectWL(Compiled
                      > > Code)
                      > > at
                      > > weblogic.common.internal.WLObjectOutputStreamBase.writeArrayList(Compiled
                      > > Code)
                      > > at
                      > > weblogic.cluster.Announcement.writeObject(Announcement.java:75)
                      > > at
                      > > weblogic.common.internal.WLObjectOutputStreamBase.writePublicSerializable(Compiled
                      > > Code)
                      > > at
                      > > weblogic.common.internal.WLObjectOutputStreamBase.writeObjectBody(Compiled
                      > > Code)
                      > > at
                      > > weblogic.common.internal.WLObjectOutputStreamBase.writeObject(Compiled
                      > > Code)
                      > > at
                      > > weblogic.common.internal.WLObjectOutputStreamBase.writeObjectWL(Compiled
                      > > Code)
                      > > at weblogic.cluster.TMSocket.send(Compiled Code)
                      > > at weblogic.cluster.TMSocket.start(Compiled Code)
                      > > at
                      > > weblogic.cluster.ClusterManager.start(ClusterManager.java:166)
                      > > at weblogic.cluster.ClusterMain.start(ClusterMain.java:270)
                      > > at weblogic.t3.srvr.T3Srvr.start(Compiled Code)
                      > > at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:827)
                      > > at java.lang.reflect.Method.invoke(Native Method)
                      > > at weblogic.Server.startServerDynamically(Server.java:99)
                      > > at weblogic.Server.main(Server.java:65)
                      > > at weblogic.Server.main(Server.java:55)
                      > >
                      > > Fri Nov 03 20:04:43 CST 2000:<I> <WebLogicServer> WebLogic Server
                      > > started
                      > > Fri Nov 03 20:05:07 CST 2000:<I> <ServletContext-General> classes: init
                      
                      
            • 3. Re: Problem with javax.mail.Session in cluster
              3004
              Right, I agree, how are you binding this object into the jndi tree. If you are doing the
                        bind, you can actually set it not to replicate the bindings then you won't run into this
                        this problem.
                        
                        - Prasad
                        
                        
                        
                        Wong Kok Wai wrote:
                        
                        > I'm just following the EJB specs and lookup the Session from the JNDI. The session bean
                        > works fine in a non-clustered WLS. Initially, I thought it's because I'm using the
                        > mail.jar from Sun but the exception still persists when I use SP6.
                        >
                        > Comments from BEA engineers?
                        >
                        > Prasad Peddada wrote:
                        >
                        > > mail.Session is a final non serializable class and hence you are seeing this
                        > > exception. Are you by any chance binding this into jndi tree.
                        > >
                        > > - Prasad
                        > > Wong Kok Wai wrote:
                        > >
                        > > > Encounter the following exception when running on Solaris cluster. Is
                        > > > the exception fatal?
                        > > >
                        > > > Fri Nov 03 20:04:42 CST 2000:<I> <ListenThread> Listening on port: 7001
                        > > > address
                        > > > : 192.168.1.239
                        > > > Fri Nov 03 20:04:42 CST 2000:<I> <Posix Performance Pack> System has
                        > > > file descr
                        > > > iptor limits of - soft: '1024', hard: '1024'
                        > > > Fri Nov 03 20:04:42 CST 2000:<I> <Posix Performance Pack> Using
                        > > > effective filedescriptor limit of: '1024' open sockets/files.
                        > > > Fri Nov 03 20:04:42 CST 2000:<I> <Posix Performance Pack> Allocating:
                        > > > '3' POSIX
                        > > > reader threads
                        > > > Fri Nov 03 20:04:42 CST 2000:<E> <MulticastSocket> Error sending blocked
                        > > > messag
                        > > > e
                        > > > java.io.IOException: Class javax.mail.Session with code=-1 does not
                        > > > implement S
                        > > > erializable, Externalizable or WLSerializable
                        > > > at java.lang.Throwable.fillInStackTrace(Native Method)
                        > > > at java.lang.Throwable.fillInStackTrace(Compiled Code)
                        > > > at java.lang.Throwable.<init>(Compiled Code)
                        > > > at java.lang.Exception.<init>(Compiled Code)
                        > > > at java.io.IOException.<init>(Compiled Code)
                        > > > at
                        > > > weblogic.common.internal.WLObjectOutputStreamBase.writeObjectBody(Co
                        > > > a:92)
                        > > > at
                        > > > weblogic.common.internal.WLObjectOutputStreamBase.writePublicSerializable(Compiled
                        > > > Code)
                        > > > at
                        > > > weblogic.common.internal.WLObjectOutputStreamBase.writeObjectBody(Compiled
                        > > > Code)
                        > > > at
                        > > > weblogic.common.internal.WLObjectOutputStreamBase.writeObject(Compiled
                        > > > Code)
                        > > > at
                        > > > weblogic.common.internal.WLObjectOutputStreamBase.writeObjectWL(Compiled
                        > > > Code)
                        > > > at
                        > > > weblogic.common.internal.WLObjectOutputStreamBase.writeArrayList(Compiled
                        > > > Code)
                        > > > at
                        > > > weblogic.cluster.Announcement.writeObject(Announcement.java:75)
                        > > > at
                        > > > weblogic.common.internal.WLObjectOutputStreamBase.writePublicSerializable(Compiled
                        > > > Code)
                        > > > at
                        > > > weblogic.common.internal.WLObjectOutputStreamBase.writeObjectBody(Compiled
                        > > > Code)
                        > > > at
                        > > > weblogic.common.internal.WLObjectOutputStreamBase.writeObject(Compiled
                        > > > Code)
                        > > > at
                        > > > weblogic.common.internal.WLObjectOutputStreamBase.writeObjectWL(Compiled
                        > > > Code)
                        > > > at weblogic.cluster.TMSocket.send(Compiled Code)
                        > > > at weblogic.cluster.TMSocket.start(Compiled Code)
                        > > > at
                        > > > weblogic.cluster.ClusterManager.start(ClusterManager.java:166)
                        > > > at weblogic.cluster.ClusterMain.start(ClusterMain.java:270)
                        > > > at weblogic.t3.srvr.T3Srvr.start(Compiled Code)
                        > > > at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:827)
                        > > > at java.lang.reflect.Method.invoke(Native Method)
                        > > > at weblogic.Server.startServerDynamically(Server.java:99)
                        > > > at weblogic.Server.main(Server.java:65)
                        > > > at weblogic.Server.main(Server.java:55)
                        > > >
                        > > > Fri Nov 03 20:04:43 CST 2000:<I> <WebLogicServer> WebLogic Server
                        > > > started
                        > > > Fri Nov 03 20:05:07 CST 2000:<I> <ServletContext-General> classes: init
                        
                        --
                        Cheers
                        
                        - Prasad
                        
                        
                        
              • 4. Re: Problem with javax.mail.Session in cluster
                3004
                Hi,
                          
                          Thanks for your advice but I don't understand why you mean by "not to replicate the
                          bindings"? I supposed you mean I should only bind to one WLS within the same cluster but how
                          do I specify in the weblogic.properties?
                          
                          TIA.
                          
                          Prasad Peddada wrote:
                          
                          > Right, I agree, how are you binding this object into the jndi tree. If you are doing the
                          > bind, you can actually set it not to replicate the bindings then you won't run into this
                          > this problem.
                          >
                          > - Prasad
                          >
                          > Wong Kok Wai wrote:
                          >
                          > > I'm just following the EJB specs and lookup the Session from the JNDI. The session bean
                          > > works fine in a non-clustered WLS. Initially, I thought it's because I'm using the
                          > > mail.jar from Sun but the exception still persists when I use SP6.
                          > >
                          > > Comments from BEA engineers?
                          > >
                          > > Prasad Peddada wrote:
                          > >
                          > > > mail.Session is a final non serializable class and hence you are seeing this
                          > > > exception. Are you by any chance binding this into jndi tree.
                          > > >
                          > > > - Prasad
                          > > > Wong Kok Wai wrote:
                          > > >
                          > > > > Encounter the following exception when running on Solaris cluster. Is
                          > > > > the exception fatal?
                          > > > >
                          > > > > Fri Nov 03 20:04:42 CST 2000:<I> <ListenThread> Listening on port: 7001
                          > > > > address
                          > > > > : 192.168.1.239
                          > > > > Fri Nov 03 20:04:42 CST 2000:<I> <Posix Performance Pack> System has
                          > > > > file descr
                          > > > > iptor limits of - soft: '1024', hard: '1024'
                          > > > > Fri Nov 03 20:04:42 CST 2000:<I> <Posix Performance Pack> Using
                          > > > > effective filedescriptor limit of: '1024' open sockets/files.
                          > > > > Fri Nov 03 20:04:42 CST 2000:<I> <Posix Performance Pack> Allocating:
                          > > > > '3' POSIX
                          > > > > reader threads
                          > > > > Fri Nov 03 20:04:42 CST 2000:<E> <MulticastSocket> Error sending blocked
                          > > > > messag
                          > > > > e
                          > > > > java.io.IOException: Class javax.mail.Session with code=-1 does not
                          > > > > implement S
                          > > > > erializable, Externalizable or WLSerializable
                          > > > > at java.lang.Throwable.fillInStackTrace(Native Method)
                          > > > > at java.lang.Throwable.fillInStackTrace(Compiled Code)
                          > > > > at java.lang.Throwable.<init>(Compiled Code)
                          > > > > at java.lang.Exception.<init>(Compiled Code)
                          > > > > at java.io.IOException.<init>(Compiled Code)
                          > > > > at
                          > > > > weblogic.common.internal.WLObjectOutputStreamBase.writeObjectBody(Co
                          > > > > a:92)
                          > > > > at
                          > > > > weblogic.common.internal.WLObjectOutputStreamBase.writePublicSerializable(Compiled
                          > > > > Code)
                          > > > > at
                          > > > > weblogic.common.internal.WLObjectOutputStreamBase.writeObjectBody(Compiled
                          > > > > Code)
                          > > > > at
                          > > > > weblogic.common.internal.WLObjectOutputStreamBase.writeObject(Compiled
                          > > > > Code)
                          > > > > at
                          > > > > weblogic.common.internal.WLObjectOutputStreamBase.writeObjectWL(Compiled
                          > > > > Code)
                          > > > > at
                          > > > > weblogic.common.internal.WLObjectOutputStreamBase.writeArrayList(Compiled
                          > > > > Code)
                          > > > > at
                          > > > > weblogic.cluster.Announcement.writeObject(Announcement.java:75)
                          > > > > at
                          > > > > weblogic.common.internal.WLObjectOutputStreamBase.writePublicSerializable(Compiled
                          > > > > Code)
                          > > > > at
                          > > > > weblogic.common.internal.WLObjectOutputStreamBase.writeObjectBody(Compiled
                          > > > > Code)
                          > > > > at
                          > > > > weblogic.common.internal.WLObjectOutputStreamBase.writeObject(Compiled
                          > > > > Code)
                          > > > > at
                          > > > > weblogic.common.internal.WLObjectOutputStreamBase.writeObjectWL(Compiled
                          > > > > Code)
                          > > > > at weblogic.cluster.TMSocket.send(Compiled Code)
                          > > > > at weblogic.cluster.TMSocket.start(Compiled Code)
                          > > > > at
                          > > > > weblogic.cluster.ClusterManager.start(ClusterManager.java:166)
                          > > > > at weblogic.cluster.ClusterMain.start(ClusterMain.java:270)
                          > > > > at weblogic.t3.srvr.T3Srvr.start(Compiled Code)
                          > > > > at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:827)
                          > > > > at java.lang.reflect.Method.invoke(Native Method)
                          > > > > at weblogic.Server.startServerDynamically(Server.java:99)
                          > > > > at weblogic.Server.main(Server.java:65)
                          > > > > at weblogic.Server.main(Server.java:55)
                          > > > >
                          > > > > Fri Nov 03 20:04:43 CST 2000:<I> <WebLogicServer> WebLogic Server
                          > > > > started
                          > > > > Fri Nov 03 20:05:07 CST 2000:<I> <ServletContext-General> classes: init
                          >
                          > --
                          > Cheers
                          >
                          > - Prasad
                          
                          
                • 5. Re: Problem with javax.mail.Session in cluster
                  3004
                  What you could do is have a startup class in that
                            
                            you can do the following
                            
                            Environment env = new Environment();
                            env.setReplicateBindings(false); // this means that the jndi tree won't try to replicate
                            bindings in // a cluster. Thus if you have non serializable object it won't be sent over the
                            wire and hence you
                            // should be fine.
                            Context ctx = new env.getInitialContext();
                            ctx.bind("foo", javax.mail.Session);
                            
                            Hope this helps.
                            
                            - Prasad
                            
                            Wong Kok Wai wrote:
                            
                            > Hi,
                            >
                            > Thanks for your advice but I don't understand why you mean by "not to replicate the
                            > bindings"? I supposed you mean I should only bind to one WLS within the same cluster but how
                            > do I specify in the weblogic.properties?
                            >
                            > TIA.
                            >
                            > Prasad Peddada wrote:
                            >
                            > > Right, I agree, how are you binding this object into the jndi tree. If you are doing the
                            > > bind, you can actually set it not to replicate the bindings then you won't run into this
                            > > this problem.
                            > >
                            > > - Prasad
                            > >
                            > > Wong Kok Wai wrote:
                            > >
                            > > > I'm just following the EJB specs and lookup the Session from the JNDI. The session bean
                            > > > works fine in a non-clustered WLS. Initially, I thought it's because I'm using the
                            > > > mail.jar from Sun but the exception still persists when I use SP6.
                            > > >
                            > > > Comments from BEA engineers?
                            > > >
                            > > > Prasad Peddada wrote:
                            > > >
                            > > > > mail.Session is a final non serializable class and hence you are seeing this
                            > > > > exception. Are you by any chance binding this into jndi tree.
                            > > > >
                            > > > > - Prasad
                            > > > > Wong Kok Wai wrote:
                            > > > >
                            > > > > > Encounter the following exception when running on Solaris cluster. Is
                            > > > > > the exception fatal?
                            > > > > >
                            > > > > > Fri Nov 03 20:04:42 CST 2000:<I> <ListenThread> Listening on port: 7001
                            > > > > > address
                            > > > > > : 192.168.1.239
                            > > > > > Fri Nov 03 20:04:42 CST 2000:<I> <Posix Performance Pack> System has
                            > > > > > file descr
                            > > > > > iptor limits of - soft: '1024', hard: '1024'
                            > > > > > Fri Nov 03 20:04:42 CST 2000:<I> <Posix Performance Pack> Using
                            > > > > > effective filedescriptor limit of: '1024' open sockets/files.
                            > > > > > Fri Nov 03 20:04:42 CST 2000:<I> <Posix Performance Pack> Allocating:
                            > > > > > '3' POSIX
                            > > > > > reader threads
                            > > > > > Fri Nov 03 20:04:42 CST 2000:<E> <MulticastSocket> Error sending blocked
                            > > > > > messag
                            > > > > > e
                            > > > > > java.io.IOException: Class javax.mail.Session with code=-1 does not
                            > > > > > implement S
                            > > > > > erializable, Externalizable or WLSerializable
                            > > > > > at java.lang.Throwable.fillInStackTrace(Native Method)
                            > > > > > at java.lang.Throwable.fillInStackTrace(Compiled Code)
                            > > > > > at java.lang.Throwable.<init>(Compiled Code)
                            > > > > > at java.lang.Exception.<init>(Compiled Code)
                            > > > > > at java.io.IOException.<init>(Compiled Code)
                            > > > > > at
                            > > > > > weblogic.common.internal.WLObjectOutputStreamBase.writeObjectBody(Co
                            > > > > > a:92)
                            > > > > > at
                            > > > > > weblogic.common.internal.WLObjectOutputStreamBase.writePublicSerializable(Compiled
                            > > > > > Code)
                            > > > > > at
                            > > > > > weblogic.common.internal.WLObjectOutputStreamBase.writeObjectBody(Compiled
                            > > > > > Code)
                            > > > > > at
                            > > > > > weblogic.common.internal.WLObjectOutputStreamBase.writeObject(Compiled
                            > > > > > Code)
                            > > > > > at
                            > > > > > weblogic.common.internal.WLObjectOutputStreamBase.writeObjectWL(Compiled
                            > > > > > Code)
                            > > > > > at
                            > > > > > weblogic.common.internal.WLObjectOutputStreamBase.writeArrayList(Compiled
                            > > > > > Code)
                            > > > > > at
                            > > > > > weblogic.cluster.Announcement.writeObject(Announcement.java:75)
                            > > > > > at
                            > > > > > weblogic.common.internal.WLObjectOutputStreamBase.writePublicSerializable(Compiled
                            > > > > > Code)
                            > > > > > at
                            > > > > > weblogic.common.internal.WLObjectOutputStreamBase.writeObjectBody(Compiled
                            > > > > > Code)
                            > > > > > at
                            > > > > > weblogic.common.internal.WLObjectOutputStreamBase.writeObject(Compiled
                            > > > > > Code)
                            > > > > > at
                            > > > > > weblogic.common.internal.WLObjectOutputStreamBase.writeObjectWL(Compiled
                            > > > > > Code)
                            > > > > > at weblogic.cluster.TMSocket.send(Compiled Code)
                            > > > > > at weblogic.cluster.TMSocket.start(Compiled Code)
                            > > > > > at
                            > > > > > weblogic.cluster.ClusterManager.start(ClusterManager.java:166)
                            > > > > > at weblogic.cluster.ClusterMain.start(ClusterMain.java:270)
                            > > > > > at weblogic.t3.srvr.T3Srvr.start(Compiled Code)
                            > > > > > at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:827)
                            > > > > > at java.lang.reflect.Method.invoke(Native Method)
                            > > > > > at weblogic.Server.startServerDynamically(Server.java:99)
                            > > > > > at weblogic.Server.main(Server.java:65)
                            > > > > > at weblogic.Server.main(Server.java:55)
                            > > > > >
                            > > > > > Fri Nov 03 20:04:43 CST 2000:<I> <WebLogicServer> WebLogic Server
                            > > > > > started
                            > > > > > Fri Nov 03 20:05:07 CST 2000:<I> <ServletContext-General> classes: init
                            > >
                            > > --
                            > > Cheers
                            > >
                            > > - Prasad
                            
                            --
                            Cheers
                            
                            - Prasad
                            
                            
                            
                  • 6. Re: Problem with javax.mail.Session in cluster
                    3004
                    Thanks for your advice. I'll give it a try. BTW, this is what I've done:
                              
                              in weblogic.properties, I've defined:
                              
                              weblogic.resource.MailSession.myMailSession=\
                              mail.smtp.host=<name of SMTP host>
                              
                              in ejb-jar.xml for my bean, I've defined:
                              
                              <resource-ref>
                              <description>Mailing ability</description>
                              <res-ref-name>mail/Session</res-ref-name>
                              <res-type>javax.mail.Session</res-type>
                              <res-auth>Container</res-auth>
                              </resource-ref>
                              
                              in the weblogic-ejb-jar.xml, I've defined:
                              
                              <resource-description>
                              <res-ref-name>mail/Session</res-ref-name>
                              <jndi-name>myMailSession</jndi-name>
                              </resource-description>
                              
                              and in the bean implementation, I look up using:
                              
                              Context context = new InitialContext();
                              Session session=(Session)context.lookup("java:comp/env/mail/Session");
                              
                              So like I've said previously, I've followed the specs closely and I didn't do any bindings myself.
                              
                              
                              
                              
                              
                              
                              
                    • 7. Re: Problem with javax.mail.Session in cluster
                      3004
                      Thanks for your advice. I'll give it a try. BTW, this is what I've done:
                                
                                in weblogic.properties, I've defined:
                                
                                weblogic.resource.MailSession.myMailSession=\
                                mail.smtp.host=<name of SMTP host>
                                
                                in ejb-jar.xml for my bean, I've defined:
                                
                                <resource-ref>
                                <description>Mailing ability</description>
                                <res-ref-name>mail/Session</res-ref-name>
                                <res-type>javax.mail.Session</res-type>
                                <res-auth>Container</res-auth>
                                </resource-ref>
                                
                                in the weblogic-ejb-jar.xml, I've defined:
                                
                                <resource-description>
                                <res-ref-name>mail/Session</res-ref-name>
                                <jndi-name>myMailSession</jndi-name>
                                </resource-description>
                                
                                and in the bean implementation, I look up using:
                                
                                Context context = new InitialContext();
                                Session session=(Session)context.lookup("java:comp/env/mail/Session");
                                
                                So like I've said previously, I've followed the specs closely and I didn't do any bindings myself.
                                
                                
                                
                                
                                
                                
                                
                      • 8. Re: Problem with javax.mail.Session in cluster
                        3004
                        You didn't do anything wrong. Since there is a work around, I wouldn't worry about it too much for
                                  now. Any way I will check to see if we can do something to avoid this.
                                  
                                  Thanks
                                  
                                  - Prasad
                                  
                                  Wong Kok Wai wrote:
                                  
                                  > Thanks for your advice. I'll give it a try. BTW, this is what I've done:
                                  >
                                  > in weblogic.properties, I've defined:
                                  >
                                  > weblogic.resource.MailSession.myMailSession=\
                                  > mail.smtp.host=<name of SMTP host>
                                  >
                                  > in ejb-jar.xml for my bean, I've defined:
                                  >
                                  > <resource-ref>
                                  > <description>Mailing ability</description>
                                  > <res-ref-name>mail/Session</res-ref-name>
                                  > <res-type>javax.mail.Session</res-type>
                                  > <res-auth>Container</res-auth>
                                  > </resource-ref>
                                  >
                                  > in the weblogic-ejb-jar.xml, I've defined:
                                  >
                                  > <resource-description>
                                  > <res-ref-name>mail/Session</res-ref-name>
                                  > <jndi-name>myMailSession</jndi-name>
                                  > </resource-description>
                                  >
                                  > and in the bean implementation, I look up using:
                                  >
                                  > Context context = new InitialContext();
                                  > Session session=(Session)context.lookup("java:comp/env/mail/Session");
                                  >
                                  > So like I've said previously, I've followed the specs closely and I didn't do any bindings myself.
                                  
                                  --
                                  Cheers
                                  
                                  - Prasad
                                  
                                  
                                  
                        • 9. Re: Problem with javax.mail.Session in cluster
                          3004
                          I can provide you with a patch and it will come out officially in sp7. Let me know if you need it.
                                    
                                    - Prasad
                                    
                                    Wong Kok Wai wrote:
                                    
                                    > Thanks for your advice. I'll give it a try. BTW, this is what I've done:
                                    >
                                    > in weblogic.properties, I've defined:
                                    >
                                    > weblogic.resource.MailSession.myMailSession=\
                                    > mail.smtp.host=<name of SMTP host>
                                    >
                                    > in ejb-jar.xml for my bean, I've defined:
                                    >
                                    > <resource-ref>
                                    > <description>Mailing ability</description>
                                    > <res-ref-name>mail/Session</res-ref-name>
                                    > <res-type>javax.mail.Session</res-type>
                                    > <res-auth>Container</res-auth>
                                    > </resource-ref>
                                    >
                                    > in the weblogic-ejb-jar.xml, I've defined:
                                    >
                                    > <resource-description>
                                    > <res-ref-name>mail/Session</res-ref-name>
                                    > <jndi-name>myMailSession</jndi-name>
                                    > </resource-description>
                                    >
                                    > and in the bean implementation, I look up using:
                                    >
                                    > Context context = new InitialContext();
                                    > Session session=(Session)context.lookup("java:comp/env/mail/Session");
                                    >
                                    > So like I've said previously, I've followed the specs closely and I didn't do any bindings myself.
                                    
                                    
                          • 10. Re: Problem with javax.mail.Session in cluster
                            3004
                            Hi,
                                      
                                      When will SP7 be released? In any case, would appreciate if you can send the patch to me.
                                      
                                      thanks!
                                      
                                      Prasad Peddada wrote:
                                      
                                      > I can provide you with a patch and it will come out officially in sp7. Let me know if you need it.
                                      >
                                      > - Prasad
                                      >
                                      
                                      
                            • 11. Re: Problem with javax.mail.Session in cluster
                              3004
                              Prasad,
                                        
                                        Hi. We have just run into the same problem. Our portal application
                                        goes live on the 4th. At the moment the decision is to run it
                                        non-clustered until SP7. Can you provides an ETA for SP7? Is the patch
                                        proven?
                                        
                                        David Wade
                                        
                                        >
                                        > I can provide you with a patch and it will come out officially in sp7. Let me know if you need it.
                                        >
                                        > - Prasad
                                        >
                                        > Wong Kok Wai wrote:
                                        >
                                        > > Thanks for your advice. I'll give it a try. BTW, this is what I've done:
                                        > >
                                        > > in weblogic.properties, I've defined:
                                        > >
                                        > > weblogic.resource.MailSession.myMailSession=\
                                        > > mail.smtp.host=<name of SMTP host>
                                        > >
                                        > > in ejb-jar.xml for my bean, I've defined:
                                        > >
                                        > > <resource-ref>
                                        > > <description>Mailing ability</description>
                                        > > <res-ref-name>mail/Session</res-ref-name>
                                        > > <res-type>javax.mail.Session</res-type>
                                        > > <res-auth>Container</res-auth>
                                        > > </resource-ref>
                                        > >
                                        > > in the weblogic-ejb-jar.xml, I've defined:
                                        > >
                                        > > <resource-description>
                                        > > <res-ref-name>mail/Session</res-ref-name>
                                        > > <jndi-name>myMailSession</jndi-name>
                                        > > </resource-description>
                                        > >
                                        > > and in the bean implementation, I look up using:
                                        > >
                                        > > Context context = new InitialContext();
                                        > > Session session=(Session)context.lookup("java:comp/env/mail/Session");
                                        > >
                                        > > So like I've said previously, I've followed the specs closely and I didn't do any bindings myself.