March 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1527) Allow delivery to be paused/resumed on queues

by Tim Fox (JIRA)

Allow delivery to be paused/resumed on queues --------------------------------------------- Key: JBMESSAGING-1527 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1527 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assignee: Tim Fox Fix For: 2.1.0.beta We should allow users to be able to suspend/resume delivery to consumers on a queue. In effect "stall" the queue. -- 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1524) Send message to multiple addresses

by Tim Fox (JIRA)

Send message to multiple addresses ---------------------------------- Key: JBMESSAGING-1524 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1524 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assignee: Tim Fox Fix For: 2.1.0.beta We should allow the user to be able to specify a comma delimited list of addresses when sending a message. The message then gets sent to all those addresses. -- 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1523) Exponential backoff on redelivery

by Tim Fox (JIRA)

Exponential backoff on redelivery --------------------------------- Key: JBMESSAGING-1523 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1523 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assignee: Tim Fox Fix For: 2.1.0.beta -- 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1521) JBM peer to peer mode / serverless mode / disconnect mode

by Tim Fox (JIRA)

JBM peer to peer mode / serverless mode / disconnect mode --------------------------------------------------------- Key: JBMESSAGING-1521 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1521 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assignee: Tim Fox Fix For: 2.1.0.beta We should provide functionality for JBM to run in peer-to-peer or serverless mode. This basically means you have a server that automatically starts at the client side, which then clusters with other clients (servers) using ClusterConnections. We can have special ClientSessionFactory impl constructors we create such a client. all client requests are fielded at the local server. A variation on this is to run the a disconnected server on the client, connected transparenty to the real server via a bridge. -- 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-6561) Regression: MTTransactionManagerUnitTestCase.testCommitSameTxInTwoThreads() fails

by Jason T. Greene (JIRA)

Regression: MTTransactionManagerUnitTestCase.testCommitSameTxInTwoThreads() fails --------------------------------------------------------------------------------- Key: JBAS-6561 URL: https://jira.jboss.org/jira/browse/JBAS-6561 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Jason T. Greene Assignee: Jonathan Halliday Fix For: JBossAS-5.1.0.Beta1 One of the TM tests in the AS fails due to what it perceives as a spec compliance failure. However, I am not sure the test requires is correct. The test starts a transaction using TransactionManager in thread 0 and then commits the transaction in thread 1. Thread 0 then calls tm.commit(), and it expects an IllegalStateException because the test does not think the transaction should be associated with Thread 0 at this point. The spec doesn't seem to say anything about Transaction.commit() causing other threads to unassociate themselves with the Transaction. Is the test wrong? -- 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

17 years, 3 months

1
6
0 / 0

[JBoss JIRA] Created: (JBAS-6563) EJB3 container does not honour security annotations

by Karel Gardas (JIRA)

EJB3 container does not honour security annotations --------------------------------------------------- Key: JBAS-6563 URL: https://jira.jboss.org/jira/browse/JBAS-6563 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-4.2.3.GA Environment: Sun OS 5.11 snv_79a, Sun jdk 1.6, JBoss 4.2.3 for JDK 1.6, Eclipse Ganymede Reporter: Karel Gardas Assignee: Anil Saldhana Hello, I'm using the following code as a testcase for EJB3-WS security. package demo; import javax.annotation.security.RolesAllowed; import javax.annotation.security.DenyAll; import javax.ejb.Stateless; import javax.jws.WebService; @WebService @Stateless //@RolesAllowed ("Person") public class HelloBean3 { public HelloBean3() { } @DenyAll public String sayHello() { return "EJB3x: Hello my callee!"; } } unfortunately when it's deployed to the JBoss 4.2.3 AS, it does not deny any requests to sayHello operation, but runs them happily. I'm using web service client developed in Eclipse using Axis: package demo; public class Main { public static void main(String[] args) throws Exception { // TODO Auto-generated method stub HelloBean3ServiceLocator loc = new HelloBean3ServiceLocator(); HelloBean3 hello = loc.getHelloBean3Port(); System.out.println("service tells me: `" + hello.sayHello() + "'"); } } -- 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-910) Shared transport: 'members' variable incorrect (remove from TP ?)

by Bela Ban (JIRA)

Shared transport: 'members' variable incorrect (remove from TP ?) ----------------------------------------------------------------- Key: JGRP-910 URL: https://jira.jboss.org/jira/browse/JGRP-910 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.8 TP.members is the union of all views received on *all* channels. This is incorrect, and sendToAllMembers() iterating over 'members' would unnecessarily send messages to members in a different cluster ! (these would get dropped, but it is still spurious traffic) Logically, 'members' belongs to a cluster, so maybe we ahould should have a table of cluster names and views in TP ? -- 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

17 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBXB-186) UnorderedSequenceBinding: CCE when getElement() is called for WildcardBinding

by Alexey Loubyansky (JIRA)

UnorderedSequenceBinding: CCE when getElement() is called for WildcardBinding ----------------------------------------------------------------------------- Key: JBXB-186 URL: https://jira.jboss.org/jira/browse/JBXB-186 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Affects Versions: JBossXB-2.0.1.Beta2 Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: JBossXB-2.0.1.CR1 The term of the current particle should be checked in getElement() before casting to ElementBinding. -- 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

17 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-168) Simplify access to underlying ControllerContext name

by Ales Justin (JIRA)

Simplify access to underlying ControllerContext name ---------------------------------------------------- Key: JBDEPLOY-168 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-168 Project: JBoss Deployers Issue Type: Feature Request Components: deployer Affects Versions: JBDEPLOY-2.0.5.GA Reporter: Ales Justin Assignee: Ales Justin Fix For: JBDEPLOY-2.2.0.Alpha DeploymentUnit api should have a getControllerContext method. This would simplify dependency handling within deployers - see DependenciesMetaDataDeployer. -- 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

17 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1989) Unable to remove rule flows in Guvnor

by Brian Cribbs (JIRA)

Unable to remove rule flows in Guvnor ------------------------------------- Key: JBRULES-1989 URL: https://jira.jboss.org/jira/browse/JBRULES-1989 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-guvnor Affects Versions: 5.0.0.M5 Reporter: Brian Cribbs Assignee: Mark Proctor I tried to archive (remove) a rule flow in Guvnor and I got an error saying that "the call failed on the server. please check the server logs". The following was output in the log. 2009-03-02 09:07:22,515 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/drools-guvnor]] Exception while dispatching incoming RPC call com.google.gwt.user.server.rpc.UnexpectedException: Service method 'public abstract java.lang.String org.drools.guvnor.client.rpc.RepositoryService.checkinVersion(org.drools.guvnor.client.rpc.RuleAsset) throws com.google.gwt.user.client.rpc.SerializableException' threw an unexpected exception: java.lang.NullPointerException at com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:360) at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:546) at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:164) at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost(RemoteServiceServlet.java:86) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.web.ContextFilter$1.process(ContextFilter.java:42) at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:53) at org.jboss.seam.web.ContextFilter.doFilter(ContextFilter.java:37) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.NullPointerException at org.drools.guvnor.server.contenthandler.RuleFlowHandler.storeAssetContent(RuleFlowHandler.java:89) at org.drools.guvnor.server.ServiceImplementation.checkinVersion(ServiceImplementation.java:611) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:28) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:77) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.security.SecurityInterceptor.aroundInvoke(SecurityInterceptor.java:157) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166) at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102) at org.drools.guvnor.server.ServiceImplementation_$$_javassist_7.checkinVersion(ServiceImplementation_$$_javassist_7.java) at org.drools.guvnor.server.RepositoryServiceServlet.checkinVersion(RepositoryServiceServlet.java:126) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:527) ... 27 more -- 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

17 years, 3 months

2
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 March 2009