# Input via Log4J SocketAppender fails due to charachter problems

**URL:** https://discuss.elastic.co/t/input-via-log4j-socketappender-fails-due-to-charachter-problems/201136
**Category:** Logstash
**Created:** [September 26, 2019, 4:46am UTC](https://discuss.elastic.co/t/input-via-log4j-socketappender-fails-due-to-charachter-problems/201136 "2019-09-26T04:46:29Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Dilan\_Sachintha](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dilan_sachintha/32/54894_2.png) [@Dilan\_Sachintha](https://discuss.elastic.co/u/Dilan_Sachintha)
#### Post date: [September 26, 2019, 4:46am UTC](https://discuss.elastic.co/t/input-via-log4j-socketappender-fails-due-to-charachter-problems/201136/1 "2019-09-26T04:46:29Z")

</div>

I'm using Log4J v2.x SocketAppender to send logs to logstash directly. The system was previously designed to send the logs via filebeat. Since I changed the setting, logstash now cannot read my inputs.

```
[2019-09-26T10:06:16,255][WARN][logstash.codecs.jsonlines] JSON parse error, original data now in message field {:error=>#<LogStash::Json::ParserError: Unexpected character (',' (code 44)): expected a valid value (number, String, array, object, 'true', 'false' or 'null')
"; line: 1, column: 2]>, :data=>",\"source\":\"/home/directfn/app/NTP/CloudSetup/jboss-eap-7.1/standalone/log/OMS_Analyzed.log\",\"type\":\"log\"}\r"}
[2019-09-26T10:06:16,256][WARN][logstash.codecs.jsonlines] JSON parse error, original data now in message field {:error=>#<LogStash::Json::ParserError: Illegal character ((CTRL-CHAR, code 31)): only regular white space (\r, \n, \t) is allowed between tokens
 at [Source: (String)"{"input_type":"log","message":163TXN-DFLT107CACHE_LOAD_FROM_DBOMS-TRADE127.0.0.1trueLOG_MESSAGE:CACHE LOAD FROM DBTXN_TIME:1569472482178DAO:com.dfn.oms.newgen.core.persistance.dao.SysParamDAOCACHE_KEY:SYMBOL_CLEAR_PERIOD"; line: 1, column: 32]>, :data=>"{\"input_type\":\"log\",\"message\":\u001F163\u001FTXN-DFLT\u001F107\u001FCACHE_LOAD_FROM_DB\u001FOMS-TRADE\u001F127.0.0.1\u001Ftrue\u001FLOG_MESSAGE:CACHE LOAD FROM DB\u0001TXN_TIME:1569472482178\u0001DAO:com.dfn.oms.newgen.core.persistance.dao.SysParamDAO\u0001CACHE_KEY:SYMBOL_CLEAR_PERIOD\u0001\u001F"}

```

I'm sending the logs in UTF-8 format.  
Here is the log4j configuration.

```
<Socket name="SocketRef" host="192.168.0.51" port="5055">
		<PatternLayout>
			<charset>"UTF-8"</charset>
			<pattern>{"input_type":"log","message":"%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p %c (%t) %msg","source":"/home/directfn/app/NTP/CloudSetup/jboss-eap-7.1/standalone/log/OMS_Analyzed.log","type":"log"}%n</pattern>
		</PatternLayout>
	</Socket>

```

The problem is with the **msg** since it contains charachters ▼O like this.

Can anyone give me a solution?

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 24, 2019, 4:46am UTC](https://discuss.elastic.co/t/input-via-log4j-socketappender-fails-due-to-charachter-problems/201136/2 "2019-10-24T04:46:41Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.