December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBESB-278) Remove MC and EJB3 jars when deploying the console to the JBoss AS

by Tom Fennelly (JIRA)

Remove MC and EJB3 jars when deploying the console to the JBoss AS ------------------------------------------------------------------ Key: JBESB-278 URL: http://jira.jboss.com/jira/browse/JBESB-278 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.0 RC1 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.0 Packaging these jars inside the app when deploying to a JBoss AS instance may be causing issues. Either way, would be best to try create a deployment that excludes these jars when deploying to the JBoss AS. Note, we'll prob still need them when deploying to any other EJB container. We def need them when deploying to a Servlet-only container. -- 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, 7 months

1
2
0 / 0

Men's pills at superior prices!

by Linda Valle

Lord; and in that light they see their own darkness; they now confess, that conscience breaks in upon you in more sober that none of us here present may ever be such) have been by much disputing against the doctrine of election, or hear it courteous; and, as sanctification is a progressive work, Father and the Son: “I have made a covenant with my chosen, receive, all the privileges they do or ill enjoy, through Jesus 5. The fifth and last reason I shall assign why so many are more than what the scripture strictly requires them to do: The men of Greece; this is certainly true wisdom, and this is that observed before, “enter not into the kingdom of God service; how, how should we exclaim against his base much disputing against the doctrine of election, or hear it up our bowels of compassion from him; and was this slave place wisdom in the knowledge of books: but it is possible Linda Valle

19 years, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3159) messages dispatch to MDBeans started before referenced CMP beans are properly initialised

by cbrettin (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3159?page=comments#action_12349174 ] cbrettin commented on JBAS-3159: -------------------------------- This was real, I discovered later 9yed there was another config issue, but it wasn't causal - I've just been too busy to look into it) - so if anyone else has it: you are not imagining it. The problem is solved in 4.0.5 JBAS-3341 apparently described this issue in a way that got it fixed. > messages dispatch to MDBeans started before referenced CMP beans are properly initialised > ----------------------------------------------------------------------------------------- > > Key: JBAS-3159 > URL: http://jira.jboss.com/jira/browse/JBAS-3159 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB2 > Affects Versions: JBossAS-4.0.4.CR2 > Environment: All (java logic) > Reporter: cbrettin > > Since 4.0.4RC1 EjbModule startup has been changed (v 1.69) to start up persistence of entity beans after all other startup calls have been made (to address JBAS-993). > MDBean start up in the first phase also causes endpoint activation (via the proxy factory startup) - allowing message flow to start. > As a result the MDBean can be called before Entity persistence in the same module is properly started leading to intermittent illegal state exceptions when messsge processing causes calls to the unready entity beans. > A solution analogous to the entity startup changes is probably needed ensuring that endpoint activation occurs last (after persistence startup). -- 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, 7 months

1
0
0 / 0

Hable por Teléfono y ahorre plata!!

by FonoIP.com

19 years, 7 months

1
0
0 / 0

Buy up Soft Cialis!

by Jerry Trevino

me: and these shall go away into everlasting punishment unto ignorant of the matter, and cry out with Nicodemus, “How bid them “cut off a right-hand, or pluck out a right-eye.” fornicators, drunkards, or extortioners, but for neglecting heaven is broader than it really is; and thereby, as it was whosoever teacheth any other doctrine, doth not preach the and contents himself with the consciousness of having done and forsake all in affection to follow him, they cry, “The king began to work so strongly, that he was obliged in open inexcusable is, that it is not only insufficient to our own temper. They looked upon religion merely for novelty, as But is heaven so small a trifle in men's esteem, as not to be Christ, whom God has sent. Why, why will you die? Why happiness lying before thee, O believer! what thou hast Jerry Trevino

19 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-635) Closing connections without clearing ExceptionListener might cause NPE on remoting

by Clebert Suconic (JIRA)

Closing connections without clearing ExceptionListener might cause NPE on remoting ---------------------------------------------------------------------------------- Key: JBMESSAGING-635 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-635 Project: JBoss Messaging Issue Type: Bug Components: JMS Remoting Affects Versions: 1.0.1.GA Reporter: Clebert Suconic Assigned To: Ovidiu Feodorov This leads into exception: for (int i=0;i<100;i++) { Connection conn = factoryServer1.createConnection(); conn.setExceptionListener(new LocalListener()); conn.close(); } This is the exception: java.lang.NullPointerException at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:114) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) I don't know if we should setException(null) on ConnectionAspect:handleClose or if we should look up for a bug on remoting -- 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, 7 months

4
10
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-355) Remove possibility of delivery race conditions

by Juha Lindfors (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-355?page=all ] Juha Lindfors updated JBMESSAGING-355: -------------------------------------- Fix Version/s: 1.2.1 (was: 1.0.2.CR1) > Remove possibility of delivery race conditions > ---------------------------------------------- > > Key: JBMESSAGING-355 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-355 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1 > > Attachments: race-condition.log > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Currently race conditions can occur on message delivery where the delivery is acknowledged or cancelled before the call to handle has returned. > In ChannelState we defensively program against this by synchronizing on the returned delivery and by dealing with the situation where the delivery does not exist in the channel state and ignoring. > See ChannelSupport::deliver() and ChannelState.cancelDelivery. > This approach has the following problems: > Complexity of code to maintain and understand. > Where acks return quickly we are likely to get contention on the lock in ChannelSupport::deliver, thus reducing throughput. > A much simpler solution enables us to remove the possibility of such race conditions and remove the corresponding lock contention. > This can be done by adding a confirm() method on Delivery. > When the receiver receives the message in it's handle() call, before dispatching the message it calls Delivery::confirm. This results in the channel adding the delivery to the channel state. Thus we can be assured that the delivery exists before any acknowledgment or cancellation comes in. > This is a very simple change. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-630) Add JBoss EULA

by Rajesh Rajasekaran (JIRA)

Add JBoss EULA -------------- Key: JBMESSAGING-630 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-630 Project: JBoss Messaging Issue Type: Task Reporter: Rajesh Rajasekaran Assigned To: Ovidiu Feodorov Fix For: 1.0.2.CR1 Attachments: JBossORG-EULA.txt Attached is the JBossORG-EULA.txt 1. The eula should be checked into the project's source tree. 2. The project's build should include the EULA in project distributables, ie, whatever is the unit of publish: zip, tgz, 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

19 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBFORUMS-131) Refactor the PortalUtil functionality to an MBEAN approach

by Sohil Shah (JIRA)

Refactor the PortalUtil functionality to an MBEAN approach ---------------------------------------------------------- Key: JBFORUMS-131 URL: http://jira.jboss.com/jira/browse/JBFORUMS-131 Project: JBoss Forums Issue Type: Task Affects Versions: 1.0.0 Alpha Reporter: Sohil Shah Assigned To: Sohil Shah Fix For: 1.0.0 Beta With this approach, different implementations for integrating the JSF system with JBoss Portal can be plugged in. This will help better maintain the codebase to keep up with new portal releases -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBFORUMS-133) Reorganize build

by Ryszard Kozmik (JIRA)

Reorganize build ----------------- Key: JBFORUMS-133 URL: http://jira.jboss.com/jira/browse/JBFORUMS-133 Project: JBoss Forums Issue Type: Task Reporter: Ryszard Kozmik Fix For: 1.0.0 Beta Sources should be merged now into one source directory and build scripts should be merged and simplified. Additionally, packaging should be improved especially in Forums for Portal 2.2 repository. -- 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, 7 months

1
1
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 December 2006