[JBossWS] - Re: Using StubExt.PROPERTY_CLIENT_TIMEOUT to control timeout
by jamesjoh
After a lot of time in the debugger I have figured out my issue. I don't think there is a great way to 'solve' it. Basically it looks like there are 3 seperate attempts to 'connect' to the endpoint, each one which honors the timeout. I set my timeout to 45 seconds and it will consistently return from my dispatch.invoke call 2 minutes & 15 seconds later (45 * 3).
First attempt: org.jboss.remoting.transport.http.HttpClientInvoker.useHttpURLConnection. The call to conn.getOutputStream takes 45 seconds to timeout if the endpoint its trying to connect to is unavailable. This throws an exception that is caught. In the exception handling block there is a call to HttpUrlConnection.getResponseMessage(), which chains to HttpUrlConnection.getResponseCode(). In HttpUrlConnection.getResponseCode() there is a call to HttpUrlConnection.getInputStream() which takes 45 seconds to timeout. After that times out it attempts to call HttpUrlConnection.getHeaderField(0) which also takes 45 seconds to time out. Finally control returns up the stack to my dispatch call where I can deal with the timeout.
Seems pretty crappy but there doesn't appear to be anything I can do about it. The actual code for HttpUrlConnection leads into closed source SUN code so I've hit a wall for figuring out if there's anything I can do. Anyway hope this info helps someone, maybe someone will read this and have an idea on how to get a true 45 second timeout.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227915#4227915
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227915
17 years, 1 month
[Installation, Configuration & DEPLOYMENT] - javax.naming.CommunicationException connecting to server
by naveentcs
Hello,
I am running the jboss server on linux m/c using
/opt/jboss-5.0.1.GA/bin/run.sh -b 0.0.0.0
I am trying to connect to server using a JMS client pgm for placing msg in JMS queue defined in server
Getting the below error and the url context property is set to
p.put(Context.PROVIDER_URL, "jnp://10.1.100.10:1099");
Please let me know if anything I am missing here
javax.naming.CommunicationException [Root exception is java.rmi.UnknownHostExcep
tion: Unknown host: CUE-Dev1; nested exception is:
java.net.UnknownHostException: CUE-Dev1]
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:835)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:682)
at javax.naming.InitialContext.lookup(Unknown Source)
at PutTestMsgInQ.main(PutTestMsgInQ.java:29)
Caused by: java.rmi.UnknownHostException: Unknown host: CUE-Dev1; nested excepti
on is:
java.net.UnknownHostException: CUE-Dev1
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown Source)
at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source)
at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:722)
... 3 more
Caused by: java.net.UnknownHostException: CUE-Dev1
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.(Unknown Source)
at java.net.Socket.(Unknown Source)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(Unknown S
ource)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(Unknown S
ource)
... 9 more
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227914#4227914
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227914
17 years, 1 month
[JBoss Tools (users)] - Can't get JBoss AS to start using Jboss Tools
by GermanDev
Hi!
I am using JBoss Tools to develop JBoss Seam web applications. It works great most times, but sometimes I get a very strange behaviour: The server doesn't start and seems to hang, but not even a reboot helps to get it working again. A few minutes later it works just as it should.
This is the output the server produces. After the last line nothing changes no matter how long I wait for it.
| 22:10:36,052 INFO [Server] Starting JBoss (MX MicroKernel)...
| 22:10:36,053 INFO [Server] Release ID: JBoss [Trinity] 4.2.1.GA (build: SVNTag=JBoss_4_2_1_GA date=200707131605)
| 22:10:36,064 INFO [Server] Home Dir: C:\root\app\dev\jboss-4.2.1.GA
| 22:10:36,065 INFO [Server] Home URL: file:/C:/root/app/dev/jboss-4.2.1.GA/
| 22:10:36,066 INFO [Server] Patch URL: null
| 22:10:36,066 INFO [Server] Server Name: default
| 22:10:36,066 INFO [Server] Server Home Dir: C:\root\app\dev\jboss-4.2.1.GA\server\default
| 22:10:36,067 INFO [Server] Server Home URL: file:/C:/root/app/dev/jboss-4.2.1.GA/server/default/
| 22:10:36,067 INFO [Server] Server Log Dir: C:\root\app\dev\jboss-4.2.1.GA\server\default\log
| 22:10:36,067 INFO [Server] Server Temp Dir: C:\root\app\dev\jboss-4.2.1.GA\server\default\tmp
| 22:10:36,067 INFO [Server] Root Deployment Filename: jboss-service.xml
| 22:10:36,733 INFO [ServerInfo] Java version: 1.6.0_13,Sun Microsystems Inc.
| 22:10:36,734 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 11.3-b02,Sun Microsystems Inc.
| 22:10:36,734 INFO [ServerInfo] OS-System: Windows Vista 6.0,x86
| 22:10:37,635 INFO [Server] Core system initialized
| 22:10:43,920 INFO [WebService] Using RMI server codebase: http://localhost:8083/
| 22:10:43,923 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
| 22:10:44,834 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
| 22:10:44,835 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
| 22:10:45,163 INFO [TransactionManagerService] Starting recovery manager
| 22:10:45,425 INFO [TransactionManagerService] Recovery manager started
| 22:10:45,425 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
| 22:10:50,544 INFO [EJB3Deployer] Starting java:comp multiplexer
| 22:10:52,462 INFO [ServiceEndpointManager] jbossws-1.2.1.GA (build=200704151756)
| 22:10:54,817 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jre6\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;native
| 22:10:54,921 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080
| 22:10:54,956 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8009
| 22:10:54,956 INFO [Catalina] Initialization processed in 341 ms
| 22:10:54,956 INFO [StandardService] Starting service jboss.web
| 22:10:54,962 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.0.GA
| 22:10:55,017 INFO [Catalina] Server startup in 60 ms
| 22:10:55,159 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/
| 22:10:55,977 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
| 22:10:56,474 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp7504527706735215458jbossws-context-exp.war/
| 22:10:56,707 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
| 22:10:57,627 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
| 22:10:58,291 INFO [MailService] Mail Service bound to java:/Mail
| 22:10:58,545 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar
| 22:10:58,611 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
| 22:10:58,717 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
| 22:10:58,776 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
| 22:10:58,854 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
| 22:10:58,906 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar
| 22:10:58,918 INFO [QuartzResourceAdapter] start quartz!!!
| 22:10:58,990 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
| 22:10:59,021 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
| 22:10:59,024 INFO [RAMJobStore] RAMJobStore initialized.
| 22:10:59,024 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
| 22:10:59,024 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
| 22:10:59,024 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
| 22:11:00,870 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
| 22:11:01,242 INFO [A] Bound to JNDI name: queue/A
| 22:11:01,244 INFO [B] Bound to JNDI name: queue/B
| 22:11:01,246 INFO [C] Bound to JNDI name: queue/C
| 22:11:01,250 INFO [D] Bound to JNDI name: queue/D
| 22:11:01,253 INFO [ex] Bound to JNDI name: queue/ex
| 22:11:01,275 INFO [testTopic] Bound to JNDI name: topic/testTopic
| 22:11:01,277 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
| 22:11:01,279 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
| 22:11:01,282 INFO [testQueue] Bound to JNDI name: queue/testQueue
| 22:11:01,356 INFO [UILServerILService] JBossMQ UIL service available at : localhost/127.0.0.1:8093
| 22:11:01,400 INFO [DLQ] Bound to JNDI name: queue/DLQ
| 22:11:01,582 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
| 22:11:01,813 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
| 22:11:02,075 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080
| 22:11:02,093 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8009
| 22:11:02,102 INFO [Server] JBoss (MX MicroKernel) [4.2.1.GA (build: SVNTag=JBoss_4_2_1_GA date=200707131605)] Started in 26s:32ms
|
Do you know what the problem might be?
Thank you in advance!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227906#4227906
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227906
17 years, 1 month