April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPM-793) refresh the bare bones tutorial

by Tom Baeyens (JIRA)

refresh the bare bones tutorial ------------------------------- Key: JBPM-793 URL: http://jira.jboss.com/jira/browse/JBPM-793 Project: JBoss jBPM Issue Type: Feature Request Reporter: Tom Baeyens Assigned To: Tom Baeyens Fix For: jBPM 3.2 Here's a good example of how it should look like: http://www.springframework.org/docs/MVC-step-by-step/Spring-MVC-step-by-s... No graphical designer, start from the bare jbpm download, jdk 1.4.2 and ant. Work out a minimal example. The main target audience is developers that want to see what jbpm does and how it works. Tooling should be excluded to prevent unnecessary noise for this use case. The getting started that is currently on the wiki will be kept in coexistence. That shows jbpm step by step WITH the tooling. -- 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, 11 months

2
3
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

18 years, 11 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

18 years, 11 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

18 years, 11 months

4
10
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

18 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (HIBERNATE-55) No way to specify Connection Release Mode in HMBean

by Mohammed Sadiq (JIRA)

No way to specify Connection Release Mode in HMBean --------------------------------------------------- Key: HIBERNATE-55 URL: http://jira.jboss.com/jira/browse/HIBERNATE-55 Project: Hibernate Issue Type: Feature Request Reporter: Mohammed Sadiq Assigned To: Steve Ebersole In my application I have employed an Hibernate MBean for session factory creation and binding it to JNDI and I've added a new overload for the SessionFactory.openSession(Interceptor, ConnectionReleaseMode) method to oveeride the default connection release mode. The default connection release mode for any Hibernate session created using the session factory deployed through a Hibernate MBean configuration is taken as "after_statement". It will be more helpful, if there exists an MBean attribute "ConnectionReleaseMode" which can thake the enumerated values from the org.hibernate.ConnectionReleaseMode. -- 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, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBREM-641) re-implement the callback polling for http transport to reduce latency

by Tom Elrod (JIRA)

re-implement the callback polling for http transport to reduce latency ---------------------------------------------------------------------- Key: JBREM-641 URL: http://jira.jboss.com/jira/browse/JBREM-641 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: callbacks Affects Versions: 2.0.0.GA (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.2.0.Beta1 (Bluto) Per forum thread, would be nice to have a more "real-time" way to get callbacks from server when using http transport so don't have to wait on ping period. -- 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, 11 months

2
12
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1285) portal testsuite report generation issue with ant that ships with portal

by Prabhat Jha (JIRA)

portal testsuite report generation issue with ant that ships with portal ------------------------------------------------------------------------ Key: JBPORTAL-1285 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1285 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.6.Alpha2 Reporter: Prabhat Jha When running portal testsuite with ANT_HOME set to jboss-portal-2.6/tools, report generation is failing "Could not find a valid processor version implementation from com.icl.saxon.TransformerFactoryImpl" It could be related to incompatible saxon.jar with jdk or somehow jar not getting included in classpath. This needs to be fixed. See: http://jboss.org/index.html?module=bb&op=viewtopic&p=4019427#4019427 -- 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, 11 months

3
11
0 / 0

[JBoss JIRA] Created: (JBAOP-387) Throw Exceptions when an valid advice is not found

by Flavia Rainone (JIRA)

Throw Exceptions when an valid advice is not found -------------------------------------------------- Key: JBAOP-387 URL: http://jira.jboss.com/jira/browse/JBAOP-387 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Flavia Rainone Assigned To: Flavia Rainone Fix For: 2.0.0.alpha5 We need to throw an exception warning the user that a valid advice method couldn't be found for a specific joinpoint scenario. (currently, we are printing warnings in the org.jboss.aop.advice.annotation.AdviceMethodFactory algorithm). This task involves changes to org.jboss.aop.advice.PerVMAdvice and org.jboss.aop.advice.annotation.AdviceMethodFactory 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

18 years, 11 months

2
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-629) Unneccessary puts and gets in message store

by Tim Fox (JIRA)

Unneccessary puts and gets in message store ------------------------------------------- Key: JBMESSAGING-629 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-629 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.0.1.GA, 1.2.0.Alpha1 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.Beta1 We are currently executing unnecessary puts into the message store on the primary execution path of message routing. When a new message arrives - it is first added to the message store. The message is only ever retrieved from the message store if a reference is loaded from paging and we want to make sure we do not have more than once instance in memory at once. The first put is therefore unnecessary and will have some performance implications. Messages should only be added to the message store (if necessary) when they are paged to storage -- 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, 11 months

5
10
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 April 2007