June 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3436) Synch webservices subsystem with master (upgrade to JBossWS 4.3.0.Final)

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-3436?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated WFLY-3436: ---------------------------------- Summary: Synch webservices subsystem with master (upgrade to JBossWS 4.3.0.Final) (was: Upgrade to JBossWS 4.3.0.Final) > Synch webservices subsystem with master (upgrade to JBossWS 4.3.0.Final) > ------------------------------------------------------------------------ > > Key: WFLY-3436 > URL: https://issues.jboss.org/browse/WFLY-3436 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web Services > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: 8.2.0.CR1 > > > This includes upgrade to JBossWS 4.3 series and dependent changes that are currently on WFLY master only. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3436) Upgrade to JBossWS 4.3.0.Final

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-3436?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated WFLY-3436: ---------------------------------- Issue Type: Task (was: Component Upgrade) > Upgrade to JBossWS 4.3.0.Final > ------------------------------ > > Key: WFLY-3436 > URL: https://issues.jboss.org/browse/WFLY-3436 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web Services > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: 8.2.0.CR1 > > > This includes upgrade to JBossWS 4.3 series and dependent changes that are currently on WFLY master only. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3457) Nginx + Wildfly 8.1 + Varnish

by Thiago Hernandes (JIRA)

[ https://issues.jboss.org/browse/WFLY-3457?page=com.atlassian.jira.plugin.... ] Thiago Hernandes commented on WFLY-3457: ---------------------------------------- Please, pass me link FORUMs. Thanks > Nginx + Wildfly 8.1 + Varnish > ----------------------------- > > Key: WFLY-3457 > URL: https://issues.jboss.org/browse/WFLY-3457 > Project: WildFly > Issue Type: Support Request > Security Level: Public(Everyone can see) > Reporter: Thiago Hernandes > Assignee: Jason Greene > Labels: nginx, perfomrance, varnish > > Performance it´s more important in development web applications. > I´ve tested Python + Nginx + Tornado Web Server. It´s ok and worked. > is there any sugestion to configurate Nginx + Wildfly + Varnish??? > It could be in documentation of Wildfly with some examples or tutorials. > Is there somebody can be indicate or show any example? > I think, it´s one the best way to power of deploy applications Java with tecnologies i sad before. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3430) Recurring Timers are called concurrently

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-3430?page=com.atlassian.jira.plugin.... ] Stuart Douglas updated WFLY-3430: --------------------------------- Assignee: Stuart Douglas (was: Jason Greene) Component/s: EJB > Recurring Timers are called concurrently > ---------------------------------------- > > Key: WFLY-3430 > URL: https://issues.jboss.org/browse/WFLY-3430 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Affects Versions: 8.1.0.Final > Reporter: Carlos Barragan > Assignee: Stuart Douglas > Labels: timer > > According to https://docs.jboss.org/author/display/WFLY8/EJB+3+Reference+Guide recurring timers should not be executed concurrently. > That is not the case. I don't think the current behavior is actually expected. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3387) myfaces support : Handling PostConstruct annotations - wrong order

by hamid aghazzaf (JIRA)

[ https://issues.jboss.org/browse/WFLY-3387?page=com.atlassian.jira.plugin.... ] hamid aghazzaf commented on WFLY-3387: -------------------------------------- we are using the version 8.0.0.Final, thank u in advance for alerting me as soon as the JSF installer containing the fix is attached. > myfaces support : Handling PostConstruct annotations - wrong order > ------------------------------------------------------------------- > > Key: WFLY-3387 > URL: https://issues.jboss.org/browse/WFLY-3387 > Project: WildFly > Issue Type: Feature Request > Components: JSF > Affects Versions: 8.0.0.Final > Reporter: hamid aghazzaf > Assignee: Farah Juma > Attachments: JavaServerFaces.rar, JavaServerFaces.rar > > > The specification states that managed bean methods annotated with @PostConstruct have to be called after the object is initialized and after dependency injection is performed. However, MyFaces calls those methods after the bean instance is created but before dependency injection is performed. > This issue was resolved for tomcat7 server (https://issues.apache.org/jira/browse/MYFACES-1761). But remain with WildFly 8.0.Final . > Bellow the list of third party artifacts used with their versions : > activation-1.1.jar joda-time-2.3.jar velocity-1.6.2.jar > aopalliance-1.0.jar jrobin-1.5.9.jar xml-apis-1.0.b2.jar > aspectjrt-1.6.12.jar jsr305-1.3.9.jar xmlbeans-2.3.0.jar > aspectjtools-1.6.2.jar jstl-1.2.jar > aspectjweaver-1.6.11.jar junit-3.8.1.jar > atmosphere-runtime-2.0.1.jar log4j-1.2.12.jar > avalon-framework-4.1.3.jar logback-classic-0.9.30.jar > bcmail-jdk14-1.38.jar logback-core-0.9.30.jar > bcmail-jdk14-138.jar logkit-1.0.1.jar > bcprov-jdk14-1.38.jar mail-1.4.jar > bcprov-jdk14-138.jar myfaces-api-2.1.12.jar > bctsp-jdk14-1.38.jar myfaces-impl-2.1.12.jar > bsh-2.0b4.jar oro-2.0.8.jar > castor-1.2.jar poi-3.7.jar > cglib-3.0.jar poi-ooxml-3.7.jar > commons-beanutils-1.8.2.jar poi-ooxml-schemas-3.7.jar > commons-codec-1.3.jar primefaces-4.0.jar > commons-collections-3.2.jar primefaces-extensions-0.7.1.jar > commons-dbcp-1.2.2.jar servlet-api-2.3.jar > commons-digester-1.8.jar slf4j-api-1.6.2.jar > commons-fileupload-1.3.1.jar slf4j-log4j12-1.6.1.jar > commons-io-2.4.jar smoothness-1.0.10.jar > commons-lang-2.2.jar snakeyaml-1.6.jar > commons-lang3-3.1.jar spring-aop-3.1.0.RELEASE.jar > commons-logging-1.1.jar spring-asm-3.1.0.RELEASE.jar > commons-pool-1.3.jar spring-aspects-3.1.0.RELEASE.jar > dom4j-1.6.1.jar spring-beans-3.1.0.RELEASE.jar > geronimo-stax-api_1.0_spec-1.0.jar spring-binding-2.3.2.RELEASE.jar > groovy-all-2.0.1.jar spring-context-3.1.0.RELEASE.jar > gsfar-base-0.0.8-SNAPSHOT.jar spring-context-support-3.1.0.RELEASE.jar > gsfar-core-0.0.8-SNAPSHOT.jar spring-core-3.1.0.RELEASE.jar > gsfar-domain-0.0.8-SNAPSHOT.jar spring-data-commons-1.5.2.RELEASE.jar > gson-2.2.2.jar spring-data-commons-core-1.4.0.RELEASE.jar > guava-12.0.jar spring-data-envers-0.1.0.RELEASE.jar > hibernate-commons-annotations-4.0.1.Final.jar spring-data-jpa-1.3.4.RELEASE.jar > hibernate-core-4.1.7.Final.jar spring-expression-3.2.1.RELEASE.jar > hibernate-entitymanager-4.1.7.Final.jar spring-faces-2.3.2.RELEASE.jar > hibernate-envers-4.1.7.Final.jar spring-integration-core-2.2.2.RELEASE.jar > hibernate-jpa-2.0-api-1.0.1.Final.jar spring-integration-jdbc-2.2.2.RELEASE.jar > hsqldb-1.8.0.7.jar spring-jdbc-3.1.0.RELEASE.jar > itext-2.1.7.jar spring-js-2.3.2.RELEASE.jar > jackson-annotations-2.1.4.jar spring-js-resources-2.3.2.RELEASE.jar > jackson-core-2.1.4.jar spring-orm-3.1.0.RELEASE.jar > jackson-databind-2.1.4.jar spring-retry-1.0.2.RELEASE.jar > jasperreports-5.5.1.jar spring-security-config-3.1.4.RELEASE.jar > javamelody-core-1.49.0.jar spring-security-core-3.1.4.RELEASE.jar > javassist-3.15.0-GA.jar spring-security-web-3.1.4.RELEASE.jar > jboss-logging-3.1.0.GA.jar spring-test-3.1.0.RELEASE.jar > jboss-transaction-api_1.1_spec-1.0.0.Final.jar spring-tx-3.1.0.RELEASE.jar > jcl-over-slf4j-1.7.1.jar spring-web-3.1.0.RELEASE.jar > jcommander-1.12.jar spring-webflow-2.3.2.RELEASE.jar > jcommon-1.0.15.jar spring-webmvc-3.2.1.RELEASE.jar > jdtcore-3.1.0.jar stax-api-1.0.1.jar > jfreechart-1.0.12.jar testng-6.4.jar > I use spring profiles rather than maven profiles, this way, the same build (war file) is deploy-able in tomcat7 server as well as in Wildfly-8.0.0.Final. > I have toggled two types of breakpoints in one of my managed bean : > The first type is for the initialization method ( annotated with @PostConstruct ) > The second type is for setters of all properties aware of injection ( annotated with @ManagedProperty("# {xxx} > ") ). > When deploying to Tomcat7, every thing is well, all injections methods are invoked before the initialization method is called. > But, when running under Wildfly-8.0.0.Final, the initialization method is called before, and this causes NullPointerException for properties not yet injected. This behavior is the same regardless the deployment is done from the administration console or from my eclipse workbench. > We don’t have a lot of choices regarding the version of myfaces to use, as the only installer provided for adding support of myfaces to wildFly contains the version 2.1.12. And it's not a problem for continue with this version of myfaces. The installer is down-loadable from nexus : https://repository.jboss.org/nexus/index.html#nexus-search;gav~org.wildfl... > Thanks a lot in advance for your response. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3439) Websockets not working

by Veli Cris (JIRA)

[ https://issues.jboss.org/browse/WFLY-3439?page=com.atlassian.jira.plugin.... ] Veli Cris commented on WFLY-3439: --------------------------------- Not working deployed as .war file. All messages in Console seems to be OK, no errors but I cannot connect to WebSocket. In 8.0.0 Final is working without any issue. import javax.websocket.OnMessage; import javax.websocket.Session; import javax.websocket.server.ServerEndpoint; @ServerEndpoint("/shout") public class ShoutServerEndpoint { @OnMessage public void shout(String text, Session client) { client.getAsyncRemote().sendText(text.toUpperCase()); } } > Websockets not working > ---------------------- > > Key: WFLY-3439 > URL: https://issues.jboss.org/browse/WFLY-3439 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Sockets > Affects Versions: 8.1.0.Final > Reporter: Veli Cris > Assignee: Stuart Douglas > > Hi, > I deployed a .war file containing a single endpoint definition (Websocket). I can see following lines in console but nothing happens when trying to open connection from a websocket client. Same .war deployed in WildFly 8.0.0 is working. Please investigate! > The configuration is standalone. > [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017519: Undertow HTTP listener default listening on /0.0.0.0:8080 > [io.undertow.websockets.jsr] (MSC service thread 1-4) UT026003: Adding annotated server endpoint ... > [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017534: Registered web context: ... > [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "web.war" (runtime-name : "web.war") -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3459) Test

by Kabir Khan (JIRA)

Kabir Khan created WFLY-3459: -------------------------------- Summary: Test Key: WFLY-3459 URL: https://issues.jboss.org/browse/WFLY-3459 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kabir Khan Assignee: Jason Greene -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3386) Nullpointer exception on AbstractSessionBeanStore.getLockStore from within Activiti CDI

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/WFLY-3386?page=com.atlassian.jira.plugin.... ] Martin Kouba commented on WFLY-3386: ------------------------------------ So I looked at the Activiti code briefly. To sum it up: {{DefaultContextAssociationManager}} is looking for the appropriate {{ScopedAssociation}}. The "broadest" active context it gets is conversation, which is correct (see my comment about CDI 1.1 above). After that a {{ConversationScopedAssociation}} client proxy method is invoked, the conversation context attempts to retrieve the contextual instance and there is no current {{HttpSession}} and we're not able to create a new one. This should work provided it happens within a single HTTP request, no async processing or thread manipulation. > Nullpointer exception on AbstractSessionBeanStore.getLockStore from within Activiti CDI > --------------------------------------------------------------------------------------- > > Key: WFLY-3386 > URL: https://issues.jboss.org/browse/WFLY-3386 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CDI / Weld > Affects Versions: 8.0.0.Final > Environment: CentOS, Mac (Mountain Lion). > Reporter: Andries Ehlers > Assignee: Martin Kouba > > Background: > The actual exception seems to be very close the one in issue: WFLY-3001 but we are not using JSF at all, but Activiti CDI. > Not sure if this is a Wildfly or Activiti issue - it could very well be that there is a bug in Activiti with how it manages the CDI scopes. Unfortunately we're at a loss and seeing that the nullpointer is thrown from within a weld AbstractSessionBeanStore, I decided to post it here. Please advise. > Error: > We use Activiti CDI within Wildfly 8.0.0.Final. We randomly encounter an issue (sometimes immediately after a redeploy, other times after a few hours of inactivity on the server) the following issue. When Activiti attempts to retrieve the ContextBeanInstance from its ConversationScopedAssociationProxy, a NullPointer exception is thrown while attempting to retrieve the lock store within Weld (see below). > ----------------------------- > 2014-05-21 10:05:34,430 INFO [stdout] (default task-12) java.lang.NullPointerException: null > 2014-05-21 10:05:34,430 INFO [stdout] (default task-12) at org.jboss.weld.context.beanstore.http.AbstractSessionBeanStore.getLockStore(AbstractSessionBeanStore.java:113) ~[weld-core-impl-2.1.2.Final.jar!/:2014-01-09 09:23] > 2014-05-21 10:05:34,430 INFO [stdout] (default task-12) at org.jboss.weld.context.beanstore.AttributeBeanStore.lock(AttributeBeanStore.java:210) ~[weld-core-impl-2.1.2.Final.jar!/:2014-01-09 09:23] > 2014-05-21 10:05:34,430 INFO [stdout] (default task-12) at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:90) ~[weld-core-impl-2.1.2.Final.jar!/:2014-01-09 09:23] > 2014-05-21 10:05:34,431 INFO [stdout] (default task-12) at org.jboss.weld.context.PassivatingContextWrapper$AbstractPassivatingContextWrapper.get(PassivatingContextWrapper.java:76) ~[weld-core-impl-2.1.2.Final.jar!/:2014-01-09 09:23] > 2014-05-21 10:05:34,431 INFO [stdout] (default task-12) at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:98) ~[weld-core-impl-2.1.2.Final.jar!/:2014-01-09 09:23] > 2014-05-21 10:05:34,431 INFO [stdout] (default task-12) at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:78) ~[weld-core-impl-2.1.2.Final.jar!/:2014-01-09 09:23] > 2014-05-21 10:05:34,431 INFO [stdout] (default task-12) at org.activiti.cdi.impl.context.DefaultContextAssociationManager$ConversationScopedAssociation$Proxy$_$$_WeldClientProxy.getTask(Unknown Source) ~[activiti-cdi-5.15.jar:na] > 2014-05-21 10:05:34,431 INFO [stdout] (default task-12) at org.activiti.cdi.impl.context.DefaultContextAssociationManager.getTask(DefaultContextAssociationManager.java:237) ~[activiti-cdi-5.15.jar:na] > 2014-05-21 10:05:34,432 INFO [stdout] (default task-12) at org.activiti.cdi.BusinessProcess.startTask(BusinessProcess.java:332) ~[activiti-cdi-5.15.jar:na] -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3458) RESTEasy: Remote attacker can read server's files - XML eXternal Entity (XXE) security flaw

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-3458: ------------------------------------ Summary: RESTEasy: Remote attacker can read server's files - XML eXternal Entity (XXE) security flaw Key: WFLY-3458 URL: https://issues.jboss.org/browse/WFLY-3458 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: REST Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3347) the recovery manager service is starting before the CMRResourceAdd is being processed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3347?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3347: ----------------------------------------------- Ondrej Chaloupka <ochaloup(a)redhat.com> changed the Status of [bug 1091308|https://bugzilla.redhat.com/show_bug.cgi?id=1091308] from ON_QA to ASSIGNED > the recovery manager service is starting before the CMRResourceAdd is being processed > ------------------------------------------------------------------------------------- > > Key: WFLY-3347 > URL: https://issues.jboss.org/browse/WFLY-3347 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transactions > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Fix For: 9.0.0.Alpha1 > > > we need to set com.arjuna.ats.jta.common.JTAEnvironmentBean::setCommitMarkableResourceJNDINames before the recovery manager service is started -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 12 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2014