[ 
https://issues.apache.org/jira/browse/LOG4J2-2577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thttps://issues.apache.org/jira/secure/CreateIssue!default.jspahomas Esseling 
updated LOG4J2-2577:
--------------------------------------------------------------------------------------------------
    Description: 
Hi,

i am the adminstrator of some WebSphere Liberty servers running on a z/OS 
mainframe. 
 One of our applications uses the log4j syslog appender to connect to a syslog 
servers via UDP. 

When log4j initialises, we we receive a security violation because log4j tries 
to use UDP broadcast. The system prohibts the broadcast and log4j does not 
initialize.

Please help, regards

Thomas

Here's the exception: '

 

{{{color:#ff0000}Syslogintq.xxx.xxx java.net.SocketException{color}: Å]}}{{     
         }}

{{at java.net.PlainDatagramSocketImpl.datagramSocketCreate(Native Method)}}{{   
            }}

{{at 
java.net.AbstractPlainDatagramSocketImpl.create(AbstractPlainDatagramSocketImpl.java:91)}}{{
               }}

{{at java.net.DatagramSocket.createImpl(DatagramSocket.java:348)}}{{            
   }}

{{at java.net.DatagramSocket.<init>(DatagramSocket.java:250)}}{{               
}}

{{at java.net.DatagramSocket.<init>(DatagramSocket.java:207)}}{{               
at 
org.apache.logging.log4j.core.net.DatagramOutputStream.<init>(DatagramOutputStream.java:72)}}{{
               }}

{{at 
org.apache.logging.log4j.core.net.DatagramSocketManager$DatagramSocketManagerFactory.createManager(DatagramSocketManager.java:120)}}{{
               at 
org.apache.logging.log4j.core.net.DatagramSocketManager$DatagramSocketManagerFactory.createManager(DatagramSocketManager.java:109}}

 

 This is the appdender definition:

{{}}{{<Syslog name="SYSLOG_TEST" host="syslogintq.xxx.xxx" port="514"}}{{       
         appName="aaa@zzz" protocol="UDP" includeMDC="true" mdcId="mdc" 
format="RFC5424" facility="SYSLOG"}}{{                mdcPrefix="mdc:"  
enterpriseNumber="18060" newLine="true" messageId="Audit" id="App" />}}

  was:
Hi,

i am the adminstrator of some WebSphere Liberty servers running on a z/OS 
mainframe. 
One of our applications uses the log4j syslog appender to connect to a syslog 
servers via UDP. 

When log4j initialises, we we receive a security violation because log4j tries 
to use UDP broadcast. The system prohibts the broadcast and log4j does not 
initialize. 

Please help, regards

Thomas


Here's the exception: '

{{{color:#FF0000}Syslogintq.xxx.xxx java.net.SocketException{color}: Å]}}{{     
          at java.net.PlainDatagramSocketImpl.datagramSocketCreate(Native 
Method)}}{{               at 
java.net.AbstractPlainDatagramSocketImpl.create(AbstractPlainDatagramSocketImpl.java:91)}}{{
               at 
java.net.DatagramSocket.createImpl(DatagramSocket.java:348)}}{{               
at java.net.DatagramSocket.<init>(DatagramSocket.java:250)}}{{               at 
java.net.DatagramSocket.<init>(DatagramSocket.java:207)}}{{               at 
org.apache.logging.log4j.core.net.DatagramOutputStream.<init>(DatagramOutputStream.java:72)}}{{
               at 
org.apache.logging.log4j.core.net.DatagramSocketManager$DatagramSocketManagerFactory.createManager(DatagramSocketManager.java:120)}}{{
               at 
org.apache.logging.log4j.core.net.DatagramSocketManager$DatagramSocketManagerFactory.createManager(DatagramSocketManager.java:109}}

 

 This is the appdender definition:


{{}}{{<Syslog name="SYSLOG_TEST" host="syslogintq.xxx.xxx" port="514"}}{{       
         appName="aaa@zzz" protocol="UDP" includeMDC="true" mdcId="mdc" 
format="RFC5424" facility="SYSLOG"}}{{                mdcPrefix="mdc:"  
enterpriseNumber="18060" newLine="true" messageId="Audit" id="App" />}}


> UDP Broadcast Issue with syslog appender
> ----------------------------------------
>
>                 Key: LOG4J2-2577
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2577
>             Project: Log4j 2
>          Issue Type: Question
>          Components: Appenders
>    Affects Versions: 2.11.2
>         Environment: OS: z/OS 2.2
> Websphere Liberty 18.0.0.3
> JDK 1.8
>            Reporter: 
> Thttps://issues.apache.org/jira/secure/CreateIssue!default.jspahomas Esseling
>            Priority: Minor
>
> Hi,
> i am the adminstrator of some WebSphere Liberty servers running on a z/OS 
> mainframe. 
>  One of our applications uses the log4j syslog appender to connect to a 
> syslog servers via UDP. 
> When log4j initialises, we we receive a security violation because log4j 
> tries to use UDP broadcast. The system prohibts the broadcast and log4j does 
> not initialize.
> Please help, regards
> Thomas
> Here's the exception: '
>  
> {{{color:#ff0000}Syslogintq.xxx.xxx java.net.SocketException{color}: Å]}}{{   
>            }}
> {{at java.net.PlainDatagramSocketImpl.datagramSocketCreate(Native Method)}}{{ 
>               }}
> {{at 
> java.net.AbstractPlainDatagramSocketImpl.create(AbstractPlainDatagramSocketImpl.java:91)}}{{
>                }}
> {{at java.net.DatagramSocket.createImpl(DatagramSocket.java:348)}}{{          
>      }}
> {{at java.net.DatagramSocket.<init>(DatagramSocket.java:250)}}{{              
>  }}
> {{at java.net.DatagramSocket.<init>(DatagramSocket.java:207)}}{{              
>  at 
> org.apache.logging.log4j.core.net.DatagramOutputStream.<init>(DatagramOutputStream.java:72)}}{{
>                }}
> {{at 
> org.apache.logging.log4j.core.net.DatagramSocketManager$DatagramSocketManagerFactory.createManager(DatagramSocketManager.java:120)}}{{
>                at 
> org.apache.logging.log4j.core.net.DatagramSocketManager$DatagramSocketManagerFactory.createManager(DatagramSocketManager.java:109}}
>  
>  This is the appdender definition:
> {{}}{{<Syslog name="SYSLOG_TEST" host="syslogintq.xxx.xxx" port="514"}}{{     
>            appName="aaa@zzz" protocol="UDP" includeMDC="true" mdcId="mdc" 
> format="RFC5424" facility="SYSLOG"}}{{                mdcPrefix="mdc:"  
> enterpriseNumber="18060" newLine="true" messageId="Audit" id="App" />}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to