[JBoss Portal] - Migrating data
by JohnnyTheHun
I am migrating jbp data tables from mysql5 to oracle9. I am using jboss-portal-2.7.0.CR1.
I have used JBoss Portal to create it's own structure in Oracle.
Then I emptied all oracle tables and populated them with data from mysql.
But if I start JBoss, it wants to insert duplicate path values into jbp_object_node. And because oracle didn't let this it wouldn't start.
So i disabled the unique constraint to see what the portal does.
After this it was able to insert some default tables from it's own default-object.xml, but Hibernate threw an exception I pasted below.
My question is, if I copied the whole table structure and data, why does it still want to update it, even though it worked perfectly when I used mysql?
|
| 2009-02-26 03:07:15,375 ERROR [org.jboss.deployment.MainDeployer] Could not start deployment: file:/E:/utils/web/jboss-portal-2.7.0.CR1/server/default/deploy/jboss-portal.sar/conf/data/default-object.xml
| org.jboss.deployment.DeploymentException: query did not return a unique result: 2; - nested throwable: (org.hibernate.NonUniqueResultException: query did not return a unique result: 2)
| at org.jboss.portal.core.deployment.jboss.ObjectDeployment.start(ObjectDeployment.java:103)
| at org.jboss.portal.server.deployment.jboss.DeploymentContext.start(DeploymentContext.java:99)
| at org.jboss.portal.server.deployment.jboss.PortalDeploymentInfoContext.start(PortalDeploymentInfoContext.java:220)
| at org.jboss.portal.server.deployment.jboss.ServerDeployer.start(ServerDeployer.java:217)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
| 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 $Proxy211.deploy(Unknown Source)
| at org.jboss.portal.server.deployment.jboss.ServerDeployer.registerFactory(ServerDeployer.java:119)
| at org.jboss.portal.server.deployment.jboss.AbstractDeploymentFactory.registerFactory(AbstractDeploymentFactory.java:113)
| at org.jboss.portal.server.deployment.jboss.AbstractDeploymentFactory.start(AbstractDeploymentFactory.java:152)
| 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.portal.jems.as.system.JBossServiceModelMBean$ServiceMixin.execute(JBossServiceModelMBean.java:486)
| at org.jboss.portal.jems.as.system.JBossServiceModelMBean$ServiceMixin.startService(JBossServiceModelMBean.java:452)
| ....
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4213217#4213217
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4213217
17 years, 1 month
[JBoss Messaging] - Re: JBoss messaging client timeout
by pratimkm
Howard,
while we are testing failover I am seeing this in the logs
WARN org.jboss.remoting.Client - unable to remove remote callback handler: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://***:4457/?JBM_clientMaxPoolSize=500&clientLeasePeriod=50000&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&connectionWait=60000&dataType=jms&marshaller=org.jboss.jms.wireformat.JMSWireFormat&numberOfCallRetries=1&numberOfRetries=30&pingFrequency=214748364&pingWindowFactor=10&socket.check_connection=false&stopLeaseOnFailure=true&timeout=0&unmarshaller=org.jboss.jms.wireformat.JMSWireFormat&validatorPingPeriod=10000&validatorPingTimeout=50000]
As you suggested I had increased clientLeasePeriod to 50000 and validatorPingTimeout to 50000. Those seems to be passed to the client now which we see in the logs. But still we are seeing this socket connection timeout for a few messages after a long idle time.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4213211#4213211
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4213211
17 years, 1 month