[JBossCache] - Problem with JBoss JDBCCacheLoader
by archanaa_panda
Hello,
We are using JBoss Cache 1.3 for our project which is under development. Recently while doing some performance testing we found a problem with the JDBC Cache Loader (we are using an Oracle database as the backing store for our JBoss Cache). When we run with multiple threads or sometimes even one thread, we get the following exception:
java.lang.RuntimeException: java.lang.IllegalStateException: Failed to insert node: ORA-00001: unique constraint (FASTDEV.JBOSSCACHE_PK) violated at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:4810)
at org.jboss.cache.TreeCache.put(TreeCache.java:3242)
at com.sisl.ashleycomm.cache.CacheTimeoutManager.putCacheable(CacheTimeoutManager.java:452)
at com.sisl.ashleycomm.cache.push.command.MobilePushCacheTimeoutManager.putCacheable(MobilePushCacheTimeoutManager.java:168)
at com.sisl.ashleycomm.cache.DefaultCacheableVersionProxy.processEvent(DefaultCacheableVersionProxy.java:134)
at com.sisl.ashleycomm.cache.push.command.MobilePushCacheTimeoutManager.getMobilePushCommandsForGprsSend
Caused by: java.lang.IllegalStateException: Failed to insert node: ORA-00001: unique constraint (FASTDEV.JBOSSCACHE_PK) violated
at org.jboss.cache.loader.JDBCCacheLoader.insertNode(JDBCCacheLoader.java:982)
at org.jboss.cache.loader.JDBCCacheLoader.put(JDBCCacheLoader.java:325)
at org.jboss.cache.interceptors.CacheStoreInterceptor.invoke(CacheStoreInterceptor.java:202)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:67)
at org.jboss.cache.interceptors.CacheLoaderInterceptor.invoke(CacheLoaderInterceptor.java:187)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:67)
at org.jboss.cache.interceptors.UnlockInterceptor.invoke(UnlockInterceptor.java:32)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:67)
at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInterceptor.java:32)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:67)
at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:328)
at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:139)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:67)
at org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:153)
at org.jboss.cache.TreeCache.invokeMethod(TreeCache.java:4804)
Actually the scenario is like this:
A thread gets a node on the cache and then does some modification on the node and tries to put it back on the cache.
There may be multiple threads accessing the same node.
Looking at the source code of JBoss Cache 1.3, I find that when put() is called on JDBCCacheLoader, loadNode() method is called. Apparantly this is returning null so the insertNode() is being called. But then when it tries to do the insertNode, it gets the PK violated error which indicates the row was existing in the database already!!!
What are the precautions we need to take to avoid this problem? Is our setting wrong?
A quick reply would be very much appreciated. Please let me know if there are more details required for diagnosing the problem
Thanks and Regards,
Archanaa Panda
Following are the details of our cache config xml file-
<attribute name="TransactionManagerLookupClass">org.jboss.cache.DummyTransactionManagerLookup</attribute>
| <attribute name="IsolationLevel">READ_COMMITTED</attribute>
| <attribute name="CacheMode">REPL_SYNC</attribute>
|
|
| <attribute name="CacheLoaderConfiguration">
| <config>
| <passivation>false</passivation>
| <preload>/</preload>
| <shared>true</shared>
| <cacheloader>
| <class>org.jboss.cache.loader.JDBCCacheLoader</class>
| <properties>
| cache.jdbc.table.name=jbosscache
| cache.jdbc.table.create=true
| cache.jdbc.table.drop=false
| cache.jdbc.table.primarykey=jbosscache_pk
| cache.jdbc.fqn.column=fqn
| cache.jdbc.fqn.type=varchar(255)
| cache.jdbc.node.column=node
| cache.jdbc.node.type=blob
| cache.jdbc.parent.column=parent
| cache.jdbc.driver=oracle.jdbc.driver.OracleDriver
| cache.jdbc.url=jdbc:oracle:thin:@132.186.106.26:1541:ACRMDEV
| cache.jdbc.user=FASTDEV
| cache.jdbc.password=fastdev123$
| </properties>
| <async>false</async>
| <fetchPersistentState>true</fetchPersistentState>
| <ignoreModifications>false</ignoreModifications>
| </cacheloader>
| </config>
| </attribute>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990965#3990965
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990965
19 years, 7 months
[JBoss Portal] - unable to deploy jboss portal (build created from open sourc
by anjana
I have created the jboss-portal.sar from open source jboss portal version 2.4. when i try to deploy onn jboss 4.04.GA if fails with following exception
2006-12-04 16:26:34,055 DEBUG [org.jboss.portal.portlet.container.PortletContainer] Loading portlet class org.jboss.portal.core.portlet.test.BasicPortlet
2006-12-04 16:26:34,055 DEBUG [org.jboss.portal.portlet.container.PortletContainer] Creating portlet object org.jboss.portal.core.portlet.test.BasicPortlet
2006-12-04 16:26:34,070 DEBUG [org.jboss.portal.portlet.container.PortletContainer] Created portlet object org.jboss.portal.core.portlet.test.BasicPortlet
2006-12-04 16:26:34,070 DEBUG [org.jboss.portal.portlet.container.PortletContainer] Initialized portlet object org.jboss.portal.core.portlet.test.BasicPortlet
2006-12-04 16:26:34,070 DEBUG [org.jboss.portal.core.deployment.jboss.PortletAppDeployment] Looking for the WEB-INF path of samples
2006-12-04 16:26:34,084 ERROR [org.jboss.portal.core.deployment.jboss.PortletAppDeployment] Error when creating instances
org.hibernate.HibernateException: Unable to locate current JTA transaction
i have create the portal-mysql-ds.xml with following entries
<?xml version="1.0" encoding="UTF-8"?>
<local-tx-datasource>
<jndi-name>PortalDS</jndi-name>
<connection-url>jdbc:mysql://localhost:3306/jbossportal?useServerPrepStmts=false&jdbcCompliantTruncation=false</connection-url>
<driver-class>org.gjt.mm.mysql.Driver</driver-class>
<user-name>portal</user-name>
portalpassword
</local-tx-datasource>
the above file is copied into Jboss folder
\server\default\deploy
can anyone pls guide what is missiing in my environment
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990964#3990964
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990964
19 years, 7 months
[EJB 3.0] - Re: @PrePersist @PreUpdate within @AroundInvoke results in c
by gnulp
but that means that you have NO chance to intercept a business-logic call from a client who is doing an update on an entity that has cascading enabled !!!
Assume 2 entities e.g. person [1:n] address. You have got a business-method that can be called with person as an attribute only, and the client changed a referenced address-object (remember cascade all is enabled !). So we get a call-back in the pre-update-Method of the address, but we will never know that in the interceptor of the business-logic call, due to the late update-callback (unfortunaltelly we can not use an entityManager in listener-callbacks, but we have also no chance doing this in an interceptor !!!)
In other words I would have to check weather any address-object has changed myself although I am using ejb3 that is doing these things anyhow ! So why am I using ejb3, if I have to reinvent the wheel ?
Thx for any feedback
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990963#3990963
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990963
19 years, 7 months
[Messaging, JMS & JBossMQ] - Re: JBossMQ Fails under load - Exiting on IOE
by alchemista
I'm still having the same problem. If there is an ERROR in the log, I would not ignore it, if it's just a DEBUG or INFO maybe. My connection will hard-die (i.e. never come back to life) after this error occurs too often.
On the server-side, the server.log throws the following error around the time the client gives the error posted earlier.
2006-11-30 16:31:34,159 ERROR [org.jboss.ejb.plugins.LogInterceptor] Unexpected
Error in method: public abstract void javax.jms.MessageListener.onMessage(javax.jms.Message)
java.lang.OutOfMemoryError: Java heap space
2006-11-30 16:31:34,160 ERROR [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Exception in JMSCI message listener
javax.ejb.EJBException: Unexpected Error
java.lang.OutOfMemoryError: Java heap space
at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:395)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:196)
at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122)
at org.jboss.ejb.MessageDrivenContainer.internalInvoke(MessageDrivenContainer.java:389)
at org.jboss.ejb.Container.invoke(Container.java:873)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.invoke(JMSContainerInvoker.java:1090)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$MessageListenerImpl.onMessage(JMSContainerInvoker.java:1392)
at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:256)
at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:904)
at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:160)
at org.jboss.mq.SpySession.run(SpySession.java:333)
at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:180)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
at java.lang.Thread.run(Thread.java:595)
2006-11-30 16:33:32,663 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin ReadTask.run
2006-11-30 16:33:32,663 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin WriteTask.run
2006-11-30 16:33:32,663 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created ObjectInputStream
2006-11-30 16:33:32,663 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created ObjectOutputStream
2006-11-30 16:33:32,667 DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler]
Setting up the UILClientIL Connection
2006-11-30 16:33:32,667 DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler]
The UILClientIL Connection is set up
2006-11-30 16:34:59,549 ERROR [org.jboss.mq.il.uil2.SocketManager] Failed to handle: org.jboss.mq.il.uil2.msgs.AddMsg20684031[msgType: m_addMessage, msgID: -2147473491, error: null]
java.lang.OutOfMemoryError: Java heap space
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990961#3990961
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990961
19 years, 7 months
[EJB/JBoss] - Almost identical session beans, one works one fails
by Melladh
The failing one is looked up like this, and I get a "not bound" exception when activating the servlet it's called from.
Context context = new InitialContext();
| Object listRef = context.lookup("java:comp/env/ejb/ListApplicants");
|
The working one is looked up the same way, except that it's called Applicant instead of ListApplicants. All the configurations look the same.
Home interface
package ejb;
|
| /**
| * Home interface for ListApplicants.
| */
| public interface ListApplicantsHome
| extends javax.ejb.EJBHome
| {
| public static final String COMP_NAME="java:comp/env/ejb/ListApplicants";
| public static final String JNDI_NAME="ejb/ListApplicants";
|
| public ejb.ListApplicants create(java.lang.String param)
| throws javax.ejb.CreateException,java.rmi.RemoteException;
|
| }
|
jboss.xml
<session>
| <ejb-name>ListApplicants</ejb-name>
| <jndi-name>ejb/ListApplicants</jndi-name>
| <local-jndi-name>ListApplicantsLocal</local-jndi-name>
| </session>
ejb-jar.xml
<session >
| <description><![CDATA[Description for ListApplicants]]></description>
| <display-name>Name for ListApplicants</display-name>
|
| <ejb-name>ListApplicants</ejb-name>
|
| <home>ejb.ListApplicantsHome</home>
| <remote>ejb.ListApplicants</remote>
| <ejb-class>ejb.ListApplicantsBean</ejb-class>
|
| <session-type>Stateful</session-type>
| <transaction-type>Container</transaction-type>
|
| </session>
This looks exactly the same for my ApplicantBean, with the names changed accordingly, and that one works! This one doesn't. Anyone have a clue about what's wrong?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990953#3990953
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990953
19 years, 7 months
[EJB 3.0] - SocketException converted into UndeclaredThrowableException
by metelka
Hi,
I have a problem with exception reporting in EJB3 remote calls. My remote client has 20s timeout on remote calls and the timeout works fine, however the timeout exception is converted into UndeclaredThrowableException by jboss remoting/ejb3 invocation interceptors. I would expect to receive some kind of communication exception or remoting exception, which I could handle in my client code. Any ideas?
Thanks
SW versions: JBoss 4.0.4GA, EJB3 RC9, JBoss Remoting 1.4.4.
My stacktrace:
anonymous wrote :
| 2006-11-30 17:01:37,334 FATAL [cz.tipsport.pluginsys.gui.ApplicationUncaughtExceptionHandler] (AWT-EventQueue-0:) Unchecked exception thrown!
| java.lang.reflect.UndeclaredThrowableException
| at $Proxy44.findAddressees(Unknown Source)
| at cz.tipsport.tip.dms.gui.addressee.gui.AddresseeSelectorPanelCtl.(AddresseeSelectorPanelCtl.java:156)
|
| ... not important ...
|
| Caused by: java.rmi.MarshalException: Socket timed out. Waited 20000 milliseconds for response while calling on InvokerLocator [socket://172.16.19.42:3673/?timeout=20000]; nested exception is:
| java.net.SocketTimeoutException: Read timed out
| at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:302)
| at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143)
| at org.jboss.remoting.Client.invoke(Client.java:525)
| at org.jboss.remoting.Client.invoke(Client.java:488)
| at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
| at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
| at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:55)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
| at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:77)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
| at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102)
| ... 114 more
| Caused by: java.net.SocketTimeoutException: Read timed out
| at java.net.SocketInputStream.socketRead0(Native Method)
| at java.net.SocketInputStream.read(SocketInputStream.java:129)
| at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
| at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
| at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2200)
| at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2490)
| at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2500)
| at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1267)
| at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339)
| at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:128)
| at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:66)
| at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:279)
| ... 126 more
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990952#3990952
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990952
19 years, 7 months
[JBoss AOP] - Re: Bug in SuperClassesFirstWeavingStrategy?
by stalep
hm, its quite possible that we have several concurrent issues with the generated advisors instrumentation that uses SuperClassesFirstWeavingStrategy.
you can easily tell jboss aop to use a different instrumentor (its only from jboss aop 2.0 that generated advisors are default instrumentor).
add this property to either aopc or as a systemproperty when you run the program:
| jboss.aop.instrumentor = org.jboss.aop.instrument.ClassicInstrumentor
|
then you will get the "old" instrumentor, please let us know if you still have the problem with this instrumentor.
to get more verbose output (and which instrumenter thats used) set this property to true: "jboss.aop.verbose"
- and yes, jboss aop will load all classes into its instrumentor to check if the class match any of the pointcuts/aspects/etc. if it doesnt match anything it doesnt do anything, but it will check all classes.
thanks for the info and good work btw, these kinds of bugs isnt very easy to reproduce in a test so real world apps and feedback are very appreciated.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990947#3990947
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990947
19 years, 7 months
[JBossWS] - problems in deploying jbossws-1.0.4 with jboss-4.0.5.GA
by MmarcoM
HI ALL,
i have just installed jboss-4.0.5.GA (was coming wth jbossws-1.0.3)...
deployed my app (J2EE-1.4 WS), everything is fine
i have then upgraded to jbossws-1.0.4 (replacing proper files)..and when i restart the server i got following exception
| 2006-12-04 11:09:50,359 ERROR [org.jboss.deployment.MainDeployer] Could not create deployment: file:/D:/Sw/jboss-4.0.5.GA/server/default/tmp/deploy/tmp16811ngenMiddlewareEAR-1.0-SNAPSHOT.ear-contents/ngenMiddleware-1.0-SNAPSHOT.jar
| java.lang.NullPointerException
| at org.jboss.ws.integration.jboss.DeployerInterceptor.getServiceEndpointDeployer(DeployerInterceptor.java:142)
| at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:80)
| at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44)
| at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
| at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy27.create(Unknown Source)
| at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
| at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy6.deploy(Unknown Source)
| at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
| at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| 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)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| 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)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy4.start(Unknown Source)
| at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy5.deploy(Unknown Source)
| at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
| at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
| at org.jboss.Main.boot(Main.java:200)
| at org.jboss.Main$1.run(Main.java:490)
| at java.lang.Thread.run(Thr
|
i have seen some threads about that in the forum, if i remember one of replies was that jbossws was compatible with ejb3-rc9..
but jboss 4.0.5.GA has within rc9 of ejbs... can anyone help me out in finding out what's theproblem?
thanks in advance and regards
Marco
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990944#3990944
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990944
19 years, 7 months
[JBoss Portal] - IPC using AJAX
by sirishy
I'm using Jboss Portal 2.4 bundled version.
Currently I've implemented IPC scenario without Ajax as follows:
I made the image as a link and onclick of the image in portlet A, I'm sending the imageName as hidden parameter using javascript to the portletA.java.
In this java file, in processAction() method, I'm getting the imageName and setting it in the portlet session (APPLICATION_SCOPE).
In portletB.java, in doView() method I'm getting the imageName from the APPLICATION_SCOPE. Depending on this value (i.e., if imageName != null)I'm displaying a HTML page in portlet B.
I have both the portlets in the same war file.
portlet A and portlet B are visible on the page for the first time.
It reloads the entire page onclick of the image in portlet A, thus influencing the portlet B.
I want the scenario to be as follows:
Only portlet A should be visible for the first time.
Onclick of the image in portlet A, on the fly portlet B should come up without reloading the entire page.
thanks,
sirishy
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990943#3990943
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990943
19 years, 7 months
[JBoss Seam] - Re: Oracle ADF
by lowecg2004
Gavin,
Yes a good advert for "don't drink and drive" ;) Apology accepted.
As stated in my post, it was only speculation and I was clearly wrong. While my assumption now appears rather naive (and, yes, I feel suitably embarrassed) please appreciate that many us on the forum are not yet well versed in the subtleties of AOP and classloading. In my class cast example I was able to bind to a regular managed bean but not via a Seam binding "because Seam used a different classloading mechanism to get the underlying class". Surely this IS quite subtle from a regular Seam programmers pov? Is this something that could be cleared up in the Seam reference, say introduce a section from a "Seam and the JEE environment" interaction perspective?
I would have taken the time to acquaint myself with the subtleties of JEE classloading but having read that documentation you'll know that stuff is not exactly 'light' reading hence my polite request for direction to the required material. RTFM is often a fair response but when the 'M' is something as big and vague as the JEE spec then some direction would be appreciated.
I agree with you that preprender does not work under Seam. I personally DO NOT want to be dealing with the raw JSF component instances. But let's face it, there will be a lot of people migrating to Seam from JSC who are used to having exactly that sort of experience of JSF programming. I only got onto to this because of the way in which the Trinidad built-in table selections work. Again, maybe something in the Seam reference could 'educate' people who may be used to other JSF programming models?
Anyway please accept my apologies if I upset you. I really appreciate the help you are giving myself and others on this forum. I will refrain from speculation from now on and I will now go away to read up on classloading and try to understand what's going on.
Best Regards,
Chris.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990940#3990940
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990940
19 years, 7 months
[JBoss/Spring Integration] - Re: NoSuchMethodError when trying to deploy sample ear
by sneha.munnangi
Hi Ales,
I upgraded my spring from spring-1.2.7 to spring-2.0 and I am using the jboss spring deployer jboss-spring-version4, still I am getting the same error.
I have my spring.jar in server/default/lib
Besides my jboss-spring.deployer contains following items.
spring-aop.jar
spring-beans.jar
spring-context.jar
jboss-spring.jar
spring-core.jar
META-INF/jboss-service.xml.
The error which I am getting is
| ERROR [MainDeployer] Could not create deployment: file:/usr/local/jboss/server/default/deploy/jboss-spring.xml
| INFO | jvm 1 | 2006/12/03 05:06:58 | org.jboss.deployment.DeploymentException: Unexpected exception parsing XML document from URL [file:/usr/local/jboss/server/
| fault/tmp/deploy/tmp31505jboss-spring.xml]; nested exception is java.lang.NoSuchMethodError: org.jboss.spring.factory.NamedXmlBeanDefinitionReader: method createRead
| Context(Lorg/springframework/core/io/Resource;)Lorg/springframework/beans/factory/support/ReaderContext; not found; - nested throwable: (org.springframework.beans.fa
| ory.BeanDefinitionStoreException: Unexpected exception parsing XML document from URL [file:/usr/local/jboss/server/default/tmp/deploy/tmp31505jboss-spring.xml]; nest
| exception is java.lang.NoSuchMethodError: org.jboss.spring.factory.NamedXmlBeanDefinitionReader: method createReaderContext(Lorg/springframework/core/io/Resource;)L
| g/springframework/beans/factory/support/ReaderContext; not found)
|
Please suggest.I have been struck at it from quite a long time.
Is this some problem with the order of deployment?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990933#3990933
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990933
19 years, 7 months
[Installation, Configuration & Deployment] - Concurrent scheduler tasks?
by kresho
I have two tasks that should be executed at different schedules, so I created to Schedulable classes and deployed two mbeans:
Task 1 (nightly):
<server>
| <mbean code="org.jboss.varia.scheduler.Scheduler" name="hr.chipoteka.erp.nightly-tasks:service=Scheduler">
| <depends>jboss.j2ee:service=EJB,jndiName=ejb/NightlyTasksLocal</depends>
|
| <attribute name="StartAtStartup">true</attribute>
| <attribute name="SchedulableClass">hr.chipoteka.erp.server.NightlyTasksBean</attribute>
|
| <attribute name="DateFormat">yyyy-MM-dd HH:mm:ss</attribute>
| <attribute name="InitialStartDate">2006-10-30 21:30:00</attribute>
| <!-- attribute name="SchedulePeriod">60000</attribute -->
| <attribute name="SchedulePeriod">86400000</attribute>
|
| <attribute name="InitialRepetitions">-1</attribute>
| </mbean>
| </server>
|
And task 2 (every 10 seconds):
<server>
| <mbean code="org.jboss.varia.scheduler.Scheduler" name="hr.chipoteka.erp.synchronizer:service=Scheduler">
| <depends>jboss.j2ee:service=EJB,jndiName=ejb/SynchronizerLocal</depends>
|
| <attribute name="StartAtStartup">true</attribute>
| <attribute name="SchedulableClass">hr.chipoteka.erp.server.SynchronizerBean</attribute>
|
| <attribute name="DateFormat">yyyy-MM-dd HH:mm:ss</attribute>
| <attribute name="InitialStartDate">2006-11-01 00:00:00</attribute>
| <attribute name="SchedulePeriod">10000</attribute>
|
| <attribute name="InitialRepetitions">-1</attribute>
| </mbean>
| </server>
|
jboss.app:
<?xml version="1.0"?>
|
| <jboss-app>
| <module>
| <har>hibernate-service.xml</har>
| </module>
| <module>
| <service>chipoteka-erp-nightly-tasks-scheduler-service.xml</service>
| </module>
| <module>
| <service>chipoteka-erp-synchronizer-scheduler-service.xml</service>
| </module>
| </jboss-app>
|
Sometimes execution times of these tasks overlap, but instead of being started concurrently, the scheduler starts them one after the other. How do I make them independent of one another and have them started at their schedules concurrently?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990932#3990932
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990932
19 years, 7 months