January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBESB-387) jUDDI-registry (juddi.war) is missing deploy/undeploy ant task

by jarkko Lietolahti (JIRA)

jUDDI-registry (juddi.war) is missing deploy/undeploy ant task -------------------------------------------------------------- Key: JBESB-387 URL: http://jira.jboss.com/jira/browse/JBESB-387 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: jarkko Lietolahti Assigned To: Mark Little As I hate copying files I found out that jUDDI-registry in trunk/product/install/jUDDI-registry is missing proper ant build.xml. Find it attacted here. The build.xml relies on a new global deployment.properties located at ../../../deployment.properties from trunk/product/install/jUDDI-registry that is in the root of the project. This new file should be there that one only has to configure org.jboss.esb.appserver.home and org.jboss.esb.appserver.config only ONCE to make deployment a lot easier for new checkouts and installations. I hate nothing more than copying files to some weird location (e.g. H:/dev/etc ) when running ant first time in a directory ;) -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-346) Create unit tests for classes in the org.jboss.soa.esb.actions.routing package (listeners)

by Tom Fennelly (JIRA)

Create unit tests for classes in the org.jboss.soa.esb.actions.routing package (listeners) ------------------------------------------------------------------------------------------ Key: JBESB-346 URL: http://jira.jboss.com/jira/browse/JBESB-346 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.0 CR1 Reporter: Tom Fennelly Assigned To: Mark Little Fix For: 4.0 Current coverage on this package is at 0/117 lines (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

19 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-780) Fix thirdparty.remoting HTTP tests

by Ovidiu Feodorov (JIRA)

Fix thirdparty.remoting HTTP tests ---------------------------------- Key: JBMESSAGING-780 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-780 Project: JBoss Messaging Issue Type: Sub-task Components: Tests and Performance Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Beta2 -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-371) MessageListener times out on inactivity, after receiving at least one message

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-371?page=comments#action_12... ] Ovidiu Feodorov commented on JBMESSAGING-371: --------------------------------------------- Test: RemotingTest.testMessageListenerTimeout() > MessageListener times out on inactivity, after receiving at least one message > ----------------------------------------------------------------------------- > > Key: JBMESSAGING-371 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-371 > Project: JBoss Messaging > Issue Type: Bug > Components: JMS Remoting > Affects Versions: 1.0.1.CR1, 1.2.0.Beta2 > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Blocker > Fix For: 1.0.1.CR2, 1.2.0.Beta2 > > > 15:15:31,530 ERROR [ServerThread] socket timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.read(SocketInputStream.java:129) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:183) > at java.io.BufferedInputStream.read(BufferedInputStream.java:201) > at java.io.FilterInputStream.read(FilterInputStream.java:66) > at org.jboss.serial.io.JBossObjectInputStream.read(JBossObjectInputStream.java:140) > at org.jboss.remoting.transport.socket.ServerThread.readVersion(ServerThread.java:464) > at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:381) > at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:498) > at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:240) -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-371) MessageListener times out on inactivity, after receiving at least one message

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-371?page=all ] Ovidiu Feodorov updated JBMESSAGING-371: ---------------------------------------- Fix Version/s: 1.2.0.Beta2 Affects Version/s: 1.2.0.Beta2 Description: 15:15:31,530 ERROR [ServerThread] socket timed out java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:183) at java.io.BufferedInputStream.read(BufferedInputStream.java:201) at java.io.FilterInputStream.read(FilterInputStream.java:66) at org.jboss.serial.io.JBossObjectInputStream.read(JBossObjectInputStream.java:140) at org.jboss.remoting.transport.socket.ServerThread.readVersion(ServerThread.java:464) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:381) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:498) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:240) was: 15:15:31,530 ERROR [ServerThread] socket timed out java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:183) at java.io.BufferedInputStream.read(BufferedInputStream.java:201) at java.io.FilterInputStream.read(FilterInputStream.java:66) at org.jboss.serial.io.JBossObjectInputStream.read(JBossObjectInputStream.java:140) at org.jboss.remoting.transport.socket.ServerThread.readVersion(ServerThread.java:464) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:381) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:498) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:240) Priority: Blocker (was: Major) > MessageListener times out on inactivity, after receiving at least one message > ----------------------------------------------------------------------------- > > Key: JBMESSAGING-371 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-371 > Project: JBoss Messaging > Issue Type: Bug > Components: JMS Remoting > Affects Versions: 1.0.1.CR1, 1.2.0.Beta2 > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Blocker > Fix For: 1.0.1.CR2, 1.2.0.Beta2 > > > 15:15:31,530 ERROR [ServerThread] socket timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.read(SocketInputStream.java:129) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:183) > at java.io.BufferedInputStream.read(BufferedInputStream.java:201) > at java.io.FilterInputStream.read(FilterInputStream.java:66) > at org.jboss.serial.io.JBossObjectInputStream.read(JBossObjectInputStream.java:140) > at org.jboss.remoting.transport.socket.ServerThread.readVersion(ServerThread.java:464) > at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:381) > at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:498) > at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:240) -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-371) MessageListener times out on inactivity, after receiving at least one message

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-371?page=all ] Ovidiu Feodorov reopened JBMESSAGING-371: ----------------------------------------- > MessageListener times out on inactivity, after receiving at least one message > ----------------------------------------------------------------------------- > > Key: JBMESSAGING-371 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-371 > Project: JBoss Messaging > Issue Type: Bug > Components: JMS Remoting > Affects Versions: 1.0.1.CR1, 1.2.0.Beta2 > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Fix For: 1.0.1.CR2, 1.2.0.Beta2 > > > 15:15:31,530 ERROR [ServerThread] socket timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.read(SocketInputStream.java:129) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:183) > at java.io.BufferedInputStream.read(BufferedInputStream.java:201) > at java.io.FilterInputStream.read(FilterInputStream.java:66) > at org.jboss.serial.io.JBossObjectInputStream.read(JBossObjectInputStream.java:140) > at org.jboss.remoting.transport.socket.ServerThread.readVersion(ServerThread.java:464) > at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:381) > at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:498) > at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:240) -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-779) Fix crash test CallbackFailureTest.testCallbackFailure()

by Ovidiu Feodorov (JIRA)

Fix crash test CallbackFailureTest.testCallbackFailure() -------------------------------------------------------- Key: JBMESSAGING-779 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-779 Project: JBoss Messaging Issue Type: Sub-task Components: Tests and Performance Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Beta2 -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-689) Server-side callback failure not propagated to calling application in certain situations

by Ovidiu Feodorov (JIRA)

Server-side callback failure not propagated to calling application in certain situations ---------------------------------------------------------------------------------------- Key: JBREM-689 URL: http://jira.jboss.com/jira/browse/JBREM-689 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: callbacks Affects Versions: 2.2.0.Alpha6 Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 2.2.0.Alpha7 n case of push callbacks, the information that a push callback may have failed is used internally (via a CallbackErrorHandler, specifically a DefaultCallbackErrorHandler instance, which destroys the offending ServerInvokerCallbackHandler instance), but it is not propagated to the invoking application. This is not OK, as calling applications (Messaging in this case) may rely on the exception being reported, so they can take quick corrective action. -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBFORUMS-85) Identify and Define Training Materials for Portal Training

by Ryszard Kozmik (JIRA)

[ http://jira.jboss.com/jira/browse/JBFORUMS-85?page=all ] Ryszard Kozmik updated JBFORUMS-85: ----------------------------------- Fix Version/s: 1.2.0 Alpha (was: 1.0.0 RC) > Identify and Define Training Materials for Portal Training > ---------------------------------------------------------- > > Key: JBFORUMS-85 > URL: http://jira.jboss.com/jira/browse/JBFORUMS-85 > Project: JBoss Forums > Issue Type: Task > Components: Documentation, Portlet Productization > Affects Versions: 1.0.0 Alpha > Reporter: Damon Sicore > Assigned To: Ryszard Kozmik > Fix For: 1.2.0 Alpha > > > At a minimum, we need to at least identify the relationships with JBoss Portal training and where JBoss Forums administration and usage concepts are required. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBFORUMS-92) UTF-8 doesn't work in topic subjects

by Ryszard Kozmik (JIRA)

[ http://jira.jboss.com/jira/browse/JBFORUMS-92?page=all ] Ryszard Kozmik updated JBFORUMS-92: ----------------------------------- Component/s: Forum View Layer > UTF-8 doesn't work in topic subjects > ------------------------------------ > > Key: JBFORUMS-92 > URL: http://jira.jboss.com/jira/browse/JBFORUMS-92 > Project: JBoss Forums > Issue Type: Bug > Components: Forum View Layer > Reporter: Tomasz Szymanski > Assigned To: Ryszard Kozmik > Fix For: 1.0.0 Beta > > > http://65.244.175.213:8080/portal-forums/views/index.jsf > shows some silly chars instead of polish diacritic letters. -- 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, 5 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 January 2007