6 Replies Latest reply on Oct 16, 2008 7:12 PM by Peter Johnson

    Very urgent An EJB3.0 Exception

    zihao shang Newbie

      Our Development Environment was Windows ,and we had achieved logic-communion among web sets with jboss4.2.3 ejb3 which was transfered by tomcat5.5 .
      And ejb3 was just used as interface of data transmission,which accessed business logic code according to the transmitted date.
      That is to say,all the transfers were transmitted by an ejb3 interface .
      There was not any problem of our program when it was being developed and tested on Windows,while we found that jboss client-side frequently could not get the date of jboss server-side during the communication when the program was deployed on formal server,slackware12.
      And what is worse,there was not any exception nor error being thrown both in tomcat and jboss.
      In fact,tomcat has indeed transfered ejb3 of jboss,but we still could get returned value.

        • 1. Re: Very urgent An EJB3.0 Exception
          Peter Johnson Master

          I am sorry, but I do not understand the problem description. What do you mean by "could not get the date of jboss server-side"? And is that what the problem is. or is the problem something else?

          • 2. Re: Very urgent An EJB3.0 Exception
            zihao shang Newbie

             

            "PeterJ" wrote:
            I am sorry, but I do not understand the problem description. What do you mean by "could not get the date of jboss server-side"? And is that what the problem is. or is the problem something else?

            Thanks for PeterJ,I Think the problem come forth Jboss,When Tomcat is running and Jboss is running,Tomcat Call Jboss, The Jboss now and then miss date. Tomcat can't get Date from Jboss!Please tell me what's problem?

            • 3. Re: Very urgent An EJB3.0 Exception
              zihao shang Newbie

              Tomcat local program error message is :
              system error : className(com.just.logic.choose.User) methodName(newqueryByPassid) date(Thu Oct 16 09:46:12 CST 2008)
              at the same time Jboss log message is :
              2008-10-16 09:46:11,811 DEBUG [org.jboss.remoting.transport.socket.ClientSocketWrapper] reset timeout: 29000
              2008-10-16 09:46:12,110 DEBUG [org.jboss.remoting.transport.socket.ClientSocketWrapper] reset timeout: 29000
              2008-10-16 09:46:12,782 DEBUG [org.jboss.remoting.transport.socket.ServerThread] WorkerThread#3[127.0.0.1:53903] closing socketWrapper: ServerSocketWrapper[Socket[addr=/127.0.0.1,port=53903,localport=3873].114b553]
              2008-10-16 09:46:12,783 DEBUG [org.jboss.remoting.transport.socket.ServerSocketWrapper] wrote CLOSING
              2008-10-16 09:46:12,783 DEBUG [org.jboss.remoting.transport.socket.SocketWrapper] ServerSocketWrapper[Socket[addr=/127.0.0.1,port=53903,localport=3873].114b553] closing
              2008-10-16 09:46:12,783 DEBUG [org.jboss.remoting.transport.socket.ServerThread] WorkerThread#2[127.0.0.1:53902] closing socketWrapper: ServerSocketWrapper[Socket[addr=/127.0.0.1,port=53902,localport=3873].8c7c7f]
              2008-10-16 09:46:12,784 DEBUG [org.jboss.remoting.transport.socket.ServerSocketWrapper] wrote CLOSING
              2008-10-16 09:46:12,784 DEBUG [org.jboss.remoting.transport.socket.SocketWrapper] ServerSocketWrapper[Socket[addr=/127.0.0.1,port=53902,localport=3873].8c7c7f] closing

              • 4. Re: Very urgent An EJB3.0 Exception
                zihao shang Newbie

                Tomcat local program error message is :
                system error : className(com.just.logic.UserAndUserinfo) methodName(queryById) time(2008-10-16 15:9:53,728)?param([[Ljava.lang.Object;@588ec0])

                at the same time Jboss log message is :
                2008-10-16 15:09:53,545 DEBUG [org.jboss.remoting.transport.socket.ServerSocketWrapper] wrote CLOSING
                2008-10-16 15:09:53,545 DEBUG [org.jboss.remoting.transport.socket.SocketWrapper] ServerSocketWrapper[Socket[addr=/127.0.0.1,port=41265,localport=3873].759d75] closing
                2008-10-16 15:09:53,555 DEBUG [org.jboss.remoting.transport.socket.ClientSocketWrapper] reset timeout: 29000
                2008-10-16 15:09:53,733 DEBUG [org.jboss.remoting.transport.socket.ServerThread] WorkerThread#0[127.0.0.1:41266] closing socketWrapper: ServerSocketWrapper[Socket[addr=/127.0.0.1,port=41266,localport=3873].14cc136]
                2008-10-16 15:09:53,734 DEBUG [org.jboss.remoting.transport.socket.ServerSocketWrapper] wrote CLOSING
                2008-10-16 15:09:53,734 DEBUG [org.jboss.remoting.transport.socket.SocketWrapper] ServerSocketWrapper[Socket[addr=/127.0.0.1,port=41266,localport=3873].14cc136] closing

                netstat -nac | grep 3873 message is :
                tcp 0 0 127.0.0.1:3873 127.0.0.1:41265 ESTABLISHED
                tcp6 0 0 ::ffff:127.0.0.1:41266 ::ffff:127.0.0.1:3873 ESTABLISHED

                • 5. Re: Very urgent An EJB3.0 Exception
                  Wolfgang Knauf Master

                  Maybe someone can help you, if you provide more infos. Up to now, this post is unfortunately a sample for bad "calling for help"(http://catb.org/~esr/faqs/smart-questions.html).

                  Please provide:
                  -an overview of your application architecture (only parts which are relevant for this problem)
                  -small code snippets for the client/server parts of your app, where communication fails

                  Check for a "real" exception. Maybe you have an empty try/catch in your app? It is really rare that an internal exception occurs without stack trace or even exception class name.

                  And avoid the word "urgent" in your title ;-).

                  Best regards

                  Wolfgang

                  • 6. Re: Very urgent An EJB3.0 Exception
                    Peter Johnson Master

                    Wolfgang is absolutely correct. If we cannot understand your question we cannot help you.

                    I have no idea what you mean when you say "Tomcat can't get Date from Jboss!" This is especially confusing since the date is obtained from the operating system, and Tomcat is embedded within JBossAS. And I have no idea how the log entries, or netstat output, you posted are relate to the problem.