[JBoss Tools (users)] - Re: Failed to Start JBoss 4.2.0 Application Platform with JB
by flindet
No, I'm mistaken. I'm sorry. I must have noticed that permission problem earlier and corrected it. And didn't notice that my exception had changed. I apologize.
It looks like I'm currently troubleshooting the following:
2007-07-17 09:18:30,935 ERROR [org.apache.catalina.connector.Connector] Coyote connector has not been started
and:
2007-07-17 09:18:31,675 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Unable to obtain watchUrl from deployer. Use url: file:/usr/local/jboss-eap-4.2/jboss-as/server/dojesb/deploy/deploy.last/
| java.lang.NullPointerException
| at org.jboss.deployment.scanner.AbstractDeploymentScanner.getDeployer(AbstractDeploymentScanner.java:88)
| at org.jboss.deployment.scanner.URLDeploymentScanner$DeployedURL.getLastModified(URLDeploymentScanner.java:762)
| at org.jboss.deployment.scanner.URLDeploymentScanner$DeployedURL.deployed(URLDeploymentScanner.java:734)
| at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:432)
| 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.GeneratedMethodAccessor3.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| 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:585)
| 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:585)
| 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:508)
| at java.lang.Thread.run(Thread.java:595)
| 2007-07-17 09:18:31,723 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] java.lang.NullPointerException
It's still true that I can start the JBoss EAP 4.2 from command line with my regular user account without problem. I just can't do so from within Eclipse 3.3 using JBoss Tools (now upgraded to JBossTools-200707170856-nightly-ALL-linux-gtk).
flindet@HQISB-7Y2GF61:/usr/local/jboss-eap-4.2/jboss-as/server/dojesb/deploy> ls -ld
| drwxrwxr-x 16 jboss dojesb 4096 2007-07-12 11:27 ./
| flindet@HQISB-7Y2GF61:/usr/local/jboss-eap-4.2/jboss-as/server/dojesb/deploy> ls -ld deploy.last/
| drwxrwxr-x 2 jboss dojesb 4096 2007-07-10 14:41 deploy.last/
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065077#4065077
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4065077
18Â years, 11Â months
[JBoss Seam] - Exception on running the seamdiscs example
by kingcu
I built the seamdiscs example from cvs with no problem, and deployed with no problem either. When I open the browser and point it to the url "http://localhost:8080/seam-discs", the page doesn't load and I got the following exception:
12:39:34,765 INFO [Contexts] starting up: org.jboss.seam.security.identity
| 12:39:34,781 INFO [Contexts] starting up: org.jboss.seam.web.session
| 12:39:35,281 ERROR [ExceptionFilter] handling uncaught exception
| javax.servlet.ServletException: Servlet execution threw an exception
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:313)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._invokeDoFilter(TrinidadFilterImpl.java:208)
| at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:165)
| at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:138)
| at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:82)
| at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68)
| at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68)
| at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:61)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68)
| at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:44)
| at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68)
| at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:149)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
| at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
| at java.lang.Thread.run(Unknown Source)
| Caused by: java.lang.NoSuchMethodError: org.jboss.seam.contexts.Lifecycle.setPhaseId(Ljavax/faces/event/PhaseId;)V
| at org.jboss.seam.debug.jsf.SeamDebugPhaseListener.beforePhase(SeamDebugPhaseListener.java:35)
| at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:222)
| at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144)
| at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
| ... 35 more
I am running JBoss AS 4.2.0 GA.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065075#4065075
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4065075
18Â years, 11Â months
[JBoss Seam] - Cache level
by rapowder
Hi,
I'm not sure whether this is the right place to post this question, but I'm not sure either if the problem I have comes from Hibernate or from Seam Conversations.
I am using seam 1.2.1.GA and hibernate 3.2. In my application, data is updated quite frequently by many concurrent clients. Scenario is very simple. Two pages: one to show items, one to edit an item's properties.
My item entity is defined as such:
@Entity
| @Name("item")
| @Table(name="item")
| public class MItem implements Serializable {
|
| @ManyToMany
| @org.hibernate.annotations.Fetch(FetchMode.SUBSELECT)
| @Cascade({
| CascadeType.SAVE_UPDATE,
| CascadeType.MERGE,
| CascadeType.PERSIST})
| @JoinTable(
| name = "item_prop",
| joinColumns = {@JoinColumn(name = "ip_item")},
| inverseJoinColumns = {@JoinColumn(name = "ip_prop")})
| private Set<MProperty> properties = new HashSet<MProperty>();
|
| [...]
| }
and the property class:
| @Entity
| @Name("property")
| @Table(name="property")
| public class MProperty implements Serializable {
|
| @ManyToMany(mappedBy = "properties")
| private Set<MItem>items = new HashSet<MItem>();
|
| @Column(name = "pr_value")
| private String value;
|
| [...]
| }
The conversation spans from the item list page to the edit item (join) and is never ended (not even after saving the changes to the item properties).
If from Client A I update one of the properties of an item I can see my changes in the item list (even without ending the conversation upon persisting) but if from Client B I query the DB I can not see changes done to that property until I logout and login again (or simply when the http session is ended).
On the contrary, when I create a new item I can see changes on both clients.
I was not sure weather this was related to the second-level cache of hibernate, which I now disabled but this didn't give any significant results.
The only solution I found so far is to execute an em.refresh(item) on each item of the list before showing it, which works but has a terrible effect on performances!
Annotating queries with hints does not work either, does somebody have a good solution for this problem?
Thank you!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065071#4065071
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4065071
18Â years, 11Â months
[JNDI/Naming/Network] - Remote JMS connection over NAT'ed IP
by swatkat1976
Hi,
I am trying to connect to a remote JMS queue from my JBoss Server 4.0.3SP1 and using JBossMQ. The other server also hosts JBossMQ.
The machines involved and their IPs are as below:
The client Machine:
Name: XYZ
Config: JBoss Server 4.0.3SP1
Network IP: 122.xx.xx.xx {Say Network MC)
The host machine:
Name: ABC
JBoss Server 4.0.2
Network IP: 60.23.xx.xx {Say Network JS}
JMS Config: JBossMQ and is configured with HAJNDI on port 1100
Connection from Machine ABC to XYZ:
Method: VPN
Host IP: 122.xx.xx.xx {Network MC}
NAT'ed IP: 172.xx.xx.xxx {NATIP}, this IP has port mapping to
Final Destination IP 60.23.xx.xx {Network JS}
Ports Mapped: 1100 and 1099,
I can ping,telnet and access Network JS from Network MC through NATIP
Remote host hajndi-jms-ds.xml file
| <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
| name="jboss.mq:service=JMSProviderLoader,name=HAJNDIJMSProvider">
| <attribute name="ProviderName">DefaultJMSProvider</attribute>
| <attribute name="ProviderAdapterClass">
| org.jboss.jms.jndi.JNDIProviderAdapter
| </attribute>
| <!-- The combined connection factory -->
| <attribute name="FactoryRef">java:/XAConnectionFactory</attribute>
| <!-- The queue connection factory -->
| <attribute name="QueueFactoryRef">XAConnectionFactory</attribute>
| <!-- The topic factory -->
| <attribute name="TopicFactoryRef">XAConnectionFactory</attribute>
| <!-- Access JMS via HAJNDI -->
| <attribute name="Properties">
| java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
| java.naming.provider.url=<someObscureServer>.com:1100
| </attribute>
| </mbean>
Remote JNDIView Output: using NAT'ed IP http://172.xx.xx.xxx:8080/jmx-console/HtmlAdaptor
java: Namespace
| +- JmsXA
| +- ConnectionFactory
| +- DefaultJMSProvider
| +- XAConnectionFactory
|
| Global JNDI Namespace
| +- ConnectionFactory
| +- HTTPConnectionFactory
| +- XAConnectionFactory
| +- UILXAConnectionFactory[link -> XAConnectionFactory]
| +- UIL2XAConnectionFactory[link -> XAConnectionFactory]
| +- UIL2ConnectionFactory[link -> ConnectionFactory]
| +- UILConnectionFactory[link -> ConnectionFactory]
| +- queue
| | +- A
| | +- DataFeed
|
I have made various attempts to connect to remote JNDI using the configurations below
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Trial 1 JMS Provider on port 1100
jms-ds.xml
| <mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="jboss.mq:service=JMSProviderLoader,name=RemoteJMSProvider,server=RemoteSite">
| <attribute name="ProviderName">RemoteSiteJMSProvider</attribute>
| <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
| <attribute name="QueueFactoryRef">XAConnectionFactory</attribute>
| <attribute name="TopicFactoryRef">XAConnectionFactory</attribute>
| <attribute name="Properties">
| java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
| java.naming.provider.url=172.xx.xx.xxx:1100
| </attribute>
| </mbean>
| <tx-connection-factory>
| <jndi-name>JSTJmsXA</jndi-name>
| <rar-name>jms-ra.rar</rar-name>
| <connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition>
| <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Queue</config-property>
| <config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/RemoteSiteJMSProvider</config-property>
| </tx-connection-factory>
|
|
Java Code: (Standalone Java Client)
properties.put("java.naming.factory.initial","org.jnp.interfaces.NamingContextFactory");
| properties.put("java.naming.factory.url.pkgs","org.jboss.naming:org.jnp.interfaces");
| properties.put("java.naming.provider.url","jnp://localhost:1099");
| initialContext = new InitialContext(properties);
|
| queueConFac = (QueueConnectionFactory) initialContext.lookup("JSTJmsXA");
|
|
Result:
javax.naming.NameNotFoundException: JSTJmsXA not bound
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Trial 2 External Context on port 1100
jms-ds.xml
<mbean code="org.jboss.naming.ExternalContext" name="jboss.jndi:service=ExternalContext,jndiName=jstRemoteJNDI">
| <attribute name="JndiName">jstRemoteJNDI</attribute>
| <attribute name="Properties">
| java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| java.naming.factory.url.pkgs=org.jnp.interfaces
| java.naming.provider.url=172.xx.xx.xxx:1100
| </attribute>
| <attribute name="InitialContext">javax.naming.InitialContext</attribute>
| <attribute name="RemoteAccess">true</attribute>
| <depends>jboss:service=Naming</depends>
| </mbean>
|
JNDIView Output:
Global JNDI Namespace
| +- jstRemoteJNDI
| error while listing context javax.naming.InitialContext@1054f93: javax.naming.CommunicationException [Root exception is java.rmi.RemoteException: Service unavailable.]javax.naming.CommunicationException [Root exception is java.rmi.RemoteException: Service unavailable.]
| at org.jnp.interfaces.NamingContext.list(NamingContext.java:797)
|
|
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Trial 3 External Context on port 1099
jms-ds.xml
<mbean code="org.jboss.naming.ExternalContext" name="jboss.jndi:service=ExternalContext,jndiName=jstRemoteJNDI">
| <attribute name="JndiName">jstRemoteJNDI</attribute>
| <attribute name="Properties">
| java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| java.naming.factory.url.pkgs=org.jnp.interfaces
| java.naming.provider.url=172.xx.xx.xxx:1099
| </attribute>
| <attribute name="InitialContext">javax.naming.InitialContext</attribute>
| <attribute name="RemoteAccess">true</attribute>
| <depends>jboss:service=Naming</depends>
| </mbean>
JNDIView Output: {Connection refused to actual Remote IP instead of NAT'ed IP
| +- jstRemoteJNDI
| error while listing context javax.naming.InitialContext@a4be02: javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Connection refused to host: 60.23.xx.xx; nested exception is:
| java.net.ConnectException: Connection refused: connect
I have referred to the postings below but have not been able to figure out the problem yet.
http://wiki.jboss.org/wiki/Wiki.jsp?page=HowDoIConfigureTheJMSResourceAda...
http://wiki.jboss.org/wiki/Wiki.jsp?page=HowDoIConfigureAnMDBToTalkToARem...
http://www.jboss.org/wiki/Wiki.jsp?page=JBossNS
http://www.jboss.org/wiki/Wiki.jsp?page=JBossNSFAQ
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065064#4065064
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4065064
18Â years, 11Â months