October 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Resolved: (JBAS-6722) Hot deployment broken with JBoss 5.0.1.GA

by Dmytro Lisnichenko (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-6722?page=com.atlassian.jira.plug... ] Dmytro Lisnichenko resolved JBAS-6722. -------------------------------------- Resolution: Done > Hot deployment broken with JBoss 5.0.1.GA > ----------------------------------------- > > Key: JBAS-6722 > URL: https://jira.jboss.org/jira/browse/JBAS-6722 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Component > Environment: JBoss 5.0.1 GA > JDK 5 update 16 > Seam trunk > Reporter: Jozef Hartinger > Assignee: Ales Justin > Priority: Critical > Fix For: JBossAS-5.2.0.Beta1 > > > Hot deployment does not seem to work. I am using seam-gen to create a war packaged application and deploy it on JBoss 5.0.1 GA. It deploys fine, but: > a) deployment of XHTML template > modified facelet templates are not being picked up > b) deployment of action Java Bean > I run new-action to create a ping action component and run "explode" target. Component does not deploy. There is nothing in the server log that would indicate that server is even trying to load the component. > All mentioned above works fine on JBoss 4.2.3 and JBoss 5.0.0 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBAS-6722) Hot deployment broken with JBoss 5.0.1.GA

by Dmytro Lisnichenko (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-6722?page=com.atlassian.jira.plug... ] Dmytro Lisnichenko reopened JBAS-6722: -------------------------------------- > Hot deployment broken with JBoss 5.0.1.GA > ----------------------------------------- > > Key: JBAS-6722 > URL: https://jira.jboss.org/jira/browse/JBAS-6722 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Component > Environment: JBoss 5.0.1 GA > JDK 5 update 16 > Seam trunk > Reporter: Jozef Hartinger > Assignee: Ales Justin > Priority: Critical > Fix For: JBossAS-5.2.0.Beta1 > > > Hot deployment does not seem to work. I am using seam-gen to create a war packaged application and deploy it on JBoss 5.0.1 GA. It deploys fine, but: > a) deployment of XHTML template > modified facelet templates are not being picked up > b) deployment of action Java Bean > I run new-action to create a ping action component and run "explode" target. Component does not deploy. There is nothing in the server log that would indicate that server is even trying to load the component. > All mentioned above works fine on JBoss 4.2.3 and JBoss 5.0.0 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7392) org.jboss.wsf.stack.jbws.EndpointServlet

by Shelly McGowan (JIRA)

org.jboss.wsf.stack.jbws.EndpointServlet ---------------------------------------- Key: JBAS-7392 URL: https://jira.jboss.org/jira/browse/JBAS-7392 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan -- 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, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-7389) javassist.util.proxy.SerializedProxy

by Shelly McGowan (JIRA)

javassist.util.proxy.SerializedProxy ------------------------------------ Key: JBAS-7389 URL: https://jira.jboss.org/jira/browse/JBAS-7389 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBID-202) STSClientConfig: Add parse method to populate the builder to allow properties overrides

by Daniel Bevenius (JIRA)

STSClientConfig: Add parse method to populate the builder to allow properties overrides --------------------------------------------------------------------------------------- Key: JBID-202 URL: https://jira.jboss.org/jira/browse/JBID-202 Project: JBoss Identity Issue Type: Task Components: Identity-Federation Reporter: Daniel Bevenius Assignee: Daniel Bevenius Priority: Minor Fix For: IDFED-1.0.0.beta3 Add a parse method that parses a sts client configuration file (properties file) and returns a the builder instance. This will allow for overrides. The use case I have for this is a password in the configuration that may be a path to an encrypted password file. Having this method would allow a client to first parse the configuration file and modify a property before creating the STSConfigClient instance For example: Builder builder = new STSClientConfig.Builder("wstrust/sts-client.properties"); builder.password(overriddenPassword); STSClientConfig config = builder.build(); -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBBOOT-113) Don't expose the default server implementation class namein JBossASEmbeddedServerFactory

by Andrew Lee Rubinger (JIRA)

Don't expose the default server implementation class namein JBossASEmbeddedServerFactory ---------------------------------------------------------------------------------------- Key: JBBOOT-113 URL: https://jira.jboss.org/jira/browse/JBBOOT-113 Project: JBoss Bootstrap Issue Type: Task Components: api-embedded Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: api-embedded-2.0.0-alpha-2 public > private -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-1075) TestNG dependency problem

by Bulat Nigmatullin (JIRA)

TestNG dependency problem ------------------------- Key: JGRP-1075 URL: https://jira.jboss.org/jira/browse/JGRP-1075 Project: JGroups Issue Type: Patch Affects Versions: 2.8 Reporter: Bulat Nigmatullin Assignee: Bela Ban Priority: Optional Fix For: 2.8 Maven produced jar include TestNG dependency. If project uses JGroups then all it dependencies automatically downloaded and attached to classpath. If project uses JUnit for unit test then Maven Surefire Plugin don't run them, cause find TestNG in classpath and searching for TestNG test suites. -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBBOOT-112) Add overview.html, package.html for JavaDoc

by Andrew Lee Rubinger (JIRA)

Add overview.html, package.html for JavaDoc ------------------------------------------- Key: JBBOOT-112 URL: https://jira.jboss.org/jira/browse/JBBOOT-112 Project: JBoss Bootstrap Issue Type: Feature Request Components: api, api-as, api-embedded, api-mc, build, impl-as, impl-base, impl-embedded, impl-mc, legacy, main, spi, spi-as, spi-mc Reporter: Andrew Lee Rubinger Identified by Jesper -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-967) Deadlock in FD_SOCK

by Richard Achmatowicz (JIRA)

Deadlock in FD_SOCK -------------------- Key: JGRP-967 URL: https://jira.jboss.org/jira/browse/JGRP-967 Project: JGroups Issue Type: Bug Affects Versions: 2.4.5 Environment: Deadlock detected on Fedora 8, JDK 1.4/JDK 1.5. Reporter: Richard Achmatowicz Assignee: Bela Ban Priority: Minor Due to a problem with IPv6 addresses and ServerSocket connections hanging, a deadlock was revealed in FD_SOCK. The deadlock reveals itself, for example, in the test RpcDispatcherAnycastTest at the end of the test, when the channels are being torn down. What follows are my original emails to Bela: Richard: I've tracked down the test case failure of RpcDispatcherAnycastTest under IPv6 to a problem with shutting down the protocol stack. The test executes fine, but in the teardown phase, when the test tries to close the three JChannels which have been set up, the first channel closes correctly, but the second channel hangs. JChannel tries to disconnect from the group before shutting down by: (i) sending a DISCONNECT event and waits for a DISCONNECT_OK event via a promise (ii) sending a STOP_QUEUING event and waita for a return from the call (i.e. has reached the bottom of the stack) It then calls ProtocolStack.stopStack() which sends a STOP event down the stack and waits for a STOP_OK event via a promise. The STOP event is not making its way correctly down the stack. Here is a trace with IPv4 (i've added in some tracing of the STOP event of my own): [junit] JChannel.disconnect(): waiting for DISCONNECT_OK [junit] JChannel.disconnect(): got DISCONNECT_OK [junit] JChannel.disconnect(): stopping queue [junit] FD_SOCK.down called, event = STOP_QUEUEING [junit] JChannel.disconnect(): stopped queue [junit] JChannel.disconnect(): stopping stack [junit] ProtocolStack: Sending STOP event [junit] STATE_TRANSFER: STOP event received [junit] FRAG2: STOP event received [junit] FC: STOP event received [junit] GMS: STOP event received [junit] VIEW_SYNC: STOP event received [junit] pbcast.STABLE: STOP event received [junit] UNICAST: STOP event received [junit] VERIFY_SUSPECT: STOP event received [junit] FD: STOP event received [junit] FD_SOCK.down called, event = STOP [junit] FD_SOCK: STOP event received [junit] MERGE2: STOP event received [junit] PING: STOP event received [junit] ProtocolStack: Received STOP event [junit] JChannel.disconnect(): stopped stack Here is a bad trace with IPv6: [junit] JChannel.disconnect(): waiting for DISCONNECT_OK [junit] JChannel.disconnect(): got DISCONNECT_OK [junit] JChannel.disconnect(): stopping queue [junit] FD_SOCK.down called, event = STOP_QUEUEING [junit] JChannel.disconnect(): stopped queue [junit] JChannel.disconnect(): stopping stack [junit] ProtocolStack: Sending STOP event [junit] STATE_TRANSFER: STOP event received [junit] FRAG2: STOP event received [junit] FC: STOP event received [junit] GMS: STOP event received [junit] VIEW_SYNC: STOP event received [junit] pbcast.STABLE: STOP event received [junit] UNICAST: STOP event received [junit] VERIFY_SUSPECT: STOP event received [junit] FD: STOP event received [junit] FD_SOCK.down called, event = MSG [junit] FD_SOCK.down called, event = MSG [junit] FD_SOCK.down called, event = MSG [junit] FD_SOCK.down called, event = MSG If I remove FD_SOCK from the stack, the tests pass. If I include it, this stuff happens. I also found that if I turn on the uphandler and downhandler threads in FD_SOCK, the problem disappears: ... <MERGE2 max_interval="30000" down_thread="false" up_thread="false" min_interval="10000"/> <FD_SOCK down_thread="true" up_thread="true"/> <FD timeout="10000" max_tries="5" down_thread="false" up_thread="false" shun="true"/> ... Bela: Then it must be a locking issue, I'll take a look tomorrow. Or if you find the solution sooner, all the better ! :-) -- 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, 9 months

3
13
0 / 0

[JBoss JIRA] Created: (JBWEB-150) Facilitate identifying web app classloader in heap dump

by Mike Millson (JIRA)

Facilitate identifying web app classloader in heap dump ------------------------------------------------------- Key: JBWEB-150 URL: https://jira.jboss.org/jira/browse/JBWEB-150 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mike Millson Assignee: Mike Millson When troubleshooting OutOfMemoryError issues in situations where the JVM is running multiple applications, it would be very helpful for troubleshooting to be able to relate a web application to the web app classloader. It is proposed to sets the display-name of the war as a property on the web app classloader so that it can be easily accessed when viewing a heap dump (e.g. with a tool such as the Eclipse Memory Analyzer Tool). -- 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, 9 months

2
13
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 October 2009