[JCA/JBoss] - JCA 1.5 problem when deploying in JBOSS 4.0
by tpawankumar
Hi All,
I am migrating my application from weblogic 8.1.4 to JBOSS 4.0 when i migrate the jca module and tried to deploy it is showing the following error
15:40:16,834 ERROR [RARDeployment] Starting failed jboss.jca:service=RARDeployme
nt,name='infranetconnector.rar'
java.lang.IllegalArgumentException: No resource adapter class name specified
at org.jboss.resource.deployment.ResourceAdapterFactory.createResourceAd
apter(ResourceAdapterFactory.java:55)
at org.jboss.resource.deployment.RARDeployment.startService(RARDeploymen
t.java:101)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:221)
at org.jboss.system.ServiceDynamicMBeanSupport.invoke(ServiceDynamicMBea
nSupport.java:110)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:1
50)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:891)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:416)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy29.start(Unknown Source)
at org.jboss.deployment.SimpleSubDeployerSupport.startService(SimpleSubD
eployerSupport.java:378)
at org.jboss.deployment.SimpleSubDeployerSupport.start(SimpleSubDeployer
Support.java:141)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:935)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:746)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:709)
at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:119)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:131)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
tScanner.java:305)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
canner.java:481)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
doScan(AbstractDeploymentScanner.java:204)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
loop(AbstractDeploymentScanner.java:215)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
run(AbstractDeploymentScanner.java:194)
i think i am missing <resourceadapter-class> tag in ra.xml.
is this tag compulsory for JBOSS 4.0 because when i deployed in weblogic 10.0 which is using JCA 1.5 specification it is working.
Please help me.
Thanks in advance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066604#4066604
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066604
18Â years, 9Â months
[JBoss Seam] - pooledTaskInstanceList limiting to specific role
by harpritt
Hi Lads and Ladettes
i have a UI page that shows all the tasks for people that are in the "processor" role.
I use the following in my process definition to assign the task to the role
<task name="pr_process_cr" description="#{crId}">
| <assignment pooled-actors="processor"/>
| </task>
the following to display the list
<h:dataTable value="#{pooledTaskInstanceList}" var="task">
| <h:column>
|
| <h:commandLink action="#{ticketSystem.view_cr_waiting_processing}">
| <h:commandButton value="view change Request #{task.description}"/>
| <f:param name="taskId" value="#{task.id}"/>
| </h:commandLink>
| </h:column>
| </h:dataTable>
I cant see a way of filtering the pooledTaskInstanceList to a specic role/actor pool. i only want the list to contain tasks for "processors" because my UI page is only concerned with task for that group, and to also show tasks for "Approvers" which is a possiblilty because a user can have many roles.
Many thanks for any comments.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066602#4066602
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066602
18Â years, 9Â months
[JBoss Seam] - Re: Quick entity question
by ellenzhao
I wanted @In for entity beans too!
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=114111
I watched the Rod presentation. In fact rich domain model is already pretty easy to do with Seam. (With the @In support in entity class, it would be even more convenient)
Rich Domain Model, The Seam Way:
Seam has out-of-box support for Drools, you can write a rule base for any entity class and use the entity's own rule base for its "rich model behaviour". This way, an entity is a totally self-contained knowledge base/expert system, it simply "knows" how to do any "rich behaviour", provided that the "how" knowledge is stored in the rule base. The rule bases can be authored in many dialects, you can author it in Java/MVEL/whatever you like, as long as there is an adapter in the drools compiler....And services can be declared in .drl files as global so any services can be used whenever entities need them. Days ago when I was refactoring my application in this way and showed a bit code to Mark Procter, he said it was the dummiest design he had ever seen, and said I'm better off with Groovy if I just want to write bean methods. But Mark, after investigating Groovy during the weekend, so far I'm not discouraged to bind a rule base to each entity. Because things like closure in Groovy is in fact rules applied to data. (Mark was extremely busy releasing Drools 4.0 GA these days, he worked almost 24/7, so I should be blamed to disturb him at such a chaotic moment....). Yes, Rete-based rule engine is only best suitable for many object/many pattern matching problem, but my entity happens to have several collections and there are some complex inter-entity pattern matching when I want an entity to "behave" something..... And please do not forget now there is the Drools Business Rules Management System out there.....Rules/Knowledge management is easier for programmers than before.....In my opinion, in fact an entity only needs to hook up two things: A database and a rule base. Database to store the "atom" properties and a rule base to store the rules of how to orchestrating different services to perform a certain entity behaviour (eg: for the Vet entity bean: rule "render myself using jsf" .... , rule "register microchip" ....). Since services are global in these rule bases, it can be really easy to change a service itself and not modifying all the rules code..... It can be a totally stupid idea, I'm also learning and just _started_ this experiment, any constructive critics and discussion are most welcome! :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066597#4066597
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066597
18Â years, 9Â months
[Messaging, JMS & JBossMQ] - Re: OutOfMemory because of too many threads and not sure wha
by adrianï¼ jboss.org
"zooxmusic" wrote :
| Is there anyway to detect a broken connection on the server side and kill the threads?
|
The server already does this. It disconnects clients that have stopped pinging
after 2 minutes (See "Read Timeout" in uil2-service.xml).
Most likely you've not closed the connection after you got "client id" error message
so it is still open and pinging the server.
It's one of the common errors, the initialization code should look like this:
| Connection c = connectionFactory.createConnection(...);
| try
| {
| c.setClientId(x);
| }
| catch (JMSException e)
| {
| // Failed to initialize (close the connection!)
| try
| {
| c.close();
| }
| catch (JMSException ignored) {}
| throw e;
| }
|
Of course, you could wait until the client side VM does a full GC,
but by then you've probably got hundreds of open connections lying around.
It's never a good idea to leave resource intensive objects to be closed by
the garbage collector.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066595#4066595
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066595
18Â years, 9Â months