[JBoss JIRA] Created: (JBAS-3503) Clustering testbeancluster test failures - Deployment Error
by Rajesh Rajasekaran (JIRA)
Clustering testbeancluster test failures - Deployment Error
-----------------------------------------------------------
Key: JBAS-3503
URL: http://jira.jboss.com/jira/browse/JBAS-3503
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-4.0.5.CR1
Reporter: Rajesh Rajasekaran
Assigned To: Brian Stansberry
Fix For: JBossAS-4.0.5.CR1
Deployment of the test resources for the following tests fail with the error shown below. Hence the tests cannot connect to the service as shown in the results on CC
http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.0-testsuite-sun-1.4/2...
Server log for the errors shown below:
http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.0-testsuite-sun-1.4/2...
org.jboss.test.testbeancluster.test.CacheInvalidationUnitTestCase(Default-UDP)
org.jboss.test.testbeancluster.test.RetryInterceptorUnitTestCase(Default-UDP)
org.jboss.test.testbeancluster.test.SingleRetryInterceptorUnitTestCase(Default-UDP)
2006-08-09 22:39:57,054 DEBUG [org.jboss.ejb.EjbModule] Starting failed jboss.j2ee:module=test-cif.jar,service=EjbModule
org.jboss.deployment.DeploymentException: Error: can't find data source: java:/CIFTestDS; - nested throwable: (javax.naming.NameNotFoundException: CIFTestDS not bound)
at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.init(JDBCEntityBridge.java:153)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.initStoreManager(JDBCStoreManager.java:435)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:368)
at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:172)
at org.jboss.ejb.EjbModule.startService(EjbModule.java:411)
--
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, 11 months
[JBoss JIRA] Created: (JBAS-3489) Test failure - org.jboss.test.aop.test.ScopedUnitTestCase
by Rajesh Rajasekaran (JIRA)
Test failure - org.jboss.test.aop.test.ScopedUnitTestCase
---------------------------------------------------------
Key: JBAS-3489
URL: http://jira.jboss.com/jira/browse/JBAS-3489
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Test Suite
Affects Versions: JBossAS-4.0.5.CR1
Reporter: Rajesh Rajasekaran
Fix For: JBossAS-4.0.5.CR1
org.jboss.test.aop.test.ScopedUnitTestCase
testcases: testEar1 & testEar2
http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.0-testsuite-sun-1.4/2...
Comparison of actual scope and expected scope fails because
org.jboss.test.aop.scoped.ear.interceptor.TestInterceptor returns null
2006-08-07 19:44:57,396 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/ear1].[EarExampleServlet]] Servlet.service() for servlet EarExampleServlet threw exception
java.lang.NullPointerException
at org.jboss.test.aop.scoped.ear.servlet.EarExampleServlet.service(EarExampleServlet.java:63)
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)
--
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, 11 months
[JBoss JIRA] Created: (JBAS-3490) Test failure - org.jboss.test.aop.test.ObservableUnitTestCase
by Rajesh Rajasekaran (JIRA)
Test failure - org.jboss.test.aop.test.ObservableUnitTestCase
-------------------------------------------------------------
Key: JBAS-3490
URL: http://jira.jboss.com/jira/browse/JBAS-3490
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Test Suite
Affects Versions: JBossAS-4.0.5.CR1
Reporter: Rajesh Rajasekaran
Fix For: JBossAS-4.0.5.CR1
Test :org.jboss.test.aop.test.ObservableUnitTestCase (testAll)
Error:
RuntimeMBeanException: null Cause: java.lang.ClassCastException
at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:176)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:163)
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)
http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.0-testsuite-sun-1.4/2...
Server Log shows the following RunTimeException
http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.0-testsuite-sun-1.4/2...
2006-08-07 19:53:52,497 ERROR [STDERR] java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: Could not find interface for annotation org.jboss.cache.aop.annotation.InstanceOfPojoCacheable
2006-08-07 19:53:52,497 ERROR [STDERR] at org.jboss.aop.pointcut.Util.matchesClassExpr(Util.java:95)
2006-08-07 19:53:52,497 ERROR [STDERR] at org.jboss.aop.pointcut.FieldMatcher.visit(FieldMatcher.java:103)
2006-08-07 19:53:52,498 ERROR [STDERR] at org.jboss.aop.pointcut.ast.ASTField.jjtAccept(ASTField.java:43)
2006-08-07 19:53:52,498 ERROR [STDERR] at org.jboss.aop.pointcut.FieldMatcher.visit(FieldMatcher.java:157)
2006-08-07 19:53:52,498 ERROR [STDERR] at org.jboss.aop.pointcut.ast.ASTFieldExecution.jjtAccept(ASTFieldExecution.java:37)
2006-08-07 19:53:52,498 ERROR [STDERR] at org.jboss.aop.pointcut.MatcherHelper.visit(MatcherHelper.java:88)
--
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, 11 months
[JBoss JIRA] Resolved: (JBPORTAL-914) munges URLs but doesn't handle the common case of reference's resources
by Roy Russo (JIRA)
[ http://jira.jboss.com/jira/browse/JBPORTAL-914?page=all ]
Roy Russo resolved JBPORTAL-914.
--------------------------------
Fix Version/s: 3.0 Final
(was: 2.6 Final)
Resolution: Deferred
The problem lies in the editor being used, as it concretely defined the root path for all resources in the javascript wysiwyg page. This cannot be changed unless we replace the editor entirely, which is a possibility moving to fckeditor in 3.0.
> munges URLs but doesn't handle the common case of reference's resources
> -----------------------------------------------------------------------
>
> Key: JBPORTAL-914
> URL: http://jira.jboss.com/jira/browse/JBPORTAL-914
> Project: JBoss Portal
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: Portal CMS
> Affects Versions: 2.6 Final
> Environment: ALL
> Reporter: Ezra Epstein
> Assigned To: Roy Russo
> Priority: Minor
> Fix For: 3.0 Final
>
>
> The CMS should work with standard content. If an html file would work in an Apache server or as static content in JBoss it should work in the CMS. Thus if there's an <img> tag in an .html file referencing a file images/pretty.jpeg and that .html files is uploaded and so is the image the image should be found. But, oops, it won't be. Why not? Because (by default) the relative URL for the image under the CMS system is actually default/images/pretty.jpeg and not the original images/pretty.jpeg. It's fine for CMS to do this, but then CMSPortlet, since it munges relative URLs anyway, should account for this.
--
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, 11 months
[JBoss JIRA] Commented: (JBAS-3258) JDBC artificats should throw SQLException when already closed
by Ravi K (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3258?page=comments#action_12341344 ]
Ravi K commented on JBAS-3258:
------------------------------
Temporary Fix while we wait for 404SP1
If you are comfortable with enabling aspects here's a touch-free solution to the "Already closed" exceptions in 4.0.4. This works with JDK 5.0.
Put this class anywhere you like in your source:
---------------------------------------
package mypackage;
import java.sql.SQLException;
import org.jboss.aop.Bind;
import org.jboss.aop.InterceptorDef;
import org.jboss.aop.advice.Interceptor;
import org.jboss.aop.joinpoint.Invocation;
/**
* Temporary fix to JBoss's connection pool which throws an exception
* every time a JDBC resource is closed twice. This violates the
* JDBC API contract.
*
* In this aspect the close call is being wrapped and the false
* exception is being ignored.
*
* @author ravi
*/
@InterceptorDef
@Bind (pointcut="execution(* org.jboss.resource.adapter.jdbc.WrappedStatement->close())")
@Bind (pointcut="execution(* org.jboss.resource.adapter.jdbc.WrappedResultSet->close())")
public class JBossConnectionAspect implements Interceptor
{
public String getName()
{
return "JBossConnectionAspect";
}
public Object invoke(Invocation invocation) throws Throwable
{
try
{
return invocation.invokeNext();
}
catch(SQLException sqle)
{
/* Ignore false exceptions throw due to a JBoss bug */
if(sqle.getMessage().equals("Already closed"))
{
System.out.println("Aspectized wrapper: JBoss said resource already closed.");
return null;
}
else
{
throw sqle;
}
}
}
}
---------------------------------------
You might want to turn off the System.out if it gets too verbose.
Assuming you followed the standard instructions and JBoss is running the jboss-aof-jdk50.deployer just change base-aop.xml under ..\server\<servername>\deploy\jboss-aop-jdk50.deployer\
<aop>
<aspect class="mypackage.JBossConnectionAspect"/>
<bind pointcut="execution(public void org.jboss.resource.adapter.jdbc.WrappedStatement->close(..))">
<interceptor class="mypackage.JBossConnectionAspect"/>
</bind>
</aop>
ravi(a)pobox.com
> JDBC artificats should throw SQLException when already closed
> -------------------------------------------------------------
>
> Key: JBAS-3258
> URL: http://jira.jboss.com/jira/browse/JBAS-3258
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JCA service
> Affects Versions: JBossAS-4.0.4.GA
> Reporter: Adrian Brock
> Assigned To: Weston Price
> Fix For: JBossAS-4.0.4.SP1
>
>
> In the change to fix JBAS-2741 I mistakenly made the JDBC wrappers throw an SQL
> exception if the artifact is already closed. They should just return with an exception.
> From the Javadoc:
> "Calling the method close on a Statement object that is already closed has no effect."
> e.g. In WrappedStatement
> public void close() throws SQLException
> {
> synchronized (lock)
> {
> if (closed)
> throw new SQLException("Already closed");
> closed = true;
> }
> lc.unregisterStatement(this);
> internalClose();
> }
> this should be:
> public void close() throws SQLException
> {
> synchronized (lock)
> {
> if (closed)
> return;
> closed = true;
> }
> lc.unregisterStatement(this);
> internalClose();
> }
--
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, 11 months
[JBoss JIRA] Created: (JBMESSAGING-522) javax.jms.IllegalStateException: The session is closed
by Joel Lindheimer (JIRA)
javax.jms.IllegalStateException: The session is closed
------------------------------------------------------
Key: JBMESSAGING-522
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-522
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.0.1.CR4
Environment: Windows, JBoss 4.0.4.GA, Oracle
Reporter: Joel Lindheimer
Assigned To: Ovidiu Feodorov
We occasionally have test failures because a sender goes to get a Session. This stacktrace is from our Inbound message receiver receiver method; it has picked up a message and started processing it; it then goes to send a message to a queue, however it grabs a closed session:
2006-08-15 15:31:53,492 WARN [com.cc.commons.xmlgateway.receiver.impl.MessageReceiverImpl] Caught Throwable thrown from: processReceivedMessage().
com.cc.commons.exception.UnrecoverableException: Failed to send message. Message:(
<?xml version="1.0" encoding="UTF-8"?>
<XML>
(... removed long XML print here...)
</XML>
at com.cc.commons.jms.impl.JmsSenderImpl.send(JmsSenderImpl.java:679)
at com.cc.commons.xmlgateway.router.impl.MessageRouterImpl.routeMessage(MessageRouterImpl.java:161)
at com.cc.commons.xmlgateway.process.impl.MessageProcessorImpl.process(MessageProcessorImpl.java:78)
at sun.reflect.GeneratedMethodAccessor1113.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:334)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:181)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:148)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:100)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:170)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:209)
at $Proxy107.process(Unknown Source)
at com.cc.commons.xmlgateway.receiver.impl.MessageReceiverImpl.receiveInboundMessage(MessageReceiverImpl.java:397)
at com.cc.commons.xmlgateway.receiver.impl.MessageReceiverImpl.processReceivedMessage(MessageReceiverImpl.java:374)
at com.cc.commons.xmlgateway.receiver.impl.MessageReceiverImpl.receive(MessageReceiverImpl.java:213)
at sun.reflect.GeneratedMethodAccessor1109.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:334)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:181)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:148)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:100)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:170)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:209)
at $Proxy108.receive(Unknown Source)
at com.cc.commons.xmlgateway.jms.mdb.AbstractMessageReceiverMDB.processTextMessage(AbstractMessageReceiverMDB.java:71)
at com.cc.commons.xmlgateway.jms.mdb.AbstractMessageReceiverMDB.onMessageInternal(AbstractMessageReceiverMDB.java:44)
at com.cc.commons.jms.mdb.AbstractMDB$1.doInTransactionWithoutResult(AbstractMDB.java:68)
at org.springframework.transaction.support.TransactionCallbackWithoutResult.doInTransaction(TransactionCallbackWithoutResult.java:33)
at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:128)
at com.cc.commons.jms.mdb.AbstractMDB.onMessage(AbstractMDB.java:57)
at org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:802)
at org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:741)
at org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:711)
at com.cc.commons.jms.WMXDefaultMessageContainer102.doExecuteListener(WMXDefaultMessageContainer102.java:45)
at org.springframework.jms.listener.DefaultMessageListenerContainer.doReceiveAndExecute(DefaultMessageListenerContainer.java:511)
at org.springframework.jms.listener.DefaultMessageListenerContainer.receiveAndExecute(DefaultMessageListenerContainer.java:458)
at com.cc.commons.jms.WMXDefaultMessageContainer102.receiveAndExecute(WMXDefaultMessageContainer102.java:28)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:823)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:782)
at org.springframework.core.task.SimpleAsyncTaskExecutor$ConcurrencyThrottlingRunnable.run(SimpleAsyncTaskExecutor.java:203)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.jms.IllegalStateException: The session is closed
at org.jboss.resource.adapter.jms.JmsSession.getSession(JmsSession.java:115)
at org.jboss.resource.adapter.jms.JmsSession.getQueueSession(JmsSession.java:636)
at org.jboss.resource.adapter.jms.JmsSession.createSender(JmsSession.java:431)
at com.cc.commons.jms.impl.JmsSenderImpl.send(JmsSenderImpl.java:614)
... 42 more
--
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, 11 months