May 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1127) Google App Engine support: Do not call new Thread() by allowing to plug in a custom ThreadFactory

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1127?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on DROOLS-1127: ------------------------------------------------- Xiong Zhi Ming <zxiong(a)redhat.com> changed the Status of [bug 1329093|https://bugzilla-qe-05.host.stage.eng.rdu2.redhat.com/show_bug.cg...] from NEW to ASSIGNED > Google App Engine support: Do not call new Thread() by allowing to plug in a custom ThreadFactory > ------------------------------------------------------------------------------------------------- > > Key: DROOLS-1127 > URL: https://issues.jboss.org/browse/DROOLS-1127 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > Fix For: 7.0.0.Beta1 > > > Any code that does `new Thread()` on GAE throws an exception, because you can't create new threads yourself. > Other future cloud platforms might have a similar restriction. It should be possible to plug in a custom way of creating threads. > *Proposal A)* Add a kieBase configuration property to change the ThreadFactory > {code} > drools.threadFactory = com.user.project.GoogleAppEngineThreadFactory > {code} > *Proposal B)* Add a kieBase configuration property to change the ExecutorServiceFactory > {code} > drools.executorServiceFactory = com.user.project.ExecutorServiceFactory > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1125) Google App Engine support: ClassLoader.getSystemClassLoader() throws exception

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1125?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on DROOLS-1125: ------------------------------------------------- Xiong Zhi Ming <zxiong(a)redhat.com> changed the Status of [bug 1329093|https://bugzilla-qe-05.host.stage.eng.rdu2.redhat.com/show_bug.cg...] from NEW to ASSIGNED > Google App Engine support: ClassLoader.getSystemClassLoader() throws exception > ------------------------------------------------------------------------------ > > Key: DROOLS-1125 > URL: https://issues.jboss.org/browse/DROOLS-1125 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > Fix For: 7.0.0.Beta1 > > > Class org.kie.internal.utils.ChainedProperties > Every call to get the System Class Loader > confClassLoader = ClassLoader.getSystemClassLoader(); (i.e. lines 133, 169) > raises an exception. > Todo: figure out which particular exception. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-395) Undertow HTTPS listener offers no cipher suite for DEFAULT enabled-cipher-suites

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-395?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse commented on ELY-395: -------------------------------------- Here is the SSL debug output: - {noformat} 17:59:26,482 INFO [stdout] (default I/O-10) Using SSLEngineImpl. 17:59:26,532 INFO [stdout] (default I/O-10) Allow unsafe renegotiation: false 17:59:26,532 INFO [stdout] (default I/O-10) Allow legacy hello messages: true 17:59:26,532 INFO [stdout] (default I/O-10) Is initial handshake: true 17:59:26,532 INFO [stdout] (default I/O-10) Is secure renegotiation: false 17:59:26,533 INFO [stdout] (default I/O-10) No available cipher suite for TLSv1 17:59:26,533 INFO [stdout] (default I/O-10) No available cipher suite for TLSv1.1 17:59:26,533 INFO [stdout] (default I/O-10) No available cipher suite for TLSv1.2 17:59:26,534 INFO [stdout] (default I/O-10) default I/O-10, fatal error: 80: problem unwrapping net record 17:59:26,534 INFO [stdout] (default I/O-10) javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate) 17:59:26,534 INFO [stdout] (default I/O-10) default I/O-10, SEND TLSv1.2 ALERT: fatal, description = internal_error 17:59:26,535 INFO [stdout] (default I/O-10) default I/O-10, WRITE: TLSv1.2 Alert, length = 2 17:59:26,535 INFO [stdout] (default I/O-10) default I/O-10, called closeInbound() 17:59:26,535 INFO [stdout] (default I/O-10) default I/O-10, fatal: engine already closed. Rethrowing javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack? 17:59:26,536 INFO [stdout] (default I/O-10) default I/O-10, called closeOutbound() 17:59:26,536 INFO [stdout] (default I/O-10) default I/O-10, closeOutboundInternal() 17:59:26,539 INFO [stdout] (default I/O-12) Using SSLEngineImpl. 17:59:26,547 INFO [stdout] (default I/O-12) Allow unsafe renegotiation: false 17:59:26,547 INFO [stdout] (default I/O-12) Allow legacy hello messages: true 17:59:26,547 INFO [stdout] (default I/O-12) Is initial handshake: true 17:59:26,547 INFO [stdout] (default I/O-12) Is secure renegotiation: false 17:59:26,547 INFO [stdout] (default I/O-12) No available cipher suite for TLSv1 17:59:26,548 INFO [stdout] (default I/O-12) No available cipher suite for TLSv1.1 17:59:26,548 INFO [stdout] (default I/O-12) No available cipher suite for TLSv1.2 17:59:26,548 INFO [stdout] (default I/O-12) default I/O-12, fatal error: 80: problem unwrapping net record 17:59:26,548 INFO [stdout] (default I/O-12) javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate) 17:59:26,549 INFO [stdout] (default I/O-12) default I/O-12, SEND TLSv1.2 ALERT: fatal, description = internal_error 17:59:26,549 INFO [stdout] (default I/O-12) default I/O-12, WRITE: TLSv1.2 Alert, length = 2 17:59:26,549 INFO [stdout] (default I/O-12) default I/O-12, called closeInbound() 17:59:26,549 INFO [stdout] (default I/O-12) default I/O-12, fatal: engine already closed. Rethrowing javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack? 17:59:26,549 INFO [stdout] (default I/O-12) default I/O-12, called closeOutbound() 17:59:26,549 INFO [stdout] (default I/O-12) default I/O-12, closeOutboundInternal() 17:59:26,551 INFO [stdout] (default I/O-14) Using SSLEngineImpl. 17:59:26,557 INFO [stdout] (default I/O-14) Allow unsafe renegotiation: false 17:59:26,558 INFO [stdout] (default I/O-14) Allow legacy hello messages: true 17:59:26,558 INFO [stdout] (default I/O-14) Is initial handshake: true 17:59:26,558 INFO [stdout] (default I/O-14) Is secure renegotiation: false 17:59:26,558 INFO [stdout] (default I/O-14) No available cipher suite for TLSv1 17:59:26,558 INFO [stdout] (default I/O-14) No available cipher suite for TLSv1.1 17:59:26,558 INFO [stdout] (default I/O-14) No available cipher suite for TLSv1.2 17:59:26,558 INFO [stdout] (default I/O-14) default I/O-14, fatal error: 80: problem unwrapping net record 17:59:26,559 INFO [stdout] (default I/O-14) javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate) 17:59:26,559 INFO [stdout] (default I/O-14) default I/O-14, SEND TLSv1.2 ALERT: fatal, description = internal_error 17:59:26,560 INFO [stdout] (default I/O-14) default I/O-14, WRITE: TLSv1.2 Alert, length = 2 17:59:26,560 INFO [stdout] (default I/O-14) default I/O-14, called closeInbound() 17:59:26,560 INFO [stdout] (default I/O-14) default I/O-14, fatal: engine already closed. Rethrowing javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack? 17:59:26,560 INFO [stdout] (default I/O-14) default I/O-14, called closeOutbound() 17:59:26,560 INFO [stdout] (default I/O-14) default I/O-14, closeOutboundInternal() {noformat} > Undertow HTTPS listener offers no cipher suite for DEFAULT enabled-cipher-suites > -------------------------------------------------------------------------------- > > Key: ELY-395 > URL: https://issues.jboss.org/browse/ELY-395 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Affects Versions: 1.0.2.Final > Reporter: Ondrej Kotek > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta6 > > > No cipher suites are available for handshake with HTTPS Undertow listener. > According to OpenSSL documentation [1], cipher suites corresponding with ALL:!COMPLEMENTOFDEFAULT:!eNULL cipher string should be available for handshake. > According to Elytron documentation [2], cipher suites corresponding with ALL:!aNULL:!eNULL cipher string should be available for handshake. > [1] https://www.openssl.org/docs/manmaster/apps/ciphers.html#CIPHER-STRINGS > [2] http://wildfly-security.github.io/wildfly-elytron/org/wildfly/security/ss... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2040) Seeing a OOM in JGroup 3.4

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2040?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2040: -------------------------------- http://www.jgroups.org/manual/index.html#TCPPING_Prot > Seeing a OOM in JGroup 3.4 > -------------------------- > > Key: JGRP-2040 > URL: https://issues.jboss.org/browse/JGRP-2040 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4 > Environment: Linux Operating System > Reporter: Kshitiz Saxena > Assignee: Bela Ban > > We are seeing an OOM in our application where thread dump points to JGroup. > We see the below in thread dumps, > 3XEHSTTYPE 07:33:24:346241000 GMT j9vm.294 - >setCurrentException index=11 constructorIndex=0 detailMessage=0000000000F61678 > 3XEHSTTYPE 07:33:24:346183000 GMT j9mm.126 - at 0000000050F8CD60 java/lang/Thread.run()V, jit 00007FCF323EA580, pc 00007FCF489E0A36 > 3XEHSTTYPE 07:33:24:346179000 GMT j9mm.126 - at 0000000053644748 *org/jgroups/blocks/TCPConnectionMap$TCPConnection$Receiver.run()*V, jit 0000000000000000, pc 00007FCF3354D334 > 3XEHSTTYPE 07:33:24:346175000 GMT j9mm.101 - J9AllocateIndexableObject() returning NULL! *1650814064 bytes* requested for object of class 0000000050F79700 from memory space 'Generational' id=00007FCF440427C0 > In the thread dump we also see > WARNING : OutOfMemoryError possibly caused by 1650814064 bytes requested for object of class 0000000050F79700 from memory space 'Generational' id=00007FCF440427C0 > Java Heap Information > -Xmx (Maximum Java heap size) : 1280m > -Xms (Initial Java heap size) : 640m > -Xss (Maximum stack size for Java threads) : 256k > Total Java heap size: 1.25 GB > Used Java heap size: 174.27 MB > Free Java heap size: 1.08 GB -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6368) Upgrade CXF from 3.1.4 to 3.1.6

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-6368?page=com.atlassian.jira.plugin.... ] Alessio Soldano reopened WFLY-6368: ----------------------------------- Assignee: Alessio Soldano (was: Jason Greene) > Upgrade CXF from 3.1.4 to 3.1.6 > ------------------------------- > > Key: WFLY-6368 > URL: https://issues.jboss.org/browse/WFLY-6368 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Bartosz Baranowski > Assignee: Alessio Soldano > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1127) Google App Engine support: Do not call new Thread() by allowing to plug in a custom ThreadFactory

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1127?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on DROOLS-1127: ------------------------------------------------- Xiong Zhi Ming <zxiong(a)redhat.com> changed the Status of [bug 1329093|https://bugzilla-qe-05.host.stage.eng.rdu2.redhat.com/show_bug.cg...] from ON_QA to NEW > Google App Engine support: Do not call new Thread() by allowing to plug in a custom ThreadFactory > ------------------------------------------------------------------------------------------------- > > Key: DROOLS-1127 > URL: https://issues.jboss.org/browse/DROOLS-1127 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > Fix For: 7.0.0.Beta1 > > > Any code that does `new Thread()` on GAE throws an exception, because you can't create new threads yourself. > Other future cloud platforms might have a similar restriction. It should be possible to plug in a custom way of creating threads. > *Proposal A)* Add a kieBase configuration property to change the ThreadFactory > {code} > drools.threadFactory = com.user.project.GoogleAppEngineThreadFactory > {code} > *Proposal B)* Add a kieBase configuration property to change the ExecutorServiceFactory > {code} > drools.executorServiceFactory = com.user.project.ExecutorServiceFactory > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1125) Google App Engine support: ClassLoader.getSystemClassLoader() throws exception

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1125?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on DROOLS-1125: ------------------------------------------------- Xiong Zhi Ming <zxiong(a)redhat.com> changed the Status of [bug 1329093|https://bugzilla-qe-05.host.stage.eng.rdu2.redhat.com/show_bug.cg...] from ON_QA to NEW > Google App Engine support: ClassLoader.getSystemClassLoader() throws exception > ------------------------------------------------------------------------------ > > Key: DROOLS-1125 > URL: https://issues.jboss.org/browse/DROOLS-1125 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > Fix For: 7.0.0.Beta1 > > > Class org.kie.internal.utils.ChainedProperties > Every call to get the System Class Loader > confClassLoader = ClassLoader.getSystemClassLoader(); (i.e. lines 133, 169) > raises an exception. > Todo: figure out which particular exception. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6368) Upgrade CXF from 3.1.4 to 3.1.6

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFLY-6368?page=com.atlassian.jira.plugin.... ] Chao Wang commented on WFLY-6368: --------------------------------- why this was rejected ? > Upgrade CXF from 3.1.4 to 3.1.6 > ------------------------------- > > Key: WFLY-6368 > URL: https://issues.jboss.org/browse/WFLY-6368 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Bartosz Baranowski > Assignee: Jason Greene > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6655) When creating JMS bridge management API should pass bridge name to JMS broker

by Tom Ross (JIRA)

Tom Ross created WFLY-6655: ------------------------------ Summary: When creating JMS bridge management API should pass bridge name to JMS broker Key: WFLY-6655 URL: https://issues.jboss.org/browse/WFLY-6655 Project: WildFly Issue Type: Bug Components: JMS Environment: JBoss EAP 7.0 Reporter: Tom Ross Assignee: Jeff Mesnil In situations where there are multiple JMS bridges being created it woudl help if bridge name is logged in the server name. This helps with recognising which JMS bridge is having problems. For this to work the JBoss messaging API layer has to pass bridge name to the JMS broker. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1127) Google App Engine support: Do not call new Thread() by allowing to plug in a custom ThreadFactory

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1127?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on DROOLS-1127: ------------------------------------------------- Xiong Zhi Ming <zxiong(a)redhat.com> changed the Status of [bug 1329093|https://bugzilla-qe-05.host.stage.eng.rdu2.redhat.com/show_bug.cg...] from MODIFIED to ON_QA > Google App Engine support: Do not call new Thread() by allowing to plug in a custom ThreadFactory > ------------------------------------------------------------------------------------------------- > > Key: DROOLS-1127 > URL: https://issues.jboss.org/browse/DROOLS-1127 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > Fix For: 7.0.0.Beta1 > > > Any code that does `new Thread()` on GAE throws an exception, because you can't create new threads yourself. > Other future cloud platforms might have a similar restriction. It should be possible to plug in a custom way of creating threads. > *Proposal A)* Add a kieBase configuration property to change the ThreadFactory > {code} > drools.threadFactory = com.user.project.GoogleAppEngineThreadFactory > {code} > *Proposal B)* Add a kieBase configuration property to change the ExecutorServiceFactory > {code} > drools.executorServiceFactory = com.user.project.ExecutorServiceFactory > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2016