March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBAS-2423) Upgrade commons-httpclient.jar from 2.0 to 2.0.2

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2423?page=comments#action_12357516 ] Dimitris Andreadis commented on JBAS-2423: ------------------------------------------ If you had searched a little better: JBAS-3955 > Upgrade commons-httpclient.jar from 2.0 to 2.0.2 > ------------------------------------------------ > > Key: JBAS-2423 > URL: http://jira.jboss.com/jira/browse/JBAS-2423 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Other > Reporter: Dimitris Andreadis > Assigned To: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-5.0.0.Beta1, JBossAS-3.2.8RC1, JBossAS-4.0.4RC1 > > > Update from 2.0 to latest stable release 2.0.2 > see > http://archive.apache.org/dist/jakarta/commons/httpclient/RELEASE-NOTES-2... -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-2423) Upgrade commons-httpclient.jar from 2.0 to 2.0.2

by Jonathan Huang (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2423?page=comments#action_12357514 ] Jonathan Huang commented on JBAS-2423: -------------------------------------- Hi, Would it be possible to upgrade HttpClient to its latest stable version (3.0.1) or the current version 3.1-rc1? I am porting over code where I've used standalone with HttpClient and the following call is not supported when using jbossall-client.jar since the HttpClient class it packages is too old: httppost.setRequestEntity (new ByteArrayRequestEntity (ba)); where httppost is of type PostMethod. This is fairly standard code but the API is only available starting from 3.0 on. Even with this bug fix I would still have this problem since it only updates it to version 2.0.2, which is fairly old now. I see this bug was originally filed in November 2005 so a lot of changes have gone into HttpClient since then. It'd be nice to update it to the latest version if possible. Thanks, Jonathan Huang > Upgrade commons-httpclient.jar from 2.0 to 2.0.2 > ------------------------------------------------ > > Key: JBAS-2423 > URL: http://jira.jboss.com/jira/browse/JBAS-2423 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Other > Reporter: Dimitris Andreadis > Assigned To: Dimitris Andreadis > Priority: Minor > Fix For: JBossAS-5.0.0.Beta1, JBossAS-3.2.8RC1, JBossAS-4.0.4RC1 > > > Update from 2.0 to latest stable release 2.0.2 > see > http://archive.apache.org/dist/jakarta/commons/httpclient/RELEASE-NOTES-2... -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBFORUMS-199) a wrong comment

by Luca Stancapiano (JIRA)

a wrong comment --------------- Key: JBFORUMS-199 URL: http://jira.jboss.com/jira/browse/JBFORUMS-199 Project: JBoss Forums Issue Type: Bug Components: Forum View Layer Affects Versions: 1.2.0 Alpha Environment: any Reporter: Luca Stancapiano Assigned To: Ryszard Kozmik Fix For: 1.2.0 Alpha hi......there is a little bug about comment into /src/resources/portal-forums-war/WEB-INF/subSilver/jsp/profile_view_body.jsp into the row 10 :  the first comment should to be so:  otherwise we see a uuuuugly sign as this : "-> -->" I send you the patch...bye -- 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, 3 months

2
9
0 / 0

[JBoss JIRA] Created: (JBAS-3800) EJBQLToSQL92Compiler should use only searchable columns with DISTINCT

by Alexey Loubyansky (JIRA)

EJBQLToSQL92Compiler should use only searchable columns with DISTINCT --------------------------------------------------------------------- Key: JBAS-3800 URL: http://jira.jboss.com/jira/browse/JBAS-3800 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: CMP service Affects Versions: JBossAS-4.0.5.GA, JBossAS-3.2.8.SP1 Reporter: Alexey Loubyansky Assigned To: Alexey Loubyansky Currently it selects all columns which causes errors since, e.g. BLOBs are not comparable or searchable and, hence, can't be used with distinct. -- 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, 3 months

3
2
0 / 0

[JBoss JIRA] Commented: (JBPM-615) mavenize jbpm

by Manfred Moser (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-615?page=comments#action_12357482 ] Manfred Moser commented on JBPM-615: ------------------------------------ When you move to Maven, make sure you move to Maven 2. I very much look forward to the move. Especially to have the artifacts available in the jboss repository. > mavenize jbpm > ------------- > > Key: JBPM-615 > URL: http://jira.jboss.com/jira/browse/JBPM-615 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > > restructure jbpm to something similar as maven. probably use maven while we're at it: mainly one artifact per subproject. > also the gpd and bpel subprojects should be included in the new structure > see also jbpm forum discussions > http://www.jboss.com/index.html?module=bb&op=viewtopic&t=77833 > and > http://www.jboss.com/index.html?module=bb&op=viewtopic&t=74429 -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4247) failing org.jboss.test.messagedriven.test.JMSContainerInvokerQueueMessageDrivenUnitTestCase

by Dimitris Andreadis (JIRA)

failing org.jboss.test.messagedriven.test.JMSContainerInvokerQueueMessageDrivenUnitTestCase ------------------------------------------------------------------------------------------- Key: JBAS-4247 URL: http://jira.jboss.com/jira/browse/JBAS-4247 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JMS service Environment: Java Version 1.5.0_10 Java Vendor Sun Microsystems Inc. Java VM Name Java HotSpot(TM) Server VM Java VM Version 1.5.0_10-b03 Java VM Info mixed mode OS Name Linux OS Version 2.6.9-42.0.2.ELsmp OS Arch i386 Reporter: Dimitris Andreadis Assigned To: Adrian Brock Priority: Critical Fix For: JBossAS-4.2.0.GA testRestartJMS Error Cannot send a message to the JMS server; - nested throwable: (java.io.IOException: Client is not connected) org.jboss.mq.SpyJMSException: Cannot send a message to the JMS server; - nested throwable: (java.io.IOException: Client is not connected) at org.jboss.mq.SpyJMSException.getAsJMSException(SpyJMSException.java:72) at org.jboss.mq.SpyJMSException.rethrowAsJMSException(SpyJMSException.java:57) at org.jboss.mq.Connection.sendToServer(Connection.java:922) at org.jboss.mq.SpySession.sendMessage(SpySession.java:924) at org.jboss.mq.SpyMessageProducer.send(SpyMessageProducer.java:272) at org.jboss.mq.SpyMessageProducer.send(SpyMessageProducer.java:206) at org.jboss.test.messagedriven.support.SendMessageOperation.run(SendMessageOperation.java:50) at org.jboss.test.messagedriven.support.BasicMessageDrivenUnitTest.runTest(BasicMessageDrivenUnitTest.java:112) at org.jboss.test.messagedriven.test.JMSContainerInvokerQueueMessageDrivenUnitTestCase.testRestartJMS(JMSContainerInvokerQueueMessageDrivenUnitTestCase.java:67) Caused by: java.io.IOException: Client is not connected at org.jboss.mq.il.uil2.SocketManager.internalSendMessage(SocketManager.java:264) at org.jboss.mq.il.uil2.SocketManager.sendMessage(SocketManager.java:220) at org.jboss.mq.il.uil2.UILServerIL.addMessage(UILServerIL.java:245) at org.jboss.mq.Connection.sendToServer(Connection.java:918) ... 21 more -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-937) Benchmark VersionAwareMarshaller

by Galder Zamarreno (JIRA)

Benchmark VersionAwareMarshaller -------------------------------- Key: JBCACHE-937 URL: http://jira.jboss.com/jira/browse/JBCACHE-937 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.ALPHA2 Reporter: Galder Zamarreno Assigned To: Manik Surtani Fix For: 2.0.0.BETA2 Benchmark VersionAwareMarshaller to make it more performant. There's already a unit test to use it as base: VersionAwareMarshallerPerfTest. It should probably make comparison failures based on results from different marshalling methods, i.e, if difference bigger than x, fail. Also add marshalling different types of objects. Potential performance improvements: - Using similar techniques as used in ExposedByteArrayOutputStream (JGroups) for VAM? Needs profiling to determine effect. -- 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, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-4256) Add support for stopping ILs triggering the ExceptionListener - JVMIL

by Adrian Brock (JIRA)

Add support for stopping ILs triggering the ExceptionListener - JVMIL --------------------------------------------------------------------- Key: JBAS-4256 URL: http://jira.jboss.com/jira/browse/JBAS-4256 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.0.4RC1 Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta2, JBossAS-4.0.5.SP1 As per the super task which is a fix to make sure client exception listeners get triggered if somebody stops the server, this same behaviour should occur if somebody just stops the IL. This involves making each IL keep track of their respective connections. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-3975) support value classes in EJBQLToSQL92Compiler

by Alexey Loubyansky (JIRA)

support value classes in EJBQLToSQL92Compiler --------------------------------------------- Key: JBAS-3975 URL: http://jira.jboss.com/jira/browse/JBAS-3975 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: CMP service Affects Versions: JBossAS-5.0.0.Beta1, JBossAS-4.0.5.GA, JBossAS-3.2.8.SP1 Reporter: Alexey Loubyansky Assigned To: Alexey Loubyansky Fix For: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.CR1, JBossAS-4.0.5.SP1 , JBossAS-3.2.8.SP2 The EJBQLToSQL92Compiler doesn't value classes in paths and as parameters. -- 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, 3 months

3
2
0 / 0

[JBoss JIRA] Commented: (JBAS-1098) Foreign key violation during cascade delete

by Gunnar Grim (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1098?page=comments#action_12357453 ] Gunnar Grim commented on JBAS-1098: ----------------------------------- Perhaps batch-cascade-delete works with multiple levels in simple one-many relationship chains but it won't work in this case: PropertyType has many PropertyValue entities. The foreign key is in PropertyValue and references PropertyType. Both cascade-delete and batch-cascade-delete are used in the role referencing PropertyType. PropertyValue has a one-one relationship with PropertyValueExt. The foreign key (nullable) is in PropertyValue and references PropertyValueExt. Cascade-delete is used in the role referencing PropertyValue. Batch-cascade-delete can't be specified for the latter relationship since deployment fails with the message "Batch cascade-delete supported only for roles with no foreign keys." If I try to remove a PropertyType that has related PropertyValue instances, and one of these have a related PropertyValueExt instance, the deletion fails with an SQL exception: Cannot delete or update a parent row: a foreign key constraint fails ("doistudio/PropertyValue", CONSTRAINT "FK_ExtendedValue_PropertyValue" FOREIGN KEY ("PropValueExtID") REFERENCES "PropertyValueExt" ("PropValueID")) The same application works fine on Sun AS 8.1 and 9.0. If it is true that you "don't invest in CMP2.x anymore" then that is a pity but hardly a reason to reject this bug IMO. > Foreign key violation during cascade delete > ------------------------------------------- > > Key: JBAS-1098 > URL: http://jira.jboss.com/jira/browse/JBAS-1098 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CMP service > Affects Versions: JBossAS-3.2.6 Final > Reporter: SourceForge User > Assigned To: Alexey Loubyansky > Fix For: No Release > > > SourceForge Submitter: sflexus . > JBoss 3.2.5, JDK 1.4.2_04, Linux. > I have CMP Entity Customer and CMP entity Album with > the following relationships: > 1) 1 Customer has Many Albums > 2) 1 Customer has 1 Album "Inbox" > 3) 1 Customer has 1 Album "Private" > 4) 1 Customer has 1 Album "Recycle Bin" > So basically there are 3 Albums each of which has double > relationship to Customer, both 1-1 and 1-M > Relationship (1) has cascade-delete on Album side, so if > customer is deleted, all his albums should be deleted. > Relationships (2)-(4) has NO cascade-delete setting, > since (1) should be enough, as it references ALL > customer's albums, including those referenced in (2)-(4). > There are other entities related to Customer in the > application, but they seem non-important (at first sight). > If I try to remove Customer instance, I get foreigh key > violation in the database. All foreign keys were created > by JBoss itself. I have attached TRACE-level log. What > happens is that all 3 albums (inbox, private and recycle > bin, their IDs are 162, 163 and 164) are scheduled for > cascade delete, but only the one with ID=164 is updated > to set its CMR column to NULL before issuing DELETE > FROM Customer SQL. The foreign key fk_album_owner > which is being violated corresponds to relation (1) "1 > Customer has Many Albums". > The interesting thing is that if I redeploy the application > and issue remove again, it completes normally! Looks like > it depends on some cache state. > Two files are attached. First one demonstrates foreign > key violation, second one demonstrates success deletion > after application is redeployed. -- 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, 3 months

1
0
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 2007