[Design of JBoss Profiler] - Re: problem with jboss profiler 2.0 beta 2 on jboss version
by sairamvla
If I start profiler with $JAVA_HOME/bin/java -Djboss-profiler-client.properties=$JBOSS_HOME/bin/jboss-profiler-client.properties -jar jboss-profiler-client.jar startProfiler
I am getting the following exception:
[org.jboss.remoting.transport.socket.MicroSocketClientInvoker] Received version 254: treating as end of file
2008-08-20 12:23:07,946 INFO [org.jboss.remoting.transport.socket.MicroSocketClientInvoker] Received version 254: treating as end of file
2008-08-20 12:23:07,947 INFO [org.jboss.remoting.transport.socket.MicroSocketClientInvoker] Received version 254: treating as end of file
2008-08-20 12:23:07,948 ERROR [org.jboss.remoting.transport.socket.SocketClientInvoker] Got marshalling exception, exiting
java.net.SocketException: end of file
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:580)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
at org.jboss.remoting.Client.invoke(Client.java:1550)
at org.jboss.remoting.Client.invoke(Client.java:530)
at org.jboss.remoting.Client.invoke(Client.java:518)
at org.jboss.profiler.client.cmd.Client.main(Client.java:254)
2008-08-20 12:23:07,949 ERROR [org.jboss.profiler.client.cmd.Client] Failed to communicate. Problem during marshalling/unmarshalling; nested exception is:
java.net.SocketException: end of file
java.rmi.MarshalException: Failed to communicate. Problem during marshalling/unmarshalling; nested exception is:
java.net.SocketException: end of file
at org.jboss.remoting.transport.socket.SocketClientInvoker.handleException(SocketClientInvoker.java:122)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:654)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
at org.jboss.remoting.Client.invoke(Client.java:1550)
at org.jboss.remoting.Client.invoke(Client.java:530)
at org.jboss.remoting.Client.invoke(Client.java:518)
at org.jboss.profiler.client.cmd.Client.main(Client.java:254)
Caused by: java.net.SocketException: end of file
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:580)
... 5 more
[kndev@appserver02dvhq /usr/local/jboss-4.2.2.GA/bin]$ ./startprofiler.sh
2008-08-20 12:26:28,350 INFO [org.jboss.remoting.transport.socket.MicroSocketClientInvoker] Received version 254: treating as end of file
2008-08-20 12:26:28,353 INFO [org.jboss.remoting.transport.socket.MicroSocketClientInvoker] Received version 254: treating as end of file
2008-08-20 12:26:28,355 INFO [org.jboss.remoting.transport.socket.MicroSocketClientInvoker] Received version 254: treating as end of file
2008-08-20 12:26:28,356 ERROR [org.jboss.remoting.transport.socket.SocketClientInvoker] Got marshalling exception, exiting
java.net.SocketException: end of file
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:580)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
at org.jboss.remoting.Client.invoke(Client.java:1550)
at org.jboss.remoting.Client.invoke(Client.java:530)
at org.jboss.remoting.Client.invoke(Client.java:518)
at org.jboss.profiler.client.cmd.Client.main(Client.java:254)
2008-08-20 12:26:28,357 ERROR [org.jboss.profiler.client.cmd.Client] Failed to communicate. Problem during marshalling/unmarshalling; nested exception is:
java.net.SocketException: end of file
java.rmi.MarshalException: Failed to communicate. Problem during marshalling/unmarshalling; nested exception is:
java.net.SocketException: end of file
at org.jboss.remoting.transport.socket.SocketClientInvoker.handleException(SocketClientInvoker.java:122)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:654)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
at org.jboss.remoting.Client.invoke(Client.java:1550)
at org.jboss.remoting.Client.invoke(Client.java:530)
at org.jboss.remoting.Client.invoke(Client.java:518)
at org.jboss.profiler.client.cmd.Client.main(Client.java:254)
Caused by: java.net.SocketException: end of file
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:580)
... 5 more
[kndev@appserver02dvhq /usr/local/jboss-4.2.2.GA/bin]$ ./startprofiler.sh
2008-08-20 12:27:08,967 INFO [org.jboss.remoting.transport.socket.MicroSocketClientInvoker] Received version 254: treating as end of file
2008-08-20 12:27:08,970 INFO [org.jboss.remoting.transport.socket.MicroSocketClientInvoker] Received version 254: treating as end of file
2008-08-20 12:27:08,971 INFO [org.jboss.remoting.transport.socket.MicroSocketClientInvoker] Received version 254: treating as end of file
2008-08-20 12:27:08,972 ERROR [org.jboss.remoting.transport.socket.SocketClientInvoker] Got marshalling exception, exiting
java.net.SocketException: end of file
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:580)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
at org.jboss.remoting.Client.invoke(Client.java:1550)
at org.jboss.remoting.Client.invoke(Client.java:530)
at org.jboss.remoting.Client.invoke(Client.java:518)
at org.jboss.profiler.client.cmd.Client.main(Client.java:254)
2008-08-20 12:27:08,973 ERROR [org.jboss.profiler.client.cmd.Client] Failed to communicate. Problem during marshalling/unmarshalling; nested exception is:
java.net.SocketException: end of file
java.rmi.MarshalException: Failed to communicate. Problem during marshalling/unmarshalling; nested exception is:
java.net.SocketException: end of file
at org.jboss.remoting.transport.socket.SocketClientInvoker.handleException(SocketClientInvoker.java:122)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:654)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
at org.jboss.remoting.Client.invoke(Client.java:1550)
at org.jboss.remoting.Client.invoke(Client.java:530)
at org.jboss.remoting.Client.invoke(Client.java:518)
at org.jboss.profiler.client.cmd.Client.main(Client.java:254)
Caused by: java.net.SocketException: end of file
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:580)
... 5 more
[kndev@appserver02dvhq /usr/local/jboss-4.2.2.GA/bin]$ ./startprofiler.sh
2008-08-20 12:29:24,931 ERROR [org.jboss.profiler.client.cmd.Client] Can not get connection to server. Problem establishing socket connection for InvokerLocator [socket://localhost:5400/]
org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [socket://localhost:5400/]
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:530)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
at org.jboss.remoting.Client.invoke(Client.java:1550)
at org.jboss.remoting.Client.invoke(Client.java:530)
at org.jboss.remoting.Client.invoke(Client.java:518)
at org.jboss.profiler.client.cmd.Client.main(Client.java:254)
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:520)
at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:801)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:526)
... 5 more
[kndev@appserver02dvhq /usr/local/jboss-4.2.2.GA/bin]$ ./startprofiler.sh
2008-08-20 12:31:55,331 INFO [org.jboss.remoting.transport.socket.MicroSocketClientInvoker] Received version 254: treating as end of file
2008-08-20 12:31:55,334 INFO [org.jboss.remoting.transport.socket.MicroSocketClientInvoker] Received version 254: treating as end of file
2008-08-20 12:31:55,335 INFO [org.jboss.remoting.transport.socket.MicroSocketClientInvoker] Received version 254: treating as end of file
2008-08-20 12:31:55,336 ERROR [org.jboss.remoting.transport.socket.SocketClientInvoker] Got marshalling exception, exiting
java.net.SocketException: end of file
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:580)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
at org.jboss.remoting.Client.invoke(Client.java:1550)
at org.jboss.remoting.Client.invoke(Client.java:530)
at org.jboss.remoting.Client.invoke(Client.java:518)
at org.jboss.profiler.client.cmd.Client.main(Client.java:254)
2008-08-20 12:31:55,337 ERROR [org.jboss.profiler.client.cmd.Client] Failed to communicate. Problem during marshalling/unmarshalling; nested exception is:
java.net.SocketException: end of file
java.rmi.MarshalException: Failed to communicate. Problem during marshalling/unmarshalling; nested exception is:
java.net.SocketException: end of file
at org.jboss.remoting.transport.socket.SocketClientInvoker.handleException(SocketClientInvoker.java:122)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:654)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
at org.jboss.remoting.Client.invoke(Client.java:1550)
at org.jboss.remoting.Client.invoke(Client.java:530)
at org.jboss.remoting.Client.invoke(Client.java:518)
at org.jboss.profiler.client.cmd.Client.main(Client.java:254)
Caused by: java.net.SocketException: end of file
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:580)
... 5 more
[
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171617#4171617
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171617
17 years, 7 months
[Design of JBoss Profiler] - problem with jboss profiler 2.0 beta 2 on jboss version 4.2.
by sairamvla
Hi,
I need urgent help. I downloaded jboss profiler 2.0 beta 2 from http://www.jboss.org/jbossprofiler/downloads/ and installed as per instructions:
* Copy jboss-profiler.jar to jbossas/bin
* Copy jboss-profiler.properties to jbossas/bin
* Edit jboss-profiler.properties in jbossas/bin to include the classes to be profiled
* Copy jboss-profiler-plugins.jar to jbossas/bin
* Edit run.conf (Unix) or run.bat (Windows) in jbossas/bin to include JBoss Profiler in JAVA_OPTS
* Copy jboss-profiler.sar to jbossas/server//deploy
* Boot application server
But when I am starting profiler with $JAVA_HOME/bin/java -jar jboss-profiler-client.jar startProfiler, I am getting issue. It is throwing exception:
ERROR [org.jboss.profiler.client.cmd.Client] Can not get connection to server. Problem establishing socket connection for InvokerLocator [socket://localhost:5400/]
org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [socket://localhost:5400/]
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:530)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
at org.jboss.remoting.Client.invoke(Client.java:1550)
at org.jboss.remoting.Client.invoke(Client.java:530)
at org.jboss.remoting.Client.invoke(Client.java:518)
at org.jboss.profiler.client.cmd.Client.main(Client.java:254)
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:520)
at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:801)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:526)
... 5 more
In jmx-console I have following for Communicator Mbean:
SocketPort int
Socket boolean RW True
Host java.lang.String R 0.0.0.0
RmiPort int RW
HttpPort int RW
Http boolean RW True
Rmi boolean RW True
I started jboss with option -Djboss.bind.address=0.0.0.0. Is this causing issue? Please suggest how to fix it.
Thanks in advance,
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171602#4171602
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171602
17 years, 7 months
[Design of POJO Server] - Re: Looking at deployment structure - JBAS-5823
by bstansberry＠jboss.com
No I meant the testsuite didn't run to completion:
| tests-clustered-profileservice:
| .....
| [server:start] Starting server "cluster-profilesvc-0", with command (start timeout is 120 seconds ):
| [server:start] /qa/tools/opt/jdk1.5.0_15/bin/java -cp /qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/build/output/jboss-5.0.0.CR2/bin/run.jar:/qa/tools/opt/jdk1.5.0_15/lib/tools.jar -Xms128m -Xmx512m -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryError -Djava.net.preferIPv4Stack=true -Djava.endorsed.dirs=/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/build/output/jboss-5.0.0.CR2/lib/endorsed -Dresolve.dns=false -Djgroups.udp.ip_ttl=0 -Djboss.messaging.ServerPeerID=0 -Djboss.partition.name=DefaultPartition org.jboss.Main -c cluster-profilesvc-0 -b 10.18.34.175 -u 227.43.0.80
| [server:start] Starting server "cluster-profilesvc-1", with command (start timeout is 120 seconds ):
| [server:start] /qa/tools/opt/jdk1.5.0_15/bin/java -cp /qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/build/output/jboss-5.0.0.CR2/bin/run.jar:/qa/tools/opt/jdk1.5.0_15/lib/tools.jar -Xms128m -Xmx512m -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryError -Djava.net.preferIPv4Stack=true -Djava.endorsed.dirs=/qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/build/output/jboss-5.0.0.CR2/lib/endorsed -Dresolve.dns=false -Djgroups.udp.ip_ttl=0 -Djboss.messaging.ServerPeerID=1 -Djboss.partition.name=DefaultPartition org.jboss.Main -c cluster-profilesvc-1 -b 10.18.34.176 -u 227.43.0.80
| [server:start] Failed to start server "cluster-profilesvc-1" before timeout. Destroying the process.
|
| BUILD FAILED
| /qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/build.xml:935: The following error occurred while executing this line:
| /qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/testsuite/imports/config/tests-clustering.xml:337: Error starting server "cluster-profilesvc-1": Server failed to start; see logs.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171540#4171540
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171540
17 years, 7 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Paging discussion:
by clebert.suconic＠jboss.com
"timfox" wrote : "clebert.suconic(a)jboss.com" wrote :
| | I would need a parameter on increment / decrement to determine if it is durable or not. The ServerMessage don't know about that
|
| Yes, I'd add a parameter. Otherwise for durable messages you going to have to call two methods - incrementDurable() and incrementPaging() or whatever you called it.
increment and decrement are atomic operations.
If I add a parameter I would be dealing with two counters, and those methods would need to become void.
This is the current ack code on my Branch. Notice that those counters are called atomically... so I really need two methods:
private void doAck(final MessageReference ref) throws Exception
| {
| ServerMessage message = ref.getMessage();
|
| Queue queue = ref.getQueue();
|
| if (message.decrementRefCount() == 0)
| {
| postOffice.messageDone(message);
| }
|
| if (message.isDurable() && queue.isDurable())
| {
| int count = message.decrementDurableRefCount();
|
| if (count == 0)
| {
| storageManager.storeDelete(message.getMessageID());
| }
| else
| {
| storageManager.storeAcknowledge(queue.getPersistenceID(), message.getMessageID());
| }
| }
|
| queue.referenceAcknowledged(ref);
| }
|
Another option would be to add two arguments to return the two counters... such as:
increment(boolean durable, AtomicInt returnDurable, AtomicInt returnNonDurable);
But that's terrible... so I will just keep two methods.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171526#4171526
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171526
17 years, 7 months