February 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6390) Problem with jboss versions of xerces and xalan: XML Parsing Error: duplicate attribute in wsdl definitions

by Jan Roman (JIRA)

[ https://issues.jboss.org/browse/AS7-6390?page=com.atlassian.jira.plugin.s... ] Jan Roman edited comment on AS7-6390 at 2/25/13 1:24 PM: --------------------------------------------------------- Paul as discussed on mailing list it is desired behavior of Jboss to instantiate managed version of XALAN insted of native one from JDK. I looked into problem and this seems to be rooted much deeper. Please find my pull request linked. There is also another possibility of resolving that problem by change in AttributesImplSerializer just checking for duplicates in attribute list of element at the beginning of "public final void addAttribute(String,String,String,String,String)". was (Author: romanj): Paul as discussed on mailing list it is desired behavior of Jboss to instantiate managed version of XALAN insted of native one from JDK. I looked into problem and this seems to be rooted much deeper. Please find my pull request linked. There is also another possibility of resolving that problem by change in AttributesImplSerializer just checking for duplicates in "public final void addAttribute(String,String,String,String,String)". > Problem with jboss versions of xerces and xalan: XML Parsing Error: duplicate attribute in wsdl definitions > ----------------------------------------------------------------------------------------------------------- > > Key: AS7-6390 > URL: https://issues.jboss.org/browse/AS7-6390 > Project: Application Server 7 > Issue Type: Bug > Components: Web Services > Affects Versions: 7.1.1.Final > Reporter: Michael Vetter > > We are using a feature (SimpleWsdl11Definition) of spring ws (version 1.5.9) to serve wsdl files to the browser or to a client. > Our wsdl file has custom namespace prefixes like this: > <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:bsf="http:/... > > It works in JBoss 5.1 and eap 6.0.0 but with JBoss 7.1.1 or the current 7.2 snapshot I get the following error when I enter the wsdl URL in the browser: > XML Parsing Error: duplicate attribute > Location: http://localhost:8080/sc-webservices/service/loginServiceWS.wsdl > Line Number 1, Column 671:<?xml version="1.0" encoding="UTF-8"?><wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:bsf="http:// > The wsdl served to the browser contains duplicates of the custom namespace prefixes defined in the original wsdl file packaged in a war inside an ear. > While debugging I only saw classes from jboss versions of xerces and xalan parsing the wsdl and serving the result to the client. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6390) Problem with jboss versions of xerces and xalan: XML Parsing Error: duplicate attribute in wsdl definitions

by Jan Roman (JIRA)

[ https://issues.jboss.org/browse/AS7-6390?page=com.atlassian.jira.plugin.s... ] Jan Roman commented on AS7-6390: -------------------------------- Paul as discussed on mailing list it is desired behavior of Jboss to instantiate managed version of XALAN insted of native one from JDK. I looked into problem and this seems to be rooted much deeper. Please find my pull request linked. There is also another possibility of resolving that problem by change in AttributesImplSerializer just checking for duplicates in "public final void addAttribute(String,String,String,String,String)". > Problem with jboss versions of xerces and xalan: XML Parsing Error: duplicate attribute in wsdl definitions > ----------------------------------------------------------------------------------------------------------- > > Key: AS7-6390 > URL: https://issues.jboss.org/browse/AS7-6390 > Project: Application Server 7 > Issue Type: Bug > Components: Web Services > Affects Versions: 7.1.1.Final > Reporter: Michael Vetter > > We are using a feature (SimpleWsdl11Definition) of spring ws (version 1.5.9) to serve wsdl files to the browser or to a client. > Our wsdl file has custom namespace prefixes like this: > <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:bsf="http:/... > > It works in JBoss 5.1 and eap 6.0.0 but with JBoss 7.1.1 or the current 7.2 snapshot I get the following error when I enter the wsdl URL in the browser: > XML Parsing Error: duplicate attribute > Location: http://localhost:8080/sc-webservices/service/loginServiceWS.wsdl > Line Number 1, Column 671:<?xml version="1.0" encoding="UTF-8"?><wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:bsf="http:// > The wsdl served to the browser contains duplicates of the custom namespace prefixes defined in the original wsdl file packaged in a war inside an ear. > While debugging I only saw classes from jboss versions of xerces and xalan parsing the wsdl and serving the result to the client. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6185) EJB2 CMP/CMR problem reading CMR in ejbStore() - IllegalStateException: ARJUNA016082: Synchronizations are not allowed!

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6185?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6185: ---------------------------------- Fix Version/s: 7.2.0.Alpha1 (was: 7.2.0.CR1) (was: 7.1.4.Final (EAP)) > EJB2 CMP/CMR problem reading CMR in ejbStore() - IllegalStateException: ARJUNA016082: Synchronizations are not allowed! > ----------------------------------------------------------------------------------------------------------------------- > > Key: AS7-6185 > URL: https://issues.jboss.org/browse/AS7-6185 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: 7.1.2.Final (EAP) > Reporter: Wolf-Dieter Fink > Assignee: Brad Maxwell > Fix For: 7.2.0.Alpha1 > > > If a CMR relation is loaded within the ejbStore() of an entity the transaction manager throw a IllegalStateException. > The scenario should be possible from EJB spec and it works in EAP5. > The log excerpt is attached. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6500) Wrong injection made by container

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-6500?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved AS7-6500. --------------------------------- Fix Version/s: 8.0.0.Alpha1 Resolution: Done > Wrong injection made by container > --------------------------------- > > Key: AS7-6500 > URL: https://issues.jboss.org/browse/AS7-6500 > Project: Application Server 7 > Issue Type: Bug > Components: EE, EJB, JPA / Hibernate > Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP), 7.1.4.Final (EAP) > Reporter: Luan Cestari > Assignee: Stuart Douglas > Fix For: 8.0.0.Alpha1 > > > Description of problem: > I got an issue in a salesforce case [1] about an incorrect injection. > [1] https://c.na7.visual.force.com/apex/Case_View?id=500A000000CRqDG&sfdc.ove... > Version-Release number of selected component (if applicable): > How reproducible: > To reproduce the case is required to have two PersistentUnit (PU), a Abstract class with a setter method to inject one PU and others classes inheriting the Abstract class and overriding the setter method to inject a different PU. In the runtime, the container inject twice the PU, first the correct PU and then the PU described in super class. > I talked with the client (who is a Red Hat consultant) and we made the attached project based on a very simple JBoss example to reproduce the issue which happens in EAP6. I put a lot of 'println' to be very clear (even printing stacktrace to show who is calling). The most important files are: > -> hibernate4Test/src/main/java/org/jboss/as/quickstart/hibernate4/data/BaseDAO.java -- The abstract class with the default PU injection > -> hibernate4Test/src/main/java/org/jboss/as/quickstart/hibernate4/data/MemberRepository.java -- BaseDAO subclass > -> hibernate4Test/src/main/java/org/jboss/as/quickstart/hibernate4/data/SecondaryMemberRepository.java -- BaseDAO subclass > -> hibernate4Test/src/main/java/org/jboss/as/quickstart/hibernate4/data/MemberListProducer.java -- The class which inject the MemberListProducer and SecondaryMemberRepository > -> hibernate4Test/src/main/resources/META-INF/persistence.xml -- We changed the configuration here to each PU have a different entity mapped > Steps to Reproduce: > > Actual results: > The EM injection occurs twice, which the last one the wrong EM. > Expected results: > Just one injection occurs. > Additional info: -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-4246) Attribute passivate-events-on-replicate of cluster-passivation-store can't be change via drm or cli

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4246?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-4246: --------------------------------------- Please explain how this is a bug. It is not a requirement that the change be immediately propagated to the running services without an intermediate reload. > Attribute passivate-events-on-replicate of cluster-passivation-store can't be change via drm or cli > --------------------------------------------------------------------------------------------------- > > Key: AS7-4246 > URL: https://issues.jboss.org/browse/AS7-4246 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: 7.1.1.Final > Reporter: Ondřej Chaloupka > Assignee: Richard Achmatowicz > Labels: eap6_need_triage > > Setting attribute passivate-events-on-replicate via drm or cli does not take affect until operation :reload is used. > In case that the attribute ( <cluster-passivation-store name="infinispan" cache-container="ejb" passivate-events-on-replicate="false" />) is set directly in standalone*.xml configuration file the supposed functionality is working. > The test for this could be checked on: > https://github.com/ochaloup/jboss-as/blob/JBQA-5855-test-migration-passiv... -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6239) Attribute read for uninstalled bundle breaks console

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6239?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-6239: --------------------------------------- Do you have the full stack trace? > Attribute read for uninstalled bundle breaks console > ---------------------------------------------------- > > Key: AS7-6239 > URL: https://issues.jboss.org/browse/AS7-6239 > Project: Application Server 7 > Issue Type: Bug > Components: Console, OSGi > Reporter: Thomas Diesler > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-52) Both kie-api.jar and drools-compiler.jar contain org/kie/KieBase.class

by Charles Moulliard (JIRA)

[ https://issues.jboss.org/browse/DROOLS-52?page=com.atlassian.jira.plugin.... ] Charles Moulliard commented on DROOLS-52: ----------------------------------------- We also have the same issue with org.drools.grid package which has been created for drools-spring (needed by drools-core I think so) and drools-grid. > Both kie-api.jar and drools-compiler.jar contain org/kie/KieBase.class > ---------------------------------------------------------------------- > > Key: DROOLS-52 > URL: https://issues.jboss.org/browse/DROOLS-52 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Geoffrey De Smet > Assignee: Geoffrey De Smet > Priority: Blocker > > Both kie-api.jar and drools-compiler.jar contain org/kie/KieBase.class. > It looks like drools-compiler is fat jar. Fat jars (even shaded fat jars) are evil. See slide 39-42: > http://ge0ffrey.github.com/maven-dependency-puzzlers/maven-dependency-puz... > Certain platforms (android, ...) don't even allow to deploy such jars. Others (osgi, ...) throw warnings. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6624) Jboss connection pool is not auto reconnects to mySQl (XA-datasource)

by Alexey S. (JIRA)

[ https://issues.jboss.org/browse/AS7-6624?page=com.atlassian.jira.plugin.s... ] Alexey S. commented on AS7-6624: -------------------------------- seems that your last nightly build is not supporting Local EJB connections between Ejb Timer and EJB Session Bean. So it cant be verified there, I suggest you will look on 7.1.1 final > Jboss connection pool is not auto reconnects to mySQl (XA-datasource) > --------------------------------------------------------------------- > > Key: AS7-6624 > URL: https://issues.jboss.org/browse/AS7-6624 > Project: Application Server 7 > Issue Type: Bug > Components: JCA > Affects Versions: 7.1.1.Final > Reporter: Alexey S. > Assignee: Stefano Maestri > > I am using JPA Hibernate in Timer EJB. > After MySQL's restarted, JBOSS connection pool should be restarted also to renew the transaction, but it doesnt happened. > my datasource is > <xa-datasource jndi-name="java:jboss/datasources/db" pool-name="db" enabled="true" use-java-context="true"> > <xa-datasource-property name="ServerName"> > localhost > </xa-datasource-property> > <xa-datasource-property name="DatabaseName"> > db > </xa-datasource-property> > <xa-datasource-property name="User"> > root > </xa-datasource-property> > <xa-datasource-property name="Password"> > xxxxx > </xa-datasource-property> > <xa-datasource-property name="AutoReconnectForPools"> > true > </xa-datasource-property> > <xa-datasource-property name="FailOverReadOnly"> > false > </xa-datasource-property> > <xa-datasource-property name="MaxReconnects"> > 100 > </xa-datasource-property> > <xa-datasource-property name="ReconnectAtTxEnd"> > true > </xa-datasource-property> > <driver>com.mysql</driver> > <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation> > <validation> > <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker"/> > <check-valid-connection-sql>select 1</check-valid-connection-sql> > <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter"/> > </validation> > </xa-datasource> -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6426) Jboss-cli crashes on Windows on backslash in history

by Ståle Pedersen (JIRA)

[ https://issues.jboss.org/browse/AS7-6426?page=com.atlassian.jira.plugin.s... ] Ståle Pedersen commented on AS7-6426: ------------------------------------- jarkko, could you try out a fresh build from git and see if this still fails? i wasnt able to reproduce it when i tested it within æsh on windows with the latest version. > Jboss-cli crashes on Windows on backslash in history > ---------------------------------------------------- > > Key: AS7-6426 > URL: https://issues.jboss.org/browse/AS7-6426 > Project: Application Server 7 > Issue Type: Bug > Components: CLI > Affects Versions: 7.2.0.Alpha1 > Environment: Windows 7, 64-bit > Reporter: Jarkko Rantavuori > Assignee: Alexey Loubyansky > > Note: seems to apply to latest snapshot only, not to 7.1.1. > If you use a backslash in commands (like you need to use on absolute path deployments on windows) and then press up button to go back to that command, jboss-cli crashes with > java.lang.NumberFormatException: For input string: "1B" > at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) > at java.lang.Integer.parseInt(Integer.java:492) > at java.lang.Integer.<init>(Integer.java:677) > at org.fusesource.jansi.AnsiOutputStream.write(AnsiOutputStream.java:120) > at java.io.FilterOutputStream.write(FilterOutputStream.java:125) > at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221) > at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291) > at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295) > at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141) > at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229) > at java.io.PrintWriter.flush(PrintWriter.java:320) > at org.jboss.aesh.terminal.WindowsTerminal.writeToStdOut(WindowsTerminal.java:89) > at org.jboss.aesh.console.Console.drawLine(Console.java:923) > at org.jboss.aesh.console.Console.redrawLine(Console.java:902) > at org.jboss.aesh.console.Console.getHistoryElement(Console.java:673) > at org.jboss.aesh.console.Console.parseOperation(Console.java:476) > at org.jboss.aesh.console.Console.read(Console.java:377) > at org.jboss.aesh.console.Console.read(Console.java:331) > at org.jboss.as.cli.impl.Console$Factory$1.readLine(Console.java:171) > at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl.java:1181) > at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:259) > at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.modules.Module.run(Module.java:270) > at org.jboss.modules.Main.main(Main.java:294) > Press any key to continue . . . -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6624) Jboss connection pool is not auto reconnects to mySQl (XA-datasource)

by Alexey S. (JIRA)

[ https://issues.jboss.org/browse/AS7-6624?page=com.atlassian.jira.plugin.s... ] Alexey S. commented on AS7-6624: -------------------------------- I asked there, nobody knows, will try to reproduce that with latest build > Jboss connection pool is not auto reconnects to mySQl (XA-datasource) > --------------------------------------------------------------------- > > Key: AS7-6624 > URL: https://issues.jboss.org/browse/AS7-6624 > Project: Application Server 7 > Issue Type: Bug > Components: JCA > Affects Versions: 7.1.1.Final > Reporter: Alexey S. > Assignee: Stefano Maestri > > I am using JPA Hibernate in Timer EJB. > After MySQL's restarted, JBOSS connection pool should be restarted also to renew the transaction, but it doesnt happened. > my datasource is > <xa-datasource jndi-name="java:jboss/datasources/db" pool-name="db" enabled="true" use-java-context="true"> > <xa-datasource-property name="ServerName"> > localhost > </xa-datasource-property> > <xa-datasource-property name="DatabaseName"> > db > </xa-datasource-property> > <xa-datasource-property name="User"> > root > </xa-datasource-property> > <xa-datasource-property name="Password"> > xxxxx > </xa-datasource-property> > <xa-datasource-property name="AutoReconnectForPools"> > true > </xa-datasource-property> > <xa-datasource-property name="FailOverReadOnly"> > false > </xa-datasource-property> > <xa-datasource-property name="MaxReconnects"> > 100 > </xa-datasource-property> > <xa-datasource-property name="ReconnectAtTxEnd"> > true > </xa-datasource-property> > <driver>com.mysql</driver> > <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation> > <validation> > <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker"/> > <check-valid-connection-sql>select 1</check-valid-connection-sql> > <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter"/> > </validation> > </xa-datasource> -- 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, 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 2013