[Installation, Configuration & DEPLOYMENT] - ObjectName: jboss.remoting:service=Connector, transport=socke
by 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
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185323#4185323
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185323
17 years, 6 months
[Performance Tuning] - Re: [JBoss 5.0-CR2] OutOfMemory JVM Crash during JIT
by ceciiil
Hi Peter,
Thanks for your feedback. My Windows 2003 SP2 server running in 32 bits mode (with /3GB option in boot.ini) is set up with 4GB memory and 4GB paging.
The problem has been reproduced with both JRE-1.6.0_7 and JRE-1.5.0_15.
So I have tried to change my JVM options with increased Perm size as follow :
| jvm_args: -Dprogram.name=pdm.bat -Xms1024m -Xmx1024m -XX:PermSize=512m -XX:MaxPermSize=512m -XX:+Dis
| ableExplicitGC
|
Result : JBoss 5 crashes at startup time ! (with JRE6 - I didn't try this set up with JRE5). Again CompilerThread while this time compiling JBoss method :
| #
| # An unexpected error has been detected by Java Runtime Environment:
| #
| # java.lang.OutOfMemoryError: requested 35608 bytes for Chunk::new. Out of swap space?
| #
| # Internal Error (allocation.cpp:218), pid=5756, tid=8176
| # Error: Chunk::new
| #
| # Java VM: Java HotSpot(TM) Server VM (10.0-b23 mixed mode windows-x86)
| # If you would like to submit a bug report, please visit:
| # http://java.sun.com/webapps/bugreport/crash.jsp
| # The crash happened outside the Java Virtual Machine in native code.
| # See problematic frame for where to report the bug.
| #
|
| --------------- T H R E A D ---------------
|
| Current thread (0x64142800): JavaThread "CompilerThread0" daemon [_thread_in_native, id=8176, stack(0x64330000,0x64380000)]
|
| Stack: [0x64330000,0x64380000]
| [error occurred during error reporting (printing stack bounds), id 0x80000001]
|
|
| Current CompileTask:
| C2:1420 ! org.jboss.ejb3.Ejb3Deployment.deployElement(Ljava/io/InputStream;Lorg/jboss/ejb3/Ejb3HandlerFactory;Ljavax/naming/InitialContext;)V (66 bytes)
|
| Heap
| PSYoungGen total 217472K, used 176224K [0x539d0000, 0x639d0000, 0x639d0000)
| eden space 170432K, 97% used [0x539d0000,0x5dbec148,0x5e040000)
| from space 47040K, 21% used [0x60be0000,0x615dc210,0x639d0000)
| to space 44672K, 0% used [0x5e040000,0x5e040000,0x60be0000)
| PSOldGen total 786432K, used 200494K [0x239d0000, 0x539d0000, 0x539d0000)
| object space 786432K, 25% used [0x239d0000,0x2fd9b9b0,0x539d0000)
| PSPermGen total 524288K, used 39978K [0x039d0000, 0x239d0000, 0x239d0000)
| object space 524288K, 7% used [0x039d0000,0x060da870,0x239d0000)
|
|
So i have fixed the issue decreasing the heap memory :
| jvm_args: -Dprogram.name=pdm.bat -Xms768m -Xmx768m -XX:PermSize=256m -XX:MaxPermSize=256m -XX:+Dis
| ableExplicitGC
|
I can now run the test with the same level of users as in JBoss 4.2.3/EJB2 but lower perfromances as heap size is reduced.
To summarize what we have observed :
- Heap = 1024 / Perm = 256 : JVM crashes with 5 users (JRE5/JRE6)
- Heap = 1024 / Perm = 512 : JVM crashes at JBoss startup time (JRE6)
- Heap = 768 / Perm = 512 = OK (JRE6)
I suspect there is an issue in the way JBoss 5 handles Perm size and CompilerThreads in JIT. And I dont think we will migrate our solution to JBoss 5 as a result unless this issue is fixed.
If you would I can mail you the pic of our GC Viewer while the test is running and until the system crashes (I can't attach a file here and because of my company proxy I can't upload the picture on the www)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185318#4185318
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185318
17 years, 6 months
[JBoss Portal] - WSRP Exception with jboss-portal-2.7.0.CR1-bundled
by axelmotyka
Hello,
iam evaluating JBoss with Portal for my company.
My configuration is:
| * jboss-portal-2.7.0.CR1-bundled
| * Java 1.6.07
| * MS Sql Server 2000
| * MS JDBC 1.2
| * Windows XP SP2
|
Now the only thing i modified is database access:
anonymous wrote :
| <local-tx-datasource>
| <jndi-name>PortalDS</jndi-name>
| <connection-url>jdbc:sqlserver://SQLSERVER:1433;DatabaseName=Portal_DEV</connection-url>
| <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
| <user-name>user</user-name>
| user
|
| <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
|
| <type-mapping>MS SQLSERVER2000</type-mapping>
|
| </local-tx-datasource>
|
All other things are default. When i start jboss with default config, my first exception is:
anonymous wrote :
| 2008-10-29 10:56:28,390 ERROR [org.jboss.deployment.MainDeployer] Could not start deployment: file:/D:/Dev/jboss-4.2.3.GA/server/default/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.war/
| org.jboss.ws.metadata.wsdl.WSDLException: javax.wsdl.WSDLException: WSDLException: faultCode=OTHER_ERROR: Cannot extract schema definition: java.net.SocketException: Connection reset
| at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:154)
| at org.jboss.ws.metadata.umdm.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:295)
| at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCServerMetaDataBuilder.buildMetaData(JAXRPCServerMetaDataBuilder.java:97)
| at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.create(UnifiedMetaDataDeploymentAspect.java:56)
| at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:118)
| at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97)
| at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:90)
| at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
| at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
| 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.server.jmx.LazyMBeanServer.invoke(LazyMBeanServer.java:291)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy201.start(Unknown Source)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
| at org.jboss.deployment.MainDeployer.addDeployer(MainDeployer.java:368)
No i searched the forum, and as far as I understand i have to add:
anonymous wrote : set JAVA_OPTS=%JAVA_OPTS% -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl
| set JAVA_OPTS=%JAVA_OPTS% -Djboss.platform.mbeanserver
| set JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote
|
But that didnt help.
I am a totaly new to JBoss and most of the J2EE stuff.
What must be done to execute JBoss+Portal without exceptions?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185317#4185317
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4185317
17 years, 6 months