July 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBREM-303) org.jboss.test.remoting.transport.multiplex.BasicSocketTestCase(jboss_serialization) failure

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-303?page=all ] Ron Sigal closed JBREM-303. --------------------------- Resolution: Done This problem hasn't recurred, and it looks like a timing problem between the client and the server. A Thread.sleep() added to the server "script" for the failing test, testRemoteInputShutdown(), might help to keep the timing problem from recurring. In any case, it looks like the problem lies in the test case rather than in the core Multiplex code. > org.jboss.test.remoting.transport.multiplex.BasicSocketTestCase(jboss_serialization) failure > -------------------------------------------------------------------------------------------- > > Key: JBREM-303 > URL: http://jira.jboss.com/jira/browse/JBREM-303 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: transport-multiplex > Affects Versions: 1.4.0 beta > Environment: WinXP, JDK 1.5 > Reporter: Tom Elrod > Assigned To: Ron Sigal > Priority: Minor > Fix For: 2.0.0.CR1 (Boon) > > Attachments: BasicSocketTestCase(jboss_serialization)-err.txt, BasicSocketTestCase(jboss_serialization)-out.txt, BasicSocketTestCase(jboss_serialization).html > > > org.jboss.test.remoting.transport.multiplex.BasicSocketTestCase(jboss_serialization) fails when running testsuite on WinXP with JDK 1.5. This is only with jboss serialization (java serialization test passes). Test output files attached (but looks like was due to a broken pipe). -- 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

20 years

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-427) MDB compatibility test fails with an 1.0.1.CR1 server

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-427?page=all ] Ovidiu Feodorov updated JBMESSAGING-427: ---------------------------------------- JBoss Forum Reference: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=85729 > MDB compatibility test fails with an 1.0.1.CR1 server > ----------------------------------------------------- > > Key: JBMESSAGING-427 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-427 > Project: JBoss Messaging > Issue Type: Bug > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Fix For: 1.0.1.GA > > > 17:18:45,875 INFO [STDOUT] The Message Driven Bean failed! > 17:18:45,890 ERROR [STDERR] java.lang.RuntimeException: Failed to read payload > 17:18:45,890 ERROR [STDERR] at org.jboss.messaging.core.message.MessageSupport.getPayload(MessageSupport.java:226) > 17:18:45,890 ERROR [STDERR] at org.jboss.jms.message.JBossTextMessage.getText(JBossTextMessage.java:144) > 17:18:45,890 ERROR [STDERR] at org.jboss.jms.message.TextMessageProxy.getText(TextMessageProxy.java:55) > 17:18:45,890 ERROR [STDERR] at org.jboss.example.jms.mdb.MDBExample.onMessage(MDBExample.java:37) > 17:18:45,890 ERROR [STDERR] at sun.reflect.GeneratedMethodAccessor83.invoke(Unknown Source) > 17:18:45,890 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > 17:18:45,890 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:324) > 17:18:45,890 ERROR [STDERR] at org.jboss.invocation.Invocation.performCall(Invocation.java:359) > 17:18:45,890 ERROR [STDERR] at org.jboss.ejb.MessageDrivenContainer$ContainerInterceptor.invoke(MessageDrivenContainer.java:495) > 17:18:45,890 ERROR [STDERR] at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:158) > 17:18:45,890 ERROR [STDERR] at org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor.invoke(MessageDrivenInstanceInterceptor.java:116) > 17:18:45,890 ERROR [STDERR] at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63) > 17:18:45,890 ERROR [STDERR] at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121) > 17:18:45,890 ERROR [STDERR] at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:350) > 17:18:45,890 ERROR [STDERR] at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:181) > 17:18:45,890 ERROR [STDERR] at org.jboss.ejb.plugins.RunAsSecurityInterceptor.invoke(RunAsSecurityInterceptor.java:109) > 17:18:45,890 ERROR [STDERR] at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205) > 17:18:45,890 ERROR [STDERR] at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:136) > 17:18:45,890 ERROR [STDERR] at org.jboss.ejb.MessageDrivenContainer.internalInvoke(MessageDrivenContainer.java:402) > 17:18:45,890 ERROR [STDERR] at org.jboss.ejb.Container.invoke(Container.java:954) > 17:18:45,890 ERROR [STDERR] at org.jboss.ejb.plugins.jms.JMSContainerInvoker.invoke(JMSContainerInvoker.java:987) > 17:18:45,890 ERROR [STDERR] at org.jboss.ejb.plugins.jms.JMSContainerInvoker$MessageListenerImpl.onMessage(JMSContainerInvoker.java:1287) > 17:18:45,890 ERROR [STDERR] at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:266) > 17:18:45,890 ERROR [STDERR] at org.jboss.jms.client.remoting.MessageCallbackHandler.callOnMessage(MessageCallbackHandler.java:82) > 17:18:45,890 ERROR [STDERR] at org.jboss.jms.client.container.AsfAspect.handleRun(AsfAspect.java:165) > 17:18:45,890 ERROR [STDERR] at sun.reflect.GeneratedMethodAccessor82.invoke(Unknown Source) > 17:18:45,890 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > 17:18:45,890 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:324) > 17:18:45,890 ERROR [STDERR] at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:130) > 17:18:45,890 ERROR [STDERR] at org.jboss.jms.client.delegate.ClientSessionDelegate$run_N8003352271541955702.invokeNext(ClientSessionDelegate$run_N8003352271541955702.java) > 17:18:45,890 ERROR [STDERR] at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:130) > 17:18:45,890 ERROR [STDERR] at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:117) > 17:18:45,890 ERROR [STDERR] at org.jboss.jms.client.delegate.ClientSessionDelegate$run_N8003352271541955702.invokeNext(ClientSessionDelegate$run_N8003352271541955702.java) > 17:18:45,890 ERROR [STDERR] at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:69) > 17:18:45,890 ERROR [STDERR] at org.jboss.jms.client.delegate.ClientSessionDelegate$run_N8003352271541955702.invokeNext(ClientSessionDelegate$run_N8003352271541955702.java) > 17:18:45,890 ERROR [STDERR] at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107) > 17:18:45,890 ERROR [STDERR] at org.jboss.jms.client.delegate.ClientSessionDelegate$run_N8003352271541955702.invokeNext(ClientSessionDelegate$run_N8003352271541955702.java) > 17:18:45,890 ERROR [STDERR] at org.jboss.jms.client.delegate.ClientSessionDelegate.run(ClientSessionDelegate.java) > 17:18:45,890 ERROR [STDERR] at org.jboss.jms.client.JBossSession.run(JBossSession.java:199) > 17:18:45,890 ERROR [STDERR] at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:194) > 17:18:45,890 ERROR [STDERR] at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748) > 17:18:45,890 ERROR [STDERR] at java.lang.Thread.run(Thread.java:534) > 17:18:45,890 ERROR [STDERR] Caused by: java.io.EOFException > 17:18:45,890 ERROR [STDERR] at java.io.DataInputStream.readFully(DataInputStream.java:268) > 17:18:45,890 ERROR [STDERR] at org.jboss.serial.util.StringUtil.pullDataToBuffer(StringUtil.java:170) > 17:18:45,890 ERROR [STDERR] at org.jboss.serial.util.StringUtil.readString(StringUtil.java:211) > 17:18:45,890 ERROR [STDERR] at org.jboss.serial.io.JBossObjectInputStream.readUTF(JBossObjectInputStream.java:237) > 17:18:45,890 ERROR [STDERR] at org.jboss.jms.message.JBossTextMessage.readPayloadExternal(JBossTextMessage.java:166) > 17:18:45,890 ERROR [STDERR] at org.jboss.messaging.core.message.MessageSupport.getPayload(MessageSupport.java:211) > 17:18:45,890 ERROR [STDERR] ... 41 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

20 years

1
0
0 / 0

[JBoss JIRA] Updated: (BPEL-161) loop with condition at the end

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-161?page=all ] Alejandro Guizar updated BPEL-161: ---------------------------------- Fix Version/s: jBPM BPEL 1.1 beta 3 (was: jBPM BPEL 1.1 beta 2) > loop with condition at the end > ------------------------------ > > Key: BPEL-161 > URL: http://jira.jboss.com/jira/browse/BPEL-161 > Project: JBoss jBPM BPEL > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 4 > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 beta 3 > > > The BPEL spec, section 12.4, describes <repeatUntil>, an structure that performs its nested activity so long as after that activity executes some condition holds true. -- 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

20 years

1
0
0 / 0

[JBoss JIRA] Updated: (BPEL-151) export the reference of the published endpoint

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-151?page=all ] Alejandro Guizar updated BPEL-151: ---------------------------------- Fix Version/s: jBPM BPEL 1.1 beta 3 (was: jBPM BPEL 1.1 beta 2) > export the reference of the published endpoint > ---------------------------------------------- > > Key: BPEL-151 > URL: http://jira.jboss.com/jira/browse/BPEL-151 > Project: JBoss jBPM BPEL > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 3 > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Priority: Critical > Fix For: jBPM BPEL 1.1 beta 3 > > > Provide the endpoint reference of the process with respect to partner links. Implement its use as the source of assignment, as described in section 9.4 of the spec. -- 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

20 years

1
0
0 / 0

[JBoss JIRA] Updated: (BPEL-59) get original BPEL document after deployment

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-59?page=all ] Alejandro Guizar updated BPEL-59: --------------------------------- Fix Version/s: jBPM BPEL 1.1 beta 3 (was: jBPM BPEL 1.1 beta 2) > get original BPEL document after deployment > ------------------------------------------- > > Key: BPEL-59 > URL: http://jira.jboss.com/jira/browse/BPEL-59 > Project: JBoss jBPM BPEL > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 3 > Reporter: Dmitry > Assigned To: Alejandro Guizar > Priority: Minor > Fix For: jBPM BPEL 1.1 beta 3 > > > i'm developing a BAM system(http://sourceforge.net/projects/jbam). and i need on my presentation part of the system show the user on what step of the execution of the process are we currently on. i'm intercepting JBPM system ivents via JBossAOP framework, and as a reason of it have no problem to know on which step of process instance execution are we currently on and what is my input data, but i can't meanwhile to find way to get process flow definition. according to my design i would like to get on each processinstance start a process xml model so i could transform it to SVG and show to end user on portal(the representation on my system). this is needed becouse process might have different versions and i'd like to show to user the updated one or busuness analyst might what to know how did the process flow looked two month ago, and this information i can give him from my database if i have xml definition stored inside it. > Regards, > Dmitry. -- 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

20 years

1
0
0 / 0

[JBoss JIRA] Updated: (BPEL-143) bpel web service production

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-143?page=all ] Alejandro Guizar updated BPEL-143: ---------------------------------- Fix Version/s: jBPM BPEL 1.1 beta 3 (was: jBPM BPEL 1.1 beta 2) > bpel web service production > --------------------------- > > Key: BPEL-143 > URL: http://jira.jboss.com/jira/browse/BPEL-143 > Project: JBoss jBPM BPEL > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 1 > Environment: ws4ee, w3c dom, saaj, jms > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 beta 3 > > -- 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

20 years

1
0
0 / 0

[JBoss JIRA] Updated: (BPEL-144) publish document/literal endpoints

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-144?page=all ] Alejandro Guizar updated BPEL-144: ---------------------------------- Fix Version/s: jBPM BPEL 1.1 beta 3 (was: jBPM BPEL 1.1 beta 2) > publish document/literal endpoints > ---------------------------------- > > Key: BPEL-144 > URL: http://jira.jboss.com/jira/browse/BPEL-144 > Project: JBoss jBPM BPEL > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 4 > Environment: jaxrpc, saaj, w3c dom > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 beta 3 > > > jBPM BPEL currently generates service WSDL documents and processes SOAP request/response messages only for RPC/literal web services. Enhancing the service generation tool and the JAX-RPC handler to cover the document style is crucial for interoperability, particulary with .NET. -- 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

20 years

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-550) Eliminate redundant classes in org.jboss.remoting.transport.multiplex

by Ron Sigal (JIRA)

Eliminate redundant classes in org.jboss.remoting.transport.multiplex --------------------------------------------------------------------- Key: JBREM-550 URL: http://jira.jboss.com/jira/browse/JBREM-550 Project: JBoss Remoting Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR1 (Boon) Reporter: Ron Sigal Assigned To: Ron Sigal Priority: Minor Fix For: 2.0.0.CR1 (Boon) Several classes in org.jboss.remoting.transport.multiplex have been moved to org.jboss.remoting.transport.multiplex.utility and should be removed from org.jboss.remoting.transport.multiplex. -- 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

20 years

1
2
0 / 0

[JBoss JIRA] Closed: (JBREM-391) Add javadoc

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-391?page=all ] Ron Sigal closed JBREM-391. --------------------------- Resolution: Done javadoc added. > Add javadoc > ----------- > > Key: JBREM-391 > URL: http://jira.jboss.com/jira/browse/JBREM-391 > Project: JBoss Remoting > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Affects Versions: 2.0.0.Beta2 (Boon) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Fix For: 2.0.0.CR1 (Boon) > > > Self explanatory. -- 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

20 years

1
0
0 / 0

[JBoss JIRA] Closed: (JBCACHE-594) Make interceptors use SPI rather than TreeCache impl

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-594?page=all ] Manik Surtani closed JBCACHE-594. --------------------------------- Resolution: Done > Make interceptors use SPI rather than TreeCache impl > ---------------------------------------------------- > > Key: JBCACHE-594 > URL: http://jira.jboss.com/jira/browse/JBCACHE-594 > Project: JBoss Cache > Issue Type: Sub-task > Reporter: Manik Surtani > Assigned To: Manik Surtani > Fix For: 2.0.0 > > Time Spent: 3 days > Remaining Estimate: 0 minutes > -- 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

20 years

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 July 2006