May 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1412) Hibernate Metamodel Generator is not aware of persistence.xml for JPA 2.1

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-1412?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-1412: ------------------------------------ Looks like a Hibernate warning and exception that needs to be addressed with a [HHH|https://hibernate.onjira.com/browse/HHH] jira/code change. The WildFly persistence.xml parser change for 2.1 was merged a few minutes ago but I don't think that will help you. > Hibernate Metamodel Generator is not aware of persistence.xml for JPA 2.1 > ------------------------------------------------------------------------- > > Key: WFLY-1412 > URL: https://issues.jboss.org/browse/WFLY-1412 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 8.0.0.Alpha2 > Reporter: Juergen Zimmermann > Assignee: Scott Marlow > > I'm using a snapshot of WildFly Alpha2. > The latest usable version of the Hibernate Metamodel Generator is 1.2.0.Final which is only aware of JPA 2.1. If I use a persistence.xml with the new namespace for JPA 2.1, then I get the following (serious?) warning during compilation. I'm not sure whether this is a WildFly or a Hibernate warning. > [WARNING] Hibernate JPA 2 Static-Metamodel Generator 1.2.0.Final > [WARNING] Error unmarshalling /META-INF/persistence.xml with exception : > javax.xml.bind.UnmarshalException > - with linked exception: > [org.xml.sax.SAXParseException; lineNumber: 12; columnNumber: 28; cvc-elt.1: Deklaration des Elements "persistence" kann nicht gefunden werden.] > > This is the beginning of persistence.xml: > <?xml version="1.0"?> >  > <persistence xmlns="http://xmlns.jcp.org/xml/ns/persistence" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd" > version="2.1">  > <persistence-unit name="de.shop.PU"> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1412) Hibernate Metamodel Generator is not aware of persistence.xml for JPA 2.1

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-1412?page=com.atlassian.jira.plugin.... ] Scott Marlow resolved WFLY-1412. -------------------------------- Resolution: Rejected rejecting, please create a HHH jira instead. :-) > Hibernate Metamodel Generator is not aware of persistence.xml for JPA 2.1 > ------------------------------------------------------------------------- > > Key: WFLY-1412 > URL: https://issues.jboss.org/browse/WFLY-1412 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 8.0.0.Alpha2 > Reporter: Juergen Zimmermann > Assignee: Scott Marlow > > I'm using a snapshot of WildFly Alpha2. > The latest usable version of the Hibernate Metamodel Generator is 1.2.0.Final which is only aware of JPA 2.1. If I use a persistence.xml with the new namespace for JPA 2.1, then I get the following (serious?) warning during compilation. I'm not sure whether this is a WildFly or a Hibernate warning. > [WARNING] Hibernate JPA 2 Static-Metamodel Generator 1.2.0.Final > [WARNING] Error unmarshalling /META-INF/persistence.xml with exception : > javax.xml.bind.UnmarshalException > - with linked exception: > [org.xml.sax.SAXParseException; lineNumber: 12; columnNumber: 28; cvc-elt.1: Deklaration des Elements "persistence" kann nicht gefunden werden.] > > This is the beginning of persistence.xml: > <?xml version="1.0"?> >  > <persistence xmlns="http://xmlns.jcp.org/xml/ns/persistence" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd" > version="2.1">  > <persistence-unit name="de.shop.PU"> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1397) handle parsing version 2.1 in JPA subsystem

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-1397?page=com.atlassian.jira.plugin.... ] Scott Marlow closed WFLY-1397. ------------------------------ > handle parsing version 2.1 in JPA subsystem > ------------------------------------------- > > Key: WFLY-1397 > URL: https://issues.jboss.org/browse/WFLY-1397 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Affects Versions: 8.0.0.Alpha1 > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 8.0.0.Alpha2 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1397) handle parsing version 2.1 in JPA subsystem

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-1397?page=com.atlassian.jira.plugin.... ] Scott Marlow resolved WFLY-1397. -------------------------------- Resolution: Done > handle parsing version 2.1 in JPA subsystem > ------------------------------------------- > > Key: WFLY-1397 > URL: https://issues.jboss.org/browse/WFLY-1397 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Affects Versions: 8.0.0.Alpha1 > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 8.0.0.Alpha2 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBAS-9539) ${jdbc.maxPoolSize} value in *-ds.xml file always read as 0 in JBOSS 6.1

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBAS-9539?page=com.atlassian.jira.plugin.... ] Jesper Pedersen closed JBAS-9539. --------------------------------- Labels: (was: regression) Resolution: Out of Date We don't do updates to JBoss AS anymore. Use WildFly, or buy a subscription to JBoss Enterprise Application Platform. For future reference, open a forum post before filing JIRAs. > ${jdbc.maxPoolSize} value in *-ds.xml file always read as 0 in JBOSS 6.1 > ------------------------------------------------------------------------ > > Key: JBAS-9539 > URL: https://issues.jboss.org/browse/JBAS-9539 > Project: Application Server 3 4 5 and 6 > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JCA service > Affects Versions: 6.1.0 > Environment: CentOS/Windows > Reporter: Karthick Narayanan > Assignee: Jesper Pedersen > > I’ve recently started using JBoss 6.1.0 and ran into an issue with setting min and max pool size in oracle-ds.xml. I tried two approaches (for both max and min pool size): > 1. as a hardcoded number like <max-pool-size>5</max-pool-size> > 2. as a configurable variable like <max-pool-size>${jdbc.maxPoolSize}</max-pool-size> > While the first approach worked fine the second one didn't. When the max and min pool sizes were set as configurable variables, the Java.sql.DataSource object created had max-pool-size=0 and min-pool-size=0. All the other settings (being set as configurable variables) in the same xml config file worked as expected. When I did further investigation I found that, > Org.jboss.resource.deployers.ManagedConnectionFactoryParserDeployer class reads all the oracle*-ds.xml files and sets the max/min pool size values to 0 even though I specified <max-pool-size>${jdbc.maxPoolSize}</max-pool-size>. It is not going and reading the value from the property file. > This had been working fine in JBoss 4.2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-887) Support legacy ServiceMBeans in SAR deployments

by Guy Kaisin (JIRA)

[ https://issues.jboss.org/browse/AS7-887?page=com.atlassian.jira.plugin.sy... ] Guy Kaisin edited comment on AS7-887 at 5/29/13 7:52 AM: --------------------------------------------------------- Hi The jboss version you are using does NOT contain the sar deployment correction. The correction has been integrated and tested in jboss 7.2.0 alpha1 build 1372. Please use the last jboss artifact (nightly build for instance). regards, Guy was (Author: kaising): Hi The jboss version you are using oes NOT contain the sar deployment correction. The correction has been integrated and tested in jboss 7.2.0 alpha1 build 1372. Please use the last jboss artifact (nightly build for instance). regards, Guy > Support legacy ServiceMBeans in SAR deployments > ----------------------------------------------- > > Key: AS7-887 > URL: https://issues.jboss.org/browse/AS7-887 > Project: Application Server 7 > Issue Type: Enhancement > Components: JMX > Reporter: Matt Drees > Assignee: Eduardo Martins > Fix For: EAP 6.1.0.Alpha (7.2.0.Final) > > > It looks like the current SAR deployment code (jboss-as-sar) will deploy simple MBeans just fine. However, users may expect to be able to deploy older ServiceMBeans from previous Jboss AS versions. Currently, attempting to do this results in a ClassNotFoundException, since the org.jboss.system.ServiceMBean interface doesn't exist anymore. > Ideally this would also involve supporting ServiceMBeans that extend org.jboss.system.ServiceMBeanSupport, which also doesn't exist anymore. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-887) Support legacy ServiceMBeans in SAR deployments

by Guy Kaisin (JIRA)

[ https://issues.jboss.org/browse/AS7-887?page=com.atlassian.jira.plugin.sy... ] Guy Kaisin commented on AS7-887: -------------------------------- Hi The jboss version you are using oes NOT contain the sar deployment correction. The correction has been integrated and tested in jboss 7.2.0 alpha1 build 1372. Please use the last jboss artifact (nightly build for instance). regards, Guy > Support legacy ServiceMBeans in SAR deployments > ----------------------------------------------- > > Key: AS7-887 > URL: https://issues.jboss.org/browse/AS7-887 > Project: Application Server 7 > Issue Type: Enhancement > Components: JMX > Reporter: Matt Drees > Assignee: Eduardo Martins > Fix For: EAP 6.1.0.Alpha (7.2.0.Final) > > > It looks like the current SAR deployment code (jboss-as-sar) will deploy simple MBeans just fine. However, users may expect to be able to deploy older ServiceMBeans from previous Jboss AS versions. Currently, attempting to do this results in a ClassNotFoundException, since the org.jboss.system.ServiceMBean interface doesn't exist anymore. > Ideally this would also involve supporting ServiceMBeans that extend org.jboss.system.ServiceMBeanSupport, which also doesn't exist anymore. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-887) Support legacy ServiceMBeans in SAR deployments

by rajesh k (JIRA)

[ https://issues.jboss.org/browse/AS7-887?page=com.atlassian.jira.plugin.sy... ] rajesh k commented on AS7-887: ------------------------------ We are using Jboss EAP6.0.1 and used foo-commonj workmanager.sar that implemented on ServiceMBean and ServiceMBeanSupport. It received same exception as reported here and included previous version supported jars. Can I use your fix that is 6.1.0 jars to resolve this issue. Please help me in this. -Rajesh > Support legacy ServiceMBeans in SAR deployments > ----------------------------------------------- > > Key: AS7-887 > URL: https://issues.jboss.org/browse/AS7-887 > Project: Application Server 7 > Issue Type: Enhancement > Components: JMX > Reporter: Matt Drees > Assignee: Eduardo Martins > Fix For: EAP 6.1.0.Alpha (7.2.0.Final) > > > It looks like the current SAR deployment code (jboss-as-sar) will deploy simple MBeans just fine. However, users may expect to be able to deploy older ServiceMBeans from previous Jboss AS versions. Currently, attempting to do this results in a ClassNotFoundException, since the org.jboss.system.ServiceMBean interface doesn't exist anymore. > Ideally this would also involve supporting ServiceMBeans that extend org.jboss.system.ServiceMBeanSupport, which also doesn't exist anymore. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1412) Hibernate Metamodel Generator is not aware of persistence.xml for JPA 2.1

by Juergen Zimmermann (JIRA)

Juergen Zimmermann created WFLY-1412: ---------------------------------------- Summary: Hibernate Metamodel Generator is not aware of persistence.xml for JPA 2.1 Key: WFLY-1412 URL: https://issues.jboss.org/browse/WFLY-1412 Project: WildFly Issue Type: Bug Components: JPA / Hibernate Affects Versions: 8.0.0.Alpha2 Reporter: Juergen Zimmermann Assignee: Scott Marlow I'm using a snapshot of WildFly Alpha2. The latest usable version of the Hibernate Metamodel Generator is 1.2.0.Final which is only aware of JPA 2.1. If I use a persistence.xml with the new namespace for JPA 2.1, then I get the following (serious?) warning during compilation. I'm not sure whether this is a WildFly or a Hibernate warning. [WARNING] Hibernate JPA 2 Static-Metamodel Generator 1.2.0.Final [WARNING] Error unmarshalling /META-INF/persistence.xml with exception : javax.xml.bind.UnmarshalException - with linked exception: [org.xml.sax.SAXParseException; lineNumber: 12; columnNumber: 28; cvc-elt.1: Deklaration des Elements "persistence" kann nicht gefunden werden.] This is the beginning of persistence.xml: <?xml version="1.0"?>  <persistence xmlns="http://xmlns.jcp.org/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd" version="2.1">  <persistence-unit name="de.shop.PU"> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1411) UT005013 at the end of an Arquillian test

by Juergen Zimmermann (JIRA)

Juergen Zimmermann created WFLY-1411: ---------------------------------------- Summary: UT005013 at the end of an Arquillian test Key: WFLY-1411 URL: https://issues.jboss.org/browse/WFLY-1411 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 8.0.0.Alpha2 Reporter: Juergen Zimmermann Assignee: Stuart Douglas I'm using an Alpha 2 snapshot of WildFly. When an Arquillian test ends I'm getting the following stacktrace: ... 20:07:12,101 INFO [org.jboss.as.server] JBAS018558: Undeployed "shop2.war" (runtime-name: "shop2.war") 20:07:12,131 ERROR [io.undertow.request.io] UT005013: An IOException occurred: java.io.IOException: Eine vorhandene Verbindung wurde vom Remotehost geschlossen at sun.nio.ch.SocketDispatcher.read0(Native Method) [rt.jar:1.7.0_21] at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43) [rt.jar:1.7.0_21] at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:225) [rt.jar:1.7.0_21] at sun.nio.ch.IOUtil.read(IOUtil.java:193) [rt.jar:1.7.0_21] at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:359) [rt.jar:1.7.0_21] at org.xnio.nio.NioSocketConduit.read(NioSocketConduit.java:262) [xnio-nio-3.1.0.CR3.jar:3.1.0.CR3] at org.xnio.conduits.ConduitStreamSourceChannel.read(ConduitStreamSourceChannel.java:127) [xnio-api-3.1.0.CR3.jar:3.1.0.CR3] at io.undertow.server.HttpReadListener.handleEvent(HttpReadListener.java:83) at io.undertow.server.HttpReadListener.handleEvent(HttpReadListener.java:43) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:91) [xnio-api-3.1.0.CR3.jar:3.1.0.CR3] at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:61) [xnio-api-3.1.0.CR3.jar:3.1.0.CR3] at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:85) [xnio-nio-3.1.0.CR3.jar:3.1.0.CR3] at org.xnio.nio.WorkerThread.run(WorkerThread.java:528) [xnio-nio-3.1.0.CR3.jar:3.1.0.CR3] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

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 May 2013