[JBoss JIRA] Created: (JBCACHE-711) Replication eats out exception on the remote node
by Ben Wang (JIRA)
Replication eats out exception on the remote node
-------------------------------------------------
Key: JBCACHE-711
URL: http://jira.jboss.com/jira/browse/JBCACHE-711
Project: JBoss Cache
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Replication
Affects Versions: 1.4.0
Reporter: Ben Wang
Assigned To: Manik Surtani
Fix For: 2.0.0
I have seen this on the 1.4 release on ejb3. Here is what happens. Two nodes replication. When the remote node throws an exception like NPE, the originating node will display with NonSerializableException. I don't a unit test for this but I think it should be easy to reproduce.
21:51:32,490 INFO [TxInterceptor] There was a problem handling this request
java.io.NotSerializableException: RpcDispatcher returned a null. This is most often caused by args for _replicate(_put(null, /testNestedStateful/5c4o1e-xzw6rx-eq1m0jea-1-eq1m4tna-5, bean, org.jboss.ejb3.stateful.ProxiedStatefulBeanContext@7b8be7, true)) not being serializable.
at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4166)
at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4113)
at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4214)
at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:110)
at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:88)
at org.jboss.cache.interceptors.ReplicationInterceptor.handleReplicatedMethod(ReplicationInterceptor.java:114)
at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInterceptor.java:83)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at org.jboss.cache.interceptors.PassivationInterceptor.invoke(PassivationInterceptor.java:69)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68)
at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterce
--
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
17 years, 7 months
[JBoss JIRA] Created: (JBAS-3517) Redeploy of Tomcat5 Service chokes with RuntimeException
by Anil Saldhana (JIRA)
Redeploy of Tomcat5 Service chokes with RuntimeException
--------------------------------------------------------
Key: JBAS-3517
URL: http://jira.jboss.com/jira/browse/JBAS-3517
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Security, Web (Tomcat) service
Affects Versions: JBossAS-4.0.4.GA
Reporter: Anil Saldhana
Assigned To: Anil Saldhana
Fix For: JBossAS-4.0.5.GA, JBossAS-5.0.0.GA
Suppose you change a flag in jboss-service.xml in deploy/jbossweb-tomcat55.sar/META-INF, a redeploy of the tomcat 5 service happens.
You will notice the following Runtime Exception and the tomcat service fails to deploy.
==============================================================================================
13:33:30,421 INFO [Catalina] Initialization processed in 562 ms
13:33:30,421 INFO [StandardService] Starting service jboss.web
13:33:30,421 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.1
7
13:33:30,453 INFO [StandardHost] XML validation disabled
13:33:30,468 INFO [Catalina] Server startup in 47 ms
13:33:30,468 WARN [ServiceController] Problem starting service jboss.web:service=WebServer
java.lang.IllegalArgumentException: Handler for key=javax.servlet.http.HttpServl
etRequest, exists, handler: org.jboss.web.tomcat.security.HttpServletRequestPolicyContextHandler@1bb03ee
at javax.security.jacc.PolicyContext.registerHandler(PolicyContext.java:185)
at org.jboss.web.tomcat.tc5.Tomcat5.startService(Tomcat5.java:467)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
===================================================================================
Use the following api of PolicyContext in Tomcat5 service
http://java.sun.com/j2ee/1.4/docs/api/javax/security/jacc/PolicyContext.h...
--
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
17 years, 7 months
[JBoss JIRA] Created: (JBPORTAL-983) Upload of large files fails.
by Peter Johnson (JIRA)
Upload of large files fails.
----------------------------
Key: JBPORTAL-983
URL: http://jira.jboss.com/jira/browse/JBPORTAL-983
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal CMS
Affects Versions: 2.4 Final
Environment: Windows XP, JDK 1.5, JBoss AS 4.0.4GA
Reporter: Peter Johnson
Fix For: 2.4 Final
Using the CMS Admin portlet, I attempted to upload a zip file into a directory, as per section 3.2.9 of the User Guide. Initially I tried a zip ofabout 6MB containing many files, and eventually got down to a a zip file of about 500M with only a single Word document inside. The upload failed and an "SQLException: could not reset reader" error appeared (see forum post for stack trace).
I am, however, able to upload very small zip files.
--
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
17 years, 7 months
[JBoss JIRA] Created: (JBREM-549) remove dependancy on concurrent.jar within remoting client
by Tom Elrod (JIRA)
remove dependancy on concurrent.jar within remoting client
----------------------------------------------------------
Key: JBREM-549
URL: http://jira.jboss.com/jira/browse/JBREM-549
Project: JBoss Remoting
Issue Type: Task
Security Level: Public (Everyone can see)
Components: general
Affects Versions: 2.0.0.Beta2 (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.0.0.CR1 (Boon)
Currently, the remoting clients will require concurrent.jar to be on the classpath because org.jboss.util.id.GUID is used to create the client session id. Problem is that org.jboss.util.id.GUID is what requires concurrent.jar. So will either need to modify the code within jboss common repository or find another class to use for generating the client session id.
java.lang.NoClassDefFoundError: EDU/oswego/cs/dl/util/concurrent/SynchronizedLong
at org.jboss.util.id.UID.<clinit>(UID.java:56)
at org.jboss.util.id.VMID.create(VMID.java:259)
at org.jboss.util.id.VMID.getInstance(VMID.java:223)
at org.jboss.util.id.GUID.<init>(GUID.java:65)
at org.jboss.remoting.Client.<init>(Client.java:133)
at org.jboss.remoting.Client.<init>(Client.java:210)
at org.jboss.remoting.Client.<init>(Client.java:191)
at org.jboss.test.remoting.transport.InvokerClientTest.init(InvokerClientTest.java:80)
--
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
17 years, 7 months
[JBoss JIRA] Created: (JBREM-577) Investigate failure of org.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase, jdk 1.4, on cruisecontrol
by Ron Sigal (JIRA)
Investigate failure of org.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase, jdk 1.4, on cruisecontrol
----------------------------------------------------------------------------------------------------------------------
Key: JBREM-577
URL: http://jira.jboss.com/jira/browse/JBREM-577
Project: JBoss Remoting
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 2.0.0.GA (Boon)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.0.0.GA (Boon)
This test is failing rather consistently in testRule4ServerFirst() on cruisecontrol, even though this particular failure can't be reproduced on any other environment. In case the problem is more than environmental, i.e., a real problem in Multiplex, some additional log statements will be added to MultiplexServerInvoker and OutputMultiplexor.
What is happening is that in runPushCallbackTests(), the message "stopped callback Connector" appears, but then the test dies before the callback Connector completes its shut down. It would be nice to believe that there is a deadlock, but none is evident, unless it's due to a problem with Collections.synchronizedMap in jdk 1.4. Note that this problem never occurs in the jdk 1.5 cruisecontrol tests.
--
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
17 years, 7 months