Message -
From: "Alex Loubyansky" <[EMAIL PROTECTED]>
To: "Michael Delamere" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, July 04, 2002 10:39 AM
Subject: Re[4]: [JBoss-user] javax.naming.CommunicationException
> MD> I´ve done exatct
>
To: "Michael Delamere" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, July 04, 2002 10:39 AM
Subject: Re[4]: [JBoss-user] javax.naming.CommunicationException
> MD> I´ve done exatctly as you said but unfortunately the problem remains.
>
> Do yo
y" <[EMAIL PROTECTED]>
MD> To: "Michael Delamere" <[EMAIL PROTECTED]>
MD> Sent: Thursday, July 04, 2002 10:22 AM
MD> Subject: Re[2]: [JBoss-user] javax.naming.CommunicationException
>> MD> should I be starting with "-nonaming" (which I´m not)?
uot; <[EMAIL PROTECTED]>
Sent: Thursday, July 04, 2002 10:22 AM
Subject: Re[2]: [JBoss-user] javax.naming.CommunicationException
> MD> should I be starting with "-nonaming" (which I´m not)?
>
> Yes, sure. You are trying to lookup in JBoss JNDI but Tomcat uses it's
&g
Hello Michael,
Are you running tomcat with 'nonaming' option?
If no, tomcat uses its own JNDI.
To start with nonaming:
startup.bat -nonaming
alex
Thursday, July 04, 2002, 10:53:40 AM, you wrote:
MD> Hi,
MD> Originally I had jboss3.0 with an embedded tomcat4.0.3 and my application
MD> worked f
Hi,
Originally I had jboss3.0 with an embedded tomcat4.0.3 and my application
worked fine. Yesterday I attempted to seperate the two by installing jboss
and tomcat on their own.
The client side works until the first call is made via jndi to my staless
session bean. I then get the error stated
Hello Sean,
I had exactly the same error and I found how to avoid it.
Check the JBoss startup log. If jnp server started successfully?
I`m using JBoss-2.4.4_Tomcat-4.0.1(Win2k) and I face its strange behaviour.
It is starting without errors only at first time. At next startups it
generates many
I am using:
Sun JDK 1.4.0_01
Windows 2000
JBoss 3.0.0
I deployed a single Session EJB to JBoss 3.0.0
I wrote a simple client application that performs a JNDI lookup for the
bean's home interface
The JNDI lookup (and subsequent cast) results in a "timed out" error
message.
The JNDI
Hi all
Got a problerm which came out of the blues. My app was running fine until
since lately i've been getting the error listed below. below is the part of
the server.log. I'd appreciate any help.
[Bean Cache] Resized cache for bean ProjectBean: old capacity = 1000, new
capacity = 50
[Default
Hello all,
I am using JBoss 2.2.1 with Jetty 3.1 RC4 on Windows
2000, i have some entity and session beans too..
when i run the jboss server i get the following trace.
Any idea where the problem isi am using jdk1.3.1.
Regards and Thanks in advance
Kash
[Info] Java version: 1.3.1,Sun Micros
Hi -
I am using jboss 2.0 and jdk1.2. I am trying to deploy a simple session
bean.
I put the jar that contains the classes and the ejb-jar.xml into the deploy
directory
and exectute run.bat from the bin directory. I am using Win98.
Heres my jar: --
0 Tue Mar 20 14:35:
Hi -
my jar contains:
0 Tue Mar 20 14:35:46 EST 2001 META-INF/
66 Tue Mar 20 14:35:46 EST 2001 META-INF/MANIFEST.MF
3905 Tue Mar 20 14:16:36 EST 2001 com/web_tomorrow/interest/Interest.class
877 Mon Mar 19 17:39:28 EST 2001
com/web_tomorrow/interest/InterestBean.class
325
Append the results of "jar -tvf your-jar".
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, March 19, 2001 6:42 PM
Subject: [JBoss-user] javax.naming.CommunicationException. Root exception is
java.rmi.StubNotFoundExc
> Hi -
Hi -
I am using jboss 2.0 and jdk1.2. I am trying to deploy a simple session
bean.
I put the jar that contains the classes and the ejb-jar.xml into the deploy
directory
and exectute run.bat from the bin directory. Heres the result:
File logging] Initialized
[Classpath extension] Initializi
14 matches
Mail list logo
