September 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1673) Update documentation with JBoss AS version to use (4.2.1)

by Antoine Herzog (JIRA)

Update documentation with JBoss AS version to use (4.2.1) --------------------------------------------------------- Key: JBPORTAL-1673 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1673 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Reference Guide Affects Versions: 2.6.1 Final Environment: JBP 2.6.1 GA Reporter: Antoine Herzog Assigned To: Julien Viet Priority: Minor Fix For: 2.6.2 Final In the reference guide, (v 2.6.1 dated 25 july 2007), there is : 2.2. Installing from Binary Download "... please install JBoss 4.0.5+ from here ." I guess, now, it is not anymore 4.0.5, but 4.2.1 there should be some other place where this happens (system requirements, etc...) some clarification about using 4.0.5 or 4.2.1 will be welcome too. may be a few links to some wiki about important things to care for the portal, about moving from 4.0.5 to 4.2.1.... Such as the JSF implementation. -- 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

16 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBREM-733) When org.jboss.remoting.Client.addListener() creates a Connector, it should pass in InvokerLocator parameters with configuration map.

by Ron Sigal (JIRA)

When org.jboss.remoting.Client.addListener() creates a Connector, it should pass in InvokerLocator parameters with configuration map. ------------------------------------------------------------------------------------------------------------------------------------- Key: JBREM-733 URL: http://jira.jboss.com/jira/browse/JBREM-733 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) Currently, Client.addListener() is just passing in Client.configuration. It should also add the InvokerLocator parameters so that the server configuration, e.g., XML service file, can contribute to the configuration of a callback server invoker. -- 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

16 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-730) JNDIDetector should use rebind() instead of bind() to add new local detection messages

by Ron Sigal (JIRA)

JNDIDetector should use rebind() instead of bind() to add new local detection messages -------------------------------------------------------------------------------------- Key: JBREM-730 URL: http://jira.jboss.com/jira/browse/JBREM-730 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) Currently, JNDIDetector.registerDetectionMsg() is using javax.naming.Context.bind() to add a new local detection message to the JNDI server, which means it can't overwrite a detection message that already exists. It should call Context.rebind() instead. -- 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

16 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBREM-717) servlet invoker illegal state exception not serializable

by John Mazzitelli (JIRA)

servlet invoker illegal state exception not serializable -------------------------------------------------------- Key: JBREM-717 URL: http://jira.jboss.com/jira/browse/JBREM-717 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.GA (Boon) Reporter: John Mazzitelli Assigned To: Tom Elrod I have my server-side using the servlet invoker (I'm inside JBossAS 4.0.5). After I shutdown and try to restart, I think I might not be restarting properly. If a client sends in a message, I get this stack trace and an HTTP 500 error comes across on the client. Here's the server-side stack: 15:59:05,510 WARN [[ServerInvokerServlet]] Servlet.service() for servlet ServerInvokerServlet threw exception java.io.NotSerializableException: org.jboss.remoting.transport.servlet.ServletServerInvoker at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1075) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1369) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1341) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1284) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1073) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:291) at org.jboss.remoting.marshal.http.HTTPMarshaller.write(HTTPMarshaller.java:69) at org.jboss.remoting.transport.servlet.ServletServerInvoker.processRequest(ServletServerInvoker.java:257) at sun.reflect.GeneratedMethodAccessor183.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:201) at $Proxy185.processRequest(Unknown Source) at org.jboss.remoting.transport.servlet.web.ServerInvokerServlet.processRequest(ServerInvokerServlet.java:127) at org.jboss.remoting.transport.servlet.web.ServerInvokerServlet.doPost(ServerInvokerServlet.java:156) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:595) So this IllegalStateException is thrown because something didn't get restarted. But the fact that this IllegalStateException is defined inside the ServerInvoker object makes it not serializable (ServerInvoker.IllegalStateException is not serializable because ServerInvoker is not serializable). This issue is to document the fact that this exception is not serializable - the whole "restart didn't fully restart" problem is something that may be my fault. Recommend that you split out IllegalStateException so you can send it over the wire - or thrown a java.lang.IllegalStateException. This is in 2.0.0.GA. I haven't tried to see if this is an issue in later versions. -- 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

16 years, 8 months

4
10
0 / 0

[JBoss JIRA] Created: (JBRULES-1159) Function calls for not work for the MVEL dialect

by Mark Proctor (JIRA)

Function calls for not work for the MVEL dialect ------------------------------------------------ Key: JBRULES-1159 URL: http://jira.jboss.com/jira/browse/JBRULES-1159 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.1, 4.0.0.GA Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 4.0.2 MVEL dialect cannot call DRL functions or static method functions on existing classes. -- 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

16 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBREM-789) Release 2.2.1.SP1

by Ron Sigal (JIRA)

Release 2.2.1.SP1 ----------------- Key: JBREM-789 URL: http://jira.jboss.com/jira/browse/JBREM-789 Project: JBoss Remoting Issue Type: Release Security Level: Public (Everyone can see) Reporter: Ron Sigal Assigned To: Ron Sigal -- 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

16 years, 8 months

1
8
0 / 0

[JBoss JIRA] Created: (JBREM-796) Verify Remoting 2.2.2 is compatible with earlier versions

by Ron Sigal (JIRA)

Verify Remoting 2.2.2 is compatible with earlier versions --------------------------------------------------------- Key: JBREM-796 URL: http://jira.jboss.com/jira/browse/JBREM-796 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.2.GA Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.2.GA Need to add version 2.2.0.SP4 jboss-remoting.jar to src/etc/lib and run tests.versioning.all. -- 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

16 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-767) Avoid deadlock in callback BisocketClientInvoker when timeout == 0

by Ron Sigal (JIRA)

Avoid deadlock in callback BisocketClientInvoker when timeout == 0 ------------------------------------------------------------------ Key: JBREM-767 URL: http://jira.jboss.com/jira/browse/JBREM-767 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) If timeout == 0 then org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket() can hang forever if the client side is unavailable. One fix is to not set timeout to 0, but currently the timeout value is inherited from the server invoker, for which timeout == 0 might be appropriate. One solution is to implement a separate timeout parameter for callback client invokers (JBREM-765). Another fix is for PingTimeTask to notify a thread waiting in createSocket() when an attempt to send a PING to the client fails. -- 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

16 years, 8 months

1
6
0 / 0

[JBoss JIRA] Created: (JBREM-765) Add a separate timeout parameter for callback clients

by Ron Sigal (JIRA)

Add a separate timeout parameter for callback clients ----------------------------------------------------- Key: JBREM-765 URL: http://jira.jboss.com/jira/browse/JBREM-765 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) Currently, the timeout set for the server filters down to callback client invokers. However, it would be useful to be able to specify a different timeout value for callback clients. Example. In JBossMessaging the server timeout is set to 0. This causes a problem for bisocket callback client invokers, since they create sockets by sending a message to the client side and then calling wait(). If timeout == 0 and the client dies, then the thread in wait() could wait forever. -- 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

16 years, 8 months

1
5
0 / 0

[JBoss JIRA] Created: (JBREM-731) Address of secondary server socket should be acquired each time a control connection is created.

by Ron Sigal (JIRA)

Address of secondary server socket should be acquired each time a control connection is created. ------------------------------------------------------------------------------------------------ Key: JBREM-731 URL: http://jira.jboss.com/jira/browse/JBREM-731 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.0.GA (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) Scenario: Client is connected to a server, server dies, and server is restarted (with same InvokerLocator). The new server creates a secondary server socket on a different port than the previous server, but the client invoker retains the old secondary server socket InvokerLocator. When a new Client is created, the old client invoker gets reused, and it isn't possible to create a control connection. -- 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

16 years, 8 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2007