ERROR in deploying EAR in JBoss 4.2.0 GA Server !!| JBoss.org Content Archive (Read Only)

15. Re: ERROR in deploying EAR in JBoss 4.2.0 GA Server !!

saswatamandal Jun 29, 2010 5:20 AM (in response to peterj)

Ok, but we dont have a paid subscription , The EAP version is only a 30 days Evaluation version.

So now we have decided to move to GA .

And in GA too , we are receiving the same error.

So, can you suggest some solution for this error !!!

Thanks & Regards

saswata mandal.

16. Re: ERROR in deploying EAR in JBoss 4.2.0 GA Server !!

wolfgangknauf Jun 29, 2010 12:00 PM (in response to saswatamandal)

Hi,

I took a look at your server.log, but didn't see any deploy error. There are only two exceptions with DEBUG level, which means they won't have an impact on the server state.

Best regards

Wolfgang

17. Re: ERROR in deploying EAR in JBoss 4.2.0 GA Server !!

saswatamandal Jun 30, 2010 3:50 AM (in response to wolfgangknauf)

OH NO NO.......

There are ERRORS , one can search the server.log with the timestamps ,

I have highlighted the ERRORS found in the log . :-

2010-06-28 17:34:57,997 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@110769b, cl=org.jboss.mx.loading.HeirarchicalLoaderRepository3$CacheClassLoader@18a8ae7{ url=null ,addedOrder=0}
2010-06-28 17:34:58,541 ERROR [STDERR] Jun 28, 2010 5:34:58 PM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized
INFO: WSSERVLET12: JAX-WS context listener initializing
2010-06-28 17:34:58,546 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@110769b, cl=org.jboss.mx.loading.HeirarchicalLoaderRepository3$CacheClassLoader@daa6a6{ url=null ,addedOrder=0}

.................................................................................

2010-06-28 17:35:05,013 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@110769b, cl=org.jboss.mx.loading.HeirarchicalLoaderRepository3$CacheClassLoader@1a9dc55{ url=null ,addedOrder=0}
2010-06-28 17:35:05,015 ERROR [STDERR] Jun 28, 2010 5:35:05 PM com.sun.xml.ws.transport.http.servlet.WSServletDelegate <init>
INFO: WSSERVLET14: JAX-WS servlet initializing
2010-06-28 17:35:05,028 DEBUG [org.jboss.web.tomcat.filters.ReplyHeaderFilter] Adding header name: X-Powered-By='Servlet 2.4; JBoss-4.2.0.GA_CP09 (build: SVNTag=JBPAPP_4_2_0_GA_CP09 date=201004202158)/JBossWeb-2.0'

.................................................................................

2010-06-28 17:35:05,211 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] No FacesServlet found in deployment descriptor - bypassing configuration
2010-06-28 17:35:05,212 ERROR [STDERR] Jun 28, 2010 5:35:05 PM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized
INFO: WSSERVLET12: JAX-WS context listener initializing
2010-06-28 17:35:05,679 ERROR [STDERR] Jun 28, 2010 5:35:05 PM com.sun.xml.ws.transport.http.servlet.WSServletDelegate <init>
INFO: WSSERVLET14: JAX-WS servlet initializing

.................................................................................

2010-06-28 17:35:05,905 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] No FacesServlet found in deployment descriptor - bypassing configuration
2010-06-28 17:35:05,905 ERROR [STDERR] Jun 28, 2010 5:35:05 PM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized
INFO: WSSERVLET12: JAX-WS context listener initializing
2010-06-28 17:35:06,568 ERROR [STDERR] Jun 28, 2010 5:35:06 PM com.sun.xml.ws.transport.http.servlet.WSServletDelegate <init>
INFO: WSSERVLET14: JAX-WS servlet initializing

.................................................................................

2010-06-28 17:35:06,805 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] No FacesServlet found in deployment descriptor - bypassing configuration
2010-06-28 17:35:06,806 ERROR [STDERR] Jun 28, 2010 5:35:06 PM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized
INFO: WSSERVLET12: JAX-WS context listener initializing
2010-06-28 17:35:10,577 ERROR [STDERR] Jun 28, 2010 5:35:10 PM com.sun.xml.ws.transport.http.servlet.WSServletDelegate <init>
INFO: WSSERVLET14: JAX-WS servlet initializing

.................................................................................

2010-06-28 17:35:10,740 DEBUG [javax.enterprise.resource.webcontainer.jsf.config] No FacesServlet found in deployment descriptor - bypassing configuration
2010-06-28 17:35:10,740 ERROR [STDERR] Jun 28, 2010 5:35:10 PM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized
INFO: WSSERVLET12: JAX-WS context listener initializing
2010-06-28 17:35:11,181 ERROR [STDERR] Jun 28, 2010 5:35:11 PM com.sun.xml.ws.transport.http.servlet.WSServletDelegate <init>
INFO: WSSERVLET14: JAX-WS servlet initializing

.................................................................................

2010-06-28 17:35:21,840 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@94691f, cl=org.jboss.mx.loading.HeirarchicalLoaderRepository3$CacheClassLoader@10dbc8d{ url=null ,addedOrder=0}
2010-06-28 17:35:21,842 ERROR [STDERR] Jun 28, 2010 5:35:21 PM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized
INFO: WSSERVLET12: JAX-WS context listener initializing
2010-06-28 17:35:21,852 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@94691f, cl=org.jboss.mx.loading.HeirarchicalLoaderRepository3$CacheClassLoader@d5e310{ url=null ,addedOrder=0}

.................................................................................

2010-06-28 17:35:26,106 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@94691f, cl=org.jboss.mx.loading.HeirarchicalLoaderRepository3$CacheClassLoader@8a750a{ url=null ,addedOrder=0}
2010-06-28 17:35:26,108 ERROR [STDERR] Jun 28, 2010 5:35:26 PM com.sun.xml.ws.transport.http.servlet.WSServletDelegate <init>
INFO: WSSERVLET14: JAX-WS servlet initializing
2010-06-28 17:35:26,111 DEBUG [org.jboss.web.tomcat.filters.ReplyHeaderFilter] Adding header name: X-Powered-By='Servlet 2.4; JBoss-4.2.0.GA_CP09 (build: SVNTag=JBPAPP_4_2_0_GA_CP09 date=201004202158)/JBossWeb-2.0'

Kindly suggest , why are these errors thrown.

We have copied the contents of the 'all' server configuration folder to our node folder and deployed the ear in the nodes deploy directory.

Thanks & Regards

saswata mandal.

18. Re: ERROR in deploying EAR in JBoss 4.2.0 GA Server !!

saswatamandal Jun 30, 2010 5:56 AM (in response to saswatamandal)

Hi Experts,

Any suggestions !!

Thanks & Regards

Saswata mandal.

19. Re: ERROR in deploying EAR in JBoss 4.2.0 GA Server !!

jaikiran Jun 30, 2010 6:08 AM (in response to saswatamandal)

As already noted in the replies to this thread, those ERROR messages are not useful to figure out what's wrong. I already told you what you could do to find out what the problem is:

jaikiran wrote:

Those ERROR level logs are the same as the ones on the console (no suprise there). I was asking if there were any error messages or any useful information being logged at lower log level (like DEBUG) in your server.log. From what you have posted so far, I don't see anything informational in the log files (not saying it's your fault). I guess, you have to try to isolate the problem by trimming the .war file to the basic minimum and then try adding the functionalities incrementally. That might tell you at what point, the application fails. Or you can even attach a debugger to JBoss source code and see where it fails and why (the stacktrace shows something in com.sun.* classes, so I am not sure if even the debugger would help).

20. Re: ERROR in deploying EAR in JBoss 4.2.0 GA Server !!

saswatamandal Jun 30, 2010 6:39 AM (in response to jaikiran)

Hi Jaikiran & all Experts of this forum ,

I have already attached the full server.log file in one of the previous posts in this discussion thread.

Kindly suggest , why these errors are thrown !!!

We have copied the contents of the "all" server configuration in our node folder and deployed the ear in its deploy directory.

Thanks & Regards

Saswata mandal.

21. Re: ERROR in deploying EAR in JBoss 4.2.0 GA Server !!

wolfgangknauf Jun 30, 2010 8:04 AM (in response to saswatamandal)

Hi,

sorry for not seing the error message. I was searching for keyword "exception" ;-).

Besides those error messages, what does not work for you? Any exceptions when accessing your app?

I found two posts, which have the same error message:

http://community.jboss.org/message/340351#340351

http://community.jboss.org/message/202029#202029

Both unfortunately with no solution....

Does your WAR file contain any Web service related JARs, e.g. the Sun Reference Implementation? If yes try to remove them, because JBoss contains it's own webservice implementation.

Hope this helps

Wolfgang

22. Re: ERROR in deploying EAR in JBoss 4.2.0 GA Server !!

saswatamandal Jun 30, 2010 8:34 AM (in response to wolfgangknauf)

Yes , the EAR contains Web - Service related WARs developed by EMC.

But , cant remove the JARs from that , as those are in the package. Removing the jars in the EAR will have negative impact on the web services.

Can we remove JBoss 's web-service implementation from the server completely ?

Thanks & Regards

saswata mandal.

23. Re: ERROR in deploying EAR in JBoss 4.2.0 GA Server !!

wolfgangknauf Jun 30, 2010 9:42 AM (in response to saswatamandal)

EMC is a closed source product, as far as I see? Then you might ask their support.

Best regards

Wolfgang

24. Re: ERROR in deploying EAR in JBoss 4.2.0 GA Server !!

peterj Jun 30, 2010 11:20 AM (in response to saswatamandal)

>>2010-06-28 17:34:58,541 ERROR [STDERR] Jun 28, 2010 5:34:58 PM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized
INFO: WSSERVLET12: JAX-WS context listener initializing

These are not errors. These are informational messages written to stderr. Given that the messages originated from com.sun.* it is my guess that they were written using java.util logging, which writes all log statements to stderr. This particular entry appears to be indicating that the listerner is finished initializing and is ready to process requests.

25. Re: ERROR in deploying EAR in JBoss 4.2.0 GA Server !!

saswatamandal Jul 1, 2010 4:39 AM (in response to peterj)

But ,

The word ERROR in ERROR [STDERR] is what I am afraid off.

26. Re: ERROR in deploying EAR in JBoss 4.2.0 GA Server !!

saswatamandal Jul 5, 2010 11:16 AM (in response to saswatamandal)

The Web Services and the Application are not working .

This is a severe error......need solution.