[Installation, Configuration & DEPLOYMENT] - Unexpected error processing socket in jboss-4.0.5.GA
by jigu888
Hi,
I have deployed my application on jboss-4.0.5.GA and it is running smoothly since last 6 months. But last week suddenly the application stopped responding and was not accessible. I checked the log file and got following:
-------------------------------------------------------
09:03:54,593 INFO [STDOUT] Done.....
09:03:58,218 ERROR [CoyoteAdapter] An exception or error occurred in the container during the request processing
09:04:00,625 ERROR [Http11Processor] Error processing request
09:04:04,218 ERROR [PoolTcpEndpoint] Unexpected error processing socket
09:04:06,593 ERROR [STDERR] Exception in thread "http-0.0.0.0-443-2"
09:04:10,218 ERROR [CoyoteAdapter] An exception or error occurred in the container during the request processing
09:04:12,624 ERROR [Http11Processor] Error processing request
09:04:16,202 ERROR [PoolTcpEndpoint] Unexpected error processing socket
09:04:18,609 ERROR [STDERR] Exception in thread "http-0.0.0.0-443-10"
09:04:22,468 ERROR [CoyoteAdapter] An exception or error occurred in the container during the request processing
09:04:24,843 ERROR [Http11Processor] Error processing request
09:04:28,452 ERROR [PoolTcpEndpoint] Unexpected error processing socket
09:04:30,843 ERROR [STDERR] Exception in thread "http-0.0.0.0-443-12"
09:04:32,483 INFO [STDOUT] Done.....
09:04:32,483 INFO [STDOUT] Not AdminN
09:04:33,155 INFO [STDOUT] Done.....
09:04:33,155 INFO [STDOUT] Not AdminN
09:04:42,952 ERROR [CoyoteAdapter] An exception or error occurred in the container during the request processing
09:04:45,358 ERROR [Http11Processor] Error processing request
09:04:48,952 ERROR [PoolTcpEndpoint] Unexpected error processing socket
09:04:51,358 ERROR [STDERR] Exception in thread "http-0.0.0.0-443-5"
09:04:56,155 ERROR [CoyoteAdapter] An exception or error occurred in the container during the request processing
09:04:58,546 ERROR [Http11Processor] Error processing request
09:05:02,139 ERROR [PoolTcpEndpoint] Unexpected error processing socket
09:05:04,530 ERROR [STDERR] Exception in thread "http-0.0.0.0-443-13"
09:05:09,514 ERROR [CoyoteAdapter] An exception or error occurred in the container during the request processing
09:05:11,920 ERROR [Http11Processor] Error processing request
09:05:15,514 ERROR [PoolTcpEndpoint] Unexpected error processing socket
09:05:17,889 ERROR [STDERR] Exception in thread "http-0.0.0.0-443-4"
09:06:41,107 ERROR [ContainerBase] Exception invoking periodic operation:
09:06:43,482 ERROR [STDERR] Exception in thread "ContainerBackgroundProcessor[StandardEngine[jboss.web]]"
09:08:02,575 INFO [STDOUT] Done.....
09:08:02,575 INFO [STDOUT] Done.....
09:08:02,575 INFO [STDOUT] PMS_CampaignMasterBean - getting domain_id 15
09:08:04,981 ERROR [CoyoteAdapter] An exception or error occurred in the container during the request processing
09:08:07,403 ERROR [Http11Processor] Error processing request
09:08:10,996 ERROR [PoolTcpEndpoint] Unexpected error processing socket
09:08:13,371 ERROR [STDERR] Exception in thread "http-0.0.0.0-443-1"
09:09:29,573 INFO [STDOUT] Done.....
09:09:29,573 INFO [STDOUT] Done.....
09:09:29,573 INFO [STDOUT] PMS_CampaignMasterBean - getting domain_id 15
09:09:31,995 ERROR [CoyoteAdapter] An exception or error occurred in the container during the request processing
09:09:34,386 ERROR [Http11Processor] Error processing request
09:09:38,026 ERROR [PoolTcpEndpoint] Unexpected error processing socket
09:09:40,417 ERROR [STDERR] Exception in thread "http-0.0.0.0-443-19"
09:09:40,417 INFO [STDOUT] Done.....
09:09:41,620 INFO [STDOUT] Done.....
09:09:41,620 INFO [STDOUT] PMS_CampaignMasterBean - getting domain_id 15
09:09:44,058 ERROR [CoyoteAdapter] An exception or error occurred in the container during the request processing
09:09:46,479 ERROR [Http11Processor] Error processing request
09:09:50,089 ERROR [PoolTcpEndpoint] Unexpected error processing socket
09:09:52,511 ERROR [STDERR] Exception in thread "http-0.0.0.0-443-9"
09:09:53,807 INFO [STDOUT] Done.....
09:09:53,807 INFO [STDOUT] Done.....
09:09:53,807 INFO [STDOUT] PMS_CampaignMasterBean - getting domain_id 15
09:09:56,229 ERROR [CoyoteAdapter] An exception or error occurred in the container during the request processing
09:09:58,636 ERROR [Http11Processor] Error processing request
09:10:02,229 ERROR [PoolTcpEndpoint] Unexpected error processing socket
09:10:04,620 ERROR [STDERR] Exception in thread "http-0.0.0.0-443-3"
-------------------------------------------------------
The STDOUT statements in log are System.out.prinltn() from my application's code.
I restarted the JBoss service and it started working fine.
But I don't know the reason behind this exception.
Can any one tell me if you had encountered such problem.
Thanks in advance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4085259#4085259
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4085259
18 years, 9 months
[EJB 3.0] - 4.2.1.GA vs 4.0.5.GA JNDI names
by sbivol
I have a @Stateless bean deployed in an ejb.jar within a ear, and it has to support ejb 2.1 clients, so it has a @RemoteHome annotation:
@Stateless(name = "MyService")
@Remote(MyServiceRemote.class)
@RemoteHome(MyServiceRemoteHome.class)
@Local(MyServiceLocal.class)
public class MyServiceBean implements MyService, MyServiceLocal {
?
}
On jboss 4.0.5.GA, after deploying the app, the jndi view would show the following under ?Global JNDI Namespace? :
+- myear (class: org.jnp.interfaces.NamingContext)
| +- MyService (class: org.jnp.interfaces.NamingContext)
| | +- remoteHome (proxy: $Proxy184 implements interface com...MyServiceRemoteHome)
| | +- local (proxy: $Proxy185 implements interface com...MyServiceLocal,interface org.jboss.ejb3.JBossProxy,interface javax.ejb.EJBLocalObject)
| | +- remote (proxy: $Proxy183 implements interface com...MyServiceRemote,interface org.jboss.ejb3.JBossProxy,interface javax.ejb.EJBObject)
On jboss 4.2.1.GA, the remoteHome entry does not show up under myear/MyService. A new 'MyService' entry appears at same level as 'myear' as follows:
+- MyService (class: org.jnp.interfaces.NamingContext)
| +- home (proxy: $Proxy181 implements interface com...MyServiceRemoteHome)
+- myear (class: org.jnp.interfaces.NamingContext)
| +- MyService (class: org.jnp.interfaces.NamingContext)
| | +- local (proxy: $Proxy185 implements interface com...MyServiceLocal,interface org.jboss.ejb3.JBossProxy,interface javax.ejb.EJBLocalObject)
| | +- remote (proxy: $Proxy183 implements interface com...MyServiceRemote,interface org.jboss.ejb3.JBossProxy,interface javax.ejb.EJBObject)
Is this known behavior? Can I specify the JNDI name for remoteHome in a deployment descriptor to make it consistent with the others?
Thank you
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4085252#4085252
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4085252
18 years, 9 months
[JBoss Seam] - Re: Seam nightly builds
by nkhilnani
Since friday i seem to be getting a 'Could not create Component: org.jboss.seam.core.resourceBundle' error when using the nightly snapshots. The current exception is based on build 245.
All i did was replace the Seam-2.0.0 beta jars with the ones from the nightly snapshot. Anyone else getting these errors?
The Goal was to test Richfaces 3.1.0. It doesnt seem to like Seam 2.0.0 beta jars.
Thanks,
Nik
| Sep 17, 2007 4:34:53 PM org.apache.catalina.core.StandardContext listenerStart
| SEVERE: Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener
| java.lang.RuntimeException: Could not create Component: org.jboss.seam.core.resourceBundle
| at org.jboss.seam.init.Initialization.addComponent(Initialization.java:955)
| at org.jboss.seam.init.Initialization.installComponents(Initialization.java:882)
| at org.jboss.seam.init.Initialization.init(Initialization.java:538)
| at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34)
| at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827)
| at org.apache.catalina.core.StandardContext.start(StandardContext.java:4334)
| at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
| at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
| at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
| at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:825)
| at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:714)
| at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
| at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1206)
| at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:293)
| at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
| at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1337)
| at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1601)
| at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610)
| at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1590)
| at java.lang.Thread.run(Thread.java:613)
| Caused by: java.lang.IllegalArgumentException: no such setter method: org.jboss.seam.core.ResourceBundle.bundleNames
| at org.jboss.seam.util.Reflections.getSetterMethod(Reflections.java:236)
| at org.jboss.seam.Component.initInitializers(Component.java:482)
| at org.jboss.seam.Component.<init>(Component.java:260)
| at org.jboss.seam.Component.<init>(Component.java:214)
| at org.jboss.seam.init.Initialization.addComponent(Initialization.java:940)
| ... 19 more
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4085250#4085250
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4085250
18 years, 9 months