[JNDI and Naming] - javax.naming.NameNotFoundException with Migration from JBoss-5.1.0 to JBoss-7.1.1
by Kevin Yuan
Kevin Yuan [https://community.jboss.org/people/kyuan] created the document:
"javax.naming.NameNotFoundException with Migration from JBoss-5.1.0 to JBoss-7.1.1"
To view the document, visit: https://community.jboss.org/docs/DOC-18532
--------------------------------------------------------------
I am also trying to connect to a stateless session bean, and it works partially – I can deploy my application ear successfully, also can contact the server, but no matter how I try to name the EJB, I get a NameNotFoundException, just like:
javax.naming.NameNotFoundException: eclipselink-advanced-model/TestRunner!org.eclipse.persistence.testing.framework.server.TestRunner -- service jboss.naming.context.java.jboss.exported.eclipselink-advanced-model."TestRunner!org.eclipse.persistence.testing.framework.server.TestRunner"
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178)
at org.jboss.naming.remote.protocol.v1.Protocol$1.handleServerMessage(Protocol.java:127)
at org.jboss.naming.remote.protocol.v1.RemoteNamingServerV1$MessageReciever$1.run(RemoteNamingServerV1.java:73)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
I have the following environment:
JBoss-as-7.1.1.Final
My EAR: eclipselink-advanced-model.ear
My EJB archive: eclipselink-advanced-model_ejb.jar
My stateless session bean: TestRunnerBean
Actually my application worked fine on JBoss-5.1.0, I have made the following changes with jndi.properties and lookup, my jndi.properties just like the following:
java.naming.factory.initial=org.jboss.naming.remote.client.InitialContextFactory
java.naming.factory.url.pkgs=org.jboss.ejb.client.naming
java.naming.provider.url=remote://localhost:4447
java.naming.security.principal=usera
java.naming.security.credentials=passworda
java.naming.security.authentication=none
And the lookup just like: ejb:eclipselink-advanced-model/eclipselink-advanced-model_ejb/TestRunner!org.eclipse.persistence.testing.framework.server.TestRunner
(for JBoss-5.1.0, the lookup is: TestRunner/remote-org.eclipse.persistence.testing.framework.server.TestRunner)
I have referred to the post: https://community.jboss.org/message/722635#722635 https://community.jboss.org/message/722635, and I also tried to add jboss-ejb-client.properties in the client classpath, still didn't help. BTW, my jboss-ejb-client.properties just like the following:
remote.connections=default
endpoint.name=client-endpoint
remote.connection.default.port=4447
remote.connection.default.host=127.0.0.1
remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false
remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false
remote.connection.default.username=usera
remote.connection.default.password=passworda
Does anyone can give me a hint to things I can try out? Any suggestion will be appreciated.
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-18532]
Create a new document in JNDI and Naming at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
12 years
[jBPM] - Unable to load session snapshot in jbpm 5.3
by Bira Neto
Bira Neto [https://community.jboss.org/people/biraneto] created the discussion
"Unable to load session snapshot in jbpm 5.3"
To view the discussion, visit: https://community.jboss.org/message/739415#739415
--------------------------------------------------------------
I've searched the posts and found a few similar problems. I decided to post this anyway for two reasons. 1. The stack trace of the cause wasn't the same. 2. This wasn't happening on version 5.2
I am getting the error
java.lang.RuntimeException: Unable to load session snapshot
with main cause
Caused by: java.lang.NullPointerException
at org.drools.common.Scheduler$ActivationTimerInputMarshaller.deserialize(Scheduler.java:230)
at org.drools.marshalling.impl.ProtobufInputMarshaller.readTimer(ProtobufInputMarshaller.java:597)
at org.drools.marshalling.impl.ProtobufInputMarshaller.readSession(ProtobufInputMarshaller.java:292)
at org.drools.marshalling.impl.ProtobufInputMarshaller.readSession(ProtobufInputMarshaller.java:161)
at org.drools.marshalling.impl.ProtobufMarshaller.unmarshall(ProtobufMarshaller.java:117)
at org.drools.persistence.SessionMarshallingHelper.loadSnapshot(SessionMarshallingHelper.java:91)
I'm currently using Postgres.
This happens after loading a knowledge base and executing just one workflow. After that the same session can't be loaded anymore.
Any ideas why this could be happening?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/739415#739415]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years
[IronJacamar] - ironjacamar maven validator 1.1.0.Alpha7 throws
by gonzalad
gonzalad [https://community.jboss.org/people/gonzalad] created the discussion
"ironjacamar maven validator 1.1.0.Alpha7 throws"
To view the discussion, visit: https://community.jboss.org/message/741219#741219
--------------------------------------------------------------
Hello,
I'm trying to validate my jca connector with Ironjacamar maven validator (as documented here : http://docs.jboss.org/ironjacamar/userguide/1.1/en-US/html/validator.html... http://docs.jboss.org/ironjacamar/userguide/1.1/en-US/html/validator.html...)
I get the following error when running mvn clean install on my pom.xml :
java.lang.IllegalStateException: Unable to find an annotation scanner implementa
tion
at org.jboss.jca.common.spi.annotations.repository.AnnotationScannerFact
ory.getAnnotationScanner(AnnotationScannerFactory.java:72)
at org.jboss.jca.validator.Validation.validate(Validation.java:148)
at org.jboss.jca.validator.maven.ValidatorMojo.execute(ValidatorMojo.jav
a:72)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Default
BuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:209)
My pom.xml contains
<plugin>
<groupId>org.jboss.ironjacamar</groupId>
<artifactId>ironjacamar-validator-maven</artifactId>
<version>1.1.0.Alpha7</version>
<executions>
<execution>
<goals>
<goal>validate</goal>
</goals>
</execution>
</executions>
<configuration>
<outputDir>.</outputDir>
<rarFile>${project.build.directory}/${project.build.finalName}.rar</rarFile>
</configuration>
</plugin>
If i add a dependency to ironjacamar-common-impl-papaki, everything runs fine :
<plugin>
<groupId>org.jboss.ironjacamar</groupId>
<artifactId>ironjacamar-validator-maven</artifactId>
<version>1.1.0.Alpha7</version>
<dependencies>
<dependency>
<groupId>org.jboss.ironjacamar</groupId>
<artifactId>ironjacamar-common-impl-papaki</artifactId>
<version>1.1.0.Alpha7</version>
</dependency>
</dependencies>
<executions>
<execution>
<goals>
<goal>validate</goal>
</goals>
</execution>
</executions>
<configuration>
<outputDir>.</outputDir>
<rarFile>${project.build.directory}/${project.build.finalName}.rar</rarFile>
</configuration>
</plugin>
Should I open an issue ?
Thanks
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/741219#741219]
Start a new discussion in IronJacamar at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years
[JBoss Tools] - JBoss Tools and Developer Studio Candidate Release
by Max Rydahl Andersen
Max Rydahl Andersen [https://community.jboss.org/people/maxandersen] modified the blog post:
"JBoss Tools and Developer Studio Candidate Release"
To view the blog post, visit: https://community.jboss.org/community/tools/blog/2012/06/12/jboss-tools-a...
--------------------------------------------------------------
The release candidate of JBoss Tools and Developer Studio is now available - mainly with bugfixes but also a few nice improvements for AS 7, OpenShift and Maven integration.
https://community.jboss.org/servlet/JiveServlet/showImage/38-4854-18193/j... https://community.jboss.org/servlet/JiveServlet/downloadImage/38-4854-181...
h4. CR1
Developer Studio: [ http://devstudio.jboss.com/earlyaccess Download] | Tools: [ http://www.jboss.org/tools/download/dev Download] [ http://download.jboss.org/jbosstools/updates/development/indigo/ Update Site] | [ http://docs.jboss.org/tools/whatsnew What's New] [ http://www.jboss.com/index.html?module=bb&op=viewforum&f=201 Forums] [ http://jira.jboss.com/jira/browse/JBIDE JIRA] [ http://twitter.com/jbosstools Twitter]
JBoss Tools is a set of plugins for Eclipse that complements, enhances and goes beyond the support that exist for JBoss and related technologies in the default Eclipse distribution.
JBoss Developer Studio is a fully bundled Eclipse distribution which not only includes majority of JBoss Tools but also all its needed dependencies and 3rd party plugins allowing for an easy one-click and no-fuzz installation.
If you are into doing your own bleeding edge eclipse plugin assembly, JBoss tools is for you, if you are more into having something that "Just Works" then JBoss Developer Studio is the way to go.
h2. Installation
+JBoss Developer Studio+ comes with everything pre-bundled in its installer. Simply http://devstudio.jboss.com/earlyaccess download it and run it like this:
java -jar jbdevstudio-<installername>.jar
Note, if you are on Mac OSX 64-bit we recommend you ensure to select the 32-bit option in the multi-platform installer to get Visual Page editor working and use much less memory.
Similar if you are on Windows 64-bit then use a 32-bit JDK to get 32-bit version running.
+JBoss Tools+ requires a bit more:
This release requires at least Eclipse 3.7.1 but we recommend using the http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/... Eclipse 3.7.2 JEE Bundle since then you get most of the dependencies preinstalled.
Once you have installed Eclipse, you either find us on http://marketplace.eclipse.org/content/jboss-tools-indigo Eclipse Marketplace under "JBoss Tools (Indigo)" or use our update site directly.
The update site URL to use from Help > Install New Software... is:
http://download.jboss.org/jbosstools/updates/development/indigo/ http://download.jboss.org/jbosstools/updates/development/indigo/
Note: SOA tooling such as Drools, jbpm, ESB, Teeid etc. are not included in the JBoss Tools core releases at this time - they will be available separately.
h2. JBoss AS 7
The server adapter for JBoss AS 7 had a series improvements done in its handling of remote management and JMX connections. One thing that is relevant is that because of AS 7.1 https://community.jboss.org/community/tools/blog/2012/02/29/excited-about... Secure by default approach when you launch remotely the management services are not autoatmically exposed. We keep that secure-by-default in the tools, but now also provides a simple checkbox to allow you to expose the management service when we launch it to actually remotely manage the server.
https://issues.jboss.org/secure/attachment/12354382/JBIDE-11921.png https://issues.jboss.org/secure/attachment/12354382/JBIDE-11921.png
Of course just exposing the port does not make it fully available before you have added a user to the server. You can read about how to do that in https://community.jboss.org/community/tools/blog/2012/02/29/excited-about... this blog.
And finally the server adapter now works with IPv6, allows deploying outside of the deployments folder and it does not choke on a space in the server part - Hurray!
h2. OpenShift, now faster and more patient
One of the most common bug report we got in the Beta's (thank you for the feedback!) was that when creating OpenShift applications our wizard would time out and you would have to manually import the project again. We now have extended the timeout period to three minutes to accomodate for overloads, network latency etc. but also given you the option to wait some more for the OpenShift provisioning to be fully done.
A new feature of the application creation wizard is also to be able to set the size of the Gear your application will run on and to enable scaling for your applications.
http://docs.jboss.org/tools/whatsnew/openshift/images/gears-and-scaling.png http://docs.jboss.org/tools/whatsnew/openshift/images/gears-and-scaling.png
Mind you that the list of possible gears depends on your users permissions.
Various actions like Tail Files, Environment variables and Port Forwarding which previously were only available in OpenShift Explorer is now also available from the OpenShift server adapter.
http://docs.jboss.org/tools/whatsnew/openshift/images/server-adapter-acti... http://docs.jboss.org/tools/whatsnew/openshift/images/server-adapter-acti...
And for those users with large set of applications or slow networks we've made the loading of OpenShift metadata more incremental giving you faster feedback,especially on networks far away from the OpenShift servers.
h2. Maven and Endorsed Libraries
If you have ever had to fight with using JavaEE 6 Webservices on Java 6 with Maven and Eclipse at the same time you know what a pain having to use that combination can be because JavaEE 6 Webservices are actually using libraries that are not available before Java 7. Meaning you have to configure and setup endorsed libraries in Eclipse, which actually does not have such a feature exposed on projects, but only at the JVM level setup. Thus its "easy" for running applications but not when compiling.
In Maven there are various tricks to solve this and none of them are obeyed/understood by m2eclipse - but not anymore.
http://docs.jboss.org/tools/whatsnew/images/endorsed_libs.png http://docs.jboss.org/tools/whatsnew/images/endorsed_libs.png
We've added a Maven configurator which will look for the common tricks to set and configure endorsed libraries and when they are found inject an "Endorsed Library" classpath container with the approprate classpath entries.
Allowing you to not have to worry about this anymore when using Maven + Eclipse. Fred writes more in detail about how this works in http://docs.jboss.org/tools/whatsnew/maven/maven-news-3.3.0.CR1.html What's New
h2. Pixel Density
And an example of where the little details matters comes that BrowserSim now has controls for pixel density allowing you to get a better and closer representative layout of your mobile applications.
http://docs.jboss.org/tools/whatsnew/vpe/images/3.3.0.CR1/pixel-ratio.png http://docs.jboss.org/tools/whatsnew/vpe/images/3.3.0.CR1/pixel-ratio.png
h2. ...and more
As usual screenshots and more explanation of what is new are available from the http://docs.jboss.org/tools/whatsnew What's New site!
Let us know what you think and remember that http://www.jboss.org/events/JUDCon/2012/boston/agenda/day1track1 Xavier and http://www.jboss.org/events/JUDCon/2012/boston/agenda/day2track1 I will be showing a lot of these features at JUDCon and http://www.redhat.com/summit/ Red Hat Summit w/JBoss World end of this month with a GA release. See you there ?
Have fun,
Max
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/community/tools/blog/2012/06/12/jboss-tools-a...]
12 years
