February 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6099) JPA's persistence.xml is deployed before datasources are created through application.xml

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-6099?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-6099: -------------------------------------- is the javax.sql.DataSource class packaged somewhere in your deployment? > JPA's persistence.xml is deployed before datasources are created through application.xml > ---------------------------------------------------------------------------------------- > > Key: WFLY-6099 > URL: https://issues.jboss.org/browse/WFLY-6099 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.Final > Reporter: Renann Prado > Assignee: Jason Greene > Attachments: server_with_mysql_driver.log > > > Please refer to discussion > https://developer.jboss.org/thread/267371 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-509) Correctly deal with deployment service restart

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-509?page=com.atlassian.jira.plugin... ] Stuart Douglas resolved WFCORE-509. ----------------------------------- Resolution: Rejected > Correctly deal with deployment service restart > ---------------------------------------------- > > Key: WFCORE-509 > URL: https://issues.jboss.org/browse/WFCORE-509 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > At the moment a lot of deployment services are not restartable, as they rely on transient state. The DeploymentUnitService has a device that will restart the whole deployment if it detects a restart, we should investigate adding something similar to other deployment services. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5911) Update fasterxml.jackson.* from 2.5.4 to 2.6.4.

by Juergen Zimmermann (JIRA)

[ https://issues.jboss.org/browse/WFLY-5911?page=com.atlassian.jira.plugin.... ] Juergen Zimmermann commented on WFLY-5911: ------------------------------------------ Upgrading to 2.6.4/2.6.5 (and not to 2.7.x) should be preferred: * https://github.com/FasterXML/jackson-databind/issues/1079 * https://github.com/FasterXML/jackson-databind/issues/1087 * https://jira.spring.io/browse/SPR-13853 > Update fasterxml.jackson.* from 2.5.4 to 2.6.4. > ----------------------------------------------- > > Key: WFLY-5911 > URL: https://issues.jboss.org/browse/WFLY-5911 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Affects Versions: 10.0.0.CR5 > Reporter: Frank Langelage > Assignee: Stuart Douglas > Fix For: 10.1.0.Final > > > Update com.fasterxml.jackson to latest version. > Precondition: update of resteasy to latest version. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3805) JGroupsBroadcastGroupConfiguration Serialization Problem

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-3805?page=com.atlassian.jira.plugin.... ] Yong Hao Gao commented on WFLY-3805: ------------------------------------ As far as I know, it need be fixed on 2.3.x (but my PR got rejected, so it's still pending). I don't think there is a requirement for 2.4.x. > JGroupsBroadcastGroupConfiguration Serialization Problem > -------------------------------------------------------- > > Key: WFLY-3805 > URL: https://issues.jboss.org/browse/WFLY-3805 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 8.1.0.Final > Reporter: Yong Hao Gao > Assignee: Yong Hao Gao > Fix For: 10.1.0.Final > > > When configuring JMS connection factories using jgroups discovery group, the client will get serialization exceptions because we pass a JChannel which is not serializable. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3805) JGroupsBroadcastGroupConfiguration Serialization Problem

by Clebert Suconic (JIRA)

[ https://issues.jboss.org/browse/WFLY-3805?page=com.atlassian.jira.plugin.... ] Clebert Suconic commented on WFLY-3805: --------------------------------------- I remember we fixed it on 2.3.x. There is currently no plans on 2.4.x. Is that required? > JGroupsBroadcastGroupConfiguration Serialization Problem > -------------------------------------------------------- > > Key: WFLY-3805 > URL: https://issues.jboss.org/browse/WFLY-3805 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 8.1.0.Final > Reporter: Yong Hao Gao > Assignee: Yong Hao Gao > Fix For: 10.1.0.Final > > > When configuring JMS connection factories using jgroups discovery group, the client will get serialization exceptions because we pass a JChannel which is not serializable. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6099) JPA's persistence.xml is deployed before datasources are created through application.xml

by Renann Prado (JIRA)

[ https://issues.jboss.org/browse/WFLY-6099?page=com.atlassian.jira.plugin.... ] Renann Prado commented on WFLY-6099: ------------------------------------ Cool. Thanks. I've just done what you said and now at least the error changed. Basically I'm getting this exception, which was also happening with MariaDB's driver, so I changed to MySQL's and still get the below exception. {code} Caused by: java.lang.ClassCastException: com.mysql.jdbc.Driver cannot be cast to javax.sql.DataSource at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getDataSource(LocalManagedConnectionFactory.java:634) ... 39 more {code} Full log has been attached. > JPA's persistence.xml is deployed before datasources are created through application.xml > ---------------------------------------------------------------------------------------- > > Key: WFLY-6099 > URL: https://issues.jboss.org/browse/WFLY-6099 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.Final > Reporter: Renann Prado > Assignee: Jason Greene > Attachments: server_with_mysql_driver.log > > > Please refer to discussion > https://developer.jboss.org/thread/267371 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6099) JPA's persistence.xml is deployed before datasources are created through application.xml

by Renann Prado (JIRA)

[ https://issues.jboss.org/browse/WFLY-6099?page=com.atlassian.jira.plugin.... ] Renann Prado updated WFLY-6099: ------------------------------- Attachment: server_with_mysql_driver.log > JPA's persistence.xml is deployed before datasources are created through application.xml > ---------------------------------------------------------------------------------------- > > Key: WFLY-6099 > URL: https://issues.jboss.org/browse/WFLY-6099 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.Final > Reporter: Renann Prado > Assignee: Jason Greene > Attachments: server_with_mysql_driver.log > > > Please refer to discussion > https://developer.jboss.org/thread/267371 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3805) JGroupsBroadcastGroupConfiguration Serialization Problem

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-3805?page=com.atlassian.jira.plugin.... ] Yong Hao Gao commented on WFLY-3805: ------------------------------------ Yeah, agreed. > JGroupsBroadcastGroupConfiguration Serialization Problem > -------------------------------------------------------- > > Key: WFLY-3805 > URL: https://issues.jboss.org/browse/WFLY-3805 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 8.1.0.Final > Reporter: Yong Hao Gao > Assignee: Yong Hao Gao > Fix For: 10.1.0.Final > > > When configuring JMS connection factories using jgroups discovery group, the client will get serialization exceptions because we pass a JChannel which is not serializable. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3805) JGroupsBroadcastGroupConfiguration Serialization Problem

by Clebert Suconic (JIRA)

[ https://issues.jboss.org/browse/WFLY-3805?page=com.atlassian.jira.plugin.... ] Clebert Suconic commented on WFLY-3805: --------------------------------------- Se can't back port the uri fix. That breaks compatibility. > JGroupsBroadcastGroupConfiguration Serialization Problem > -------------------------------------------------------- > > Key: WFLY-3805 > URL: https://issues.jboss.org/browse/WFLY-3805 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 8.1.0.Final > Reporter: Yong Hao Gao > Assignee: Yong Hao Gao > Fix For: 10.1.0.Final > > > When configuring JMS connection factories using jgroups discovery group, the client will get serialization exceptions because we pass a JChannel which is not serializable. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3805) JGroupsBroadcastGroupConfiguration Serialization Problem

by Yong Hao Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-3805?page=com.atlassian.jira.plugin.... ] Yong Hao Gao commented on WFLY-3805: ------------------------------------ Hi Clebert, This issue was from wildfly 7. With Artemis the issue should be gone because Artemis use URL form of serialization while HornetQ's not. I had a PR for HornetQ fix but that's before Artemis came out. It's been rejected. So I think if we need fix the wildfly 7 we have to back port the URL feature to HornetQ. Howard > JGroupsBroadcastGroupConfiguration Serialization Problem > -------------------------------------------------------- > > Key: WFLY-3805 > URL: https://issues.jboss.org/browse/WFLY-3805 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 8.1.0.Final > Reporter: Yong Hao Gao > Assignee: Yong Hao Gao > Fix For: 10.1.0.Final > > > When configuring JMS connection factories using jgroups discovery group, the client will get serialization exceptions because we pass a JChannel which is not serializable. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 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 February 2016