[JBoss JIRA] Created: (JBREM-600) org.jboss.test.remoting.lease.multiplex.MultiplexLeaseTestCase fails
by Tom Elrod (JIRA)
org.jboss.test.remoting.lease.multiplex.MultiplexLeaseTestCase fails
--------------------------------------------------------------------
Key: JBREM-600
URL: http://jira.jboss.com/jira/browse/JBREM-600
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: transport-multiplex
Affects Versions: 2.0.0.GA (Boon)
Reporter: Tom Elrod
Assigned To: Ron Sigal
Fix For: 2.2.0.Beta1 (Bluto)
When run org.jboss.test.remoting.lease.multiplex.MultiplexLeaseTestCase, the test fails. From debugging, the ServerInvoker's leaseManagement variable is not set to true when it's invoke() method is called (thus by-passing leasing).
Also noticed when debugging that when Connector.addConnectionListener() calls:
invoker.addConnectionListener(listener);
that the invoker instance was MultiplexServerInvoker[master] (this is where the leaseManagement variable gets set to true) and when the PING invocation request is processed within ServerInvoker.invoke() method (where checks to see if leaseManagement variable is true and is not), the invoker instance is MultiplexServerInvoker[virtual:/127.0.0.1:5400->/127.0.0.1:1914].
--
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, 8 months
[JBoss JIRA] Created: (JBAS-3799) Eclipse 3.2 deploys new EAR, JBoss trys to unload old EAR from memory but gives error before able to load new EAR.
by Melinda Savoy (JIRA)
Eclipse 3.2 deploys new EAR, JBoss trys to unload old EAR from memory but gives error before able to load new EAR.
------------------------------------------------------------------------------------------------------------------
Key: JBAS-3799
URL: http://jira.jboss.com/jira/browse/JBAS-3799
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployment services
Affects Versions: JBossAS-4.0.5.GA
Environment: Windows XP, Eclipse 3.2
Reporter: Melinda Savoy
Assigned To: Dimitris Andreadis
Our dev team just installed Eclipse 3.2 and JBoss 4.0.5.GA on our local Window XP
machines.
When trying to run on server a JSP page from within the Eclipse 3.2 IDE I am getting the
following error:
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from
fulfilling this request.
exception
java.lang.NullPointerException
org.jboss.mx.loading.RepositoryClassLoader.findClass(RepositoryClassLoader.java:620)
java.lang.ClassLoader.loadClass(Unknown Source)
org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:464)
org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:405)
java.lang.ClassLoader.loadClass(Unknown Source)
java.lang.ClassLoader.loadClassInternal(Unknown Source)
org.acegisecurity.ui.ntlm.NtlmProcessingFilter.onPreAuthentication(NtlmProcessingFilter.java:344)
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:200)
org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274)
org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:110)
org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274)
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:191)
org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274)
org.acegisecurity.util.FilterChainProxy.doFilter(FilterChainProxy.java:148)
org.acegisecurity.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:90)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
note The full stack trace of the root cause is available in the Apache
Tomcat/5.5.20 logs.
It appears(?) that the issue is that Eclipse will rebuild and redeploy the EAR
to JBoss while at the same time opening up IE and trying to load the JSP. JBoss
eventually will see the new EAR and it has to go through a process of unloading
the current EAR from memory and then reloading the new EAR. The error I see is
happening when JBoss unloads the current EAR from memory as far as I can tell.
--
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, 8 months