April 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBMETA-346) LoadOnStartup annotation of a servlet is ignored if servlet is mentioned in the web.xml even without a load-on-startup element

by Robert Panzer (Created) (JIRA)

LoadOnStartup annotation of a servlet is ignored if servlet is mentioned in the web.xml even without a load-on-startup element ------------------------------------------------------------------------------------------------------------------------------ Key: JBMETA-346 URL: https://issues.jboss.org/browse/JBMETA-346 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Components: web Environment: JBoss 7.1.0.CR1-SNAPSHOT, Win7 64Bit, JDK 1.6.0-29 64Bit Reporter: Robert Panzer Assignee: Carlo de Wolf I have a servlet that defines a loadOnStartup value using an annotation. Additionally I have a web.xml that mentions this servlet but does not contain a load-on-startup element and is not metadata-complete. Then the annotated value is ignored and the loadOnStartup value falls back to a "default" of 0 (instead of -1 being the predefined default). I already found the bug and will attach a pull request -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

8
9
0 / 0

[JBoss JIRA] (JBMETA-355) Application Exception Class is not trimmed

by Bartosz Baranowski (JIRA)

Bartosz Baranowski created JBMETA-355: ----------------------------------------- Summary: Application Exception Class is not trimmed Key: JBMETA-355 URL: https://issues.jboss.org/browse/JBMETA-355 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Components: ejb Affects Versions: 7.0.0.Final Reporter: Bartosz Baranowski Assignee: Carlo de Wolf Priority: Minor Fix For: 7.0.1 All parsers use super.getElementText(XML...), the Application Exception parser does not. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
4
0 / 0

[JBoss JIRA] (JBRULES-2269) Virtual Service Manager

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/JBRULES-2269?page=com.atlassian.jira.plug... ] Toni Rikkola updated JBRULES-2269: ---------------------------------- Fix Version/s: 5.4.0.Final (was: 5.4.0.CR1) > Virtual Service Manager > ----------------------- > > Key: JBRULES-2269 > URL: https://issues.jboss.org/browse/JBRULES-2269 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assignee: Mark Proctor > Fix For: 5.4.0.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-2936) Importing decision table from Excel: Non Ascii chars should not be corrupted

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/JBRULES-2936?page=com.atlassian.jira.plug... ] Toni Rikkola updated JBRULES-2936: ---------------------------------- Fix Version/s: 5.4.0.Final (was: 5.4.0.CR1) > Importing decision table from Excel: Non Ascii chars should not be corrupted > ---------------------------------------------------------------------------- > > Key: JBRULES-2936 > URL: https://issues.jboss.org/browse/JBRULES-2936 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Geoffrey De Smet > Fix For: 5.4.0.Final > > > see > http://stackoverflow.com/questions/5298748/guvnor-rules-encoding > Excel (like windows) probably has crappy encoding standardization (as in none at all), so I suspect that we 'll need to ask the excel document what encoding (or even what locale) it is and read the data in that encoding. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-4473) Appclient: "JBAS013202: Error closing connection: java.io.InterruptedIOException: Interrupted while waiting for close to complete" in console

by Wolfgang Knauf (JIRA)

Wolfgang Knauf created AS7-4473: ----------------------------------- Summary: Appclient: "JBAS013202: Error closing connection: java.io.InterruptedIOException: Interrupted while waiting for close to complete" in console Key: AS7-4473 URL: https://issues.jboss.org/browse/AS7-4473 Project: Application Server 7 Issue Type: Bug Components: Application Client Affects Versions: 7.1.1.Final Environment: JBoss 7.1.2 snapshot of 2012-04-10, Windows XP64, Sun Java 1.6.0_31 Reporter: Wolfgang Knauf Assignee: Stuart Douglas Priority: Minor I tried to run the sample attached to the 7th reply in the linked forum thread, using "appclient.bat" (which was made functionable in snapshot of 2012-04-10). Everything works fine, but in the console output, I see this exception: 20:52:17,156 ERROR [org.jboss.as.appclient.logging] JBAS013202: Error closing connection: java.io.InterruptedIOException: Interrupted while waiting for close to complete at org.jboss.remoting3.spi.AbstractHandleableCloseable.close(AbstractHandleableCloseable.java:180) [jboss-remoting-3.2.4.GA.jar:3.2.4.GA] at org.jboss.as.appclient.service.LazyConnectionContextSelector.close(LazyConnectionContextSelector.java:88) [jboss-as-appclient-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.appclient.service.ApplicationClientStartService$1.run(ApplicationClientStartService.java:148) [jboss-as-appclient-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_31] Attached is the full console output of the appclient run. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] (AS7-4434) CLONE - It's impossible to add more than 1 custom workmanager to JCA subsystem

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4434?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-4434: --------------------------------------- Stefano, can you make this one a priority? > CLONE - It's impossible to add more than 1 custom workmanager to JCA subsystem > ------------------------------------------------------------------------------ > > Key: AS7-4434 > URL: https://issues.jboss.org/browse/AS7-4434 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, JCA > Affects Versions: 7.1.1.Final > Reporter: Vladimir Rastseluev > Assignee: Stefano Maestri > Fix For: 7.1.2.Final-redhat1 > > > 09:45:35,526 ERROR [org.jboss.as.server] JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:141) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.server.ServerService.boot(ServerService.java:266) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:155) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_23] > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[200,13] > Message: JBAS014789: Unexpected element '{urn:jboss:domain:jca:1.1}workmanager' encountered > at org.jboss.as.controller.parsing.ParseUtils.unexpectedElement(ParseUtils.java:85) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.connector.subsystems.jca.JcaExtension$ConnectorSubsystemParser.readElement(JcaExtension.java:311) > at org.jboss.as.connector.subsystems.jca.JcaExtension$ConnectorSubsystemParser.readElement(JcaExtension.java:176) > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.as.server.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:897) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_1(StandaloneXml.java:332) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:128) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:100) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > ... 3 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBID-234) JBoss IDM LM debug output is always on

by Martin Vecera (JIRA)

Martin Vecera created JBID-234: ---------------------------------- Summary: JBoss IDM LM debug output is always on Key: JBID-234 URL: https://issues.jboss.org/browse/JBID-234 Project: JBoss Identity Issue Type: Bug Components: Identity-Federation, IDM Affects Versions: 1.0.0.alpha2 Reporter: Martin Vecera Assignee: Boleslaw Dawidowicz Priority: Trivial There are missing curly braces in the JBossIdentityIDMLoginModule.initialize() method and debug messages are always logged except for the first one. I found it in the version 1.1.1.GA which is not present in Affects Version here in Jira. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
2
0 / 0

[JBoss JIRA] (AS7-4474) Properly escape the jmx model contoller facade object names

by Kabir Khan (JIRA)

Kabir Khan created AS7-4474: ------------------------------- Summary: Properly escape the jmx model contoller facade object names Key: AS7-4474 URL: https://issues.jboss.org/browse/AS7-4474 Project: Application Server 7 Issue Type: Sub-task Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 7.1.2.Final-redhat1 Since AS7-4026 allows more values, improve the escaping of the value parts of the path elements in the object name properties. Do this according to the ObjectName javadoc -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-4475) Fix error handling in the helloworld-jms quickstart

by Farah Juma (JIRA)

Farah Juma created AS7-4475: ------------------------------- Summary: Fix error handling in the helloworld-jms quickstart Key: AS7-4475 URL: https://issues.jboss.org/browse/AS7-4475 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.1.Final Reporter: Farah Juma When building the helloworld-jms quickstart without having created an application user, the call to connection = connectionFactory.createConnection(); fails with the error: {code} Apr 11, 2012 9:25:15 AM org.jboss.as.quickstarts.jms.HelloWorldJMSClient main SEVERE: Unable to validate user: null {code} The server log shows: {code} 09:25:15,186 ERROR [org.hornetq.core.protocol.core.impl.HornetQPacketHandler] (Old I/O server worker (parentId: 213209572, [id: 0x0cb551e4, /127.0.0.1:5445])) Failed to create session : HornetQException[errorCode=105 message=Unable to validate user: null] at org.hornetq.core.security.impl.SecurityStoreImpl.authenticate(SecurityStoreImpl.java:147) [hornetq-core-2.2.13.Final.jar:] at org.hornetq.core.server.impl.HornetQServerImpl.createSession(HornetQServerImpl.java:807) [hornetq-core-2.2.13.Final.jar:] at org.hornetq.core.protocol.core.impl.HornetQPacketHandler.handleCreateSession(HornetQPacketHandler.java:187) [hornetq-core-2.2.13.Final.jar:] at org.hornetq.core.protocol.core.impl.HornetQPacketHandler.handlePacket(HornetQPacketHandler.java:85) [hornetq-core-2.2.13.Final.jar:] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:508) [hornetq-core-2.2.13.Final.jar:] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:556) [hornetq-core-2.2.13.Final.jar:] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:517) [hornetq-core-2.2.13.Final.jar:] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:533) [hornetq-core-2.2.13.Final.jar:] at org.hornetq.core.remoting.impl.netty.HornetQChannelHandler.messageReceived(HornetQChannelHandler.java:73) [hornetq-core-2.2.13.Final.jar:] ... {code} To run this quickstart, an application user needs to be created first. However, when a user hasn't been created, the quickstart still displays a BUILD SUCCESS even though that's not true. The exception is caught and the SEVERE message is logged but the messages were never sent nor received. The quickstart should be rewritten so that it succeeds only if the messages that were sent are effectively received. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-1322) Discovery protocol based on mod-cluster

by alex soto (JIRA)

Discovery protocol based on mod-cluster --------------------------------------- Key: JGRP-1322 URL: https://issues.jboss.org/browse/JGRP-1322 Project: JGroups Issue Type: Feature Request Reporter: alex soto Assignee: Bela Ban It would be nice to have a discovery protocol that can use mod-cluster as the source of the node information. Mod-cluster already knows the list of participating nodes and provides this information in a well known format, so it could be simple to implement. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
3
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 April 2012