[JBoss JIRA] Created: (JBAS-5528) If SingletonStatelessSessionInstancePool is used for a SLSB, container MBean state is reported incorrectly
by Andrew Shcheglov (JIRA)
If SingletonStatelessSessionInstancePool is used for a SLSB, container MBean state is reported incorrectly
----------------------------------------------------------------------------------------------------------
Key: JBAS-5528
URL: http://jira.jboss.com/jira/browse/JBAS-5528
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB2
Affects Versions: JBossAS-4.0.5.GA
Environment: JDK 1.4.2, Windows NT 5.1, Cygwin
(any other anvironment should do as well, though).
Reporter: Andrew Shcheglov
Assigned To: Alexey Loubyansky
If SingletonStatelessSessionInstancePool instead of regular StatelessSessionInstancePool is used for a SLSB,
State/StateString JMX attributes
of the container MBean (jboss.j2ee:jndiName=XXX,plugin=pool,service=EJB)
are always 8/Registered.
This is most probably caused by the fact that org.jboss.ejb.plugins.SingletonStatelessSessionInstancePool class
directly overrides create()/start()/stop()/destroy() operations
with empty implementations,
which any MBean derived from ServiceMBeanSupport shouldn't.
This seems even more useless
since AbstractInstancePool (the direct superclass of SingletonStatelessSessionInstancePool )
doesn't override any methods from ServiceMBeanSupport.
--
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, 2 months
[JBoss JIRA] Created: (JBAS-5355) @JMX lifecycle should be tied to POJO lifecycle
by Adrian Brock (JIRA)
@JMX lifecycle should be tied to POJO lifecycle
-----------------------------------------------
Key: JBAS-5355
URL: http://jira.jboss.com/jira/browse/JBAS-5355
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: MicroContainer bus
Reporter: Adrian Brock
Fix For: JBossAS-5.0.0.CR1
The @JMX annotation should create a registration with the ServiceController that is driven by the POJO lifecycle.
i.e. when create() is invoked on the POJO lifecycle it should move the state to CREATED in the legacy ServiceController
but not re-invoke the create() method on the MBean.
Similarly when create() is invoked from the JMX console, this should reallly re-target to the POJO lifecycle.
--
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, 2 months
[JBoss JIRA] Created: (JBREM-980) ServerInvokerServlet should retrieve ServletServerInvoker based on updated InvokerLocator
by Ron Sigal (JIRA)
ServerInvokerServlet should retrieve ServletServerInvoker based on updated InvokerLocator
-----------------------------------------------------------------------------------------
Key: JBREM-980
URL: http://jira.jboss.com/jira/browse/JBREM-980
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.4.0.CR2
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.GA
>From Galder:
Consider
<servlet>
<servlet-name>Ejb3ServerInvokerServlet</servlet-name>
<description>The ServerInvokerServlet receives requests via HTTP
protocol from within a web container and passes it onto the
ServletServerInvoker for processing.
</description>
<servlet-class>org.jboss.remoting.transport.servlet.web.ServerInvokerServlet</servlet-class>
<init-param>
<param-name>locatorUrl</param-name>
<param-value>servlet://${jboss.bind.address}:8080/unified-invoker/Ejb3ServerInvokerServlet</param-value>
<description>The servlet server invoker</description>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
Now, let's say you bind to 0.0.0.0. You'll get an exception like this:
13:39:26,856 ERROR [ContainerBase] Servlet /unified-invoker threw load() exception
javax.servlet.ServletException: Can not find servlet server invoker with same locator as specified (servlet://0.0.0.0:8080/unified-invoker/Ejb3ServerInvokerServlet)
at org.jboss.remoting.transport.servlet.web.ServerInvokerServlet.getInvokerFromInvokerUrl(ServerInvokerServlet.java:198)
at org.jboss.remoting.transport.servlet.web.ServerInvokerServlet.init(ServerInvokerServlet.java:66)
The problem arises from the fact that Remoting is trying to compare:
servlet://0.0.0.0:8080/unified-invoker/Ejb3ServerInvokerServlet
with
servlet://localhost.localdomain:8080/unified-invoker/Ejb3ServerInvokerServlet
So either, ServerInvokerServlet should call ServerInvoker.validateLocator() with locatorUrl, take the return of that and compare that with the list of locators.
Or validateLocator() is modified to have the real original host passed to the InvokerLocator constructor, rather than the transformed or newHost.
--
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, 2 months