[Installation, Configuration & Deployment] - java.rmi.server.ExportException
by hussain_rangwala
hi guys,
this is a weird problem that i am facing....actually i get this error wen i start run.bat from bin directory....actually my application was running fine till last week ...however wen i returned from the weekend and tried to start the server i got this error....please help me out to resolve this issue.........I have downloaded jboss portal 2.4.0.GA and i have jdk 1.5 installed on my machine.....
| 2007-01-29 17:26:06,233 DEBUG [org.jboss.naming.NamingService] Starting failed jboss:service=Naming
| java.rmi.server.ExportException: Port already in use: 1098; nested exception is:
| java.net.BindException: Address already in use: JVM_Bind
| at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:243)
| at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:178)
| at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
| at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
| at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:180)
| at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:293)
| at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:256)
| at org.jnp.server.Main.initJnpInvoker(Main.java:314)
| at org.jnp.server.Main.start(Main.java:277)
| at org.jboss.naming.NamingService.startService(NamingService.java:236)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| at org.jboss.system.ServiceController.start(ServiceController.java:435)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy4.start(Unknown Source)
| at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:755)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy5.deploy(Unknown Source)
| at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
| at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
| at org.jboss.Main.boot(Main.java:200)
| at org.jboss.Main$1.run(Main.java:464)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: java.net.BindException: Address already in use: JVM_Bind
| at java.net.PlainSocketImpl.socketBind(Native Method)
| at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
| at java.net.ServerSocket.bind(ServerSocket.java:319)
| at java.net.ServerSocket.<init>(ServerSocket.java:185)
| at org.jboss.net.sockets.DefaultSocketFactory.createServerSocket(DefaultSocketFactory.java:120)
| at org.jboss.net.sockets.DefaultSocketFactory.createServerSocket(DefaultSocketFactory.java:95)
| at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:622)
| at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:231)
| ... 61 more
| 2007-01-29 17:26:06,233 WARN [org.jboss.system.ServiceController] Problem starting service jboss:service=Naming
| java.rmi.server.ExportException: Port already in use: 1098; nested exception is:
| java.net.BindException: Address already in use: JVM_Bind
| at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:243)
| at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:178)
| at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
| at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
| at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:180)
| at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:293)
| at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:256)
| at org.jnp.server.Main.initJnpInvoker(Main.java:314)
| at org.jnp.server.Main.start(Main.java:277)
| at org.jboss.naming.NamingService.startService(NamingService.java:236)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| at org.jboss.system.ServiceController.start(ServiceController.java:435)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy4.start(Unknown Source)
| at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:755)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy5.deploy(Unknown Source)
| at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
| at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
| at org.jboss.Main.boot(Main.java:200)
| at org.jboss.Main$1.run(Main.java:464)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: java.net.BindException: Address already in use: JVM_Bind
| at java.net.PlainSocketImpl.socketBind(Native Method)
| at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
| at java.net.ServerSocket.bind(ServerSocket.java:319)
| at java.net.ServerSocket.<init>(ServerSocket.java:185)
| at org.jboss.net.sockets.DefaultSocketFactory.createServerSocket(DefaultSocketFactory.java:120)
| at org.jboss.net.sockets.DefaultSocketFactory.createServerSocket(DefaultSocketFactory.java:95)
| at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:622)
| at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:231)
| ... 61 more
|
Kindly reply as soon as possible
Thanks and Regards
Hussain
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4007737#4007737
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4007737
19 years, 2 months
[Messaging, JMS & JBossMQ] - JMSException while initializing DLQHandler
by mschwarz
Hi there,
I'm using JBoss 3.2.7 and just tried to start the server which includes a configuration for an ActiveMQ Service.
Unfortunately a JMSException is thrown during startup.
| Initialization failed DLQHandler
| javax.jms.JMSException: Error creating the dlq connection:
| Failed to find method for hash:-790108502850547550
| available={
| -884175917852741154=public abstract java.lang.Object org.jnp.interfaces.Naming.lookup(javax.naming.Name)
| throws javax.naming.NamingException,java.rmi.RemoteException,
| -5642140585403320990=public abstract java.util.Collection org.jnp.interfaces.Naming.listBindings(javax.naming.Name)
| throws javax.naming.NamingException,java.rmi.RemoteException,
| 7733619496521189953=public abstract java.io.Serializable org.jboss.ha.framework.interfaces.HAPartition$HAPartitionStateTransfer.getCurrentState(),
| -4221607359560216057=public abstract java.util.Collection org.jnp.interfaces.Naming.list(javax.naming.Name)
| throws javax.naming.NamingException,java.rmi.RemoteException,
| -5717908715153450081=public abstract void org.jnp.interfaces.Naming.rebind(javax.naming.Name,java.lang.Object,java.lang.String)
| throws javax.naming.NamingException,java.rmi.RemoteException,
| 6991977298034536864=public abstract void org.jboss.ha.framework.interfaces.HAPartition$HAPartitionStateTransfer.setCurrentState(java.io.Serializable),
| -8107796390111393345=public abstract void org.jnp.interfaces.Naming.unbind(javax.naming.Name)
| throws javax.naming.NamingException,java.rmi.RemoteException,
| -7286638714004764603=public abstract javax.naming.Context org.jnp.interfaces.Naming.createSubcontext(javax.naming.Name)
| throws javax.naming.NamingException,java.rmi.RemoteException,
| -6149798079139202860=public abstract void org.jnp.interfaces.Naming.bind(javax.naming.Name,java.lang.Object,java.lang.String)
| throws javax.naming.NamingException,java.rmi.RemoteException
| }
| at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:171)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:237)
| at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:164)
| at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:563)
| at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:780)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
| at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:324)
| at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:899)
| at $Proxy215.start(Unknown Source)
|
I deleted all of the JMS_MESSAGES which were still in my database and tried again, but I get the same error coming up.
Can anybody give me a hint what causes this problem ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4007735#4007735
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4007735
19 years, 2 months
[JCA/JBoss] - Re: EJB3 - XA datasource - Transactions - XAER_OUTSIDE
by adrian＠jboss.org
"apill" wrote :
| How could the connection be used in a local transaction when the data source is setup as XA?
|
e.g. Hibernate or the EJB2.1 container will check the tables exist during deployment.
During deployment there is no JTA transaction, so they are free to do:
| connection.setAutoCommit(false);
| try
| {
| // check/create tables
| }
| finally
| {
| connection.commit();
|
| }
|
Which is a local transaction.
This is option (1) on the list of solutions on the link posted.
If this was the problem then using no-tx-seperate-pools would fix it.
The connection used outside a JTA transaction would NOT be used
for a connection inside a JTA transaction (they would come from different
sub-pools).
anonymous wrote :
| What does it mean by
|
| Quote:
|
| change the application attributes or application to complete the connection.
|
|
| Is that something I can do, or is it something JBoss needs to do?
|
This is option (2) on the list of solutions.
It means you are passing the wrong parameters. This is not the case
for JBoss, which will pass the XID and the correct flags to the
XAResource.start()
Which leaves option (3) - apply patches to fix the database/jdbc driver.
ALL THE OTHER QUESTIONS ARE FOR IBM.
There is nothing we can do to fix/debug IBM drivers or "guess"
what the problem is for an IBM generated error message.
(That is short of reverse engineering, which I'm sure is disallowed
by their license :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4007733#4007733
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4007733
19 years, 2 months
[JBoss Seam] - Devided application ignores some classes
by hubaer
Hi all,
I have problems deviding my application in differnent ears, to use it on a distributed environment.
At the moment I have one EAR file including the complete application (session beans, entity bean in a JAR file and all the web stuff in a WAR file).
Now I want to devide the application in two separate ears.
1. One for the business logic (APP-EAR)
2. One for the web frontend (WEB-EAR)
I devided it so far as followed:
APP-EAR:
+- JAR:
+--- session beans with business logic.
+--- entity beans
+--- persistence context
WEB-EAR:
+- JAR:
| +--- session beans for Seam.
+- WAR:
| +--- jsf pages, config files etc.
+- Client-JAR of APP-EAR
+--- including the remote interfaces and entity beans to connect to EAR1.
The entity beans have the seam annotations @Name and @Scope, and are the same classes in both APP-EAR and Client of APP-EAR.
The APP-EAR has no seam.properties so Seam ignore it at deployment (as expected).
The Client of APP-EAR has the seam.properties and so Seam register the entity beans on deployment of the WEB-EAR.
But not all entity beans will be registered as Component and the web application fails, if I try to use an IN-annotated attribute, with the message "RequiredException: In attribute requires value for component".
I figured out that only parent classes of an inheritance are missing after deployment.
So if I have class A and class B (which is extended from A) B is registered as compoment, A is missing. If I put A in the compoments.xml the IN-annotated attribute can be resolved.
All worked fine as all was together in one ear.
So do I miss something? Why are some classes ignored?
Regards
Marco
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4007726#4007726
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4007726
19 years, 2 months