September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBAS-1832) Improving JBoss WebConsole's snapshots

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1832?page=all ] Darran Lofthouse updated JBAS-1832: ----------------------------------- Component/s: Web Console (was: Management services) > Improving JBoss WebConsole's snapshots > -------------------------------------- > > Key: JBAS-1832 > URL: http://jira.jboss.com/jira/browse/JBAS-1832 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web Console > Affects Versions: JBossAS-4.0.0 Final > Environment: Not relevant > Reporter: Mathieu Bourrier > Priority: Minor > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The snapshots in the Webconsole cannot be started automatically on startup, as the Recording field isn't an attribute. > 2 classes need to be modified, and the changes are quite small. > Given topic describes changes to be made in order to manage it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBESB-5) Leverage existing tools

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-5?page=all ] Mark Little closed JBESB-5. --------------------------- Resolution: Out of Date > Leverage existing tools > ----------------------- > > Key: JBESB-5 > URL: http://jira.jboss.com/jira/browse/JBESB-5 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JBI Core > Reporter: Joseph Marques > Assigned To: Mark Little > > Why doesn't JBoss start from and extend one of the current open source ESB solutions such as Mule or ServiceMix (the latter of which has a core JBI implementation)? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-142) Add support for processing messages received by Listeners through a pipeline of action processors.

by Tom Fennelly (JIRA)

Add support for processing messages received by Listeners through a pipeline of action processors. -------------------------------------------------------------------------------------------------- Key: JBESB-142 URL: http://jira.jboss.com/jira/browse/JBESB-142 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Reporter: Tom Fennelly Assigned To: Mark Little Fix For: 4.0 Rosetta supported a 1:1 listener to action handler message processing model. We need to be able to push the messages into a pipeline of action processors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
2
0 / 0

WebHosting Profesional.

by Hostex.cl

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3672) EJB3.0 session bean look up and data source configuration

by madan srinivas (JIRA)

EJB3.0 session bean look up and data source configuration --------------------------------------------------------- Key: JBAS-3672 URL: http://jira.jboss.com/jira/browse/JBAS-3672 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-4.0.4.CR2 Environment: Windows 2000 Professional , JBoss 4.0.4CR2, SQL Server 2005 Reporter: madan srinivas Assigned To: Bill Burke I have deployed datasource using mssqlds.xml in jboss/server/default/deploy sqljdbc.jar has been placed in jboss/server/default/lib directory driver class is com.microsoft.sqlserver.jdbc.SQLServerDriver but if i use it i get Wrong driver class error hence i changed it to com.microsoft.jdbc.sqlserver.SQLServerDriver but irt fails to register the river Error : Caused by: org.jboss.resource.JBossResourceException: Failed to register driver for: com.microsoft.jdbc.sqlserver.SQLServerDriver; - nested throwable: (java.lan g.ClassNotFoundException: No ClassLoaders found for: com.microsoft.jdbc.sqlserve r.SQLServerDriver) Server output on console for EJB deployment : But when i do jndi look up i get received timed out error , pls help 11:47:06,356 INFO [NamingHelper] JNDI InitialContext properties:{java.naming.fa ctory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.p kgs=org.jboss.naming:org.jnp.interfaces} 11:47:06,403 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:jar=Test. jar,name=FileDetailsClientBean,service=EJB3 with dependencies: 11:47:06,403 INFO [JmxKernelAbstraction] persistence.units:jar=Test.jar,u nitName=manager1 11:47:06,653 INFO [EJBContainer] STARTED EJB: com.hqs.ppsadvantage.ejb.FileDeta ilsClientBean ejbName: FileDetailsClientBean 11:47:06,731 INFO [EJB3Deployer] Deployed: file:/D:/jboss-4.0.4.CR2/server/defa ult/deploy/Test.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-542) Closing connection inside MessageListener's onMessage() causes deadlock

by Ovidiu Feodorov (JIRA)

Closing connection inside MessageListener's onMessage() causes deadlock ----------------------------------------------------------------------- Key: JBMESSAGING-542 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-542 Project: JBoss Messaging Issue Type: Bug Components: JMS Facade Affects Versions: 1.0.1.CR4 Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.0.1.CR5, 1.2.0.Alpha1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
6
0 / 0

[JBoss JIRA] Created: (JBSER-88) Create DataContainer.clone method

by Clebert Suconic (JIRA)

Create DataContainer.clone method --------------------------------- Key: JBSER-88 URL: http://jira.jboss.com/jira/browse/JBSER-88 Project: JBoss Serialization Issue Type: Feature Request Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: 1.0.3 GA, 1.1.0 Beta DataContainer was not meant to be multi-thread. However if you want to use Datacontainer as an object factory it would be possible to reuse its internal data in a clone operation, and then use the result in a multi-thread environment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
6
0 / 0

[JBoss JIRA] Commented: (JBCACHE-326) Create the concept of a "priority queue" to speed execution of certain remote method invocations

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-326?page=comments#action_12343627 ] Brian Stansberry commented on JBCACHE-326: ------------------------------------------ I'm not 100% sure, but this likely won't improve much for state transfer once FLUSH is done. I guess the benefit would be if block call were stuck in the jg up queue because a preceding repl msg is held up by a lock conflict. Probably we should wait and see what comes out of implementing block() . > Create the concept of a "priority queue" to speed execution of certain remote method invocations > ------------------------------------------------------------------------------------------------ > > Key: JBCACHE-326 > URL: http://jira.jboss.com/jira/browse/JBCACHE-326 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Stansberry > Assigned To: Vladimir Blagojevic > Fix For: 2.0.0 > > > Change the handling of requests in JBossCache (another interceptor on top of ReplicationInterceptor): > - Create 2 queues (of MethodCall objects), one thread for each queue > - The regular MethodCalls like put(), remove() etc go into the default queue (A), where they are processed according to order (FIFO) > - The special calls like block(), _getState(), commit() or acks for PREPARE/COMMIT calls go into the other (priority) queue (B), these calls *CAN* be received out of sequence > - This way, an _getState() would always be processed and would be able to (1) stop the processing of queue A and (2) force- release any locks held > by on the tree. > _ This way commit() calls can promptly release locks, without having to wait behind other prepare calls. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2614) Add a stress test of region activation/inactivation under load

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2614?page=all ] Brian Stansberry updated JBAS-2614: ----------------------------------- Fix Version/s: JBossAS-4.0.6.CR1 (was: JBossAS-4.0.5.GA) > Add a stress test of region activation/inactivation under load > -------------------------------------------------------------- > > Key: JBAS-2614 > URL: http://jira.jboss.com/jira/browse/JBAS-2614 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Test Suite > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Priority: Minor > Fix For: JBossAS-4.0.6.CR1 > > Original Estimate: 6 hours > Remaining Estimate: 6 hours > > There are already tests of this in the JBossCache testsuite, but a test that involves the JBossCacheManager layer as well would be good. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-311) Add destination deployment params test

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-311?page=all ] Ovidiu Feodorov closed JBMESSAGING-311. --------------------------------------- > Add destination deployment params test > -------------------------------------- > > Key: JBMESSAGING-311 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-311 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Alex Fu > Fix For: 1.0.1.CR1 > > > A bug was fixed just before 1.0 release where destination params were being validated on each setXXX call, causing destinations to de deployed with the wrong params. > This has been fixed, but test needs to be added to prevent this happening again. > Imagine I have queue with fullSize = 100, pageSize = 50, downCacheSize = 50 > I then want to set the queue to have fullSize = 1000, pageSize = 500, downCacheSize = 500 > If I attempt to set the queue's downCacheSize to 500 then it will fail to set it, since the downCacheSize would temporarily be more than fullSize. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 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 September 2006