[Clustering/JBoss] - two nodes not joining cluster, while merge view is successfu
by navkalp
Hi,
I am running tow nodes on the difference machine, with the basic jboss cluster configuration.
These two nodes are not joining each other, while I can see following message in the log.
17:06:47,124 INFO [TreeCache] viewAccepted(): MergeView::[172.16.64.21:37784|1] [172.16.64.21:37784, 172.16.64.24:36902], su
bgroups=[[172.16.64.21:37784|0] [172.16.64.21:37784], [172.16.64.24:36902|0] [172.16.64.24:36902]]
17:21:42,192 WARN [NAKACK] 172.16.64.24:36909] discarded message from non-member 172.16.64.21:37791, my view is [172.16.64.2
4:36909|0] [172.16.64.24:36909]
Could somebody help me out.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192808#4192808
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4192808
17 years, 5 months
[Installation, Configuration & DEPLOYMENT] - Re: ERROR deployment.scanner.AbstractDeploymentScanner$Scan
by venugopalp
The application(ear) is deployed successfully in jboss-4.0.2 on Linux with j2sdk-1.4.2, when we do load test(on sockets and threads used in the application) on the application we are getting the following exception
Oct-17-2008 08:30:24 ERROR jboss.naming.NamingService run.428 - Naming accept handler stopping
java.net.SocketException: Too many open files
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353)
at java.net.ServerSocket.implAccept(ServerSocket.java:448)
at java.net.ServerSocket.accept(ServerSocket.java:419)
at org.jnp.server.Main$AcceptHandler.run(Main.java:417)
at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:134)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
at java.lang.Thread.run(Thread.java:534)
Oct-17-2008 08:30:24 ERROR jboss.naming.NamingService run.428 - Naming accept handler stopping
java.net.SocketException: Too many open files
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353)
at java.net.ServerSocket.implAccept(ServerSocket.java:448)
at java.net.ServerSocket.accept(ServerSocket.java:419)
at org.jnp.server.Main$AcceptHandler.run(Main.java:417)
at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:134)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
at java.lang.Thread.run(Thread.java:534)
Oct-17-2008 08:30:24 ERROR jboss.naming.NamingService run.428 - Naming accept handler stopping
java.net.SocketException: Too many open files
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353)
at java.net.ServerSocket.implAccept(ServerSocket.java:448)
at java.net.ServerSocket.accept(ServerSocket.java:419)
at org.jnp.server.Main$AcceptHandler.run(Main.java:417)
at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:134)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
at java.lang.Thread.run(Thread.java:534)
Oct-17-2008 08:30:26 ERROR deployment.scanner.AbstractDeploymentScanner$ScannerThread doScan.207 - Scanning failed; continuing
java.lang.NullPointerException
Oct-17-2008 08:30:28 ERROR jboss.naming.NamingService run.428 - Naming accept handler stopping
java.net.SocketException: Too many open files
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353)
at java.net.ServerSocket.implAccept(ServerSocket.java:448)
at java.net.ServerSocket.accept(ServerSocket.java:419)
at org.jnp.server.Main$AcceptHandler.run(Main.java:417)
at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:134)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
at java.lang.Thread.run(Thread.java:534)
Oct-17-2008 08:30:31 ERROR deployment.scanner.AbstractDeploymentScanner$ScannerThread doScan.207 - Scanning failed; continuing
java.lang.NullPointerException
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192802#4192802
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4192802
17 years, 5 months
[JBossWS] - Wrong minOccurs in wsdl generated by Jboss
by Gitu
I hope this is the righht forum
Am using JBOSS 4.3.0 with WebService. WSDL is autogenerated by JBOSS.
Issue in wsdl is with minOccurs in WSDL. Even method arguments are optional(minOcuurs="0")
For E. G My Method Signature is "getJobByName(String aJobName)" , generated wsdl has aJobName optional.
For some other methods its mandatory , which I dont understand how as there is hardly any difference .
| <xs:complexType name="getJobByName">
| <xs:sequence>
| <xs:element minOccurs="0" name="aJobName" type="xs:string"/>
| </xs:sequence>
| </xs:complexType>
|
|
Also , for some complex type (model object) , some fields are optional , others mandatory like Model (JobBean) which has name , type , version
Here Name and type will be generated as optional and version as mandatory. How can I fix it ?
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192801#4192801
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4192801
17 years, 5 months