September 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBANN-32) Add an exlude all annotations option

by Jesper Pedersen (JIRA)

Add an exlude all annotations option ------------------------------------ Key: JBANN-32 URL: https://jira.jboss.org/jira/browse/JBANN-32 Project: Papaki Issue Type: Task Components: Tool - Indexer Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Beta1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBANN-31) Add a maven download description

by Jesper Pedersen (JIRA)

Add a maven download description -------------------------------- Key: JBANN-31 URL: https://jira.jboss.org/jira/browse/JBANN-31 Project: Papaki Issue Type: Task Components: Documentation Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Beta1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBANN-30) Add an advanced usage scenario

by Jesper Pedersen (JIRA)

Add an advanced usage scenario ------------------------------ Key: JBANN-30 URL: https://jira.jboss.org/jira/browse/JBANN-30 Project: Papaki Issue Type: Task Components: Documentation Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Beta1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
1
0 / 0

[JBoss JIRA] Resolved: (JBANN-7) Generate a HTML report of annotations

by Jesper Pedersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBANN-7?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBANN-7. --------------------------------- Resolution: Done XML not included > Generate a HTML report of annotations > ------------------------------------- > > Key: JBANN-7 > URL: https://jira.jboss.org/jira/browse/JBANN-7 > Project: Papaki > Issue Type: Task > Components: Tool - Indexer > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.0.0.Beta1 > > > Generate a HTML report of the annotations found inside the file -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-1107) SocketServerInvoker.IdleTimeoutTask interrupts ServerThreads during long invocation

by Ron Sigal (JIRA)

SocketServerInvoker.IdleTimeoutTask interrupts ServerThreads during long invocation ----------------------------------------------------------------------------------- Key: JBREM-1107 URL: https://jira.jboss.org/jira/browse/JBREM-1107 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.5.0.SP2 (Flounder) , 2.2.2.SP11 Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.2.SP12, 2.5.0.SP3 (Flounder) org.jboss.remoting.transport.socket.SocketServerInvoker.IdleTimerTask is intended to shut down org.jboss.remoting.transport.socket.ServerThreads that haven't been in use for some configured amount of time. For each ServerThread, it compares the value of System.currentTimeMillis() to the time at which the ServerThread last started or finished processing an invocation, and, if the difference exceeds the value of the "idleTimeout" parameter, it shuts down the ServerThread. The problem is that if processing an invocation takes longer than the value of "idleTimeout", a ServerThread could be shut down DURING the processing of an invocation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
5
0 / 0

[JBoss JIRA] Created: (JBREM-1146) Treat IOException("Connection reset by peer") as a retriable exception

by Ron Sigal (JIRA)

Treat IOException("Connection reset by peer") as a retriable exception ---------------------------------------------------------------------- Key: JBREM-1146 URL: https://jira.jboss.org/jira/browse/JBREM-1146 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.2.3, 2.5.1 (Flounder) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.2 (Flounder), 2.2.3.SP1 org.jboss.remoting.transport.socket.MicroSocketClientInvoker uses the parameter "numberOfCallRetries" to determine the number of invocation attempts to make upon receiving java.net.SocketExceptions. For example, SocketException("Connection reset") will cause MicroSocketClientInvoker to get another socket and try again. However, if a connection is reset on the other side, then an IOException("Connection reset by peer") is thrown, which doesn't lead to a retry. It should be possible to configure the socket transport to treat an IOException("Connection reset by peer") as retriable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

2
4
0 / 0

[JBoss JIRA] Resolved: (JBANN-8) Support exclusion of annotations

by Jesper Pedersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBANN-8?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBANN-8. --------------------------------- Resolution: Done > Support exclusion of annotations > -------------------------------- > > Key: JBANN-8 > URL: https://jira.jboss.org/jira/browse/JBANN-8 > Project: Papaki > Issue Type: Task > Components: Tool - Indexer > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.0.0.Beta1 > > > Allow the user to specify which annotations should be excluded from in annotation parsing phase. > F.ex. java.lang.Deprecated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7230) Deployment Problem

by Satyaranjan Panda (JIRA)

Deployment Problem ------------------ Key: JBAS-7230 URL: https://jira.jboss.org/jira/browse/JBAS-7230 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-5.1.0.GA Environment: Java 6, Jboss5.1.0.GA EJB 2.x Reporter: Satyaranjan Panda Assignee: Alexey Loubyansky Priority: Critical I am getting error when I am going to deploy my ear file. Below is the error. Failed to create Resource Puma.ear - cause: java.lang.RuntimeException:org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS IN ERROR: Name -> Error vfsfile:/D:/jboss-5.1.0.GA/server/default/deploy/Puma.ear/ -> org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/D:/jboss-5.1.0.GA/server/default/deploy/Puma.ear/PumaEJBComp/ DEPLOYMENTS IN ERROR: Deployment "vfsfile:/D:/jboss-5.1.0.GA/server/default/deploy/Puma.ear/" is in error due to the following reason(s): org.jboss.xb.binding.JBossXBRuntimeException: -1:-1 87:3 The markup in the document preceding the root element must be well-formed. -> org.jboss.deployers.client.spi.IncompleteDeploymentException:Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS IN ERROR: Name -> Error vfsfile:/D:/jboss-5.1.0.GA/server/default/deploy/Puma.ear/ -> org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/D:/jboss-5.1.0.GA/server/default/deploy/Puma.ear/PumaEJBComp/ DEPLOYMENTS IN ERROR: Deployment "vfsfile:/D:/jboss-5.1.0.GA/server/default/deploy/Puma.ear/" is in error due to the following reason(s): org.jboss.xb.binding.JBossXBRuntimeException: -1:-1 87:3 The markup in the document preceding the root element must be well-formed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1720) JMSUserManager has insert data into JBM_ROLE and JBM_USER every time when it starts.

by ryu ken (JIRA)

JMSUserManager has insert data into JBM_ROLE and JBM_USER every time when it starts. ------------------------------------------------------------------------------------ Key: JBMESSAGING-1720 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1720 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Persistence Affects Versions: 1.4.0.SP3.CP08 Reporter: ryu ken Priority: Minor "CreateTablesOnStartup" attribute value of JMSUserManager has been set to "false". >From the second start of JBossMessaging, Even data of jbm user and role is already exist in JBM_ROLE and JBM_USER tables, JMSUserManager still try to insert data into the tables and cause the data already exist a SQLException. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBANN-29) Rebrand project as Papaki

by Jesper Pedersen (JIRA)

Rebrand project as Papaki ------------------------- Key: JBANN-29 URL: https://jira.jboss.org/jira/browse/JBANN-29 Project: Papaki Issue Type: Task Components: Build, Core, Documentation, Tool - Indexer, Tool - Validator Reporter: Jesper Pedersen Assignee: Jesper Pedersen Priority: Blocker Fix For: 1.0.0.Beta1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
1
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 September 2009