KB Article #160327

XMS message file is full

Problem


XMS Errors seen in Gateway Navigator or Integrator Trace:

message 'null';sent, rolled back:Message file is full.
com.axway.xms.jms.exception.XmsJMSException: Message file is full.

Resolution


The XMS queue has the message file full with messages. In order to empty the queue, you have to use one of these methods (A or B):

- load the profile file
.  synch44/Messaging/runtime/etc/profile

- identify the runtime port and license key:
admin@44su1164:~> grep x_fr synch44/Messaging/runtime/etc/profile
x_frontend_port="4569"

admin@44su1164:~> grep key synch44/Messaging/runtime/etc/conffile
    product_key                 = "3D3HGJ8WNEG--yourkeyhere--J4J4SRMYD73FFH"

- do a backup of Messaging folder:
admin@44su1164:~/synch44/Messaging> xmsadm stop
   Testing Messaging product in system ...
   Connecting to Messaging . -> Ok
   Sending stop request to Messaging . -> Ok
   Shutdown complete
>be sure that ~/bck exists;
admin@44su1164:~> cp -aR synch44/Messaging/ ~/bck/

>check the copied folder size:
admin@44su1164:~> du -ks synch44/Messaging/
306088  synch44/Messaging/
admin@44su1164:~> du -ks bck/Messaging/
306068  bck/Messaging/
> identify the queue manager and queues names:

admin@44su1164:~> xmsstat qmgr
LOCALMSG
admin@44su1164:~> xmsstat queue|grep named
 Message statistics on queue named 'XMS_STL'
 Message statistics on queue named 'XMS_ERROR'
 Message statistics on queue named 'XMS_ADM_REQUEST'
 Message statistics on queue named 'XMS_ADM_REPLY'
 Message statistics on queue named 'GI2IG'
 Message statistics on queue named 'IG2GI'
 
> see the status of queue (and number of messages):
xmsstat queue -i IG2GI
 Message statistics on queue named 'IG2GI'
  Current statistics
   data messages to receive (prio H)                 0
   data messages to receive (prio M)              2000
   data messages to receive (prio L)                 0
   notif messages to receive                         0
   error messages to receive                         0
   indexed messages to receive                       0
   not available messages                            0
  Cumulated statistics since startup
   rollbacked messages sent                          0
   rollbacked messages received                      0
   expired messages                                  0
   messages sent                                  2000
   data messages already received                    0
   notif messages already received                   0
   error messages already received                   0

   
A) use xmsutil to get all messages (to consume):
xmsutil -host 44su1164 -p 4569 -get -qmgr LOCALMSG -queue IG2GI -nb 10000 -nodsp

> you may use into another console (after loading profile) the monitor feature to see in realtime the status:
xmsutil -host 44su1164 -p 4569 -monitor -qmgr localmsg -queue IG2GI




B) use xmsinstall to overwrite the queue manager definitions (where you may change whatever you want), having as effect:
- emptying all data;
- keeping all queues there:

> stop the Messaging (XMS):
admin@44su1164:~/synch44/Messaging> xmsadm stop
   Testing Messaging product in system ...
   Connecting to Messaging . -> Ok
   Sending stop request to Messaging . -> Ok
   Shutdown of Messaging in progress .   Shutdown complete
admin@44su1164:~/synch44/Messaging>

admin@44su1164:~/synch44/Messaging> ./bin/xmsinstall runtime
Configuration of Messaging product
--------------------------------
The product installation home directory is: '/home/admin/synch44/Messaging'
Enter the directory runtime path to the Messaging Server (default: /home/admin/synch44/Messaging/runtime) ?
Messaging is already installed in [/home/admin/synch44/Messaging/runtime].
WARNING: If you change message parameter, ALL messages will be lost.
Do you want to change messages parameter ?  (Y,[N],A)?
Local qmgr LOCALMSG found in Messaging DataBase.
Do you want to use multi license option ? (Y,[N],A)?
Enter your Messaging software key (default: 3D3HG--hereisthekey---RMYD73FFH) ?
Installing Messaging LOGG Environment
Setting I/O Interface for Messaging LOGG files to:
        1 : Unix Style Secure OPEN I/O Interface
        Note : The OPEN I/O Interface can be used in Synchrone mode to
        protect the integrity of Messaging LOGG files in case of a system
        crash or in Normal mode to increase performance.
        Please refer to Messaging UNIX Installation Documentation to select
        the OPEN Interface in Synchrone or Normal mode
        Do you want to use the OPEN Interface in Synchrone mode ?  ([Y],N,A)?
        Do you confirm your choice ([Y],N,A)?
        
Enter the maximum size for messages (less or equals 128 Mo) (default: '4194304', A: abort) :
Enter a listening TCP/IP address for the Messaging Server: (default: 44su1164) ?
Enter a TCP/IP port number for the Messaging Server: (default: '4569', A: abort) :
Do you want to use TLS for remote clients (Y,[N],A)?
Do you want to use security control (Y,[N],A)?
Do you want to use the system console (Y,[N],A)?
Do you want to use Messaging Sentinel notification option (Y,[N],A)?
Do you want to verify the configuration ([Y],N,A)?
Display configuration
---------------------
  local qmgr name      : LOCALMSG
  max message size     : 4194304
  block size           : 2048
  max number of blocks : 51200
  message file size    : 104857600 Bytes
Do you agree with this configuration ([Y],N,A)?
Installing Messaging Environment...
Creating /home/admin/synch44/Messaging/runtime/etc/conffile configuration file ...
Creation ended successfully
Creating file /home/admin/synch44/Messaging/runtime/etc/profile
Creation ended successfully
Warning : could not find example configuration file for the bridge: '/home/admin/synch44/Messaging/etc/xmsbridge'
Updating Default Local Qmgr...
Default Local Qmgr updated.
Installation of Messaging product completed.
admin@44su1164:~/synch44/Messaging>

admin@44su1164:~> xmsstat queue -i IG2GI
 Message statistics on queue named 'IG2GI'
  Current statistics
   data messages to receive (prio H)                 0
   data messages to receive (prio M)                 0
   data messages to receive (prio L)                 0
   notif messages to receive                         0
   error messages to receive                         0
   indexed messages to receive                       0
   not available messages                            0
  Cumulated statistics since startup
   rollbacked messages sent                          0
   rollbacked messages received                      0
   expired messages                                  0
   messages sent                                     0
   data messages already received                    0
   notif messages already received                   0
   error messages already received                   0
admin@44su1164:~>

> if this step has no effect (to empty the queue) try A);

> If you are using in flow Integrator & XMS, be sure that JMS tasks in Task Monitor were started before you will check all flow again.