[Installation, Configuration & DEPLOYMENT] - Could not restore EJB timers error
by kmekme
Hi everyone,
I've installed JBoss AS and portal on two machines (2 nodes on a machine and the other one on the other) , it worked fine at first. But now, I've got this error on 2 of my nodes :
| 08:10:41,777 INFO [ClusterFileTransfer] Finished cluster pull of file hgpp_patient_ejb_worklist_jdbc.jar to hgpp_patient_ejb_worklist_jdbc.jar
| 08:10:41,777 INFO [ClusterFileTransfer] Start pull of file hgpp_patient_ejb_identite_xwayjdbc.jar from cluster.
| 08:10:41,791 INFO [ClusterFileTransfer] Finished cluster pull of file hgpp_patient_ejb_identite_xwayjdbc.jar to hgpp_patient_ejb_identite_xwayjdbc.jar
| 08:10:41,791 INFO [ClusterFileTransfer] Start pull of file hgpp_patient_ejb_cim_xwayjdbc.jar from cluster.
| 08:10:41,800 INFO [ClusterFileTransfer] Finished cluster pull of file hgpp_patient_ejb_cim_xwayjdbc.jar to hgpp_patient_ejb_cim_xwayjdbc.jar
| 08:10:42,292 INFO [EjbModule] Deploying fr_mckesson_common_ejb_auditreader
| 08:10:42,484 INFO [ProxyFactory] Bound EJB Home 'fr_mckesson_common_ejb_auditreader' to jndi 'fr_mckesson_common_ejb_auditreader'
| 08:10:42,486 WARN [StatelessSessionContainer] Could not restore ejb timers
| javax.management.RuntimeMBeanException
| 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)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.ejb.Container.restoreTimers(Container.java:771)
| at org.jboss.ejb.SessionContainer.startService(SessionContainer.java:410)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| at sun.reflect.GeneratedMethodAccessor5.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.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.GeneratedMethodAccessor10.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)
|
I'm using JBoss 4.2.2 & Portal 2.6.4 and I've some EJB in the farm folder.
Anybody?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144270#4144270
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144270
18 years, 3 months
[JBoss Messaging] - Re: MQ migration help
by clebert.suconic＠jboss.com
anonymous wrote :
| 1. Change the DefaultDS to use MySQL XA connections. Can more than 1 node share the same database on MySQL if I set up the DefaultDS to point to the same database across all nodes?
You actually need a shared database across the nodes to guarantee a proper failover. You don't need XA on the Database though... just simple transactions. When you open a jms.Connection in XA mode we already control our transactions to the database.
anonymous wrote :
| 2. Define a new Datasource and point each node to the same database.
|
| All databases will be in MySQL cluster.
Same as above, right?
http://wiki.jboss.org/wiki/JBMSpringJMSTemplateNotes
anonymous wrote : However, it doesn't point to a good way to connect from POJO clients outside the container. Can anyone point me to an article so that I can implement a JBoss "approved" JMSTemplate with connection pooling? These client queues will need to be XA compatible.
|
|
Well.. IMO that is a Spring issue. You definitely need to reuse your connections. Creating a new connection on every message receive is not practical with any JMS provider. You'd better find help on Spring guys.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144254#4144254
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144254
18 years, 3 months
[EJB/JBoss] - Accessing Applet behind NAT firewall [EJB application]
by SandeepDJboss
Hi Everyone,
I need to know the details of using applet based application in JBOSS - the clients are connecting from NAT enviornments.
I have implementd RMI over HTTP protocol for EJB communication.
But the Client Connect address configuration which is used in Nat'ed IP scenario is to be done at startup.
Even the configuration in HTTP-invoker.sar file where we can form the URL has to be done at the start up; if I provide the NAT IP which client uses here then it binds the domain to that particular client only.
And the same domain can not be used by any other client as they might NAT to diffrent IP.
I need a solution which will allow me to form the URL's from the client end using NAT IP at the runtime; if this can be done the same JBOSS instance can be used by all clients - thos who NAT and those who do not NAT as well.
Please suggest a way out if you have come across similar issue where you need to support many clients out of the same domain and some of them NAT the IP's on client side.
Any help on this will be very much appreciated !!
Thank you
Sandeep
The JBOSS remoting document says that the ClientConnectAddress can not be changed at the runtime.
5.4.2. Configurations affecting the invoker client
There are some configurations which will impact the invoker client. These will be communicated to the client invoker
via parameters in the Locator URI. These configurations can not be changed during runtime, so can only be
set up upon initial configuration of the server invoker on the server side. The following is a list of these and their
effects.
clientConnectPort - the port the client will use to connect to the remoting server. This would be needed in the case
that the client will be going through a router that forwards requests made externally to a different port internally.
clientConnectAddress - the ip or hostname the client will use to connect to the remoting server. This would be
needed in the case that the client will be going through a router that forwards requests made externally to a different
ip or host internally.
If no client connect address or server bind address specified, will use the local host's address (via InetAddress.
getLocalHost().getHostAddress() ).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144251#4144251
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144251
18 years, 3 months
[JBoss Messaging] - Clustered server preference
by chip_schoch
JBoss AS 4.2.2.ga, JBM1.4.0.SP1.
I several clients that connect to a 2 machine cluster (devapp1 and devapp2). Below is the JMSProvider I use. On one machine I have the naming provider with devapp1 first in the list. On the second I have devapp2, as shown here. The second machine always connects to devapp1 unless I completely remove the reference to devapp1 from the list. Then it it will connect to devapp2. I thought it was supposed to try to connect in the order that they are listed in java.naming.provider.url. Is this an incorrect assumption?
I am able to determine which machine it has connection by looking at the number of consumers the app servers have connected to them.
<mbean code="org.jboss.jms.jndi.JMSProviderLoader"
| name="jboss.messaging:service=JMSProviderLoader,name=ConversionJMSProvider">
| <attribute name="ProviderName">ConversionJMSProvider</attribute>
| <attribute name="ProviderAdapterClass">
| org.jboss.jms.jndi.JNDIProviderAdapter
| </attribute>
|
| <attribute name="FactoryRef">ClusteredXAConnectionFactory</attribute>
| <attribute name="QueueFactoryRef">ClusteredXAConnectionFactory</attribute>
| <attribute name="TopicFactoryRef">ClusteredXAConnectionFactory</attribute>
|
| <attribute name="Properties">
| java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
| java.naming.provider.url=jnp://devapp2.qa.cin.int:1100,jnp://devapp1.qa.cin.int:1100
| jnp.disableDiscovery=true
| jnp.partitionName=dev.application
| jnp.discoveryGroup=228.1.2.4
| jnp.discoveryPort=1102
| jnp.discoveryTTL=16
| jnp.discoveryTimeout=5000
| jnp.maxRetries=1
| </attribute>
| </mbean>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144247#4144247
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144247
18 years, 3 months
[JBoss Tools (users)] - Problem with freemarker plugin
by dinger55
I get the following stack trace when I try to open a file in eclipse using the freemarker plugin:
!ENTRY org.eclipse.ui.workbench 4 2 2008-04-15 15:28:57.770
| !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
| !STACK 0
| java.lang.NullPointerException
| at org.jboss.ide.eclipse.freemarker.model.ItemSet.<init>(ItemSet.java:56)
| at org.jboss.ide.eclipse.freemarker.editor.Editor.getItemSet(Editor.java:271)
| at org.jboss.ide.eclipse.freemarker.outline.OutlinePage.update(OutlinePage.java:119)
| at org.jboss.ide.eclipse.freemarker.outline.OutlinePage.setInput(OutlinePage.java:93)
| at org.jboss.ide.eclipse.freemarker.editor.Editor.getAdapter(Editor.java:106)
| at org.jboss.ide.eclipse.freemarker.editor.FreemarkerMultiPageEditor.getAdapter(FreemarkerMultiPageEditor.java:344)
| at org.eclipse.ui.internal.views.ViewsPlugin.getAdapter(ViewsPlugin.java:103)
| at org.eclipse.ui.views.contentoutline.ContentOutline.doCreatePage(ContentOutline.java:129)
| at org.eclipse.ui.part.PageBookView.createPage(PageBookView.java:399)
| at org.eclipse.ui.part.PageBookView.partActivated(PageBookView.java:741)
| at org.eclipse.ui.views.contentoutline.ContentOutline.partBroughtToTop(ContentOutline.java:210)
| at org.eclipse.ui.internal.PartListenerList$2.run(PartListenerList.java:87)
| at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
| at org.eclipse.core.runtime.Platform.run(Platform.java:857)
| at org.eclipse.ui.internal.PartListenerList.fireEvent(PartListenerList.java:57)
| at org.eclipse.ui.internal.PartListenerList.firePartBroughtToTop(PartListenerList.java:85)
| at org.eclipse.ui.internal.PartService.firePartBroughtToTop(PartService.java:87)
| at org.eclipse.ui.internal.WorkbenchPagePartList.firePartBroughtToTop(WorkbenchPagePartList.java:75)
| at org.eclipse.ui.internal.WorkbenchPagePartList.fireActiveEditorChanged(WorkbenchPagePartList.java:51)
| at org.eclipse.ui.internal.PartList.setActiveEditor(PartList.java:152)
| at org.eclipse.ui.internal.WorkbenchPage.makeActiveEditor(WorkbenchPage.java:1224)
| at org.eclipse.ui.internal.WorkbenchPage.setActivePart(WorkbenchPage.java:3395)
| at org.eclipse.ui.internal.WorkbenchPage.activate(WorkbenchPage.java:611)
| at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2748)
| at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2651)
| at org.eclipse.ui.internal.WorkbenchPage.access$13(WorkbenchPage.java:2643)
| at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2595)
| at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
| at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2590)
| at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2574)
| at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2557)
| at org.eclipse.ui.ide.IDE.openEditorOnFileStore(IDE.java:1090)
| at org.eclipse.ui.internal.ide.actions.OpenLocalFileAction.run(OpenLocalFileAction.java:105)
| at org.eclipse.ui.internal.ide.actions.OpenLocalFileAction.run(OpenLocalFileAction.java:75)
| at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:256)
| at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:229)
| at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:546)
| at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490)
| at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402)
| at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
| at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
| at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
| at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
| at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
| at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
| at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
| at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
| at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
| at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
| at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
| at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
| at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
| at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
| at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
| at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
| at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
| at java.lang.reflect.Method.invoke(Unknown Source)
| at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
| at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
| at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
Any ideas?
Rob
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144246#4144246
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144246
18 years, 3 months