Thank you for your reply!
Thank you very much!
That's the solution!
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3878864#3878864
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3878864
I have a similar problem, does anyone have a solution?
--BobC
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3878829#3878829
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3878829
Hi Rawat
I have a similar problem, because Apache is giving me the same error. I am
running JBoss 2.4.2 though. Please let me know whether you got your problem and
how you went out solving this:
My problem goes like this:
I have been unable to get Budi Kurniawan's application to read anything
Right, after a lot more digging firstly I found a reference to adding
local-jndi-name to the individual -jboss.xml descriptor files. This worked
for me, but I notice from postings on the web that it doesn't work for
everyone. Hmmm, I wonder if they are using a version of JBoss earlier
You should never have been looking up the local ejbs from the global jndi
namespace in the first place. Its only an implementation detail of jboss that
allowed you to do this. I doubt it would work an any other app server. You
should be using the ejb-local-ref mechanism to access the local home
Hey
This is how I fixed my problem...
my linux box runs with the ip address 192.168.0.123
as soon as I started JBoss like this:
| run.sh -c default --host=192.168.0.123
|
everything worked fine.
it's the small things you miss that makes everything work fine...
thankx for all the help.
I have a similar problem, If I run my JBoss4 server on windows, and compile it
all there, everything works fine, the app client also works from the other
machines on the network, but when I convert it to compile and run on linux, the
client app can't connect to the linux jboss4 server. What's
Hey, I'm also new to JBoss, I have a couple of examples working, and I used
this in the jndi.properties file, check if it works for your prog...
| java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| java.naming.provider.url=Your JBoss server ip example:
Hi
I seem to have got it working since I posted to the forum. Make sure that the
jar files in your client are the ones that come with the Jboss server you're
connecting to. I think I'd forgotten to do this when upgrading the system.
Rich
View the original post :
sorry I missread the q, you'll probably also need these:
application.xml
ps. you should replace the display-name, home and remote to your program's names
| ?xml version=1.0 encoding=UTF-8?
| !DOCTYPE application-client PUBLIC '-//Sun Microsystems, Inc.//DTD J2EE
Application Client 1.3//EN'
to connect to the jboss server you need this:
| Context initial = new InitialContext();
| Context myEnv = (Context)initial.lookup(java:comp/env);
| Object objref = myEnv.lookup(ejb/ExampleRef);
| ExampleHome home = (ExampleHome)PortableRemoteObject.narrow(objref,
ExampleHome.class);
Yup, I have the correct jar file, I still get that exception,when running the
app on linux with the linux jboss running, it works fine, but as soon as I take
that jar and try and run it on windows it gives me the exception in my post
above.
View the original post :
When I was trying to solve my problem (I've not got Linux for my system) I read
that there are issues with Java on Linux resolving Localhost. I can't remember
what the specific problems are, but I think setting something in the hosts file
(or Linux equivalent) might be a solution.
View the
You mean the hosts file on the linux box where jboss is running or the hosts
file on windows where the client-app is trying to connect from?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3877948#3877948
Reply to the post :
Where it's trying to connect from - but this problem was definitely a client
running on Linux.
The other thing I checked was occurences of ${jboss.bind.address} within
JBoss's config files. I don't think I changed anything, but perhaps I did!
Sorry I can't be more specific!
View the original
cool, I'll check all of that, thanks for the help.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3877950#3877950
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3877950
I have a similar problem maybe , bind: Trying to bind to : java:ejb/Fibo the
tutorial app...
get error :
javax.naming.NameNotFoundException: ejb not bound
However the bind works fine from a java main program and fails from servlet
implementation.
Have tryed java:/comp/env/ejb/Fibo that fails as
I just found out that it seems to be a problem with jetspeed changing the
classloader, so it isn't a JBoss problem.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3877903#3877903
Reply to the post :
By the way I m using JBOSS 4.0
Thanking you for any help
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3877752#3877752
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3877752
Here's what I do when I encounter an exception via the
onException(JMSException) method :
| if (jndiContext != null) {
| try {
| logger.debug(Closing JNDI InitialContext.);
| jndiContext.close();
|
would u mind sending a code snippet. I tried the closing the initial context
but no success.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3877248#3877248
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3877248
Check out jboss-service.xml in
JBOSS SERVER HOME\deploy\jmx-invoker-adaptor-server.sar\META-INF
Uncomment org.jboss.jmx.connector.invoker.AuthenticationInterceptor section.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3876957#3876957
Reply to the post :
rty to Use ./run.sh -c default --host=server's Ip address
./run.sh --help will show you the help message
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3876868#3876868
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3876868
Thank you, my bean is bound in JNDI View MBean ,
but if I deployed all Beans( 10 in my application), all Beans are undeployed.
I don't know the souce of this problem.
Can you help me?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3876882#3876882
Reply to
Are you getting any errors in the console when you go through deployment?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3876889#3876889
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3876889
I don't getting erros in the console, the deployment is successfull, but in my
project, I create on EJB Module and add any Beans in this, It 's correct?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3876900#3876900
Reply to the post :
JDK1.2 has not been supported for nearly 3 years.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3876856#3876856
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3876856
---
Hello Mr. John Stark,
We actually met before, at LAJUG. I hope to see you there again. In fact, I
tried to reach JBoss and invite them again, but I was not responded back to.
Thank you for informing me that JDK 1.2 hasn't been supported for 3 years.
To me, it makes perfect sense that JBoss
You are starting at the wrong point when trying to resolve this problem. A
'NameNotFoundException' usually without fail means that it is not bound.
Remove everything that you have currently deployed
Restart JBoss
Deploy your jar containing the ejb
Check the console to see if any errors are
there is a msg java.net.NoRouteToHostException, Datagram send failed when I
run the app not connected to lan
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3876066#3876066
Reply to the post :
forgot to say that when server and client are on different machines but in the
same domain it works as well.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3875891#3875891
Reply to the post :
Scott,
Thanks for the response. I thought of that (and probably should have mentioned
it in my last post). In any regards when I have just this...
| attribute name=Properties
| java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory
|
A little more information:
The ServiceLocator is a Singleton object which runs as part of the server, and
has its InitalContext bound the first time it's used (this happens in the
ServiceLocator Singleton's constructor). The weirdness I'm experiencing is that
it completes several lookups
The bonehead mistake which was causing the problem: I was always looking up my
EJBs with java:comp/env/ prefixed to the actual JNDI name of the EJB. Now
that I've removed this everything works as it should.
--James
View the original post :
I have figured out what is happening, thought I would add it here just in case
anyone else encounters the problem.
When we build our URL class loader on the client, the URL for the local files
is simply a string built in the code (eg file://documents and settings...) from
the known install
Self followup,
Upon further research I discovered attribute Properties should _not_
reference a file, but instead spell out properties as they would appear in a
properties file. So now I have...
| attribute name=Properties
| java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory
Simply remove the login related properties.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3875215#3875215
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3875215
---
SF
OK a little update. I realized that Message Driven beans wouldn't be able
to achieve everything I needed, so I went back to the lab. ;)
After reading a little about RMI-IIOP (from Ed Roman's book on EJBs) I realized
I was making a mistake. I have to use RMI-IIOP and not just RMI to get in
I found the solution.
Added below two lines of code in my client program
System.setProperty(org.jboss.security.httpInvoker.sslSocketFactoryBuilder,AMSSLSocketFactoryBuilder);
System.setProperty(org.jboss.security.ignoreHttpsHost,true);
AMSSLSocketFactoryBuilder is a class and code is
Hello,
I have done something similar however instead of binding the object directly to
JNDI I have made it a stateless session bean on the server.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3875006#3875006
Reply to the post :
Hello,
You could try specifying the property java.rmi.server.hostname to the jvm that
is running the jboss server. This should be a name or ip the clients can to use
to connect to the server. I think this defaults to localhost (127.0.0.1)
normally.
One way to do this would be to add it to the
I don't think I can do what I need (a logger) with a bean. I need a live
object to keep track of events in an application (the application will notify
the logger) and to notify clients (Remote Objects too) about those events.
View the original post :
Couldn't you just say that Message-Driven Beans are meant for that??? :P :D
I feel so ashamed.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3875066#3875066
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3875066
Logger is a RemoteObject
| public Logger() throws SmileException {
| // me registro en JNDI
| try {
| EJBUtil.setResource(this, Logger.JNDI_NAME);
| System.out.println(Logger registrado);
| } catch
Well.. that is inaccurate.
The RemoteObject is trying to bind itself in its constructor.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3875055#3875055
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3875055
ClassNotFoundException
Add the jbossall-client.jar from the client folder to the classpath of your
client.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3874788#3874788
Reply to the post :
it is already there in the classpath
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3874795#3874795
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3874795
---
This SF.Net
Is the remote server running Linux?
Have you specified the IP address in /etc/hosts?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3874447#3874447
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3874447
Hi,
To clarify I've added to
/usr/local/jboss-4.0.1sp1/server/default/conf/jboss-service.xml
the following:
mbean code=org.jboss.naming.NamingAlias
| name=jboss:service=NamingAlias,fromName=34402
| attribute name=ToName34402_EN/attribute
|
What exactly does the /etc/hosts file need to contain.
The ip address of the machine im connecting to is 192.168.6.19
Thanks
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3873722#3873722
Reply to the post :
| 192.168.1.1 localhost thisPC thisPC.net
|
The machine has the IP 192.168.1.1, his name
is localhost, and thisPC, the net ist 'net', so
localhost.net and thisPC.net are the long names.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3873725#3873725
Reply
Ok found it !
I looks like I had to close the Initialcontext first.
Works nicely now.
cya
Henk
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3873220#3873220
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3873220
In FAQ there is a solution to edit hosts file. But it did not work for us.
Michael
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3873015#3873015
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3873015
(copied from a thread in MQ forum)
Problem:
Looking up the jndi tree of a remote jboss, over http
(http://192.168.20.11:80/invoker/JNDIFactory), works fine from stand-alone java
client.
When doing that from inside a servlet in a local jboss, it returns local jndi
tree of local jboss.
Doing
You need to edit the /etc/hosts of the Linux machine to contain the IP address
of itself, at the moment it is set to 127.0.0.1.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3873038#3873038
Reply to the post :
Thanks a lot! That's it. Seems to me like I need to learn more about
linux-administration...
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3873045#3873045
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3873045
Same problem, was about to post it. I still actually cannot belive it. Well i
use 4.01sp1 so no go with that one. Temporary solution for me is to have them
deployed under different names, add a little R for remote to the other one:).
It's an overhead, but
View the original post :
This is a problem caused by the clustering code, right ? Can we disable
clustering to get around this problem, or is it truly necessary to use a
different name in the remote's JNDI ?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3872738#3872738
Reply to the
I tried JBoss 4.0.2 RC1 and it DOES work. So can someone tell us when will
4.0.2 become official. We are going production with JBoss in May.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3872749#3872749
Reply to the post :
There is a problem with calling beans remotely on some versions of JBoss.
http://jira.jboss.com/jira/browse/JBAS-1442
What JBoss version are you using?
Can you try your code on JBoss 4.0.2 RC1 to see if the fix above solves your
problem.
View the original post :
We are using JBoss 4.01 and we are NOT using clustering. This is a case of one
JBoss simply talking o another JBoss.
May be I should try this on 4.01 SP1 first, that's the version to plan to go
production...
View the original post :
[EMAIL PROTECTED] wrote : We are using JBoss 4.01 and we are NOT using
clustering. This is a case of one JBoss simply talking o another JBoss.
|
The issue does not describe a clustering issue.
The issue describes how an enhancement made to the clustering code has had an
effect on behaviour
501 - 562 of 562 matches
Mail list logo
