Skip to main content

Strange mobicents.log dimension and content..

6 replies [Last post]
robertofrancesc...
Offline
Joined: 2008-08-28

I'm running tests against my implemented B2BUA using sipp and I found out that I have a huge mobicents.log file containing primarily the following elements:

2008-09-19 18:04:31,809 ERROR [org.mobicents.slee.resource.sip.SipResourceAdaptor] ===> CT is NULL - RTR ? CALLID[bd703f14204213cffe29f8c4889b518c@192.168.1.183] BRANCH[z9hG4bK993b3ad6008e78adbaa9c2f3483489f8] METHOD[INVITE] CODE[200]

AND

2008-09-19 18:24:01,913 ERROR [org.mobicents.slee.runtime.EventRouterImpl] Failed to process initial event for ServiceID[Selector SLEE Service#it.unipg.diei.slee#0.1]
javax.transaction.SystemException: Failed to commit tx. [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] Can't commit because the transaction is in aborted state
at org.mobicents.slee.runtime.transaction.TransactionManagerImpl.commit(TransactionManagerImpl.java:349)
at org.mobicents.slee.runtime.EventRouterImpl.processInitialEvents(EventRouterImpl.java:321)
at org.mobicents.slee.runtime.EventRouterImpl.routeQueuedEvent(EventRouterImpl.java:728)
at org.mobicents.slee.runtime.EventRouterImpl.access$100(EventRouterImpl.java:64)
at org.mobicents.slee.runtime.EventRouterImpl$EventExecutor.run(EventRouterImpl.java:121)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)

Why am I getting these errors, are they related to failed calls?
Does anybody know why I'm not getting these errors on the console but only in this log file that exceeds the GB dimension? I'm using the log4j.xml file used in the sip-load-test.

Thank you for your support!
Roberto.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
robertofrancesc...
Offline
Joined: 2008-08-28

Ok so for the first thing I'll check the 200OK retransmission from the 2nd leg, but why these errors are only written to the file and not on the console using mobicents 1.2.0.BETA3?

My scenario is this one:
caller --> SLEE --> callee

the caller starts the whole thing sending an INVITE to the SLEE that forwards it to the callee creating another leg. So the retransmission of the 200OK could only belong to the second leg....

The second error appears by chance on the log and I don't know why it is there.

You can view the source code of the SBB that manages the leg creation and the call on this page: http://forums.java.net/jive/thread.jspa?threadID=47172&tstart=0

Thank you

robertofrancesc...
Offline
Joined: 2008-08-28

Hello folks I'm resuming this old thread of my own to ask you how can I disable the file output debug on the server.log file of JBOSS and the mobicents.log file of the SLEE itself?

I tried to delete the entry in the JBOSS conf file and in the META-INF file in deploy/mobicents.sar folder but I'm still having the mobicents log written with retransmission dued exception (like CT is NULL).

Thank you and best regards,
Roberto Francescangeli.

alexandrem
Offline
Joined: 2005-10-19

Hi Roberto,

Which version of mobicents are you using?

You should change to 1.2.0.GA version as it does not suffer from that problem, mobicents.log file has been disabled while a fix is not found for this issue: http://code.google.com/p/mobicents/issues/detail?id=278 ( the one from duplicate lines, has been fixed: http://code.google.com/p/mobicents/issues/detail?id=106 ).

To configure JBoss logging you should edit JBOSS_HOME/server//conf/jboss-log4j.xml and set it accordingly to your needs. For instance, you can set the appenders level to something higher than DEBUG/INFO, such as ERROR or FATAL.

For more info about JBoss logging, refer to http://wiki.jboss.org/wiki/Logging

Regards,
Alexandre Mendonca
JBoss R&D

macche
Offline
Joined: 2008-03-05

Hi Alexandre,

i work together with Roberto to the same project. In fact now with 1.2.0.GA version, mobicents.log is disappeared (now we have a server.log file, but that one has normal size in mb and is overwritten every time jboss is restarted).

Thank you for your support!
Emanuele Maccherani

alexandrem
Offline
Joined: 2005-10-19

Hi Emanuele,

Yes, with 1.2.0.GA we dropped mobicents independent logger due to some problems. And you still get a much more stable version ;-)

Regards,
Alexandre Mendonca
JBoss R&D

baranowb
Offline
Joined: 2006-01-09

> I'm running tests against my implemented B2BUA using
> sipp and I found out that I have a huge mobicents.log
> file containing primarily the following elements:
>
> 2008-09-19 18:04:31,809 ERROR
> [org.mobicents.slee.resource.sip.SipResourceAdaptor]
> ===> CT is NULL - RTR ?
> CALLID[bd703f14204213cffe29f8c4889b518c@192.168.1.183]
> BRANCH[z9hG4bK993b3ad6008e78adbaa9c2f3483489f8]
> METHOD[INVITE] CODE[200]
>

You get retransmission - this happens when client transaction is null - it cant be obtained (Its how jsip works).

> AND
>
> 2008-09-19 18:24:01,913 ERROR
> [org.mobicents.slee.runtime.EventRouterImpl] Failed
> to process initial event for ServiceID[Selector SLEE
> Service#it.unipg.diei.slee#0.1]
> javax.transaction.SystemException: Failed to commit
> tx.
> [com.arjuna.ats.internal.jta.transaction.arjunacore.co
> mmitwhenaborted]
> [com.arjuna.ats.internal.jta.transaction.arjunacore.co
> mmitwhenaborted] Can't commit because the transaction
> is in aborted state
> at
> t
> org.mobicents.slee.runtime.transaction.TransactionMana
> gerImpl.commit(TransactionManagerImpl.java:349)
> at
> t
> org.mobicents.slee.runtime.EventRouterImpl.processInit
> ialEvents(EventRouterImpl.java:321)
> at
> t
> org.mobicents.slee.runtime.EventRouterImpl.routeQueued
> Event(EventRouterImpl.java:728)
> at
> t
> org.mobicents.slee.runtime.EventRouterImpl.access$100(
> EventRouterImpl.java:64)
> at
> t
> org.mobicents.slee.runtime.EventRouterImpl$EventExecut
> or.run(EventRouterImpl.java:121)
> at
> t
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask
> (ThreadPoolExecutor.java:885)
> at
> t
> java.util.concurrent.ThreadPoolExecutor$Worker.run(Thr
> eadPoolExecutor.java:907)
> at java.lang.Thread.run(Thread.java:619)
>
>
give scenario.
> Why am I getting these errors, are they related to
> failed calls?
> Does anybody know why I'm not getting these errors on
> the console but only in this log file that exceeds
> the GB dimension? I'm using the log4j.xml file used
> in the sip-load-test.
>
> Thank you for your support!
> Roberto.