date:20191001

Re: [Dev] wso2 EI 6.4.0: "System may be unstable" error

2019-10-01 Thread Hasitha Hiranya

Hi,

Even if the system level open file count limit is unlimited, there is a
limit per process.
Please check if that is hit [1].

[1].
https://stackoverflow.com/questions/21752067/counting-open-files-per-process

Thanks


On Tue, Oct 1, 2019 at 4:01 PM Bernard Paris 
wrote:

>
> running 2 nodes wso2 EI 6.4.0  behind a load balancer (round robbin) for
> months now, suddenly yesterday one node was very very busy without any good
> reason..
> In the logs we found thousands and thousands  of this message :
>
>
> [2019-09-30 16:41:06,440] [-1] [] [PassThrough HTTPS-Listener I/O
> dispatcher Listener]  WARN
> {org.apache.synapse.transport.passthru.PassThroughHttpSSLListener} -
> System may be unstable: HTTPS ListeningIOReactor encountered a checked
> exception : Too many open files
> java.io.IOException: Too many open files
> at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
> at sun.nio.ch
> .ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:422)
> at sun.nio.ch
> .ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:250)
> at
> org.apache.http.impl.nio.reactor.DefaultListeningIOReactor.processEvent(DefaultListeningIOReactor.java:170)
> at
> org.apache.http.impl.nio.reactor.DefaultListeningIOReactor.processEvents(DefaultListeningIOReactor.java:153)
> at
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:349)
> at
> org.apache.synapse.transport.passthru.core.PassThroughListeningIOReactorManager$1.run(PassThroughListeningIOReactorManager.java:536)
> at java.lang.Thread.run(Thread.java:748)
>
> We needed to stop then restart the process.
>
> This is strange since on this linux machine we configured ulimit to
> "unlimited" and no particular intensive traffic was found at this moment.
>
> We now are afraid this can be come again, what could be the origin of this
> problem ? any idea to avoid it ?
>
> Thanks
> Bernard
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 
*Hasitha Abeykoon*
Associate Technical Lead; WSO2, Inc.; http://wso2.com
*cell:* *+94 719363063*
*blog: **abeykoon.blogspot.com* 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 Identity Server 5.9.0 RC2

2019-10-01 Thread Piraveena Paralogarajah

Hi all,


We are pleased to announce the second release candidate of WSO2 Identity
Server 5.9.0.



New Features

   -

   An improved, simpler configuration model
   -

   RESTful APIs for user self-services
   -

   Passwordless authentication with WebAuthn
   -

   Reusable script library for adaptive authentication
   -

   Cross-protocol single logout capability
   -

   Inbuilt support to view and revoke user sessions
   -

   Azure AD/Office365 multi-domain federation support



Fixes

This release includes the following issue fixes and improvements:

   -

   5.9.0-m1 
   -

   5.9.0-m2 
   -

   5.9.0-m3 
   -

   5.9.0-m4 
   -

   5.9.0-m5 
   -

   5.9.0-m6 
   -

   5.9.0-alpha 
   -

   5.9.0-beta 
   -

   5.9.0-GA 



Source and Distribution

The source and distribution

are available at https://github.com/wso2/product-is/releases/tag/v5.9.0-rc2


Please download the product, test it, and vote using the following
convention.

[+] Stable - go ahead and release

[-] Broken - do not release (explain why)

Thanks,

WSO2 Identity and Access Management Team

*Piraveena Paralogarajah*
Software Engineer | WSO2 Inc.
*(m)* +94776099594 | *(e)* pirave...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue in running as windows service in JDK 11

2019-10-01 Thread Senthalan Kanagalingam

Hi all,

After some analysis, I have found that yajsw 11.03 do not have the JDK 11
support and yajsw 12.14 supports JDK11.

With further analyse we found the cause why the service not working with
yajsw 12.14  and fixed [1]. With these changes, the WSO2 Identity server
5.9.0-rc1 pack as windows service worked with JDK 8 and JDK 11.

So we decided to continue with this.

[1] - https://github.com/wso2/carbon-kernel/pull/2312

Thanks,

On Wed, Sep 25, 2019 at 11:44 AM Senthalan Kanagalingam 
wrote:

> Hi all,
>
> When we are facing the following issue[1] when running WSO2 IS 5.9.0-alph3
> as a Windows service[2](with this[3] wrapper.conf) in JDK11 using yaw
> 11.03. Please note that running as a Windows service works fine with java 8
>
> C:\Users\Administrator\Downloads\yajsw-stable-11.03\yajsw-stable-11.03\bat>call
>  setenv.bat
> "java" -Xmx30m 
> -Djna_tmpdir="C:\Users\Administrator\Downloads\yajsw-stable-11.03\yajsw-stable-11.03\bat\/../tmp"
>  -jar 
> "C:\Users\Administrator\Downloads\yajsw-stable-11.03\yajsw-stable-11.03\bat\/../wrapper.jar"
>  -c 
> "C:\Users\Administrator\Downloads\yajsw-stable-11.03\yajsw-stable-11.03\bat\/../conf/wrapper.conf"
> YAJSW: yajsw-stable-11.03
> OS   : Windows Server 2016/10.0/amd64
> JVM  : Oracle Corporation/11.0.4
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> org.codehaus.groovy.reflection.CachedClass$3$1 
> (file:/C:/Users/Administrator/Downloads/yajsw-stable-11.03/yajsw-stable-11.03/./lib/core/groovy/groovy-all-1.8.6.jar)
>  to method java.lang.Object.finalize()
> WARNING: Please consider reporting this to the maintainers of 
> org.codehaus.groovy.reflection.CachedClass$3$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Sep 24, 2019 7:00:35 PM org.apache.commons.vfs2.VfsLog info
> INFO: Using "C:\Users\ADMINI~1\AppData\Local\Temp\2\vfs_cache" as temporary 
> files store.
> platform null
> platform null
> WARNING|wrapper|"WSO2 Carbon"|19-09-24 19:00:36|YAJSW: yajsw-stable-11.03
> WARNING|wrapper|"WSO2 Carbon"|19-09-24 19:00:36|OS   : Windows Server 
> 2016/10.0/amd64
> WARNING|wrapper|"WSO2 Carbon"|19-09-24 19:00:36|JVM  : Oracle 
> Corporation/11.0.4
> Using the autodetected NIO constraint level: 0
> INFO|wrapper|"WSO2 Carbon"|19-09-24 19:00:36|ahessian jmx service bound to 
> port 15002
> INFO|wrapper|"WSO2 Carbon"|19-09-24 19:00:36|spawned system tray icon process 
> with pid 3712
> INFO|wrapper|"WSO2 Carbon"|19-09-24 19:00:36|set state IDLE->STARTING
> INFO|wrapper|"WSO2 Carbon"|19-09-24 19:00:36|Controller State: UNKNOWN -> 
> WAITING
> INFO|wrapper|"WSO2 Carbon"|19-09-24 19:00:36|working dir 
> C:\senthalan\wso2is-5.9.0-alpha3\wso2is-5.9.0-alpha3
> INFO|wrapper|"WSO2 Carbon"|19-09-24 19:00:36|create script: 
> ../scripts/trayMessage.gv
> INFO|wrapper|"WSO2 Carbon"|19-09-24 19:00:37|found script 
> ../scripts/trayMessage.gv
> INFO|wrapper|"WSO2 Carbon"|19-09-24 19:00:37|started process with pid 3204
> INFO|wrapper|"WSO2 Carbon"|19-09-24 19:00:37|set state STARTING->RUNNING
> WARNING|wrapper|"WSO2 Carbon"|19-09-24 19:00:38|[id: 0x20772839, 
> /127.0.0.1:50746 => /127.0.0.1:15002] connected
> INFO|3204/0|"WSO2 Carbon"|19-09-24 19:00:38|Controller State: WAITING -> 
> PROCESS_KILLED
> INFO|wrapper|"WSO2 Carbon"|19-09-24 19:00:38|restart process due to default 
> exit code rule
> INFO|wrapper|"WSO2 Carbon"|19-09-24 19:00:38|restart internal RUNNING
> INFO|wrapper|"WSO2 Carbon"|19-09-24 19:00:38|set state RUNNING->RESTART
> INFO|wrapper|"WSO2 Carbon"|19-09-24 19:00:39|set state RESTART->RESTART_STOP
> INFO|wrapper|"WSO2 Carbon"|19-09-24 19:00:39|stopping process with 
> pid/timeout 3204 45000
> INFO|3204/0|"WSO2 Carbon"|19-09-24 19:00:39|Controller State: PROCESS_KILLED 
> -> USER_STOP
> INFO|wrapper|"WSO2 Carbon"|19-09-24 19:00:39|process exit code: 999
> INFO|wrapper|"WSO2 Carbon"|19-09-24 19:00:39|set state 
> RESTART_STOP->RESTART_WAIT
> INFO|wrapper|"WSO2 Carbon"|19-09-24 19:00:44|set state 
> RESTART_WAIT->RESTART_START
> INFO|3204/0|"WSO2 Carbon"|19-09-24 19:00:44|Controller State: USER_STOP -> 
> UNKNOWN
> INFO|wrapper|"WSO2 Carbon"|19-09-24 19:00:44|Controller State: UNKNOWN -> 
> WAITING
> INFO|wrapper|"WSO2 Carbon"|19-09-24 19:00:44|working dir 
> C:\senthalan\wso2is-5.9.0-alpha3\wso2is-5.9.0-alpha3
> INFO|wrapper|"WSO2 Carbon"|19-09-24 19:00:44|create script: 
> ../scripts/trayMessage.gv
> INFO|wrapper|"WSO2 Carbon"|19-09-24 19:00:44|found script 
> ../scripts/trayMessage.gv
> INFO|wrapper|"WSO2 Carbon"|19-09-24 19:00:44|started process with pid 7812
> INFO|wrapper|"WSO2 Carbon"|19-09-24 19:00:44|set state RESTART_START->RUNNING
> INFO|wrapper|"WSO2 Carbon"|19-09-24 19:00:46|Controller State: WAITING -> 
> PROCESS_KILLED
> INFO|wrapper|"WSO2 Carbon"|19-09-24 19:00:46|restart process due to default 
> exit code rule
> INFO|wrapper|"WSO2 Carbon"|19-09-24 19:00:46|

[Dev] wso2 EI 6.4.0: "System may be unstable" error

2019-10-01 Thread Bernard Paris



running 2 nodes wso2 EI 6.4.0  behind a load balancer (round robbin) for months 
now, suddenly yesterday one node was very very busy without any good reason.. 
In the logs we found thousands and thousands  of this message :


[2019-09-30 16:41:06,440] [-1] [] [PassThrough HTTPS-Listener I/O dispatcher 
Listener]  WARN 
{org.apache.synapse.transport.passthru.PassThroughHttpSSLListener} -  System 
may be unstable: HTTPS ListeningIOReactor encountered a checked exception : Too 
many open files
java.io.IOException: Too many open files
at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
at 
sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:422)
at 
sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:250)
at 
org.apache.http.impl.nio.reactor.DefaultListeningIOReactor.processEvent(DefaultListeningIOReactor.java:170)
at 
org.apache.http.impl.nio.reactor.DefaultListeningIOReactor.processEvents(DefaultListeningIOReactor.java:153)
at 
org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:349)
at 
org.apache.synapse.transport.passthru.core.PassThroughListeningIOReactorManager$1.run(PassThroughListeningIOReactorManager.java:536)
at java.lang.Thread.run(Thread.java:748)

We needed to stop then restart the process.

This is strange since on this linux machine we configured ulimit to "unlimited" 
and no particular intensive traffic was found at this moment.

We now are afraid this can be come again, what could be the origin of this 
problem ? any idea to avoid it ?

Thanks
Bernard
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] wso2 EI 6.4.0: "System may be unstable" error

[Dev] [VOTE] Release WSO2 Identity Server 5.9.0 RC2

Re: [Dev] Issue in running as windows service in JDK 11

[Dev] wso2 EI 6.4.0: "System may be unstable" error

4 matches

Site Navigation

Mail list logo

Footer information