[JNDI/Naming/Network] - Re: How to Access EJB over HTTP in remote machine?
by robert.geisler
"ritesh163" wrote : 21:06:02,350 INFO [ServiceConfigurator] Problem configuring service jboss:service=Naming
| | org.jboss.deployment.DeploymentException: No Attribute found with name: RmiBindAddress
well, i do not exactly know what the reason for this error is, but i would guess it does not depend on the InvokerURLs. ServiceConfigurator says he cannot find "RmiBindAddress". RmiBindAddress is configured in /conf/jboss-service.xml and defaults to "${jboss.bind.address}" which is imho set through the "-b" option.
please check whether JBoss starts successfully with your command if you do not have configured standardjboss.xml, jboss.xml and the InvokerURLs. i would except the error to remain...?
"ritesh163" wrote : Here, I am talking about client side Jboss (machine B). machine A is already in External IP, so it runs on external IP [...] Machine B has internal ip and jboss also run on that ip which is redirected by router ip or external ip.
lets clarify your network topology first. i assume * you have two JBoss instances running (machine A and machine B),
| * your client (application) connects to machine A over JNDI (http) and uses
| * an EJB in machine A which has to access an EJB (http, too) in machine B.
| * machine A do not know the address of machine B, but
| * machine A knows the address of the router and get redirected.is this correct? if yes then... both machines need to use http invokers, i think.* because your client tries to connect to machine A over http (HttpNamingContextFactory), you have to configure the servlets for machine A. the InvokerURLs should be the address of machine A from the clients point of view, because JBoss will return the InvokerURL to tell your client(s proxies) where to connect to.
| * and because machine A tries to connect to machine B over http (external address and redirecting), you have to configure the servlets for machine B. the InvokerURLs should again be the address of machine B from machine As point of view, because machine A will recieve proxies which have to connect to the external/ routing address of machine B.and you have to configure standardjboss.xml and jboss.xml for both machines, of course.
i hope, this works for you.
robert
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160511#4160511
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160511
18 years
[EJB/JBoss] - Could not destroy component: ......
by Ceene
Hello all
I have a problem with one of my Beans. It works well and i have no problems with a method or else. The only problem I have is that if I deploy the Bean new I get the following error:
anonymous wrote : 12:47:51,203 INFO [TomcatDeployer] undeploy, ctxPath=/TCTest, warUrl=.../tmp/deploy/tmp51760TCTest.ear-contents/app-exp.war/
| 12:47:51,250 WARN [Contexts] Could not destroy component: kundehdl
| javax.ejb.EJBException: java.lang.RuntimeException: java.lang.NoClassDefFoundError: com/sun/el/ExpressionFactoryImpl
| at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:63)
| at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83)
| at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
I have the "destroy()"-Method in these Bean, why I get the error?
P.S.: Sry for the bad English.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160500#4160500
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160500
18 years
[Messaging, JMS & JBossMQ] - [ram] registration is not done -> stop
by telukuntla
Hi ,
I am creating topic dynamicaaly. and immidietlly iam lookup the same topic that time its showing , topic in not bounded.
please find the code bellow
creating dynamic topic:
private boolean createJbossTopic(String topicName) throws Exception
{
boolean createStatus=false;
Topic topic=null;
RMIAdaptor server=null;
Hashtable env = new Hashtable();
Context ctx=null;
env.put(Context.INITIAL_CONTEXT_FACTORY,"org.jnp.interfaces.NamingContextFactory");
String PROVIDER_URL = "jnp://192.168.0.71:1099";
env.put(Context.PROVIDER_URL,PROVIDER_URL);
try {
ctx = new InitialContext(env);
}
catch(Exception e){
System.out.println("InitialContext problem::"+ e.getMessage());
}
try
{
server = (RMIAdaptor)ctx.lookup("jmx/invoker/RMIAdaptor");
}
catch(Exception es){
System.out.println("jmx/invoker/RMIAdaptor problem::"+ es.getMessage());
}
server.invoke(destinationManager, "createTopic", new Object[]{topicName,"topic/"+topicName+""},new String[]{String.class.getName(), String.class.getName()});
topic = (Topic) ctx.lookup("topic/"+topicName);
createStatus=true;
// System.out.println("Got topic--> " + ctx.toString());
return createStatus;
}
// here i am lookup the same topic
public boolean dummy(String sender)
{
boolean result=false;
System.out.println(":: Begin Dummy methode");
TopicConnectionFactory cf;
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY,"org.jnp.interfaces.NamingContextFactory");
// env.put(Context.PROVIDER_URL, "localhost");
env.put(Context.PROVIDER_URL, "jnp://192.168.0.170:1099");
try{
System.out.println("Before Thread sleep");
Thread.sleep(300);
System.out.println("After Thread sleep");
}catch (Exception e) {
System.out.println("Exception Thread sleep-->"+e.getMessage());
}
try{
// Thread.yield();
Context ctx = new InitialContext(env);
cf = (TopicConnectionFactory) ctx.lookup("/ConnectionFactory");
Topic destination = (Topic)ctx.lookup("topic/"+sender);
System.out.println("Found Topic");
result=true;
System.out.println("After Topic checking-->"+result);
}catch (Exception e) {
System.out.println("Exception Checking topic sleep-->"+e.getMessage());
}
return result;
}
because this topic has to be refer by the flex client.
for us front end is flex.
Please clarify me , its very urgent for us
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160498#4160498
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160498
18 years
[JBossWS] - new format required for wsdl in JBossws>2.0.0?
by timeagentess
Hello all,
I have some problems transitioning from JBoss 4.0.5 + JBossws 2.0.0 to JBoss 4.2.0 + JBossws 3.0.2.
A simple web service (deployed as an annotated EJB within an ear) which was working perfectly in the initial configuration cannot be consumed by wsconsume in the second configuration:
anonymous wrote : [wsconsume] Failed to read the WSDL document: http://nifhel:8080/webservices-ws/services/WSTwo?wsdl, because 1) could not find the document; /2) the document could not be read; 3) the root element of the document is not <wsdl:definitions>.
| [wsconsume] [ERROR] failed.noservice=Could not find wsdl:service in the provided WSDL(s):
| [wsconsume] At least one WSDL with at least one service definition needs to be provided.
| [wsconsume] Failed to parse the WSDL.
| ...
|
My generated WSDL file indeed does not have a wsdl:service tag as root, it looks like this (with some parts eliminated for clarity):
anonymous wrote :
| <definitions name='WSTwoServiceBeanService' targetNamespace='http://localhost:8080/atb' xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:tns='http://localhost:8080/atb' xmlns:xsd='http://www.w3.org/2001/XMLSchema'>
|
| <xs:schema targetNamespace='http://localhost:8080/atb' version='1.0' xmlns:tns='http://localhost:8080/atb' xmlns:xs='http://www.w3.org/2001/XMLSchema'>
| <xs:element name='hello' type='tns:hello'/>
| <xs:element name='helloResponse' type='tns:helloResponse'/>
| <xs:complexType name='hello'>
| <xs:sequence>
| <xs:element minOccurs='0' name='arg0' type='xs:string'/>
| </xs:sequence>
|
| </xs:complexType>
| <xs:complexType name='helloResponse'>
| <xs:sequence>
| <xs:element minOccurs='0' name='return' type='xs:string'/>
| </xs:sequence>
| </xs:complexType>
| </xs:schema>
|
| [...]
|
How can I influence the generation of a wsdl document which complies to what wsconsume seems to expect? Or is there another mistake I might have made?
Additional things I tried: Searching around led me to this forum post: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102431
and this JIRA issue: http://jira.jboss.org/jira/browse/JBESB-1719, which seem (?) to be related to my problem.
Setting fork="true" for wsconsume like suggested in the forum post linked above led to the gnu.getopt.LongOpt class to be reported as not found, and after adding the corresponding jar to the classpath I get an almost identical error to the one I've started with:
anonymous wrote : [wsconsume] parsing WSDL...
| [wsconsume] [ERROR] Connection reset
| [wsconsume] Failed to read the WSDL document: http://nifhel:8080/webservices-ws/services/WSTwo?wsdl, because 1) could not find the document; /2) the document could not be read; 3) the root element of the document is not <wsdl:definitions>.
| [wsconsume] [ERROR] failed.noservice=Could not find wsdl:service in the provided WSDL(s):
| [wsconsume] At least one WSDL with at least one service definition needs to be provided.
| [wsconsume] Failed to parse the WSDL.
| [wsconsume] Failed to invoke WsImport
| [wsconsume] java.lang.IllegalStateException: WsImport invocation failed. Try the verbose switch for more information
| [wsconsume] at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumerImpl.java:234)
| [wsconsume] at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(WSConsume.java:223)
| [wsconsume] at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:81)
| [wsconsume] Error: Could not import. (use --verbose to see full traces)
| [wsconsume] java.lang.IllegalStateException: WsImport invocation failed. Try the verbose switch for more information
| [wsconsume] at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumerImpl.java:234)
| [wsconsume] at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(WSConsume.java:223)
| [wsconsume] at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:81)
Can anyone help with this issue?
Thank you very much!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160485#4160485
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160485
18 years