-
Hi all,
How to get description of Command_Status Error Codes?.
2009-11-07 00:31:31 UTC by vietdoor
-
I also have this problem, after i changed code in the "submit" function by using ENC_ASCII
request.setShortMessage(shortMessage,Data.ENC_ASCII);.
2009-11-07 00:29:38 UTC by vietdoor
-
sverkera committed revision 81 to the OpenSmpp/SMS Tools SVN repository, changing 1 files.
2009-10-28 02:22:01 UTC by sverkera
-
sverkera committed revision 80 to the OpenSmpp/SMS Tools SVN repository, changing 5 files.
2009-10-28 02:13:18 UTC by sverkera
-
sverkera committed revision 79 to the OpenSmpp/SMS Tools SVN repository, changing 1 files.
2009-10-28 01:05:18 UTC by sverkera
-
paoloc committed revision 78 to the OpenSmpp/SMS Tools SVN repository, changing 1 files.
2009-09-24 16:18:28 UTC by paoloc
-
paoloc committed revision 77 to the OpenSmpp/SMS Tools SVN repository, changing 1 files.
2009-09-24 16:13:09 UTC by paoloc
-
Hi Zsido,
Thanks for raising this. I'll have a look into it and update the ticket soon.
Abhik.
2009-09-23 06:28:08 UTC by abhiksarkar
-
This has already been fixed in SCM by synchronizing (volatile alone would not have been enough to safeguard ++ operation on an int). Can't use AtomicInteger until we commit to >= JDK1.5. Closing comment posting on this closed bug.
2009-08-11 13:22:06 UTC by paoloc
-
The ++sequenceNumber would be threadsafe if this int variable would be volatile.
In this case, the variable wasn't marked volatile and the JVM sometimes used the cached value of the variable. This is now, with the current model but it is safer to protect with synchronize. for better performance the client code could use an AtomicInteger and set the PDU sequence number manually.
2009-08-11 11:06:17 UTC by zsjoska
