ObjectName: jboss.remoting:service=Connector,transport=socke

[rks_86]

Hi all,

Am using JBOSS 4.3 {EAP} version
java is Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_15-b04, mixed mode)

OS: Red Hat Enterprise Linux Server release 5.1 (Tikanga)

While stating jboss with below options
./run.sh -c production -b 0.0.0.0

Though it starts but at the end its giving me below error.
Anyone have any idea why this comes then please suggest me
Its giving me following error

5:44:16,401 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
15:44:16,612 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=assemblyDB' to JNDI name 'java:assemblyDB'
15:44:16,635 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
15:44:16,761 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

--- Packages waiting for a deployer ---
org.jboss.deployment.DeploymentInfo@5a8979ae { url=file:/opt/jboss-as/server/jboss2/deploy/css-mode.txt }
 deployer: null
 status: null
 state: INIT_WAITING_DEPLOYER
 watch: file:/opt/jboss-as/server/jboss2/deploy/css-mode.txt
 altDD: null
 lastDeployed: 1225275256760
 lastModified: 1225275256000
 mbeans:

--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@5a8979ae { url=file:/opt/jboss-as/server/jboss2/deploy/css-mode.txt }
 deployer: null
 status: null
 state: INIT_WAITING_DEPLOYER
 watch: file:/opt/jboss-as/server/jboss2/deploy/css-mode.txt
 altDD: null
 lastDeployed: 1225275256760
 lastModified: 1225275256000
 mbeans:

--- MBeans waiting for other MBeans ---
ObjectName: jboss:service=invoker,type=unified
 State: CONFIGURED
 I Depend On:
 jboss:service=TransactionManager
 jboss.remoting:service=Connector,transport=socket

ObjectName: jboss.ejb3:service=EJB3Deployer
 State: CONFIGURED
 I Depend On:
 jboss.aop:service=AspectDeployer
 jboss.ejb:service=EJBDeployer
 jboss.ejb3:service=JarsIgnoredForScanning
 Depends On Me:
 jboss.ws:service=DeployerInterceptorEJB3

ObjectName: jboss.ejb:service=EJBDeployer
 State: CONFIGURED
 I Depend On:
 jboss:service=TransactionManager
 jboss:service=WebService
 Depends On Me:
 jboss.ejb3:service=EJB3Deployer
 jboss.ws:service=DeployerInterceptorEJB21

ObjectName: jboss.ws:service=DeployerInterceptorEJB21
 State: CONFIGURED
 I Depend On:
 jboss.ejb:service=EJBDeployer

ObjectName: jboss.ws:service=DeployerInterceptorEJB3
 State: CONFIGURED
 I Depend On:
 jboss.ejb3:service=EJB3Deployer

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss:service=WebService
 State: NOTYETINSTALLED
 Depends On Me:
 jboss.ejb:service=EJBDeployer

ObjectName: jboss.remoting:service=Connector,transport=socket
 State: NOTYETINSTALLED
 Depends On Me:
 jboss:service=invoker,type=unified


15:44:16,853 ERROR [Server] Root deployment has missing dependencies; continuing
Incomplete Deployment listing:

--- Packages waiting for a deployer ---
org.jboss.deployment.DeploymentInfo@5a8979ae { url=file:/opt/jboss-as/server/jboss2/deploy/css-mode.txt }
 deployer: null
 status: null
 state: INIT_WAITING_DEPLOYER
 watch: file:/opt/jboss-as/server/jboss2/deploy/css-mode.txt
 altDD: null
 lastDeployed: 1225275256760
 lastModified: 1225275256000
 mbeans:

--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@5a8979ae { url=file:/opt/jboss-as/server/jboss2/deploy/css-mode.txt }
 deployer: null
 status: null
 state: INIT_WAITING_DEPLOYER
 watch: file:/opt/jboss-as/server/jboss2/deploy/css-mode.txt
 altDD: null
 lastDeployed: 1225275256760
 lastModified: 1225275256000
 mbeans:

--- MBeans waiting for other MBeans ---
ObjectName: jboss:service=invoker,type=unified
 State: CONFIGURED
 I Depend On:
 jboss:service=TransactionManager
 jboss.remoting:service=Connector,transport=socket

ObjectName: jboss.ejb3:service=EJB3Deployer
 State: CONFIGURED
 I Depend On:
 jboss.aop:service=AspectDeployer
 jboss.ejb:service=EJBDeployer
 jboss.ejb3:service=JarsIgnoredForScanning
 Depends On Me:
 jboss.ws:service=DeployerInterceptorEJB3

ObjectName: jboss.ejb:service=EJBDeployer
 State: CONFIGURED
 I Depend On:
 jboss:service=TransactionManager
 jboss:service=WebService
 Depends On Me:
 jboss.ejb3:service=EJB3Deployer
 jboss.ws:service=DeployerInterceptorEJB21

ObjectName: jboss.ws:service=DeployerInterceptorEJB21
 State: CONFIGURED
 I Depend On:
 jboss.ejb:service=EJBDeployer

ObjectName: jboss.ws:service=DeployerInterceptorEJB3
 State: CONFIGURED
 I Depend On:
 jboss.ejb3:service=EJB3Deployer

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss:service=WebService
 State: NOTYETINSTALLED
 Depends On Me:
 jboss.ejb:service=EJBDeployer

ObjectName: jboss.remoting:service=Connector,transport=socket
 State: NOTYETINSTALLED
 Depends On Me:
 jboss:service=invoker,type=unified


 at org.jboss.deployment.MainDeployer.checkIncompleteDeployments(MainDeployer.java:1385)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:785)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
 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:508)
 at java.lang.Thread.run(Thread.java:595)
15:44:16,879 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8180
15:44:16,914 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-8109
15:44:16,997 INFO [Server] JBoss (MX MicroKernel) [4.3.0.GA (build: SVNTag=JBPAPP_4_3_0_GA date=200801031548)] Started in 27s:223ms

[jaikiran]

You have a css-mode.txt file in the /opt/jboss-as/server/jboss2/deploy/ folder. Since this is not a recognized deployable, you see this exception. Remove this css-mode.txt file from the deploy folder.

[rks_86]

After removing the file also ..Am still getting ERRORS

Help me!!

16:30:56,131 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=assemblyDB' to JNDI name 'java:assemblyDB'
16:30:56,154 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
16:30:56,626 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

--- MBeans waiting for other MBeans ---
ObjectName: jboss:service=invoker,type=unified
 State: CONFIGURED
 I Depend On:
 jboss:service=TransactionManager
 jboss.remoting:service=Connector,transport=socket

ObjectName: jboss.ejb3:service=EJB3Deployer
 State: CONFIGURED
 I Depend On:
 jboss.aop:service=AspectDeployer
 jboss.ejb:service=EJBDeployer
 jboss.ejb3:service=JarsIgnoredForScanning
 Depends On Me:
 jboss.ws:service=DeployerInterceptorEJB3

ObjectName: jboss.ejb:service=EJBDeployer
 State: CONFIGURED
 I Depend On:
 jboss:service=TransactionManager
 jboss:service=WebService
 Depends On Me:
 jboss.ejb3:service=EJB3Deployer
 jboss.ws:service=DeployerInterceptorEJB21

ObjectName: jboss.ws:service=DeployerInterceptorEJB21
 State: CONFIGURED
 I Depend On:
 jboss.ejb:service=EJBDeployer

ObjectName: jboss.ws:service=DeployerInterceptorEJB3
 State: CONFIGURED
 I Depend On:
 jboss.ejb3:service=EJB3Deployer

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss:service=WebService
 State: NOTYETINSTALLED
 Depends On Me:
 jboss.ejb:service=EJBDeployer

ObjectName: jboss.remoting:service=Connector,transport=socket
 State: NOTYETINSTALLED
 Depends On Me:
 jboss:service=invoker,type=unified


16:30:57,019 ERROR [Server] Root deployment has missing dependencies; continuing
Incomplete Deployment listing:

--- MBeans waiting for other MBeans ---
ObjectName: jboss:service=invoker,type=unified
 State: CONFIGURED
 I Depend On:
 jboss:service=TransactionManager
 jboss.remoting:service=Connector,transport=socket

ObjectName: jboss.ejb3:service=EJB3Deployer
 State: CONFIGURED
 I Depend On:
 jboss.aop:service=AspectDeployer
 jboss.ejb:service=EJBDeployer
 jboss.ejb3:service=JarsIgnoredForScanning
 Depends On Me:
 jboss.ws:service=DeployerInterceptorEJB3

ObjectName: jboss.ejb:service=EJBDeployer
 State: CONFIGURED
 I Depend On:
 jboss:service=TransactionManager
 jboss:service=WebService
 Depends On Me:
 jboss.ejb3:service=EJB3Deployer
 jboss.ws:service=DeployerInterceptorEJB21

ObjectName: jboss.ws:service=DeployerInterceptorEJB21
 State: CONFIGURED
 I Depend On:
 jboss.ejb:service=EJBDeployer

ObjectName: jboss.ws:service=DeployerInterceptorEJB3
 State: CONFIGURED
 I Depend On:
 jboss.ejb3:service=EJB3Deployer

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss:service=WebService
 State: NOTYETINSTALLED
 Depends On Me:
 jboss.ejb:service=EJBDeployer

ObjectName: jboss.remoting:service=Connector,transport=socket
 State: NOTYETINSTALLED
 Depends On Me:
 jboss:service=invoker,type=unified


 at org.jboss.deployment.MainDeployer.checkIncompleteDeployments(MainDeployer.java:1385)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:785)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
 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:508)
 at java.lang.Thread.run(Thread.java:595)
16:30:57,038 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8180
16:30:57,058 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-8109
16:30:57,068 INFO [Server] JBoss (MX MicroKernel) [4.3.0.GA (build: SVNTag=JBPAPP_4_3_0_GA date=200801031548)] Started in 26s:578ms

Thanks,
Ricky

[rks_86]

Mainly I want to resolve the following ERROR

ObjectName: jboss.remoting:service=Connector,transport=socket
 State: NOTYETINSTALLED
 Depends On Me:
 jboss:service=invoker,type=unified

The above error does not come in JBoss 4.2.3 GA with default startup options.

But this ERROR is comming in JBoss 4.3 EAP.

[jaikiran]

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss:service=WebService
State: NOTYETINSTALLED
Depends On Me:
jboss.ejb:service=EJBDeployer

ObjectName: jboss.remoting:service=Connector,transport=socket
State: NOTYETINSTALLED
Depends On Me:
jboss:service=invoker,type=unified

Did you do any changes to a clean installation? I see that you have created a "jboss2" profile under the server folder. How did you create it? Are you sure you created it right?

[rks_86]

Actually i did not create it.
It was bundled with the JBoss 4.3 EAP software tar.qz file.
There are 3 folders under server
jboss1 , jboss2, jboss3

No folder structure like minimal,default,all like in Jboss 4.2.3 GA free versions.

I thought jboss1 will be minimal, jboss 2 default and jboss 3 will be all.

so i used the same command to start it, like i do in Jboss 4.2.3 GA free versions
./run.sh -c default -b 0.0.0.0
here i did
./run.sh -c jboss2 -b 0.0.0.0

Note:
No application is deployed yet its just a plain server with out any apps.

[jaikiran]

Unfortunately, i haven't tried the EAP version of JBoss. Someone else with experience on it might be able to help you.

Note:
No application is deployed yet its just a plain server with out any apps.

A clean installation on any server (irrespective of whether its EAP version of free version) should startup without any errors. Maybe the tar.qz file was corrupt?

[rks_86]

Yes i also think so .
I have check the tar.gz file its ok.
no issues with the file.

Hope someone with expertise in EAP will help me.. soon.

Thnks!!

[peterj]

That is weird. First of all, when I download EAP 4.3 from the support site, I get a zip file (whether I download from Windows or Linux). In addition, my copy of EAP 4.3 has, under server: minimal, default, all and production.

Exactly where did you get your copy of EAP from? And what was the full file name of the download?

[rks_86]

File name is:
jboss_EAP4.3_linux.tar.gz

Actually this file is shipped to us by our clients for developmwnt proposes and its a full version with out any limitations.

jboss_EAP4.3_linux.tar size is: 350Mb

Am using Red Hat Enterprise Linux Server release 5.1 (Tikanga) 64 bit
with java version "1.5.0_15"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_15-b04)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_15-b04, mixed mode)

Hey do i need to use any higher version of java..or something like that.
and as you told you downloaded the EAP 4.3 and got folder structure like default,minimal,all and production.
but here i dont have any of these except production which is default that is if you will not mention anything during startup default will go to production as its hard coded in run.sh file.

I need to check these three folders jboss1 jboss2 jboss3 in my soft.
If you get any further info then please do post here.

Thanks.
-Ricky

[rks_86]

Hey Peter Can you tell me what is the file name you downloaded from Redhat support.

Is jboss-eap-4.3.0.GA-1.ep1.8.zip this the file name size:192.mb

Its a 30-day trial right.

[rks_86]

Hey issue resolved.

Actually what ever client gave us we found that in jboss-service.xml file some of the components for webservice and Connector configs are missing .
We replaced with the default and now its working.

Thanks.

[peterj]

That is what I suspected - the configuration you got from the client was incorrect. Glad you found the missing pieces and are running.

I have two EAP downloads:
jboss-eap-4.3.0.GA-1.ep1.8.zip (downloaded in January)
jboss-eap-4.3.0.GA_CP02.zip (downloaded in September)