[Tomcat, HTTPD, Servlets & JSP] - Re: CPU (threads) at 100%, Tomcat sockets in CLOSE_WAIT
by georges.goebel
Hi,
Today I had again the same problem (plenty of CLOSE_WAIT sessions and the CPU is on 100%).
Is somebody out there who can solve this problem. I use apache 2.2 with mod_proxy_balancer to the ajp port.
Changing from ajp to http does not solve my problem because the absolute url is changed. http://bla.pch.etat.lu/ap1 -> http://node1.pch.etat.lu:8080/ap1
Neither using the native JBoss library because the SAP native library does not like the binaries of JBoss navtive :-( (JBoss does not starte whene the SAP JCO libraries are in LD_LIBRARY_PATH)
Thanks for any help
Georges
| <Proxy balancer://myCluster>
| BalancerMember ajp://jbosssrv01.pch.etat.lu:8009 route=worker1 loadfactor=10
| BalancerMember ajp://jbosssrv02.pch.etat.lu:8009 route=worker2 loadfactor=10
| </Proxy>
|
| [java@jbosssrv01 ~]$ netstat -na | grep 8009
| tcp 0 0 0.0.0.0:8009 0.0.0.0:* LISTEN
| tcp 0 0 148.110.55.140:8009 148.110.55.136:33657 SYN_RECV
| tcp 0 0 148.110.55.140:8009 148.110.55.136:33663 SYN_RECV
| tcp 0 0 148.110.55.140:8009 148.110.55.136:33655 SYN_RECV
| tcp 0 0 148.110.55.140:8009 148.110.55.136:33660 SYN_RECV
| tcp 0 0 148.110.55.140:8009 148.110.55.136:33651 SYN_RECV
| tcp 0 0 148.110.55.140:8009 148.110.55.136:33652 SYN_RECV
| tcp 387 0 148.110.55.140:8009 148.110.55.136:34073 CLOSE_WAIT
| tcp 394 0 148.110.55.140:8009 148.110.55.136:34072 CLOSE_WAIT
| tcp 394 0 148.110.55.140:8009 148.110.55.136:34079 CLOSE_WAIT
| tcp 375 0 148.110.55.140:8009 148.110.55.136:34078 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:34067 CLOSE_WAIT
| tcp 440 0 148.110.55.140:8009 148.110.55.136:44816 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:37131 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:37130 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:39177 CLOSE_WAIT
| tcp 394 0 148.110.55.140:8009 148.110.55.136:34063 CLOSE_WAIT
| tcp 375 0 148.110.55.140:8009 148.110.55.136:34062 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:44814 CLOSE_WAIT
| tcp 607 0 148.110.55.140:8009 148.110.55.136:44812 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:37123 CLOSE_WAIT
| tcp 440 0 148.110.55.140:8009 148.110.55.136:44801 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:44807 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:37126 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:47929 CLOSE_WAIT
| tcp 667 0 148.110.55.140:8009 148.110.55.136:53053 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:53042 CLOSE_WAIT
| tcp 0 0 148.110.55.140:8009 148.110.55.136:55346 ESTABLISHED
| tcp 272 0 148.110.55.140:8009 148.110.55.136:53046 CLOSE_WAIT
| tcp 272 0 148.110.55.140:8009 148.110.55.136:53033 CLOSE_WAIT
| tcp 387 0 148.110.55.140:8009 148.110.55.136:34088 CLOSE_WAIT
| tcp 742 0 148.110.55.140:8009 148.110.55.136:53039 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:44588 CLOSE_WAIT
| tcp 532 0 148.110.55.140:8009 148.110.55.136:53027 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:34083 CLOSE_WAIT
| tcp 537 0 148.110.55.140:8009 148.110.55.136:53026 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:53025 CLOSE_WAIT
| tcp 394 0 148.110.55.140:8009 148.110.55.136:34087 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:33575 CLOSE_WAIT
| tcp 649 0 148.110.55.140:8009 148.110.55.136:53029 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:53082 CLOSE_WAIT
| tcp 0 0 148.110.55.140:8009 148.110.55.136:55647 ESTABLISHED
| tcp 313 0 148.110.55.140:8009 148.110.55.136:53843 CLOSE_WAIT
| tcp 721 0 148.110.55.140:8009 148.110.55.136:53842 CLOSE_WAIT
| tcp 532 0 148.110.55.140:8009 148.110.55.136:53840 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:42071 CLOSE_WAIT
| tcp 537 0 148.110.55.140:8009 148.110.55.136:53839 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:36173 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:47939 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:47938 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:53314 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:44613 CLOSE_WAIT
| tcp 313 0 148.110.55.140:8009 148.110.55.136:53828 CLOSE_WAIT
| tcp 527 0 148.110.55.140:8009 148.110.55.136:42107 CLOSE_WAIT
| tcp 887 0 148.110.55.140:8009 148.110.55.136:35707 CLOSE_WAIT
| tcp 533 0 148.110.55.140:8009 148.110.55.136:42106 CLOSE_WAIT
| tcp 492 0 148.110.55.140:8009 148.110.55.136:42105 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:35704 CLOSE_WAIT
| tcp 533 0 148.110.55.140:8009 148.110.55.136:42110 CLOSE_WAIT
| tcp 527 0 148.110.55.140:8009 148.110.55.136:42109 CLOSE_WAIT
| tcp 417 0 148.110.55.140:8009 148.110.55.136:35709 CLOSE_WAIT
| tcp 0 0 148.110.55.140:8009 148.110.55.136:33139 ESTABLISHED
| tcp 492 0 148.110.55.140:8009 148.110.55.136:42098 CLOSE_WAIT
| tcp 492 0 148.110.55.140:8009 148.110.55.136:42092 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:48739 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:41826 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:41830 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:41828 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:44388 CLOSE_WAIT
| tcp 769 0 148.110.55.140:8009 148.110.55.136:35730 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:57232 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:35734 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:37782 CLOSE_WAIT
| tcp 566 0 148.110.55.140:8009 148.110.55.136:43158 CLOSE_WAIT
| tcp 416 0 148.110.55.140:8009 148.110.55.136:57236 CLOSE_WAIT
| tcp 489 0 148.110.55.140:8009 148.110.55.136:35732 CLOSE_WAIT
| tcp 468 0 148.110.55.140:8009 148.110.55.136:43146 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:41097 CLOSE_WAIT
| tcp 533 0 148.110.55.140:8009 148.110.55.136:42121 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:35720 CLOSE_WAIT
| tcp 0 0 148.110.55.140:8009 148.110.55.136:59279 ESTABLISHED
| tcp 814 0 148.110.55.140:8009 148.110.55.136:35724 CLOSE_WAIT
| tcp 527 0 148.110.55.140:8009 148.110.55.136:43139 CLOSE_WAIT
| tcp 416 0 148.110.55.140:8009 148.110.55.136:57223 CLOSE_WAIT
| tcp 489 0 148.110.55.140:8009 148.110.55.136:35719 CLOSE_WAIT
| tcp 533 0 148.110.55.140:8009 148.110.55.136:43143 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:41094 CLOSE_WAIT
| tcp 527 0 148.110.55.140:8009 148.110.55.136:43142 CLOSE_WAIT
| tcp 589 0 148.110.55.140:8009 148.110.55.136:35717 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:43141 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:57220 CLOSE_WAIT
| tcp 769 0 148.110.55.140:8009 148.110.55.136:35716 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:57528 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:57535 CLOSE_WAIT
| tcp 570 0 148.110.55.140:8009 148.110.55.136:57533 CLOSE_WAIT
| tcp 516 0 148.110.55.140:8009 148.110.55.136:57525 CLOSE_WAIT
| tcp 570 0 148.110.55.140:8009 148.110.55.136:57524 CLOSE_WAIT
| tcp 318 0 148.110.55.140:8009 148.110.55.136:44714 CLOSE_WAIT
| tcp 308 0 148.110.55.140:8009 148.110.55.136:44713 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:57512 CLOSE_WAIT
| tcp 570 0 148.110.55.140:8009 148.110.55.136:57518 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:44718 CLOSE_WAIT
| tcp 566 0 148.110.55.140:8009 148.110.55.136:43170 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:57511 CLOSE_WAIT
| tcp 308 0 148.110.55.140:8009 148.110.55.136:44711 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:44709 CLOSE_WAIT
| tcp 0 0 148.110.55.140:8009 148.110.55.136:41691 ESTABLISHED
| tcp 306 0 148.110.55.140:8009 148.110.55.136:42459 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:45787 CLOSE_WAIT
| tcp 643 0 148.110.55.140:8009 148.110.55.136:55000 CLOSE_WAIT
| tcp 560 0 148.110.55.140:8009 148.110.55.136:42463 CLOSE_WAIT
| tcp 513 0 148.110.55.140:8009 148.110.55.136:45790 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:41693 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:55004 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:41682 CLOSE_WAIT
| tcp 560 0 148.110.55.140:8009 148.110.55.136:42450 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:50386 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:41680 CLOSE_WAIT
| tcp 416 0 148.110.55.140:8009 148.110.55.136:42454 CLOSE_WAIT
| tcp 651 0 148.110.55.140:8009 148.110.55.136:50389 CLOSE_WAIT
| tcp 651 0 148.110.55.140:8009 148.110.55.136:54997 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:54984 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:42446 CLOSE_WAIT
| tcp 596 0 148.110.55.140:8009 148.110.55.136:54989 CLOSE_WAIT
| tcp 570 0 148.110.55.140:8009 148.110.55.136:57539 CLOSE_WAIT
| tcp 518 0 148.110.55.140:8009 148.110.55.136:57542 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:33221 CLOSE_WAIT
| tcp 516 0 148.110.55.140:8009 148.110.55.136:57541 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:33220 CLOSE_WAIT
| tcp 422 0 148.110.55.140:8009 148.110.55.136:45818 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:44793 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:38905 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:36600 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:37112 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:44799 CLOSE_WAIT
| tcp 607 0 148.110.55.140:8009 148.110.55.136:44797 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:37116 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:45810 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:44790 CLOSE_WAIT
| tcp 589 0 148.110.55.140:8009 148.110.55.136:42472 CLOSE_WAIT
| tcp 422 0 148.110.55.140:8009 148.110.55.136:45805 CLOSE_WAIT
| tcp 306 0 148.110.55.140:8009 148.110.55.136:38893 CLOSE_WAIT
| tcp 513 0 148.110.55.140:8009 148.110.55.136:45804 CLOSE_WAIT
| tcp 518 0 148.110.55.140:8009 148.110.55.136:45794 CLOSE_WAIT
| tcp 521 0 148.110.55.140:8009 148.110.55.136:45793 CLOSE_WAIT
| tcp 417 0 148.110.55.140:8009 148.110.55.136:42465 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:37095 CLOSE_WAIT
| tcp 1 0 148.110.55.140:8009 148.110.55.136:37094 CLOSE_WAIT
| tcp 416 0 148.110.55.140:8009 148.110.55.136:42468 CLOSE_WAIT
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131816#4131816
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131816
18 years, 1 month
[EJB/JBoss] - Re: ejb application
by allanrj
Full StackTrace:
javax.naming.CommunicationException [Root exception is java.io.InvalidClassException: org.jboss.invocation.InvokerInterceptor; unable to create instance]
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:780)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
| at javax.naming.InitialContext.lookup(Unknown Source)
| at teste.BeanClient.main(BeanClient.java:22)
| Caused by: java.io.InvalidClassException: org.jboss.invocation.InvokerInterceptor; unable to create instance
| at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
| at java.io.ObjectInputStream.readObject0(Unknown Source)
| at java.io.ObjectInputStream.readObject(Unknown Source)
| at org.jboss.proxy.Interceptor.readExternal(Interceptor.java:80)
| at java.io.ObjectInputStream.readExternalData(Unknown Source)
| at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
| at java.io.ObjectInputStream.readObject0(Unknown Source)
| at java.io.ObjectInputStream.readObject(Unknown Source)
| at org.jboss.proxy.Interceptor.readExternal(Interceptor.java:80)
| at java.io.ObjectInputStream.readExternalData(Unknown Source)
| at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
| at java.io.ObjectInputStream.readObject0(Unknown Source)
| at java.io.ObjectInputStream.readObject(Unknown Source)
| at org.jboss.proxy.Interceptor.readExternal(Interceptor.java:80)
| at java.io.ObjectInputStream.readExternalData(Unknown Source)
| at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
| at java.io.ObjectInputStream.readObject0(Unknown Source)
| at java.io.ObjectInputStream.readObject(Unknown Source)
| at org.jboss.proxy.ClientContainer.readExternal(ClientContainer.java:156)
| at java.io.ObjectInputStream.readExternalData(Unknown Source)
| at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
| at java.io.ObjectInputStream.readObject0(Unknown Source)
| at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
| at java.io.ObjectInputStream.readSerialData(Unknown Source)
| at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
| at java.io.ObjectInputStream.readObject0(Unknown Source)
| at java.io.ObjectInputStream.readObject(Unknown Source)
| at java.rmi.MarshalledObject.get(Unknown Source)
| at org.jnp.interfaces.MarshalledValuePair.get(MarshalledValuePair.java:72)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:710)
| ... 3 more
| Caused by: java.lang.reflect.InvocationTargetException
| at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
| at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
| at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
| at java.lang.reflect.Constructor.newInstance(Unknown Source)
| at java.io.ObjectStreamClass.newInstance(Unknown Source)
| ... 33 more
| Caused by: java.lang.NoClassDefFoundError: EDU/oswego/cs/dl/util/concurrent/SynchronizedLong
| at org.jboss.util.id.UID.<clinit>(UID.java:56)
| at org.jboss.util.id.VMID.create(VMID.java:259)
| at org.jboss.util.id.VMID.getInstance(VMID.java:223)
| at org.jboss.util.id.GUID.<init>(GUID.java:65)
| at org.jboss.invocation.Invoker.<clinit>(Invoker.java:55)
| at org.jboss.invocation.InvokerInterceptor.<init>(InvokerInterceptor.java:61)
| ... 38 more
| Caused by: java.lang.ClassNotFoundException: EDU.oswego.cs.dl.util.concurrent.SynchronizedLong
| at java.net.URLClassLoader$1.run(Unknown Source)
| at java.security.AccessController.doPrivileged(Native Method)
| at java.net.URLClassLoader.findClass(Unknown Source)
| at java.lang.ClassLoader.loadClass(Unknown Source)
| at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
| at java.lang.ClassLoader.loadClass(Unknown Source)
| at java.lang.ClassLoader.loadClassInternal(Unknown Source)
| ... 44 more
This error happens when i run a ejb client to test the deploy
Class Client:
import java.util.Properties;
| import javax.naming.Context;
| import javax.naming.InitialContext;
|
| public class BeanClient {
|
| public static void main(String[] args) {
| Properties prop = new Properties();
| prop.put(Context.INITIAL_CONTEXT_FACTORY,
| "org.jnp.interfaces.NamingContextFactory");
| prop.put(Context.PROVIDER_URL, "localhost:1099");
|
| try {
| InitialContext ic = new InitialContext(prop);
|
| Object refLocal = ic.lookup("SitesLocal");
|
| Object refRemote = ic.lookup("SitesSB");
|
|
| } catch (Exception e) {
| e.printStackTrace();
| }
| }
| }
ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
|
| <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
|
| <ejb-jar >
|
| <description><![CDATA[No Description.]]></description>
| <display-name>Generated by XDoclet</display-name>
|
| <enterprise-beans>
|
| <!-- Session Beans -->
| <session >
| <description><![CDATA[Bean implementation class for Enterprise Bean: SitesSB]]></description>
| <display-name>SitesSB</display-name>
|
| <ejb-name>SitesSB</ejb-name>
|
| <home>br.com.gcm.ejb.sb.SitesSBHome</home>
| <remote>br.com.gcm.ejb.sb.SitesSB</remote>
| <ejb-class>br.com.gcm.ejb.sb.SitesSBBean</ejb-class>
| <session-type>Stateless</session-type>
| <transaction-type>Container</transaction-type>
|
| <resource-ref >
| <res-ref-name>jdbc/APAESP</res-ref-name>
| <res-type>javax.sql.DataSource</res-type>
| <res-auth>Container</res-auth>
| <res-sharing-scope>Shareable</res-sharing-scope>
| </resource-ref>
| <resource-ref >
| <res-ref-name>jdbc/MARLIN</res-ref-name>
| <res-type>javax.sql.DataSource</res-type>
| <res-auth>Container</res-auth>
| <res-sharing-scope>Shareable</res-sharing-scope>
| </resource-ref>
| <resource-ref >
| <res-ref-name>jdbc/GCM2</res-ref-name>
| <res-type>javax.sql.DataSource</res-type>
| <res-auth>Container</res-auth>
| <res-sharing-scope>Shareable</res-sharing-scope>
| </resource-ref>
|
| </session>
|
| <!--
| To add session beans that you have deployment descriptor info for, add
| a file to your XDoclet merge directory called session-beans.xml that contains
| the <session></session> markup for those beans.
| -->
|
| <!-- Entity Beans -->
| <entity >
| <description><![CDATA[Bean implementation class for Enterprise Bean: Sites]]></description>
|
| <ejb-name>Sites</ejb-name>
|
| <local-home>br.com.gcm.ejb.cmp.SitesLocalHome</local-home>
| <local>br.com.gcm.ejb.cmp.SitesLocal</local>
|
| <ejb-class>br.com.gcm.ejb.cmp.SitesBean</ejb-class>
| <persistence-type>Container</persistence-type>
| <prim-key-class>br.com.gcm.ejb.cmp.SitesKey</prim-key-class>
| <reentrant>False</reentrant>
| <cmp-version>2.x</cmp-version>
| <abstract-schema-name>Sites</abstract-schema-name>
| <cmp-field >
| <description><![CDATA[Get accessor for persistent attribute: siteid]]></description>
| <field-name>siteid</field-name>
| </cmp-field>
| <cmp-field >
| <description><![CDATA[Get accessor for persistent attribute: sitename]]></description>
| <field-name>sitename</field-name>
| </cmp-field>
| <cmp-field >
| <description><![CDATA[Get accessor for persistent attribute: siteimage]]></description>
| <field-name>siteimage</field-name>
| </cmp-field>
| <cmp-field >
| <description><![CDATA[Get accessor for persistent attribute: siteacronym]]></description>
| <field-name>siteacronym</field-name>
| </cmp-field>
| <cmp-field >
| <description><![CDATA[Get accessor for persistent attribute: siteprodurl]]></description>
| <field-name>siteprodurl</field-name>
| </cmp-field>
| <cmp-field >
| <description><![CDATA[Get accessor for persistent attribute: sitehomologurl]]></description>
| <field-name>sitehomologurl</field-name>
| </cmp-field>
|
| <!-- Write a file named ejb-finders-SitesBean.xml if you want to define extra finders. -->
|
| </entity>
|
| <!--
| To add entity beans that you have deployment descriptor info for, add
| a file to your XDoclet merge directory called entity-beans.xml that contains
| the <entity></entity> markup for those beans.
| -->
|
| <!-- Message Driven Beans -->
| <!--
| To add message driven beans that you have deployment descriptor info for, add
| a file to your XDoclet merge directory called message-driven-beans.xml that contains
| the <message-driven></message-driven> markup for those beans.
| -->
|
| </enterprise-beans>
|
| <!-- Relationships -->
|
| <!-- Assembly Descriptor -->
| <!--
| To specify your own assembly descriptor info here, add a file to your
| XDoclet merge directory called assembly-descriptor.xml that contains
| the <assembly-descriptor></assembly-descriptor> markup.
| -->
|
| <assembly-descriptor >
| <!--
| To specify additional security-role elements, add a file in the merge
| directory called ejb-security-roles.xml that contains them.
| -->
|
| <!-- method permissions -->
| <!--
| To specify additional method-permission elements, add a file in the merge
| directory called ejb-method-permissions.ent that contains them.
| -->
|
| <!-- transactions -->
| <!--
| To specify additional container-transaction elements, add a file in the merge
| directory called ejb-container-transactions.ent that contains them.
| -->
|
| <!-- finder transactions -->
|
| <!-- message destinations -->
| <!--
| To specify additional message-destination elements, add a file in the merge
| directory called ejb-message-destinations.ent that contains them.
| -->
|
| <!-- exclude list -->
| <!--
| To specify an exclude-list element, add a file in the merge directory
| called ejb-exclude-list.xml that contains it.
| -->
| </assembly-descriptor>
|
| </ejb-jar>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131813#4131813
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131813
18 years, 1 month
[EJB/JBoss] - Re: ejb application
by jaikiran
anonymous wrote : Stacktrace:
| javax.naming.CommunicationException [Root exception is java.io.InvalidClassException: org.jboss.invocation.InvokerInterceptor; unable to create instance]
You havent posted the entire exception stacktrace that you see in the logs yet. Going by this one line its difficult to tell why you are seeing this exception. When does this exception occur? When you are deploying your application or when you are accessing the application? Does it occur on the server or on the client from where you invoke the application? This exception usually occurs when you are using an incorrect version of a jar file. Post the entire exception stacktrace. That might help in identifying the problem.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131812#4131812
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131812
18 years, 1 month
[EJB/JBoss] - Re: ejb application
by allanrj
Hi jaikiran,
Im using jboss 4.2.2 and java 1.6
Stacktrace:
javax.naming.CommunicationException [Root exception is java.io.InvalidClassException: org.jboss.invocation.InvokerInterceptor; unable to create instance]
jboss.xml
<?xml version="1.0" encoding="UTF-8"?>
| <!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 4.0//EN" "http://www.jboss.org/j2ee/dtd/jboss_4_0.dtd">
|
| <jboss>
|
| <enterprise-beans>
|
| <!--
| To add beans that you have deployment descriptor info for, add
| a file to your XDoclet merge directory called jboss-beans.xml that contains
| the <session></session>, <entity></entity> and <message-driven></message-driven>
| markup for those beans.
| -->
|
| <entity>
| <ejb-name>Sites</ejb-name>
| <local-jndi-name>SitesLocal</local-jndi-name>
|
| <method-attributes>
| </method-attributes>
|
| </entity>
|
| <session>
| <ejb-name>SitesSB</ejb-name>
| <jndi-name>SitesSB</jndi-name>
|
| <resource-ref>
| <res-ref-name>jdbc/APAESP</res-ref-name>
| <jndi-name>jdbc/APAESP</jndi-name>
| </resource-ref>
| <resource-ref>
| <res-ref-name>jdbc/MARLIN</res-ref-name>
| <jndi-name>jdbc/MARLIN</jndi-name>
| </resource-ref>
| <resource-ref>
| <res-ref-name>jdbc/GCM2</res-ref-name>
| <jndi-name>jdbc/GCM2</jndi-name>
| </resource-ref>
|
| <method-attributes>
| </method-attributes>
| </session>
|
| <!--
| write a merge file jboss-webservices.ent for webservice-description
| -->
|
| </enterprise-beans>
|
| <!--
| To specify your own assembly descriptor info here, add a file to your
| XDoclet merge directory called jboss-assembly-descriptor.xml that contains
| the <assembly-descriptor></assembly-descriptor> markup.
| -->
| <assembly-descriptor>
| <!-- message destinations -->
| <!--
| To specify additional message-destination elements, add a file in the merge
| directory called jboss-message-destinations.ent that contains them.
| -->
| </assembly-descriptor>
|
| <resource-managers>
| </resource-managers>
|
| <!--
| | for container settings, you can merge in jboss-container.xml
| | this can contain <invoker-proxy-bindings/> and <container-configurations/>
| -->
|
| </jboss>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131808#4131808
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131808
18 years, 1 month
[JBossCache] - Re: JBoss Cache 2.0.0 in GA
by yrk.kaushik
I am using Jboss cache 2.0.0 GA. I've used the configuration file- local-eviction-cacheloader-service.xml, available under JBossCache-all-2.0.0.GA\etc\META-INF and place it in Jboss\server\default\deploy folder. But while starting the server, I am getting incomplete deployment error as shown below. Could any of you please help me out in resolving this?
12:01:43,095 INFO [ServiceConfigurator] Problem configuring service jboss.cache:service=TreeCache
org.jboss.deployment.DeploymentException: Exception setting attribute javax.management.Attribute@110195c on mbean jboss.cache:service=TreeCache; - nested throwable: (java.lang.VerifyError: (class: org/jboss/cache/config/Configuration, method: setCacheLoaderConfig signature: (Lorg/jboss/cache/config/CacheLoaderConfig;)V) Incompatible argument to function)
at org.jboss.system.ServiceConfigurator.setAttribute(ServiceConfigurator.java:698)
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:332)
Caused by: java.lang.VerifyError: (class: org/jboss/cache/config/Configuration, method: setCacheLoaderConfig signature: (Lorg/jboss/cache/config/CacheLoaderConfig;)V) Incompatible argument to function
at org.jboss.cache.jmx.CacheJmxWrapper.getConfiguration(CacheJmxWrapper.java:124)
at org.jboss.cache.jmx.CacheJmxWrapper.setTransactionManagerLookupClass(CacheJmxWrapper.java:545)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
--- MBeans waiting for other MBeans ---
ObjectName: jboss.cache:service=TreeCache
State: FAILED
Reason: org.jboss.deployment.DeploymentException: Exception setting attribute javax.management.Attribute@110195c on mbean jboss.cache:service=TreeCache; - nested throwable: (java.lang.VerifyError: (class: org/jboss/cache/config/Configuration, method: setCacheLoaderConfig signature: (Lorg/jboss/cache/config/CacheLoaderConfig;)V) Incompatible argument to function)
I Depend On:
jboss:service=Naming
jboss:service=TransactionManager
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.cache:service=TreeCache
State: FAILED
Reason: org.jboss.deployment.DeploymentException: Exception setting attribute javax.management.Attribute@110195c on mbean jboss.cache:service=TreeCache; - nested throwable: (java.lang.VerifyError: (class: org/jboss/cache/config/Configuration, method: setCacheLoaderConfig signature: (Lorg/jboss/cache/config/CacheLoaderConfig;)V) Incompatible argument to function)
I Depend On:
jboss:service=Naming
jboss:service=TransactionManager
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131805#4131805
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131805
18 years, 1 month
[JBoss jBPM] - BPEL: The service is not in an appropiate state for the requ
by rgesteban
Hi All,
Iôm using jBpm-Bpel 1.1 with Jboss 4.2.2 in all configuration. I deploy a bpel service but when I try to call it with a cliente I obtain :
javax.xml.ws.soap.SOAPFaultException: The service is not in an appropiate state for the requested operation
at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:69)
at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:109)
at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:553)
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:371)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:243)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
at $Proxy8.sendGroupsByMail(Unknown Source)
at es.cyii.service.bpel.WSMailAdapter.sendMail(WSMailAdapter.java:24
If somebody could help me I will apprecciate it.
Thanks
Rodolfo
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131796#4131796
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131796
18 years, 1 month
[JBoss jBPM] - Re: Problem with Timer, Scheduler
by sid82
Thanks for the reply. I tried starting the JobExecutor and it looks like it is running too.
What I did was :-
1. Created the following entry in my web.xml
| <servlet>
| <servlet-name>JobExecutorServlet</servlet-name>
| <servlet-class>org.jbpm.job.executor.JobExecutorServlet</servlet-class>
| <load-on-startup>1</load-on-startup>
| </servlet>
|
|
| <servlet-mapping>
| <servlet-name>JobExecutorServlet</servlet-name>
| <url-pattern>/jobs</url-pattern>
| </servlet-mapping>
|
| When I hit the url (/jobs), it displays me a page which tells JbpmJobExecutor isAlive:true
Also, I change my jbpm.cfg.xml file, I replaced the following :-
<bean name="jbpm.job.executor" class="org.jbpm.job.executor.JobExecutor">
| <field name="jbpmConfiguration"><ref bean="jbpmConfiguration" /></field>
| <field name="name"><string value="JbpmJobExector" /></field>
| <field name="nbrOfThreads"><int value="1" /></field>
| <field name="idleInterval"><int value="5000" /></field>
| <field name="maxIdleInterval"><int value="3600000" /></field> <!-- 1 hour -->
| <field name="historyMaxSize"><int value="20" /></field>
| <field name="maxLockTime"><int value="600000" /></field> <!-- 10 minutes -->
| <field name="lockMonitorInterval"><int value="60000" /></field> <!-- 1 minute -->
| <field name="lockBufferTime"><int value="5000" /></field> <!-- 5 seconds -->
| </bean>
|
with the following :-
<!-- <null name="jbpm.job.executor" /> -->
Rest remains the same.
But still no timer action is getting executed at all.
One more thing, I am using Weblogic as my application server and trying to use jbpm timer in my enterprise application.
Please if you can provide some input about what is going wrong.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131794#4131794
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131794
18 years, 1 month