[JBoss JIRA] Created: (JBCACHE-1170) Partial state transfer fails when multiple regions present
by Brian Stansberry (JIRA)
Partial state transfer fails when multiple regions present
----------------------------------------------------------
Key: JBCACHE-1170
URL: http://jira.jboss.com/jira/browse/JBCACHE-1170
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.0.0.GA
Reporter: Brian Stansberry
Assigned To: Manik Surtani
The partial state transfer mechanism is getting confused about the Fqn of the region being transferred.
Following is logging from the AS test org.jboss.test.multicfg.web.field.test.StateTransferUnitTestCase. Test is trying to activate region /JSESSION/localhost/http-scoped; logging is from the the node that is generating and returning the state:
2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.VersionAwareMarshaller] Wrote version 20
2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.CacheMarshaller200] Region based call. Using region /JSESSION/localhost/http-field
2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.CacheMarshaller200] Marshalling object true
2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.marshall.CacheMarshaller200] Writing region /JSESSION/localhost/http-field to stream
2007-08-23 17:02:21,162 DEBUG [org.jboss.cache.statetransfer.StateTransferManager] locking the /JSESSION/localhost/http-scoped subtree to return the in-memory (transient) state
The second line shows the problem -- "/JSESSION/localhost/http-field" is written to the stream; it should be "/JSESSION/localhost/http-scoped".
Tracing this, the problem seems to be in CacheMarshaller200.objectToObjectStream(Object o, ObjectOutputStream out). Method is treating 'o' as a return value from a MethodCall and pulling the Fqn to write to the stream from a ThreadLocal. Two problems:
1) This shows that a value is being leaked to the ThreadLocal. We need to clean up the ThreadLocal properly.
2) Need to ensure that the right Fqn gets written. In the logging above, the object being written is actually boolean 'true' so I think no Fqn at all is needed. Need to check if just not writing an Fqn affects anything. If not, just cleaning up the ThreadLocal should work.
--
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, 1 month
[JBoss JIRA] Created: (JBMICROCONT-184) Parsing more than one file
by Adrian Brock (JIRA)
Parsing more than one file
--------------------------
Key: JBMICROCONT-184
URL: http://jira.jboss.com/jira/browse/JBMICROCONT-184
Project: JBoss MicroContainer
Issue Type: Task
Components: Deployment
Reporter: Adrian Brock
Fix For: JBossMC_2_0_0_CR1
The AbstractVFSParser has the following limitiation:
@Override
protected T parse(DeploymentUnit unit, String name, String suffix, T root) throws Exception
{
// Should we include the deployment
// The infrastructure will only check leafs anyway so no need to check here
if (name == null && isIncludeDeploymentFile())
name = unit.getName();
// Try to find the metadata
VFSDeploymentUnit vfsDeploymentUnit = (VFSDeploymentUnit) unit;
List<VirtualFile> files = vfsDeploymentUnit.getMetaDataFiles(name, suffix);
if (files.size() == 0)
return null;
// TODO remove this limitation
if (files.size() > 1)
throw new DeploymentException("Only one file is allowed, found=" + files);
VirtualFile file = files.get(0);
This is really also related to the "reparse" that is done for ejb-jar.xml/jboss.xml and [jboss-]web.xml
There should be parsing deployers that know how to parse multiple files into one object model.
--
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, 1 month
[JBoss JIRA] Created: (JBAS-4189) @EJB doesn't work inside a servlet
by Juergen Zimmermann (JIRA)
@EJB doesn't work inside a servlet
----------------------------------
Key: JBAS-4189
URL: http://jira.jboss.com/jira/browse/JBAS-4189
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB3
Affects Versions: JBossAS-4.2.0.CR1
Environment: JBossAS 4.2.0CR1, JDK 5.0_11, WinXP SP2, Eclipse WTP 1.5.3
Reporter: Juergen Zimmermann
Assigned To: Bill Burke
When a servlet tries to invoke a proxa referencing a stateless session bean I get a null pointer.
1) Stateless session bean:
@Stateless
@Local(EjbRefLocal.class)
public class EjbRefBean implements EjbRefLocal {
public String foo() {
return "ok";
}
}
2) Local interface
public interface EjbRefLocal {
String foo();
}
3) Servlet
public class MyServlet extends HttpServlet {
@EJB
private EjbRefLocal proxy;
@Override
protected void doGet(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
final String result = proxy.foo();
System.out.println("RESULT = " + result);
}
}
--
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, 1 month