[JBoss Tools (users)] - missing the seam perspective with ganymede SR2
by dozer247
Hi,
I've installed eclipse ganymede SR2 and added the update site JBoss Tools Development Release Update Site (http://download.jboss.org/jbosstools/updates/development).
After updating and restarting eclipse i can't see seam perspective in open perspective window.
In the log i'm also getting getting the following errors
| !SESSION 2009-03-04 14:13:30.437 -----------------------------------------------
| eclipse.buildId=M20090211-1700
| java.version=1.6.0_07
| java.vendor=Sun Microsystems Inc.
| BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
| Command-line arguments: -os win32 -ws win32 -arch x86
|
| !ENTRY org.eclipse.ui.workbench.texteditor 4 0 2009-03-04 14:13:35.406
| !MESSAGE The 'org.eclipse.wst.jsdt.web.ui.internal.hyperlink.script.JSPJavaHyperlinkDetector' extension from plug-in 'org.eclipse.wst.jsdt.web.ui' to the 'org.eclipse.ui.workbench.texteditor.hyperlinkDetectors' extension point will be ignored because it contains invalid attributes.
|
| !ENTRY org.eclipse.ui.workbench.texteditor 4 0 2009-03-04 14:13:35.406
| !MESSAGE The 'org.eclipse.wst.jsdt.web.ui.internal.hyperlink.script.event.JSPJavaHyperlinkDetector' extension from plug-in 'org.eclipse.wst.jsdt.web.ui' to the 'org.eclipse.ui.workbench.texteditor.hyperlinkDetectors' extension point will be ignored because it contains invalid attributes.
|
| !ENTRY org.eclipse.jface 2 0 2009-03-04 14:13:39.375
| !MESSAGE Keybinding conflicts occurred. They may interfere with normal accelerator operation.
| !SUBENTRY 1 org.eclipse.jface 2 0 2009-03-04 14:13:39.375
| !MESSAGE A conflict occurred for ALT+SHIFT+D R:
| Binding(ALT+SHIFT+D R,
| ParameterizedCommand(Command(org.eclipse.wst.server.launchShortcut.debug,Debug on Server,
| Debug the current selection on a server,
| Category(org.eclipse.debug.ui.category.run,Run/Debug,Run/Debug command category,true),
| ,
| ,,true),null),
| org.eclipse.ui.defaultAcceleratorConfiguration,
| org.eclipse.ui.contexts.window,,,system)
| Binding(ALT+SHIFT+D R,
| ParameterizedCommand(Command(org.eclipse.rap.ui.launch.RAPLaunchShortcut.debug,Debug RAP Application,
| Debug RAP Application,
| Category(org.eclipse.debug.ui.category.run,Run/Debug,Run/Debug command category,true),
| ,
| ,,true),null),
| org.eclipse.ui.defaultAcceleratorConfiguration,
| org.eclipse.ui.contexts.window,,,system)
| !SUBENTRY 1 org.eclipse.jface 2 0 2009-03-04 14:13:39.375
| !MESSAGE A conflict occurred for ALT+SHIFT+X R:
| Binding(ALT+SHIFT+X R,
| ParameterizedCommand(Command(org.eclipse.wst.server.launchShortcut.run,Run on Server,
| Run the current selection on a server,
| Category(org.eclipse.debug.ui.category.run,Run/Debug,Run/Debug command category,true),
| ,
| ,,true),null),
| org.eclipse.ui.defaultAcceleratorConfiguration,
| org.eclipse.ui.contexts.window,,,system)
| Binding(ALT+SHIFT+X R,
| ParameterizedCommand(Command(org.eclipse.rap.ui.launch.RAPLaunchShortcut.run,Run RAP Application,
| Run RAP Application,
| Category(org.eclipse.debug.ui.category.run,Run/Debug,Run/Debug command category,true),
| ,
| ,,true),null),
| org.eclipse.ui.defaultAcceleratorConfiguration,
| org.eclipse.ui.contexts.window,,,system)
|
| !ENTRY org.eclipse.wst.common.project.facet.core 4 0 2009-03-04 14:13:39.609
| !MESSAGE Project facet jst.seam has not been defined. It is used in plugin org.jboss.tools.portlet.core.
|
does anyone know how i can fix these errors and view the seam perspective
thanks
Darrell
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214718#4214718
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214718
15 years, 10 months
[JBoss Messaging] - Destination COnfiguration issue with Jboss 5 and Messaging
by guy.finger
Hi
I am recently upgrading to Jboss 5 and started evaluating Jboss Messaging. I have configured orcale as database. Server came up properly. Later on I have added new topic configuration in destination-service.xml
<mbean code="org.jboss.jms.server.destination.TopicService"
| name="jboss.messaging.destination:service=Topic,name=serverPublishTopic"
| xmbean-dd="xmdesc/Topic-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| <attribute name="SecurityConfig">
| <security>
| <role name="guest" read="true" write="true"/>
| <role name="publisher" read="true" write="true" create="false"/>
| <role name="durpublisher" read="true" write="true" create="true"/>
| <role name="dursubscriber" read="true" write="true" create="true"/>
| </security>
| </attribute>
| </mbean>
Once after adding the above destination I have restarted the server. It came up properly.
Then I have logged into JMX_CONSOLE and find the my topic under destinations section. When I am trying to open my destination(serverPublishTopic) I am getting the following exception. I am also getting the same exception even I am trying to access any example topics.
16:16:30,761 ERROR [ExceptionUtil] Topic[(destination.getName() == NULL)] listMessagesNonDu
| rableSub
| java.lang.NullPointerException
| at org.jboss.jms.server.destination.ManagedTopic.getMessageCounters(ManagedTopic.ja
| va:159)
| at org.jboss.jms.server.destination.TopicService.getMessageCounters(TopicService.ja
| va:559)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
| a:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.AttributeDispatcher.invoke(AttributeDispatcher.java:99)
|
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanAttributeInterceptor.invoke(ModelMBeanAttribu
| teInterceptor.java:197)
| at org.jboss.mx.interceptor.PersistenceInterceptor.invoke(PersistenceInterceptor.ja
| va:76)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
| at org.jboss.mx.server.AbstractMBeanInvoker.getAttribute(AbstractMBeanInvoker.java:
| 362)
| at org.jboss.mx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:565)
| at org.jboss.jmx.adaptor.control.Server.getMBeanAttributeResultInfo(Server.java:144
| )
| at org.apache.jsp.inspectMBean_jsp._jspService(inspectMBean_jsp.java:283)
| at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
| at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369)
| at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:322)
| at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:249)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt
| erChain.java:290)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.
| java:206)
| at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java
| :638)
| at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatc
| her.java:444)
| at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.j
| ava:382)
| at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.jav
| a:310)
| at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.inspectMBean(HtmlAdaptorServlet.ja
| va:227)
| at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.
| java:100)
| at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doGet(HtmlAdaptorServlet.java:81)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt
| erChain.java:290)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.
| java:206)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:9
| 6)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt
| erChain.java:235)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.
| java:206)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:2
| 35)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:1
| 91)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociatio
| nValve.java:190)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
| at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(Security
| ContextEstablishmentValve.java:126)
| at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityC
| ontextEstablishmentValve.java:70)
| 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(CachedConnectionVa
| lve.java:158)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109
| )
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Pr
| otocol.java:601)
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
| at java.lang.Thread.run(Thread.java:595)
| 16:16:30,933 WARN [TopicService] Topic is stopped.
| 16:16:30,933 WARN [TopicService] Topic is stopped.
| 16:16:30,933 WARN [TopicService] Topic is stopped.
| 16:16:30,933 WARN [TopicService] Topic is stopped.
| 16:16:30,933 WARN [TopicService] Topic is stopped.
| 16:16:30,933 WARN [TopicService] Topic is stopped.
When I am trying to make a JMS Connection to this topic from a simple Java client I am getting following excpeiton
Exception in thread "main" javax.naming.NameNotFoundException: ConnectionFactory not bound
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)
| at org.jnp.server.NamingServer.getObject(NamingServer.java:785)
| at org.jnp.server.NamingServer.lookup(NamingServer.java:443)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja
| a:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
| at sun.rmi.transport.Transport$1.run(Transport.java:153)
| at java.security.AccessController.doPrivileged(Native Method)
| at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
| at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
| at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
| at java.lang.Thread.run(Thread.java:595)
| at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall
| java:247)
| at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
| at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
| at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:667)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
| at javax.naming.InitialContext.lookup(InitialContext.java:351)
| at TestClientJBoss.main(TestClientJBoss.java:33)
It seems I am missing something in configurations. Please advise.
Thanks
Raj
Thanks
Raj
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214710#4214710
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214710
15 years, 10 months
[Installation, Configuration & DEPLOYMENT] - Re: Deploying Spring 2.5 Application in JBoss 5
by charliebarjel
Here is the exception stacktrace:
| 2009-03-03 08:44:06,404 WARN [org.jboss.util.xml.JBossEntityResolver] (main) Trying to resolve systemId as a non-file URL: http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
| 2009-03-03 08:44:18,419 DEBUG [org.jboss.util.xml.JBossEntityResolver] (main) Cannot resolve [publicID=null,systemID=http://www.springframework.org/schema/beans/spring...]
| 2009-03-03 08:44:18,419 WARN [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (main) schema_reference.4: Failed to read schema document 'http://www.springframework.org/schema/beans/spring-beans-2.5.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. @ vfszip:/C:/apache/jboss/jboss-5.0.1.GA-jdk6/jboss-5.0.1.GA/server/default/deploy/iwas.war/WEB-INF/applicationContext-hibernate.xml[12,106]
| 2009-03-03 08:44:18,419 WARN [org.jboss.util.xml.JBossEntityResolver] (main) Trying to resolve systemId as a non-file URL: http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
| 2009-03-03 08:44:18,419 DEBUG [org.jboss.util.xml.JBossEntityResolver] (main) Cannot resolve [publicID=http://www.springframework.org/schema/beans,systemID=http://www....]
| 2009-03-03 08:44:18,419 WARN [org.jboss.util.xml.JBossEntityResolver] (main) Trying to resolve systemId as a non-file URL: http://www.springframework.org/schema/beans
| 2009-03-03 08:44:18,419 DEBUG [org.jboss.util.xml.JBossEntityResolver] (main) Cannot resolve [publicID=null,systemID=http://www.springframework.org/schema/beans]
| 2009-03-03 08:44:18,419 DEBUG [org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer] (main) Error during deploy: vfszip:/C:/apache/jboss/jboss-5.0.1.GA-jdk6/jboss-5.0.1.GA/server/default/deploy/iwas.war/
| org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/C:/apache/jboss/jboss-5.0.1.GA-jdk6/jboss-5.0.1.GA/server/default/deploy/iwas.war/
| at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
| at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:337)
| at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:297)
| at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:269)
| at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:230)
| at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
| at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:698)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205)
| at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405)
| at org.jboss.Main.boot(Main.java:209)
| at org.jboss.Main$1.run(Main.java:547)
| at java.lang.Thread.run(Thread.java:619)
| Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI=http://www.springframework.org/schema/beans location=http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
| at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)
| at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:199)
| at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:170)
| at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132)
| at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118)
| at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:256)
| at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:239)
| at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:330)
| ... 22 more
| Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI=http://www.springframework.org/schema/beans location=http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
| at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:313)
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401)
| at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
| at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
| at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
| at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
| at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(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.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)
| ... 30 more
|
|
When trying to find a solution on google, I came across some posts that suggest that Jboss 5 is not compatible with Spring 2.5. Could this be the problem?
Thanks again.
Charlie
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214704#4214704
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214704
15 years, 10 months
[JBoss Cache: Core Edition] - Re: on child insert parent, child collection updated in DB b
by bstansberry＠jboss.com
The collection eviction is done via a call to the org.hibernate.cache.access.CollectionRegionAccessStrategy interface's remove(Object) method. The Hibernate/JBC integration implements that by calling JBC's Cache.removeNode(Fqn) method.
Calls to CollectionRegionAccessStrategy.remove() are all made via org.hibernate.action.CollectionAction.evict(). That in turn is called by the execute() method of the various subclasses of CollectionAction.
The PFER call comes via org.hibernate.engine.loading.CollectionLoadContext.addCollectionToCache(...)
Above classes are all in the "core" module of Hibernate Core.
I agree that the fact this only happens under load certainly seems like a big clue. Just not sure what to make of it yet.
I don't have experience with the Bitronix TX Manager, so don't know if it would have the synchronization ordering issue. But if you were seeing that problem I'd think you'd have other issues less subtle than this one.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214697#4214697
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214697
15 years, 10 months