# Strange empty message on error log

**URL:** <https://community.wowza.com/t/strange-empty-message-on-error-log/44180>\
**Category:** Wowza Streaming Engine\
**Created:** [May 13, 2015, 12:56pm UTC](https://community.wowza.com/t/strange-empty-message-on-error-log/44180 "2015-05-13T12:56:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Diogo\_Moraes](https://avatars.discourse-cdn.com/v4/letter/d/8baadc/32.png) [@Diogo\_Moraes](https://community.wowza.com/u/Diogo_Moraes)\
**Post date:** [May 13, 2015, 12:56pm UTC](https://community.wowza.com/t/strange-empty-message-on-error-log/44180/1 "2015-05-13T12:56:05Z")

</div>

Hello everyone. I have come across a strange error on my logs. My server was working on production just fine, but out of nowhere I got a invoke(onDisconnect) error message, but when I opened the access and error logs, this is what I see:

Access Log:

```auto
2015-05-11	20:44:28	BRT	comment	server	INFO	200	-	e[94mCHTWSServer::closeRoom >> instanceName: 703737, instanceHash: asde[0m	_defaultVHost_	camerahot_chat	703737	10546.0	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
2015-05-11	20:44:28	BRT	comment	server	INFO	200	-	e[32mApplication::startShutdown >> chatId: 380616e[0m	_defaultVHost_	camerahot_chat	703737	10546.001	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
2015-05-11	20:44:28	BRT	comment	server	INFO	200	-	e[32mRoomLogger::closeLoge[0m	_defaultVHost_	camerahot_chat	703737	10546.001	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
2015-05-11	20:44:28	BRT	-	-	-	-	-	-	_defaultVHost_	camerahot_chat	703737	10546.001	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-
2015-05-11	20:44:28	BRT	comment	server	ERROR	500	-	invoke(onDisconnect): java.lang.reflect.InvocationTargetException|at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)|at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)|at java.lang.reflect.Method.invoke(Method.java:483)|at com.wowza.wms.module.ModuleFunction.invoke(ModuleFunction.java:383)|at com.wowza.wms.module.ModuleFunctions.a(ModuleFunctions.java:670)|	_defaultVHost_	camerahot_chat	703737	10546.007	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-	-

```

Error Log:

```auto
WARN	server	comment	2015-05-11	20:43:45	-	-	-	-	-	10503.179	-	-	-	-	-	-	-	-	CupertinoPacketHandler.handleHolder[camerahot_chat/737355/stream_11_05_2015_737355_1431380435488]: Invalid video/audio codec combination for iPhone/iPod: video:H264 audio:SPEEX
WARN	server	comment	2015-05-11	20:43:45	-	-	-	-	-	10503.179	-	-	-	-	-	-	-	-	CupertinoPacketHandler.handleHolder[camerahot_chat/737355/stream_11_05_2015_737355_1431380435488]: Invalid audio codec for iPhone/iPod:SPEEX
-	-	-	2015-05-11	20:44:28	-	-	-	-	-	10546.001	-	-	-	-	-	-	-	-	-
ERROR	server	comment	2015-05-11	20:44:28	-	-	-	-	-	10546.007	-	-	-	-	-	-	-	-	invoke(onDisconnect): java.lang.reflect.InvocationTargetException|at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)|at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)|at java.lang.reflect.Method.invoke(Method.java:483)|at com.wowza.wms.module.ModuleFunction.invoke(ModuleFunction.java:383)|at com.wowza.wms.module.ModuleFunctions.a(ModuleFunctions.java:670)|

```

Has anyone seem something like this?

---

<div class="post-metadata">

**Author:** ![sal\_jefferson](https://avatars.discourse-cdn.com/v4/letter/s/6de8d8/32.png) [@sal\_jefferson](https://community.wowza.com/u/sal_jefferson)\
**Post date:** [May 13, 2015, 3:45pm UTC](https://community.wowza.com/t/strange-empty-message-on-error-log/44180/2 "2015-05-13T15:45:10Z")

</div>

Hello.

If you are building this in Eclipse, then edit your run or debug configuration in eclipse, and try adding the following to the VM Arguments on the Arguments tab.

-Dcom.wowza.wms.native.base=“win”

Or on Mac

-Dcom.wowza.wms.native.base=“osx”

Also, this kind of error indicates the compiled jar file is not in the lib/ folder of your Wowza Streaming Engine install, or possibly anything it may rely on to work correctly.

What I would do is strip down the module to a bare minimum and get that working then add back any code to see if/how/when it fails.

Regards,

Salvadore