July 2007 - jboss-user - Jboss List Archives

[JBoss jBPM] - Re: create task at runtime

by syngolis

"massimiliano_cuccia" wrote : (this means that ti.getTask() is null) No, this means getTaskController() is null, as I mentioned in the post before. Try it without the controller or create one. In order to get variables (without variableaccess): taskInstance.getVariable("Name") For further information, please have a look at the testcases. There are much examples. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067292#4067292 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067292

18 years, 9 months

1
0
0 / 0

Strange Problem with JBoss 4.0.1

by Udayvir Singh

Hi, Actually, I m facing a strange problem with JBoss 4.0.1. I m running JBoss 4.0.1 with Eclipse 3.2 and J2SDK 1.4. When I run my application on the JBoss 4.0.1 server, some times I get "NullPointerException" and some time it says "the requested resource ( myaction.do) is not found / unavailable". And then, if I refresh (immediately) the same page, it shows up the entire page. This happens 70% of the times. Another thing that happens is, some times images are not shown on the page, however when I refresh the same page, the page shows up perfectly (i.e along with the images). I m deploying the application properly. I first start the server using Eclipse. Once the Eclipse is up n running I deploy the application on the server (Run on server - option by right clicking on the project). On deploying application eclipse 3.2 opens the browser on its own with the welcome page. But, as I told u 70% of the times it gives me that problem. On the if I refresh the page it comes up properly. I feel that this is a problem with some JBoss setting, because if it is a problem with my application it would not run properly on refreshing the page. Apart from this my application is running properly on Tomcat 4.3 (with Eclipse 3.0). If u know any thing about this problem, please help me, if u can. Its urgent. Regards, Udayvir Singh

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: XML Parsing Error: not well-formed

by samdoyle

Great, thanks I'll give that a try. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067290#4067290 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067290

18 years, 9 months

1
0
0 / 0

[JCA/JBoss] - Re: Message DB + Oracle database connection count problems

by sks4jboss

Hi Adrian, This is lot of useful info. 1) We have been watching thread dump and havent seen threads using connections while application doesn't has any available connection left. 2) From the pool stats available in jmx-console (actually we even log AvailableConnectionCount and InUseConnectionCount every minute). For the last incident, we see that available connection count slowly reaches 0 and in use connection count was around 25 for last 20 mins. The sum of 0 and 25 is way less then 130 configured as max pool size (We miss a thread dump at that time). Need to also use CachedConnectionManager. Used CachedConnectionManager to view inuse connections under normal operations of the system. I find the below stacktrace. But interestingly I dont find any such thread in thread dump. So does this means that this is an example of not closing the connection ? (This should definitely help in finding out when the connections are not closed.) Any further clue about why 0 (Avl conn cnt) + 25 (in use conn cnt) << 130 (Conf max num connections). I am definitely reading the wiki page created for me. anonymous wrote : | | {org.jboss.resource.adapter.jdbc.WrappedConnection(a)10e0edb=java.lang.Exception: STACKTRACE | at org.jboss.resource.connectionmanager.CachedConnectionManager.registerConnection(CachedConnectionManager.java:321) | at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:467) | at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:874) | at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:103) | at com.mobilgw.sam.common.WFComponentFactory.(WFComponentFactory.java:123) | ............. | ............. | at javax.servlet.GenericServlet.init(GenericServlet.java:211) | at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1091) | at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:925) | at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3857) | at org.apache.catalina.core.StandardContext.start(StandardContext.java:4118) | at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) | at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) | at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) | 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:324) | at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503) | at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:150) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) | at org.apache.catalina.core.StandardContext.init(StandardContext.java:5005) | 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:324) | at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503) | at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:150) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) | at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:274) | at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:91) | at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:357) | at org.jboss.web.WebModule.startModule(WebModule.java:68) | at org.jboss.web.WebModule.startService(WebModule.java:46) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222) | at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:324) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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:249) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:897) | at $Proxy0.start(Unknown Source) | at org.jboss.system.ServiceController.start(ServiceController.java:418) | at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:324) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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:249) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) | at $Proxy24.start(Unknown Source) | at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:394) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738) | at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:324) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:121) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) | at $Proxy8.deploy(Unknown Source) | at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:325) | at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:501) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204) | at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:277) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222) | at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:324) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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:249) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:897) | at $Proxy0.start(Unknown Source) | at org.jboss.system.ServiceController.start(ServiceController.java:418) | at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:324) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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:249) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) | at $Proxy4.start(Unknown Source) | at org.jboss.deployment.SARDeployer.start(SARDeployer.java:273) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:722) | 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:324) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:121) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) | at $Proxy5.deploy(Unknown Source) | at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:434) | at org.jboss.system.server.ServerImpl.start(ServerImpl.java:315) | at org.jboss.Main.boot(Main.java:195) | at org.jboss.Main$1.run(Main.java:463) | at java.lang.Thread.run(Thread.java:534) | | Thanks again, Info is really useful. Sudarshan View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067288#4067288 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067288

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: Any way to debug why Seam isn't registering a component?

by SmokingAPipe

Thanks for the hint on enabling debugging. Now it is getting stranger, because it is finding the components: | 21:38:36,965 DEBUG [Scanner] found: rbcworkflow/beans/TestAction.class | 21:38:36,967 DEBUG [ComponentScanner] found component class: rbcworkflow/beans/TestAction.class | So the ComponentScanner found the component class. But it never does anything further with it. There's no "initializing component" for those classes. Any idea what could be lacking or incorrect? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067287#4067287 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067287

18 years, 9 months

1
0
0 / 0

[EJB/JBoss] - Re: JUnit exception thrown when doing a context.lookup

by tonylmai

I traced it down to a NamingContext within JBoss using the wrong Logger. I am posting a new posting for this question. Thanks -tony View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067285#4067285 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067285

18 years, 9 months

1
0
0 / 0

[EJB/JBoss] - org.jnp.interfaces.NamingContext throwing java.lang.NoSuchFi

by tonylmai

Hello all, I am using JBoss 4.2.1GA. When I tried to perform a Context.lookup(), I ran into a java.lang.NoSuchFieldError: TRACE exception in the following line: org.jnp.interfaces.NamingContext:622 | boolean trace = log.isTraceEnabled(); where log is of type org.jboss.logging.Logger.class. I think it's my client using the wrong jar file. I can see that there are several Logger in the following jar files: jboss-common-client.jar jbossall-client.jar jboss-common.jar jboss-ejb3-all.jar Which jar should I use? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067284#4067284 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067284

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: Any way to debug why Seam isn't registering a component?

by christian.bauer＠jboss.com

You do not need the debug.jar or the debug="true" setting. This is for component/context debugging with the special http://localhost:8080/myapp/debug.seam URL once the application is actually running. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067283#4067283 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067283

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: Any way to debug why Seam isn't registering a component?

by christian.bauer＠jboss.com

Edit server/default/conf/jboss-log4j.xml (or server/default/conf/log4j.xml in AS < 4.2): | <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE log4j:configuration SYSTEM "log4j.dtd"> | | <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/" debug="false"> | | <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender"> | <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/> | <param name="Target" value="System.out"/> | <layout class="org.apache.log4j.PatternLayout"> |  | <param name="ConversionPattern" value="%d{ABSOLUTE} %-5p [%c{1}] %m%n"/> | </layout> | </appender> | | <category name="org.jboss.seam"> | <priority value="DEBUG"/> | </category> | | <root> | <priority value="INFO"/> | <appender-ref ref="CONSOLE"/> | </root> | | </log4j:configuration> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067281#4067281 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067281

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: XML Parsing Error: not well-formed

by michael.yuan＠jboss.com

Can you copy everything from examples/jpa/view to examples/jee5/view and see if the problem still exists? I think that should solve your problem. It seems that we forgot to update the jee5 view files ... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067279#4067279 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067279

18 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user July 2007