March 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-928) Make JBossRemoting v2.2.2.SP2 available for download

by Tom Fennelly (JIRA)

Make JBossRemoting v2.2.2.SP2 available for download ---------------------------------------------------- Key: JBREM-928 URL: http://jira.jboss.com/jira/browse/JBREM-928 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Fennelly JBossESB v4.2.1.CP1 has a dependency on JBossRemoting v2.2.2.SP2 (because it's in line with SOA-P, which depends on v2.2.2.SP2). When deploying the JBossESB v4.2.1.CP1 on JBoss AS v4.2.1.GA , the AS needs to be patched with JBossRemoting v2.2.2.SP2, but there's no download available for this on JBossRemoting downloads. Can we make a distro for this version available for download? -- 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

18 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-444) RequestCorrelator does not respect FLUSH.FlushHeader.BYPASS_FLUSH

by Michael Newcomb (JIRA)

RequestCorrelator does not respect FLUSH.FlushHeader.BYPASS_FLUSH ----------------------------------------------------------------- Key: JGRP-444 URL: http://jira.jboss.com/jira/browse/JGRP-444 Project: JGroups Issue Type: Bug Affects Versions: 2.5 Environment: 2.5 alpha 2 Reporter: Michael Newcomb Assigned To: Bela Ban private void handleRequest(Message req, Header hdr) { ... rsp=req.makeReply(); if(rsp_buf != null) rsp.setBuffer(rsp_buf); rsp_hdr=new Header(Header.RSP, hdr.id, false, name); rsp.putHeader(name, rsp_hdr); // *************** patch ***************** // can't check for FLUSH.FlushHeader.BYPASS_FLUSH because it has package protection, so just check for FLUSH header // if (req.getHeader(org.jgroups.protocols.pbcast.FLUSH.NAME) != null) { rsp.putHeader(org.jgroups.protocols.pbcast.FLUSH.NAME, new org.jgroups.protocols.pbcast.FLUSH.FlushHeader(org.jgroups.protocols.pbcast.FLUSH.FlushHeader.FLUSH_BYPASS)); } // *************** patch ***************** if(log.isTraceEnabled()) log.trace(new StringBuffer("sending rsp for ").append(rsp_hdr.id).append(" to ").append(rsp.getDest())); ... } -- 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

18 years, 4 months

3
10
0 / 0

[JBoss JIRA] Created: (JBAS-4242) Port Hibernate depoyer to VDF

by Scott M Stark (JIRA)

Port Hibernate depoyer to VDF ----------------------------- Key: JBAS-4242 URL: http://jira.jboss.com/jira/browse/JBAS-4242 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Deployment services, Hibernate service Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Scott M Stark Assigned To: Steve Ebersole Fix For: JBossAS-5.0.0.Beta3 The current hibernate integration tests are broken in jboss5 trunk, and the deployer needs to be ported to the VDF (http://wiki.jboss.org/wiki/Wiki.jsp?page=JBoss5DeploymentFramework). This really should be done in concert with the ejb3 deployer refactoring as there should be minimal duplication of the various deployment aspects related to persistence. -- 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

18 years, 4 months

4
7
0 / 0

[JBoss JIRA] Created: (JBRULES-1506) RuleAgent will not read binary packages from Apache HTTP Server

by David Stringer (JIRA)

RuleAgent will not read binary packages from Apache HTTP Server --------------------------------------------------------------- Key: JBRULES-1506 URL: http://jira.jboss.com/jira/browse/JBRULES-1506 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: All Affects Versions: 4.0.4 Environment: Rules Package is stored in SVN, accessed through Apache 2.0.52 Rules Agent is running within WAR on Jboss 4.0.5, Java 1.6 Both Servers are running on Cent-OS 4 Reporter: David Stringer Assigned To: Mark Proctor Hi, We were hoping to deploy our rules packages in SVN fronted by Apache 2.0.52. The rule agent fails when trying to load the URI that resolves into the repository.. Exception is as follows: 2008-03-14 11:46:08,270 ERROR [STDERR] RuleAgent(MyConfig) INFO (Fri Mar 14 11:46:08 PDT 2008): Configuring package provider : URLScanner monitoring URLs: http://vconfig.dev.alea.ca/alea/eco/rules/eco.pkg with local cache dir of /tmp 2008-03-14 11:46:08,583 ERROR [STDERR] RuleAgent(MyConfig) WARNING (Fri Mar 14 11:46:08 PDT 2008): Was an error contacting http://vconfig.dev.alea.ca/alea/eco/rules/eco.pkg. Reponse header: {null=[HTTP/1.1 200 OK], ETag=["360//alea/eco/rules/eco.pkg"], Date=[Fri, 14 Mar 2008 18:46:08 GMT], Last-Modified=[Fri, 14 Mar 2008 17:06:15 GMT], Keep-Alive=[timeout=15, max=100], Accept-Ranges=[bytes], Connection=[Keep-Alive], Content-Type=[application/octet-stream], Server=[Apache]} 2008-03-14 11:46:08,583 ERROR [STDERR] RuleAgent(MyConfig) WARNING (Fri Mar 14 11:46:08 PDT 2008): Falling back to local cache. I believe the problem resides in "org.droos.agent.HttpClientImpl". It is looking for a http header field "lastModified", instead of the HTTP standard header field "last-modified". Thus it never updates the lastUpdated field in "LastUpdatedPing", which means the server will never load the file. It seems to me to be an easy fix, to check for both headers.. ? Thanks, David. -- 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

18 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1252) Spy JMS Exception

by aneesh vasanthan (JIRA)

Spy JMS Exception ----------------- Key: JBMESSAGING-1252 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1252 Project: JBoss Messaging Issue Type: Bug Components: JMS Client Manager Environment: windows xp, jboss 4.0.2 Reporter: aneesh vasanthan Assigned To: Tim Fox Priority: Critical Fix For: 1.0.0 alpha PR1 (non-clustered) we are using jboss4.0.2 as our application server. we are facing a major problem in jms connection. It happens very frequently. After a restart will be fine for sometime n again it crashes.The exception trace is as shown below. expecting ur eteemed reply. Application server: jboss 4.0.2 Application deployed in : jboss\server\default [java] 10:00:01,759 WARN [Connection] Connection failure, use javax.jms.Connection.setExceptionListener() to handle this error and reconnect [java] org.jboss.mq.SpyJMSException: No pong received; - nested throwable: (java.io.IOException: ping timeout.) [java] at org.jboss.mq.Connection$PingTask.run(Connection.java:1277) [java] at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364) [java] at java.lang.Thread.run(Thread.java:595) [java] Caused by: java.io.IOException: ping timeout. [java] ... 3 more Same error occurs if we try to change the system time -- 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

18 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBREM-932) Check remaining time in MicroSocketClientInvoker per invocation timeout facility

by Ron Sigal (JIRA)

Check remaining time in MicroSocketClientInvoker per invocation timeout facility -------------------------------------------------------------------------------- Key: JBREM-932 URL: http://jira.jboss.com/jira/browse/JBREM-932 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta2 (Pinto) Reporter: Ron Sigal Priority: Minor Fix For: 2.4.0.CR1 (Pinto) If the per invocation timeout value is set, org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport() temporarily sets the current socket's SO_TIMEOUT value for the duration of the invocation. However, it needs to check that the currently remaining time is > 0. -- 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

18 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1307) Update and expand documentation for decision tables to show actual uses for all keywords

by John Scott (JIRA)

Update and expand documentation for decision tables to show actual uses for all keywords ---------------------------------------------------------------------------------------- Key: JBRULES-1307 URL: http://jira.jboss.com/jira/browse/JBRULES-1307 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0.2 Environment: Drools 4.0.3, Rational Application Developer 7.0.0, XP SP2, Reporter: John Scott Priority: Minor I'm trying to implement a decision table for implementing some very simple rules. Currently I apparently am getting into what I believe is an infinite loop as the call never comes back from the fireAllRules method. I had this happen when I implemented the same rules as a DRL, but reading the documentation for the UNLOOP keyword, this is the only description: "Indicates that if there cell values in this column, the no-loop attribute should be set" In addition to the missing words (i.e. "If there ??? cell values..."), this is not very descriptive. Which column? What values? The no-loop attribute SHOULD be set? Would it be possible to show an example of where and how each of these keywords would be used? These keywords can exist at multiple levels of the XLS doc (i.e. the rule set, the rule, individual columns, etc.) so it's quite confusing as to the actual syntax of these. I haven't seen an example yet that uses UNLOOP, and the documentation (as stated above) is not very helpful as to how to implement this. Thanks -- 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

18 years, 4 months

4
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1248) Missing attribute to enable message counters

by Tim Fox (JIRA)

Missing attribute to enable message counters -------------------------------------------- Key: JBMESSAGING-1248 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1248 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2 Currently there is no server peer attribute to enable message counters, only an operation. This means it has to be invoked every time after start up which can be annoying. -- 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

18 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1174) Refactor EJB 3 onto ejb3-interceptors

by Carlo de Wolf (JIRA)

Refactor EJB 3 onto ejb3-interceptors ------------------------------------- Key: EJBTHREE-1174 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1174 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Assigned To: Carlo de Wolf -- 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

18 years, 4 months

2
17
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1250) It should be possible to configure a null persistence manager

by Tim Fox (JIRA)

It should be possible to configure a null persistence manager ------------------------------------------------------------- Key: JBMESSAGING-1250 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1250 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.4.0.SP3.CP02, 1.4.1.beta2 Some users want purely transient messaging - they don't want to persist anything in the database - bindings, messages and do no paging. We should supply a NullPersistenceManager (NO-OP) to enable them to do this. -- 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

18 years, 4 months

1
2
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 2008