[Management, JMX/JBoss] - Migration issues from previous versions(JBOSS 3.2.x) to JBOS
by faisalhelpline
I have made an application which is clustered enabled. but i am facing few issues while porting it onto jBOSS4.0.5, its perfectly running in JBOSS-3.2.6
1-HARMIProxyCallBack interface not found, in JBOSS-4.0.5 what is the alternate of it.
i had RMIListnerMBean which is extends ServiceMBeanSupport and implements HARMIProxyCallback
and in the start Service Method i was doing something like
String fullPartitionName = "/HAPartition/DefaultPartition";
context = new InitialContext();
partition = (HAPartition) context.lookup(fullPartitionName);
// Create a clustered Proxy/stub
msghandler = new MyMessageHandler();//my own class extending the Listner Class
myHARMIServer = new HARMIServerImpl(partition, "RmiMessageServer", Listener.class,
msghandler, 0, null, null, null, this);
stub = myHARMIServer.createHAStub(new RoundRobin());
rebind();
should i port this code other way..? to make it compatible with JBOSS4.0.5
2-getting error while invoking on
context = new InitialContext();
adaptor = (RMIAdaptor) context.lookup("jmx/rmi/RMIAdaptor");
ObjectName objName = new ObjectName("txt:config=Core");
Object obj = adaptor.invoke(objName, "getCoreDBSource",null, null);
this piece of code is working fine in 3.2.6 version.
i read somewhere that in new versions we should use MBeanServerConnection instead of RMIAdaptor i used it but still getting exception:
javax.management.ReflectionException
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInv
is there any need... to extend MBean from certain classes or implement any interface?
my MBean is very simple..
extending HAServiceMBeanSupport and implementing NotificationListener.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4044789#4044789
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4044789
19 years, 1 month
[JBoss Seam] - How to decrypt this (Seam's exception) error message?
by tonylmai
Hello,
I am new in writing JSF. I have no doubt that my pages are full of bugs. How do I go about debugging the pages to figure out what error Seam is referring to?
For example, Seam threw the following exception in the log:
anonymous wrote : 12:04:44,734 ERROR [STDERR] May 10, 2007 12:04:44 PM com.sun.facelets.FaceletViewHandler handleRenderException
| SEVERE: Error Rendering View[/pending_orders.xhtml]
| java.lang.IllegalArgumentException
| at javax.faces.component.UIComponentBase$AttributesMap.put(UIComponentBase.java:1577)
| at javax.faces.component.UIComponentBase$AttributesMap.put(UIComponentBase.java:1504)
| at com.sun.facelets.tag.jsf.ComponentRule$LiteralAttributeMetadata.applyMetadata(ComponentRule.java:49)
| at com.sun.facelets.tag.MetadataImpl.applyMetadata(MetadataImpl.java:36)
| at com.sun.facelets.tag.MetaTagHandler.setAttributes(MetaTagHandler.java:62)
| at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:144)
| at com.sun.facelets.tag.jstl.core.ChooseWhenHandler.apply(ChooseWhenHandler.java:45)
| at com.sun.facelets.tag.jstl.core.ChooseHandler.apply(ChooseHandler.java:68)
| at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
| at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:314)
| at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:169)
| at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
| at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:314)
| at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:169)
| at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:314)
| at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:169)
| at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49)
| at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25)
| at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:248)
| at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:294)
| at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:273)
| at com.sun.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:143)
| at com.sun.facelets.tag.ui.IncludeHandler.apply(IncludeHandler.java:60)
| at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
| at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49)
| at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
| at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25)
| at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:248)
| at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:294)
| at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:273)
| at com.sun.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:143)
| at com.sun.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:113)
| at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49)
| at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25)
| at com.sun.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:95)
| at com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java:503)
| at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:546)
| at org.ajax4jsf.framework.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108)
| at org.ajax4jsf.framework.ajax.AjaxViewHandler.renderView(AjaxViewHandler.java:229)
| at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:108)
| at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:266)
| at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:159)
| at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:63)
| at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57)
| at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
| at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:60)
| at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
| at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
| at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
| at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:79)
| at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
| at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:96)
| at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:220)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
| at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
| at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Unknown Source)
That's the end of the log. How would I decrypt this error message?
Thanks for your help.
-tony
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4044788#4044788
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4044788
19 years, 1 month
[JBoss jBPM] - How to deal with complex Action children (configInfoElements
by jruud
Our custom actions are able to process complex (nested) children like in the example below (the parent... stuff):
<node name="Cancel Bill">
| <action class="MyAction">
| <parent>
| <child>CANCEL</child>
| </parent>
| </action>
| </node>
However, I'm a little confused as to how GD 3.1 deals with these complex elements (we're currently using the XML editor to modify them, but plan on adding custom property pages).
Assuming I understand correctly, children of Delegation subclasses like Action are stored in a configInfoElements collection. However, I get the feeling that ConfigInfoElement may possibly not have been designed to deal with complex elements (for example because: ConfigInfoElementDomAdapter.doModelAdd(XmlAdapter) seems to be intentionally ignoring any children).
In order to support complex structues like those above, does it make sense to try to make it work with the ConfigInfoElement approach (and extending it if necessary), or should I rather create my own semantic element and xml adaper to deal with the complex Action children? (any pointers on this would be very helpful!)
Thanks, John
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4044783#4044783
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4044783
19 years, 1 month
[Persistence, JBoss/CMP, Hibernate, Database] - where to put my database driver
by davidhu
I have a j2ee application that is packaged into a WAR file. It used to work very well in Linux with jboss 4.0.2. However, recently, for some unknown reason, when my web app. tries to connect to the database, I got the following exception
[JBossManagedConnectionPool] Throwable while attempting to get a new connection: null
org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (org.jboss.resource.JBossResourceException: Apparently wrong driver class specified for URL: class: oracle.jdbc.driver.OracleDriver, url: jdbc:oracle:thin:@xxxx:1521:xx)
at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.c reateManagedConnection(LocalManagedConnectionFactory.java:179)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.cr eateConnectionEventListener(InternalManagedConnectionPool.java:565)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.ge tConnection(InternalManagedConnectionPool.java:250)
at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BaseP ool.getConnection(JBossManagedConnectionPool.java:491)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManage dConnection(BaseConnectionManager2.java:341)
at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedCo nnection(TxConnectionManager.java:301)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateC onnection(BaseConnectionManager2.java:396)
at org.jboss.resource.connectionmanager.BaseConnectionManager2$Connectio nManagerProxy.allocateConnection(BaseConnectionManager2.java:842)
at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(Wrapp erDataSource.java:88)
at .......
..............................
I later found out the reason I got this exception is that I put ojdbc14.jar inside the dir $my_app_context/WEB-INF/lib, if I put it under $jboss_home/server/default/lib, I do not have this problem. But I tried on Windows, even if I put this jar file under $jboss_home/server/default/lib, I do not have this problem. Why I got this strange behavior? I do want to package this ojdbc14.jar into my WAR file, so that the user will not need to copy it explicitly to the $jboss_home/server/default/lib dir.
I have another file called oracle-ds.xml which was put in $jboss_home/server/default/deploy to config oracle data source.
Can anyone help me on my problem?
Thanks,
David
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4044781#4044781
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4044781
19 years, 1 month