13 Replies Latest reply on Apr 30, 2003 10:03 AM by cholliday

    Problem with UIL

    mekatoka

      Hi,

      I am using JBoss 3.0.6, UIL

      I have a machine in my lab that has nothing but a fresh OS installed recently. We have developed an application that runs fine on other machines but when run on this machine, the machine cant seem to send out asynchronous messages.

      Lets call this machine X

      Scenario:
      ---------

      I want to run a Jboss server instance on X and send an asynchronous message to another Jboss server instance running on another machine say Y.

      Note:
      ------
      I have the localhost value in /etc/hosts to my network ip address and not 127.0.0.1


      Likewise I have another machine say A that does exactly the reverse as X ..viz., it can send but cant recieve asynchronous messages. Plain Socket calls run perfect on both of these systems.

      What are the config settings on machine A ?? I am not sure ? So we can leave that out. But machine X has nothing but clean OS installed.

      ** No firewalls on the network
      ** Machine X runs DHCP server, I tried turning it off but still no change.


      Thanks in advance

      Regards

      Meka Toka

        • 1. Re: Problem with UIL

          When you say you have localhost set to the ip address
          don't you mean the real host name?

          Regards,
          Adrian

          • 2. Re: Problem with UIL
            mekatoka

            No, i set the ip address there. The ip address of that machine in the network is 192.168.1.106.

            Does it make difference ?

            I have followed almost all the posts on firewall, NAT, UIL etc etc. now i remember that everybody used host name. Is it a huge difference ?
            If yes, in what way ?

            Regards

            Meka Toka

            • 3. Re: Problem with UIL
              mekatoka

              Hi,

              The oddity here is that the application works on every other system in my network except that ?? At the end of the day we even used a network analyzer to see if the packets were going or not ?

              We noticed that it is recieving JMS messages but cant send them out.

              what could be the reason ?

              Regards

              Meka Toka

              • 4. Re: Problem with UIL

                This might be a stupid question, but can you
                ping from/to that server?

                Regards,
                Adrian

                • 5. Re: Problem with UIL
                  mekatoka

                  Yes, that sounds stupid to me too ?? But thats whats been happening.

                  And yes i can ping the machine. I have an application client which is registered to a topic on the server, and when it has to send anything to the server it uses a Queue.

                  When i run this application client, the messages dont go through the queue, on the other hand when you the server is sending updates (messages) to all clients registered on the topic, it can recieve the message.

                  For more info, I am running Windows 2000 Advanced Server.

                  Regards

                  Meka Toka

                  • 6. Re: Problem with UIL
                    mekatoka

                    Hi Adrian,

                    Apoligies, for the line Yes, that sounds stupid to me too ? ... in my post.


                    I was referring to my question as stupid. :)

                    Regards

                    Meka Toka

                    • 7. Re: Problem with UIL

                      Add log4j.jar to your client's classpath
                      and configure trace for jboss.mq





                      Then try to send one message.
                      Maybe this will show something.

                      Try the same on the server as well,
                      you will need to remove the Threshold on the file appender.

                      Regards,
                      Adrian

                      • 8. Re: Problem with UIL
                        mekatoka

                         

                        "mekatoka" wrote:
                        Will try that and will let you know the result. Please watch this thread.

                        Regards

                        Meka Toka


                        • 9. Re: Problem with UIL
                          mekatoka

                          Hi warjort,

                          I had to adopt a temporary solution for the above problem for the time being. Now i am getting back to solve it. Before configuring log4j i wanted to try out a small application. Here's whats there

                          A simple client and an application deployed on JBOSS server with 1 SB, 1 EB and 1 MDB. What i noticed is that there are two systems in my lab which show inconsistent behavior, in sense they work only with some systems running JBOSS.

                          However their pattern has been consistent ... they are able to send messages to any system(with JBOSS) on queues but they cant recieve messages on topic.

                          Here is the stack trace that results when the server is unable to send the message

                          [I]
                          2003-04-29 16:53:10,625 WARN [org.jboss.mq.server.ClientConsumer:ID:7] Could not send messages to a receiver.
                          java.rmi.RemoteException: Cannot contact the remote object; nested exception is:
                          java.net.SocketException: Connection reset
                          at org.jboss.mq.il.oil.OILClientIL.waitAnswer(OILClientIL.java:211)
                          at org.jboss.mq.il.oil.OILClientIL.receive(OILClientIL.java:141)
                          at org.jboss.mq.server.ClientConsumer.doWork(ClientConsumer.java:295)
                          at org.jboss.mq.threadpool.ThreadPool$WorkerThread.run(ThreadPool.java:230)
                          Caused by: java.net.SocketException: Connection reset
                          at java.net.SocketInputStream.read(SocketInputStream.java:168)
                          at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
                          at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
                          at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2133)
                          at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2316)
                          at java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2383)
                          at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2455)
                          at java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputStream.java:2604)
                          at java.io.ObjectInputStream.readByte(ObjectInputStream.java:845)
                          at org.jboss.mq.il.oil.OILClientIL.waitAnswer(OILClientIL.java:200)
                          ... 3 more
                          2003-04-29 16:53:10,625 ERROR [org.jboss.mq.server.JMSDestinationManager] The connection to client ID:7 failed.
                          2003-04-29 16:53:16,515 WARN [org.jboss.mq.il.oil.OILServerILService] Client request resulted in a server exception:
                          org.jboss.mq.SpyJMSException: Could not pong; - nested throwable: (java.rmi.RemoteException: Cannot contact the remote object; nested exception is:
                          java.net.SocketException: Connection reset by peer: socket write error)
                          at org.jboss.mq.server.JMSDestinationManager.ping(JMSDestinationManager.java:864)
                          at org.jboss.mq.server.JMSServerInterceptorSupport.ping(JMSServerInterceptorSupport.java:308)
                          at org.jboss.mq.server.TracingInterceptor.ping(TracingInterceptor.java:645)
                          at org.jboss.mq.server.JMSServerInvoker.ping(JMSServerInvoker.java:310)
                          at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.java:324)
                          at java.lang.Thread.run(Thread.java:536)
                          Caused by: java.rmi.RemoteException: Cannot contact the remote object; nested exception is:
                          java.net.SocketException: Connection reset by peer: socket write error
                          at org.jboss.mq.il.oil.OILClientIL.waitAnswer(OILClientIL.java:211)
                          at org.jboss.mq.il.oil.OILClientIL.pong(OILClientIL.java:115)
                          at org.jboss.mq.server.JMSDestinationManager.ping(JMSDestinationManager.java:860)
                          ... 5 more
                          Caused by: java.net.SocketException: Connection reset by peer: socket write error
                          at java.net.SocketOutputStream.socketWrite0(Native Method)
                          at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
                          at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
                          at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:69)
                          at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:127)
                          at java.io.ObjectOutputStream$BlockDataOutputStream.flush(ObjectOutputStream.java:1583)
                          at java.io.ObjectOutputStream.flush(ObjectOutputStream.java:639)
                          at org.jboss.mq.il.oil.OILClientIL.waitAnswer(OILClientIL.java:199)
                          ... 7 more
                          [/I]

                          I am also going to configure and check the log4j now, can you think of anything ?

                          MORE INFO
                          ----------------

                          JBOSS 3.0.6, CMP 2.0, no firewalls, all WINDOWS 2k Adv Srvrs

                          Regards,

                          Meka Toka


                          • 10. Re: Problem with UIL
                            mekatoka

                            Hi warjort,

                            I had to adopt a temporary solution for the above problem for the time being. Now i am getting back to solve it. Before configuring log4j i wanted to try out a small application. Here's whats there

                            A simple client and an application deployed on JBOSS server with 1 SB, 1 EB and 1 MDB. What i noticed is that there are two systems in my lab which show inconsistent behavior, in sense they work only with some systems running JBOSS.

                            However their pattern has been consistent ... they are able to send messages to any system(with JBOSS) on queues but they cant recieve messages on topic.

                            Here is the stack trace that results when the server is unable to send the message


                            2003-04-29 16:53:10,625 WARN [org.jboss.mq.server.ClientConsumer:ID:7] Could not send messages to a receiver.
                            java.rmi.RemoteException: Cannot contact the remote object; nested exception is:
                            java.net.SocketException: Connection reset
                            at org.jboss.mq.il.oil.OILClientIL.waitAnswer(OILClientIL.java:211)
                            at org.jboss.mq.il.oil.OILClientIL.receive(OILClientIL.java:141)
                            at org.jboss.mq.server.ClientConsumer.doWork(ClientConsumer.java:295)
                            at org.jboss.mq.threadpool.ThreadPool$WorkerThread.run(ThreadPool.java:230)
                            Caused by: java.net.SocketException: Connection reset
                            at java.net.SocketInputStream.read(SocketInputStream.java:168)
                            at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
                            at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
                            at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2133)
                            at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2316)
                            at java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2383)
                            at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2455)
                            at java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputStream.java:2604)
                            at java.io.ObjectInputStream.readByte(ObjectInputStream.java:845)
                            at org.jboss.mq.il.oil.OILClientIL.waitAnswer(OILClientIL.java:200)
                            ... 3 more
                            2003-04-29 16:53:10,625 ERROR [org.jboss.mq.server.JMSDestinationManager] The connection to client ID:7 failed.
                            2003-04-29 16:53:16,515 WARN [org.jboss.mq.il.oil.OILServerILService] Client request resulted in a server exception:
                            org.jboss.mq.SpyJMSException: Could not pong; - nested throwable: (java.rmi.RemoteException: Cannot contact the remote object; nested exception is:
                            java.net.SocketException: Connection reset by peer: socket write error)
                            at org.jboss.mq.server.JMSDestinationManager.ping(JMSDestinationManager.java:864)
                            at org.jboss.mq.server.JMSServerInterceptorSupport.ping(JMSServerInterceptorSupport.java:308)
                            at org.jboss.mq.server.TracingInterceptor.ping(TracingInterceptor.java:645)
                            at org.jboss.mq.server.JMSServerInvoker.ping(JMSServerInvoker.java:310)
                            at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.java:324)
                            at java.lang.Thread.run(Thread.java:536)
                            Caused by: java.rmi.RemoteException: Cannot contact the remote object; nested exception is:
                            java.net.SocketException: Connection reset by peer: socket write error
                            at org.jboss.mq.il.oil.OILClientIL.waitAnswer(OILClientIL.java:211)
                            at org.jboss.mq.il.oil.OILClientIL.pong(OILClientIL.java:115)
                            at org.jboss.mq.server.JMSDestinationManager.ping(JMSDestinationManager.java:860)
                            ... 5 more
                            Caused by: java.net.SocketException: Connection reset by peer: socket write error
                            at java.net.SocketOutputStream.socketWrite0(Native Method)
                            at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
                            at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
                            at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:69)
                            at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:127)
                            at java.io.ObjectOutputStream$BlockDataOutputStream.flush(ObjectOutputStream.java:1583)
                            at java.io.ObjectOutputStream.flush(ObjectOutputStream.java:639)
                            at org.jboss.mq.il.oil.OILClientIL.waitAnswer(OILClientIL.java:199)
                            ... 7 more


                            I am also going to configure and check the log4j now, can you think of anything ?

                            MORE INFO
                            ----------------

                            JBOSS 3.0.6, CMP 2.0, no firewalls, all WINDOWS 2k Adv Srvrs

                            Regards,

                            Meka Toka

                            • 11. Re: Problem with UIL
                              cholliday

                              I think I have been seeing this problem for about a month. See http://www.jboss.org/modules/bb/index.html?module=bb&op=viewtopic&t= had a production machine encounter this problem after running for 6 months. I was able to get it up and working on a different machine. I am in the process of try to get a new production machine up and running but I ran into the same problem on this machine. So right now I have everything working on 2 linux boxes but I cannot get it to work on 2 other linux boxes. Same similar thing. I can send messages over a queue but I cannot receive them over a topic. My network settings seem to be them same on all 4 four servers. I have tried everything I can think of.

                              Christian

                              • 12. Re: Problem with UIL
                                cholliday

                                My trace looks like this on the topic message is this

                                2003-04-30 05:00:58,982 TRACE [org.jboss.mq.server.TracingInterceptor] CALLED : addMessage
                                2003-04-30 05:00:58,982 TRACE [org.jboss.mq.server.TracingInterceptor] ARG : org.jboss.mq.SpyObjectMessage {
                                Header {
                                jmsDestination : TOPIC.RIGHTS_PRD
                                jmsDeliveryMode : 1
                                jmsExpiration : 1051693858981
                                jmsPriority : 4
                                jmsMessageID : ID:6-10516932589811
                                jmsTimeStamp : 1051693258981
                                jmsCorrelationID: null
                                jmsReplyTo : null
                                jmsType : null
                                jmsRedelivered : false
                                jmsPropertiesReadWrite:true
                                msgReadOnly : false
                                producerClientId: ID:6
                                }
                                }
                                2003-04-30 05:00:58,983 TRACE [org.jboss.mq.security.SecurityManager] Checking authorize on subjectInfo: SubjectInfo {subject=Subject:
                                Principal: guest
                                Principal: Roles(members:guest)
                                ;principal=null;roles=Roles(members:guest) for rolePrincipals [guest]
                                2003-04-30 05:00:58,984 TRACE [org.jboss.mq.server.MessageCache] counter lock aquire 14
                                2003-04-30 05:00:58,984 TRACE [org.jboss.mq.server.MessageCache] counter lock release 14
                                2003-04-30 05:00:58,984 TRACE [org.jboss.mq.server.MessageCache] add lock aquire message 14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776
                                2003-04-30 05:00:58,984 TRACE [org.jboss.mq.server.MessageCache] add lock aquire lruCache 14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776
                                2003-04-30 05:00:58,984 TRACE [org.jboss.mq.server.MessageCache] add locks release14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776
                                2003-04-30 05:00:58,984 TRACE [org.jboss.mq.server.MessageCache] run lock aquire, validateSoftReferenceDepth
                                2003-04-30 05:00:58,984 TRACE [org.jboss.mq.server.MessageCache] run lock release, validateSoftReferenceDepth
                                2003-04-30 05:00:58,984 TRACE [org.jboss.mq.server.MessageReference] getMessage lock aquire 14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776
                                2003-04-30 05:00:58,984 TRACE [org.jboss.mq.server.MessageCache] messageReferenceUsedEvent lock aquire message 14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776 wasHard=true
                                2003-04-30 05:00:58,984 TRACE [org.jboss.mq.server.MessageCache] messageReferenceUsedEvent lock aquire lrucache 14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776 wasHard=true
                                2003-04-30 05:00:58,984 TRACE [org.jboss.mq.server.MessageCache] messageReferenceUsedEvent locks released 14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776 wasHard=true
                                2003-04-30 05:00:58,984 TRACE [org.jboss.mq.server.MessageReference] getMessage lock released 14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776
                                2003-04-30 05:00:58,985 TRACE [org.jboss.mq.server.MessageReference] getMessage lock aquire 14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776
                                2003-04-30 05:00:58,985 TRACE [org.jboss.mq.server.MessageCache] messageReferenceUsedEvent lock aquire message 14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776 wasHard=true
                                2003-04-30 05:00:58,985 TRACE [org.jboss.mq.server.MessageCache] messageReferenceUsedEvent lock aquire lrucache 14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776 wasHard=true
                                2003-04-30 05:00:58,985 TRACE [org.jboss.mq.server.MessageCache] messageReferenceUsedEvent locks released 14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776 wasHard=true
                                2003-04-30 05:00:58,985 TRACE [org.jboss.mq.server.MessageReference] getMessage lock released 14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776
                                2003-04-30 05:00:58,985 TRACE [org.jboss.mq.server.MessageReference] getMessage lock aquire 14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776
                                2003-04-30 05:00:58,985 TRACE [org.jboss.mq.server.MessageCache] messageReferenceUsedEvent lock aquire message 14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776 wasHard=true
                                2003-04-30 05:00:58,985 TRACE [org.jboss.mq.server.MessageCache] messageReferenceUsedEvent lock aquire lrucache 14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776 wasHard=true
                                2003-04-30 05:00:58,985 TRACE [org.jboss.mq.server.MessageCache] messageReferenceUsedEvent locks released 14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776 wasHard=true
                                2003-04-30 05:00:58,985 TRACE [org.jboss.mq.server.MessageReference] getMessage lock released 14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776
                                2003-04-30 05:00:58,986 TRACE [org.jboss.mq.server.TracingInterceptor] RETURN : addMessage
                                2003-04-30 05:00:58,986 TRACE [org.jboss.mq.server.MessageReference] getMessage lock aquire 14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776
                                2003-04-30 05:00:58,986 TRACE [org.jboss.mq.server.MessageCache] messageReferenceUsedEvent lock aquire message 14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776 wasHard=true
                                2003-04-30 05:00:58,986 TRACE [org.jboss.mq.server.MessageCache] messageReferenceUsedEvent lock aquire lrucache 14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776 wasHard=true
                                2003-04-30 05:00:58,986 TRACE [org.jboss.mq.server.MessageCache] messageReferenceUsedEvent locks released 14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776 wasHard=true
                                2003-04-30 05:00:58,986 TRACE [org.jboss.mq.server.MessageReference] getMessage lock released 14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776
                                2003-04-30 05:00:58,989 TRACE [org.jboss.mq.server.TracingInterceptor] CALLED : acknowledge
                                2003-04-30 05:00:58,989 TRACE [org.jboss.mq.server.TracingInterceptor] ARG : AcknowledgementRequest:ACK,QUEUE.RIGHTS_PRD,ID:14-10517077009481
                                2003-04-30 05:00:58,989 TRACE [org.jboss.mq.server.MessageCache] remove lock aquire message 10 msg=0 hard NOT_STORED NON_PERSISTENT queue=QUEUE.RIGHTS_PRD priority=4 hashCode=5057297 clear=true reset=true
                                2003-04-30 05:00:58,989 TRACE [org.jboss.mq.server.MessageCache] remove lock aquire lrucache 10 msg=0 hard NOT_STORED NON_PERSISTENT queue=QUEUE.RIGHTS_PRD priority=4 hashCode=5057297 clear= true reset=true
                                2003-04-30 05:00:58,989 TRACE [org.jboss.mq.server.MessageCache] remove lock release lrucache 10 msg=0 hard NOT_STORED NON_PERSISTENT queue=QUEUE.RIGHTS_PRD priority=4 hashCode=5057297 clear= true reset=true
                                2003-04-30 05:00:58,989 TRACE [org.jboss.mq.server.MessageReference] clear lock aquire 10 msg=0 hard NOT_STORED NON_PERSISTENT queue=QUEUE.RIGHTS_PRD priority=4 hashCode=5057297
                                2003-04-30 05:00:58,989 TRACE [org.jboss.mq.server.MessageReference] clear lock relased 10 msg=0 hard REMOVED NON_PERSISTENT queue=QUEUE.RIGHTS_PRD priority=4 hashCode=5057297
                                2003-04-30 05:00:58,989 TRACE [org.jboss.mq.server.MessageCache] remove lock release message NOT IN CACHE hashCode=5057297 clear= true reset=true
                                2003-04-30 05:00:58,989 TRACE [org.jboss.mq.server.TracingInterceptor] RETURN : acknowledge
                                2003-04-30 05:00:58,990 TRACE [org.jboss.mq.server.TracingInterceptor] CALLED : receive
                                2003-04-30 05:00:58,990 TRACE [org.jboss.mq.server.TracingInterceptor] ARG : -2147483648
                                2003-04-30 05:00:58,990 TRACE [org.jboss.mq.server.TracingInterceptor] ARG : 0
                                2003-04-30 05:00:58,990 TRACE [org.jboss.mq.security.ServerSecurityInterceptor] Checking receive authorize on SpyDistributedConnection:ID:7/b2cbd5aced0e566f1f84bfe4ca61af4f subId=-2147483648
                                2003-04-30 05:00:58,990 TRACE [org.jboss.mq.security.SecurityManager] Checking authorize on subjectInfo: SubjectInfo {subject=Subject:
                                Principal: guest
                                Principal: Roles(members:guest)
                                ;principal=null;roles=Roles(members:guest) for rolePrincipals [guest]
                                2003-04-30 05:00:58,991 TRACE [org.jboss.mq.server.TracingInterceptor] RETURN : receive
                                2003-04-30 05:00:59,003 TRACE [org.jboss.mq.server.TracingInterceptor] CALLED : acknowledge
                                2003-04-30 05:00:59,003 TRACE [org.jboss.mq.server.TracingInterceptor] ARG : AcknowledgementRequest:ACK,TOPIC.RIGHTS_PRD,ID:6-10516932589811
                                2003-04-30 05:00:59,003 TRACE [org.jboss.mq.server.MessageCache] remove lock aquire message 14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776 clear=true reset=true
                                2003-04-30 05:00:59,003 TRACE [org.jboss.mq.server.MessageCache] remove lock aquire lrucache 14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776 clear= true reset=true
                                2003-04-30 05:00:59,003 TRACE [org.jboss.mq.server.MessageCache] remove lock release lrucache 14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776 clear= true reset=true
                                2003-04-30 05:00:59,004 TRACE [org.jboss.mq.server.MessageReference] clear lock aquire 14 msg=0 hard NOT_STORED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776
                                2003-04-30 05:00:59,004 TRACE [org.jboss.mq.server.MessageReference] clear lock relased 14 msg=0 hard REMOVED NON_PERSISTENT queue=TOPIC.RIGHTS_PRD.ID:13.-2147483648 priority=4 hashCode=32417776
                                2003-04-30 05:00:59,004 TRACE [org.jboss.mq.server.MessageCache] remove lock release message NOT IN CACHE hashCode=32417776 clear= true reset=true
                                2003-04-30 05:00:59,004 TRACE [org.jboss.mq.server.TracingInterceptor] RETURN : acknowledge
                                2003-04-30 05:00:59,009 TRACE [org.jboss.mq.server.TracingInterceptor] CALLED : receive
                                2003-04-30 05:00:59,009 TRACE [org.jboss.mq.server.TracingInterceptor] ARG : -2147483648
                                2003-04-30 05:00:59,009 TRACE [org.jboss.mq.server.TracingInterceptor] ARG : 0
                                2003-04-30 05:00:59,009 TRACE [org.jboss.mq.security.ServerSecurityInterceptor] Checking receive authorize on SpyDistributedConnection:ID:13/f40f7c411e9e2056a9ce5cab0724e10a subId=-2147483648
                                2003-04-30 05:00:59,009 TRACE [org.jboss.mq.security.SecurityManager] Checking authorize on subjectInfo: SubjectInfo {subject=Subject:
                                Principal: guest
                                Principal: Roles(members:guest)
                                ;principal=null;roles=Roles(members:guest) for rolePrincipals [guest]
                                2003-04-30 05:00:59,009 TRACE [org.jboss.mq.server.TracingInterceptor] RETURN : receive

                                • 13. Re: Problem with UIL
                                  cholliday

                                  After comparing your stack trace with mine they don't look like the same problem but they may have a similar cause.