[JBoss jBPM] - Change the status workflow
by magnumff
hi
I want to change the status workflow from a client external the web service (jbpm)
code:
| Object o=commandService.execute(new GetProcessInstanceCommand(17));
| ProcessInstance process=(ProcessInstance)o;
| process.signal();
|
my error is :
class org.jbpm.graph.exe.ProcessInstance
org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: org.jbpm.graph.exe.ProcessInstance.instances, no session or session was closed
at org.hibernate.collection.AbstractPersistentCollection.throwLazyInitializationException(AbstractPersistentCollection.java:358)
at org.hibernate.collection.AbstractPersistentCollection.throwLazyInitializationExceptionIfNotConnected(AbstractPersistentCollection.java:350)
at org.hibernate.collection.AbstractPersistentCollection.readElementByIndex(AbstractPersistentCollection.java:151)
at org.hibernate.collection.PersistentMap.get(PersistentMap.java:127)
at org.jbpm.graph.exe.ProcessInstance.getInstance(ProcessInstance.java:212)
at org.jbpm.graph.exe.Token.startCompositeLog(Token.java:377)
at org.jbpm.graph.exe.Token.signal(Token.java:188)
at org.jbpm.graph.exe.Token.signal(Token.java:140)
at org.jbpm.graph.exe.ProcessInstance.signal(ProcessInstance.java:271)
at ProvaClient.main(ProvaClient.java:46)
Exception : org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: org.jbpm.graph.exe.ProcessInstance.instances, no session or session was closed
Cause : null
StackTrace : [Ljava.lang.StackTraceElement;@15db314
Message : failed to lazily initialize a collection of role: org.jbpm.graph.exe.ProcessInstance.instances, no session or session was closed
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177332#4177332
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177332
17 years, 10 months
[JBoss Portal] - Re: Take 3 - Relationship between jboss-app.xml and *-object
by youssef.mohammed
+1
"nicolasduminil" wrote : Chris,
|
| Firstable, while the hyperlinks you posted in your message point to several documents and articles, no one of them doesn't respond to my questions. I patiently red these several dozens of unrelated document and I can tell you that none doesn't explain neither what the "*" in the *-objects.xml stands for, nore why once a potlet deployed, one is not able anymore to change the name in the file jboss-app.xml and to redeploy the portlet. Of course, I have red these documents before having posted my question.
|
| Second, as you claim having red my message, it doesn't seem so. If you did, you would have understood that the problem doesn't have anything to do with Richfaces. But, in order to give to an eventual interlocutor as much details as possible, I explained that the application I was talking about has beed originally generated by the JBoss Portlet Bridge maven archetype.
|
| Third, complaining about the poor quality of the products, even if there are "free", is absolutelly natural, given the huge publicity campaign you're doing to show how great JBoss stuff is. But from my personal experience, as well as the one of my colleagues at Simplex Software, a company having several very competent architects and developpers Java/J2EE, JBoss stuff could be successfully used in the simples cases, for small prototypes. But as soon as one needs to use them in "real life", lots of bugs apear, preventing the user to really take advantage. And the thing you're calling at JBoss "documentation" doesn't help.
|
| We, as architects and developpers, we are aware by the fact that we don't have to build strategic solutions based on this kind of products, unless we are subscribing to your support services, in which case the total cost of the operations would be higher than if we were be using commercial, well documented products. But the management is taking "ad literam" JBoss advertizing and thinks that a software company may really dramatically decrease the costs by using a free application server and portal server. Which is not the case because a big effort is required in order to get things working.
|
| For example, in 2006 we started a portal project and, as BEA customers, we naturally wanted to continue using WebLogic Portal which has given to us entirelly satisfaction. But management forced us to use JBoss Portal because it's free. We spent several weeks trying to get things working and during this time we weren't focusing on our project. After several weeks, we went back to WebLogic Portal and Workshop. Now we started a new project wirh JBoss Portal and, as things are going, there is a very strong probability that in a couple of weeks to go back to BEA/Oracle stuff.
|
| Instead of writing you're long message you could simply give the answers I was waiting for. But in this case we wouldn't of course buy consulting from JBoss. As a matter of fact, if the documentation is well done and if the forum gives people the answers they need, who would buy anymore consulting from you ? This is to say that JBoss products are free as well as they don't work and there is not any know-how. But if one wants them to really work, well, in this case they are not any more free, they become even more expansive than the comercial ones.
|
| Now, to come back to my questions, please don't bother too much. It apears that:
|
| i) the "*" in front of -object.xml stands for nothing.
| ii) the problem that I signaled concerning the changes in jboss-app.xml preventing the deployment to function properly is related to the chaotic management by JBoss Portal of associations between portlet and portlet instances.
|
| As far as I'm concerned, I won't ever go live with something like that.
|
| Kind regards,
|
| Nicolas
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177328#4177328
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177328
17 years, 10 months
[JBoss Portal] - Re: Take 3 - Relationship between jboss-app.xml and *-object
by nicolasduminil
Chris,
Firstable, while the hyperlinks you posted in your message point to several documents and articles, no one of them doesn't respond to my questions. I patiently red these several dozens of unrelated document and I can tell you that none doesn't explain neither what the "*" in the *-objects.xml stands for, nore why once a potlet deployed, one is not able anymore to change the name in the file jboss-app.xml and to redeploy the portlet. Of course, I have red these documents before having posted my question.
Second, as you claim having red my message, it doesn't seem so. If you did, you would have understood that the problem doesn't have anything to do with Richfaces. But, in order to give to an eventual interlocutor as much details as possible, I explained that the application I was talking about has beed originally generated by the JBoss Portlet Bridge maven archetype.
Third, complaining about the poor quality of the products, even if there are "free", is absolutelly natural, given the huge publicity campaign you're doing to show how great JBoss stuff is. But from my personal experience, as well as the one of my colleagues at Simplex Software, a company having several very competent architects and developpers Java/J2EE, JBoss stuff could be successfully used in the simples cases, for small prototypes. But as soon as one needs to use them in "real life", lots of bugs apear, preventing the user to really take advantage. And the thing you're calling at JBoss "documentation" doesn't help.
We, as architects and developpers, we are aware by the fact that we don't have to build strategic solutions based on this kind of products, unless we are subscribing to your support services, in which case the total cost of the operations would be higher than if we were be using commercial, well documented products. But the management is taking "ad literam" JBoss advertizing and thinks that a software company may really dramatically decrease the costs by using a free application server and portal server. Which is not the case because a big effort is required in order to get things working.
For example, in 2006 we started a portal project and, as BEA customers, we naturally wanted to continue using WebLogic Portal which has given to us entirelly satisfaction. But management forced us to use JBoss Portal because it's free. We spent several weeks trying to get things working and during this time we weren't focusing on our project. After several weeks, we went back to WebLogic Portal and Workshop. Now we started a new project wirh JBoss Portal and, as things are going, there is a very strong probability that in a couple of weeks to go back to BEA/Oracle stuff.
Instead of writing you're long message you could simply give the answers I was waiting for. But in this case we wouldn't of course buy consulting from JBoss. As a matter of fact, if the documentation is well done and if the forum gives people the answers they need, who would buy anymore consulting from you ? This is to say that JBoss products are free as well as they don't work and there is not any know-how. But if one wants them to really work, well, in this case they are not any more free, they become even more expansive than the comercial ones.
Now, to come back to my questions, please don't bother too much. It apears that:
i) the "*" in front of -object.xml stands for nothing.
ii) the problem that I signaled concerning the changes in jboss-app.xml preventing the deployment to function properly is related to the chaotic management by JBoss Portal of associations between portlet and portlet instances.
As far as I'm concerned, I won't ever go live with something like that.
Kind regards,
Nicolas
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177327#4177327
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177327
17 years, 10 months
[Security & JAAS/JBoss] - Kerberos / JBoss Negotiate issues and questions
by ejb3workshop
I have deployed JBoss Negotiate onto JBoss 4.2.3. Initially I tried to create the server users account using a generic name such as JBoss instead of the hostname of the machine. I couldn't get this working. After creating a username whose name matched the hostname of the JBoss server I was able to complete the Basic Negotiation and the Security Domain Test from another client. I am still not able to perform those from the server itself. IE works from the other clients, but neither IE, nor Firefox work on my client.
I read some suggestions to clear the cache, but I haven't found instructions on doing this.
When I try the Secured test I get the exception below. I wonder if there is a problem on my system which also runs the JBoss server which could be causing this ?
| 09:54:39,905 TRACE [UsersRolesLoginModule] Properties file=file:/C:/jboss-4.2.3.GA/server/default/conf/props/spnego-roles.properties, defaults=null
| 09:54:39,905 DEBUG [UsersRolesLoginModule] Loaded properties, users=[operator, ahartner(a)TH.local, vreddy@TH, user, ahartner@TH, jamesm@TH, other, vreddy(a)TH.local, jamesm(a)TH.local, sysop]
| 09:54:39,905 TRACE [UsersRolesLoginModule] abort
| 09:54:39,920 TRACE [SPNEGO] Login failure
| javax.security.auth.login.LoginException: Continuation Required.
| at org.jboss.security.negotiation.spnego.SPNEGOLoginModule.login(SPNEGOLoginModule.java:156)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
| at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
| at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
| at java.security.AccessController.doPrivileged(Native Method)
| at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
| at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
| at org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecurityManager.java:603)
| at org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecurityManager.java:537)
| at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:344)
| at org.jboss.web.tomcat.security.JBossSecurityMgrRealm.authenticate(JBossSecurityMgrRealm.java:491)
| at org.jboss.security.negotiation.spnego.SPNEGOAuthenticator.authenticate(SPNEGOAuthenticator.java:103)
| at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:490)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
| at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
| at java.lang.Thread.run(Thread.java:619)
| 09:54:40,030 TRACE [SPNEGO] End isValid, false
| 09:54:40,030 DEBUG [SPNEGOAuthenticator] authenticated principal = null
| 09:54:40,030 TRACE [SPNEGOContext] clear 31752641
| 09:54:40,030 TRACE [SecurityAssociation] clear, server=true
| 09:54:40,045 TRACE [SPNEGOAuthenticator] Authenticating user
| 09:54:40,045 INFO [SPNEGOAuthenticator] Header - Negotiate oYIF2zCCBdeiggXTBIIFz2CCBcsGCSqGSIb3EgECAgEAboIFujCCBbagAwIBBaEDAgEOogcDBQAgAAAAo4IE5WGCBOEwggTdoAMCAQWhChsIVEguTE9DQUyiITAfoAMCAQKhGDAWGwRI
|
...
| 0xcf 0x0e 0x1a 0x1b 0xbd 0xaa 0xa1 0x63
| 09:54:40,546 DEBUG [SPNEGOLoginModule] Creating new GSSContext.
| 09:54:40,686 TRACE [SPNEGOLoginModule] Result - GSSException: Failure unspecified at GSS-API level (Mechanism level: Invalid argument (400) - Cannot find key of appropriate type to decrypt AP REP - RC4 with HMAC)
| 09:54:40,686 ERROR [SPNEGOLoginModule] Unable to authenticate
| GSSException: Failure unspecified at GSS-API level (Mechanism level: Invalid argument (400) - Cannot find key of appropriate type to decrypt AP REP - RC4 with HMAC)
| at sun.security.jgss.krb5.Krb5Context.acceptSecContext(Krb5Context.java:741)
| at sun.security.jgss.GSSContextImpl.acceptSecContext(GSSContextImpl.java:323)
| at sun.security.jgss.GSSContextImpl.acceptSecContext(GSSContextImpl.java:267)
| at org.jboss.security.negotiation.spnego.SPNEGOLoginModule$AcceptSecContext.run(SPNEGOLoginModule.java:295)
| at java.security.AccessController.doPrivileged(Native Method)
| at javax.security.auth.Subject.doAs(Subject.java:337)
| at org.jboss.security.negotiation.spnego.SPNEGOLoginModule.login(SPNEGOLoginModule.java:113)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
| at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
| at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
| at java.security.AccessController.doPrivileged(Native Method)
| at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
| at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
| at org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecurityManager.java:603)
| at org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecurityManager.java:537)
| at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:344)
| at org.jboss.web.tomcat.security.JBossSecurityMgrRealm.authenticate(JBossSecurityMgrRealm.java:491)
| at org.jboss.security.negotiation.spnego.SPNEGOAuthenticator.authenticate(SPNEGOAuthenticator.java:103)
| at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:490)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
| at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
| at java.lang.Thread.run(Thread.java:619)
| Caused by: KrbException: Invalid argument (400) - Cannot find key of appropriate type to decrypt AP REP - RC4 with HMAC
| at sun.security.krb5.KrbApReq.authenticate(KrbApReq.java:262)
| at sun.security.krb5.KrbApReq.<init>(KrbApReq.java:134)
| at sun.security.jgss.krb5.InitSecContextToken.<init>(InitSecContextToken.java:79)
| at sun.security.jgss.krb5.Krb5Context.acceptSecContext(Krb5Context.java:724)
| ... 32 more
| 09:54:40,827 INFO [STDOUT] [Krb5LoginModule]: Entering logout
| 09:54:40,843 INFO [STDOUT] [Krb5LoginModule]: logged out Subject
| 09:54:40,843 TRACE [SPNEGOLoginModule] abort
| 09:54:40,843 TRACE [UsersRolesLoginModule] initialize, instance=@12914915
| 09:54:40,843 TRACE [UsersRolesLoginModule] Security domain: SPNEGO
| 09:54:40,858 TRACE [UsersRolesLoginModule] findResource: null
| 09:54:40,858 TRACE [UsersRolesLoginModule] Properties file=file:/C:/jboss-4.2.3.GA/server/default/conf/props/spnego-users.properties, defaults=null
| 09:54:40,858 DEBUG [UsersRolesLoginModule] Loaded properties, users=[]
| 09:54:40,858 TRACE [UsersRolesLoginModule] findResource: null
| 09:54:40,858 TRACE [UsersRolesLoginModule] Properties file=file:/C:/jboss-4.2.3.GA/server/default/conf/props/spnego-roles.properties, defaults=null
| 09:54:40,874 DEBUG [UsersRolesLoginModule] Loaded properties, users=[operator, ahartner(a)TH.local, vreddy@TH, user, ahartner@TH, jamesm@TH, other, vreddy(a)TH.local, jamesm(a)TH.local, sysop]
| 09:54:40,874 TRACE [UsersRolesLoginModule] abort
| 09:54:40,874 TRACE [SPNEGO] Login failure
| javax.security.auth.login.LoginException: Unable to authenticate - Failure unspecified at GSS-API level (Mechanism level: Invalid argument (400) - Cannot find key of appropriate type to decrypt AP REP - RC4 with HMAC)
| at org.jboss.security.negotiation.spnego.SPNEGOLoginModule.login(SPNEGOLoginModule.java:136)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
| at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
| at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
| at java.security.AccessController.doPrivileged(Native Method)
| at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
| at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
| at org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecurityManager.java:603)
| at org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecurityManager.java:537)
| at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:344)
| at org.jboss.web.tomcat.security.JBossSecurityMgrRealm.authenticate(JBossSecurityMgrRealm.java:491)
| at org.jboss.security.negotiation.spnego.SPNEGOAuthenticator.authenticate(SPNEGOAuthenticator.java:103)
| at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:490)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
| at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
| at java.lang.Thread.run(Thread.java:619)
| 09:54:40,999 TRACE [SPNEGO] End isValid, false
| 09:54:40,999 DEBUG [SPNEGOAuthenticator] authenticated principal = null
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177326#4177326
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177326
17 years, 10 months
[Installation, Configuration & DEPLOYMENT] - Error while deploying CentraSite 7.1 on JBoss
by abi_balaa4
Hi all,
I have come up against an error after deploying CentraSite 7.1 on JBoss application server.
CentraSite is successfully deployed on JBoss 4.0.5 GA, but when i log out from the application, i am getting the following error:
2008-09-18 07:24:59,226 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/].[org.apache.jsp.html.portal.render_005fportlet_jsp]] Servlet.service() for servlet org.apache.jsp.html.portal.render_005fportlet_jsp threw exception
java.lang.IllegalStateException: getAttribute: Session already invalidated
at org.apache.catalina.session.StandardSession.getAttribute(StandardSession.java:1011)
at org.apache.catalina.session.StandardSessionFacade.getAttribute(StandardSessionFacade.java:109)
at org.apache.jsp.html.portal.render_005fportlet_jsp._jspService(Unknown Source)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.liferay.filters.strip.StripFilter.doFilter(StripFilter.java:268)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.liferay.filters.compression.CompressionFilter.doFilter(CompressionFilter.java:124)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.liferay.portal.servlet.filters.virtualhost.VirtualHostFilter.doFilter(VirtualHostFilter.java:135)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574)
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499)
at com.liferay.portal.util.PortalUtil.renderPortlet(PortalUtil.java:1094)
at com.liferay.portlet.layoutconfiguration.util.RuntimePortletUtil.processPortlet(RuntimePortletUtil.java:148)
at com.liferay.portlet.layoutconfiguration.util.RuntimePortletUtil.processPortlet(RuntimePortletUtil.java:89)
at com.liferay.portlet.layoutconfiguration.util.RuntimePortletUtil.processTemplate(RuntimePortletUtil.java:239)
at com.liferay.portlet.layoutconfiguration.util.RuntimePortletUtil.processTemplate(RuntimePortletUtil.java:172)
at org.apache.jsp.html.portal.layout.view.portlet_jsp._jspService(Unknown Source)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.liferay.filters.strip.StripFilter.doFilter(StripFilter.java:268)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.liferay.filters.compression.CompressionFilter.doFilter(CompressionFilter.java:124)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.liferay.portal.servlet.filters.virtualhost.VirtualHostFilter.doFilter(VirtualHostFilter.java:135)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574)
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499)
at com.liferay.taglib.util.IncludeTag.doEndTag(IncludeTag.java:62)
at org.apache.jsp.html.portal.layout_jsp._jspService(Unknown Source)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.liferay.filters.strip.StripFilter.doFilter(StripFilter.java:268)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.liferay.filters.compression.CompressionFilter.doFilter(CompressionFilter.java:124)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.liferay.portal.servlet.filters.virtualhost.VirtualHostFilter.doFilter(VirtualHostFilter.java:135)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574)
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499)
at com.liferay.taglib.util.IncludeTag.doEndTag(IncludeTag.java:62)
at org.apache.jsp.html.themes.classic.templates.portal_005fnormal_jsp._jspService(Unknown Source)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.liferay.filters.strip.StripFilter.doFilter(StripFilter.java:268)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.liferay.filters.compression.CompressionFilter.doFilter(CompressionFilter.java:124)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.liferay.portal.servlet.filters.virtualhost.VirtualHostFilter.doFilter(VirtualHostFilter.java:135)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574)
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499)
at com.liferay.taglib.util.ThemeUtil.includeJSP(ThemeUtil.java:109)
at com.liferay.taglib.util.ThemeUtil.include(ThemeUtil.java:70)
at com.liferay.taglib.util.IncludeTag.doEndTag(IncludeTag.java:57)
at org.apache.jsp.html.common.themes.portal_jsp._jspx_meth_liferay$1theme_include_1(Unknown Source)
at org.apache.jsp.html.common.themes.portal_jsp._jspx_meth_c_otherwise_0(Unknown Source)
at org.apache.jsp.html.common.themes.portal_jsp._jspService(Unknown Source)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.liferay.filters.strip.StripFilter.doFilter(StripFilter.java:268)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.liferay.filters.compression.CompressionFilter.doFilter(CompressionFilter.java:124)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.liferay.portal.servlet.filters.virtualhost.VirtualHostFilter.doFilter(VirtualHostFilter.java:135)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:463)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
at com.liferay.portal.struts.StrutsUtil.forward(StrutsUtil.java:92)
at com.liferay.portal.struts.PortalRequestProcessor.doForward(PortalRequestProcessor.java:194)
at org.apache.struts.tiles.TilesRequestProcessor.processTilesDefinition(TilesRequestProcessor.java:239)
at org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(TilesRequestProcessor.java:302)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:241)
at com.liferay.portal.struts.PortalRequestProcessor.process(PortalRequestProcessor.java:171)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
at com.liferay.portal.servlet.MainServlet.callParentService(MainServlet.java:505)
at com.liferay.portal.servlet.MainServlet.service(MainServlet.java:965)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.liferay.filters.strip.StripFilter.doFilter(StripFilter.java:94)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.liferay.filters.secure.SecureFilter.doFilter(SecureFilter.java:143)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.liferay.filters.compression.CompressionFilter.doFilter(CompressionFilter.java:115)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.liferay.portal.servlet.filters.layoutcache.LayoutCacheFilter.doFilter(LayoutCacheFilter.java:204)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.liferay.portal.servlet.filters.autologin.AutoLoginFilter.doFilter(AutoLoginFilter.java:117)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.liferay.portal.servlet.filters.virtualhost.VirtualHostFilter.doFilter(VirtualHostFilter.java:135)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:595)
2008-09-18 07:24:59,241 ERROR [com.liferay.taglib.util.IncludeTag] java.lang.IllegalStateException: getAttribute: Session already invalidated
at org.apache.catalina.session.StandardSession.getAttribute(StandardSession.java:1011)
at org.apache.catalina.session.StandardSessionFacade.getAttribute(StandardSessionFacade.java:109)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.liferay.filters.strip.StripFilter.doFilter(StripFilter.java:268)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.liferay.filters.compression.CompressionFilter.doFilter(CompressionFilter.java:124)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.liferay.portal.servlet.filters.virtualhost.VirtualHostFilter.doFilter(VirtualHostFilter.java:135)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574)
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499)
at com.liferay.portal.util.PortalUtil.renderPortlet(PortalUtil.java:1094)
at com.liferay.portlet.layoutconfiguration.util.RuntimePortletUtil.processPortlet(RuntimePortletUtil.java:148)
Please help.
Thanks,
Abi
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177323#4177323
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177323
17 years, 10 months
[JBoss Messaging] - Re: jms and fault tolerance
by francesco_81
I've used the ClusterConnectionFactory but the result is the same.
What are the attributes that I've to set in the mbean ClusteredConnectionFactories in the file connection-factories-service.xml that I post below?
I've read somewhere that there is the need to make persistence-messages in order to get fault tolerance. How can I send/receive persistent messages? Are there some further configurations step to do (e.g. in the mysql-persitence-service.xml ). Are only this type of messages take in considetarion by buddy node(s).
|
| <?xml version="1.0" encoding="UTF-8"?>
|
| <!--
| Messaging Connection Factories deployment descriptor.
|
| $Id: connection-factories-service.xml 3332 2007-11-15 09:32:43Z timfox $
| -->
|
| <server>
|
| <!-- The default connection factory does not support automatic failover or load balancing-
| this is so we can maintain compatiblity with applications written for JBoss MQ which use this
| connection factory.
| -->
| <mbean code="org.jboss.jms.server.connectionfactory.ConnectionFactory"
| name="jboss.messaging.connectionfactory:service=ConnectionFactory"
| xmbean-dd="xmdesc/ConnectionFactory-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends optional-attribute-name="Connector">jboss.messaging:service=Connector,transport=bisocket</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
|
| <attribute name="JNDIBindings">
| <bindings>
| <binding>/ConnectionFactory</binding>
| <binding>/XAConnectionFactory</binding>
| <binding>java:/ConnectionFactory</binding>
| <binding>java:/XAConnectionFactory</binding>
| </bindings>
| </attribute>
| </mbean>
|
| <!-- A clustered connection factory that supports automatic failover and load balancing of created
| connections.
| This factory is not suitable to be used by MDBs.
| -->
| <mbean code="org.jboss.jms.server.connectionfactory.ConnectionFactory"
| name="jboss.messaging.connectionfactory:service=ClusteredConnectionFactory"
| xmbean-dd="xmdesc/ConnectionFactory-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends optional-attribute-name="Connector">jboss.messaging:service=Connector,transport=bisocket</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
|
| <attribute name="JNDIBindings">
| <bindings>
| <binding>/ClusteredConnectionFactory</binding>
| <binding>/ClusteredXAConnectionFactory</binding>
| <binding>java:/ClusteredConnectionFactory</binding>
| <binding>java:/ClusteredXAConnectionFactory</binding>
| </bindings>
| </attribute>
|
| <attribute name="SupportsFailover">true</attribute>
| <attribute name="SupportsLoadBalancing">true</attribute>
| </mbean>
|
| <!-- A connection factory with no JNDI bindings that is used in clustering to create the connections that
| pull messages from one node to another
| -->
| <mbean code="org.jboss.jms.server.connectionfactory.ConnectionFactory"
| name="jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory"
| xmbean-dd="xmdesc/ConnectionFactory-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends optional-attribute-name="Connector">jboss.messaging:service=Connector,transport=bisocket</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| <attribute name="SupportsFailover">false</attribute>
| <attribute name="SupportsLoadBalancing">false</attribute>
| </mbean>
|
| <!-- An example connection factory with all attributes shown
|
| <mbean code="org.jboss.jms.server.connectionfactory.ConnectionFactory"
| name="jboss.messaging.connectionfactory:service=MyExampleConnectionFactory"
| xmbean-dd="xmdesc/ConnectionFactory-xmbean.xml">
|
| <constructor>
|
| <!- - You can specify the default Client ID to use for connections created using this factory - ->
|
| <arg type="java.lang.String" value="MyClientID"/>
|
| </constructor>
|
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
|
| <!- - The transport to use - can be bisocket, sslbisocket or http - ->
|
| <depends optional-attribute-name="Connector">jboss.messaging:service=Connector,transport=http</depends>
|
| <depends>jboss.messaging:service=PostOffice</depends>
|
| <!- - PrefetchSize determines the approximate maximum number of messages the client consumer will buffer locally - ->
|
| <attribute name="PrefetchSize">150</attribute>
|
| <!- - Paging params to be used for temporary queues - ->
|
| <attribute name="DefaultTempQueueFullSize">200000</attribute>
|
| <attribute name="DefaultTempQueuePageSizeSize">2000</attribute>
|
| <attribute name="DefaultTempQueueDownCacheSize">2000</attribute>
|
| <!- - The batch size to use when using the DUPS_OK_ACKNOWLEDGE acknowledgement mode - ->
|
| <attribute name="DupsOKBatchSize">5000</attribute>
|
| <!- - Does this connection factory support automatic failover? - ->
|
| <attribute name="SupportsFailover">false</attribute>
|
| <!- - Does this connection factory support automatic client side load balancing? - ->
|
| <attribute name="SupportsLoadBalancing">false</attribute>
|
| <!- - The class name of the factory used to create the load balancing policy to use on the client side - ->
|
| <attribute name="LoadBalancingFactory">org.jboss.jms.client.plugin.RoundRobinLoadBalancingFactory</attribute>
|
| <!- - Whether we should be strict TCK compliant, i.e. how we deal with foreign messages, defaults to false- ->
|
| <attribute name="StrictTck">true</attribute>
|
| <!- - Disable JBoss Remoting Connector sanity checks - There is rarely a good reason to set this to true - ->
|
| <attribute name="DisableRemotingChecks">false</attribute>
|
| <!- - The connection factory will be bound in the following places in JNDI - ->
|
| <attribute name="JNDIBindings">
|
| <bindings>
|
| <binding>/acme/MyExampleConnectionFactory</binding>
|
| <binding>/acme/MyExampleConnectionFactoryDupe</binding>
|
| <binding>java:/xyz/CF1</binding>
|
| <binding>java:/connectionfactories/acme/connection_factory</binding>
|
| </bindings>
|
| </attribute>
|
| </mbean>
|
| -->
|
| </server>
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177317#4177317
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177317
17 years, 10 months
[JBoss Tools (users)] - Seam Auto-generated code
by ipazmino
Hi,
I was following a small seam example, and created a couple of entities, a session bean for the logic and a view xhtml file. Then, I generated the EB with the tools and they were far better.
The problem is that afterward I realized that for the Customer, it had created, besides the EB:
two SB, one extending from EntityHome (CustomerHome) and other extending EntityQuery (CustomerList).
three .xhtml pages: Customer.xhtml, CustomerEdit.xhtml and CustomerList.xhtml
three .xml files: Customer.page.xtml, CustomerEdit.page.xtml and CustomerList.page.xtml
So, I don't get a few things.
If I had a class or any file that matched the generated files' name, would it have been overwritten and lost what I had done?
Can I specify what I want to be generated?
What do the abstract classes, EntityHome and EntityQuery, do or are for?
What are those xmls, that seem to be one per .xhtml, for?
Sorry if these are obvious questions, but I was just beginning and now lost.
Thanks in advance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177275#4177275
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177275
17 years, 10 months
[News & Announcements] - JBossAS 5.0.0.CR2 released
by rrajesh
JBoss Application Server 5.0.0.CR2 has been released and is available for download at:
http://www.jboss.org/jbossas/downloads/
JBoss 5.0.0.CR2 Release Notes
This is the last Candidate Release release of the JBoss 5.0.x series for the Java EE⢠5 codebase and the first JBossAS release that fully complies with the Java EE 5 conformance testing certification requirements! This is an important milestone in the development of JBossAS as we will have more time now to spend on developer productivity features and server manageability improvements.
A common theme for JBossAS 5 is the breaking out of internal subsystems into stand-alone projects and the introduction of SPIs throughout the server codebase. Those changes should not affect directly the end user but they are an important part of the JBoss strategy for making available the various EE services as independent projects, so that they can be wired-together and be consumed a-la-carte inside different runtime environments and not just inside the JBoss Application Server.
If you are building JBossAS from source you'll notice we are migrating to a maven2 build. At this point the build is a hybrid one because it declares all JBoss dependencies as maven2 artifacts, however after the dependencies are resolved/imported the legacy ant based build is used to compile and build the distribution. This will change to a full maven build at some point in time. The jboss maven repo can be found here. Starting from AS5 CR2, please note how the -sources.jar are also downloaded.
Another target for this release was to improve support for Java 6. JBossAS 5 CR2 can be build with both JDK5 and JDK6. The JDK5 compiled binaries have undergone more rigorous testing, they constitute our certified version and can run under both Java 5 & 6 VMs (with a few configuration changes for JDK6, see the configuration section below). The JDK6 compiled binaries include support for the JDBC 4 APIs, but this should be considered experimental at this point.
For information on the APIs that make up Java EE 5, see Java EE APIs & Docs. A tutorial on Java EE 5 can be found here.
A sample Java EE 5 application that can be run on top of JBoss 5 and demonstrates many interesting technologies is the Seam Booking Application available here. Check out the JBoss Seam Wiki that links to many interesting topics about Seam.
Overview
* Highlights
* Compatibility Issues
* Configuration Issues
* Other Issues
* JBoss/Thirdparty Library Updates
* Detailed Release Notes
* Additional Docs and Help
* Licenses
* About JBoss
Highlights
JBoss 5 is the next generation of the JBoss Application Server build on top of the new JBoss Microcontainer. The JBoss Microcontainer is a lightweight container for managing POJOs, their deployment, configuration and lifecycle. It is a standalone project that replaces the famous JBoss JMX Microkernel of the 3.x and 4.x JBoss series. The Microcontainer integrates nicely with the JBoss framework for Aspect Oriented Programming, JBoss AOP. Support for JMX in JBoss 5 remains strong and MBean services written against the old Microkernel are expected to work.
JBoss5 is designed around the advanced concept of a Virtual Deployment Framework (VDF), that takes the aspect oriented design of many of the earlier JBoss containers and applies it to the deployment layer. Aspectized Deployers operate in a chain over a Virtual File System (VFS), analyze deployments and produce metadata to be used by the JBoss Microcontainer, which in turn instantiates and wires together the various pieces of a deployment, controlling their lifecycle and dependencies.
Many key features of JBoss 5 are provided by integrating other standalone JBoss projects:
* JBoss EJB3 included with JBoss 5 provides the implementation of the latest revision of the Enterprise Java Beans (EJB) specification. EJB 3.0 is a deep overhaul and simplification of the EJB specification. EJB 3.0's goals are to simplify development, facilitate a test driven approach, and focus more on writing plain old java objects (POJOs) rather than coding against complex EJB APIs.
* JBoss Messaging is a high performance JMS provider in the JBoss Enterprise Middleware Stack (JEMS), included with JBoss 5 as the default messaging provider. It is also the backbone of the JBoss ESB infrastructure. JBoss Messaging is a complete rewrite of JBossMQ, which is the default JMS provider for the JBoss AS 4.x series.
* JBossCache that comes in two flavors. A traditional tree-structured node-based cache and a PojoCache, an in-memory, transactional, and replicated cache system that allows users to operate on simple POJOs transparently without active user management of either replication or persistency aspects.
* JBossWS is the web services stack for JBoss 5 providing Java EE compatible web services, JAX-WS-2.0.
* JBoss Transactions is the default transaction manager for JBoss 5. JBoss Transactions is founded on industry proven technology and 18 year history as a leader in distributed transactions, and is one of the most interoperable implementations available.
* JBoss Web is the Web container in JBoss 5, an implementation based on Apache Tomcat that includes the Apache Portable Runtime (APR) and Tomcat native technologies to achieve scalability and performance characteristics that match and exceed the Apache Http server.
Minor feature additions for this release include:
* JBAS-5862, a new look for the jmx-console
* JBAS-5793, array interception for POJOs stored in web sessions with FIELD granularity.
* JBAS-5192, a POJO based replacement for the JBoss 4 ServiceBindingManager (WIP).
* JBAS-5822, support of the new ServiceBindingManager in old -service.xml deployments.
JBoss 5 includes features and bug fixes, many of them carried over upstream from the 4.x codebase. See the Detailed Release Notes section for the full details.
Compatibility Issues
JBossAS 5.0.0.CR2 can be compiled with both Java5 & Java6. The Java5 compiled binary is our primary/recommended binary distribution. It has undergone rigorous testing and can run under both a Java 5 and a Java 6 runtime. When running under Java 6 you need to manually copy the following libraries from the JBOSS_HOME/client directory to the JBOSS_HOME/lib/endorsed directory, so that the JAX-WS 2.0 apis supported by JBossWS are used:
* jbossws-native-saaj.jar
* jbossws-native-jaxrpc.jar
* jbossws-native-jaxws.jar
* jbossws-native-jaxws-ext.jar
The other option is to download the jdk6 distribution (jboss-5.0.0.CR2-jdk6.zip) in which case no configuration changes are required. If you still have problems using JBoss with a Sun Java 6 runtime, you may want to set -Dsun.lang.ClassLoader.allowArraySyntax=true, as described in JBAS-4491. Other potential problems under a Java 6 runtime include:
* ORB getting prematurely destroyed when using Sun JDK 6 (see Sun Bug ID: 6520484)
* Unimplemented methods in Hibernate for JDK6 interfaces.
* When JBossAS 5 is compiled with Java 6, support for the extended JDBC 4 API is included in the binary, however this can only be used under a Java 6 runtime. In this case no manual configuration steps are necessary. It should be noted however that the Java 6 compiled distribution of JBoss AS 5 is still in experimental stage.
Other compatibility issues:
* All the *-beans.xml configuration files have been renamed to *-jboss-beans.xml to avoid conflicts with spring configuration files.
* For mod_cluster integration you will have to use the workaround described in JBAS-5966 until the tomcat service mbean descriptor is converted to an MC bean descriptor.
* JBoss VFS provides a set of different switches to control it's internal behavior. JBoss AS sets jboss.vfs.forceCopy=true by default. To see all the provided VFS flags check out the code of the VFSUtils.java class.
* Hibernate-core is now using slf4j-api as a logging facade. To properly integrate that in JBossAS we have created an slf4j-to-jboss-logging adapter (slf4j-jboss-logging.jar) that creates a static binding between sl4j and jboss-logging-spi . The jboss-logging default implementation is configured to use log4j. See JBAS-5519.
* The client/jbossall-client.jar library that used to bundle the majority of jboss client libraries, is now referencing them instead through the Class-Path manifest entry. This allows swapping included libraries (e.g. jboss-javaee.jar) without having to re-package jbossall-client.jar. On the other hand, it requires that you have jbossall-client.jar together with the other client/*.jar libraries, so they can be found. See JBAS-4355.
* If using proprietary JBoss/EJB3 annotations, those have moved (since Beta4) into the org.jboss.ejb3.annotation package, EJBTHREE-1099. Those are now included in a new artifact, jboss-ejb3-ext-api.jar
* Interoperating with previous JBoss EJB3 implementations may present problems due to serialVersionUIDs issues, EJBTHREE-1118.
* Use of JBoss Cache 2.x. JBC 2.x has a significantly different API from the 1.x releases used in JBoss AS 4.x and 3.2.x.
* @EJB injections should now work from servlets, JBAS-5646.
* The ClassPathExtension MBean has been replaced with a VFS classloader definition, see JBAS-5446.
For strict JavaEE compatibility compliance you can:
* Enable call-by-value in deployers/ear-deployer-jboss-beans.xml
true
* Enable call-by-value for "jboss:service=Naming" in conf/jboss-service.xml
true
* Set the following system property in your startup script
-Dorg.apache.catalina.STRICT_SERVLET_COMPLIANCE=true
Configuration Issues
This section lists changes that could affect the server configuration.
The directory structure of JBoss 5 resembles that of the 4.x series with some notable differences:
* bin - start scripts and run.jar
* client - client jars
* docs - docs, schemas/dtds, examples
* lib - core bootstrap jars, somewhat different with the introduction of the microcontainer and breakup of jboss-common.
* server - the same server configuration dirs.
o default configuration
+ conf
# bootstrap.xml - new mc kernel bootstrap configuration referencing other
configuration files that contain the beans that setup each individual subsystem.
* classloader.xml
* aop.xml
* jmx.xml
* deployers.xml
* bindings.xml (*New POJO-based ServiceBindingManager*)
* profile.xml
# jax-ws-catalog.xml - oasis catalog driven schema/dtd namespace configuration
# jbossjta-properties.xml - new JBossTS properties
# jboss-service.xml - legacy static mbeans for compatibility
# jndi.properties - the same jndi props
# log4j.xml - the same log4j config
# login-config.xml - the same jaas login config
# props/ - the same default jaas login properties files
# standardjaws.xml - obsolete cmp config
# standardjbosscmp-jdbc.xml - the same cmp2 config
# standardjboss.xml - the same ejb2 config
# xmdesc/ - legacy xmbean descriptors
+ deploy/ - the same deploy directory.
+ deployers/ - new vdf deployers
# bsh-deployer - beanshell deployer
# ejb3.deployer - ejb3 deployers
# jboss-aop-jboss5.deployer - aspect deployer
# jboss-jca.deployer - JCA deployers
# jbossweb.deployer - war deployers
# jbossws.deployer - web services deployers
# seam.deployer - SEAM deployer
# alias-deployers-jboss-beans.xml
# clustering-deployers-jboss-beans.xml
# ear-deployer-jboss-beans.xml - ear deployers
# ejb-deployer-jboss-beans.xml - ejb2.x deployers
# metadata-deployer-jboss-beans.xml - metadata handlers
# security-deployer-jboss-beans.xml - security deployers
# profileservice-jboss-beans.xml.bak - an example of the repository based profile service
+ lib/ - the same static library jars
Various configuration issues:
* Use of the jboss.jgroups.udp.mcast_port property to control easy configuration of multicast port, JBAS-2395
* Overriding of ra.xml properties in jboss-ra.xml, JBAS-3343
* Support for defining depenndencies in JCA adapters, JBAS-4508
* Controlling command line arguments for the appClientLauncher, JBAS-5888.
* Shutdown.sh now accepts a JNDI url, JBAS-5922.
* DeleteWorkDirOnContextDestroy property for JSP pages, JBAS-5453.
* The clustering configurations have been organized in the deploy dir in a new cluster subfolder (JBAS-4709).
* A separate cache is now used for Clustered SSO (JBAS-4676).
* Per webapp configuration of useJK, snapshot mode and snapshot interval (JBAS-3460). Default for useJK is whether jvmRoute is set (JBAS-4961).
* Total replication (rather than buddy replication) is the default setting for session replication (JBAS-5085).
* The transaction manager configuration has moved from conf/jboss-service.xml to deploy/transaction-service.xml (JBAS-5103).
* The default conf/jboss-log4j.xml configuration now includes the thread name for entries in log/server.log (JBAS-5274).
* All the security related configuration files are now grouped under the deploy/security directory (JBAS-5318).
* Loopback is now set to true for all JGroups UDP stacks (JBAS-5323).
EJB3 configuration is now controlled by deployers/ejb3.deployer/META-INF/ejb3-deployers-jboss-beans.xml. For more details check out this wiki page.
For security related configuration changes, please consult this wiki page.
For clustering related changes, check out the Wiki for more info.
Other Issues
* The Farm service is removed. Distributed deployments will eventually be handled by the AS 5 Profile Service, with the Profile Service (or JBoss ON) coordinating deployments across the cluster from a centralized repository. The Farm Service's function of replicating deployment archives between file systems will not be maintained.
* The JSR77 view of the server is not implemented yet.
* Bootstrap time has improved compared to AS5 CR1, but it still somewhat slower when compared to the 4.2.x series. This is due to multiple passes of annotation processing from different subsystems. This will be eventually reduced to a single pass.
* JBoss should now be able to start when JBOSS_HOME contains spaces, JBAS-5796.
Library Updates
For a full list of the JBoss and thirdparty libraries used with JBoss AS 5.0.0.CR2 check the pom.xml found in the component-matrix directory of the source code distribution. To see the maven dependency tree you can also do a 'mvn dependency:tree' from the thirdparty directory of the source code distro.
Some rather important used jboss project versions are listed below:
* JBoss Transactions, v4.4.0.CR2
* JBoss WebServices, v3.0.3.GA
* JBoss Messaging, v1.4.1.CR1
* JBoss Web, v2.1.1.CR7
* JBoss AOP, 2.0.0.CR17
* JBoss EJB3, v1.0.0-Beta3
* JBoss Microcontainer, v2.0.0.CR1
* JBoss Security, v2.0.2.CR6
* Hibernate, v3.3.1.GA
* Hibernate Entity Manager, v3.4.0.GA
* Hibernate Annotations, v3.4.0.GA
* JBoss Cache POJO, v2.2.0.CR5
* JBoss Cache Core, v2.2.0.GA
* JGroups, v.2.6.3.GA
Detailed Release Notes
Includes versions: JBossAS-5.0.0.CR2
Feature Request
* [JBAS-2395] - Allow for easy configuration of multicast port like multicast address
* [JBAS-3343] - JCA 1.5 Resource Adapter Config Properties cannot be specified
* [JBAS-3911] - Default max-pool-size in DataSource configuration
* [JBAS-4508] - Add a way to define dependencies for a JCA adapter
* [JBAS-5249] - Upgrade Bean scripting framework
* [JBAS-5636] - Stop HTTP/AJP connectors on Server.STOP_NOTIFICATION_TYPE
* [JBAS-5647] - HAPartition to support wait for first positive response
* [JBAS-5704] - Provide JAAS credentials in org.jboss.ant.JMX task so that calls can be made to security protected MBeans
* [JBAS-5743] - MBeans have hard coded "localhost" in their names
* [JBAS-5760] - Allow mc bootstrap file to be specified via the "jboss.bootstrap.url" system property
* [JBAS-5761] - Rename conf/*-service.xml to *-beans.xml to be consistent with naming conventions
* [JBAS-5782] - HASingletonElector interface
* [JBAS-5793] - Array interception for pojos stored in FIELD granularity web sessions
* [JBAS-5808] - Expose MC Kernel and DeploymentUnit in ServletContext attributes
* [JBAS-5813] - Download source jars into thirdparty by default
* [JBAS-5822] - Add support for value-factory injection to -service.xml parsing
* [JBAS-5832] - Add Facelets logging bridge to AS
* [JBAS-5841] - Allow the JMS RAR to determine the destinationType at runtime
* [JBAS-5848] - Optimize AnnotatedMetaDataDeployer
* [JBAS-5862] - New look for jmx-console
* [JBAS-5888] - Add support for controlling ClientLauncher behavior via command line arguments
* [JBAS-5896] - Add a MailService sharedSession option
* [JBAS-5922] - Allow shutdown.sh to still work if it passed a http(s) jndi url
* [JBAS-5931] - Ensure that the call into the MDB container is with no security context
* [JBAS-5932] - Refactor redundant code in EJB2 SecurityInterceptors (invoke and invokeHome)
* [JBAS-5939] - MessageDestinationReferenceResolver should be injected
* [JBAS-5946] - SecurityContextEstablishmentValve should handle current security context with a different name
Bug
* [JBAS-1151] - deadlock during cluster failover
* [JBAS-2558] - default virtual host always "localhost"
* [JBAS-3918] - jbossweb virtual-host processing not working
* [JBAS-4282] - Can't create a root context web app
* [JBAS-4287] - run.sh can consume 100% single CPU resources on Solaris
* [JBAS-4399] - @EJB in JSF ignores mappedName
* [JBAS-4522] - Remoting Connector attribute "socketTimeout" in jboss-service.xml should be "timeout"
* [JBAS-4592] - NPE in ExtendedFormAuthenticator
* [JBAS-4661] - org.jboss.test.marshaliiop.test.EjbUnMarshalUnitTestCase.testUnMarshalException failing
* [JBAS-4684] - Invalid war is not showing up in MainDeployer.checkComplete(Deployment)
* [JBAS-4732] - Multihome support: HAJNDI`s HANamingServiceMBean needs a configurable RmiBindAddress (like Naming`s MainMBean)
* [JBAS-4871] - TransactionIsolation is not reset when Connection is returned to the pool
* [JBAS-4965] - Embedded unwrapped deployments fail with opaque error when in WEB-INF/lib
* [JBAS-5095] - Race condition between connection.close() and transaction.rollback() causes connection leak
* [JBAS-5173] - Bug with whitespace in jboss-web.xml
* [JBAS-5236] - Encrypting passwords with DIGEST prevents shutting down JBoss from command line
* [JBAS-5257] - Cannot deploy through jax-ws endpoint API
* [JBAS-5414] - Application class loaders leak to JGroups thread pools
* [JBAS-5453] - Make DeleteWorkDirOnContextDestroy=true the default setting
* [JBAS-5457] - Implement EE 8.2.1 section 2 functionality
* [JBAS-5487] - xml-apis.jar in lib/endorsed causes WrappedRuntimeException
* [JBAS-5578] - Cannot deploy ServiceMBeanSupport as an mc bean with @JMX
* [JBAS-5590] - UnifiedInvoker stop() should not stop its ServerInvoker
* [JBAS-5609] - ClusteredSingleSignOn cannot handle cross-context apps with same session id
* [JBAS-5645] - JBossWeb losing POST data during FORM Authentication
* [JBAS-5646] - @EJB does not work in servlet
* [JBAS-5671] - Attempting to deploy a duplicate context removes existing servlet bindings
* [JBAS-5674] - Web components without top-level annotations not processed correctly
* [JBAS-5681] - Proxy SecurityInterceptor should consider SecurityAssociation Client VM mode possibility
* [JBAS-5684] - servlets are not properly loaded when load-at-startup is 0
* [JBAS-5693] - Web session passivation isn't LRU
* [JBAS-5694] - o.j.test.cluster.defaultcfg.web.field.test.FieldBasedSessionPassivationTestCase.testSessionPassivationWMaxActive fails intermittently
* [JBAS-5695] - Licenses not available for release packaging
* [JBAS-5696] - removal of entity with self-referencing CMR and fk-constraint
* [JBAS-5700] - messaging-service.xml SecurityMetaDataStore needs to have a dependency on JNDIBasedSecurityRegistration
* [JBAS-5714] - Leaked heuristic outcome in XAExceptionUnitTestCase
* [JBAS-5715] - -ds.xml not trimming whitespace in jboss5
* [JBAS-5717] - jboss-ds_1_5.dtd has syntax error
* [JBAS-5719] - Deployment ordering of WAR and -ds.xml not working in JBoss-5.0 CR1
* [JBAS-5735] - Session not reliably bound to SessionReplicationContext if SecurityAssocationValve not present
* [JBAS-5737] - Moderate: AOP Binding JSP reveals source code
* [JBAS-5762] - Binding service deployed after RMI port opened
* [JBAS-5773] - Regression in nested war manifest classpath behavior
* [JBAS-5796] - JBoss does not start with spaces in install path
* [JBAS-5800] - jrmp/pooled-invoker-tests fail due to java.lang.OutOfMemoryError: PermGen Space
* [JBAS-5801] - New ManagedConnection locking does not play nicely with transaction interleaving
* [JBAS-5830] - message-destination needs global resolution support
* [JBAS-5831] - mysql-get-generated-keys does not work with xa datasource
* [JBAS-5833] - maxMessages in activation spec wrongly sets maxSession
* [JBAS-5850] - Tx sticky lbp issue with shutdown nodes
* [JBAS-5852] - InvokerLocator Connector no longer available on 3873
* [JBAS-5855] - Moderate: Cross-Site-Scripting in JMX console
* [JBAS-5871] - Client Metadata Creator does not take class Hierarchy into account for Main-Class
* [JBAS-5880] - Synchronization Problem in TxServerClientInterceptor
* [JBAS-5892] - ClientLauncher relies on full metadata to obtain classpath
* [JBAS-5898] - Build needs to be more explicit in what it copies
* [JBAS-5904] - ClientUserTransaction singleton initialisation is not thread safe
* [JBAS-5906] - Client user transaction lookups aren't closing initial contexts
* [JBAS-5911] - WARStructure should be in the appserver codebase
* [JBAS-5912] - WARStructure should include WEB-INF/lib/*.jars/META-INF in the metadata locations
* [JBAS-5917] - Error during deployment means cannot redeploy
* [JBAS-5921] - Stopped deployments should not be visible in the Profile.getModifiedDeployments
* [JBAS-5923] - Weak hash map usage in UnifiedInvokerHAProxy is not thread safe
* [JBAS-5933] - JMX operations eat underlying exception
* [JBAS-5935] - WebServiceDeployer should create JACC permissions for dynamic web app
* [JBAS-5944] - Get rid of GMS.shun=false in JGroups protocol stacks
* [JBAS-5948] - UserTransactionSessionImpl is not thread safe
Task
* [JBAS-4456] - Replace JRMPProxyService with a remoting based bean.
* [JBAS-4635] - Fix jboss-head-testsuite-sun-1.5
* [JBAS-4669] - Port ClusteredSingleSignOn testNoAuthSingleSignOn test to trunk
* [JBAS-4769] - TransactionLocal cannot be locked when transaction is marked rollback only
* [JBAS-4773] - Move the JBossWS integration tests to the AS test module
* [JBAS-4908] - Support vertical clustering port replacement for cluster services
* [JBAS-4918] - replace ${jboss.server.home.dir}/log references with ${jboss.server.log.dir}
* [JBAS-4952] - Add clustering dependencies to clustered EJB2 beans
* [JBAS-5022] - WebAppClassLoader is not optimized for RMI
* [JBAS-5333] - Fix object name of the JMS based EJB2 entity cache invalidation mbean
* [JBAS-5432] - Ensure HAPartition-based services can handle concurrent JGroups requests
* [JBAS-5446] - ClassPathExtension MBean "removed"
* [JBAS-5503] - JUnitReport OutOfMemoryError failed many testsuite on hudson
* [JBAS-5509] - Remove support for passing null types to HAPartition.callMethodOnCluster
* [JBAS-5560] - Add Seam to JBoss AS testsuite
* [JBAS-5583] - Review timer.num_threads configs in JGroups protocol stacks
* [JBAS-5587] - Move clustered Hibernate 2nd level caching to Hibernate RegionFactory
* [JBAS-5627] - Properly handle cleanup of clustered web session persistent store
* [JBAS-5637] - Put all web-app classloading rules in WarClassLoaderDeployer
* [JBAS-5676] - Reduce the default FD timeout in JGroups stacks
* [JBAS-5679] - metadata: switch to JBoss50Creator from EjbJar30Creator
* [JBAS-5685] - XAResourceWrapper should be in the transaction SPI
* [JBAS-5702] - Add JDBC4 support to DataSourceInterceptor
* [JBAS-5718] - Add maven dependencies in repository.jboss.com
* [JBAS-5748] - Update links in ROOT.war/index.html
* [JBAS-5756] - Integrate jpa-deployers
* [JBAS-5757] - Add scoped and non-scoped annotation tests to as testsuite
* [JBAS-5781] - Use READ_COMMITTED for clustered entity cache
* [JBAS-5788] - Replace Oswego usage with java.util.concurrent
* [JBAS-5794] - Administration and configuration guide
* [JBAS-5795] - Administration and configuration guide
* [JBAS-5797] - Fix / suppress deprecation warnings in connector module
* [JBAS-5803] - Fix the -beans.xml usage in META-INF for jboss deployments
* [JBAS-5804] - Remove the setting of the "types" property in the appserver config
* [JBAS-5805] - Don't wait forever to get the lock in the jdbc and jms resource adapters
* [JBAS-5809] - External configuration from ejb3 project is wrong
* [JBAS-5811] - JBossWS is using external configuration
* [JBAS-5814] - Move jboss.messaging:service=SecurityStore to messaging-jboss-beans.xml
* [JBAS-5820] - Refactor web session replication interaction with JBC into pluggable component
* [JBAS-5821] - Get rid of ClusterPartition deadlock detection config
* [JBAS-5823] - Looking at deployment structure
* [JBAS-5826] - Update dist build to include stax-api.jar and activation.jar copied to lib/endorsed
* [JBAS-5827] - Remove ExtendedByImportUnitTestCase
* [JBAS-5837] - Update the EARStructure to use the StructureContext api
* [JBAS-5842] - Fix the injection of mainDeployer, profileService in ProfileServiceBootstrap
* [JBAS-5843] - Set target on ServiceControllerContext when deployed via @JMX
* [JBAS-5889] - Refactor ClusteredSSO interaction with JBC into pluggable component
* [JBAS-5905] - Validate why JBM's jbm-data Channel config doesn't have FD
* [JBAS-5907] - Fix FieldGranularityClassloaderLeakUnitTestCase.testFieldWar failure
* [JBAS-5909] - RetryInterceptor should close its NamingContext
* [JBAS-5910] - Point out the -b flag in the docs
* [JBAS-5913] - Extract an SPI for cluster module service's interaction with JBoss Cache
* [JBAS-5914] - Convert HAJNDI back to -jboss-beans.xml
* [JBAS-5915] - CacheManager to set TCCL before creating/starting caches
* [JBAS-5916] - Remove the JBC integration SPIs and impls from the AS code base
* [JBAS-5918] - Hudson builds erroneously report builds as failed after ant upgrade
* [JBAS-5940] - Application client support for persistence unit
* [JBAS-5962] - Make release notes for AS5.0.0.CR2
* [JBWS-259] - Scout/jUDDI based JAXR Implementation
Sub-task
* [JBAS-2251] - Fix JBoss Cache / AS integration issues
* [JBAS-2577] - isolating Hibernate as an internal impl detail
* [JBAS-2647] - Remove potential deadlock condition from HASingletonSupport
* [JBAS-3415] - Port RARDeployer
* [JBAS-4192] - Evaluate having ProxyFactoryFinderInterceptor clear the ProxyFactory ThreadLocal on request exit
* [JBAS-4644] - fix org.jboss.test.webservice.jbws309.JBWS309TestCase(JACC)
* [JBAS-5047] - Fix ValidConnectionChecker serialization
* [JBAS-5054] - tests-jacc-security failures
* [JBAS-5252] - Fix classloader leak test failures
* [JBAS-5341] - See if JBM and AS can agree on a shared transport config for UDP and TCP
* [JBAS-5433] - Ensure ClusterPartition can handle concurrent JGroups requests
* [JBAS-5434] - Ensure DistributedReplicantManager can handle concurrent JGroups requests
* [JBAS-5435] - Ensure DistributedState can handle concurrent JGroups requests
* [JBAS-5436] - Ensure HASessionState can handle concurrent JGroups requests
* [JBAS-5437] - Ensure HA-JNDIcan handle concurrent JGroups requests
* [JBAS-5438] - Ensure HASingletonSupport can handle concurrent JGroups requests
* [JBAS-5439] - Ensure JGCacheInvalidationBridge can handle concurrent JGroups requests
* [JBAS-5441] - Ensure misc HAPartition-based services can handle concurrent JGroups requests
* [JBAS-5580] - Upgrade JGroups to 2.6.3.GA
* [JBAS-5585] - Fix tomcat federation tests
* [JBAS-5589] - Update hibernate-int module to understand RegionFactory
* [JBAS-5596] - Upgrade jboss-integration to 5.0.0.CR2
* [JBAS-5601] - Upgrade jboss-managed/metatype to 2.0.0.CR/GA
* [JBAS-5602] - Upgrade jboss-vfs to 2.0.0.CR/GA
* [JBAS-5603] - Upgrade jboss-deployers to 2.0.0.CR/GA
* [JBAS-5604] - Upgrade jboss-microcontainer to 2.0.0.CR/GA level
* [JBAS-5605] - Upgrade jboss-reflect to 2.0.0.CR/GA level
* [JBAS-5606] - Upgrade jboss-mdr to 2.0.0.CR/GA level
* [JBAS-5607] - Upgrade jboss-classloading to 2.0.0.CR2
* [JBAS-5621] - Ensure session regions are cleaned up in undeploy
* [JBAS-5624] - Fix org.jboss.test.cluster.* tests
* [JBAS-5625] - fix org.jboss.test.profileservice.* tests
* [JBAS-5626] - Fix org.jboss.test.web.* tests
* [JBAS-5630] - Web session persistent store cleanup with total repl and no marshalling
* [JBAS-5653] - Upgrade jboss-metadata to CR/GA level
* [JBAS-5673] - Metadata processing needs to be redone
* [JBAS-5687] - org.jboss.test.profileservice tests failing with file locking issues on Windows
* [JBAS-5690] - org.jboss.test.jca*
* [JBAS-5691] - org.jboss.test.jmx
* [JBAS-5692] - org.jboss.test.naming
* [JBAS-5699] - Upgrade JBoss Security to 2.0.2.CR6
* [JBAS-5705] - Upgrade JBoss Cache to 2.2.0.GA
* [JBAS-5708] - Upgrade Spring to 2.5.5
* [JBAS-5738] - Upgrade jboss transactions to 4.4.0.CR2
* [JBAS-5747] - Upgrade to the latest JSF implementation 1.2_09 (from 1.2_08)
* [JBAS-5751] - Make max unreplicated time for clustered session configurable in AS 5
* [JBAS-5784] - Upgrade JBoss JAXR to 1.2.0.SP2
* [JBAS-5806] - org.jboss.test.refs.test.*
* [JBAS-5807] - org.jboss.test.deployers.ear.test.EARAltDDConnectorDeploymentUnitTestCase
* [JBAS-5836] - Upgrade jbossws to 3.0.3
* [JBAS-5838] - Upgrade ha-client and ha-server-api to 1.1.0.GA
* [JBAS-5839] - Upgrade ejb3
* [JBAS-5840] - Uprade jboss-aspects to CR level
* [JBAS-5844] - Upgrade jboss-remoting to 2.5.0.GA
* [JBAS-5845] - Upgrade jnpclient and jnpserver to 5.0.0.CR2
* [JBAS-5846] - org.jboss.test.asynch.AsynchTestCase
* [JBAS-5847] - Upgrade hibernate-core/jmx/jbosscache2 to 3.3.0.GA
* [JBAS-5853] - Upgrade hibernate-annotations/common-annotations/entity-manager to latest CR2 releases
* [JBAS-5861] - Upgrade jboss-test to 1.1.1.GA
* [JBAS-5865] - Upgrade woodstox to spec-compliant version (3.2.6)
* [JBAS-5866] - Fix org.jboss.test.timer.test.BasicTimerUnitTestCase.testMDBTimer
* [JBAS-5867] - fix org.jboss.test.profileservice.test.DeployUnitTestCase(profileservice).testEjb3xDeployment
* [JBAS-5868] - fix appclient regressions
* [JBAS-5875] - Clustered webapps session manager to use same ObjectName pattern as non-clustered
* [JBAS-5876] - Expose StandardManager attributes/operations in JBossCacheManagerMBean
* [JBAS-5877] - Upgrade jboss-javaee.jar to remove persistence APIs
* [JBAS-5882] - Upgrade BSF (Bean Scripting Framework) to v2.4.0 (from 2.3.0)
* [JBAS-5884] - Access MBeanServer via Tomcat Registry
* [JBAS-5885] - Clustered classloader leak tests for web session clustering
* [JBAS-5890] - Upgrade to the latest jboss-common-core 2.2.8.GA
* [JBAS-5891] - fix JBAS-5203 regression
* [JBAS-5893] - Upgrade Javassist to 3.8.1.GA
* [JBAS-5899] - Possible regression due to Ejb3ClientDeployer changes
* [JBAS-5902] - fix org.jboss.test.jca.test.ManagedDeploymentUnitTestCase
* [JBAS-5920] - fix org.jboss.test.xslt.test.ScopedXalanUnitTestCase.testScopedXalanDeployment
* [JBAS-5926] - fix org.jboss.test.jpa.test.WebClasses*.testWebJPA tests
* [JBAS-5934] - Upgrade jbossxb to 2.0.0.CR15
* [JBAS-5938] - Upgrade hibernate-core/jmx/jbosscache2 to 3.3.1
* [JBAS-5947] - Upgrade Seam integration to 5.0.0.CR2
Patch
* [JBAS-4478] - ignore local ant options when building
* [JBAS-5073] - fix build authenticated proxy (there seems to have been a cut and paste error at some point)
Thirdparty Change
* [JBAS-5122] - Track jboss and thirdparty dependencies upgrades for JBoss 5.0.0.CR2
* [JBAS-5901] - Update the bundled ant version used to build the server to 1.7.1
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177260#4177260
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177260
17 years, 10 months
[JBoss jBPM] - deploy jbpm-enterprise.ear on jboss 4.2.2 ga
by AJanz
i got a jboss 4.2.2 ga server using seam.
i deployed jbpm-enterprise.ear on it.
in the server.log i see
| 2008-09-17 23:19:48,582 DEBUG [org.jboss.proxy.ejb.ProxyFactory] Proxy Factory for ejb/CommandServiceBean initialized
| 2008-09-17 23:19:48,629 DEBUG [org.jboss.system.ServiceController] Creating service jboss.j2ee:service=EJB,plugin=pool,jndiName=ejb/CommandServiceBean
| 2008-09-17 23:19:48,629 DEBUG [org.jboss.ejb.plugins.StatelessSessionInstancePool] Creating jboss.j2ee:service=EJB,plugin=pool,jndiName=ejb/CommandServiceBean
| 2008-09-17 23:19:48,629 DEBUG [org.jboss.ejb.plugins.StatelessSessionInstancePool] Created jboss.j2ee:service=EJB,plugin=pool,jndiName=ejb/CommandServiceBean
| 2008-09-17 23:19:48,629 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.j2ee:service=EJB,plugin=pool,jndiName=ejb/CommandServiceBean dependents are: []
| 2008-09-17 23:19:48,629 DEBUG [org.jboss.ejb.StatelessSessionContainer] Created jboss.j2ee:jndiName=ejb/CommandServiceBean,service=EJB
but when i try to get the commandservice bean i got error.
my function is
|
| Hashtable p = new Hashtable();
| p.put(InitialContext.INITIAL_CONTEXT_FACTORY,
| "org.jnp.interfaces.NamingContextFactory");
| p.put(InitialContext.PROVIDER_URL, "jnp://localhost:1099");
| p.put(InitialContext.URL_PKG_PREFIXES,
| "org.jboss.naming:org.jnp.interfaces");
| jndiContext = new InitialContext(p);
| RemoteCommandServiceHome remoteCommandServiceHome = (RemoteCommandServiceHome) jndiContext
| .lookup("ejb/CommandServiceBean");
| remoteCMDService = remoteCommandServiceHome.create();
|
i got the error
23:35:17,660 ERROR [Manager] User:NoneError creating remotecmdservice
javax.transaction.TransactionRolledbackException: Invalid invocation, check your
deployment packaging, method=public abstract org.jbpm.ejb.RemoteCommandService
org.jbpm.ejb.RemoteCommandServiceHome.create() throws javax.ejb.CreateException,
java.rmi.RemoteException; nested exception is:
javax.ejb.EJBException: Invalid invocation, check your deployment packag
ing, method=public abstract org.jbpm.ejb.RemoteCommandService org.jbpm.ejb.Remot
eCommandServiceHome.create() throws javax.ejb.CreateException,java.rmi.RemoteExc
eption
please help
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177255#4177255
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177255
17 years, 10 months
[Beginners Corner] - Re: problem with service MSSQLDS not installed
by PeterJ
What you posted is an excerpt from the report that the deployer logs after depliyment is done. This rpeort rarely offers any clues as to what went wrong. You need to search the console log for the first exception stack trace that shows up after that the app server and post that stack trace.
If the console log scrolled off of the console buffer, you will either have to increase the console buffer size (I have mine set to 9000 lines) and try again, or look the exception up in the server.log files (usually difficult because various stack traces show up as debug log entries and those are not important), or start JBossAS up without having your app deployed then wait until you see the "Started in xxx seconds" log entry and then deploy your app - you can then post everything after the "Started in" entry.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177253#4177253
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177253
17 years, 10 months
[JBoss Messaging] - High volume usage patterns and best practices
by xxbrandonoxx
I am trying to implement a system that will require consistently high volume with long running and constantly connected clients. To date I have followed the samples included with JBoss Messaging and am creating a new connection+session+temp_response_queue on a per request basis. It was suggested that some of this is actually an anti-pattern.
This actually works fairly well and sufficiently fast on my local development environment aka, laptop, but breaks down when I promote it to a clustered development environment that is otherwise identical. I fairly quickly run out of memory, and get a 25+% failure rate even at low volumes. I am inclined to believe it is in part due to the way in which I am accessing the queue's and topics.
I would like advice on the best way to handle the "pooling" of some of these objects (connections and sessions) for reuse. Is this advisable at all? If so, is there solution examples anyone is aware of? I would hate to have to create my own pooling logic with all the inherent issues in high volume systems.
One example of where I do not see the feasibility of this is in the connection object. I do not see any exposed way in the API to "test" the connectedness of the connection objects. I would assume in any pooling situation I would have to make sure it is still alive, etc.
Any help would be appreciated.
Thanks,
Brandon
=======================================================
Solution Descrpition
Client: A simple one form one page JSF app
Server: A fairly simple MDB. It currently makes an HTTP request and echo's the response to a client created temporary response queue. It also forwards a copy to an "observer" topic for further SOA visibility.
| public String executeSynchronous(String resourceUrl, HTTPMethod method, String payload, final long timeout) {
| JMSUtil jmsUtil = new JMSUtil();
| if (timeout > MAX_TIMEOUT) {
| return "Error: timeout provided exeeds MAX_TIMEOUT(" + MAX_TIMEOUT + ")";
| }
|
| Map<String, String> headers = new HashMap<String, String>();
| headers.put("Method", method.name());
| headers.put("URL", resourceUrl);
|
| String messageId = JMSUtil.generateUUID();
| Session session = jmsUtil.generateSession();
| Queue responseQueue = jmsUtil.generateResponseQueue(session);
| jmsUtil.sendSOAQueueMessage(session, payload, jndiReferenceSOAIn, headers, messageId, responseQueue);
| String response = jmsUtil.getSOAResponse(session, responseQueue, timeout);
| jmsUtil.closeSession(session);
|
| return response;
| }
|
calls...
| public void sendSOAQueueMessage(Session session, String payload, String jndiReference, Map<String, String> headers, String messageId, Queue responseQueue) {
| try {
| // Create Message
| TextMessage message = session.createTextMessage(payload);
|
| // Assign Headers
| for (String headerName : headers.keySet()) {
| message.setStringProperty(headerName, headers.get(headerName));
| }
|
| // Set UUIDreturn null;
| message.setStringProperty("EntertainmentSOARequestId", messageId);
| message.setJMSReplyTo(responseQueue);
|
| // Create the producer.
|
| MessageProducer sender = session.createProducer(getSOAInQueue());
| sender.send(message);
| sender.close();
|
| // Commit if needed
| if (transacted) {
| session.commit();
| }
| } catch (JMSException e) {
| logger.error("A JMS Exception occurred in sending a JMS SOA message!", e);
| }
| }
|
Supported by the following util methods...
| rotected static Connection getConnection() {
| if (connection == null) {
| Hashtable properties = new Hashtable();
| properties.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
| properties.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");
| properties.put(Context.PROVIDER_URL, "jnp://localhost:1099");
| properties.put(Context.SECURITY_PRINCIPAL, "not_real");
| properties.put(Context.SECURITY_CREDENTIALS, "not_real");
|
| Context context;
| try {
| context = new InitialContext(properties);
| connectionFactory = (ConnectionFactory) context.lookup("ConnectionFactory");
| } catch (NamingException e) {
|
| e.printStackTrace();
| return null;
| }
|
| try {
| connection = connectionFactory.createConnection();
| connection.start();
| } catch (JMSException e) {
| return null;
| }
| }
| return connection;
| }
| public Queue generateResponseQueue(Session session) {
| try {
| return session.createTemporaryQueue();
| } catch (JMSException e) {
| logger.error("Could not generate temporary queue for receiving response", e);
| return null;
| }
| }
| public Session generateSession() {
| try {
| // Get a connection
| Connection connection = getConnection();
|
| // Create the session
| return connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
| } catch (JMSException e) {
| logger.error("Could not generate session", e);
| return null;
| }
| }
| public String getSOAResponse(Session session, Destination responseQueue, long timeout) {
| try {
| // Create the consumer
| MessageConsumer consumer = session.createConsumer(responseQueue);
| Message message = consumer.receive(timeout);
| message.acknowledge();
| consumer.close();
|
| if (message != null && message instanceof TextMessage) {
| return ((TextMessage) message).getText();
| } else {
| logger.error("Recieved message was not of type TextMessage!");
| return "Recieved message was not of type TextMessage!";
| }
|
| } catch (JMSException e) {
| logger.error("A JMS Exception occurred in receiving a JMS SOA message!", e);
| return "A JMS Exception occurred in receiving a JMS SOA message! " + e.getMessage();
| }
| }
|
MDB
| @MessageDriven(activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
| @ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/SOAInQueue"),
| @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge") })
| public class SOARouterMDB implements MessageListener {
|
| private final RESTAccessor restAccessor = new RESTAccessor();
|
| private static Logger logger = Logger.getLogger(SOARouterMDB.class);
|
| public void onMessage(Message msg) {
| try {
| Responder responder = new Responder();
| TextMessage tmsg = (TextMessage) msg;
|
| HTTPMethod method = HTTPMethod.valueOf(tmsg.getStringProperty("Method"));
| String url = tmsg.getStringProperty("URL");
| Map<String, String> httpHeaders = new HashMap<String, String>();
| Map<String, String> allHeaders = new HashMap<String, String>();
| Destination destination = tmsg.getJMSReplyTo();
|
| System.out.println("Destination: " + destination);
|
| // Load HttpHeaders
| Enumeration<String> propertyNames = tmsg.getPropertyNames();
| while (propertyNames.hasMoreElements()) {
| String propertyName = propertyNames.nextElement();
| if (propertyName.startsWith("HttpHeader")) {
| httpHeaders.put(propertyName.substring(10), tmsg.getStringProperty(propertyName));
| }
| allHeaders.put(propertyName, tmsg.getStringProperty(propertyName));
| }
|
| HTTPResponse response = null;
|
| switch (method) {
| case GET:
| response = restAccessor.doGet(url, httpHeaders);
| if (!response.isError()) {
| responder.respond(destination, allHeaders, response.getData());
| responder.broadcast(allHeaders, response.getData());
| } else {
| responder.reportError(tmsg);
| }
| break;
| case POST:
| response = restAccessor.doPost(url, httpHeaders, new ByteArrayInputStream(tmsg.getText().getBytes()));
| if (!response.isError()) {
| responder.respond(destination, allHeaders, response.getData());
| responder.broadcast(allHeaders, response.getData());
| } else {
| responder.reportError(tmsg);
| }
| break;
| case DELETE:
| response = restAccessor.doDelete(url, httpHeaders, tmsg.getText());
| if (!response.isError()) {
| responder.respond(destination, allHeaders, response.getData());
| responder.broadcast(allHeaders, response.getData());
| } else {
| responder.reportError(tmsg);
| }
| break;
| case PUT:
| response = restAccessor.doPost(url, httpHeaders, new ByteArrayInputStream(tmsg.getText().getBytes()));
| if (!response.isError()) {
| responder.respond(destination, allHeaders, response.getData());
| responder.broadcast(allHeaders, response.getData());
| } else {
| responder.reportError(tmsg);
| }
| break;
| default:
| // TODO: asdf
| }
| } catch (Exception e) {
| logger.error("Error processing SOA request", e);
| }
| }
|
| @PreDestroy
| public void destroy() {
| }
|
| }
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177242#4177242
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177242
17 years, 10 months
[JBoss jBPM] - JAXB in jBPM
by hauch
I'm trying to use JAXB in jBPM, which produces the error mentioned in https://jira.jboss.org/jira/browse/JBPM-1404.
I have downloaded the source code and tried to apply the patch described in the jira by replacing only the class and the inner classes.
Unfortunately I am not able to get it to work.
I am using the jBPM bundled with JBoss ESB 4.4, and I have downloaded and patched jpdl-3.2.2-SOA-4.2 from subversion.
The findClass in ProcessClassLoader now looks like:
public Class findClass(String name) throws ClassNotFoundException {
| Class clazz = null;
|
| FileDefinition fileDefinition = processDefinition.getFileDefinition();
| if (fileDefinition!=null) {
| String fileName = "classes/" + name.replace( '.', '/' ) + ".class";
| byte[] classBytes;
| try {
| classBytes = fileDefinition.getBytes(fileName);
| clazz = defineClass(name, classBytes, 0, classBytes.length);
| } catch (JbpmException e) {
| clazz = null;
| }
| // Add the package information
| final int packageIndex = name.lastIndexOf('.') ;
| if (packageIndex != -1) {
| final String packageName = name.substring(0, packageIndex) ;
| final Package classPackage = getPackage(packageName) ;
| if (classPackage == null) {
| definePackage(packageName, null, null, null, null, null, null, null) ;
| }
| System.out.println("package is: "+packageName);
| }
| }
|
| if (clazz==null) {
| throw new ClassNotFoundException("class '"+name+"' could not be found by the process classloader");
| }
|
| return clazz;
| }
|
- and the output is:
20:14:04,030 INFO [STDOUT] package is: dk.lenio.em.smile.jbpm.vo
20:14:04,063 ERROR [GraphElement] action threw exception: "dk.lenio.em.smile.jbpm.vo" doesnt contain ObjectFactory.class or jaxb.index
javax.xml.bind.JAXBException: "dk.lenio.em.smile.jbpm.vo" doesnt contain ObjectFactory.class or jaxb.index
I have a class named ObjectFactory in the package dk.lenio.em.smile.jbpm.vo.
Any suggestions?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177235#4177235
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177235
17 years, 10 months
[Clustering/JBoss] - it's a member, but it's not a member
by shulok
14:09:16,178 WARN [NAKACK] 158.185.143.28:33738] discarded message from non-member 158.185.143.26:34114, my view is [158.185.143.27:42340|3] [158.185.143.27:42340, 158.185.143.28:33738, 158.185.143.25:33577, 158.185.143.26:34114]
14:09:16,429 WARN [NAKACK] 158.185.143.28:33738] discarded message from non-member 158.185.143.25:33577, my view is [158.185.143.27:42340|3] [158.185.143.27:42340, 158.185.143.28:33738, 158.185.143.25:33577, 158.185.143.26:34114]
As near as I can tell, this happens when I shotgun start some of the nodes in the cluster. If I let them come up sequentially, this doesn't seem to happen. Any ideas?
(4.2.2GA)
Thanks,
Thom
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177222#4177222
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177222
17 years, 10 months
[Installation, Configuration & DEPLOYMENT] - Re: Need suggestion about how to proceed.
by rks_86
No, I dont think JBoss ignoring those MSM.HOME and MSM.CONFIG properties. As I'm able to login to my application it seems that its taking the DB details from my application property file config.xml(Am not sure)
as its showing up in the login page the username and password field and I'm able to login into my application whose all data are inside a oracle schema. But its not able to take the css files present may be thats why GUI looks odd.
And the Resource folder is not from JBoss its my applications Resouce folder which contains all css and templates for my application.
I have made my app work in windows system long time back with JBoss4.0.5 but there i made big changes in Jboss config files to make it work which i dont want for linux system.
I need to figureit out how JBoss will cache my css and templates.
Yours suggestions are worthful. Thanks a lot.
I think I will make it work very soon.
and will post the results how i made it work .please keep this thread in watch list.
Thanks a lot.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177220#4177220
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177220
17 years, 10 months
[Beginners Corner] - problem with service MSSQLDS not installed
by MikePhoenix
When I try to deploy an application that I had running on 4.0.1 to 4.2.3 it fails to deploy. This appears to be the root cause:
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.jca:service=DataSourceBinding,name=MSSQLDS
State: NOTYETINSTALLED
Depends On Me:
jboss.mq:service=PersistenceManager
What doesn't make sense to me is the fact that this seems to point to a binding name that should be used for MS SQL Server and we are not using that in our environment. I am using MySQL under the default-ds JNDI name and have removed hsql-ds.xml.
I sure would appreciate any help on this matter. My attempts at searching the site have been fruitless. I would also be grateful for any suggestions on how to debug the many arcane messages that JBoss spits out without having to constantly post questions on this forum.
Thanks,
Mike
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177211#4177211
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177211
17 years, 10 months
[JBoss Portal] - Help! Timeout occuring.
by johnboy
I am running a pretty reasonable version of a series of JSF xhtml in different portals. I am using JBOSS 2.6.5SP1 Portal Bridge B3. When I get into a session and start viewing some pages I would expect the session to timeout after 2hours perconfig.
When I get back to the app and hit a key, I would expect to see a login prompt in an attempt to kickstart the session.
What I get is:
08:16:51,063 ERROR [[Faces Servlet]] Servlet.service() for servlet Faces Servlet threw exception
INFO | jvm 1 | 2008/08/29 08:16:51 | javax.faces.FacesException: No saved portlet window state for an id ConfigurationPortlet2DCCB4AA0DC8790FAE3205694A9475F2:view:jbpns_2fdefault_2fManage_20SVP_2fConfigurationPortletWindowsnpbj
INFO | jvm 1 | 2008/08/29 08:16:51 | at org.jboss.portletbridge.context.ServletExternalContextImpl.(ServletExternalContextImpl.java:96)
INFO | jvm 1 | 2008/08/29 08:16:51 | at org.jboss.portletbridge.context.FacesContextFactoryImpl.getFacesContext(FacesContextFactoryImpl.java:164)
INFO | jvm 1 | 2008/08/29 08:16:51 | at javax.faces.webapp.FacesServlet.service(FacesServlet.java:239)
INFO | jvm 1 | 2008/08/29 08:16:51 | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
INFO | jvm 1 | 2008/08/29 08:16:51 | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
INFO | jvm 1 | 2008/08/29 08:16:51 | at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:147)
INFO | jvm 1 | 2008/08/29 08:16:51 | at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:276)
INFO | jvm 1 | 2008/08/29 08:16:51 | at org.ajax4jsf.Filter.doFilter(Filter.java:175)
INFO | jvm 1 | 2008/08/29 08:16:51 | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
INFO | jvm 1 | 2008/08/29 08:16:51 | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
INFO | jvm 1 | 2008/08/29 08:16:51 | at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
INFO | jvm 1 | 2008/08/29 08:16:51 | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
INFO | jvm 1 | 2008/08/29 08:16:51 | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
INFO | jvm 1 | 2008/08/29 08:16:51 | at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
INFO | jvm 1 | 2008/08/29 08:16:51 | at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
INFO | jvm 1 | 2008/08/29 08:16:51 | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
INFO | jvm 1 | 2008/08/29 08:16:51 | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
INFO | jvm 1 | 2008/08/29 08:16:51 | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
INFO | jvm 1 | 2008/08/29 08:16:51 | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
INFO | jvm 1 | 2008/08/29 08:16:51 | at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
INFO | jvm 1 | 2008/08/29 08:16:51 | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
INFO | jvm 1 | 2008/08/29 08:16:51 | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
INFO | jvm 1 | 2008/08/29 08:16:51 | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
INFO | jvm 1 | 2008/08/29 08:16:51 | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
INFO | jvm 1 | 2008/08/29 08:16:51 | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
INFO | jvm 1 | 2008/08/29 08:16:51 | at java.lang.Thread.run(Unknown Source)
Has anyone seen this kind of thing before? I know there is a config setting I am missing, but am confused about where to look.
Any thoughts would be useful.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177206#4177206
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177206
17 years, 10 months
[JBoss Messaging] - jms and fault tolerance
by francesco_81
HI all,
I've a problem in the following scenario:
there is a clusterd JBoss environmet with 2 or more messaging-node (call it mnode0, mnode1, ...), a distributed topic (call it 'mytopic'), a Publisher and a Subscriber applications on 'mytopic'. In both the pub and the sub I lookup a 'ConnectionFactory' referring to a the jndi service resolved with the url of mnode0 (e.g. 192.168.0.1:1199).
The publisher periodically sends a message.
The listener (of the sub) receives them.
If mnode0 crash on the pub I've got an exception and the listener isn't able to know that an error has happened. It isn't a nice behaviour,
Is there a manner to route the messages to an other node of the cluster of AS in order to get fault tolerance? Have I to configure the post office?
I used JB_AS 4.2.2GA and JBM 1.4.0SP3 with MySql. I've done every step of the 'JBoss Messaging Installation (chap 4 of JBoss Messaging 1.4 User's Guide)
Regards.
Francesco
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177186#4177186
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177186
17 years, 10 months
[Microcontainer] - Re: Blog post about deployers
by bob.mcwhirter
Yes, each Deployer implementation calls setStage(...) to indicate which stage of deployment it should be considered a candidate. There's a variety of base deployers you can build from, which imply the stage. For instance, there's AbstractParsingDeployer which sets the stage to PARSE. Then there's AbstractParsingDeployerWithOutput which designates it'll produce some object (MetaData or other attachments) as the result of the parse.
Based upon available inputs (files, directories, resources or MetaData) it may fire its deploy() and produce more MetaData or alter existing MetaData (or just take an action and produce no meta-data at all).
Within each stage, your deployers are ordered, so you can wedge things before or after existing deployers to change how things ultimately get processed.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177184#4177184
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177184
17 years, 10 months
[Installation, Configuration & DEPLOYMENT] - Re: Need suggestion about how to proceed.
by rks_86
"jaikiran" wrote : What is the name of the WAR file that you place in the deploy folder? Also post the JBoss console logs.
|
| While posting the logs or xml content or code, remember to wrap it in a code block using the Code button in the message editor window and please hit the Preview button to make sure your post is correctly formatted
Thanks
After you told me to send the server log files i just grepped through the log and found that my applications key files are curropt thats why its not taking my config.xml file.
I found no errors except the above license key invalid.
Noe I'm able to login to the application but the html & javascript files files are not showing up .So the gui looks horrible. I think its not able to take the Resource folder which contains all the GUI stuff.
Do i need to set some variable in some httpd.conf file to let my Resource folder recognized by server.
like in apache we set Custom_Template_Root "blash/blah/"
Alias, etc etc.
If these all required then please let me know where should i set these parameters .
Thanks,
Rk
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177172#4177172
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177172
17 years, 10 months
[JBoss jBPM] - Re: wiki>>JbpmBuildingTheSources: update for svn?
by kukeltje
anonymous wrote : I wonder why it is so difficult to get a simple, direct and clear answer...the replys are always "in svn", "in cvs", "already answered". Maybe i'm completely insane, but could it be that if so many people ask for it maybe it isn't so easy or so clear. Can't you think that maybe the problem is the information and the instructions and not the people?
|
| If someone asks me where the sourcecode is, the answer (now) is The source code is in SVN. Because it is.
|
| If I say: "I already answered it", is because I already did (multiple times)
|
| The wiki currently is in a state of flux so to some extend it is the information and not the people, but on http://jbpm.dyndns.org/jbpmwiki there IS a description on how to build from the sources with eclipse and maven. The way it currently is, was new to me as well, but I got it up and running in 15 minutes, so lets get that out of the way first.
|
| anonymous wrote : maybe it's not enough for many people that needs more complete information.
|
| Depends on the target audiance. NASA will never provide you with the docs on how to build a rocket, not to the level that you could use build one. Simply because the docs they *do* have are not targeted at you and writing docs so you could give it a try costs to many hours and will still result in to many questions to be answerd. So.... The same is true here. You need the source if you want to change something, If you don't, use the jars. If you want to change something CONSTRUCTIVELY (contributing back) you will find enough info in the current docs
|
| The reason I might sound offensive is that these questions are so basic (and distributed over many topics) That a reference to the wiki (the correct one for this, which again unfortunately is down at the moment get's lost quickly.
|
| anonymous wrote : On the other hand, it's not necessary to be so...offensive?nobody knows everything. It's possible, maybe, that i'm quite expert on java ee, struts, jsf, hibernate, ibatis, and much more and don't know anything about ant or maven. It's possible, isn't it?No most likely not, and even then, if it was, you would have the capability of lean maven/ant quickly
|
| anonymous wrote : What if I don't know anything about development or programming?i don't have the right to test it and learn?
| You do, but that is why the jBPM suite is provided. A preconfigured JBoss AS with database, jBPM etc... Runs out of the box.
|
| anonymous wrote : I think that a forum is a very useful tool for a community.A place to express, to share, to learn, to teach, to grow. Some people in this forum could be a little kinder. It is, but a jBPM forum is not the place on where you should learn maven and ant.
|
| anonymous wrote : , for dummies (like me)I'm not saying you are a dummy, the jBPM SOURCE is just not targeted at dummies. It is for well experienced developers.
|
| anonymous wrote : Sorry for writting so much.No problem, but I hope you fully understand my response and why I respond in the way I respond. The (small) error I made is that I posted a link to the sources and not the wikipage on building the sources
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177108#4177108
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177108
17 years, 10 months
[EJB/JBoss] - Jboss hangs after running for a while
by imranpariyani
My application runs fine for a while but after that it just hangs and in the log file i see this warnings
| 2008-09-16 21:03:00,116 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.c
| oordinator.BasicAction_58] - Abort of action id -3f57fee6:96b7:48ce8118:30f42 invoked while multiple threads active within it.
| 2008-09-16 21:03:00,117 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.c
| oordinator.CheckedAction_2] - CheckedAction::check - atomic action -3f57fee6:96b7:48ce8118:30f42 abo
| rting with 1 threads active!
| 2008-09-16 21:03:00,117 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.c
| oordinator.BasicAction_58] - Abort of action id -3f57fee6:96b7:48ce8118:30f48 invoked while multiple
| threads active within it.
| 2008-09-16 21:03:00,117 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.c
| oordinator.CheckedAction_2] - CheckedAction::check - atomic action -3f57fee6:96b7:48ce8118:30f48 abo
| rting with 1 threads active!
| 2008-09-16 21:03:00,118 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.c
| oordinator.BasicAction_58] - Abort of action id -3f57fee6:96b7:48ce8118:30f4e invoked while multiple
| threads active within it.
| 2008-09-16 21:03:00,118 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.c
| oordinator.CheckedAction_2] - CheckedAction::check - atomic action -3f57fee6:96b7:48ce8118:30f4e abo
| rting with 1 threads active!
| 2008-09-16 21:03:00,118 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.c
| oordinator.BasicAction_58] - Abort of action id -3f57fee6:96b7:48ce8118:30f54 invoked while multiple
| threads active within it.
| 2008-09-16 21:03:00,118 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.c
| oordinator.CheckedAction_2] - CheckedAction::check - atomic action -3f57fee6:96b7:48ce8118:30f54 abo
| rting with 1 threads active!
| 2008-09-16 21:05:00,121 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.c
| oordinator.BasicAction_58] - Abort of action id -3f57fee6:96b7:48ce8118:30f5e invoked while multiple
| threads active within it.
| 2008-09-16 21:05:00,121 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.c
| oordinator.CheckedAction_2] - CheckedAction::check - atomic action -3f57fee6:96b7:48ce8118:30f5e abo
| rting with 1 threads active!
| 2008-09-16 21:05:00,122 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.c
| oordinator.BasicAction_58] - Abort of action id -3f57fee6:96b7:48ce8118:30f68 invoked while multiple
| threads active within it.
| 2008-09-16 21:05:00,122 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.c
| oordinator.CheckedAction_2] - CheckedAction::check - atomic action -3f57fee6:96b7:48ce8118:30f68 abo
| rting with 1 threads active!
| 2008-09-16 21:06:54,238 DEBUG [org.hibernate.impl.SessionImpl] opened session at timestamp: 12215920
| 142
| 2008-09-16 21:06:54,238 DEBUG [org.hibernate.ejb.AbstractEntityManagerImpl] Looking for a JTA transa
| ction to join
| 2008-09-16 21:06:54,238 DEBUG [org.hibernate.jdbc.JDBCContext] successfully registered Synchronizati
| on
| 2008-09-16 21:06:54,238 DEBUG [org.hibernate.ejb.AbstractEntityManagerImpl] Looking for a JTA transa
| ction to join
| 2008-09-16 21:06:54,238 DEBUG [org.hibernate.ejb.AbstractEntityManagerImpl] Transaction already join
| ed
| 2008-09-16 21:07:00,124 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.c
| oordinator.BasicAction_58] - Abort of action id -3f57fee6:96b7:48ce8118:30f72 invoked while multiple
| threads active within it.
| 2008-09-16 21:07:00,124 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.c
| oordinator.CheckedAction_2] - CheckedAction::check - atomic action -3f57fee6:96b7:48ce8118:30f72 abo
| rting with 1 threads active!
| 2008-09-16 21:07:00,124 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.c
| oordinator.BasicAction_58] - Abort of action id -3f57fee6:96b7:48ce8118:30f78 invoked while multiple
| threads active within it.
| 2008-09-16 21:07:00,125 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.c
| oordinator.CheckedAction_2] - CheckedAction::check - atomic action -3f57fee6:96b7:48ce8118:30f78 abo
| rting with 1 threads active!
| 2008-09-16 21:11:54,246 DEBUG [org.hibernate.impl.SessionImpl] opened session at timestamp: 12215923
| 142
| 2008-09-16 21:11:54,246 DEBUG [org.hibernate.ejb.AbstractEntityManagerImpl] Looking for a JTA transa
| ction to join
| 2008-09-16 21:11:54,246 DEBUG [org.hibernate.jdbc.JDBCContext] successfully registered Synchronizati
| on
| 2008-09-16 21:11:54,246 DEBUG [org.hibernate.ejb.AbstractEntityManagerImpl] Looking for a JTA transa
| ction to join
| 2008-09-16 21:11:54,246 DEBUG [org.hibernate.ejb.AbstractEntityManagerImpl] Transaction already join
| ed
|
these warnings just keeps repeating .. is it because of some memory leak ?
or does it happens when writing the entities to the cache and reading it at the same time ?
I am using JBOSS 4.2.2 GA
i would appreciate any suggestions
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177091#4177091
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177091
17 years, 10 months
[JBoss Tools (users)] - Can't generate seam entities
by ssopiadis
Hi!
First of all apologize my realy bad english (i 'm greek) ... and my newbie understandnig of the SEAM-world (i 'm very new to this J2EE stuff).
My problem is realted to Eclipse 3.4, JBOSS Tools 3.0.0 Alpha and !!GLASSFISH!!
Had no problem with installing Eclipse, the (nightly build) of JBoss Tools (16/9/2008) into Eclipse (used dropin folder) and downloading and setting up Glassfish v2 driver and the application server. Setup of JBOSS 4.2.1GA into the framework worked also fine without any problem. MySQL driver was also setup, cause Eclipse seems to have problems finding the preconfigured driver.
JRE used 1.5 .
First project - no problem: New Seam Web Project->choosing JBOSS 4.2 as the deployment server, using all the default values until the last form. There i choose to create a new connection profile, setting it up properly (trying to ping, which works fine), after that, filling out the fields of Database Schema Name, Database Catalog Name and checking the DB Tables already exists checkbox.
After this step trying to SEAM GENERATE ENTITIES which works fine!
Second projet - no way to work: New Seam Web Project->choosing Glassfish as the deployment server and using all the default values until the last form. There i choose as connection profile the one from the previous project. Everything seems to work fine. After this step trying to SEAM GENERATE ENTITIES which DOES NOT WORK AT ALL!!!
The error i get is:
Can't generate seam entities
org.hibernate.console.HibernateConsoleRuntimeException: Problems while loading database driverclass (com.mysql.jdbc.Driver)
Problems while loading database driverclass (com.mysql.jdbc.Driver)
org.hibernate.console.HibernateConsoleRuntimeException: Problems while loading database driverclass (com.mysql.jdbc.Driver)
Problems while loading database driverclass (com.mysql.jdbc.Driver) java.lang.ClassNotFoundException: com.mysql.jdbc.Driver
com.mysql.jdbc.Driver
First i thought it has to do with the installation of Eclipse beeing somehow missconfigured (dont't know how!!). So i reinstalled a fresh Eclipse setup with all the stuff. Tried to create JBOSS based projects which worked fine. As soon as i tried to use Glassfish i got this error.
Does reverse engeneering not function with Glassfish selected? I searched JIRA but could not find anything similar to this.
MAAANY thanks in advance
ssopiadis
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177090#4177090
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177090
17 years, 10 months
[EJB 3.0] - Temporals and ON UPDATE CURRENT_TIMESTAMP
by ddennis
Hello there,
I have an entity bean with a field "dtupdated" that I would like to have
set to the current timestamp on each update of the dataset. It is annotated
the following way.
@Temporal(TemporalType.TIMESTAMP)
@Column(columnDefinition="TIMESTAMP ON UPDATE CURRENT_TIMESTAMP")
private Date dtupdated;
My DB is mySQL.
If I retrieve this entity bean from the DB now, make changes and write it back to the database, the dtupdated field will of course not be set to CURRENT_TIMESTAMP, because it's previous value will be explicitly passed in the UPDATE statement on the DB and CURRENT_TIMESTAMP is only set, if a NULL value is passed...
How can I create a field with the desired behaviour? Any good solutions out there?
Thanks a lot for your help -
Dennis
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177086#4177086
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177086
17 years, 10 months
[Beginners Corner] - Can't generate seam entities
by ssopiadis
Hi!
First of all apologize my realy bad english (i 'm greek) ... and my newbie understandnig of the SEAM-world (i 'm very new to this J2EE stuff).
My problem is realted to Eclipse 3.4, JBOSS Tools 3.0.0 Alpha and !!GLASSFISH!!
Had no problem with installing Eclipse, the (nightly build) of JBoss Tools (16/9/2008) into Eclipse (used dropin folder) and downloading and setting up Glassfish v2 driver and the application server. Setup of JBOSS 4.2.1GA into the framework worked also fine without any problem. MySQL driver was also setup, cause Eclipse seems to have problems finding the preconfigured driver.
JRE used 1.5 .
First project - no problem: New Seam Web Project->choosing JBOSS 4.2 as the deployment server, using all the default values until the last form. There i choose to create a new connection profile, setting it up properly (trying to ping, which works fine), after that, filling out the fields of Database Schema Name, Database Catalog Name and checking the DB Tables already exists checkbox.
After this step trying to SEAM GENERATE ENTITIES which works fine!
Second projet - no way to work: New Seam Web Project->choosing Glassfish as the deployment server and using all the default values until the last form. There i choose as connection profile the one from the previous project. Everything seems to work fine. After this step trying to SEAM GENERATE ENTITIES which DOES NOT WORK AT ALL!!!
The error i get is:
Can't generate seam entities
org.hibernate.console.HibernateConsoleRuntimeException: Problems while loading database driverclass (com.mysql.jdbc.Driver)
Problems while loading database driverclass (com.mysql.jdbc.Driver)
org.hibernate.console.HibernateConsoleRuntimeException: Problems while loading database driverclass (com.mysql.jdbc.Driver)
Problems while loading database driverclass (com.mysql.jdbc.Driver) java.lang.ClassNotFoundException: com.mysql.jdbc.Driver
com.mysql.jdbc.Driver
First i thought it has to do with the installation of Eclipse beeing somehow missconfigured (dont't know how!!). So i reinstalled a fresh Eclipse setup with all the stuff. Tried to create JBOSS based projects which worked fine. As soon as i tried to use Glassfish i got this error.
Does reverse engeneering not function with Glassfish selected? I searched JIRA but could not find anything similar to this.
MAAANY thanks in advance
ssopiadis
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177081#4177081
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177081
17 years, 10 months
[Installation, Configuration & DEPLOYMENT] - Re: Need suggestion about how to proceed.
by rks_86
"rks_86" wrote : Hi all,
|
| I'm migrating from websphere to JBoss 4.2.3GA.
| So i need help in deploying and configuring app in JBoss.
| JBoss server is deployed and running perfectly fine.
|
| What i do in Websphere.
| 1.I deploy the WAR file which contains only jar files.
| 2.I give Java Virtual Machine arguments in each server.
| JVM Args: -DMSM.HOME=/opt/MSM/SYSTEMi/Systemi -DMSM.CONFIG=/opt/MSM/Sys/Config/config.xml
| 3.I copy the resource folder to some location like opt/MSM/SYSTEMi/Systemi/Resource this folder contains all the html files and templates used for IBM HTTP Server.
| 4.Once i finished configuring httpd.conf file in HTTP server, i restart the App server and thats all deployment finished
|
| Note: Config.xml contains all the configuration parameters for MSMApp
| like hostname,webservice port number,jdbc details,etc.
| We use our connection pool to connect to oracle db.
|
| For Jboss what i did till now:
|
| 1.Installed JBoss in /opt/JBoss folder successfully. already set all the env varibales like JAVA_HOME,JBOSS_HOME,etc.
| 2.Copied WAR file to default/deploy folder
| 3.created Resouce folder where all HTML and templates resides.
| 4.In run.sh file exported one parameter JAVA_OPTS
| I have set JAVA_OPTS variable with all the java arguments i gave in Websphere.
| which is -DMSM.HOME=/opt/MSM/SYSTEMi/Systemi -DMSM.CONFIG=/opt/MSM/Sys/Config/config.xml
| 5.Restarted the server as parameter run.sh -c default -b 0.0.0.0
| 6.Server restarted successfully with out any errors.
| 7.In Jboss console Application list my application is showing up active and deployed.
| 8.But still I'm not able to view my application.
| 9.My application Url: http://localhost:8080/MSM/Userlogin
| 10.So after all these Please suggest me am i missing something which is required for configuration.
| (This much configuration works fine in Websphere.}
| AM deploying in Ent. Linux 4
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177075#4177075
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177075
17 years, 10 months
[Installation, Configuration & DEPLOYMENT] - Need suggestion about how to proceed.
by rks_86
Hi all,
I'm migrating from websphere to JBoss 4.2.3GA.
So i need help in deploying and configuring app in JBoss.
JBoss server is deployed and running perfectly fine.
What i do in Websphere.
1.I deploy the WAR file which contains only jar files.
2.I give Java Virtual Machine arguments in each server.
JVM Args: -DMSM.HOME=/opt/MSM/SYSTEMi/Systemi -DMSM.CONFIG=/opt/MSM/Sys/Config/config.xml
3.I copy the resource folder to some location like opt/MSM/SYSTEMi/Systemi/Resource this folder contains all the html files and templates used for IBM HTTP Server.
4.Once i finished configuring httpd.conf file in HTTP server, i restart the App server and thats all deployment finished
Note: Config.xml contains all the configuration parameters for MSMApp
like hostname,webservice port number,jdbc details,etc.
We use our connection pool to connect to oracle db.
For Jboss what i did till now:
1.Installed JBoss in /opt/JBoss folder successfully. already set all the env varibales like JAVA_HOME,JBOSS_HOME,etc.
2.Copied WAR file to default/deploy folder
3.created Resouce folder where all HTML and templates resides.
4.In run.sh file exported one parameter JAVA_OPTS
I have set JAVA_OPTS variable with all the java arguments i gave in Websphere.
which is -DMSM.HOME=/opt/MSM/SYSTEMi/Systemi -DMSM.CONFIG=/opt/MSM/Sys/Config/config.xml
5.Restarted the server as parameter run.sh -c default -b 0.0.0.0
6.Server restarted successfully with out any errors.
7.In Jboss console Application list my application is showing up active and deployed.
8.But still I'm not able to view my application.
9.My application Url: http://localhost:8080/MSM/Userlogin
10.So after all these Please suggest me am i missing something which is required for configuration.
(This much configuration works fine in Websphere.}
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177072#4177072
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177072
17 years, 10 months
[Installation, Configuration & DEPLOYMENT] - Re: Can't run jboss-4.2.3.GA
by M.allam
The folder is jdk6
Server.log
| 2008-09-17 23:04:05,562 DEBUG [org.jboss.logging.Log4jService] Installed System.out adapter
| 2008-09-17 23:04:05,562 DEBUG [org.jboss.logging.Log4jService] Installed System.err adapter
| 2008-09-17 23:04:05,578 DEBUG [org.jboss.logging.Log4jService] Added ThrowableListener: org.jboss.logging.Log4jService$ThrowableListenerLoggingAdapter@1e78c96
| 2008-09-17 23:04:05,578 DEBUG [org.jboss.logging.Log4jService] Created jboss.system:type=Log4jService,service=Logging
| 2008-09-17 23:04:05,578 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.system:type=Log4jService,service=Logging dependents are: []
| 2008-09-17 23:04:05,578 DEBUG [org.jboss.system.ServiceController] Creating service jboss.rmi:type=RMIClassLoader
| 2008-09-17 23:04:05,578 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.rmi:type=RMIClassLoader dependents are: []
| 2008-09-17 23:04:05,578 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=WebService
| 2008-09-17 23:04:05,578 DEBUG [org.jboss.system.ServiceController] Ignoring create request for service: jboss:service=WebService
| 2008-09-17 23:04:05,578 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=NamingBeanImpl
| 2008-09-17 23:04:05,578 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss:service=NamingBeanImpl dependents are: [ObjectName: jboss:service=Naming
| State: CONFIGURED
| I Depend On:
| jboss.system:service=ThreadPool
| jboss:service=NamingBeanImpl
| ]
| 2008-09-17 23:04:05,578 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=Naming
| 2008-09-17 23:04:05,578 DEBUG [org.jboss.naming.NamingService] Creating jboss:service=Naming
| 2008-09-17 23:04:05,578 DEBUG [org.jboss.naming.NamingService] Created jboss:service=Naming
| 2008-09-17 23:04:05,593 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss:service=Naming dependents are: []
| 2008-09-17 23:04:05,593 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=Naming
| 2008-09-17 23:04:05,593 DEBUG [org.jboss.system.ServiceController] Ignoring create request for service: jboss:service=Naming
| 2008-09-17 23:04:05,593 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=JNDIView
| 2008-09-17 23:04:05,593 DEBUG [org.jboss.naming.JNDIView] Creating jboss:service=JNDIView
| 2008-09-17 23:04:05,593 DEBUG [org.jboss.naming.JNDIView] Created jboss:service=JNDIView
| 2008-09-17 23:04:05,593 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss:service=JNDIView dependents are: []
| 2008-09-17 23:04:05,593 DEBUG [org.jboss.system.ServiceController] Creating service jboss.security:service=SecurityConfig
| 2008-09-17 23:04:05,593 DEBUG [org.jboss.security.plugins.SecurityConfig] Creating jboss.security:service=SecurityConfig
| 2008-09-17 23:04:05,593 DEBUG [org.jboss.security.plugins.SecurityConfig] Created jboss.security:service=SecurityConfig
| 2008-09-17 23:04:05,593 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.security:service=SecurityConfig dependents are: []
| 2008-09-17 23:04:05,593 DEBUG [org.jboss.system.ServiceController] Creating service jboss.security:service=XMLLoginConfig
| 2008-09-17 23:04:05,593 DEBUG [org.jboss.security.auth.login.XMLLoginConfig] Creating jboss.security:service=XMLLoginConfig
| 2008-09-17 23:04:05,593 DEBUG [org.jboss.security.auth.login.XMLLoginConfig] Created jboss.security:service=XMLLoginConfig
| 2008-09-17 23:04:05,593 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.security:service=XMLLoginConfig dependents are: []
| 2008-09-17 23:04:05,593 DEBUG [org.jboss.system.ServiceController] Creating service jboss.security:service=JaasSecurityManager
| 2008-09-17 23:04:05,593 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] Creating jboss.security:service=JaasSecurityManager
| 2008-09-17 23:04:05,593 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] Created jboss.security:service=JaasSecurityManager
| 2008-09-17 23:04:05,593 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.security:service=JaasSecurityManager dependents are: []
| 2008-09-17 23:04:05,593 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=XidFactory
| 2008-09-17 23:04:05,593 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss:service=XidFactory dependents are: []
| 2008-09-17 23:04:05,593 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=TransactionManager
| 2008-09-17 23:04:05,593 DEBUG [com.arjuna.ats.jbossatx.jta.TransactionManagerService] Creating jboss:service=TransactionManager
| 2008-09-17 23:04:05,593 DEBUG [com.arjuna.ats.jbossatx.jta.TransactionManagerService] Created jboss:service=TransactionManager
| 2008-09-17 23:04:05,656 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss:service=TransactionManager dependents are: [ObjectName: jboss:service=invoker,type=unified
| State: CONFIGURED
| I Depend On:
| jboss:service=TransactionManager
| jboss.remoting:service=Connector,transport=socket
| Depends On Me:
| jboss:service=proxyFactory,target=ClientUserTransactionFactory
| jboss:service=proxyFactory,target=ClientUserTransaction
| , ObjectName: jboss:service=invoker,type=jrmp
| State: CONFIGURED
| I Depend On:
| jboss:service=TransactionManager
| , ObjectName: jboss:service=invoker,type=local
| State: CONFIGURED
| I Depend On:
| jboss:service=TransactionManager
| , ObjectName: jboss:service=invoker,type=pooled
| State: CONFIGURED
| I Depend On:
| jboss:service=TransactionManager
| ]
| 2008-09-17 23:04:05,656 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=invoker,type=unified
| 2008-09-17 23:04:05,656 DEBUG [org.jboss.system.ServiceController] waiting in create of jboss:service=invoker,type=unified waiting on jboss.remoting:service=Connector,transport=socket
| 2008-09-17 23:04:05,656 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=invoker,type=jrmp
| 2008-09-17 23:04:05,656 DEBUG [org.jboss.invocation.jrmp.server.JRMPInvoker] Creating jboss:service=invoker,type=jrmp
| 2008-09-17 23:04:05,656 DEBUG [org.jboss.invocation.jrmp.server.JRMPInvoker] Created jboss:service=invoker,type=jrmp
| 2008-09-17 23:04:05,656 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss:service=invoker,type=jrmp dependents are: []
| 2008-09-17 23:04:05,656 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=invoker,type=local
| 2008-09-17 23:04:05,656 DEBUG [org.jboss.invocation.local.LocalInvoker] Creating jboss:service=invoker,type=local
| 2008-09-17 23:04:05,671 DEBUG [org.jboss.invocation.local.LocalInvoker] Created jboss:service=invoker,type=local
| 2008-09-17 23:04:05,671 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss:service=invoker,type=local dependents are: []
| 2008-09-17 23:04:05,671 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=invoker,type=pooled
| 2008-09-17 23:04:05,671 DEBUG [org.jboss.invocation.pooled.server.PooledInvoker] Creating jboss:service=invoker,type=pooled
| 2008-09-17 23:04:05,671 DEBUG [org.jboss.invocation.pooled.server.PooledInvoker] Created jboss:service=invoker,type=pooled
| 2008-09-17 23:04:05,671 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss:service=invoker,type=pooled dependents are: []
| 2008-09-17 23:04:05,671 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=ClientUserTransaction
| 2008-09-17 23:04:05,671 DEBUG [org.jboss.system.ServiceController] waiting in create of jboss:service=ClientUserTransaction waiting on jboss:service=proxyFactory,target=ClientUserTransactionFactory
| 2008-09-17 23:04:05,671 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=proxyFactory,target=ClientUserTransactionFactory
| 2008-09-17 23:04:05,671 DEBUG [org.jboss.system.ServiceController] waiting in create of jboss:service=proxyFactory,target=ClientUserTransactionFactory waiting on jboss:service=invoker,type=unified
| 2008-09-17 23:04:05,671 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=proxyFactory,target=ClientUserTransaction
| 2008-09-17 23:04:05,671 DEBUG [org.jboss.system.ServiceController] waiting in create of jboss:service=proxyFactory,target=ClientUserTransaction waiting on jboss:service=invoker,type=unified
| 2008-09-17 23:04:05,671 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=invoker,type=unified
| 2008-09-17 23:04:05,671 DEBUG [org.jboss.system.ServiceController] waiting in create of jboss:service=invoker,type=unified waiting on jboss.remoting:service=Connector,transport=socket
| 2008-09-17 23:04:05,671 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=invoker,type=jrmp
| 2008-09-17 23:04:05,671 DEBUG [org.jboss.system.ServiceController] Ignoring create request for service: jboss:service=invoker,type=jrmp
| 2008-09-17 23:04:05,671 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=invoker,type=local
| 2008-09-17 23:04:05,671 DEBUG [org.jboss.system.ServiceController] Ignoring create request for service: jboss:service=invoker,type=local
| 2008-09-17 23:04:05,671 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=invoker,type=pooled
| 2008-09-17 23:04:05,671 DEBUG [org.jboss.system.ServiceController] Ignoring create request for service: jboss:service=invoker,type=pooled
| 2008-09-17 23:04:05,687 DEBUG [org.jboss.system.ServiceController] Creating service jboss.remoting:service=NetworkRegistry
| 2008-09-17 23:04:05,687 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.remoting:service=NetworkRegistry dependents are: [ObjectName: jboss.remoting:service=Connector,transport=socket
| State: CONFIGURED
| I Depend On:
| jboss.remoting:service=NetworkRegistry
| Depends On Me:
| jboss:service=invoker,type=unified
| ]
| 2008-09-17 23:04:05,687 DEBUG [org.jboss.system.ServiceController] Creating service jboss.remoting:service=Connector,transport=socket
| 2008-09-17 23:04:05,750 DEBUG [org.jboss.remoting.ServerInvoker] SocketServerInvoker[UNINITIALIZED] did not find server socket factory configuration as mbean service or classname. Creating default server socket factory.
| 2008-09-17 23:04:05,750 DEBUG [org.jboss.remoting.ServerInvoker] SocketServerInvoker[UNINITIALIZED] created server socket factory javax.net.DefaultServerSocketFactory@dc41c5
| 2008-09-17 23:04:05,765 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.remoting:service=Connector,transport=socket dependents are: [ObjectName: jboss:service=invoker,type=unified
| State: CONFIGURED
| I Depend On:
| jboss:service=TransactionManager
| jboss.remoting:service=Connector,transport=socket
| Depends On Me:
| jboss:service=proxyFactory,target=ClientUserTransactionFactory
| jboss:service=proxyFactory,target=ClientUserTransaction
| ]
| 2008-09-17 23:04:05,765 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=invoker,type=unified
| 2008-09-17 23:04:05,765 DEBUG [org.jboss.invocation.unified.server.UnifiedInvoker] Creating jboss:service=invoker,type=unified
| 2008-09-17 23:04:05,765 DEBUG [org.jboss.invocation.unified.server.UnifiedInvoker] Created jboss:service=invoker,type=unified
| 2008-09-17 23:04:05,765 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss:service=invoker,type=unified dependents are: [ObjectName: jboss:service=proxyFactory,target=ClientUserTransactionFactory
| State: CONFIGURED
| I Depend On:
| jboss:service=invoker,type=unified
| Depends On Me:
| jboss:service=ClientUserTransaction
| , ObjectName: jboss:service=proxyFactory,target=ClientUserTransaction
| State: CONFIGURED
| I Depend On:
| jboss:service=invoker,type=unified
| Depends On Me:
| jboss:service=ClientUserTransaction
| ]
| 2008-09-17 23:04:05,765 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=proxyFactory,target=ClientUserTransactionFactory
| 2008-09-17 23:04:05,765 DEBUG [org.jboss.invocation.jrmp.server.JRMPProxyFactory] Creating jboss:service=proxyFactory,target=ClientUserTransactionFactory
| 2008-09-17 23:04:05,781 DEBUG [org.jboss.invocation.jrmp.server.JRMPProxyFactory] Created jboss:service=proxyFactory,target=ClientUserTransactionFactory
| 2008-09-17 23:04:05,781 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss:service=proxyFactory,target=ClientUserTransactionFactory dependents are: [ObjectName: jboss:service=ClientUserTransaction
| State: CONFIGURED
| I Depend On:
| jboss:service=proxyFactory,target=ClientUserTransactionFactory
| jboss:service=proxyFactory,target=ClientUserTransaction
| ]
| 2008-09-17 23:04:05,781 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=ClientUserTransaction
| 2008-09-17 23:04:05,781 DEBUG [org.jboss.system.ServiceController] waiting in create of jboss:service=ClientUserTransaction waiting on jboss:service=proxyFactory,target=ClientUserTransaction
| 2008-09-17 23:04:05,781 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=proxyFactory,target=ClientUserTransaction
| 2008-09-17 23:04:05,781 DEBUG [org.jboss.invocation.jrmp.server.JRMPProxyFactory] Creating jboss:service=proxyFactory,target=ClientUserTransaction
| 2008-09-17 23:04:05,781 DEBUG [org.jboss.invocation.jrmp.server.JRMPProxyFactory] Created jboss:service=proxyFactory,target=ClientUserTransaction
| 2008-09-17 23:04:05,781 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss:service=proxyFactory,target=ClientUserTransaction dependents are: [ObjectName: jboss:service=ClientUserTransaction
| State: CONFIGURED
| I Depend On:
| jboss:service=proxyFactory,target=ClientUserTransactionFactory
| jboss:service=proxyFactory,target=ClientUserTransaction
| ]
| 2008-09-17 23:04:05,781 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=ClientUserTransaction
| 2008-09-17 23:04:05,781 DEBUG [org.jboss.tm.usertx.server.ClientUserTransactionService] Creating jboss:service=ClientUserTransaction
| 2008-09-17 23:04:05,781 DEBUG [org.jboss.tm.usertx.server.ClientUserTransactionService] Created jboss:service=ClientUserTransaction
| 2008-09-17 23:04:05,781 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss:service=ClientUserTransaction dependents are: []
| 2008-09-17 23:04:05,781 DEBUG [org.jboss.system.ServiceController] Creating service jboss.remoting:service=Connector,transport=socket
| 2008-09-17 23:04:05,781 DEBUG [org.jboss.system.ServiceController] Ignoring create request for service: jboss.remoting:service=Connector,transport=socket
| 2008-09-17 23:04:05,781 DEBUG [org.jboss.system.ServiceController] Creating service jboss.jdbc:service=metadata
| 2008-09-17 23:04:05,781 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] Creating jboss.jdbc:service=metadata
| 2008-09-17 23:04:05,781 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] Created jboss.jdbc:service=metadata
| 2008-09-17 23:04:05,781 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.jdbc:service=metadata dependents are: []
| 2008-09-17 23:04:05,781 DEBUG [org.jboss.system.ServiceController] Creating service jboss.deployment:type=DeploymentScanner,flavor=URL
| 2008-09-17 23:04:05,781 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Creating jboss.deployment:type=DeploymentScanner,flavor=URL
| 2008-09-17 23:04:05,781 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Scanner thread started
| 2008-09-17 23:04:05,796 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Created jboss.deployment:type=DeploymentScanner,flavor=URL
| 2008-09-17 23:04:05,796 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.deployment:type=DeploymentScanner,flavor=URL dependents are: []
| 2008-09-17 23:04:05,796 DEBUG [org.jboss.deployment.MainDeployer] Done with create step of deploying jboss-service.xml
| 2008-09-17 23:04:05,796 DEBUG [org.jboss.deployment.MainDeployer] Begin deployment start file:/C:/jboss-4.2.3.GA/server/default/conf/jboss-service.xml
| 2008-09-17 23:04:05,796 DEBUG [org.jboss.deployment.SARDeployer] Deploying SAR, start step: url file:/C:/jboss-4.2.3.GA/server/default/conf/jboss-service.xml
| 2008-09-17 23:04:05,796 DEBUG [org.jboss.system.ServiceController] starting service jboss.management.local:j2eeType=J2EEDomain,name=Manager
| 2008-09-17 23:04:05,796 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.management.local:j2eeType=J2EEDomain,name=Manager dependent components: []
| 2008-09-17 23:04:05,796 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=AttributePersistenceService
| 2008-09-17 23:04:05,796 DEBUG [org.jboss.system.pm.AttributePersistenceService] Starting jboss:service=AttributePersistenceService
| 2008-09-17 23:04:05,796 DEBUG [org.jboss.system.pm.XMLAttributePersistenceManager] Constructed
| 2008-09-17 23:04:05,796 DEBUG [org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread] Running
| 2008-09-17 23:04:05,796 DEBUG [org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread] Disabled, waiting for notification
| 2008-09-17 23:04:05,796 DEBUG [org.jboss.system.pm.XMLAttributePersistenceManager] Using data directory: C:\jboss-4.2.3.GA\server\default\data\xmbean-attrs
| 2008-09-17 23:04:05,796 DEBUG [org.jboss.system.pm.AttributePersistenceService] Started jboss:service=AttributePersistenceService
| 2008-09-17 23:04:05,796 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss:service=AttributePersistenceService dependent components: []
| 2008-09-17 23:04:05,796 DEBUG [org.jboss.system.ServiceController] starting service jboss.system:service=ThreadPool
| 2008-09-17 23:04:05,796 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.system:service=ThreadPool dependent components: [ObjectName: jboss:service=WebService
| State: CREATED
| I Depend On:
| jboss.system:service=ThreadPool
| , ObjectName: jboss:service=Naming
| State: CREATED
| I Depend On:
| jboss.system:service=ThreadPool
| jboss:service=NamingBeanImpl
| ]
| 2008-09-17 23:04:05,796 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=WebService
| 2008-09-17 23:04:05,796 DEBUG [org.jboss.web.WebService] Starting jboss:service=WebService
| 2008-09-17 23:04:05,796 DEBUG [org.jboss.web.WebServer] Started server: ServerSocket[addr=/127.0.0.1,port=0,localport=8083]
| 2008-09-17 23:04:05,812 DEBUG [org.jboss.web.WebService] Started WebServer with address: /127.0.0.1:8083
| 2008-09-17 23:04:05,812 DEBUG [org.jboss.web.WebService] Started jboss:service=WebService
| 2008-09-17 23:04:05,812 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss:service=WebService dependent components: []
| 2008-09-17 23:04:05,812 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=Naming
| 2008-09-17 23:04:05,812 DEBUG [org.jboss.system.ServiceController] waiting in start jboss:service=Naming on jboss:service=NamingBeanImpl
| 2008-09-17 23:04:05,812 DEBUG [org.jboss.system.ServiceController] starting service jboss.system:type=Log4jService,service=Logging
| 2008-09-17 23:04:05,812 DEBUG [org.jboss.logging.Log4jService] Starting jboss.system:type=Log4jService,service=Logging
| 2008-09-17 23:04:05,812 DEBUG [org.jboss.logging.Log4jService] Started jboss.system:type=Log4jService,service=Logging
| 2008-09-17 23:04:05,812 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.system:type=Log4jService,service=Logging dependent components: []
| 2008-09-17 23:04:05,812 DEBUG [org.jboss.system.ServiceController] starting service jboss.rmi:type=RMIClassLoader
| 2008-09-17 23:04:05,812 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.rmi:type=RMIClassLoader dependent components: []
| 2008-09-17 23:04:05,812 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=WebService
| 2008-09-17 23:04:05,812 DEBUG [org.jboss.system.ServiceController] Ignoring start request for service: jboss:service=WebService
| 2008-09-17 23:04:05,812 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=NamingBeanImpl
| 2008-09-17 23:04:05,828 DEBUG [org.jnp.server.NamingBeanImpl] Using NamingServer: org.jnp.server.NamingServer@dada24
| 2008-09-17 23:04:05,828 DEBUG [org.jnp.server.NamingBeanImpl] Installed global NamingServer: org.jnp.server.NamingServer@dada24
| 2008-09-17 23:04:05,828 DEBUG [org.jnp.server.NamingBeanImpl] InitialContext Environment:
| 2008-09-17 23:04:05,828 DEBUG [org.jnp.server.NamingBeanImpl] key=java.naming.factory.initial, value(java.lang.String)=org.jnp.interfaces.NamingContextFactory
| 2008-09-17 23:04:05,828 DEBUG [org.jnp.server.NamingBeanImpl] key=java.naming.factory.url.pkgs, value(java.lang.String)=org.jboss.naming:org.jnp.interfaces
| 2008-09-17 23:04:05,828 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss:service=NamingBeanImpl dependent components: [ObjectName: jboss:service=Naming
| State: CREATED
| I Depend On:
| jboss.system:service=ThreadPool
| jboss:service=NamingBeanImpl
| ]
| 2008-09-17 23:04:05,828 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=Naming
| 2008-09-17 23:04:05,828 DEBUG [org.jboss.naming.NamingService] Starting jboss:service=Naming
| 2008-09-17 23:04:05,828 DEBUG [org.jboss.naming.NamingService] System.setProperty, key=java.naming.factory.initial, value=org.jnp.interfaces.NamingContextFactory
| 2008-09-17 23:04:05,828 DEBUG [org.jboss.naming.NamingService] System.setProperty, key=java.naming.factory.url.pkgs, value=org.jboss.naming:org.jnp.interfaces
| 2008-09-17 23:04:05,828 DEBUG [org.jboss.naming.Naming] Creating NamingServer stub, theServer=MBeanProxyExt[jboss:service=NamingBeanImpl],rmiPort=1098,clientSocketFactory=null,serverSocketFactory=org.jboss.net.sockets.DefaultSocketFactory@e048aaa4[bindAddress=/127.0.0.1]
| 2008-09-17 23:04:05,890 DEBUG [org.jboss.naming.Naming] NamingServer stub: NamingServer_Stub[UnicastRef2 [liveRef: [endpoint:[127.0.0.1:1098,org.jboss.net.sockets.DefaultSocketFactory@e048aaa4[bindAddress=/127.0.0.1]](local),objID:[0]]]]
| 2008-09-17 23:04:05,906 DEBUG [org.jboss.naming.Naming] JNDI bootstrap JNP=/127.0.0.1:1099, RMI=/127.0.0.1:1098, backlog=50, no client SocketFactory, Server SocketFactory=org.jboss.net.sockets.DefaultSocketFactory(a)e048aaa4[bindAddress=/127.0.0.1]
| 2008-09-17 23:04:05,906 DEBUG [org.jboss.naming.NamingService] Started jboss:service=Naming
| 2008-09-17 23:04:05,906 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss:service=Naming dependent components: []
| 2008-09-17 23:04:05,906 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=Naming
| 2008-09-17 23:04:05,906 DEBUG [org.jboss.system.ServiceController] Ignoring start request for service: jboss:service=Naming
| 2008-09-17 23:04:05,906 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=JNDIView
| 2008-09-17 23:04:05,906 DEBUG [org.jboss.naming.JNDIView] Starting jboss:service=JNDIView
| 2008-09-17 23:04:05,906 DEBUG [org.jboss.naming.JNDIView] Started jboss:service=JNDIView
| 2008-09-17 23:04:05,906 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss:service=JNDIView dependent components: []
| 2008-09-17 23:04:05,906 DEBUG [org.jboss.system.ServiceController] starting service jboss.security:service=SecurityConfig
| 2008-09-17 23:04:05,906 DEBUG [org.jboss.security.plugins.SecurityConfig] Starting jboss.security:service=SecurityConfig
| 2008-09-17 23:04:05,906 DEBUG [org.jboss.security.plugins.SecurityConfig] Installed JAAS Configuration service=jboss.security:service=XMLLoginConfig, config=org.jboss.security.auth.login.XMLLoginConfigImpl@c68a98
| 2008-09-17 23:04:05,906 DEBUG [org.jboss.security.plugins.SecurityConfig] Started jboss.security:service=SecurityConfig
| 2008-09-17 23:04:05,906 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.security:service=SecurityConfig dependent components: []
| 2008-09-17 23:04:05,906 DEBUG [org.jboss.system.ServiceController] starting service jboss.security:service=XMLLoginConfig
| 2008-09-17 23:04:05,906 DEBUG [org.jboss.security.auth.login.XMLLoginConfig] Starting jboss.security:service=XMLLoginConfig
| 2008-09-17 23:04:05,921 DEBUG [org.jboss.security.auth.login.XMLLoginConfigImpl] Try loading config as XML, url=file:/C:/jboss-4.2.3.GA/server/default/conf/login-config.xml
| 2008-09-17 23:04:05,968 DEBUG [org.jboss.security.auth.login.XMLLoginConfig] Started jboss.security:service=XMLLoginConfig
| 2008-09-17 23:04:05,968 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.security:service=XMLLoginConfig dependent components: []
| 2008-09-17 23:04:05,968 DEBUG [org.jboss.system.ServiceController] starting service jboss.security:service=JaasSecurityManager
| 2008-09-17 23:04:05,968 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] Starting jboss.security:service=JaasSecurityManager
| 2008-09-17 23:04:05,984 DEBUG [org.jboss.security.SecurityAssociation] Using ThreadLocal: false
| 2008-09-17 23:04:05,984 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] securityMgrCtxPath=java:/jaas
| 2008-09-17 23:04:05,984 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] cachePolicyCtxPath=java:/timedCacheFactory
| 2008-09-17 23:04:05,984 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] SecurityProxyFactory=org.jboss.security.SubjectSecurityProxyFactory@1ed5459
| 2008-09-17 23:04:06,000 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] Registered PrincipalEditor, SecurityDomainEditor
| 2008-09-17 23:04:06,000 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] ServerMode=true
| 2008-09-17 23:04:06,000 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] SecurityMgrClass=class org.jboss.security.plugins.JaasSecurityManager
| 2008-09-17 23:04:06,000 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] CallbackHandlerClass=class org.jboss.security.auth.callback.SecurityAssociationHandler
| 2008-09-17 23:04:06,000 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] Started jboss.security:service=JaasSecurityManager
| 2008-09-17 23:04:06,000 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.security:service=JaasSecurityManager dependent components: []
| 2008-09-17 23:04:06,000 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=XidFactory
| 2008-09-17 23:04:06,000 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss:service=XidFactory dependent components: []
| 2008-09-17 23:04:06,000 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=TransactionManager
| 2008-09-17 23:04:06,000 DEBUG [com.arjuna.ats.jbossatx.jta.TransactionManagerService] Starting jboss:service=TransactionManager
| 2008-09-17 23:04:06,000 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
| 2008-09-17 23:04:06,000 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] Setting up property manager MBean and JMX layer
| 2008-09-17 23:04:06,140 DEBUG [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.recovery.TransactionStatusManager_1] - Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 1421
| 2008-09-17 23:04:06,140 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] TransactionStatusManagerItem - host: 192.168.1.49 port: 1421
| 2008-09-17 23:04:06,171 DEBUG [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.recovery.TransactionStatusManager_3] - TransactionStatusManager started on port 1421 with service com.arjuna.ats.arjuna.recovery.ActionStatusService
| 2008-09-17 23:04:06,171 DEBUG [com.arjuna.ats.tsmx.logging.tsmxLogger] Registering mbean for module 'arjuna'
| 2008-09-17 23:04:06,187 DEBUG [com.arjuna.ats.tsmx.logging.tsmxLogger] Initialising JMX agent com.arjuna.ats.internal.jbossatx.agent.LocalJBossAgentImpl
| 2008-09-17 23:04:06,187 DEBUG [com.arjuna.ats.tsmx.logging.tsmxLogger] Registering mbean for module 'txoj'
| 2008-09-17 23:04:06,187 DEBUG [com.arjuna.ats.tsmx.logging.tsmxLogger] Registering mbean for module 'jta'
| 2008-09-17 23:04:06,234 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] Starting recovery manager
| 2008-09-17 23:04:06,250 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger]
| --- Start RecoveryActivators
| 2008-09-17 23:04:06,250 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger]
| --- ExpiredEntryMonitor ----Wed, 17 Sep 2008 23:04:06----
| 2008-09-17 23:04:06,406 DEBUG [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.recovery.noxanodes] No XA recovery nodes specified. Will only recover saved states.
| 2008-09-17 23:04:06,421 DEBUG [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.internal.arjuna.recovery.ready] RecoveryManagerImple is ready on port 1,424
| 2008-09-17 23:04:06,421 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] Recovery manager started
| 2008-09-17 23:04:06,421 INFO [com.arjuna.ats.jbossatx.jta.TransactionManagerService] Binding TransactionManager JNDI Reference
| 2008-09-17 23:04:06,437 DEBUG [com.arjuna.ats.jbossatx.jta.TransactionManagerService] Started jboss:service=TransactionManager
| 2008-09-17 23:04:06,437 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss:service=TransactionManager dependent components: [ObjectName: jboss:service=invoker,type=unified
| State: CREATED
| I Depend On:
| jboss:service=TransactionManager
| jboss.remoting:service=Connector,transport=socket
| Depends On Me:
| jboss:service=proxyFactory,target=ClientUserTransactionFactory
| jboss:service=proxyFactory,target=ClientUserTransaction
| , ObjectName: jboss:service=invoker,type=jrmp
| State: CREATED
| I Depend On:
| jboss:service=TransactionManager
| , ObjectName: jboss:service=invoker,type=local
| State: CREATED
| I Depend On:
| jboss:service=TransactionManager
| , ObjectName: jboss:service=invoker,type=pooled
| State: CREATED
| I Depend On:
| jboss:service=TransactionManager
| ]
| 2008-09-17 23:04:06,437 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=invoker,type=unified
| 2008-09-17 23:04:06,437 DEBUG [org.jboss.system.ServiceController] waiting in start jboss:service=invoker,type=unified on jboss.remoting:service=Connector,transport=socket
| 2008-09-17 23:04:06,437 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=invoker,type=jrmp
| 2008-09-17 23:04:06,437 DEBUG [org.jboss.invocation.jrmp.server.JRMPInvoker] Starting jboss:service=invoker,type=jrmp
| 2008-09-17 23:04:06,437 DEBUG [org.jboss.invocation.jrmp.server.JRMPInvoker] RMI Port='4444'
| 2008-09-17 23:04:06,437 DEBUG [org.jboss.invocation.jrmp.server.JRMPInvoker] Client SocketFactory='Default'
| 2008-09-17 23:04:06,437 DEBUG [org.jboss.invocation.jrmp.server.JRMPInvoker] Server SocketFactory='org.jboss.net.sockets.DefaultSocketFactory(a)e048aaa4[bindAddress=/127.0.0.1]'
| 2008-09-17 23:04:06,437 DEBUG [org.jboss.invocation.jrmp.server.JRMPInvoker] Server SocketAddr='127.0.0.1'
| 2008-09-17 23:04:06,437 DEBUG [org.jboss.invocation.jrmp.server.JRMPInvoker] SecurityDomain='Default'
| 2008-09-17 23:04:06,453 DEBUG [org.jboss.invocation.jrmp.server.JRMPInvoker] Bound JRMP invoker for JMX node
| 2008-09-17 23:04:06,453 DEBUG [org.jboss.invocation.jrmp.server.JRMPInvoker] Started jboss:service=invoker,type=jrmp
| 2008-09-17 23:04:06,453 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss:service=invoker,type=jrmp dependent components: []
| 2008-09-17 23:04:06,453 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=invoker,type=local
| 2008-09-17 23:04:06,453 DEBUG [org.jboss.invocation.local.LocalInvoker] Starting jboss:service=invoker,type=local
| 2008-09-17 23:04:06,453 DEBUG [org.jboss.invocation.local.LocalInvoker] Local invoker for JMX node started
| 2008-09-17 23:04:06,453 DEBUG [org.jboss.invocation.local.LocalInvoker] Started jboss:service=invoker,type=local
| 2008-09-17 23:04:06,453 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss:service=invoker,type=local dependent components: []
| 2008-09-17 23:04:06,453 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=invoker,type=pooled
| 2008-09-17 23:04:06,453 DEBUG [org.jboss.invocation.pooled.server.PooledInvoker] Starting jboss:service=invoker,type=pooled
| 2008-09-17 23:04:06,468 DEBUG [org.jboss.invocation.pooled.server.PooledInvoker] Bound invoker for JMX node
| 2008-09-17 23:04:06,468 DEBUG [org.jboss.invocation.pooled.server.PooledInvoker] Started jboss:service=invoker,type=pooled
| 2008-09-17 23:04:06,468 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss:service=invoker,type=pooled dependent components: []
| 2008-09-17 23:04:06,468 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=ClientUserTransaction
| 2008-09-17 23:04:06,468 DEBUG [org.jboss.system.ServiceController] waiting in start jboss:service=ClientUserTransaction on jboss:service=proxyFactory,target=ClientUserTransactionFactory
| 2008-09-17 23:04:06,468 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=proxyFactory,target=ClientUserTransactionFactory
| 2008-09-17 23:04:06,468 DEBUG [org.jboss.system.ServiceController] waiting in start jboss:service=proxyFactory,target=ClientUserTransactionFactory on jboss:service=invoker,type=unified
| 2008-09-17 23:04:06,468 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=proxyFactory,target=ClientUserTransaction
| 2008-09-17 23:04:06,468 DEBUG [org.jboss.system.ServiceController] waiting in start jboss:service=proxyFactory,target=ClientUserTransaction on jboss:service=invoker,type=unified
| 2008-09-17 23:04:06,468 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=invoker,type=unified
| 2008-09-17 23:04:06,468 DEBUG [org.jboss.system.ServiceController] waiting in start jboss:service=invoker,type=unified on jboss.remoting:service=Connector,transport=socket
| 2008-09-17 23:04:06,468 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=invoker,type=jrmp
| 2008-09-17 23:04:06,468 DEBUG [org.jboss.system.ServiceController] Ignoring start request for service: jboss:service=invoker,type=jrmp
| 2008-09-17 23:04:06,468 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=invoker,type=local
| 2008-09-17 23:04:06,468 DEBUG [org.jboss.system.ServiceController] Ignoring start request for service: jboss:service=invoker,type=local
| 2008-09-17 23:04:06,468 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=invoker,type=pooled
| 2008-09-17 23:04:06,468 DEBUG [org.jboss.system.ServiceController] Ignoring start request for service: jboss:service=invoker,type=pooled
| 2008-09-17 23:04:06,468 DEBUG [org.jboss.system.ServiceController] starting service jboss.remoting:service=NetworkRegistry
| 2008-09-17 23:04:06,468 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.remoting:service=NetworkRegistry dependent components: [ObjectName: jboss.remoting:service=Connector,transport=socket
| State: CREATED
| I Depend On:
| jboss.remoting:service=NetworkRegistry
| Depends On Me:
| jboss:service=invoker,type=unified
| ]
| 2008-09-17 23:04:06,468 DEBUG [org.jboss.system.ServiceController] starting service jboss.remoting:service=Connector,transport=socket
| 2008-09-17 23:04:06,468 DEBUG [org.jboss.remoting.ServerInvoker] SocketServerInvoker[UNINITIALIZED] added org.jboss.invocation.unified.server.UnifiedInvoker@9c82f4 for subsystem 'invoker'
| 2008-09-17 23:04:06,468 DEBUG [org.jboss.remoting.transport.socket.SocketServerInvoker] SocketServerInvoker[UNINITIALIZED] starting
| 2008-09-17 23:04:06,484 DEBUG [org.jboss.remoting.ServerInvoker] SocketServerInvoker[127.0.0.1:4446] started for locator InvokerLocator [socket://127.0.0.1:4446/?dataType=invocation&enableTcpNoDelay=true&marshaller=org.jboss.invocation.unified.marshall.InvocationMarshaller&socketTimeout=600000&unmarshaller=org.jboss.invocation.unified.marshall.InvocationUnMarshaller]
| 2008-09-17 23:04:06,484 DEBUG [org.jboss.remoting.transport.socket.SocketServerInvoker] SocketServerInvoker[127.0.0.1:4446] started
| 2008-09-17 23:04:06,484 DEBUG [org.jboss.remoting.transport.Connector] org.jboss.remoting.transport.Connector@caf0ed started
| 2008-09-17 23:04:06,484 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.remoting:service=Connector,transport=socket dependent components: [ObjectName: jboss:service=invoker,type=unified
| State: CREATED
| I Depend On:
| jboss:service=TransactionManager
| jboss.remoting:service=Connector,transport=socket
| Depends On Me:
| jboss:service=proxyFactory,target=ClientUserTransactionFactory
| jboss:service=proxyFactory,target=ClientUserTransaction
| ]
| 2008-09-17 23:04:06,484 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=invoker,type=unified
| 2008-09-17 23:04:06,484 DEBUG [org.jboss.invocation.unified.server.UnifiedInvoker] Starting jboss:service=invoker,type=unified
| 2008-09-17 23:04:06,484 DEBUG [org.jboss.invocation.unified.server.UnifiedInvoker] Starting unified invoker service.
| 2008-09-17 23:04:06,484 DEBUG [org.jboss.invocation.unified.server.UnifiedInvoker] Started jboss:service=invoker,type=unified
| 2008-09-17 23:04:06,484 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss:service=invoker,type=unified dependent components: [ObjectName: jboss:service=proxyFactory,target=ClientUserTransactionFactory
| State: CREATED
| I Depend On:
| jboss:service=invoker,type=unified
| Depends On Me:
| jboss:service=ClientUserTransaction
| , ObjectName: jboss:service=proxyFactory,target=ClientUserTransaction
| State: CREATED
| I Depend On:
| jboss:service=invoker,type=unified
| Depends On Me:
| jboss:service=ClientUserTransaction
| ]
| 2008-09-17 23:04:06,484 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=proxyFactory,target=ClientUserTransactionFactory
| 2008-09-17 23:04:06,484 DEBUG [org.jboss.invocation.jrmp.server.JRMPProxyFactory] Starting jboss:service=proxyFactory,target=ClientUserTransactionFactory
| 2008-09-17 23:04:06,500 DEBUG [org.jboss.invocation.jrmp.server.JRMPProxyFactory] Created JRMPPRoxy for service=jboss:service=ClientUserTransaction, nameHash=-2097396599, invoker=jboss:service=invoker,type=unified
| 2008-09-17 23:04:06,515 DEBUG [org.jboss.invocation.jrmp.server.JRMPProxyFactory] Bound proxy under jndiName=UserTransactionSessionFactory
| 2008-09-17 23:04:06,515 DEBUG [org.jboss.invocation.jrmp.server.JRMPProxyFactory] Started jboss:service=proxyFactory,target=ClientUserTransactionFactory
| 2008-09-17 23:04:06,531 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss:service=proxyFactory,target=ClientUserTransactionFactory dependent components: [ObjectName: jboss:service=ClientUserTransaction
| State: CREATED
| I Depend On:
| jboss:service=proxyFactory,target=ClientUserTransactionFactory
| jboss:service=proxyFactory,target=ClientUserTransaction
| ]
| 2008-09-17 23:04:06,531 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=ClientUserTransaction
| 2008-09-17 23:04:06,531 DEBUG [org.jboss.system.ServiceController] waiting in start jboss:service=ClientUserTransaction on jboss:service=proxyFactory,target=ClientUserTransaction
| 2008-09-17 23:04:06,531 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=proxyFactory,target=ClientUserTransaction
| 2008-09-17 23:04:06,531 DEBUG [org.jboss.invocation.jrmp.server.JRMPProxyFactory] Starting jboss:service=proxyFactory,target=ClientUserTransaction
| 2008-09-17 23:04:06,531 DEBUG [org.jboss.invocation.jrmp.server.JRMPProxyFactory] Created JRMPPRoxy for service=jboss:service=ClientUserTransaction, nameHash=2024786241, invoker=jboss:service=invoker,type=unified
| 2008-09-17 23:04:06,531 DEBUG [org.jboss.invocation.jrmp.server.JRMPProxyFactory] Started jboss:service=proxyFactory,target=ClientUserTransaction
| 2008-09-17 23:04:06,531 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss:service=proxyFactory,target=ClientUserTransaction dependent components: [ObjectName: jboss:service=ClientUserTransaction
| State: CREATED
| I Depend On:
| jboss:service=proxyFactory,target=ClientUserTransactionFactory
| jboss:service=proxyFactory,target=ClientUserTransaction
| ]
| 2008-09-17 23:04:06,531 DEBUG [org.jboss.system.ServiceController] starting service jboss:service=ClientUserTransaction
| 2008-09-17 23:04:06,531 DEBUG [org.jboss.tm.usertx.server.ClientUserTransactionService] Starting jboss:service=ClientUserTransaction
| 2008-09-17 23:04:06,531 DEBUG [org.jboss.tm.usertx.server.ClientUserTransactionService] Started jboss:service=ClientUserTransaction
| 2008-09-17 23:04:06,531 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss:service=ClientUserTransaction dependent components: []
| 2008-09-17 23:04:06,531 DEBUG [org.jboss.system.ServiceController] starting service jboss.remoting:service=Connector,transport=socket
| 2008-09-17 23:04:06,531 DEBUG [org.jboss.system.ServiceController] Ignoring start request for service: jboss.remoting:service=Connector,transport=socket
| 2008-09-17 23:04:06,531 DEBUG [org.jboss.system.ServiceController] starting service jboss.jdbc:service=metadata
| 2008-09-17 23:04:06,531 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] Starting jboss.jdbc:service=metadata
| 2008-09-17 23:04:06,531 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] Loading standardjbosscmp-jdbc.xml : file:/C:/jboss-4.2.3.GA/server/default/conf/standardjbosscmp-jdbc.xml
| 2008-09-17 23:04:07,062 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: FirstSQL/J
| 2008-09-17 23:04:07,078 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: Ingres
| 2008-09-17 23:04:07,093 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: McKoi
| 2008-09-17 23:04:07,109 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: Firebird
| 2008-09-17 23:04:07,125 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: InterBase
| 2008-09-17 23:04:07,125 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: DB2
| 2008-09-17 23:04:07,125 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: Derby
| 2008-09-17 23:04:07,140 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: Oracle9i
| 2008-09-17 23:04:07,140 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: Oracle8
| 2008-09-17 23:04:07,156 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: Oracle7
| 2008-09-17 23:04:07,156 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: Sybase
| 2008-09-17 23:04:07,156 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: PostgreSQL
| 2008-09-17 23:04:07,156 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: PostgreSQL 8.0
| 2008-09-17 23:04:07,156 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: PostgreSQL 7.2
| 2008-09-17 23:04:07,156 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: Hypersonic SQL
| 2008-09-17 23:04:07,171 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: PointBase
| 2008-09-17 23:04:07,171 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: SOLID
| 2008-09-17 23:04:07,171 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: mySQL
| 2008-09-17 23:04:07,171 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: MS SQLSERVER
| 2008-09-17 23:04:07,171 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: MS SQLSERVER2000
| 2008-09-17 23:04:07,187 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: DB2/400
| 2008-09-17 23:04:07,187 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: SapDB
| 2008-09-17 23:04:07,203 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: MaxDB
| 2008-09-17 23:04:07,203 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: Cloudscape
| 2008-09-17 23:04:07,203 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: InformixDB
| 2008-09-17 23:04:07,218 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] added type-mapping: Mimer SQL
| 2008-09-17 23:04:07,218 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary] Started jboss.jdbc:service=metadata
| 2008-09-17 23:04:07,218 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.jdbc:service=metadata dependent components: []
| 2008-09-17 23:04:07,218 DEBUG [org.jboss.system.ServiceController] starting service jboss.deployment:type=DeploymentScanner,flavor=URL
| 2008-09-17 23:04:07,218 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Starting jboss.deployment:type=DeploymentScanner,flavor=URL
| 2008-09-17 23:04:07,234 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/
| 2008-09-17 23:04:07,234 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment (init step) of package at: file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/
| 2008-09-17 23:04:07,234 DEBUG [org.jboss.deployment.MainDeployer] using deployer org.jboss.deployment.SARDeployer@1a06e38
| 2008-09-17 23:04:07,234 DEBUG [org.jboss.deployment.SARDeployer] Updated watch URL to: file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/META-INF/jboss-service.xml
| 2008-09-17 23:04:07,234 DEBUG [org.jboss.deployment.SARDeployer] about to copy 0 local directories
| 2008-09-17 23:04:07,234 DEBUG [org.jboss.deployment.SARDeployer] looking for nested deployments in : file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/
| 2008-09-17 23:04:07,234 DEBUG [org.jboss.deployment.SARDeployer] nested deployment: file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/jboss-annotations-ejb3.jar
| 2008-09-17 23:04:07,234 DEBUG [org.jboss.deployment.SARDeployer] nested deployment: file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/jboss-ejb3.jar
| 2008-09-17 23:04:07,234 DEBUG [org.jboss.deployment.DeploymentInfo] createLoaderRepository from config: LoaderRepositoryConfig(repositoryName: JMImplementation:service=LoaderRepository,name=Default, repositoryClassName: null, configParserClassName: null, repositoryConfig: null)
| 2008-09-17 23:04:07,234 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3@5a9de6, cl=org.jboss.mx.loading.UnifiedClassLoader3@98350a{ url=file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/ ,addedOrder=0}
| 2008-09-17 23:04:07,234 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3@5a9de6, cl=org.jboss.mx.loading.UnifiedClassLoader3@98350a{ url=file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/ ,addedOrder=0}
| 2008-09-17 23:04:07,234 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Adding org.jboss.mx.loading.UnifiedClassLoader3@98350a{ url=file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/ ,addedOrder=0}
| 2008-09-17 23:04:07,234 DEBUG [org.jboss.mx.loading.ClassLoaderUtils] Multiple class loaders found for pkg:
| 2008-09-17 23:04:07,234 DEBUG [org.jboss.deployment.MainDeployer] found 2 subpackages of file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/
| 2008-09-17 23:04:07,234 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment (init step) of package at: file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/jboss-annotations-ejb3.jar
| 2008-09-17 23:04:07,234 DEBUG [org.jboss.deployment.MainDeployer] Copying file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/jboss-annotations-ejb3.jar -> C:\jboss-4.2.3.GA\server\default\tmp\deploy\tmp27757jboss-annotations-ejb3.jar
| 2008-09-17 23:04:07,250 DEBUG [org.jboss.deployment.JARDeployer] No xml files found
| 2008-09-17 23:04:07,250 DEBUG [org.jboss.deployment.MainDeployer] using deployer org.jboss.deployment.JARDeployer@1d95492
| 2008-09-17 23:04:07,250 DEBUG [org.jboss.deployment.JARDeployer] looking for nested deployments in : file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/jboss-annotations-ejb3.jar
| 2008-09-17 23:04:07,265 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] Added url: file:/C:/jboss-4.2.3.GA/server/default/tmp/deploy/tmp27757jboss-annotations-ejb3.jar, to ucl: org.jboss.mx.loading.UnifiedClassLoader3@98350a{ url=file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/ ,addedOrder=3}
| 2008-09-17 23:04:07,265 DEBUG [org.jboss.deployment.MainDeployer] found 0 subpackages of file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/jboss-annotations-ejb3.jar
| 2008-09-17 23:04:07,265 DEBUG [org.jboss.deployment.MainDeployer] Watching new file: file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/jboss-annotations-ejb3.jar
| 2008-09-17 23:04:07,265 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment (init step) of package at: file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/jboss-ejb3.jar
| 2008-09-17 23:04:07,265 DEBUG [org.jboss.deployment.MainDeployer] Copying file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/jboss-ejb3.jar -> C:\jboss-4.2.3.GA\server\default\tmp\deploy\tmp27758jboss-ejb3.jar
| 2008-09-17 23:04:07,281 DEBUG [org.jboss.deployment.JARDeployer] No xml files found
| 2008-09-17 23:04:07,281 DEBUG [org.jboss.deployment.MainDeployer] using deployer org.jboss.deployment.JARDeployer@1d95492
| 2008-09-17 23:04:07,281 DEBUG [org.jboss.deployment.JARDeployer] looking for nested deployments in : file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/jboss-ejb3.jar
| 2008-09-17 23:04:07,359 DEBUG [org.jboss.mx.loading.ClassLoaderUtils] Multiple class loaders found for pkg: org.jboss.ejb
| 2008-09-17 23:04:07,421 DEBUG [org.jboss.mx.loading.ClassLoaderUtils] Multiple class loaders found for pkg: schema
| 2008-09-17 23:04:07,421 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] Added url: file:/C:/jboss-4.2.3.GA/server/default/tmp/deploy/tmp27758jboss-ejb3.jar, to ucl: org.jboss.mx.loading.UnifiedClassLoader3@98350a{ url=file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/ ,addedOrder=3}
| 2008-09-17 23:04:07,421 DEBUG [org.jboss.deployment.MainDeployer] found 0 subpackages of file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/jboss-ejb3.jar
| 2008-09-17 23:04:07,421 DEBUG [org.jboss.deployment.MainDeployer] Watching new file: file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/jboss-ejb3.jar
| 2008-09-17 23:04:07,421 DEBUG [org.jboss.deployment.MainDeployer] Watching new file: file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/
| 2008-09-17 23:04:07,421 DEBUG [org.jboss.deployment.MainDeployer] create step for deployment file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/
| 2008-09-17 23:04:07,421 DEBUG [org.jboss.deployment.MainDeployer] create step for deployment file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/jboss-annotations-ejb3.jar
| 2008-09-17 23:04:07,421 DEBUG [org.jboss.deployment.MainDeployer] Done with create step of deploying jboss-annotations-ejb3.jar
| 2008-09-17 23:04:07,421 DEBUG [org.jboss.deployment.MainDeployer] create step for deployment file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/jboss-ejb3.jar
| 2008-09-17 23:04:07,421 DEBUG [org.jboss.deployment.MainDeployer] Done with create step of deploying jboss-ejb3.jar
| 2008-09-17 23:04:07,421 DEBUG [org.jboss.deployment.SARDeployer] Deploying SAR, create step: url file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/
| 2008-09-17 23:04:07,421 DEBUG [org.jboss.deployment.SARDeployer] Registering service UCL=jmx.loading:UCL=98350a
| 2008-09-17 23:04:07,421 DEBUG [org.jboss.system.ServiceCreator] About to create bean: jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3 with code: org.jboss.remoting.transport.Connector
| 2008-09-17 23:04:07,437 DEBUG [org.jboss.system.ServiceCreator] Created bean: jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3
| 2008-09-17 23:04:07,437 DEBUG [org.jboss.system.ServiceController] recording that jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3 depends on jboss.aop:service=AspectDeployer
| 2008-09-17 23:04:07,437 DEBUG [org.jboss.system.ServiceConfigurator] considering <anonymous> with object name jboss.aop:service=AspectDeployer
| 2008-09-17 23:04:07,437 DEBUG [org.jboss.system.ServiceConfigurator] InvokerLocator set to socket://127.0.0.1:3873 in jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3
| 2008-09-17 23:04:07,453 DEBUG [org.jboss.system.ServiceConfigurator] Configuration set to [handlers: null] in jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3
| 2008-09-17 23:04:07,453 DEBUG [org.jboss.system.ServiceCreator] About to create bean: jboss.ejb3:service=JarsIgnoredForScanning with code: org.jboss.ejb3.JarsIgnoredForScanning
| 2008-09-17 23:04:07,453 DEBUG [org.jboss.system.ServiceCreator] Created bean: jboss.ejb3:service=JarsIgnoredForScanning
| 2008-09-17 23:04:07,484 DEBUG [org.jboss.system.ServiceConfigurator] IgnoredJars set to [Ljava.lang.String;@e14d81 in jboss.ejb3:service=JarsIgnoredForScanning
| 2008-09-17 23:04:07,484 DEBUG [org.jboss.system.ServiceCreator] About to create xmbean object: jboss.ejb3:service=EJB3Deployer with code: org.jboss.ejb3.EJB3Deployer with embedded descriptor
| 2008-09-17 23:04:07,500 DEBUG [org.jboss.system.ServiceCreator] Created bean: jboss.ejb3:service=EJB3Deployer
| 2008-09-17 23:04:07,500 DEBUG [org.jboss.system.ServiceConfigurator] DeployEjb3ExtensionOnly set to false in jboss.ejb3:service=EJB3Deployer
| 2008-09-17 23:04:07,500 DEBUG [org.jboss.system.ServiceController] recording that jboss.ejb3:service=EJB3Deployer depends on jboss.aop:service=AspectDeployer
| 2008-09-17 23:04:07,500 DEBUG [org.jboss.system.ServiceConfigurator] considering <anonymous> with object name jboss.aop:service=AspectDeployer
| 2008-09-17 23:04:07,500 DEBUG [org.jboss.system.ServiceController] recording that jboss.ejb3:service=EJB3Deployer depends on jboss.ejb:service=EJBDeployer
| 2008-09-17 23:04:07,500 DEBUG [org.jboss.system.ServiceConfigurator] considering <anonymous> with object name jboss.ejb:service=EJBDeployer
| 2008-09-17 23:04:07,500 DEBUG [org.jboss.system.ServiceController] recording that jboss.ejb3:service=EJB3Deployer depends on jboss.ejb3:service=JarsIgnoredForScanning
| 2008-09-17 23:04:07,500 DEBUG [org.jboss.system.ServiceConfigurator] considering JarsIgnoredForScanning with object name jboss.ejb3:service=JarsIgnoredForScanning
| 2008-09-17 23:04:07,500 DEBUG [org.jboss.system.ServiceController] Creating service jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3
| 2008-09-17 23:04:07,500 DEBUG [org.jboss.system.ServiceController] waiting in create of jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3 waiting on jboss.aop:service=AspectDeployer
| 2008-09-17 23:04:07,500 DEBUG [org.jboss.system.ServiceController] Creating service jboss.ejb3:service=JarsIgnoredForScanning
| 2008-09-17 23:04:07,500 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.ejb3:service=JarsIgnoredForScanning dependents are: [ObjectName: jboss.ejb3:service=EJB3Deployer
| State: CONFIGURED
| I Depend On:
| jboss.aop:service=AspectDeployer
| jboss.ejb:service=EJBDeployer
| jboss.ejb3:service=JarsIgnoredForScanning
| ]
| 2008-09-17 23:04:07,500 DEBUG [org.jboss.system.ServiceController] Creating service jboss.ejb3:service=EJB3Deployer
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.system.ServiceController] waiting in create of jboss.ejb3:service=EJB3Deployer waiting on jboss.aop:service=AspectDeployer
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.system.ServiceController] Creating service jboss.ejb3:service=EJB3Deployer
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.system.ServiceController] waiting in create of jboss.ejb3:service=EJB3Deployer waiting on jboss.aop:service=AspectDeployer
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.deployment.MainDeployer] Done with create step of deploying ejb3.deployer
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.deployment.MainDeployer] Begin deployment start file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.deployment.MainDeployer] Begin deployment start file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/jboss-annotations-ejb3.jar
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.deployment.MainDeployer] End deployment start on package: jboss-annotations-ejb3.jar
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.deployment.MainDeployer] Begin deployment start file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/jboss-ejb3.jar
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.deployment.MainDeployer] End deployment start on package: jboss-ejb3.jar
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.deployment.SARDeployer] Deploying SAR, start step: url file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.system.ServiceController] starting service jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.system.ServiceController] Start requested before create, calling create now for service: jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.system.ServiceController] Creating service jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.system.ServiceController] waiting in create of jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3 waiting on jboss.aop:service=AspectDeployer
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.system.ServiceController] waiting in start jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3 on jboss.aop:service=AspectDeployer
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.system.ServiceController] starting service jboss.ejb3:service=JarsIgnoredForScanning
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.ejb3:service=JarsIgnoredForScanning dependent components: [ObjectName: jboss.ejb3:service=EJB3Deployer
| State: CONFIGURED
| I Depend On:
| jboss.aop:service=AspectDeployer
| jboss.ejb:service=EJBDeployer
| jboss.ejb3:service=JarsIgnoredForScanning
| ]
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.system.ServiceController] starting service jboss.ejb3:service=EJB3Deployer
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.system.ServiceController] Start requested before create, calling create now for service: jboss.ejb3:service=EJB3Deployer
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.system.ServiceController] Creating service jboss.ejb3:service=EJB3Deployer
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.system.ServiceController] waiting in create of jboss.ejb3:service=EJB3Deployer waiting on jboss.aop:service=AspectDeployer
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.system.ServiceController] waiting in start jboss.ejb3:service=EJB3Deployer on jboss.aop:service=AspectDeployer
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.system.ServiceController] starting service jboss.ejb3:service=EJB3Deployer
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.system.ServiceController] Start requested before create, calling create now for service: jboss.ejb3:service=EJB3Deployer
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.system.ServiceController] Creating service jboss.ejb3:service=EJB3Deployer
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.system.ServiceController] waiting in create of jboss.ejb3:service=EJB3Deployer waiting on jboss.aop:service=AspectDeployer
| 2008-09-17 23:04:07,515 DEBUG [org.jboss.system.ServiceController] waiting in start jboss.ejb3:service=EJB3Deployer on jboss.aop:service=AspectDeployer
| 2008-09-17 23:04:07,531 DEBUG [org.jboss.deployment.MainDeployer] End deployment start on package: ejb3.deployer
| 2008-09-17 23:04:07,531 DEBUG [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/
| 2008-09-17 23:04:07,531 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Watch URL for: file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/ -> file:/C:/jboss-4.2.3.GA/server/default/deploy/ejb3.deployer/META-INF/jboss-service.xml
| 2008-09-17 23:04:07,531 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/jboss-4.2.3.GA/server/default/deploy/jboss-aop-jdk50.deployer/
| 2008-09-17 23:04:07,531 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment (init step) of package at: file:/C:/jboss-4.2.3.GA/server/default/deploy/jboss-aop-jdk50.deployer/
| 2008-09-17 23:04:07,531 DEBUG [org.jboss.deployment.MainDeployer] using deployer org.jboss.deployment.SARDeployer@1a06e38
| 2008-09-17 23:04:07,531 DEBUG [org.jboss.deployment.SARDeployer] Updated watch URL to: file:/C:/jboss-4.2.3.GA/server/default/deploy/jboss-aop-jdk50.deployer/META-INF/jboss-service.xml
| 2008-09-17 23:04:07,531 DEBUG [org.jboss.deployment.SARDeployer] about to copy 0 local directories
| 2008-09-17 23:04:07,531 DEBUG [org.jboss.deployment.SARDeployer] looking for nested deployments in : file:/C:/jboss-4.2.3.GA/server/default/deploy/jboss-aop-jdk50.deployer/
| 2008-09-17 23:04:07,531 DEBUG [org.jboss.deployment.SARDeployer] nested deployment: file:/C:/jboss-4.2.3.GA/server/default/deploy/jboss-aop-jdk50.deployer/jboss-aop-jdk50.jar
| 2008-09-17 23:04:07,546 DEBUG [org.jboss.deployment.SARDeployer] nested deployment: file:/C:/jboss-4.2.3.GA/server/default/deploy/jboss-aop-jdk50.deployer/jboss-aspect-library-jdk50.jar
| 2008-09-17 23:04:07,546 DEBUG [org.jboss.deployment.SARDeployer] nested deployment: file:/C:/jboss-4.2.3.GA/server/default/deploy/jboss-aop-jdk50.deployer/jrockit-pluggable-instrumentor.jar
| 2008-09-17 23:04:07,546 DEBUG [org.jboss.deployment.SARDeployer] nested deployment: file:/C:/jboss-4.2.3.GA/server/default/deploy/jboss-aop-jdk50.deployer/pluggable-instrumentor.jar
| 2008-09-17 23:04:07,546 DEBUG [org.jboss.deployment.SARDeployer] nested deployment: file:/C:/jboss-4.2.3.GA/server/default/deploy/jboss-aop-jdk50.deployer/trove.jar
| 2008-09-17 23:04:07,546 DEBUG [org.jboss.deployment.DeploymentInfo] createLoaderRepository from config: LoaderRepositoryConfig(repositoryName: JMImplementation:service=LoaderRepository,name=Default, repositoryClassName: null, configParserClassName: null, repositoryConfig: null)
| 2008-09-17 23:04:07,546 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3@5a9de6, cl=org.jboss.mx.loading.UnifiedClassLoader3@10c3a08{ url=file:/C:/jboss-4.2.3.GA/server/default/deploy/jboss-aop-jdk50.deployer/ ,addedOrder=0}
| 2008-09-17 23:04:07,546 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3@5a9de6, cl=org.jboss.mx.loading.UnifiedClassLoader3@10c3a08{ url=file:/C:/jboss-4.2.3.GA/server/default/deploy/jboss-aop-jdk50.deployer/ ,addedOrder=0}
| 2008-09-17 23:04:07,546 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Adding org.jboss.mx.loading.UnifiedClassLoader3@10c3a08{ url=file:/C:/jboss-4.2.3.GA/server/default/deploy/jboss-aop-jdk50.deployer/ ,addedOrder=0}
| 2008-09-17 23:04:07,546 DEBUG [org.jboss.mx.loading.ClassLoaderUtils] Multiple class loaders found for pkg:
| 2008-09-17 23:04:07,546 DEBUG [org.jboss.deployment.MainDeployer] found 5 subpackages of file:/C:/jboss-4.2.3.GA/server/default/deploy/jboss-aop-jdk50.deployer/
| 2008-09-17 23:04:07,546 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment (init step) of package at: file:/C:/jboss-4.2.3.GA/server/default/deploy/jboss-aop-jdk50.deployer/jboss-aop-jdk50.jar
| 2008-09-17 23:04:07,546 DEBUG [org.jboss.deployment.MainDeployer] Copying file:/C:/jboss-4.2.3.GA/server/default/deploy/jboss-aop-jdk50.deployer/jboss-aop-jdk50.jar -> C:\jboss-4.2.3.GA\server\default\tmp\deploy\tmp27759jboss-aop-jdk50.jar
| 2008-09-17 23:04:07,562 DEBUG [org.jboss.deployment.JARDeployer] No xml files found
| 2008-09-17 23:04:07,562 DEBUG [org.jboss.deployment.MainDeployer] using deployer org.jboss.deployment.JARDeployer@1d95492
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177039#4177039
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177039
17 years, 10 months
[Remoting] - Re: Compression marshalling
by robert.geisler
thank your for your reply, ron.
"ron.sigal(a)jboss.com" wrote : I'm concerned, though, that the same solution didn't work for Remoting 2.4. Did you just give up on 2.4, or is there anything else you can tell me about your experiments with 2.4?
well, as far as i can remember... i just didnt update the jbossall-client.jar with JBoss Remoting 2.4. thus my server and client didnt use the same version of Remoting which led to the exception(s) shown in my previous posts, of course.
i think the solution should work with JBoss Remoting 2.4, too (update server and(!) client libraries). but i just tried to change as less as possible... so i chose Remoting 2.2.2 SP8 O: )
thank you very much for your explanations concerning EJB 2.1. it seems to be not too complicated to me. but i will not try this out anyway, because we are going to migrate all of our EJBs from 2.1 to 3.0 in the next months. so compression is one more reason (of small importance) pro migration ; )
regards
robert
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177023#4177023
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177023
17 years, 10 months
[Beginners Corner] - Re: dynamically load classes within app on JBOSS
by tuezney
The app on jboss is a webapp, it is a servlet that tries to classload a jar file with a POJO app that is in the deploy directory.
This worked in our previous jboss version (JBoss_4_0_1_SP1) for e few years. We used
a bea jrockit 1.5 jvm.
Now I am upgrading our server to 4.2.3.GA and our java version to sun's 1.6 imp.
The whole idea is the following.
Use all the nice stuff of the appserver :
- db connection pooled and managed by container
- 1 jvm for all applications
- unified classloading
- jmx
- jms
Without the use of ejb3, writing a deployment descriptors, annotations all over the place etc etc etc
And still have the possibility (if needed) to run the applications (for test eg) without the appserver.
We succeeded in this by developping servlet and an interface (DeployableApplication).
All the developer has to do is to implement the DeployableApplication, pack this into a jar file and deploy it in the deploy directory. The app will be started with a request on the servlet I mentioned before.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177017#4177017
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177017
17 years, 10 months
[JBoss jBPM] - Re: wiki>>JbpmBuildingTheSources: update for svn?
by k_feanor
I've spent many hours reading lots of posts in this forum with the same question: jbpm console sources.
I wonder why it is so difficult to get a simple, direct and clear answer...the replys are always "in svn", "in cvs", "already answered". Maybe i'm completely insane, but could it be that if so many people ask for it maybe it isn't so easy or so clear. Can't you think that maybe the problem is the information and the instructions and not the people?maybe it's not enough for many people that needs more complete information.
On the other hand, it's not necessary to be so...offensive?nobody knows everything. It's possible, maybe, that i'm quite expert on java ee, struts, jsf, hibernate, ibatis, and much more and don't know anything about ant or maven. It's possible, isn't it? Maybe, in my team, that's somebody else work...maybe...maybe i have no idea of how to make that simple build, but i'm able to use and modify the console...maybe. Anyway, what if i don't know anything about development or programming?i don't have the right to test it and learn? is it something like "if you don't know how to do that, you don't deserve it?". I can be wrong, but i think that this is not de right aproach for an open source community. In my opinion, of course.
Ending, i'm member of many forums. I think that a forum is a very useful tool for a community. A place to express, to share, to learn, to teach, to grow. Some people in this forum could be a little kinder. If it is so easy to build it, instead of laughing at me, you could share that knowledge and give a set of a-b-c steps, for dummies (like me) and probably people will stop asking always the same question.
Sorry for writting so much.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177009#4177009
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177009
17 years, 10 months
[Clustering/JBoss] - Re: Custom InvokerInterceptor
by bdinnerv
Well, after a day of testing and changes, I cant for the life of me get my session beans to cluster.
I have implemented a custom InvokerInterceptor, placed my jar in server/all/lib, changed all references to org.jboss.invocation.InvokerInterceptor with my custom one, even tried removing all references to the MarshellingInterceptor (not the full class name I know, but it slips my mind at the moment) but the interceptor does not seem to get called. I have some sysout printing in my implementation of hasLocalTarget and also in the default no args constructor and am not getting any messages logged nor am I getting round robin load distribution for my session beans. Is there somewhere else other that standardboss.xml that I need to make the change to get the my custom Invoker used?
I am using JBoss 4.2.3 with the all configuration on jdk 1.5.16 / linux and EJB3, the session beans are annotated as follows:
@Stateless
| @Clustered(loadBalancePolicy = RoundRobin.class)
| @Remote(ICampaignService.class)
And my client uses the following:
try {
Properties env = new Properties();
env.setProperty(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
env.setProperty(Context.URL_PKG_PREFIXES,"jboss.naming:org.jnp.interfaces");
env.setProperty("jnp.partitionName", "DefaultPartition");
env.setProperty(Context.PROVIDER_URL, "localhost:1100");
_initialContext = new InitialContext(env);
} catch (NamingException e) {
fooo bar . . .
_campaignService = (ICampaignService) lookup("teleblast/CampaignServiceBean/remote");
|
| Cheers,
|
| Ben
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176989#4176989
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176989
17 years, 10 months
[Clustering/JBoss] - Re: Custom InvokerInterceptor
by bdinnerv
Hi All,
Further to my last post, can anyone provide some insight into which parameters need to be changed when utilising a custom InvokerInterceptor?
The easy way would be to take the shotgun approach and replace all references to org.jboss.invocation.InvocationInterceptor in standardjboss.xml but I am guessing that this is a bit over the top and that only certain references to it need to be changed to get SLSB clustering to work.
Looking at the config, I would guess that only the clustered-entity-unified-invoker section in the config needs to be changed, but I am not 100% sure as there are quite a few other references to InvokerInterceptor throughout the file.
Any input from people who have done this config would be appreciated.
Cheers,
Ben
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176961#4176961
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176961
17 years, 10 months
[Beginners Corner] - Re: Varia Scheduler cannot find class at startup
by lpmon
Forgot to give version:
JBoss AS 4.0.5GA
and error:
--- MBeans waiting for other MBeans ---
ObjectName: RDPExtract:service=Scheduler
State: FAILED
Reason: org.jboss.deployment.DeploymentException: Exception setting attribute javax.management.Attribute@15330ea on mbean RDPExtract:service=Scheduler; - nested throwable: (java.security.InvalidParameterException: Given class com.shockwatch.swevents.rdp.extract.RDPAutoExtract is not not found)
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: RDPExtract:service=Scheduler
State: FAILED
Reason: org.jboss.deployment.DeploymentException: Exception setting attribute javax.management.Attribute@15330ea on mbean RDPExtract:service=Scheduler; - nested throwable: (java.security.InvalidParameterException: Given class com.shockwatch.swevents.rdp.extract.RDPAutoExtract is not not found)
2008-09-16 19:06:37,284 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: RDPExtract:service=Scheduler
State: FAILED
Reason: org.jboss.deployment.DeploymentException: Exception setting attribute javax.management.Attribute@7ae145 on mbean RDPExtract:service=Scheduler; - nested throwable: (java.security.InvalidParameterException: Given class com.shockwatch.swevents.rdp.extract.RDPAutoExtract is not not found)
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: RDPExtract:service=Scheduler
State: FAILED
Reason: org.jboss.deployment.DeploymentException: Exception setting attribute javax.management.Attribute@7ae145 on mbean RDPExtract:service=Scheduler; - nested throwable: (java.security.InvalidParameterException: Given class com.shockwatch.swevents.rdp.extract.RDPAutoExtract is not not found)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176959#4176959
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176959
17 years, 10 months
[Beginners Corner] - Varia Scheduler cannot find class at startup
by lpmon
I have seen this before and created a work-around. I have since changed my deployment layout (due to EJB3/Seam) and now my work-around does not work.
in schedule-service.xml:
true
com.shockwatch.swevents.rdp.extract.RDPAutoExtract
09/16/2008 6:38
120000
-1
The SchedulableClass is inside a jar that is inside an ear. How do I tell where to find the class?
Here is my kludge that used to work. It touches the xml config file which causes JBoss to reload it (after the ear loaded and class is available).
/**
* KLUDGE: could not get dependency to work for scheduler service, cause it to reload config
*/
private void touchScheduler()
{
try
{
Class.forName("com.shockwatch.swevents.rdp.extract.RDPAutoExtract");
String fileSep=System.getProperty("file.separator");
String deployDir=System.getProperty("jboss.server.home.dir") + fileSep + "deploy" + fileSep;
File f = new File(deployDir + "scheduler-service.xml");
f.setLastModified(System.currentTimeMillis());
}
catch (Exception ex)
{
ex.printStackTrace(System.err);
}
}
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176957#4176957
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176957
17 years, 10 months
[Beginners Corner] - Trying to install an already registered mbean: jboss.jca:ser
by MikePhoenix
Ok, I tried to search for the above error and the search engine for this site just returned a ton of stuff that mostly seemed irrelevant. The anwer may have been somwhere in the thousands of links returned, but I couldn't find it.
I am trying to bui9ld a nd deploy an application that is currently running on a 4.0.1 server on a new 4.2.3 server. I have set up the connection to my MySQL database and tested it as described in the getting started documentation. When I try to build and deploy it onto the 4.2.3 server I get the following error messages:
16:17:34,844 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
16:17:34,923 ERROR [MainDeployer] Could not create deployment: file:/C:/jboss-4.2.3.GA/server/default/deploy/mysql-ds.xml
org.jboss.deployment.DeploymentException: Trying to install an already registered mbean: jboss.jca:service=LocalTxCM,name=DefaultDS
at org.jboss.system.ServiceCreator.install(ServiceCreator.java:103)
at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:451)
at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171)
at org.jboss.system.ServiceController.install(ServiceController.java:226)
at sun.reflect.GeneratedMethodAccessor23.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
Some help would be greatly appreciated.
Mike
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176956#4176956
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176956
17 years, 10 months
[Remoting] - Re: Remoting 3 trunk - Ordered delivery problem
by barbacena
Tried but did not work (deadlocked?!).
public final class ClientToServerToClientExample {
|
| public static void main(String[] args) throws Exception {
| Security.addProvider(new Provider());
| RequestListener<Object, String> listenerServer = new AbstractRequestListener<Object, String>() {
|
| @Override
| public void handleRequest(final RequestContext<String> context, final Object request) throws RemoteExecutionException {
| System.out.println("In the server: " + request);
| try {
| Client<Object, String> client = (Client) request;
| client.send("Message from server...");
| context.sendReply("Processed client message");
| } catch (Exception e) {
| e.printStackTrace();
| }
| }
| };
| RequestListener<Object, String> listenerClient = new AbstractRequestListener<Object, String>() {
|
| @Override
| public void handleRequest(RequestContext<String> context, Object request) throws RemoteExecutionException {
| System.out.println("In the client: " + request);
| try {
| context.sendReply("Processed server message");
| } catch (Exception e) {
| e.printStackTrace();
| }
| }
| };
| Endpoint endpointServer = Remoting.createEndpoint("server");
| Endpoint endpointClient = Remoting.createEndpoint("client");
| Client<Object, String> server = null;
| Client<Object, String> client = null;
| try {
| server = Remoting.createLocalClient(endpointServer, listenerServer);
| client = Remoting.createLocalClient(endpointClient, listenerClient);
| server.invoke(client);
| } finally {
| IoUtils.safeClose(server);
| Remoting.closeEndpoint(endpointServer);
| }
| }
|
| }
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176952#4176952
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176952
17 years, 10 months
[Clustering/JBoss] - Controlled Singleton MBean failed to become master
by jbossnoob
I'm trying to deploy my ear in deploy-hasingleton and keep getting this error. Anyone have any ideas?
Thanks
14:54:56,112 ERROR [HASingletonController] Controlled Singleton MBean failed to become master
| javax.management.MBeanException
| at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.jav
| a:180)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:163)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.j
| ava:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.ha.singleton.HASingletonController.invokeSingletonMBeanMethod(HASingletonController.j
| ava:207)
| at org.jboss.ha.singleton.HASingletonController.startSingleton(HASingletonController.java:144)
| at org.jboss.ha.singleton.HASingletonSupport.startNewMaster(HASingletonSupport.java:267)
| at org.jboss.ha.singleton.HASingletonSupport.makeThisNodeMaster(HASingletonSupport.java:249)
| at org.jboss.ha.singleton.HASingletonSupport.partitionTopologyChanged(HASingletonSupport.java:191)
|
| at org.jboss.ha.jmx.HAServiceMBeanSupport$1.replicantsChanged(HAServiceMBeanSupport.java:247)
| at org.jboss.ha.framework.server.DistributedReplicantManagerImpl.notifyKeyListeners(DistributedRep
| licantManagerImpl.java:846)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176944#4176944
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176944
17 years, 10 months
[Beginners Corner] - verbose log
by jnl1
hi all...
my app is dying around the time it hits the db. i changed the log4j level from INFO to DEBUG for my console appender to get more information from jboss, but no luck. i'm using jdk1.5 and jboss 4.2.3. below is the log. i'm wondering if someone can tell me how to get more debug, or what the problem could be. it's difficult to solve without knowing more about the problem.
My initial web page just displays a 404 with the context (/datastandards) followed by a null:
| http://127.0.0.1:8087/datastandardsnull
|
I print out the hibernate sql, but nothing shows up in the log. so, i thought the problem is related to the connection.
This was working fine. it was only after updating to a later version of hibernate (3.1.3 -> 3.2.6.ga) and jboss (4.0.3sp1 -> 4.3.2.ga) and oracle dialect. i put debug between 2 operations that hit the db. the first one outputs to the log, but the second one doesn't. which is another indication that it's connection related.
thanks
| 15:05:36,365 INFO [STDOUT] 15:05:36,365 INFO [SettingsFactory] JDBC driver: Oracle JDBC driver, version: 11.1.0.6.0-Pr
| oduction+
| 15:05:36,389 INFO [STDOUT] 15:05:36,389 INFO [Dialect] Using dialect: org.hibernate.dialect.Oracle10gDialect
| 15:05:36,402 INFO [STDOUT] 15:05:36,402 INFO [TransactionFactoryFactory] Using default transaction strategy (direct JD
| BC transactions)
| 15:05:36,407 INFO [STDOUT] 15:05:36,407 INFO [TransactionManagerLookupFactory] No TransactionManagerLookup configured
| (in JTA environment, use of read-write or transactional second-level cache is not recommended)
| 15:05:36,408 INFO [STDOUT] 15:05:36,408 INFO [SettingsFactory] Automatic flush during beforeCompletion(): disabled
| 15:05:36,409 INFO [STDOUT] 15:05:36,409 INFO [SettingsFactory] Automatic session close at end of transaction: disabled
|
| 15:05:36,410 INFO [STDOUT] 15:05:36,410 INFO [SettingsFactory] JDBC batch size: 15
| 15:05:36,411 INFO [STDOUT] 15:05:36,411 INFO [SettingsFactory] JDBC batch updates for versioned data: disabled
| 15:05:36,412 INFO [STDOUT] 15:05:36,412 INFO [SettingsFactory] Scrollable result sets: enabled
| 15:05:36,415 INFO [STDOUT] 15:05:36,415 INFO [SettingsFactory] JDBC3 getGeneratedKeys(): disabled
| 15:05:36,416 INFO [STDOUT] 15:05:36,415 INFO [SettingsFactory] Connection release mode: on_close
| 15:05:36,416 INFO [STDOUT] 15:05:36,416 INFO [SettingsFactory] Default batch fetch size: 1
| 15:05:36,417 INFO [STDOUT] 15:05:36,417 INFO [SettingsFactory] Generate SQL with comments: disabled
| 15:05:36,417 INFO [STDOUT] 15:05:36,417 INFO [SettingsFactory] Order SQL updates by primary key: disabled
| 15:05:36,418 INFO [STDOUT] 15:05:36,418 INFO [SettingsFactory] Order SQL inserts for batching: disabled
| 15:05:36,418 INFO [STDOUT] 15:05:36,418 INFO [SettingsFactory] Query translator: org.hibernate.hql.ast.ASTQueryTransla
| torFactory
| 15:05:36,424 INFO [STDOUT] 15:05:36,424 INFO [ASTQueryTranslatorFactory] Using ASTQueryTranslatorFactory
| 15:05:36,425 INFO [STDOUT] 15:05:36,425 INFO [SettingsFactory] Query language substitutions: {}
| 15:05:36,426 INFO [STDOUT] 15:05:36,426 INFO [SettingsFactory] JPA-QL strict compliance: disabled
| 15:05:36,427 INFO [STDOUT] 15:05:36,427 INFO [SettingsFactory] Second-level cache: enabled
| 15:05:36,428 INFO [STDOUT] 15:05:36,428 INFO [SettingsFactory] Query cache: disabled
| 15:05:36,429 INFO [STDOUT] 15:05:36,429 INFO [SettingsFactory] Cache provider: org.hibernate.cache.EhCacheProvider
| 15:05:36,436 INFO [STDOUT] 15:05:36,436 INFO [SettingsFactory] Optimize cache for minimal puts: disabled
| 15:05:36,437 INFO [STDOUT] 15:05:36,437 INFO [SettingsFactory] Structured second-level cache entries: disabled
| 15:05:36,445 INFO [STDOUT] 15:05:36,445 INFO [SettingsFactory] Statistics: disabled
| 15:05:36,445 INFO [STDOUT] 15:05:36,445 INFO [SettingsFactory] Deleted entity synthetic identifier rollback: disabled
| 15:05:36,446 INFO [STDOUT] 15:05:36,446 INFO [SettingsFactory] Default entity-mode: pojo
| 15:05:36,447 INFO [STDOUT] 15:05:36,447 INFO [SettingsFactory] Named query checking : enabled
| 15:05:36,492 INFO [STDOUT] 15:05:36,492 INFO [SessionFactoryImpl] building session factory
| 15:05:37,184 INFO [STDOUT] 15:05:37,184 INFO [SessionFactoryObjectFactory] Not binding factory to JNDI, no JNDI name configured
| 15:05:38,001 INFO [STDOUT] 15:05:38,000 INFO [DefaultListableBeanFactory] Destroying singletons in {org.springframewor
| k.beans.factory.support.DefaultListableBeanFactory defining beans [messageSource,sessionFactory,hibernateInterceptor,sta
| ndardDao,statusDao,codeValueDao,proposalDao,standardTypeDao,groupDao,organizationDao,subCategoryDao,categoryDao,organiza
| tionCategoryDao,proposalTypeDao,dataStandardsService,abstractService,codeValueManager,dataSource,transactionManager]; ro
| ot of BeanFactory hierarchy}
| 15:05:38,008 INFO [STDOUT] 15:05:38,008 INFO [LocalSessionFactoryBean] Closing Hibernate SessionFactory
| 15:05:38,009 INFO [STDOUT] 15:05:38,009 INFO [SessionFactoryImpl] closing
| 15:05:38,013 INFO [STDOUT] 15:05:38,013 INFO [DefaultListableBeanFactory] Destroying singletons in {org.springframewor
| k.beans.factory.support.DefaultListableBeanFactory defining beans [beanRefFactory,beanRefFactoryEjb]; root of BeanFactor
| y hierarchy}
| 15:05:41,870 INFO [Server] Runtime shutdown hook called, forceHalt: true
| 15:05:41,872 INFO [Server] JBoss SHUTDOWN: Undeploying all packages
| 15:05:41,879 INFO [TomcatDeployer] undeploy, ctxPath=/datastandards-ws, warUrl=.../tmp/deploy/tmp24399datastandards-1.1
| .2.ear-contents/datastandards-webservice-1.1.2-exp.war/
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176942#4176942
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176942
17 years, 10 months
[Beginners Corner] - JBoss crash
by velasquez
Hi,
I had the below error when I restarted JBoss. Is this related to memory space. Please help.
#
# An unexpected error has been detected by Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d83de95, pid=5532, tid=3380
#
# Java VM: Java HotSpot(TM) Client VM (1.6.0_03-b05 mixed mode)
# Problematic frame:
# V [jvm.dll+0x7de95]
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
--------------- T H R E A D ---------------
Current thread (0x26c57400): VMThread [id=3380]
siginfo: ExceptionCode=0xc0000005, reading address 0x90d022f9
Registers:
EAX=0x00000000, EBX=0x0029a8d8, ECX=0xc3e80000, EDX=0x90d02299
ESP=0x26d2f9c4, EBP=0x050f0000, ESI=0x0677999a, EDI=0xc3e80000
EIP=0x6d83de95, EFLAGS=0x00010293
Top of Stack: (sp=0x26d2f9c4)
0x26d2f9c4: 6d8f710e 0677999a 0679b074 0679b06c
0x26d2f9d4: 6d9065bb 00000003 6d9c9c5c 6d9c9c5c
0x26d2f9e4: 6d8f6dea 0679b060 6d8f71ea 00000003
0x26d2f9f4: 6d962b02 6d9e4198 6d9c9c5c 0029a8d8
0x26d2fa04: 0029a8d8 6d92d6ea 6d9c9c5c 00000000
0x26d2fa14: 6d9c9c5c 6d9c9c5c 6d85cce1 00000001
0x26d2fa24: 00000002 6d9c9c5c 6d9c9c5c 00299958
0x26d2fa34: 0029a8d8 050f0000 00000000 6d85e96b
Instructions: (pc=0x6d83de95)
0x6d83de85: 00 83 e0 07 83 f8 05 74 1f 8b 54 24 04 8b 52 04
0x6d83de95: 8b 52 60 83 e2 07 80 fa 05 74 12 83 f8 01 75 0d
Stack: [0x26ce0000,0x26d30000), sp=0x26d2f9c4, free space=318k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [jvm.dll+0x7de95]
VM_Operation (0x26fac7f0): full generation collection, mode: safepoint, requested by thread 0x26cc6800
--------------- P R O C E S S ---------------
Java Threads: ( => current thread )
0x27d21800 JavaThread "Timer-2" daemon [_thread_blocked, id=1468]
0x27029800 JavaThread "UILServerILService Accept Thread" [_thread_in_native, id=3700]
0x27899c00 JavaThread "TimeoutFactory-1" daemon [_thread_blocked, id=4440]
0x27bb0400 JavaThread "JCA PoolFiller" [_thread_blocked, id=5160]
0x27d0c400 JavaThread "Timer-1" daemon [_thread_blocked, id=4624]
0x27c1c000 JavaThread "HSQLDB Timer @180e7a4" daemon [_thread_blocked, id=5944]
0x27ce4000 JavaThread "WorkManager(3)-1" daemon [_thread_blocked, id=6060]
0x27744800 JavaThread "Thread-2" daemon [_thread_blocked, id=5824]
0x270d0c00 JavaThread "JBossMQ Cache Reference Softner" daemon [_thread_blocked, id=760]
0x270ff400 JavaThread "SubscriptionWatchDog" [_thread_blocked, id=4156]
0x2789e400 JavaThread "ContainerBackgroundProcessor[StandardEngine[jboss.web]]" daemon [_thread_blocked, id=5332]
0x26c79c00 JavaThread "PooledInvokerAcceptor#0-4445" [_thread_in_native, id=5644]
0x276ab400 JavaThread "RMI TCP Accept-4444" daemon [_thread_in_native, id=5368]
0x27680800 JavaThread "TimeoutFactory-0" daemon [_thread_blocked, id=2604]
0x2768b400 JavaThread "JBoss System Threads(1)-2" daemon [_thread_in_native, id=1820]
0x27690000 JavaThread "GC Daemon" daemon [_thread_blocked, id=5804]
0x2768f000 JavaThread "RMI Reaper" [_thread_blocked, id=4148]
0x27685400 JavaThread "RMI TCP Accept-1097" daemon [_thread_in_native, id=5756]
0x275af800 JavaThread "JBoss System Threads(1)-1" daemon [_thread_in_native, id=1372]
0x275ad800 JavaThread "ScannerThread" daemon [_thread_blocked, id=2012]
0x27567000 JavaThread "Timer-0" daemon [_thread_blocked, id=5788]
0x00296c00 JavaThread "DestroyJavaVM" [_thread_blocked, id=1508]
0x26cc6800 JavaThread "main" [_thread_blocked, id=3384]
0x26c74800 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=5004]
0x26c6fc00 JavaThread "CompilerThread0" daemon [_thread_blocked, id=5520]
0x26c6e800 JavaThread "Attach Listener" daemon [_thread_blocked, id=4348]
0x26c6d800 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=3036]
0x26c5c800 JavaThread "Finalizer" daemon [_thread_blocked, id=2788]
0x26c5b800 JavaThread "Reference Handler" daemon [_thread_blocked, id=5044]
Other Threads:
=>0x26c57400 VMThread [id=3380]
0x26c75c00 WatcherThread [id=2564]
VM state:at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread: ([mutex/lock_event])
[0x002957f8/0x000006f8] Threads_lock - owner thread: 0x26c57400
[0x00295998/0x000006b8] Heap_lock - owner thread: 0x26cc6800
Heap
def new generation total 9216K, used 1144K [0x02990000, 0x03380000, 0x050f0000)
eden space 8256K, 6% used [0x02990000, 0x02a0fbc0, 0x031a0000)
from space 960K, 66% used [0x031a0000, 0x0323e7b0, 0x03290000)
to space 960K, 0% used [0x03290000, 0x03290000, 0x03380000)
tenured generation total 121024K, used 51477K [0x050f0000, 0x0c720000, 0x22990000)
the space 121024K, 42% used [0x050f0000, 0x08335648, 0x08335800, 0x0c720000)
compacting perm gen total 28416K, used 28415K [0x22990000, 0x24550000, 0x26990000)
the space 28416K, 99% used [0x22990000, 0x2454ffe0, 0x24550000, 0x24550000)
No shared spaces configured.
Dynamic libraries:
0x00400000 - 0x00423000 C:\WINDOWS\system32\java.exe
0x7c800000 - 0x7c8c0000 C:\WINDOWS\system32\ntdll.dll
0x77e40000 - 0x77f42000 C:\WINDOWS\system32\kernel32.dll
0x77f50000 - 0x77feb000 C:\WINDOWS\system32\ADVAPI32.dll
0x77c50000 - 0x77cef000 C:\WINDOWS\system32\RPCRT4.dll
0x76f50000 - 0x76f63000 C:\WINDOWS\system32\Secur32.dll
0x7c340000 - 0x7c396000 C:\Program Files\Java\jre1.6.0_03\bin\msvcr71.dll
0x6d7c0000 - 0x6da0a000 C:\Program Files\Java\jre1.6.0_03\bin\client\jvm.dll
0x77380000 - 0x77411000 C:\WINDOWS\system32\USER32.dll
0x77c00000 - 0x77c48000 C:\WINDOWS\system32\GDI32.dll
0x76aa0000 - 0x76acd000 C:\WINDOWS\system32\WINMM.dll
0x71bc0000 - 0x71bc8000 C:\WINDOWS\system32\rdpsnd.dll
0x771f0000 - 0x77201000 C:\WINDOWS\system32\WINSTA.dll
0x77ba0000 - 0x77bfa000 C:\WINDOWS\system32\msvcrt.dll
0x71c40000 - 0x71c97000 C:\WINDOWS\system32\NETAPI32.dll
0x76b70000 - 0x76b7b000 C:\WINDOWS\system32\PSAPI.DLL
0x6d310000 - 0x6d318000 C:\Program Files\Java\jre1.6.0_03\bin\hpi.dll
0x6d770000 - 0x6d77c000 C:\Program Files\Java\jre1.6.0_03\bin\verify.dll
0x6d3b0000 - 0x6d3cf000 C:\Program Files\Java\jre1.6.0_03\bin\java.dll
0x6d7b0000 - 0x6d7bf000 C:\Program Files\Java\jre1.6.0_03\bin\zip.dll
0x6d570000 - 0x6d583000 C:\Program Files\Java\jre1.6.0_03\bin\net.dll
0x71c00000 - 0x71c17000 C:\WINDOWS\system32\WS2_32.dll
0x71bf0000 - 0x71bf8000 C:\WINDOWS\system32\WS2HELP.dll
0x71b20000 - 0x71b61000 C:\WINDOWS\System32\mswsock.dll
0x76ed0000 - 0x76efa000 C:\WINDOWS\system32\DNSAPI.dll
0x76f70000 - 0x76f77000 C:\WINDOWS\System32\winrnr.dll
0x76f10000 - 0x76f3e000 C:\WINDOWS\system32\WLDAP32.dll
0x76f80000 - 0x76f85000 C:\WINDOWS\system32\rasadhlp.dll
0x6d560000 - 0x6d569000 C:\Program Files\Java\jre1.6.0_03\bin\management.dll
0x5f270000 - 0x5f2ca000 C:\WINDOWS\system32\hnetcfg.dll
0x71ae0000 - 0x71ae8000 C:\WINDOWS\System32\wshtcpip.dll
0x68000000 - 0x68035000 C:\WINDOWS\system32\rsaenh.dll
0x76920000 - 0x769e2000 C:\WINDOWS\system32\USERENV.dll
0x6d590000 - 0x6d599000 C:\Program Files\Java\jre1.6.0_03\bin\nio.dll
VM Arguments:
jvm_args: -Dprogram.name=run.bat -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.endorsed.dirs=C:\jboss-4.0.4.GA\bin\\..\lib\endorsed
java_command: org.jboss.Main
Launcher Type: SUN_STANDARD
Environment Variables:
PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\
USERNAME=Administrator
OS=Windows_NT
PROCESSOR_IDENTIFIER=x86 Family 15 Model 3 Stepping 3, GenuineIntel
--------------- S Y S T E M ---------------
OS: Windows Server 2003 family Build 3790 Service Pack 2
CPU:total 1 (1 cores per cpu, 1 threads per core) family 15 model 3 stepping 3, cmov, cx8, fxsr, mmx, sse, sse2, sse3
Memory: 4k page, physical 1046292k(297912k free), swap 2531128k(1535708k free)
vm_info: Java HotSpot(TM) Client VM (1.6.0_03-b05) for windows-x86, built on Sep 24 2007 22:24:33 by "java_re" with unknown MS VC++:1310
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176936#4176936
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176936
17 years, 10 months
[Installation, Configuration & DEPLOYMENT] - Error when JBoss was restarted
by velasquez
Hi,
I had the below error when I restarted JBoss. Is this related to memory space. Please help.
#
# An unexpected error has been detected by Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d83de95, pid=5532, tid=3380
#
# Java VM: Java HotSpot(TM) Client VM (1.6.0_03-b05 mixed mode)
# Problematic frame:
# V [jvm.dll+0x7de95]
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
--------------- T H R E A D ---------------
Current thread (0x26c57400): VMThread [id=3380]
siginfo: ExceptionCode=0xc0000005, reading address 0x90d022f9
Registers:
EAX=0x00000000, EBX=0x0029a8d8, ECX=0xc3e80000, EDX=0x90d02299
ESP=0x26d2f9c4, EBP=0x050f0000, ESI=0x0677999a, EDI=0xc3e80000
EIP=0x6d83de95, EFLAGS=0x00010293
Top of Stack: (sp=0x26d2f9c4)
0x26d2f9c4: 6d8f710e 0677999a 0679b074 0679b06c
0x26d2f9d4: 6d9065bb 00000003 6d9c9c5c 6d9c9c5c
0x26d2f9e4: 6d8f6dea 0679b060 6d8f71ea 00000003
0x26d2f9f4: 6d962b02 6d9e4198 6d9c9c5c 0029a8d8
0x26d2fa04: 0029a8d8 6d92d6ea 6d9c9c5c 00000000
0x26d2fa14: 6d9c9c5c 6d9c9c5c 6d85cce1 00000001
0x26d2fa24: 00000002 6d9c9c5c 6d9c9c5c 00299958
0x26d2fa34: 0029a8d8 050f0000 00000000 6d85e96b
Instructions: (pc=0x6d83de95)
0x6d83de85: 00 83 e0 07 83 f8 05 74 1f 8b 54 24 04 8b 52 04
0x6d83de95: 8b 52 60 83 e2 07 80 fa 05 74 12 83 f8 01 75 0d
Stack: [0x26ce0000,0x26d30000), sp=0x26d2f9c4, free space=318k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [jvm.dll+0x7de95]
VM_Operation (0x26fac7f0): full generation collection, mode: safepoint, requested by thread 0x26cc6800
--------------- P R O C E S S ---------------
Java Threads: ( => current thread )
0x27d21800 JavaThread "Timer-2" daemon [_thread_blocked, id=1468]
0x27029800 JavaThread "UILServerILService Accept Thread" [_thread_in_native, id=3700]
0x27899c00 JavaThread "TimeoutFactory-1" daemon [_thread_blocked, id=4440]
0x27bb0400 JavaThread "JCA PoolFiller" [_thread_blocked, id=5160]
0x27d0c400 JavaThread "Timer-1" daemon [_thread_blocked, id=4624]
0x27c1c000 JavaThread "HSQLDB Timer @180e7a4" daemon [_thread_blocked, id=5944]
0x27ce4000 JavaThread "WorkManager(3)-1" daemon [_thread_blocked, id=6060]
0x27744800 JavaThread "Thread-2" daemon [_thread_blocked, id=5824]
0x270d0c00 JavaThread "JBossMQ Cache Reference Softner" daemon [_thread_blocked, id=760]
0x270ff400 JavaThread "SubscriptionWatchDog" [_thread_blocked, id=4156]
0x2789e400 JavaThread "ContainerBackgroundProcessor[StandardEngine[jboss.web]]" daemon [_thread_blocked, id=5332]
0x26c79c00 JavaThread "PooledInvokerAcceptor#0-4445" [_thread_in_native, id=5644]
0x276ab400 JavaThread "RMI TCP Accept-4444" daemon [_thread_in_native, id=5368]
0x27680800 JavaThread "TimeoutFactory-0" daemon [_thread_blocked, id=2604]
0x2768b400 JavaThread "JBoss System Threads(1)-2" daemon [_thread_in_native, id=1820]
0x27690000 JavaThread "GC Daemon" daemon [_thread_blocked, id=5804]
0x2768f000 JavaThread "RMI Reaper" [_thread_blocked, id=4148]
0x27685400 JavaThread "RMI TCP Accept-1097" daemon [_thread_in_native, id=5756]
0x275af800 JavaThread "JBoss System Threads(1)-1" daemon [_thread_in_native, id=1372]
0x275ad800 JavaThread "ScannerThread" daemon [_thread_blocked, id=2012]
0x27567000 JavaThread "Timer-0" daemon [_thread_blocked, id=5788]
0x00296c00 JavaThread "DestroyJavaVM" [_thread_blocked, id=1508]
0x26cc6800 JavaThread "main" [_thread_blocked, id=3384]
0x26c74800 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=5004]
0x26c6fc00 JavaThread "CompilerThread0" daemon [_thread_blocked, id=5520]
0x26c6e800 JavaThread "Attach Listener" daemon [_thread_blocked, id=4348]
0x26c6d800 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=3036]
0x26c5c800 JavaThread "Finalizer" daemon [_thread_blocked, id=2788]
0x26c5b800 JavaThread "Reference Handler" daemon [_thread_blocked, id=5044]
Other Threads:
=>0x26c57400 VMThread [id=3380]
0x26c75c00 WatcherThread [id=2564]
VM state:at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread: ([mutex/lock_event])
[0x002957f8/0x000006f8] Threads_lock - owner thread: 0x26c57400
[0x00295998/0x000006b8] Heap_lock - owner thread: 0x26cc6800
Heap
def new generation total 9216K, used 1144K [0x02990000, 0x03380000, 0x050f0000)
eden space 8256K, 6% used [0x02990000, 0x02a0fbc0, 0x031a0000)
from space 960K, 66% used [0x031a0000, 0x0323e7b0, 0x03290000)
to space 960K, 0% used [0x03290000, 0x03290000, 0x03380000)
tenured generation total 121024K, used 51477K [0x050f0000, 0x0c720000, 0x22990000)
the space 121024K, 42% used [0x050f0000, 0x08335648, 0x08335800, 0x0c720000)
compacting perm gen total 28416K, used 28415K [0x22990000, 0x24550000, 0x26990000)
the space 28416K, 99% used [0x22990000, 0x2454ffe0, 0x24550000, 0x24550000)
No shared spaces configured.
Dynamic libraries:
0x00400000 - 0x00423000 C:\WINDOWS\system32\java.exe
0x7c800000 - 0x7c8c0000 C:\WINDOWS\system32\ntdll.dll
0x77e40000 - 0x77f42000 C:\WINDOWS\system32\kernel32.dll
0x77f50000 - 0x77feb000 C:\WINDOWS\system32\ADVAPI32.dll
0x77c50000 - 0x77cef000 C:\WINDOWS\system32\RPCRT4.dll
0x76f50000 - 0x76f63000 C:\WINDOWS\system32\Secur32.dll
0x7c340000 - 0x7c396000 C:\Program Files\Java\jre1.6.0_03\bin\msvcr71.dll
0x6d7c0000 - 0x6da0a000 C:\Program Files\Java\jre1.6.0_03\bin\client\jvm.dll
0x77380000 - 0x77411000 C:\WINDOWS\system32\USER32.dll
0x77c00000 - 0x77c48000 C:\WINDOWS\system32\GDI32.dll
0x76aa0000 - 0x76acd000 C:\WINDOWS\system32\WINMM.dll
0x71bc0000 - 0x71bc8000 C:\WINDOWS\system32\rdpsnd.dll
0x771f0000 - 0x77201000 C:\WINDOWS\system32\WINSTA.dll
0x77ba0000 - 0x77bfa000 C:\WINDOWS\system32\msvcrt.dll
0x71c40000 - 0x71c97000 C:\WINDOWS\system32\NETAPI32.dll
0x76b70000 - 0x76b7b000 C:\WINDOWS\system32\PSAPI.DLL
0x6d310000 - 0x6d318000 C:\Program Files\Java\jre1.6.0_03\bin\hpi.dll
0x6d770000 - 0x6d77c000 C:\Program Files\Java\jre1.6.0_03\bin\verify.dll
0x6d3b0000 - 0x6d3cf000 C:\Program Files\Java\jre1.6.0_03\bin\java.dll
0x6d7b0000 - 0x6d7bf000 C:\Program Files\Java\jre1.6.0_03\bin\zip.dll
0x6d570000 - 0x6d583000 C:\Program Files\Java\jre1.6.0_03\bin\net.dll
0x71c00000 - 0x71c17000 C:\WINDOWS\system32\WS2_32.dll
0x71bf0000 - 0x71bf8000 C:\WINDOWS\system32\WS2HELP.dll
0x71b20000 - 0x71b61000 C:\WINDOWS\System32\mswsock.dll
0x76ed0000 - 0x76efa000 C:\WINDOWS\system32\DNSAPI.dll
0x76f70000 - 0x76f77000 C:\WINDOWS\System32\winrnr.dll
0x76f10000 - 0x76f3e000 C:\WINDOWS\system32\WLDAP32.dll
0x76f80000 - 0x76f85000 C:\WINDOWS\system32\rasadhlp.dll
0x6d560000 - 0x6d569000 C:\Program Files\Java\jre1.6.0_03\bin\management.dll
0x5f270000 - 0x5f2ca000 C:\WINDOWS\system32\hnetcfg.dll
0x71ae0000 - 0x71ae8000 C:\WINDOWS\System32\wshtcpip.dll
0x68000000 - 0x68035000 C:\WINDOWS\system32\rsaenh.dll
0x76920000 - 0x769e2000 C:\WINDOWS\system32\USERENV.dll
0x6d590000 - 0x6d599000 C:\Program Files\Java\jre1.6.0_03\bin\nio.dll
VM Arguments:
jvm_args: -Dprogram.name=run.bat -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.endorsed.dirs=C:\jboss-4.0.4.GA\bin\\..\lib\endorsed
java_command: org.jboss.Main
Launcher Type: SUN_STANDARD
Environment Variables:
PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\
USERNAME=Administrator
OS=Windows_NT
PROCESSOR_IDENTIFIER=x86 Family 15 Model 3 Stepping 3, GenuineIntel
--------------- S Y S T E M ---------------
OS: Windows Server 2003 family Build 3790 Service Pack 2
CPU:total 1 (1 cores per cpu, 1 threads per core) family 15 model 3 stepping 3, cmov, cx8, fxsr, mmx, sse, sse2, sse3
Memory: 4k page, physical 1046292k(297912k free), swap 2531128k(1535708k free)
vm_info: Java HotSpot(TM) Client VM (1.6.0_03-b05) for windows-x86, built on Sep 24 2007 22:24:33 by "java_re" with unknown MS VC++:1310
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176932#4176932
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176932
17 years, 10 months
[EJB 3.0] - EJB 3.0 ClassNotFoundExdeption between EAR when using Securi
by sebastiendeg
Hi there,
I have 2 EAR (only EJB) application (application1 using application 2's client ejb jar).
The first EAR application is the service which has logic and web services, so it has security enabled. (Security Domain with LoginModule)
So, the users have to authenticate to access any webServices.
When the WebServices tries to send a Command Object to the second application I have the following Exception :
Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException: No ClassLoaders found for: com.company.dao.commands.account.AccountCreationCommand (no security manager: RMI class loader disabled)
| at org.jboss.aop.joinpoint.MethodInvocation.getArguments(MethodInvocation.java:276)
| at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:299)
| at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106)
| at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
| at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
| at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:373)
| at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
And this is only since a use security on the first aplication.
Any idea ?
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176912#4176912
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176912
17 years, 10 months
[Installation, Configuration & DEPLOYMENT] - jboss-4.0.5.GA
by smaya
Hi,
I downloaded jboss-4.0.5 and started jboss under default. It started successfully but when customized the default and added cs.war I am getting these error. Any adivise is helpful.
[WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:name=OracleDS,service=DataSourceBinding' to JNDI name 'java:OracleDS'
13:54:50,210 INFO [TomcatDeployer] deploy, ctxPath=/cs, warUrl=.../deploy/cs.war/
13:54:50,522 ERROR [Digester] End event threw exception
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.tomcat.util.IntrospectionUtils.callMethod1(IntrospectionUtils.java:898)
at org.apache.tomcat.util.digester.SetNextRule.end(SetNextRule.java:192)
at org.apache.tomcat.util.digester.Rule.end(Rule.java:228)
at org.apache.tomcat.util.digester.Digester.endElement(Digester.java:1057)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.endNamespaceScope(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1561)
at org.apache.catalina.startup.ContextConfig.applicationWebConfig(ContextConfig.java:351)
at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:1041)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:260)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4143)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.apache.catalina.core.StandardContext.init(StandardContext.java:5052)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:297)
at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:103)
at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:371)
at org.jboss.web.WebModule.startModule(WebModule.java:83)
at org.jboss.web.WebModule.startService(WebModule.java:61)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor64.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy38.start(Unknown Source)
at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
at org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInterceptor.java:92)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy39.start(Unknown Source)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor57.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:490)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.IllegalArgumentException: Invalid <url-pattern> /pages/reports/*.jsp in filter mapping
at org.apache.catalina.core.StandardContext.addFilterMap(StandardContext.java:2112)
... 160 more
13:54:50,553 ERROR [ContextConfig] Parse error in application web.xml file at jndi:/localhost/cs/WEB-INF/web.xml
java.lang.IllegalArgumentException: Invalid <url-pattern> /pages/reports/*.jsp in filter mapping
at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java:2725)
at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java:2751)
at org.apache.tomcat.util.digester.Digester.endElement(Digester.java:1060)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.endNamespaceScope(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1561)
at org.apache.catalina.startup.ContextConfig.applicationWebConfig(ContextConfig.java:351)
at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:1041)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:260)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4143)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.apache.catalina.core.StandardContext.init(StandardContext.java:5052)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:297)
at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:103)
at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:371)
at org.jboss.web.WebModule.startModule(WebModule.java:83)
at org.jboss.web.WebModule.startService(WebModule.java:61)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor64.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy38.start(Unknown Source)
at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
at org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInterceptor.java:92)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy39.start(Unknown Source)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor57.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:490)
at java.lang.Thread.run(Thread.java:534)
13:54:50,553 ERROR [ContextConfig] Occurred at line 125 column 21
13:54:50,553 ERROR [ContextConfig] Marking this application unavailable due to previous error(s)
13:54:50,585 ERROR [StandardContext] Error getConfigured
13:54:50,585 ERROR [StandardContext] Context [/cs] startup failed due to previous errors
13:54:50,600 WARN [ServiceController] Problem starting service jboss.web.deployment:id=430416872,war=cs.war
org.jboss.deployment.DeploymentException: URL file:/C:/jboss-4.0.5/jboss-4.0.5.GA/server/cs/deploy/cs.war/ deployment failed
at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:375)
at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:103)
at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:371)
at org.jboss.web.WebModule.startModule(WebModule.java:83)
at org.jboss.web.WebModule.startService(WebModule.java:61)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor64.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy38.start(Unknown Source)
at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
at org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInterceptor.java:92)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy39.start(Unknown Source)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor57.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:490)
at java.lang.Thread.run(Thread.java:534)
13:54:50,600 ERROR [MainDeployer] Could not start deployment: file:/C:/jboss-4.0.5/jboss-4.0.5.GA/server/cs/deploy/cs.war/
org.jboss.deployment.DeploymentException: URL file:/C:/jboss-4.0.5/jboss-4.0.5.GA/server/cs/deploy/cs.war/ deployment failed
at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:375)
at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:103)
at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:371)
at org.jboss.web.WebModule.startModule(WebModule.java:83)
at org.jboss.web.WebModule.startService(WebModule.java:61)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor64.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy38.start(Unknown Source)
at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
at org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInterceptor.java:92)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy39.start(Unknown Source)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor57.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:490)
at java.lang.Thread.run(Thread.java:534)
13:54:50,741 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
13:54:51,100 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@19a7a3e8 { url=file:/C:/jboss-4.0.5/jboss-4.0.5.GA/server/cs/deploy/cs.war/ }
deployer: MBeanProxyExt[jboss.web:service=WebServer]
status: Deployment FAILED reason: URL file:/C:/jboss-4.0.5/jboss-4.0.5.GA/server/cs/deploy/cs.war/ deployment failed
state: FAILED
watch: file:/C:/jboss-4.0.5/jboss-4.0.5.GA/server/cs/deploy/cs.war/WEB-INF/web.xml
altDD: null
lastDeployed: 1221591289944
lastModified: 1221582055229
mbeans:
--- MBeans waiting for other MBeans ---
ObjectName: jboss.web.deployment:id=430416872,war=cs.war
State: FAILED
Reason: org.jboss.deployment.DeploymentException: URL file:/C:/jboss-4.0.5/jboss-4.0.5.GA/server/cs/deploy/cs.war/ deployment failed
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.web.deployment:id=430416872,war=cs.war
State: FAILED
Reason: org.jboss.deployment.DeploymentException: URL file:/C:/jboss-4.0.5/jboss-4.0.5.GA/server/cs/deploy/cs.war/ deployment failed
13:54:51,350 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
13:54:51,631 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
13:54:51,709 INFO [JkMain] Jk running ID=0 time=0/187 config=null
13:54:51,725 INFO [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)] Started in 32s:311ms
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176903#4176903
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176903
17 years, 10 months
[EJB/JBoss] - Re: JBOSS 4.0.2 and EJB 2.1 - simple application - not worki
by lincoln__a
Hi Friends,
Still i have beeen strugging to find solution.
I am running the local ejb from command prompt in same JVM. For this no need jndi.properties file and jboss.xml. Pleae cinfirm it. Direct i am looking home interface in look up.
setting following jar files at command prompt.
set path=path%; c:...
set classpath=%classpath;
C:\jboss-4.0.2\jboss-4.0.2\server\default\lib\jboss-j2ee.jar;
C:\jboss-4.0.2\jboss-4.0.2\server\default\lib\jboss.jar;
C:\jboss-4.0.2\jboss-4.0.2\server\default\lib\jboss-transaction.jar;
C:\jboss-4.0.2\jboss-4.0.2\server\default\lib\jnpserver.jar;
C:\jboss-4.0.2\jboss-4.0.2\server\default\lib\jboss-common.jar;
Confirm these jars are enough or any jar is missed?
But it is not working.
Please kindly provide client jndi looku up code for local bean calling at command prompt and jar file required for jnoss 4.0.2 to rin ejb 2.1 at clinet?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176902#4176902
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176902
17 years, 10 months
[JBossMQ] - Exception while sending messages...
by rahul.bandgar
I am not getting what is the reason of the following exception.
Please let me know.
Thanks,
2008-09-16 14:37:10,890 DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler] The UILClientIL Connection is set up
2008-09-16 14:37:10,953 DEBUG [org.jboss.mq.il.uil2.SocketManager] Failed to handle: org.jboss.mq.il.uil2.msgs.CloseMsg18779762[msgType: m_connectionClosing, msgID: 6, error: null]
java.io.IOException: Client is not connected
at org.jboss.mq.il.uil2.SocketManager.internalSendMessage(SocketManager.java:264)
at org.jboss.mq.il.uil2.SocketManager.sendReply(SocketManager.java:238)
at org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:134)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:395)
at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:398)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
at java.lang.Thread.run(Unknown Source)
2008-09-16 14:37:10,953 DEBUG [org.jboss.mq.il.uil2.SocketManager] Failed to send error reply
java.io.IOException: Client is not connected
at org.jboss.mq.il.uil2.SocketManager.internalSendMessage(SocketManager.java:264)
at org.jboss.mq.il.uil2.SocketManager.access$800(SocketManager.java:53)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:408)
at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:398)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
at java.lang.Thread.run(Unknown Source)
2008-09-16 14:37:10,953 DEBUG [org.jboss.mq.il.uil2.SocketManager] End WriteTask.run
2008-09-16 14:37:10,953 DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Exiting on IOE
java.net.SocketException: socket closed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at org.jboss.util.stream.NotifyingBufferedInputStream.read(NotifyingBufferedInputStream.java:79)
at java.io.ObjectInputStream$PeekInputStream.peek(Unknown Source)
at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(Unknown Source)
at java.io.ObjectInputStream$BlockDataInputStream.refill(Unknown Source)
at java.io.ObjectInputStream$BlockDataInputStream.read(Unknown Source)
at java.io.ObjectInputStream$BlockDataInputStream.readByte(Unknown Source)
at java.io.ObjectInputStream.readByte(Unknown Source)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:316)
at java.lang.Thread.run(Unknown Source)
2008-09-16 14:37:10,968 DEBUG [org.jboss.mq.il.uil2.SocketManager] End ReadTask.run
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176892#4176892
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176892
17 years, 10 months