June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1194) 'Self' producer fails to be registered at server start

by Matt Wringe (JIRA)

'Self' producer fails to be registered at server start ------------------------------------------------------ Key: JBPORTAL-1194 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1194 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.Alpha1 Environment: Linux 1.5.0 JVM 4.0.5 JBoss AS Reporter: Matt Wringe Assigned To: Chris Laprun Attachments: server_output.txt When the server is started and the portal-wsrp.sar is located within the deploy directory, the portal cannot cannot load the 'self' wsrp producer. This is due to the portal trying to reference the 'self' producer before 'self' has been bound to the jndi. 15:40:14,739 INFO [WSRPDeploymentFactory] Added consumer for producer 'self' 15:40:14,956 ERROR [STDERR] org.jboss.portal.portlet.InvokerUnavailableException: Problem getting service description for producer self 15:40:14,957 ERROR [STDERR] at org.jboss.portal.wsrp.consumer.ProducerInfo.getServiceDescription(ProducerInfo.java:444) ... 15:40:15,226 ERROR [STDERR] Caused by: javax.naming.NameNotFoundException: wsrp-client not bound 15:40:15,226 ERROR [STDERR] at org.jnp.server.NamingServer.getBinding(NamingServer.java:529) ... Soon after this step, 'self' becomes bound: 15:40:33,666 INFO [ClientDeployer] Client ENC bound under: wsrp-client Note: if the wsrp-portal.sar is hot deployed after the server has started, then it will load the producer successfully. -- 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

16 years, 3 months

7
11
0 / 0

[JBoss JIRA] Created: (JGRP-376) TLS: use priority based queue rather than BoundedLinkedQueue for default thread pool

by Bela Ban (JIRA)

TLS: use priority based queue rather than BoundedLinkedQueue for default thread pool ------------------------------------------------------------------------------------ Key: JGRP-376 URL: http://jira.jboss.com/jira/browse/JGRP-376 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 This will allow us to dispatch incoming messages to threads from the pool based on criteria. - The impl implements interface BoundedChannel - It has N queues, 1 for each sender (possibly those are BoundedLinkedQueues) - There is a max size in bytes for the priority queue, each internal queue has max_size / N bytes where N = number of members. This is dynamically adjusted ADDITION - An internal queue maintains the number of bytes (Message.length()), an offer() or put() increases that amount by the size of the message, a take() or poll() decreases the amount. When a put() or offer() would exceed the max amount, it will block until a take() or poll() decreases it such that the new message can be added to the queue. We might also discard messages to full queues, or implement somthing akin to RED (random early detection), which starts discarding messages *before* the queue is full REMOVAL - Strategy pluggable, e.g. - Take from the fullest queue - Take from the least full queue - Round robin - Weighted round robin (weighted by capacity of each queue), e.g. take relative to capacity from each queue. Example: Queues A (2MB), B (2MB), C (6MB): we take 2 from A, 2 from B and 6 from C - Random robin etc -- 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

16 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (JGRP-381) TLS: all queues for thread pools should use number of bytes rather than number of messages

by Bela Ban (JIRA)

TLS: all queues for thread pools should use number of bytes rather than number of messages ------------------------------------------------------------------------------------------ Key: JGRP-381 URL: http://jira.jboss.com/jira/browse/JGRP-381 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 Instead of defining a max number of elements in a queue BoundedBlockingQueue (used by thread pool), we define a number of bytes. If that number is exceeded, we block on put()/offer(), and only unblock if a take() has removed N number of bytes so we can add our message without exceeding the limit -- 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

16 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-933) NPE when deploying web service beans

by Heiko Braun (JIRA)

NPE when deploying web service beans ------------------------------------ Key: EJBTHREE-933 URL: http://jira.jboss.com/jira/browse/EJBTHREE-933 Project: EJB 3.0 Issue Type: Bug Reporter: Heiko Braun The exception: java.lang.NullPointerException at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.getInterfaces(StatelessRemoteProxyFactory.java:74) at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.init(BaseStatelessProxyFactory.java:172) at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.init(StatelessRemoteProxyFactory.java:100) at org.jboss.ejb3.stateless.BaseStatelessProxyFactory.start(BaseStatelessProxyFactory.java:221) at org.jboss.ejb3.stateless.StatelessRemoteProxyFactory.start(StatelessRemoteProxyFactory.java:107) at org.jboss.ejb3.ProxyDeployer.start(ProxyDeployer.java:83) at org.jboss.ejb3.SessionContainer.start(SessionContainer.java:124) at org.jboss.ejb3.stateless.StatelessContainer.start(StatelessContainer.java:94) The bean that get's deployed: package com.sun.ts.tests.webservices12.ejb.annotations.WSEjbPortFieldInjectionTest; import javax.ejb.Stateless; import javax.jws.WebService; @WebService( portName="Hello", serviceName="HelloService", targetNamespace="http://Hello.org", wsdlLocation="META-INF/wsdl/HelloService.wsdl", endpointInterface="com.sun.ts.tests.webservices12.ejb.annotations.WSEjbPortFieldInjectionTest.Hello") @Stateless(name="WSEjbPortFieldInjectionTest") public class HelloBean { public String hello(String str) { return "WebSvcTest-Hello " + str; } public String bye(String str) { return "WebSvcTest-Bye and take care " + str; } } The spec: Session bean's business interface(s), if the session bean provides an EJB 3.0 local or remote client view. -- 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

16 years, 3 months

5
11
0 / 0

[JBoss JIRA] Created: (EJBTHREE-670) PreDestroy called multiple times

by Carlo de Wolf (JIRA)

PreDestroy called multiple times -------------------------------- Key: EJBTHREE-670 URL: http://jira.jboss.com/jira/browse/EJBTHREE-670 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf The PreDestroy callback is called multiple times. Once from the container and once from the pool. IMHO only the pool should call PreDestroy. Other callbacks are already handled by the pool. Unit test is in regression/ejbthree... -- 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

16 years, 3 months

3
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-969) Temporary Queues exposed via jmx

by Markus Kobler (JIRA)

Temporary Queues exposed via jmx --------------------------------- Key: JBMESSAGING-969 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-969 Project: JBoss Messaging Issue Type: Feature Request Components: Messaging Core Reporter: Markus Kobler Assigned To: Tim Fox Priority: Minor Would be helpful if Temporary Queues were exposed via jmx in the same way configured Queues and Topics are. -- 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

16 years, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (JBRULES-401) add ability to lock a node to prevent concurrent editing

by Michael Neale (JIRA)

add ability to lock a node to prevent concurrent editing -------------------------------------------------------- Key: JBRULES-401 URL: http://jira.jboss.com/jira/browse/JBRULES-401 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale For ben -- 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

16 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAOP-383) Document isntrumentation modes

by Flavia Rainone (JIRA)

Document isntrumentation modes ------------------------------ Key: JBAOP-383 URL: http://jira.jboss.com/jira/browse/JBAOP-383 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Flavia Rainone Fix For: 2.0.0.alpha5 We need to document instrumentation modes. -- 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

16 years, 4 months

2
14
0 / 0

[JBoss JIRA] Created: (JBAS-3544) org.jboss.test.management.test.DeploymentDescriptorUnitTestCase fails bcasue service modules are unavailable

by Jaroslaw Kijanowski (JIRA)

org.jboss.test.management.test.DeploymentDescriptorUnitTestCase fails bcasue service modules are unavailable ------------------------------------------------------------------------------------------------------------ Key: JBAS-3544 URL: http://jira.jboss.com/jira/browse/JBAS-3544 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Environment: win xp Reporter: Jaroslaw Kijanowski Fix For: JBossAS-5.0.0.Beta org.jboss.test.management.test.DeploymentDescriptorUnitTestCase fails because the services jbossweb-tomcat55.sar and jboss-aop.deployer can't be registered, becasue in JB5.0 they changed their names to jbossweb-tomcat6.sar and jboss-aop-jdk50.deployer. FIX: change testsuite/src/main/org/jboss/test/management/test/DeploymentDescriptorUnitTestCase.java . . . public void testGetSarDescriptor() throws Exception { // String moduleName = "jbossweb-tomcat55.sar"; String moduleName = "jbossweb-tomcat6.sar"; . . . public void testGetDeployerDescriptor() throws Exception { // String moduleName = "jboss-aop.deployer"; String moduleName = "jboss-aop-jdk50.deployer"; -- 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

16 years, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-4410) JaasSecurityDomain settings need to be sent to SecurityConfiguration

by Anil Saldhana (JIRA)

JaasSecurityDomain settings need to be sent to SecurityConfiguration -------------------------------------------------------------------- Key: JBAS-4410 URL: http://jira.jboss.com/jira/browse/JBAS-4410 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Anil Saldhana Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.Beta3 SECURITY-26 has a need for the MBean services and other security related integration aspects for the JBAS to get back into the AS workspace. I see an issue with the Ldapxxx login modules having a reliance on the DecodeAction privileged action, that internally used to call the JaasSecurityDomain mbean service to decode a b64 string. Now since the JaasSecurityDomain mbean service was the central source of the various jsse/crypto settings, we need to get away from this model and use the static SecurityConfiguration as the sink for the security settings. This static SecurityConfiguration can be populated from JaasSecurityDomain Mbean service, the security deployer or wherever. There certainly has to be a better way than the static SecuriytConfiguration. For now, it is sufficient. -- 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

16 years, 4 months

2
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2007