July 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBEE-12) getRequestCookieMap() only contains sessionid

by Florian Scandella (JIRA)

getRequestCookieMap() only contains sessionid --------------------------------------------- Key: JBEE-12 URL: https://jira.jboss.org/jira/browse/JBEE-12 Project: JBoss JavaEE APIs Issue Type: Bug Components: Servlet API Affects Versions: 5.0.1.GA Environment: gentoo/linux x86_64, icedtea 1.4.1, seam 2.1.1GA, jboss 5.0.1GA java 1.6 build Reporter: Florian Scandella Assignee: Shelly McGowan i store some cookies on the client. the cookie gets transmitted by the browser (checked with firebug) but does not end up in externalcontext.getRequestCookieMap(). this map only contains the JSESSIONID. -- 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

15 years, 8 months

4
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1074) Circular @EJB3 references in session beans fail to deploy.

by Gunnar Grim (JIRA)

Circular @EJB3 references in session beans fail to deploy. ---------------------------------------------------------- Key: EJBTHREE-1074 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1074 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.1.GA Reporter: Gunnar Grim The following circular references makes the application undeployable: In ArchiveBrokerBean: @EJB private SeriesBrokerLocal itsSeriesBroker; In SeriesBrokerBean @EJB private ArchiveBrokerLocal itsArchiveBroker; Circular references like these work fine in Glassfish but JBoss shows the following error message: ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3 State: NOTYETINSTALLED I Depend On: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3 jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveTypeBroker,service=EJB3 persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU Depends On Me: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveOrigBroker,service=EJB3 jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3 ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveOrigBroker,service=EJB3 State: NOTYETINSTALLED I Depend On: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3 persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3 State: NOTYETINSTALLED I Depend On: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3 persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU Depends On Me: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=ArchiveBroker,service=EJB3 jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=VolumeBroker,service=EJB3 ObjectName: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=VolumeBroker,service=EJB3 State: NOTYETINSTALLED I Depend On: jboss.j2ee:ear=klara5.ear,jar=klara5.jar,name=SeriesBroker,service=EJB3 persistence.units:ear=klara5.ear,jar=klara5.jar,unitName=KlaraPU -- 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

15 years, 8 months

10
11
0 / 0

[JBoss JIRA] Created: (JGRP-747) RELAY: replication between data centers

by Bela Ban (JIRA)

RELAY: replication between data centers --------------------------------------- Key: JGRP-747 URL: http://jira.jboss.com/jira/browse/JGRP-747 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.x [from JGroups/doc/design/DataCenterReplication.txt] Replication between data centers ================================ Author: Bela Ban Version: $Id: DataCenterReplication.txt,v 1.6 2008/04/25 15:54:30 belaban Exp $ We have data centers in New York (NYC) and San Francisco (SFO). The idea is to replicate traffic from NYC to SFO asynchronously. In case of a site failure of NYC, all clients can be switched over to SFO and continue working with (almost) up-to-date data. The failing over of clients to SFO is outside the scope of this proposal, and could be done for example by changing DNS entries, load balancers etc. There is no replication going on from SFO to NYC by default, only when SFO becomes the primary site. The assumption is that there is no message between data centers which requires a response. This would require NAT functionlity, which we may provide in a future version. For the example, we assume that each site uses a UDP based stack, and replication between the sites use a TCP based stack, see figure DataCenterReplication.png. There is a local cluster, based on UDP, at each site and one global cluster, based on TCP, which connects the two sites. Each coordinator of the local cluster is also a member of the global cluster, e.g. member E in NYC (assuming it is the coordinator) is also member X of the TCP cluster. This is called a *relay* member. A relay member is always member of the local and global cluster. A relay member has a UDP stack which additionally contains a protocol RELAY at the top (shown in the bottom part of the figure). RELAY has a JChannel which connects to the TCP group, but *only* when it is (or becomes) coordinator of the local cluster. The configuration of the TCP channel is done via a property in RELAY. Any *multicast* message (we don't relay unicast messages) that is received by RELAY traveling up the stack is sent via the TCP channel to the other site. When received there, the corresponding RELAY protocol changes the destination of the message to null (those are multicast messages after all) and leaves the src (which might point to X if sent from NYC), then it sends the message down the stack, where it will get multicast to all members of the local cluster (including the sender). When a response is received which points to any non-local address (e.g. X), RELAY simply drops it. When forwarding a message to the local cluster, RELAY adds a header. When it receives the multicast message it forwarded itself, and a header is present, it does *not* relay it back to the other site but simply drops it. Otherwise, we would have a cycle. When a coordinator crashes or leaves, the next-in-line becomes coordinator and activates the RELAY protocol, connecting to the TCP channel and starting to relay messages. However, if we receive messages from the local cluster while the coordinator has crashed and the new one hasn't taken over yet, we'd lose messages. Therefore, we need additional functionality in RELAY which buffers the last N messages (or M bytes, or for T seconds) and numbers all messages sent. This is done by the second-in-line. When there is a coordinator failover, the new coordinator communicates briefly with the other site to determine which was the highest message relayed by it. It then forwards buffered messages with lower numbers and removes the remaining messages in the buffer. During this replay, message relaying is suspended. Therefore, a relay has to handle 3 types of messages from the global (TCP) cluster: (1) Regular multicast messages (2) A message asking for the highest sequence number received from another relay, and the response to this (3) A message stating that the other side will go down gracefully (no need to replay buffered messages) Example walkthrough ------------------- - C (in the NYC cluster, with coordinator E) multicasts a message - A, B, C, D and E receive the multicast - D (second-in-line) buffer the message (bounded buffer) - E is the relay. The byte buffer is extracted and a new message M is created. M's source is C, the dest is null (= send to all). Note that the original headers are *not* sent with M. If this is needed, we need to revisit. - X receives M, drops it (because it is the sender, determined by the header). - Y receives M, adds a RELAY header and sends it down the stack - T, U, V, W and S receive M and deliver it - Y does not relay M because M has a header - Should some member reply (to X), then RELAY at Y will drop the message -- 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

15 years, 8 months

1
8
0 / 0

[JBoss JIRA] Created: (SECURITY-136) jboss-web defined authenticators in JBoss 4.2.x?

by Darran Lofthouse (JIRA)

jboss-web defined authenticators in JBoss 4.2.x? ------------------------------------------------ Key: SECURITY-136 URL: http://jira.jboss.com/jira/browse/SECURITY-136 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assigned To: Darran Lofthouse -- 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

15 years, 8 months

1
6
0 / 0

[JBoss JIRA] Created: (SECURITY-358) Make logging configurable with JBoss 4.0.5.GA

by Darran Lofthouse (JIRA)

Make logging configurable with JBoss 4.0.5.GA --------------------------------------------- Key: SECURITY-358 URL: https://jira.jboss.org/jira/browse/SECURITY-358 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Affects Versions: Negotiation_2.0.3.GA Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Optional Fix For: Negotiation_2.0.4.GA If possible make the logging compatible with JBoss 4.0.5.GA to allow JBoss Negotation to be deployed on this AS version. -- 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

15 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1073) SessionContext.getBusinessObject(...) throws IllegalStateException on @Service EJB

by Michael McKibben (JIRA)

SessionContext.getBusinessObject(...) throws IllegalStateException on @Service EJB ---------------------------------------------------------------------------------- Key: EJBTHREE-1073 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1073 Project: EJB 3.0 Issue Type: Bug Components: EJB3 Extensions Affects Versions: AS 4.2.1.GA Reporter: Michael McKibben Calling SessionContext.getBusinessObject(...) throws an IllegalStateException within a @Service EJB. This should behave like a Stateless/Stateful EJB no? -- 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

15 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-6994) Improve developer javadoc

by Thomas Diesler (JIRA)

Improve developer javadoc ------------------------- Key: JBAS-6994 URL: https://jira.jboss.org/jira/browse/JBAS-6994 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Thomas Diesler Fix For: JBossAS-6.0.0.Alpha1 -- 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

15 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1800) SNAPSHOT versions should have a version suffix of -SNAPSHOT instead of .SNAPSHOT

by Geoffrey De Smet (JIRA)

SNAPSHOT versions should have a version suffix of -SNAPSHOT instead of .SNAPSHOT -------------------------------------------------------------------------------- Key: JBRULES-1800 URL: https://jira.jboss.org/jira/browse/JBRULES-1800 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: All Affects Versions: 5.0.0.M2 Reporter: Geoffrey De Smet Assignee: Mark Proctor Priority: Minor Fix For: 5.0.0.M3 It causes problems, because maven doesn't recognize it as a snapshot, it's just a fake snapshot: - sources aren't downloaded for "mvn eclipse:eclipse", etc Mark told me he uses .SNAPSHOT intentionally, as a hack for building the drools eclipse plugin, but is that still necessary? What is the problem with using -SNAPSHOT there exactly and can we solve it another way? :) -- 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

15 years, 9 months

4
10
0 / 0

[JBoss JIRA] Created: (JBMETA-117) Prohibit bindings is there isn't a corresponding business interface

by Andrew Lee Rubinger (JIRA)

Prohibit bindings is there isn't a corresponding business interface ------------------------------------------------------------------- Key: JBMETA-117 URL: https://jira.jboss.org/jira/browse/JBMETA-117 Project: JBoss Metadata Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 1.0.0.CR2 The following 2 constructs should throw an informative error to the bean provider: @Stateless @Remote(MyRemote.class) @LocalBinding(jndiBinding="Whatever") // There's no local business interface public class MyBean implements MyRemote{...} @Stateless @Local(MyLocal.class) @RemoteBinding(jndiBinding="Whatever") // There's no remote business interface public class MyBean implements MyLocal{...} -- 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

15 years, 9 months

2
16
0 / 0

[JBoss JIRA] Created: (JBAS-6528) MDB - Failed to acquire the pool semaphore

by David Goodman (JIRA)

MDB - Failed to acquire the pool semaphore ------------------------------------------ Key: JBAS-6528 URL: https://jira.jboss.org/jira/browse/JBAS-6528 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.2.GA Environment: JBoss 4.2.2 + ActiveMQ 5.1.0 on RedHat Linux Reporter: David Goodman See linked issue JBAS-1599. The original bug was for SLSB, but it still affects MDBs. We have three MDBs configured with the following activation spec: @MessageDriven(activationConfig = { @ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Queue"), @ActivationConfigProperty(propertyName="maximumRedeliveries", propertyValue="0"), @ActivationConfigProperty(propertyName="acknowledgeMode", propertyValue="Auto-acknowledge") }) @Depends({"bluecrest.azzurro:service=AzzurroAppManager"}) @ResourceAdapter("activemq-rar.rar") @PoolClass (value=org.jboss.ejb3.StrictMaxPool.class, maxSize=1, timeout=30000) public class StatusMessageMDB implements MessageListener{ ... } All three MDBs have different names, and listen on different queues, but they are configured the same. In the PoolClass annotation, we are using a maxSize of 1 in an attempt to force processing of messages in the order they were loaded on the queue. We loaded two of the queues with 500 messages each. One queue processes 2-3 messages per second, we will call this the "fast" queue. The other queue, the "slow" queue, takes about 5 seconds per message. The slow queue threw the following exception 5 times during the period of time both queues were loaded with messages. Curiously, the slow queue did not seem to throw this exception once the fast queue had finished its 500 messages. 2009-02-19 11:19:47,470 ERROR [ActiveMQSession] error dispatching message: javax.ejb.EJBException: Failed to acquire the pool semaphore, strictTimeout=30000 at org.jboss.ejb3.StrictMaxPool.get(StrictMaxPool.java:122) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:54) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138) at $Proxy235.onMessage(Unknown Source) at org.apache.activemq.ra.MessageEndpointProxy$MessageEndpointAlive.onMessage(MessageEndpointProxy.java:116) at org.apache.activemq.ra.MessageEndpointProxy.onMessage(MessageEndpointProxy.java:59) at org.apache.activemq.ActiveMQSession.run(ActiveMQSession.java:695) at org.apache.activemq.ra.ServerSessionImpl.run(ServerSessionImpl.java:165) at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204) at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756) at java.lang.Thread.run(Thread.java:595) I am posting this bug report here because in the comments field of JBAS-1599 there were a couple of other people who had a similar issue with MDBs and the StrictMaxPool. -- 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

15 years, 9 months

3
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 July 2009