[JBoss Seam] - Cannot instantiate component
by srpantano
I tried to put Icefaces, Woodstock (my favorite, I would like to use this first) and JBoss RichFaces, but when I run the app the follow errors appear:
| WARN [application] JSF1004: Cannot instantiate component of type com.icesoft.faces.OutputChart
| ERROR [[/web]] com.icesoft.faces.component.outputchart.OutputChart
| javax.faces.FacesException: java.lang.UnsupportedOperationException
|
| ...
|
| Caused by: java.lang.UnsupportedOperationException
|
| ...
|
| WARN [config] One or more configured application objects cannot be created. See your web application logs for details.
| 11:32:38,563 ERROR [[/web]] Exception sending context initialized event to listener instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
| javax.faces.FacesException: One or more configured application objects cannot be created. See your web application logs for details.
|
|
PS: 1) This happens for Iceface´s, Richface´s and Woodstock´s component.
2) I´m using Seam 1.2.1GA, Jboss 4.2.0GA, JSF 1.2 (Sun RI) and Facelets 1.12.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4048704#4048704
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4048704
19 years, 1 month
[Installation, Configuration & Deployment] - Re: JBoss 4.0.0 is slow on Solaris 8 (64bit SunFire v120) 4
by bbelagodu
I'm revisiting this thread after a few years but this is an issue I'm sure someone must have gotten to and knows the solution,
I'm running solaris2.10, JDK 1.5.0_06 or 1.5.0_11 (32 bit or 64 bit), both are really slow. JBoss takes up a long time to come up and I'm running load test using JMeter and the system response time for each query is 800-900ms as suppose to 100ms on the linux box.
root@benchmark # psrinfo
0 on-line since 05/24/2007 17:11:31
1 on-line since 05/24/2007 17:11:32
2 on-line since 05/24/2007 17:11:32
3 on-line since 05/24/2007 17:11:32
4 on-line since 05/24/2007 17:11:32
5 on-line since 05/24/2007 17:11:32
6 on-line since 05/24/2007 17:11:32
7 on-line since 05/24/2007 17:11:32
8 on-line since 05/24/2007 17:11:32
9 on-line since 05/24/2007 17:11:32
10 on-line since 05/24/2007 17:11:32
11 on-line since 05/24/2007 17:11:32
12 on-line since 05/24/2007 17:11:32
13 on-line since 05/24/2007 17:11:32
14 on-line since 05/24/2007 17:11:32
15 on-line since 05/24/2007 17:11:32
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4048702#4048702
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4048702
19 years, 1 month
[Remoting] - Problem calling EJB3 method via HTTP only
by formica
I have a problem in testing remote method calls via http using JBOSS 4.2.0.GA application server.
I want to call EJB3 methods via HTTP ONLY (I have a firewall problem, as usual ;-) )
(REMARK: using simple RMI and adequate JNDI parameter the client
code is working correctly...)
Following many forums/doc/wiki pages I have ended up with a configuration of the following type:
SERVER SIDE:
1) I have modified ejb3.deployer/META-INF/jboss-service.xml in the following way:
| <mbean code="org.jboss.remoting.transport.Connector"
| name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3">
| <depends>jboss.aop:service=AspectDeployer</depends>
| <attribute name="InvokerLocator">servlet://${jboss.bind.address}:8080/invoker/EJBInvokerServlet</attribute>
| <attribute name="Configuration">
| <handlers>
| <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler>
| </handlers>
| </attribute>
| </mbean>
|
2) I have slightly modified the http-invoker.sar/META-INF/jboss-service.xml adding the the following lines to the 3 relative MBEAN definitions:
|
| <attribute name="InvokerURL">http://${jboss.bind.address}:8080/invoker/EJBInvokerServlet</attribute>
| .....
| <attribute name="InvokerURL">http://${jboss.bind.address}:8080/invoker/JMXInvokerServlet</attribute>
| .....
| <attribute name="InvokerURL">http://${jboss.bind.address}:8080/invoker/readonly/JMXInvokerServlet</attribute>
|
|
3) I have modified the conf/standardjboss.xml config file like :
| <invoker-proxy-binding>
| <name>stateless-http-invoker</name>
| <invoker-mbean>jboss:service=invoker,type=http</invoker-mbean>
| <proxy-factory>org.jboss.proxy.ejb.ProxyFactory</proxy-factory>
| <proxy-factory-config>
| <client-interceptors>
| <home>
| <interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor>
| <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
| <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
| <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
| <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
| </home>
| <bean>
| <interceptor>org.jboss.proxy.ejb.StatelessSessionInterceptor</interceptor>
| <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
| <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
| <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
| <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
| </bean>
| </client-interceptors>
| </proxy-factory-config>
| </invoker-proxy-binding>
|
and the container part accordingly
| <container-name>Standard Stateless SessionBean</container-name>
| <call-logging>false</call-logging>
| <invoker-proxy-binding-name>stateless-http-invoker</invoker-proxy-binding-name>
| .....
|
4) I have added the following annotation to my stateless session
|
| //@RemoteBinding(jndiBinding="AsapServer/OltestlinesDAOBean/remote")
| @RemoteBindings({
| @RemoteBinding(jndiBinding="AsapServer/OltestlinesDAOBean/remote"),
| @RemoteBinding(clientBindUrl="servlet://localhost:8080/invoker/EJBInvokerServlet",
| jndiBinding="AsapServer/OltestlinesDAOBean/http")
| })
|
|
and finally...
CLIENTSIDE
5) I have defined the following JNDI properties for the connection :
| java.naming.factory.initial=org.jboss.naming.HttpNamingContextFactory java.naming.provider.url=http://$host:$port/invoker/JNDIFactory java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
|
| where host/port are : localhost/8080 or 127.0.0.1/8080
|
Now, I get correctly the stub to the session bean in my client, and I
managed to execute the method, but the method execution itself fails
with the following exception from the server:
| 2007-05-25 16:20:50,986 DEBUG [org.jboss.invocation.http.servlet.InvokerServlet] Invoke threw exception
| java.lang.ClassCastException: org.jboss.remoting.InvocationRequest
| at org.jboss.invocation.http.servlet.InvokerServlet.processRequest(InvokerServlet.java:137)
| at org.jboss.invocation.http.servlet.InvokerServlet.doPost(InvokerServlet.java:224)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
| at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
| at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
| at java.lang.Thread.run(Thread.java:613)
|
while the client sees the following :
| getting stub for beanName OltestlinesDAO
| obj looked up in OltestlinesDAO/http
|
| java.lang.ClassCastException: java.lang.String
| at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:103)
| at $Proxy2.findOlsLike(Unknown Source)
| at asap.client.delegate.OpticallineDBJboss.listOpticallines(OpticallineDBJboss.java:82)
| at asap.client.delegate.OpticallineDBJboss.main(OpticallineDBJboss.java:202)
| at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:74)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:103)
| at $Proxy2.findOlsLike(Unknown Source)
| at asap.client.delegate.OpticallineDBJboss.listOpticallines(OpticallineDBJboss.java:82)
| at asap.client.delegate.OpticallineDBJboss.main(OpticallineDBJboss.java:202)
| Exception in thread "main" java.lang.NullPointerException
| at asap.client.delegate.OpticallineDBJboss.main(OpticallineDBJboss.java:203)
|
Could you please explain me what is going on ? I'll try to post the message also in Remoting forum...
Andrea
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4048700#4048700
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4048700
19 years, 1 month
[JNDI/Naming/Network] - Re: [[EJBInvokerServlet]] Servlet.service() for servlet EJB
by formica
I have a problem in testing remote method calls via http using JBOSS 4.2.0.GA application server.
I want to call EJB3 methods via HTTP ONLY (I have a firewall problem, as usual ;-) )
(REMARK: using simple RMI and adequate JNDI parameter the client
code is working correctly...)
Following many forums/doc/wiki pages I have ended up with a configuration of the following type:
SERVER SIDE:
1) I have modified ejb3.deployer/META-INF/jboss-service.xml in the following way:
| <mbean code="org.jboss.remoting.transport.Connector"
| name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3">
| <depends>jboss.aop:service=AspectDeployer</depends>
| <attribute name="InvokerLocator">servlet://${jboss.bind.address}:8080/invoker/EJBInvokerServlet</attribute>
| <attribute name="Configuration">
| <handlers>
| <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler>
| </handlers>
| </attribute>
| </mbean>
|
2) I have slightly modified the http-invoker.sar/META-INF/jboss-service.xml adding the the following lines to the 3 relative MBEAN definitions:
|
| <attribute name="InvokerURL">http://${jboss.bind.address}:8080/invoker/EJBInvokerServlet</attribute>
| .....
| <attribute name="InvokerURL">http://${jboss.bind.address}:8080/invoker/JMXInvokerServlet</attribute>
| .....
| <attribute name="InvokerURL">http://${jboss.bind.address}:8080/invoker/readonly/JMXInvokerServlet</attribute>
|
|
3) I have modified the conf/standardjboss.xml config file like :
| <invoker-proxy-binding>
| <name>stateless-http-invoker</name>
| <invoker-mbean>jboss:service=invoker,type=http</invoker-mbean>
| <proxy-factory>org.jboss.proxy.ejb.ProxyFactory</proxy-factory>
| <proxy-factory-config>
| <client-interceptors>
| <home>
| <interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor>
| <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
| <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
| <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
| <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
| </home>
| <bean>
| <interceptor>org.jboss.proxy.ejb.StatelessSessionInterceptor</interceptor>
| <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
| <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
| <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
| <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
| </bean>
| </client-interceptors>
| </proxy-factory-config>
| </invoker-proxy-binding>
|
and the container part accordingly
| <container-name>Standard Stateless SessionBean</container-name>
| <call-logging>false</call-logging>
| <invoker-proxy-binding-name>stateless-http-invoker</invoker-proxy-binding-name>
| .....
|
4) I have added the following annotation to my stateless session
|
| //@RemoteBinding(jndiBinding="AsapServer/OltestlinesDAOBean/remote")
| @RemoteBindings({
| @RemoteBinding(jndiBinding="AsapServer/OltestlinesDAOBean/remote"),
| @RemoteBinding(clientBindUrl="servlet://localhost:8080/invoker/EJBInvokerServlet",
| jndiBinding="AsapServer/OltestlinesDAOBean/http")
| })
|
|
and finally...
CLIENTSIDE
5) I have defined the following JNDI properties for the connection :
| java.naming.factory.initial=org.jboss.naming.HttpNamingContextFactory java.naming.provider.url=http://$host:$port/invoker/JNDIFactory java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
|
| where host/port are : localhost/8080 or 127.0.0.1/8080
|
Now, I get correctly the stub to the session bean in my client, and I
managed to execute the method, but the method execution itself fails
with the following exception from the server:
| 2007-05-25 16:20:50,986 DEBUG [org.jboss.invocation.http.servlet.InvokerServlet] Invoke threw exception
| java.lang.ClassCastException: org.jboss.remoting.InvocationRequest
| at org.jboss.invocation.http.servlet.InvokerServlet.processRequest(InvokerServlet.java:137)
| at org.jboss.invocation.http.servlet.InvokerServlet.doPost(InvokerServlet.java:224)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
| at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
| at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
| at java.lang.Thread.run(Thread.java:613)
|
while the client sees the following :
| getting stub for beanName OltestlinesDAO
| obj looked up in OltestlinesDAO/http
|
| java.lang.ClassCastException: java.lang.String
| at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:103)
| at $Proxy2.findOlsLike(Unknown Source)
| at asap.client.delegate.OpticallineDBJboss.listOpticallines(OpticallineDBJboss.java:82)
| at asap.client.delegate.OpticallineDBJboss.main(OpticallineDBJboss.java:202)
| at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:74)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:103)
| at $Proxy2.findOlsLike(Unknown Source)
| at asap.client.delegate.OpticallineDBJboss.listOpticallines(OpticallineDBJboss.java:82)
| at asap.client.delegate.OpticallineDBJboss.main(OpticallineDBJboss.java:202)
| Exception in thread "main" java.lang.NullPointerException
| at asap.client.delegate.OpticallineDBJboss.main(OpticallineDBJboss.java:203)
|
Could you please explain me what is going on ? I'll try to post the message also in Remoting forum...
Andrea
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4048699#4048699
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4048699
19 years, 1 month
[JBoss Seam] - Data separation in multi tenant applications with seam
by christian_zeidler
We are currently designing an application that will be exposed to multiple customers, and are therefore evaluating seam. The question we are currently discussing is how to separate the customers? data. Generally I would consider three alternatives:
1) Sharing the same database and schema. Associating every record with one client by using an ID.
2) Sharing the same database, but using separate schemas. This would mean that the tables in the schema that hold client specific data would be created for each client and identified via the table name (e.g. client1_data, client2_data etc.).
3) Using separate databases. And let the application connect to the correct database on logon based on the user?s information.
Each of these options does have advantages and disadvantages concerning scalability, performance and security related issues. While we are still evaluating these options, I?m interested in how these options could be implemented in a seam application.
Concerning option 1, storing the client ID in the session context and including it in all the queries should do the job.
Are there any good strategies concerning option 2 or 3?
I?d like to call upon the community?s experience with these topics, and ask you for your opinions on these strategies and their implementation within seam.
Thanks? for your help!
Christian
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4048694#4048694
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4048694
19 years, 1 month
[EJB 3.0] - Embeddable EJB3 and WebSphere 6.1
by ikuleshov
Guys,
I am trying to run the JBoss Embeddable EJB3 Container version Alpha RC9 on WebSphere 6.1 since WAS support for EJB3 is in early alpha too. I am stuck in the following error that occurs while registering a JBoss TransactionManager in JNDI:
anonymous wrote :
| [5/25/07 18:20:42:559 YEKST] 00000013 3 UOW= source=com.ibm.ws.naming.ipbase.NameSpace org=IBM prod=WebSphere component=Application Server thread=[server.startup : 2]
| getParentContext parm0=nsID=17, currCtx=java:, name=/TransactionManager, ctxID=ROOT CONTEXT
| [5/25/07 18:20:42:560 YEKST] 00000013 > UOW= source=com.ibm.ws.naming.ipbase.NameSpace method=getParentCtxInternal org=IBM prod=WebSphere component=Application Server thread=[server.startup : 2]
| Entry
| [5/25/07 18:20:42:560 YEKST] 00000013 3 UOW= source=com.ibm.ws.naming.java.javaURLContextRoot org=IBM prod=WebSphere component=Application Server thread=[server.startup : 2]
| getNameInNamespace()-->>java:
| [5/25/07 18:20:42:560 YEKST] 00000013 3 UOW= source=com.ibm.ws.naming.ipbase.NameSpace org=IBM prod=WebSphere component=Application Server thread=[server.startup : 2]
| getParentCtxInternal parm0=nsID=17, currCtx=java:, name=/TransactionManager, ctxID=ROOT CONTEXT
| [5/25/07 18:20:42:560 YEKST] 00000013 3 UOW= source=com.ibm.ws.naming.java.javaURLContextRoot org=IBM prod=WebSphere component=Application Server thread=[server.startup : 2]
| getNameInNamespace()-->>java:
| [5/25/07 18:20:42:560 YEKST] 00000013 < UOW= source=com.ibm.ws.naming.ipbase.NameSpace method=getParentCtxInternal: NameNotFoundException org=IBM prod=WebSphere component=Application Server thread=[server.startup : 2]
| Exit parm0=javax.naming.NameNotFoundException: Name not found in context "java:".
| at com.ibm.ws.naming.ipbase.NameSpace.getParentCtxInternal(NameSpace.java:1767)
| at com.ibm.ws.naming.ipbase.NameSpace.getParentContext(NameSpace.java:1644)
| at com.ibm.ws.naming.urlbase.UrlContextImpl.getParentBindingData(UrlContextImpl.java:1639)
| at com.ibm.ws.naming.urlbase.UrlContextImpl.bind(UrlContextImpl.java:205)
| at com.ibm.ws.naming.urlbase.UrlContextImpl.bind(UrlContextImpl.java:344)
| at javax.naming.InitialContext.bind(InitialContext.java:371)
| at org.jboss.tm.TransactionManagerInitializer.bindRef(TransactionManagerInitializer.java:690)
| at org.jboss.tm.TransactionManagerInitializer.start(TransactionManagerInitializer.java:145)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
| at java.lang.reflect.Method.invoke(Method.java:615)
| at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:55)
| at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:107)
| at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
| at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:75)
| at org.jboss.kernel.plugins.dependency.LifecycleAction.installAction(LifecycleAction.java:115)
| at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.install(KernelControllerContextAction.java:100)
| at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:709)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:429)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:538)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:472)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:274)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:177)
| at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean(AbstractKernelDeployer.java:291)
| at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDeployer.java:261)
| at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer.java:117)
| at org.jboss.kernel.plugins.deployment.xml.BeanXMLDeployer.deploy(BeanXMLDeployer.java:95)
| at org.jboss.ejb3.embedded.EJB3StandaloneBootstrap.boot(EJB3StandaloneBootstrap.java:373)
| at org.jboss.seam.core.Ejb.startup(Ejb.java:42)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
| at java.lang.reflect.Method.invoke(Method.java:615)
| at org.jboss.seam.util.Reflections.invoke(Reflections.java:20)
| at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:123)
| at org.jboss.seam.Component.callComponentMethod(Component.java:1834)
| at org.jboss.seam.Component.callCreateMethod(Component.java:1757)
| at org.jboss.seam.Component.newInstance(Component.java:1746)
| at org.jboss.seam.contexts.Lifecycle.startup(Lifecycle.java:175)
| at org.jboss.seam.contexts.Lifecycle.endInitialization(Lifecycle.java:145)
| at org.jboss.seam.init.Initialization.init(Initialization.java:504)
| at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:33)
| at com.ibm.ws.wswebcontainer.webapp.WebApp.notifyServletContextCreated(WebApp.java:621)
| at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:274)
| at com.ibm.ws.wswebcontainer.webapp.WebApp.initialize(WebApp.java:273)
| at com.ibm.ws.wswebcontainer.webapp.WebGroup.addWebApplication(WebGroup.java:88)
| at com.ibm.ws.wswebcontainer.VirtualHost.addWebApplication(VirtualHost.java:157)
| at com.ibm.ws.wswebcontainer.WebContainer.addWebApp(WebContainer.java:655)
| at com.ibm.ws.wswebcontainer.WebContainer.addWebApplication(WebContainer.java:608)
| at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:333)
| at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:549)
| at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1312)
| at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1129)
| at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:569)
| at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:814)
| at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:965)
| at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:2131)
| at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:340)
| at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)
|
According to this trace, everything is actually fine, TransactionManager is being registered under the java:/TransactionManager name. Then, for some unknown reason, WAS throws an obscuring 'Name not found in context "java:"' error. It seems that WAS is trying to lookup an empty (null) name in the java: context but I have no idea why it tries to do so.
Any help will be appreciated. And, btw, are there any sources of EJB3 container available? I had no luck to find them.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4048693#4048693
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4048693
19 years, 1 month