[JNDI/Naming/Network] - Re: Proxy ClassCastException after successful EJB lookup
by skymic
Hi cupdike and Peter,
I think I have the same problem with classloaders.
I am using a standalone tomcat V5.5 and try to lookup a remote EJB in a JBoss4.0.5 (on a different machine) using this code in my servlet:
String urlName = "jnp://localhost:1099";
Properties p = new Properties();
p.put(Context.INITIAL_CONTEXT_FACTORY,"org.jnp.interfaces.NamingContextFactory");
p.put(Context.PROVIDER_URL, urlName);
p.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");
InitialContext ic = new InitialContext(p);
Object ref = ic.lookup("SDOCI/remote/SDOCIBusinessService");
SDOCIBusinessService busiService = (SDOCIBusinessService )PortableRemoteObject.narrow(ref, SDOCIBusinessService.class);
I get the following exception:
java.lang.ClassCastException
at com.sun.corba.se.impl.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:229)
Caused by: java.lang.ClassCastException: javax.naming.Reference
Yes I have deployed my remote EJB in an ear on JBoss and also included the interface of my remote bean in a jar in WEB-INF/lib since my webapp must know the interface I am trying to narrow.
Anyway I get this exception.
Does anyone of you have an idea?
Thanks for your help.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4017606#4017606
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4017606
19Â years, 2Â months
[JBoss Eclipse IDE (users)] - Problem Starting JBoss Server in Eclipse Using JBoss Eclipse
by dagat-habagat
Specs:
> Eclipse 3.2
> JBoss AS 4.0.5
> JBoss Eclipse IDE 2.0 Beta2
> Fedora Core 4 Linux Platform
hi!
I am new at using Eclipse and JBoss. I recently installed Eclipse IDE and JBoss AS. Then
I installed JBoss Eclipse IDE into Eclipse. Things were going smoothly as i configured a
new server for JBoss in Eclipse through JBoss Eclipse IDE until i tried to start the newly
configured JBoss server through JBoss IDE. It is weird because at the Eclipse console it
says there that JBoss Server was successfully started.
20:11:23,736 INFO [Server] Starting JBoss (MX MicroKernel)...
20:11:23,742 INFO [Server] Release ID: JBoss [Zion] 4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)
20:11:23,743 INFO [Server] Home Dir: /opt/jboss-4.0.5.GA
20:11:23,743 INFO [Server] Home URL: file:/opt/jboss-4.0.5.GA/
20:11:23,744 INFO [Server] Patch URL: null
20:11:23,744 INFO [Server] Server Name: default
20:11:23,744 INFO [Server] Server Home Dir: /opt/jboss-4.0.5.GA/server/default
20:11:23,744 INFO [Server] Server Home URL: file:/opt/jboss-4.0.5.GA/server/default/
20:11:23,744 INFO [Server] Server Log Dir: /opt/jboss-4.0.5.GA/server/default/log
20:11:23,744 INFO [Server] Server Temp Dir: /opt/jboss-4.0.5.GA/server/default/tmp
20:11:23,745 INFO [Server] Root Deployment Filename: jboss-service.xml
20:11:24,530 INFO [ServerInfo] Java version: 1.5.0_10,Sun Microsystems Inc.
20:11:24,531 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_10-b03,Sun Microsystems Inc.
20:11:24,538 INFO [ServerInfo] OS-System: Linux 2.6.17-1.2142_FC4,i386
20:11:25,012 INFO [Server] Core system initialized
20:11:29,457 INFO [WebService] Using RMI server codebase: http://localhost:8083/
20:11:29,563 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
20:11:38,911 INFO [ServiceEndpointManager] WebServices: jbossws-1.0.3.SP1 (date=200609291417)
20:11:39,950 INFO [SnmpAgentService] SNMP agent going active
20:11:40,563 INFO [InterceptorChainFactory] interceptor chain is:
class org.jboss.cache.interceptors.CallInterceptor
class org.jboss.cache.interceptors.PessimisticLockInterceptor
class org.jboss.cache.interceptors.UnlockInterceptor
class org.jboss.cache.interceptors.ReplicationInterceptor
class org.jboss.cache.interceptors.TxInterceptor
class org.jboss.cache.interceptors.CacheMgmtInterceptor
20:11:41,147 INFO [STDOUT]
-------------------------------------------------------
GMS: address is orange:33186
-------------------------------------------------------
20:11:43,230 INFO [TreeCache] viewAccepted(): [orange:33186|0] [orange:33186]
20:11:43,249 INFO [TreeCache] TreeCache local address is orange:33186
20:11:43,253 INFO [TreeCache] State could not be retrieved (we are the first member in group)
20:11:43,255 INFO [TreeCache] parseConfig(): PojoCacheConfig is empty
20:11:43,864 INFO [DefaultPartition] Initializing
20:11:44,132 INFO [STDOUT]
-------------------------------------------------------
GMS: address is orange:33188 (additional data: 14 bytes)
-------------------------------------------------------
20:11:46,196 INFO [DefaultPartition] Number of cluster members: 1
20:11:46,196 INFO [DefaultPartition] Other members: 0
20:11:46,197 INFO [DefaultPartition] Fetching state (will wait for 30000 milliseconds):
20:11:46,198 INFO [DefaultPartition] New cluster view for partition DefaultPartition (id: 0, delta: 0) : [127.0.0.1:1099]
20:11:46,222 INFO [DefaultPartition] State could not be retrieved (we are the first member in group)
20:11:46,448 INFO [DefaultPartition] I am (127.0.0.1:1099) received membershipChanged event:
20:11:46,448 INFO [DefaultPartition] Dead members: 0 ([])
20:11:46,448 INFO [DefaultPartition] New Members : 0 ([])
20:11:46,448 INFO [DefaultPartition] All Members : 1 ([127.0.0.1:1099])
20:11:46,515 INFO [HANamingService] Started ha-jndi bootstrap jnpPort=1100, backlog=50, bindAddress=localhost/127.0.0.1
20:11:46,531 INFO [DetachedHANamingService$AutomaticDiscovery] Listening on localhost/127.0.0.1:1102, group=230.0.0.4, HA-JNDI address=127.0.0.1:1100
20:11:47,824 INFO [CorbaNamingService] Naming: [IOR:000000000000002B49444C3A6F6D672E6F72672F436F734E616D696E672F4E616D696E67436F6E746578744578743A312E3000000000000200000000000000E0000102000000000A3132372E302E302E31000DC8000000114A426F73732F4E616D696E672F726F6F74000000000000050000000000000008000000004A414300000000010000001C00000000000100010000000105010001000101090000000105010001000000210000005C000000000000000100000000000000240000001C0000007E00000000000000010000000A3132372E302E302E31000DC900400000000000000000001004010008060667810201010100000000000000000000000000000000000000000000002000000004000000000000001F0000000400000003000000010000002000000000000000020000002000000004000000000000001F0000000400000003]
20:11:48,023 INFO [CorbaTransactionService] TransactionFactory: [IOR:000000000000003049444C3A6F72672F6A626F73732F746D2F69696F702F5472616E73616374696F6E466163746F72794578743A312E30000000000200000000000000E0000102000000000A3132372E302E302E31000DC8000000144A426F73732F5472616E73616374696F6E732F46000000050000000000000008000000004A414300000000010000001C00000000000100010000000105010001000101090000000105010001000000210000005C000000000000000100000000000000240000001C0000007E00000000000000010000000A3132372E302E302E31000DC900400000000000000000001004010008060667810201010100000000000000000000000000000000000000000000002000000004000000000000001F0000000400000003000000010000002000000000000000020000002000000004000000000000001F0000000400000003]
20:11:49,421 INFO [Embedded] Catalina naming disabled
20:11:49,481 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rule set.
20:11:49,485 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rule set.
20:11:50,291 INFO [Http11BaseProtocol] Initializing Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080
20:11:50,305 INFO [Catalina] Initialization processed in 817 ms
20:11:50,307 INFO [StandardService] Starting service jboss.web
20:11:50,316 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.20
20:11:50,396 INFO [StandardHost] XML validation disabled
20:11:50,517 INFO [Catalina] Server startup in 210 ms
20:11:50,767 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
20:11:51,448 INFO [WebappLoader] Dual registration of jndi stream handler: factory already defined
20:11:52,464 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jbossweb-tomcat55.sar/ROOT.war/
20:11:52,664 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp38369jbossws-context-exp.war/
20:11:52,885 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
20:11:54,867 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
20:11:56,876 INFO [MailService] Mail Service bound to java:/Mail
20:11:57,449 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar
20:11:57,502 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
20:11:57,537 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
20:11:57,587 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
20:11:57,642 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
20:11:57,960 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar
20:11:59,105 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=HSQLDS' to JNDI name 'java:HSQLDS'
20:12:00,001 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
20:12:00,393 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=MySqlDS' to JNDI name 'java:MySqlDS'
20:12:00,524 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
20:12:03,311 INFO [TomcatDeployer] deploy, ctxPath=/test, warUrl=.../tmp/deploy/tmp38408test-exp.war/
20:12:03,714 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: jboss.ejb:service=EJBTimerService,persistencePolicy=database
State: CONFIGURED
I Depend On:
jboss.jca:service=DataSourceBinding,name=DefaultDS
ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
State: CONFIGURED
I Depend On:
jboss.mq:service=Invoker
jboss.web:service=WebServer
ObjectName: jboss:service=KeyGeneratorFactory,type=HiLo
State: CONFIGURED
I Depend On:
jboss:service=TransactionManager
jboss.jca:service=DataSourceBinding,name=DefaultDS
ObjectName: jboss.mq:service=StateManager
State: CONFIGURED
I Depend On:
jboss.jca:service=DataSourceBinding,name=DefaultDS
Depends On Me:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq:service=DestinationManager
State: CONFIGURED
I Depend On:
jboss.mq:service=MessageCache
jboss.mq:service=PersistenceManager
jboss.mq:service=StateManager
jboss.mq:service=ThreadPool
jboss:service=Naming
Depends On Me:
jboss.mq.destination:service=Topic,name=testTopic
jboss.mq.destination:service=Topic,name=securedTopic
jboss.mq.destination:service=Topic,name=testDurableTopic
jboss.mq.destination:service=Queue,name=testQueue
jboss.mq.destination:service=Queue,name=A
jboss.mq.destination:service=Queue,name=B
jboss.mq.destination:service=Queue,name=C
jboss.mq.destination:service=Queue,name=D
jboss.mq.destination:service=Queue,name=ex
jboss.mq:service=SecurityManager
jboss.mq.destination:service=Queue,name=DLQ
ObjectName: jboss.mq:service=PersistenceManager
State: CONFIGURED
I Depend On:
jboss.jca:service=DataSourceBinding,name=DefaultDS
Depends On Me:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq.destination:service=Topic,name=testTopic
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager
ObjectName: jboss.mq.destination:service=Topic,name=securedTopic
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager
ObjectName: jboss.mq.destination:service=Topic,name=testDurableTopic
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager
ObjectName: jboss.mq.destination:service=Queue,name=testQueue
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager
ObjectName: jboss.mq.destination:service=Queue,name=A
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq.destination:service=Queue,name=B
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq.destination:service=Queue,name=C
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq.destination:service=Queue,name=D
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq.destination:service=Queue,name=ex
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
ObjectName: jboss.mq:service=Invoker
State: CONFIGURED
I Depend On:
jboss.mq:service=TracingInterceptor
jboss:service=Naming
Depends On Me:
jboss.mq:service=InvocationLayer,type=HTTP
jboss.mq:service=InvocationLayer,type=JVM
jboss.mq:service=InvocationLayer,type=UIL2
ObjectName: jboss.mq:service=TracingInterceptor
State: CONFIGURED
I Depend On:
jboss.mq:service=SecurityManager
Depends On Me:
jboss.mq:service=Invoker
ObjectName: jboss.mq:service=SecurityManager
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
Depends On Me:
jboss.mq.destination:service=Topic,name=testTopic
jboss.mq.destination:service=Topic,name=securedTopic
jboss.mq.destination:service=Topic,name=testDurableTopic
jboss.mq.destination:service=Queue,name=testQueue
jboss.mq:service=TracingInterceptor
jboss.mq.destination:service=Queue,name=DLQ
ObjectName: jboss.mq.destination:service=Queue,name=DLQ
State: CONFIGURED
I Depend On:
jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager
ObjectName: jboss.mq:service=InvocationLayer,type=JVM
State: CONFIGURED
I Depend On:
jboss.mq:service=Invoker
ObjectName: jboss.mq:service=InvocationLayer,type=UIL2
State: CONFIGURED
I Depend On:
jboss.mq:service=Invoker
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.jca:service=DataSourceBinding,name=DefaultDS
State: NOTYETINSTALLED
Depends On Me:
jboss.ejb:service=EJBTimerService,persistencePolicy=database
jboss:service=KeyGeneratorFactory,type=HiLo
jboss.mq:service=StateManager
jboss.mq:service=PersistenceManager
20:12:03,857 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080
20:12:04,039 INFO [ChannelSocket] JK: ajp13 listening on localhost/127.0.0.1:8009
20:12:04,052 INFO [JkMain] Jk running ID=0 time=0/35 config=null
20:12:04,067 INFO [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)] Started in 40s:320ms
But on the JBoss IDE Console it says there that JBoss Server cannot be launched until
it reached the Server Time Out..It looks like this,
JBoss40
>Event Log
>Starting Server
> Console Output
Twiddle Launch: Server is Down
Twiddle Launch: Server is Down
Twiddle Launch: Server is Down
Twiddle Launch: Server is Down
Twiddle Launch: Server is Down
Twiddle Launch: Server is Down
.
.
.
.
Twiddle Launch: Server is Down
Twiddle Launch: Server is Down
Server Time Out Reached
But when I check if JBoss is running through my browser, i can see that it is up and running.
It seems that there is something wrong in what the JBoss IDE Console is showing me.
I really have no clue on to what is wrong with my installation.
Thanks in advance for the help!!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4017603#4017603
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4017603
19Â years, 2Â months
[JBoss Seam] - Re: Seam Email - IllegalStateException: No Factories configu
by bsmithjj
I've tried two variants
1.) put the seam-mail.jar and dependencies in the .war as you have done in the example.
2.) put the same set of jars in the .ear
I'm convinced that the issue I'm running into is related to class loading. Reviewing the .ear created by your seam-email example, I'm guessing you have myfaces in the tomcat jsf-libs dir on your test environment - in my case, the myfaces jars are in the .ear due to some class loading issues we had earlier in the project around DataModel and friends. That's the remaining difference between our two .ear projects. I can try putting the myfaces jars back in tomcat and out of the ear - dang this class loading stuff is a PITA! ;-) I was really looking forward to using the Seam email stuff in this project - we have a lot of dynamic email to generate.
If I could make one request to the Seam project now, it would be to review the whole JSF, Myfaces, Facelets, EAR layout, WAR layout, etc... and come up with explicit instructions for how to package a project based on desired functionality. Things like - "should Myfaces be in tomcat, or in your .ear?" etc... right now the answers to these things involves a lot of trial and error and forum digging (not necessarily a bad thing).
Anyways, thanks for the help with this.
Brad Smith
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4017599#4017599
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4017599
19Â years, 2Â months